NO> The default save is in the internal SD card. Just copy the whole " clockworkmod/backup/xxxbackupfilexxx" in the external card and similarly copy it back to the internal SD card if necessary

1) I would highly recommend Dolphin Browser HD as an alternative browser. Try it and 9.9/10 you will not want to use the default browser anymore. It is not only faster and have great Tab and bookmark features. As for your question, I don't think there is a solution for the default browser and quite few other browsers too. However Dolphin with its GESTURE features will help you greatly

QUOTE : Gesture commander feature is one of the most useful functions of the browser, as it shortens the time to access a website or do another actions such as, go back, forward, go to the top or end of a webpage. Basically, you can draw a special sign on the screen and the application will recognize it and act accordingly by automatically sending you to the webpage you previously specified. To make a gesture command you will need to click on the small hand on the left bottom corner of you browser and then draw the sign on the screen.

The small hand icon can be moved on the right bottom side or you can hide it. There's a number of predefined gesture controls that you can check by going to going to Settings / Gesture settings. You can also create you own gestures by clicking on the Create a gesture option. From what I noticed, the sign are immediately recognized and greatly improves the functionality of the application. There's no need to scroll through your bookmarks or scroll from the top to the bottom of a webpage, as you can do it with only two clicks.

[attachmentid=2015439]

2) No idea - perhaps a factory reset will help . Backup your data first using Titanium Backup or MyBackupPro

What did you do ? This shows the SGT is BRICKED. Meaning the SGT  is unable to connect to even the computer. So far I have yet to read of anyone having such an issue. This scenario was very common with the Galaxy S phones not so much for the TAB. It happens in the Galaxy S because some of the SGS phones were manufactured with the 3 buttons disabled, meaning by default pressing the 3 buttons will not get the phone into recovery or download mode

klwong99: Did you try to flash a new kernel from Paul ?

If so, reflash it as I just read one user same as your situation flashing Paul Kernel R2
This is what Paul say :
Just MCK r2 again via Odin and it will come back to life...

http://android.modaco.com/content-page/330...xy-tab/page/20/

the user finally got it done. If you are in same situation, PM the user and ask him exactly how he got his up again

Always remember when you flash through Odin, if you see FAILED DO NOT ever disconnect the TAB from the computer. You will lose the connection between the TAB and computer

So I suggest you try this trick which sometimes work for the Galaxy S

Switch off the TAB. Hold down both volume buttons and then at the same time plug in the usb into your TAB  from the computer.  When you see activity let go of the buttons . It should put you into download mode  . If you reach this stage , launch Odin and reflash roto JME

When you flash recovery, did you check the CFRoot file should be in tar format and not over extracted ?

Always remember when you flash through Odin, if you see FAILED DO NOT ever disconnect the TAB from the computer. You will lose the connection between the TAB and computer

So I suggest you try this trick which sometimes work for the Galaxy S

Switch off the TAB. Hold down both volume buttons and then at the same time plug in the usb into your TAB  from the computer.  When you see activity let go of the buttons . It should put you into download mode  . If you reach this stage , launch Odin and reflash roto JME

When you flash recovery, did you check the CFRoot file should be in tar format and not over extracted ?

At least now we see some life back to the TAB. So try a hardware reset to see whether you csn boot it back ?

Reset Galaxy Tab with Hardware Keys

Make sure tab is turned off, Press and hold the Power button for about 10 seconds to turn it off.
Press and hold the “Volume Up” and “Power” buttons at the same time, when logo appears on the screen release the “Power” button and continue press the “Volume” button
When recovery screen appears use “Volume Up/Down” buttons to navigate and select “wipe data / Factory reset” by pressing the “Home” or “Power” button (Depends on Galaxy Tab model).

Benny, my tab shown "POWER RESET or UNKNOWN UPLOAD MODE" after followed your trick, hold down both volume buttons and then at the same time plug in the usb into your TAB . But it's not show the download mode, what can i do now?

Can you reproduced above ? If so, with TAB connected top PC, Launch Odin , select repartition and attempt to boot it - select START

Found this on xda for you.Hope it helps.

The phone --!-- computer problem is solvable.

Power off your phone, and power it back on with holding the volume down button, when you see the --!-- sign release the buttons.

You are now in download mode, although you cant see the little android with the shovel. Connect it to a pc with an odin 1.7 open and you will be able to reflash it.
                       

CONGRATS !!! So wanna try reflash clockwork again ? You could have make a mistake somewhere

I used two backup programs - call me kiasu and kiasi.

I have yet to restore any stuffs on the TAB , so I cannot exactly comment how these 2 work. Backing up is so far very good with no issues. I would like to comment my usage of these 2 tools in my previous NexusOne, Galaxy S, and HD2 ( android) and present Dell Streak

Titanium is a more complete solution . If you are restoring back to the same rom there is no issue at all ; can say you will get a perfect 100% restore. However things is a bit tricky if you wish to restore it to another rom ( even though is same cook , perhaps a upgraded version). You will not have a 100% perfect restore - more of 99% ? You will face force closure of some apps ( random ) and for such apps you need to uninstall and reinstall to solve the problem. When you restore to a different rom, all related system files/apps of the older rom are highlighted in red and will not be restore. In a way this is good but it also means you will not be able to restore fully bak your data example your mail, SMS, settings etc. So what I normally do is I do a manual selection of the red flag items to restore. I do this only after I complete the first auto restore

MyBackUpPro I used mainly because it saves all my APK files nicely in a folder. It is very useful when you need to reinstall any apps. So i use this more of a secondary backup. You can have selective restore of apps, apps+data, or data only. I find restoration of SMS, bookmarks, apps settings etc is better using it

Congrats on your new 'toy". Tonight going bed with it instead of someone else ???

---

Added on January 26, 2011, 11:50 pm
Unlikely as when you successfully flash Roto JME - it will remove any protected bootloaders. If you want to try again, just remember to boot it at least one more time before flashing the recovery

You mean your concern is only the keyboard ? Just open a document , say write a sms - hold down on area you wish to write, select input method - and see what other keyboard choices are there ? If there is a full English one - select it to be your default. You can also check for KB alternatives in the Market. Use VLINGO - is free and plus point it can be voice activated to accept input by voice

---

Added on January 27, 2011, 12:14 am

YES. Strange ? Where is your source of the Roto rom ? It is supposed to remove the protected bootloaders
Anyway, you can now use the patch first before flashing the recovery again

I don't think Roto rom remove protected bootloaders.

Well not exactly.

To my understanding, if you update to the latest official build you will get a signed bootloaders and from there on you can only install rom/kernel with signed bootloaders.

In roto rom however he removed the bootloaders so people can still update to the latest without have a protected bootloader.

Hence the warning by chain fire not to update to the official rom because of the signed bootloaders.

I think you should put a warning too.

Unless my understanding of this is wrong.