Related
I was thinking that dual booting on a single device would be a really great thing. A huge step.
Why we cannot do it?
Cannot we "emulate" partitions of the internal memory on the sdcard and then create a modified spl to boot from sdcard?
I was thinking that it is possible to make the sdcard working like internal memory..
Is it so difficult?
blackgin said:
I was thinking that dual booting on a single device would be a really great thing. A huge step.
Why we cannot do it?
Cannot we "emulate" partitions of the internal memory on the sdcard and then create a modified spl to boot from sdcard?
I was thinking that it is possible to make the sdcard working like internal memory..
Is it so difficult?
Click to expand...
Click to collapse
I think this would be a good idea too. have a stable boot partition, then on the second boot have our "testing" partition.
Is this even possible?
Whether or not this is possible, I don't know.
But kinda related, I would like to see a bootloader that made an "image" of the entire phone to sdcard AND would also restore the entire "image" of the phone.
Why?
It would give us an easy way to test out different roms!
You could have your stable build for regular day-to-day use, you could also "image" any other rom you install, then you could switch back and forth without the need for a computer to restore using Fastboot. Using this method, you could "image" any number of builds you wouldn't to try.
There may be a way this could be done right now, I don't know. I haven't found out how. If it's already an option, someone please point me in the right direction!
It would be very difficult cause you would have to find another OS that isn't linux based. Even with a bootloader all the files will be knocked off from the previous flash because everything in these builds are pretty much in the root folder. The OS runs on these references and if you change them the OS will not run. You would have to rework the whole OS to get this to work
Someone delete me
argh xda is so slow
It would be very difficult cause you would have to find another OS that isn't linux based. Even with a bootloader all the files will be knocked off from the previous flash because everything in these builds are pretty much in the root folder. The OS runs on these references and if you change them the OS will not run. You would have to rework the whole OS to get this to work
Booting off the sdcard could be possible but would be pointless to do.
Everytime you mount the sdcard to the computer it would crash the phone. Also, There's not really enough internal space to dual boot. 1 decent ROM barely fits on as it is.
blueheeler said:
Whether or not this is possible, I don't know.
But kinda related, I would like to see a bootloader that made an "image" of the entire phone to sdcard AND would also restore the entire "image" of the phone.
Why?
It would give us an easy way to test out different roms!
You could have your stable build for regular day-to-day use, you could also "image" any other rom you install, then you could switch back and forth without the need for a computer to restore using Fastboot. Using this method, you could "image" any number of builds you wouldn't to try.
There may be a way this could be done right now, I don't know. I haven't found out how. If it's already an option, someone please point me in the right direction!
Click to expand...
Click to collapse
Cyanogen mentioned he was looking into this to try implement it into his recovery image. I don't think anyone's been able to restore a complete nandroid backup outside of fastboot...yet. However people are working on it. I think it's doable.
Meltus said:
Booting off the sdcard could be possible but would be pointless to do.
Everytime you mount the sdcard to the computer it would crash the phone. Also, There's not really enough internal space to dual boot. 1 decent ROM barely fits on as it is.
Click to expand...
Click to collapse
Maybe, maybe not. A second or third EXT partition on the sd card could possibly be used for a dual/tri boot enviornment. Only the FAT32 portion gets mounted when you mount through your phone. And there would be virtually no difference when mounting through ADB. Now would be a good time for those interested in persuing this notion to have a look at the data2sd thread. Sounds very possible to me.
overground said:
Maybe, maybe not. A second or third EXT partition on the sd card could possibly be used for a dual/tri boot enviornment. Only the FAT32 portion gets mounted when you mount through your phone. And there would be virtually no difference when mounting through ADB. Now would be a good time for those interested in persuing this notion to have a look at the data2sd thread. Sounds very possible to me.
Click to expand...
Click to collapse
no, i'm pretty sure all partitions get mounted, they just don't show up on windows.
on linux they all appear for me when i mount the phone.
also, sorry about the triple post, dunno wtf happened there.
Debain As Primarly OS
What Ive Been wishing for is someone to make the Dream Boot straight to Debian, No android running in the background.
Then we could boot into a debian with g1 drivers (if open source) and have gpu accl. x11.
Then maybe dual-booting android.
Im willing to try to get a debian img to boot on my g1 if someone wants to tell me where I would start to even try to attempt it.
lolz
Booting straight to Debian would be cool, except there is really no use for it on our G1's. We are best off running after loading Android, although I'm sure one day we could just boot Debian. What would the point of Debian be on our G1's? I'm running Deb5 on my Dell Mini that has a 9" inch screen and can barely see text.... how in the world would this become useful on a 3" screen???
just my £0.02
there is an old saying in my country. "if you don't believe it can work, then it won't for you". that holds so true for development. yes you will make mistakes on the way. heck i'm on my fourth G1 so far (and i suspect there will be more to come!) I love this phone, and i love the fact that we as a community can build such amazing things as the hero rom for the device.
what would we have done if the first person had said the wheel was impossible? or if the first person had said that fire was impossible. or (shock horror) electricity? or television? or telephone? or GPS? or the internet?
all of those were impossible until someone worked out how to do it.
dual boot would be pheasably posible, as the device is primeraly a computer first, and then a phone second. it boots a linux kernel from the bootloader (if i am correct in my understanding) so all we would need to do is create a bootloader with a choice in it, and then direct the phone to boot a second partition from the SD card.
the phone does mount all partitions - but only if the OS understands all partitions (test it for yourself - if you have windows and apps2sd mount the partitions and then run an app from the card it still works. but it does not under linux).
to answer the what would be the point questions, what would be the point in not doing it? surely development for a device like this is all about trying stuff, and then if it doesn't work not doing the same thing again.
i believe that a second OS would boot quite comfortably on a decent SD card. not that i have this working or anything. to make the screen readable, you just use a lower resolution (320x480). i would probably not want a full-blown GUI linux anyway, what i would want from a dual-boot OS would be a working command-line debian with FULL hardware access - allowing me to really use the phone as a fully-functioning remote terminal for my server.
i recon, though, that one thing that would be absolutely amazing is being able to have a fully-portable totally reliable XDA-Developers OS on my phone.
so, why do we not just try as much as we can to get this working? how do we start?
milestone.it said:
just my £0.02
.....
so, why do we not just try as much as we can to get this working? how do we start?
Click to expand...
Click to collapse
Just hack the spl and flash it, but be cautionous as hell
Okay, I dont claim to know alot but I'll share my thoughts anyway
When you mount the SD all partitions get mounted, if you go into disk management in windows you can see the 'Unknown' partition if you have an ext2 partition.
Secondly, we don't really 'boot' debian, it just mounts an image file on your SD card that contains the debian binaries. As I understand it there is no reason these binaries couldn't be included in android (like busybox).
Thirdly, do we really want debian? What we need is a very light OS, android is the perfect base, take away all the gloss and its linux underneath. I love the idea of having repositories and being able to apt-get and even develop on the device.
Lastly, we're forgettign why android is such a good platform, the reason android is useful is because of the Dalvik VM, it's what allows us to make portable apps that will work on any android phone. I seriously doubt everyday users will be interested enough to learn to compile source on their phone. I've worked programming games for mobiles in J2ME and it was horrible, there was barely any portability between manufacturers, i believe android will be alot better adn from what i've seen (with people porting from other droid devices) this seems to hold true. It will be interesting to see if Android gets bloated with manufacturer specific API's like J2ME.
Also I'll just throw this out there... I'm not a fan of being tied to google, yes google helped along the way, but its not 'google android', its android. Wasn't it strange hoe Gmail worked fine, but the email app didnt? (K9 is perfect though!)
hi guys, i'm not at all a developer of any kind, i suck even at web design, but here's my thoughts expanding on the whole "what if the wheel didn't work" scenario
inventions are created by the need to do something, we need to get from A to B faster, lets make a car. we want to entertain our families in the evening, Hey look, TV. i need to tel my wife to get some milk while she's at the shop, Voila, Mobile Phone.
Basicaly the point i'm trying to make is, if somebody finds a NEED for dual boot on android, then so be it, it shall be done, maybe not today, maybe not tomorrow, but if something is needed, then something shall come from it. we develop technology when we need to do something faster, easier, or just plain do it.
if somebody decides they NEED dual boot, i'm pretty sure they will figure out how to do it, either that or ask haykuro for some tips and alot of help, but i think he's still too busy with regular life at the minute, i'm not so sure, all i know is he's definately a legend, and maybe will want a piece of dual-boot pie
So who is the great man who want to try to do this? ;D
I offer my help, if it could be useful..
re: dual booting
would it be blasphemous to want to try out winmo 6.5 or 7 on these?
personally, i'd love to see WM on here. mainly, just so we know it's possible.
People are always slating Windows but, personally, i don't see whats wrong with it (Linux is my primary OS and always will be ). It would be nice to have say WM for work and Android for play
any news on this? I would really like to run a hero rom one day and then cupcake the next while not losing my settings...
I understand this directory has something to do with Bluetooth.
There are ten ~6.7 MB files in that directory with names like core.872 and core.19735.
I did a nandroid backup and then removed them. Everything seems to be OK, but I don't use BT for anything.
Any idea what these are? Could this be related to the BT ROM leak?
jonnythan said:
I understand this directory has something to do with Bluetooth.
There are ten ~6.7 MB files in that directory with names like core.872 and core.19735.
I did a nandroid backup and then removed them. Everything seems to be OK, but I don't use BT for anything.
Any idea what these are? Could this be related to the BT ROM leak?
Click to expand...
Click to collapse
I wish people wouldn't call it a "ROM leak"... it just sounds so silly. ROMs don't leak and the ROM in the Hero isn't leaking. *SOMETHING* is just occupying data space.
Having said that... those are core dumps. Weird, I'd have expected Android to disable core dumps. The phone doesn't have file(1), so it's a little difficult to tell what dumped, but the number in the extension is the PID of the faulting process.
Mine doesn't have any, or I'd yank one over to my desktop and investigate it.
They *are* taking up space in /data, which is going to make the phone look like it has less storage space available (the number in the Settings app will go down). Erase them, they're useless to you.
It might be interesting to search the whole phone with find(1)... that at least is there (or maybe it's in the busybox MoDaCo installs ^_^) and see if there are any other dump files hanging around.
posguy99 said:
I wish people wouldn't call it a "ROM leak"... it just sounds so silly. ROMs don't leak and the ROM in the Hero isn't leaking. *SOMETHING* is just occupying data space.
Having said that... those are core dumps. Weird, I'd have expected Android to disable core dumps. The phone doesn't have file(1), so it's a little difficult to tell what dumped, but the number in the extension is the PID of the faulting process.
Mine doesn't have any, or I'd yank one over to my desktop and investigate it.
They *are* taking up space in /data, which is going to make the phone look like it has less storage space available (the number in the Settings app will go down). Erase them, they're useless to you.
It might be interesting to search the whole phone with find(1)... that at least is there (or maybe it's in the busybox MoDaCo installs ^_^) and see if there are any other dump files hanging around.
Click to expand...
Click to collapse
Great info, thanks. I wonder if they're related to bluetooth crashes since they're in the btips directory?
I searched for other files named core* but nothing looks like a core dump. There's a core.xml and a bunch of "coredump_filter" in proc directories and that's about it.
I think leak is an appropriate term though. Applications that have memory leaks consume memory that they can't release. This is similar, just with the onboard flash.
I probably know the answer already but hoping...is there anyway to delete these core dump files in the btips folder without having to root the phone? Could an app or script on non-rooted device be able to just delete those files? I'm surprised there's no way through the phone to clear system dumps/cache, etc.
Looking for a way since a lot of people have this problem but not many will be comfortable rooting.
Hi all,
I'm reaching out to the Android community as a whole hoping to get some pointers. I'm having a hard time finding the information I need here and by googling (although I'm sure it exists) so I was hoping to get some tips or pointers from some people in the know. I've reached out to a few people privately who I know have already done this kind of work but no one is responding to me which is kind of a bummer.
While I'm specifically trying to port the latest Incredible OTA to the EVO, I'm hoping any information gathered here will be helpful to others and applicable to other devices.
Why port the Incredible rom to the EVO? Well for starters the hardware is virtually identical from what I can tell, so it's a good starting point to teach myself some basics and get familiar with Android and rom construction. Second, it's to solve a strange MMS problem for EVO users on Cricket and MetroPCS. We can't send MMS using Sprint based roms but can with Verizon based ones, or by putting the Verizon MMS app on our Sprint roms, but it doesn't work properly. Some people are looking to disassemble the MMS app and figure out what it will take to get it working properly on a Sprint rom. I'm attacking from the other direction (since I have seen it work with the avafroyo vcrc3 rom) by taking the entire Incredible rom and making it work on the EVO.
So my starting point was to install a copy of the latest rooted Incredible OTA on to my phone and then install the latest EVO kernel from HTC. This definitely got me up and running, however I could not use the hardware buttons below the screen (VERY difficult to do anything on the phone lol) and also quickly found out that the SD card was not being recognized either.
I think it was about this time that I found the Android Kitchen that had support for both the incredible and the evo, and starting using that instead of my entirely manual way.
I found that to fix the hardware buttons below the screen I just needed to remove the incredible-keypad.kl file from /system/usr/keylayout and replace it with the supersonic-keypad.kl file from a EVO rom. Maybe renaming the incredible file would have done the trick? Is the kernel somehow looking for a file by that name? I have no idea how this works and would love some explanation.
So now that I had the buttons working I was able to freely navigate the phone and find what else didn't work. It seems that all thing related to the BCM4329 broadcom chip are not working, which means that there is no wifi, there is no bluetooth, and there is no FM radio. All of these features produce errors or don't work within any applications that use them or attempt to turn them on. The SD card was not being recognized so I couldn't read or write to it. Also screen rotation is not working.
Since I'm interested in preserving the apps and framework from the Incredible verizon rom I stayed away from the /system/app and /system/framework folders and looked in other places. I found that bin, etc, and lib folders also look virtually identical between the two roms except for a few minor differences. These also appear to be mostly drivers and stuff. So what I then did was merge the two versions from each rom and replace duplicates with the EVO versions. After this I found that I had proper SD card access again and I know GPS is working as well (no clue if it did before or not).
So at this point I have a rooted Incredible rom running on my EVO with the verizon incredible apps and framework. GPS, 3G, buttons, USB, sd card all work, however still no wifi, bluetooth, or fm radio. It's all this one BCM4329 chip. The drivers and related files all seem to be the same. The incredible and the EVO both use the same chip from what I can tell. I don't know where the breakdown occurs now. Is it in the framework or app? Is the support for the wifi and stuff built directly into the kernel? I've noticed during repacking of the boot image that there seems to be a driver in there for the broadcom chip.
I found a sensor file in the /system/lib/hw folder called sensors.inc.so. I copied over a sensors.supersonic.so file from the EVO rom and also renamed a copy to sensors.inc.so just in case. This hasn't helped with any of the rotation though. It seems like the contents of /system/lib are almost identical between the Incredible and EVO roms and these seem like they're all hardware drivers.
Anyone have any input towards getting screen rotation and the wireless stuff working? I feel like I've made decent progress literally replacing stuff, but I've either replaced too much, or there now needs to be some real editing somewhere, or something.
I cracked the img format for Garminfones... started out by looking at the format of the file and it turns out the only difference is the loader addresses.
Took the stock recovery and disabled security, which worked. Then modified the boot.img to disable security and had the filesystems mount rw by default and flashed it to the recovery partition. Booted into recovery mode and viola... security disabled. Now it is time to flash it to the boot partition and cross fingers.
Now I just need to figure out how to compile a working recovery mode... preferrably one that can be activated by keypress. Not sure how to do that part. I can only get to recovery and bootloader mode after booting into the os.
I should have a working mkbooting soon so I don't have to hex edit the generated img files.
Well done!
I look forward to any progress reports that you make.
Are you using the official or leaked version of the 2.1 Eclair?
The official and leaked versions are equal.
And I did find out that we do have fastboot It's the blue screen that you get when you hold UP+POWER, or do adb reboot bootloader... two different messages on the screen. I can get fastboot to accept a reboot-bootloader command, but I'm having some issues actually getting any information out of it or flashing something like a boot image.
To get it to respond, you do:
fastboot -i 0x091E <command>
the -i makes it specify the Vendor ID, since fastboot only accepts a few vendors by default.
I also found out that I don't have to rebuild the mkbootimg program... if you add --base 0x1AC00000, then the load addresses match up in the resulting img file.
If someone is willing to host it, I can share the modified boot.img that sets ro.secure=0 and mounts the filesystems RW by default.
Hey, just joined to reply to this thread. Is it possible for you to upload to a file-sharing site such as megaupload, fileserve, etc.
I'm just getting into this whole rooting/modifying stuff. I used z4root to root my A50 and have installed superuser. I have deleted some of the carrier .apks but am thinking I should have made a back-up before doing so. I also bought setcpu from the market before finding out the Qualcomm chip does not allow overclocking.
Can I ask what the point of modifying the boot image is? Is this the first step in being able to install custom roms to the phone?
Anyway, appreciate the effort you guys have put in to modifying the phone.
You get a higher level of access, along with things like being able to customize parts of the phone, in my case enabling read/write by default. I also am planning on playing a bit, like remapping partitions... the instructions are in the init.rc file.
Always take a dump_image (or remount all mtd partitions as read only and just use cat to dump the mtd partitions). Also tar up each of the root folders (and files) in case you need quick access to any files you may have deleted. If you need a system app back and you don't have a backup, you have to reflash 2.1 again. Very important... if you care about the Garmin map software, make sure to get the /storage folder, including the one in it named .System... you can recover the maps, vehicles, etc by using two different Garmin web update windows programs-- one for the system stuff and one for the maps. Better safe than sorry.
any news on this
What would we need to be able to overclock?
I spent a good portion of the day yesterday rooting and installing CyanogenMod on my fiance's MyTouch Slide, and I have to say, it was amazing. It's a lot more than just a throwing around some custom default apps, cleaning up bloatware, even adding some kernel modules... I can do all of that on my rooted Garminfone just fine. It also had the Android 2.3 base, and it has polish and refinements that just can't be done without a custom built ROM.
I bought my Garminfone on purpose, even knowing that it shipped with Android 1.6, even knowing that the interface was awful, even knowing that the device wasn't going to sell as well as I wished it would. I bought it for it's offline maps, and for it's fantastic GPS. Things have improved since I bought my device... Android 2.1 was released, an improved user interface arrived, I gained root access and was able to clean up some stuff, etc. etc. But none of that prevented me from being jealous yesterday after seeing CyanogenMod. Further, Cyanogen has experience with preserving apps through the process of installing his mod for the first time; He did it when Google first sent him the Cease and Desist letter barring him from packaging CyanogenMod with Google Apps. I'm not sure HOW he did it, and I don't care, but I do think that it's very possible for him to do just that again with our Garmin Maps and the associated apps.
For these reasons, I suggest that we could have our cake, and we could eat it too: Have a modern OS (Based on Android 2.3), have a clean, unified interface, with no bloatware AND our maps... Cyanogen is not known for making his mod for phones he doesnt own. Further, as we all know, ours was possibly the worst selling and least popular android device ever released to market. While I consider myself versed in the ways of Linux, I am not a developer. I run Gentoo, and have the associated skills, and I will contribute in any way I know how, but hacking is not my forte. I can't expect brilliant minds to work for any project for nothing. Therefore, I am putting my money where my mouth is... I'm going to take all the money from my weekly paycheck that I can afford, and I'm going to donate it to that project. It won't be much... I am a starving college kid, after all... but it will be generous within my means. I am also going to post a reference to this thread everywhere I know how... My contribution might be small, but the community might be able to get something together that is mighty.
Visit topic 5864-garminfone on their forums to add your support.
(Edit: They moved my post, I have corrected this with the correct forum topic)
When I first got my G-tab I was baffled by all the instructions and the literally thousands of posts in the forum. Even now, I haven't been able to find exactly how (or why) I should update my kernel. That said, I have TNT Lite running and I love my g-tab. Exploring the possible uses and utilities on it provides hours of fun. Now - here is my question. I stumbled on some instructions for installing the ROM and I have used those same instructions to install several patches to the Rom. I see all this commentary on Clockwork, side loading, etc. and I wonder if I am missing something. Today I just installed the .25 patch for TNT-Lite. I downloaded the rar file, unzipped it on my PC to get the Recovery folder and the update.zip file. I plugged the g-tab into the pc and switched it to usb mode. Then I moved the old recover folder and update.zip to a folder (cautious me) and put the new ones in the root. I disconnected the usb and started the g-tab in recovery mode (holding the power and volume+ key. It rebooted, applied the patch and I was done. That seems simple enough. It would seem that this would work for switching roms, applying patches and probably even upgrading the kernel (If I knew where it was and why I should do it). Am I missing something? Everything seems to work.
Sounds like you got the basics ok.
The real main reason to update the kernal as i see it is to add things like driver support for devices like gps and g3, so on, also minor fixs. If your not using your gtab for anything like this you maybe happy to stay stock. But if you like myself like to use your gtab to surf with g3 or as a sweet gps, then thats what the kernal updates allow. Im sure others can correct me if ive got anything wrong or add to what ive said.
You got the basic steps right, but installing ClockWorkMod Recovery has a lot of benefits.
First, built in backup and recovery will save your skin if the gTab get "cranky".
Second, installing ROMs and/or updates saves you a few steps. From "tar" files (TnT-lite), extract the update.zip file to a folder (I created a folder named "xda", just an example) and name it after the version of ROM/update.
CWM will flash "*.zip" file. This way you can keep multiple ROMs/updates on the card and switch between them.
CWM lets you clear cache, wipe Data partition, clear Dalvik-cache (use caution there), fix permissions and so much more! It is a great tool.
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
So now we peel back another layer
OK so now the question of multiple roms comes up. I am not clear about the role of the rom - can I switch roms and keep all of my apps and data intact? I'm thinking like changing style sheets on a web page - presentation is different but the underlying data is still the same? Is it that easy?
And... if I am doing that perhaps I need to "clear cache" or "wipe data partition" but although I like to investigate new things I'm not willing to just walk up and push the big red button without knowing what it is for. So why would I "clear" or "wipe" things?
I get the impression that I could switch between ROMs just like switching between browsers on a pc - today Chrome, tomorrow, Firefox and never Internet Exploder... Is that correct? It took me quite a while to get the market working and it still doesn't work optimally but I'd hate to undo all the work I've done getting the g-tab humming along by switching roms. Can I?
So - anyone care to expound on the structure and how it all hooks together? What parts can be swapped out and what parts form the foundation? I'd hate to brick the little guy in my ignorance.
One final note if you know and you answer - where did YOU learn about this. Is there a book somewhere to read?
Thanks again for sharing your knowledge.
The Need for A Wiki
I'm in the same boat as enigma. I'm not even sure what ROM is an acronym for, though I think it means operating system. A wiki would be a big help for many people. I bet people would be glad to contribute.
Well, I don't know about Android book, especially about "hacking android book" , but this (and others) forum has plenty of reading material and guides. Not to mention people (a lot more knowledgeable and experienced than me) who will offer advice and lend a hand. And Google search comes in handy too.
Switching ROMs is almost like switching the OS, or a flavor of. Very much like switching between Linux distributions; the base OS is the same, but the overlay changes the user experience. Some things do change deep down inside, that's why is advisable to clear data.
Android, like Linux which it is based on, uses separate partitions for different parts of the OS, like boot, recovery, data, cache and user data. Plenty of write ups and discussions on the web on that.
So when flashing a ROM, you'll rewrite boot and system. Your user apps and data/preferences pertaining to those apps are stored in data partition, and since you are changing the 'OS', the apps need to be recompiled for it. Backup apps, like Titanium Backup, come extremely handy here: backup and restore apps AND appdata with a few clicks.
Backups are stored on sdcard, which is a lot like Linux /home directory, and do not get wiped during flash. Also the CWM (sometimes called Nandroid) backups are also stored there. A backup-of-the-backup is always a good habit (copy of /sdcard to your PC for safekeep).
This is just a quick rundown, hopefully that answered some of the questions.
There is a world of information available out there in "ether-world", Google is your friend.
[EDIT]:
Some links:
http://android-dls.com/wiki/index.php?title=Main_Page
http://lifehacker.com/#!5596108/how-to-choose-the-right-android-rom-for-you
and of course:
http://forum.xda-developers.com/forumdisplay.php?f=841
(use the search on top of the screen)
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
TeamSpeed said:
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
Click to expand...
Click to collapse
Yes, your Sticky is as clear as Florida sky.
I just installed Thumb Keyboard on my gTab last night and I guess I got carried away getting used to it!
Yes, I have found some very good step by steps (reflashed to vegan after reading that one). Step by steps are great but I 'd like to understand why I'm doing it. The market fix...I can follow the steps and it works but why? I wish I had time to research all these things but there are so many forums,so many posts to read! The explanation that did surface in this thread was great though. Thanks. I'll keep asking questions. There are a lot of smart people out there!