Related
"RC33JF" vs. cupcake - does cupcake have multitouch built in?
I expect some are going to jump on me for asking a dumb question, but a search on this site, which I consider the finest knowledge base around on this topic, yielded mostly conversations around the fact that cupcake will support multitouch, but they don't mention if it is turned on out of the box. In other words, would we need Luke/JF's patch work as we did with RC30 for multitouch to work, or would it just work as it should.
With RC33 out and my confidence in JF that there will be a "RC33JF out within a week" and what appears to be a MUCH more usable cupcake image (as of 2/2, anyway), I am thinking hard about if I'd give up RC33 and Maps, Gmail, etc. and just use AndNav, K9, etc. and APK repositories to survive to get my A2DP bluetooth and full time virtual keyboard, and cupcake is looking more and more promising...
first off, multitouch only works in the browser. Im not sure if the current browser would work with the cupcake firmware. If it does then you could just push it to the phone using adb.
JF or LucidREM can one of you please please please make this image without the multi-touch hack in it. You don't know how much i would appreciate it and probably others. Its too weird to have it throughout the OS and there aren't any apps that can utilize it.
I have no use for the multi and don't like the quirky issues that come with it.
Again please please please and thank you! Your work IS appreciated greatly!
you are incorrect multi-touch effects apps other than the browser in 1.41
It may cause problems but it doesnt work properly. The app would have to be coded to work with the hack. I dont know of any apps that have been coded to work with this hack.
It's off by default. Just go into your browser settings and uncheck what you checked in the first place.
I don't know much about it (multi-touch) but if it's built into the OS and (allegedly?) leads to some quirks here and there (does it?) I don't understand how you can turn it off from the browser...
I'm sure there are a lot of us who don't care about multi-touch at this point, so I would agree with the OP that it would be nice to have the option of a modified RC33 *without* multi-touch.
I would like to add my request as well.
Its off by default in the browser but the kernel is still hacked to sense multi-touch which causes issues with certain apps. This is because the hack uses an existing field to sense the 2nd finger. So apps that actually use that field for legitimate purposes don't work correctly.
Pls add me to the requests for a no-multi-touch version.
It is my understanding that you can turn auto rotate on and off in the browser, but not multi-touch.
there are the highest chances that multi-touch wont be included in cupcake..that is in the original unmodified update..
kernel is still hacked to sense multi-touch which causes issues with certain apps
Click to expand...
Click to collapse
Which apps are having issues? Somebody mentioned Steamy Windows in another thread... what other apps are having issues. I like the auto-rotate/multi-touch functionality in that order.
aukicadeso said:
Which apps are having issues? Somebody mentioned Steamy Windows in another thread... what other apps are having issues. I like the auto-rotate/multi-touch functionality in that order.
Click to expand...
Click to collapse
I was having issues where my home screen would skip back and forth. I also had issues clicking the proper menu options/icons.
So yeah count my vote in too.
justanothercrowd said:
JF or LucidREM can one of you please please please make this image without the multi-touch hack in it. You don't know how much i would appreciate it and probably others. Its too weird to have it throughout the OS and there aren't any apps that can utilize it.
I have no use for the multi and don't like the quirky issues that come with it.
Again please please please and thank you! Your work IS appreciated greatly!
Click to expand...
Click to collapse
OMG, how many threads are you going to post this in? I've counted about 4. If your steamy windows app doesn't work on JF v1.41, go back to non-rooted. I took a look at your past 15 posts, and it all relates to the multi-touch. Version 1.31 didn't have it, you could use that...
/rant
Honestly, beggars can't be choosers.
If JF chooses to not implement this, I think it'd be a step back. You are all welcome to go back to 1.31 or even use the nonrooted version... or better yet, come out with your own version of root.
But, ultimately it's up to JF, and I really hope he doesn't waste his time making two separate versions of 1.33. Ofc, if you really want him to listen to you, don't be a beggar, and be a supporter.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=1014600
If JF doesn't do it, someone else probably will... which is perfectly fine. Nobody is knocking JF if he won't do this.
I think people are just asking (kindly, I don't see anyone being a jerk about it honestly) for a "vanilla" RC33... As in, exactly as it came from Google except WITH root access added back in. No extra stuff, no recompiled kernel, no extra modules, nothing but root access added back in.
All of my posts are about it because it is the biggest issue with people in the 1.41 build.
The stock RAW image viewer does not work properly either...or cracked screen app....just becasue the apps that take advantage of the second field arent great right now doesnt mean that this isn't an issue. It could end up being a big issue since most dev's don't develop for hacked ROMS.
And for your info I have been running 1.31 for the past few days. I just don't want to see this hack pigeon hole users into not being able to use certain apps. I would like to be able to take advantage of future releases without having multi-touch.
Currently it is only a benefit in the browser and the stock zoom works much smoother, and in the rest of the OS it is a bother.
I will continue to voice my concern and it appears that quite a few others have the same concern.
justanothercrowd said:
All of my posts are about it because it is the biggest issue with people in the 1.41 build.
The stock RAW image viewer does not work properly either...or cracked screen app....just becasue the apps that take advantage of the second field arent great right now doesnt mean that this isn't an issue. It could end up being a big issue since most dev's don't develop for hacked ROMS.
And for your info I have been running 1.31 for the past few days. I just don't want to see this hack pigeon hole users into not being able to use certain apps. I would like to be able to take advantage of future releases without having multi-touch.
Currently it is only a benefit in the browser and the stock zoom works much smoother, and in the rest of the OS it is a bother.
I will continue to voice my concern and it appears that quite a few others have the same concern.
Click to expand...
Click to collapse
Feel free to ask all you want. I think it might fall on deaf ears. The point I was trying to make, is that it's not necessary to post in 4-5 different threads. I think one thread would be sufficient enough...
I agree with justanothercrowd. I'm all for the multi-touch hack, but the fact that its using an existing documented field is an issue.
I believe if you search the threads JF has already answered this question or it has been at least brought up. The only problem that was really brought to light was the steamy app. Really I think this would be a huge hassle for JF who works for free to have to update two versions every time an update is to come out maybe a simple setting to turn it off would be easier and more likely.
a setting would be great. and im more than willing to contribute $$$ for the extra time spent. i would recompile my own but im not that savvy with the android platform yet.
any feedback jf?
Hello,
I'm not a developer, so not really looking to get full root access, but I'd like to get JF for the auto-rotate, tether, and multi-touch.
My confusion is, do I get the ADP 1.1, the RC33, or both? What is the ADP 1.1 for?
My phone is for the US. It's currently on regular RC33 and the firmware is 1.1.
cigar3tte said:
Hello,
I'm not a developer, so not really looking to get full root access, but I'd like to get JF for the auto-rotate, tether, and multi-touch.
My confusion is, do I get the ADP 1.1, the RC33, or both? What is the ADP 1.1 for?
My phone is for the US. It's currently on regular RC33 and the firmware is 1.1.
Click to expand...
Click to collapse
Hello,
I think you better goggle more better or study more cause you ask if you could use RC33 and ADP or both?
If you going to ask a question like that, I think you should sell me your g1 or don't mod it!
There should be a FAQ sticky post explaining all the basics, there's too much technical info and i know beginners can have it difficult to solve very simple but important questions...
jf adp 1.1 is pretty much the same as jf rc33 but without MyFaves, without IM (only access to google's IM) and no Amazon Mp3. So, adp1.1 get a little more space somewhere..
So, choose one, read the forum and install it. I heard somewhere ADP users CAN NOT download protected / paid apps? i never could because i am from spain and never could.. so be carefull with that.
And you will have root too with adp or rc33, but apps will require your permission if they want to use root so you are safe. eg: tether will request root to work.
I recommend you to install lucidrem's firmware + apps on sd card, its really great to have 400 MB free for apps and never see that aannoying message telling you "low space".
And install the Radio update too. It improves your battery duration.
greetings
Meh, not a lot of people want to mod their phone for root access directly, but for something that only requires root access... Like WiFi tethering, in this case...
cigar3tte, I'd strongly suggest you do a bit more research on-line, as you can mess up your phone (though it'll be repairable most likely) if you don't do it properly, but I'll give you a push in the right direction. You want the RC33 version of JF's builds.
Stay away from the ADP builds unless you have a specific reason to use them, and know what they are, what they do, and why you need them.
There's a few guides on how to root your phone, make sure you follow them all (you'll need to downgrade to RC 29, etc). Good luck.
unrafa said:
There should be a FAQ sticky post explaining all the basics, there's too much technical info and i know beginners can have it difficult to solve very simple but important questions...
jf adp 1.1 is pretty much the same as jf rc43 but without MyFaves, without IM (only access to google's IM) and no Amazon Mp3. So, adp1.1 get a little more space somewhere..
So, choose one, read the forum and install it. I heard somewhere ADP users CAN NOT download protected / paid apps? i never could because i am from spain and never could.. so be carefull with that.
greetings
Click to expand...
Click to collapse
Not entirely, but mostly accurate... ADP1.1 JF builds do include the Amazon marketplace (I know because I remove it every time I reflash, stupid thing). Also, the ADP1.1 partitions are slightly different, so that more space thing isn't necessarily true.
What you said about the protected applications in the marketplace is spot on. Not all paid apps are protected, though, and we can buy paid, unprotected apps just fine. On the flip side, we can't even download free, protected apps. But either way, there's a LOT of marketplace apps, both free and paid, that are listed as protected that ADP image users can not see.
Thanks for all the replies (yes, even the first one).
I went with RC33, and successfully flashed JF 1.42.
Auto-rotate and multi-touch are working.
Hello Guys !!!!
I have The Magic Rom v 5.0.2H Installed Currently On my ADP1...
I AM IN INDIA
So As we know ADP1 Cannot See Paid Apps....
I Have The Quick Office apk installed Dont know which Version may be the one from Sapphire System Folder by Xmoo or From The Custom Build From Rild or someone with similar User Name Here (There Is A build on XDA)
Today while browsing on my ADP1, Got a Popup Saying Quick Office Update Is Available,
So I clicked on that Notification,
It Took Me to The Android Market,...To the Quick Office Paid App Costing $19~
Also Shows The Buy Option !!!
But When I checked Android Market Again, It Dint Show Any Paid App.... But opening Quick Office Sometime Shows Its App Download Window On The Market...
So I Think Even ADP1 OR Rooted Phones Can See Paid APP By Some Hack....
Please Post Your Ideas...
sangeet.003 said:
Hello Guys !!!!
I have The Magic Rom v 5.0.2H Installed Currently On my ADP1...
I AM IN INDIA
So As we know ADP1 Cannot See Paid Apps....
I Have The Quick Office apk installed Dont know which Version may be the one from Sapphire System Folder by Xmoo or From The Custom Build From Rild or someone with similar User Name Here (There Is A build on XDA)
Today while browsing on my ADP1, Got a Popup Saying Quick Office Update Is Available,
So I clicked on that Notification,
It Took Me to The Android Market,...To the Quick Office Paid App Costing $19~
Also Shows The Buy Option !!!
But When I checked Android Market Again, It Dint Show Any Paid App.... But opening Quick Office Sometime Shows Its App Download Window On The Market...
So I Think Even ADP1 OR Rooted Phones Can See Paid APP By Some Hack....
Please Post Your Ideas...
Click to expand...
Click to collapse
Ok, so you have the ADP1 phone, but are running an RC (read - NON-ADP) firmware. And what is shocking is that you think you still have an ADP1 phone. Sure the hardware is the same and you have that fancy back cover, but if the software says RC - that is the only thing the market can see. So that is how your phone is identified as an ADP or "Normal" phone.
daveid said:
Ok, so you have the ADP1 phone, but are running an RC (read - NON-ADP) firmware. And what is shocking is that you think you still have an ADP1 phone. Sure the hardware is the same and you have that fancy back cover, but if the software says RC - that is the only thing the market can see. So that is how your phone is identified as an ADP or "Normal" phone.
Click to expand...
Click to collapse
His signature says he has this phone:
Phone : ADP1
Bootloader : Hard SPL
ROM : JF 1.43 ADP 1.1h
Yes kathi but what he's saying is, the OP is not running ADP firmware so the market has no idea what the back cover looks like or how much he paid for his phone.
As far as the market is concerned, he's running a standard T-Mobile G1 with RC33.
Kinda like if i boot my mac into Vista... I'm not going to get apple updates, i'm going to get windows updates... MS doesn't know (or care at least) that i'm on mac hardware. They just know I'm running windows.
Sorry Man You R Wrong,
If It was so that changing the firmware, would show paid apps,
Even Going to JF RC versions frim ADP versions would fetch me 1 or 2 paid apps...
Changing the firmware dosen't change the whole phone info...
The information Regarding Paid Apps Is stored on a lower level which dosen't change by a change in firmware...
What I Think Is May Be The Change in Radio Can Do This because The Radio Partition is not accessible via the UI
OR
Also The Bootloader Changes May Be Responsible This,
As Magic Rom Has An Option To Change The Radio & Bootloader ... These Require Recovery Mode to Be Flashed & Which Are Not Provided In The Source...
Haykuro,
First Off All, Thanks For Magic ROM,
Need To Ask U Some Questions:
1. Where Did The Radio & Bootloader Come From & Did You Did Any Changes To It ?
(May Be It Was Updated OTA I Know Bootloader Comes OTA)
Ok, well I just looked closer and I see that you are still running an ADP firmware, it's just a JF build.
I assure you though, when I put ADP firmware on my phone, I can't get protected apps.
When I put an RC firmware, I can.
The market blocks apps based soley on your firmware, not the bootloader or radio.
ADP = no protected apps
RC = no restrictions
As far as how you were able to see Quick Office, I have no idea. So on that note, I digress.
skri11a said:
Ok, well I just looked closer and I see that you are still running an ADP firmware, it's just a JF build.
I assure you though, when I put ADP firmware on my phone, I can't get protected apps.
When I put an RC firmware, I can.
The market blocks apps based soley on your firmware, not the bootloader or radio.
ADP = no protected apps
RC = no restrictions
As far as how you were able to see Quick Office, I have no idea. So on that note, I digress.
Click to expand...
Click to collapse
No Its Not ADP Firmware The Firmware Itself Means The Build
i.e. Firmware Means:
1.0, 1.1, 1.5,...
& Build Means:
ADP1, ADP1.1, JF ADP1, JF ADP1.1, RC, JF RC, haykuro 5.0.2H, haykuro 5.0.1G, ...
So Firmware & Build Dosent Matter...
Fair enough, you've got me on semantics.
Up until the 1.5 firmwares (Haykuro's builds) started hitting up the market, the standard restrictions were as I stated above.
At this time, as far as I know, nobody knows what's going on with the Market. Since Google released the 1.5 SDK, maybe they're now making changes to the market to either purposely block 1.5 firmware until they're ready or maybe the market is truly being upgraded to only supply the correct version of apps for the correct firmware.
Either way, I stand by my original comment that up until now, ADP builds were not able to see protected apps, while all RC derivatives were. Now that RC33 includes both 1.1 and 1.5 firmware, I guess all bets are off until somebody can verify what's actually going on.
skri11a said:
Yes kathi but what he's saying is, the OP is not running ADP firmware so the market has no idea what the back cover looks like or how much he paid for his phone.
As far as the market is concerned, he's running a standard T-Mobile G1 with RC33.
Kinda like if i boot my mac into Vista... I'm not going to get apple updates, i'm going to get windows updates... MS doesn't know (or care at least) that i'm on mac hardware. They just know I'm running windows.
Click to expand...
Click to collapse
Oh, you are right. I looked back and saw his signature. I should have read his post over again and seen that he was using Haykuro's build.
I'm slapping myself in the side of my head!
edit: I went from the same JF version Sangreet had to the same Haykuro version he has now, and can also see protected apps. It's because Haykuro added the code to make the market think we are on RC33. As of last night, the G builds couldn't download on the market, but the H builds could. (I just got on here a few minutes ago, so I don't know if this has changed).
kathi17 said:
Oh, you are right. I looked back and saw his signature. I should have read his post over again and seen that he was using Haykuro's build.
I'm slapping myself in the side of my head!
Click to expand...
Click to collapse
Yeah, I'm having a hard time reading this morning too.
I saw "His Stuffs" and assumed the theme he created was the build he was running. I didn't see Haykuro's build either.
I'll just back away slowly and go back to nursing my hangover.
I still stand behind my basic point though
Sorry I updated my Sig now,
Skri11a, you got me what I was saying, great thinking may b what u said
But what I think is if its so, all paid apps would be visable,
Lets see what surprise Google has for us.
sangeet.003 said:
Sorry I updated my Sig now,
Skri11a, you got me what I was saying, great thinking may b what u said
But what I think is if its so, all paid apps would be visable,
Lets see what surprise Google has for us.
Click to expand...
Click to collapse
i already read somewhere that they lifted the ban on paid apps partially .. something about paid apps that don't encrypt or something or other .. i don't recall the exact wording the press used but some apps have been made visible to ADP for at least a month or so
Hope that's true, and ado. Users see paid apps atleast on official ROMs
Okay, so here is a small application I designed out of fun. Just install it on your desktop and run it, and it will give you the option to remove some bloatware from your phone. This is not 100% full proof. There are bound to be some errors with version numbers and all. Also, this will only work with the new gingerbread 4.22 base, because of the change in names of the stock apps.
Remember, your phone will need to be rooted, and connected via adb for this to work.
This is the first time I'm developing something so don't attack me if it doesn't work lol.
As with anything, I'm not responsible to anything that happens to your phone. ( Though the worst that probably can happen is that the application doesn't get removed.
Attached is the application in a zip folder.
Windows Only
sorry Linux users, maybe next time.
If you have any problems installing, go and download Microsoft Netframework.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e5ad0459-cbcc-4b4f-97b6-fb17111cf544
Cool ill try this out and report back. Nice work
Okay cool, thanks
hopefully it's at least %100 fool proof.
Can you define what you call "bloatware" as well? I consider all Sense ROMs to be bloatware, will this app remove it and flash an AOSP ROM? -- point being is everyone defines bloatware differently. Maybe in future versions you can have checkboxes on what the app removes allowing the user to have choice.
Thanks.
Lol, yeah hopefully.
I was defining bloatware as applications that are loaded onto the phone by the carrier. So basically, almost anything Sprint related.
maybe give the users options on what they want to remove?
yeah I have included a few apps for the user's choice to remove, but I understand what you're saying. I'll definitely expand on that.
Good luck with this. I'm sure there is a need for this software, so I hope you keep it up and mature it into something useful to the XDA hordes.
Yes, I definitely mean “wonderful” and “experts.” It is astonishing how much time, effort, and expertise the people who write the ROMs, etc., do for others, just to help us enjoy our cellphones. So, it is with no disrespect that I offer these comments on the instructions the experts give to us noobies to help us try to make our phones work better when they post “complete” instructions about how go to about this.
#1 – Odin.
There’s lots of advice to get Odin, but there are lots of Odin versions out there. Usually (generally in the computer world) what works when there’s a recommendation to get a program is to find the latest version. Even if a forum posting has a link to get a program, we figure that was the latest version available when the post was made and it still makes sense to get the currently latest version. That doesn’t work here. The latest Odin version I found was Odin 4.28. 4.28 totally fails to recognize my Samsung Droid Charge. But, if I use the ones referenced in the postings here (e.g. Odin3 v1.85) it recognizes my phone immediately. I understand the feeling that if we’re noobies we should just follow the directions exactly as written, but a little footnote about how this is different than everything else with computers would help.
I’m sure it isn’t true, but Odin seems to come from a mystical cloud location without any existence in our 3 dimensional universe. So, there seems to be no home website to explain that the latest version shouldn’t necessarily be used by everybody. And, there seems to be nobody on the forum who takes credit for upgrading Odin. Very mysterious.
Also – there’s at least three ways I’ve seen adamantly expressed as the proper way to connect a phone to Odin. #1 – simply attach the phone to the computer in the usual “download” mode, and Odin will find it.
#2 – Take out the phone battery for 5 seconds, replace it, then boot into recovery mode by holding down the up-volume, power, and home keys until “Samsung” flashes twice.
#3 – Take out the battery and don’t return it. Plug the phone into the computer, booting into recovery mode like #2.
As far as I can tell, #2 and #3 were needed for prior versions of Odin. Still, we noobies do Google this process, and it’s scary getting these conflicting directions about how to proceed. So, since you are obviously trying to make things less scary and confusing for us, you could mention this too.
Part of the problem is that there are various “Here’s how to replace your stock ROM with a better one” postings. Maybe each of them works perfectly, and there are many paths to enlightenment. Still, it’s worrisome for a noobie to try to figure out which of these paths to bet our phone on. (Of course, it’s also difficult for people trying to actually achieve spiritual enlightenment to decide on a path, so maybe this confusion is just an inevitable part of human experience.)
(cont. below)
#2 – CWM – Clock Work Mod.
I’m still confused about the need and timing of this one. Some sources say it’s entirely optional, just allowing other cool stuff done later. Others seem to say it’s important to install (flash through Odin) this before installing the new ROM. And, then there seem to be some ROMs that Odin can flash that do it all at the same time. And, then, there’s the issue of what order things are to be done in. If we just use Odin to flash a new Gingerbread ROM, can we, or should we, use Odin to flash in CWM?
As a noobie, I’m inclined to the “the less I mess with, the less chance I have of screwing everything up.” So, I think I’d like to skip the CWM while installing my new ROM, and wait to use CWM until I find some additional cool feature I can’t add without it.
#3 – ROM’s.
Where’s Consumer Reports when we need them? There are apparently various ROM’s we could use to improve our phones (e.g. Samsung Droid Charge). They are listed with somewhat cryptic explanations. Those explanations are probably perfectly explanatory for experts, but as a Noobie I don’t get a clear sense of direction from reading them. For example, Android 2.2 ROM’s (Froyo) are still listed, along with 2.3 (Gingerbread). Why would anybody want 2.2 if 2.3 is available? I assume there’s some reason I should be considering, but have no idea what it is. Among the 2.3’s, there’s also the “bloated” vs. “debloated” versions. Many of the unremovable (until rooted) stock apps seem to be both useless and resource drainers. But, I don’t know if I’m ready to give up all of them. And, the “debloated” versions are written by programmers, not people who want to devote their lives to writing up detailed commentaries about what is, and is not, debloated and why. Is there any reason not to just keep all the stock apps, and freeze or uninstall them with Titanium Backup later, as I identify the ones I do not want?
I feel anxious when I read somebody’s post about their newly released ROM, with lots of compliments, then comments that some feature now isn’t working. It’s hard enough to get answers about how to deal with the stock ROM.
I’m also confused about the difference between the “kernal” and the “ROM”. My impression is that “kernal” is which version of Android we use. “ROM” is broader, including extra’s like CDM and CDW, and Voodoo, etc. Or, not?
Part of the problem, obviously, is that the ROM writers have to do a different version for every [email protected]#$%^&*! phone that is made. Apparently even with the Samsung Galaxy family, there are enough differences that the ROM’s are customized for each one. (My prior phone was a Vibrant.) I am grateful that we have choices, and that these ROM’s are available, at all, but it would help to get a little more commentary (i.e. recommendations) about which ones are best for those of us just wanting a better ROM.
#4 – Voodoo. This is like the other issues. It seems like a great thing, to make the file system more efficient and do things like improve the sound system. But, it’s also confusing about when/if to install it in relation to the general ROM update.
So, maybe one of the wonderful experts will clarify these things here, or tweak their general instructions, for the benefit of noobies. Regardless, I again express my appreciation for all they’ve done for us.
There's a whole lot of "it depends" in this.
#1 - Odin may be up to 4.28, but Odin3 is newer than Odin. That's pretty self explanatory on its own.
#2 - You need CWM. Period. But, if you are flashing a full Odin ROM, it already comes with it, so you won't have to go into it unless you want to flash a theme or a new kernel. If you are installing a CWM ROM image, you need to flash CWM first.
#3 - Froyo (2.2) is still the only offical release for this phone. Gingerbread (2.3) is coming, but it's still in beta, and not officially released. The only GB releases we have are leaked and are not official final builds, therefore, they are not guaranteed to be of the quality or stability of Froyo, and, more importantly for us, there is no source available for the GB releases yet, so we don't have a lot of the cool tweaks available. So, it really does depend on what you are after.
#4 - All the current ROMs pretty much support it out of the box. If you are going with a stock ROM instead, you need a Voodoo enabled kernel to activate it. If you're ever in doubt of whether you have it and if it's enabled, install Voodoo Control and look at the lagfix section of the app.
I built a web page that has compiled all of the software you need to root, kernel update, ROM, and recover your Droid Charge with direct links to all of the software in one place.
http://www.toms-world.org/android
Plus it comes with very detailed instructions on how to do any one the activities mentioned above.
For those experts who do know how to do all of this, I'd like to see some collaboration and opinions on my directions. I'm only one person so I can't think of everything that could be added as far as a tutorial.
My idea is that a lot of us that know how to do this stuff should start a place where people can find the information they need for the Droid Charge all in one place without having to go from thread to thread, page to page, etc. Having it all in one place would benefit the Droid Charge community greatly.
Thanks for the replies.
Also, answering my own questions,
Not only is CWM necessary, but the remove battery 1st instructions, at:
http://forum.xda-developers.com/showpost.php?p=14692818&postcount=1
are correct. The other instructions I found that didn't include this stop didn't work -- Odin just sat there.
Also, at about page 11 of that xda thread, it says (correctly) that after ODIN says it's done, it's OK to unplug your phone, despite the large, brightly colored screen that says "Downloading... Do not turn off Target!!!"
Also, the kernal is different than the OS. So, first we find and install a rooted kernal (I guess this is like the most fundamental part of the phone's operating system), then pick a ROM (i.e. version of Android) to install.
Yes, now that you pointed it out, I agree it should have been obvious that ODIN3 is a later family version of ODIN, so no matter how high the version of ODIN we find, it's not going to be up the ODIN3 level. ...sigh
In the case of loading GummyCharged, you don't need to pick a kernel. The GummyCharged package contains an already rooted kernel (iMoseyOn's Lean Droid Charge Kernel) so basically if you load GummyCharged you have a kernel flashed along side it.
The only time you have to flash a new kernel is if you want to run a different kernel than the one contained in your ROM. Or if you want to update the kernel to a newer version of the kernel.
The kernel is the heart and soul of an operating system. It does all of the work in coordinating memory and process allocation. Think of it as a traffic cop.
trparky said:
In the case of loading GummyCharged, you don't need to pick a kernel...
Click to expand...
Click to collapse
Thanks. Your description of the kernel is much better than mine.
Another bit of noobie confusion:
The GummyCharged thread at
http://forum.xda-developers.com/showthread.php?t=1163123
says to install through CWM, after rooting. So, I already installed a new kernal, so I could have root.
As I understand better, now, I hope -- even with GummyCharged -- I had two choices, as there are two GummyCharged versions available. One is the two-step process (new kernal, then new OS). The other is to do both at the same time, through ODIN, which would have been easier.
I did install a new kernal, through CDW, seeing that path more clearly.
http://forum.xda-developers.com/showthread.php?t=1104634
Just a note that when my phone rebooted, Titanium Backup said I did not have root privileges. On a hunch, I just rebooted again, and that solved the problem. TB is happy, and so am I.
Then install a new OS through CWM.
Another thread that might have some useful information for you can be found here -> http://rootzwiki.com/showthread.php?4643-HOW-TO-quot-Clean-quot-install-GummyCharged-FE-2.0. Theres a lot there (maybe too much?) but if nothing else there are a number of useful links. I hope it helps!
Off topic: trparky I tried to send you a pm yesterday but my computer was acting up - not sure if you got it or not.
Thanks for all the help. Everything seems to be fine. This is just sort of a summary & wind-up post of another noobie's experience and successful quest for cellphone happiness.
First, there seem to be three ways to do scary things to the e-guts of my cellphone.
#1 -- Odin3 (a.k.a. Odin, but Odin3 v.x is the one that works for Samsung/Verizon Droid Charge [SDC]). Odin3 runs on the computer, with the cellphone properly tethered to the computer, and can insert stuff, like CWM. So, mostly the first step is to use Odin3 to insert CWM (superseding the stock recovery program). From some post it seemed it's possible to skip this step and do everything from Odin3, but that post also said that approach wasn't for noobies, even though it seemed easier to me. Odin3 is an elegant program, but you have to find somebody's Betty Crocker instructions for how to use it.
#2 -- Use the ordinary SDC file tethering to put .zip files onto the SDCard, because CWM uses those to install things like kernels and OS's (versions of Android). Sometimes the kernel and OS come bundled. Sometimes not. I ended up flashing a kernel first, then an OS with a bundled kernel, and everything seems fine.
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
After I had my new root kernel, I used Titanium backup to freeze the bloatware. At that point I sort of chickened/burned out because there were too many choices of which version of Android to flash. I decided I didn't really need any of them, since my phone would be efficient enough without the bloatware running to give me everything I needed. What originally got me to start flashing my Android phone was when I would (repeatedly) receive calls on my old Samsung Vibrant, but the phone was so busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. With a more advanced phone (my new SDC), and frozen bloatware, I was confident I wouldn't have that problem, so just stopped there ... ... ... until I was horrified to receive another call which my SDC told me about but was too busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. OMG, it's happening again! At that point the choice of which version of Android to use because less important, because I was sure that nobody's custom Android would let that happen. So, I went with the GummyCharged Froyo [GummyChargedFE_2.0.zip]. At this point, I'd worked with CWM enough that it was all easy. Downloaded the file, copied it to my SDCard, booted to recovery, erased files & Dalvik cache, flashed the GummyCharged, and restarted. Lovely.
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before. It's kind of a hassle to have to re-do all that manually, so special chops/thanks to the GummyCharged team for that feature. My phone works fine. I've tried, and happily failed, to make it too busy to let me answer a call.
What's left? I have to make donations to the Gummycharged people, whose software I now use, and the person who tweaked CWM that I use. It feels like I should make a donation to the Odin3 trolls, but haven't seem a request for that, nor have any who they are or how to do that.
I'll also be keeping my eye on the developing Gingerbread kernels, occasionally, until it looks like those are so mature that there's no reason to not confidently install & flash (through Odin or CWM, both of which I not feel fairly comfortable with) the upgrade.
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Thanks, again, to the wonderful experts who've helped me and so many others through this.
angelsix said:
...
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
Click to expand...
Click to collapse
I believe the program is called Heimdall - this is more often associated with Mac users, as ODIN is a Windows program.
angelsix said:
...
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before.
Click to expand...
Click to collapse
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
angelsix said:
...
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Click to expand...
Click to collapse
You can delete the file, but this is essentially the installer file - if you ever have need to re-install it later on, you will need that (or a more up-to-date one if such a thing exists) file again. I tend to be an electronic pack rat myself, but you can delete the file from your SD card without any immediate adverse effects. If I remember right, the "update.zip" of old was associated with some earlier variants of CWM - without it you would not be able to get to the "custom" recovery (i.e. CWM) to flash things. Seems like such things are no longer necessary anymore, at least not with the recent versions.
dwitherell said:
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
Click to expand...
Click to collapse
That is correct, and it's something that I strongly dislike, as I have installed plenty of things from the Market that I have since uninstalled and no desire to restore. If you skip account setup when you are first setting up the phone, and then manually go into Settings->Accounts & Sync, it will skip this, which is yet another reason to like aftermarket roms, as the stock roms will not allow you to get to the launcher until you set up a Google Account.