Tired of GB Rom problems - get me back to stock rooted please
So, I ran Project Elite a while back, got tired of that, switched to Cyanogen for a long time.....but the latest versions have been incredibly buggy on my Droid - especially the newest 7.1. I tried Pete Alfonso's 16&17 but both had tons of problems. I just can't take all the problems with trying to run Gingerbread on the Droid. I just want to go back to stock Froyo until the Galaxy Nexus comes out.
So, there are a number of ways to unroot and go back to stock, but all I want to do is run the latest Froyo stock ROM and keep root. Can someone point me to the latest stock ROM and kernel?
So, I ran Project Elite a while back, got tired of that, switched to Cyanogen for a long time.....but the latest versions have been incredibly buggy on my Droid - especially the newest 7.1. I tried Pete Alfonso's 16&17 but both had tons of problems. I just can't take all the problems with trying to run Gingerbread on the Droid. I just want to go back to stock Froyo until the Galaxy Nexus comes out.
So, there are a number of ways to unroot and go back to stock, but all I want to do is run the latest Froyo stock ROM and keep root. Can someone point me to the latest stock ROM and kernel?
Hah, I'm in the exact same situation as OP. I've been about to throw my phone against the wall with any GB ROM I put on it. I don't see how anyone gets these things stable and I've tried every kernel/clock speed and memory tweak available. I still get constant lag, FCs and reboots. I really think my Droid ran best when it had 2.1 on it.
I've been looking for the stock ROM to put back on it, for some reason ROM manager doesn't have anything under "stock ROMs" for me and hasn't for the past month or two. That app seems to have been a waste of money too since whoever maintains it doesn't keep anything besides CM ROMs updated in it. SS 5.5 has been out for a couple months at least and it's still only showing SS 5.4. Anyways, thanks, Kratos. I'm going to do that. I can't wait for the Galaxy Nexus to launch. It's going to be a night/day difference from the Droid to that (but I guess any new phone now would be too, heh).
Why is the difference between phones so drastic? I took my OG out of a drawer where it sat for 6 months, booted up UD 3.1.1 (gingerbread based) and it's running snappier than my Tbolt and xperia play did..........
Why is the difference between phones so drastic? I took my OG out of a drawer where it sat for 6 months, booted up UD 3.1.1 (gingerbread based) and it's running snappier than my Tbolt and xperia play did..........
Keep using it for a week or so. After a reboot, the phone is usually nice and fast for about a day or so. Then it bogs down as the cache is filled up and you start running out of resources.
Keep using it for a week or so. After a reboot, the phone is usually nice and fast for about a day or so. Then it bogs down as the cache is filled up and you start running out of resources.
Well I had been using this phone as my daily driver with this setup for well over a month before I dropped it for my Tbolt. Kinda weird, all 3 of my different droids have worked beautifully on UD roms
I thought I was the only one. I never used a custom rom before a few days ago. I tried GPA17 and it was okay for a day or two, then wifi got flakey and the camera crashes on the first pic every time. The browser seems a lot faster, though and I don't have a reboot problem. Still, I'm going back.
It's not just phones - you also have 100K apps from the Market to pick from - you can only give a true comparison of the same ROM when different users install the exact same apps and use the phone in the exact same manner.
Those two variables right there account for the difference in the performance being experienced when folks run GB ROMs on the DROID.
Well I just switched back to stock rooted FRG83G w/ a LV 1.1 GHz kernel and I honestly don't know how I thought any GB ROM was better than this. My phone is totally usable again, blazing fast (with the exception of launcher redraws that have plagued this phone since 2.1+) and RELIABLE. Also, my camera is actually usable again . Running any 2.3 ROM made my navigation totally unusable (rebooted consistantly within mins of navigating), camera unusable (would always lock up after a pic was taken and video had horrible video skipping which cause audio to lose sync) and running any background tasks were impossible (any audio service would get killed if I started navigating while playing something).
Turning back to stock has alleviated all of the above from what I've tested today. The only thing I don't like is the stock theme, but I'll gladly live with it if it means my phone is completely usable. I only need my Droid to last another few weeks until the Nexus launches. But has there ever been a reliable fix to the launcher re-draws? I've got 70 MBs free of internal storage and deleted the stock launcher. I'm using LauncherPro and have tried every memory configuration in the preferences; locking it in memory just gives makes it slower and gives FCs, it seems to run better unchecked, but it's still annoying. I'm about to try the local.prop fix again, but I don't remember that completely working when I tried it last.
Last edited by PhilosoRaptor; October 31st, 2011 at 10:07 PM.
Usability is in the hands of the holder. Some people have hundreds of apps on their phones, especially lots of apps that run services in the background for whatever reason - and thus they are forced to shy away from GB based ROMs for this phone. Others have maybe a few apps here and there and primarily use built in, native system apps for all they need to do in a day's work.
The only way you can make a value judgment on what others have said is if you use the phone exactly the same way they do, with the same apps, same customizations, etc. And let's face it - that's only going to happen if you're either joined at the hip or else constantly in communication with each other performing a true objective test.
Usability is by nature a very subjective opinion with some objectivity built into it - a phone that does not power on is obviously not very usable for most of the world, whereas a phone that does everything that everyone can ever imagine would pretty much be the ultimate usable phone. Therefore, you have to understand what they mean regarding usability, and ultimately take what everyone here (and on other sites) says with a grain (or three) of salt.
it's why we use the acronym YMMV (Your Mileage may Vary) a lot because, your mileage really may vary, from one extreme to another.
Usability is in the hands of the holder. Some people have hundreds of apps on their phones, especially lots of apps that run services in the background for whatever reason - and thus they are forced to shy away from GB based ROMs for this phone. Others have maybe a few apps here and there and primarily use built in, native system apps for all they need to do in a day's work.
The only way you can make a value judgment on what others have said is if you use the phone exactly the same way they do, with the same apps, same customizations, etc. And let's face it - that's only going to happen if you're either joined at the hip or else constantly in communication with each other performing a true objective test.
Usability is by nature a very subjective opinion with some objectivity built into it - a phone that does not power on is obviously not very usable for most of the world, whereas a phone that does everything that everyone can ever imagine would pretty much be the ultimate usable phone. Therefore, you have to understand what they mean regarding usability, and ultimately take what everyone here (and on other sites) says with a grain (or three) of salt.
it's why we use the acronym YMMV (Your Mileage may Vary) a lot because, your mileage really may vary, from one extreme to another.
I'm in total agreeance. Too many times have I used one ROM or another based on a few peoples testament in their respective threads only to find out that my experience isn't anything like what they're describing as far as usability and speed. A lot of times this gets blamed on user error, but I guarantee you that I followed every guideline to the ROM installations (most of the time I would prefer to wipe everything just to be safe) and still had many issues. But from what I've seen so far, I don't think there's any GB ROMS that run as stable as the stock 2.2 or ROMs based off of it. There's a reason Moto didn't update the Droid to it and it's obvious when you run anything past 2.2 on it. I think for the majority of users, it's not worth the time of constantly tweaking and customizing every aspect of the phone just to make it work the way it should in the first place. It's fun to tinker with for a while, but when it interferes with your productivity and the core features of the phone (I would occasionally not be able to answer/make calls because the phone was so unresponsive), it's time to go back.
It's crappy that Moto didn't add another 256 MBs (to make 512 MBs total) to the Droid. I think if it had that, then it would still be an outstanding phone today and I could prolly hold out at least another 6 months before wanting to upgrade to an ICS phone. If I could just stick the RAZR internals into this phone, then it would be perfect for me because I love the form factor and design. But Moto strays from the Droid formula more and more with each phone release.. locking down bootloaders and bloating up the phone while making it massive at the same time. I'm really hoping I can get used to the 4.65" Nexus because I don't think I can easily use a phone with a display larger than 4", but since it doesn't have capacitive buttons taking more room, it might be manageable.
Apparently, the "stock rom" FRG83G is not as stock as advertised? I keep getting The package was not properly signed errors when trying to update maps, goggles and music. I read elsewhere it is because I don't have the correct build number.
Here are the numbers I have in my phone:
Version: 2.2.2
Kernel Version: 2.6.32.9-g68eeef5
Build: FRG83G
Rooted with superoneclick.
Does anybody have a real stock Droid OG aroind to compare these numbers?
UPDATE
I had forgotten that I had made a backup of the factory ROM before I started fiddling. Factory ROM restored just fine. Everything updates properly now. Above numbers didn't change.
Last edited by vey; November 18th, 2011 at 08:46 AM.
Reason: update info
The Motorola Droid - the first ever Verizon Android Phone - exploded onto the mobile market with an incredibly successful ad campaign that brough Android to the masses. With a huge and vibrant touchscreen, solid metal body, full QWERTY keyboard, 5M... Read More
Tired of GB Rom problems - get me back to stock rooted please
. Running any 2.3 ROM made my navigation totally unusable (rebooted consistantly within mins of navigating), camera unusable (would always lock up after a pic was taken and video had horrible video skipping which cause audio to lose sync) and running any background tasks were impossible (any audio service would get killed if I started navigating while playing something).
