Ahh I am finally unrooted and BACK TO STOCK

Well, the root thing was an interesting ride, but JF 1.5 was getting old- I assumed an move to Cyanogen would get my system flying and imroved, but man, I just didnt like that thing at ALL.

They messed with the browser, changed the call log all around- and it was always buggin out on me..

My wife's phone was running a 100% stock 1.6 and it was smooth.

So I decided that Android is far enough along for me at this point and I don't need to be ****ing around with all these ROMs, and would rather be running the most stable and smooth version available.

Thanks to ggrant3876 who flowed me this link:

http://androidandme.com/2009/10/beginners/guides/how-to-manually-install-the-official-t-mobile-android-1-6-on-your-g1/

I am now completely unrooted and on 1.6 stock android. Ah its nice to have some stability..

So long root- it was fun for awhile
 
Yep I'm glad to be stock.

At this point, being rooted doesn't have much to excite me..

I just want stuff to run smoooth


The only thing I really miss at this point is the "1X" zoom
Button in the browser that was in JF 1.5 THAT was a cool
Feature that they should really add to stock.

What sent me running from cyano was how they changed
The address bar in the browser and completly messed up
The multiple windows list.

Not to mention the wacky call log changes and all the lag..
 
Different strokes thats all, you got to play with the roms for a bit but it
wasn't for you. Bottom line is your happy now with your android .
 
you must be doing something wrong, because cyanogenmod for the g1 is much faster than stock for me. oh well, the main thing is that you are happy
 
I respect customizing with cooked ROMs and so on... BUT, I simply want something that would not mess with my warranty, phone as made by manufacturer and simple additions like extra apps and so on would do it for me... I guess not knowing how to flash Roms scares me the most
 
I'm not dogging on Cyano- in fact I greatly appreciate that there are guys like him doing the things they do.

I just felt that it was too much of a departure into other's personal preferences for how the browser/dialer/call log, etc worked for my taste. I couldnt turn off or tweak anything in the settings, so it was take it or leave it.

At that point the closest thing to what I was looking for was stock Donut.

I'd still like to have apps2sd, caches to sd and as little internal memory eaten up by stuff like amazon MP3 & ringtones (no reason those cant be on the sd card) as possible but oh well.

I figure going forward either my next phone will have a heck of alot more internal space (where's my next decent QWERTY phone to upgrade to Tmobile?)

or Android will start addressing those issues

either way I'm happy where I am right now, and it wasnt too hard to get back.

If you are on stock 1.6 and you arent salivating over some special rooted feature, then youre fine where you are, imo
 
Do Not exist any application to help to do this(apps2sd, caches to sd and as little internal memory eaten up by stuff like amazon MP3 & ringtones and no reason those cant be on the sd card) in a more or less way.
 
This is the main reason I haven't installed a custom ROM. Don't get me wrong, Cyanogen is a brilliant and very talented guy, but where's his Quality Assurance team? Where's his formal testing procedures? Who peer checks his code or ensures there's nothing dodgy in it?

My phone with Android 1.6 has never crashed or locked up since I bought it over a year ago, it's been reliable and does everything I want it to do. Maybe it would run faster or do more things if I installed a custom ROM, but on the other hand it might not.

Google also employ a bunch of very talented people. You have to ask why they didn't, and still haven't, included Apps2SD functionality or overclocking. I can answer both - the type of flash memory used in all SD cards has a finite number of times it can be written to. Apps write to their application space many times when they're executed, so if they're on your SD card this eats into that number of write cycles your SD card can take. Worse still if you move your cache to SD card, which can have thousands of writes every second. Just search the forums or Google for people complaining about their SD card suddenly stopping working - this is almost certainly why. Overclocking is just a simple fact that the tracks on the circuit boards that handle the power from the battery to the various components are of a given thickness, so can handle a given current before heating up. Fast speed = more current. Heating them up, at best, promotes premature oxidisation (corrosion) which vastly shortens the life of the phone, and at worst burns them out altogether. Again, a quick search will reveal a lot of people's phones suddenly switch off and never turn back on, but who knows why they died.

It scares me to think that these types of points aren't readily thought about - if it is just the case of modifying a text file to make your phone run 30% faster then why didn't Google do it in the first place? If it's just a case of changing a mount point to point to your SD card to install apps on SD, why didn't they do that either?

And of course, for most phones on most carriers, rooting voids your warranty so you can't return it if it does break. But then, I doubt they'd check.
 
Thanks extorian this post with this very important information I think is vital to any new user because everyone can jump and root their devices without knowing this can make the device not a usefull tool for daily basis like in my case I use my device for medical purpose I have graphic,charts,pdr,ect. to work with my patients everyday and because of this I need a device I can depend
 
Back
Top