• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root think I am screwed, root went fine then POW

congrats! fyi petes bb rom is set to govern itself. it ramps up to 800mgh under demand then back to 250 at idle. its one of the thinngs i love about this rom. did you ever get your signal strength back?

thanks for the govern tip....

you know, I cant really say that baseband I flashed was really as good as I recalled as I seem to notice a bit better signal strength, but not as good as I recalled under 2.0.1 before 2.1 f'ed it up. I might give Pete's a try that I see in his BB offerings.
 
thanks for the govern tip....

you know, I cant really say that baseband I flashed was really as good as I recalled as I seem to notice a bit better signal strength, but not as good as I recalled under 2.0.1 before 2.1 f'ed it up. I might give Pete's a try that I see in his BB offerings.

You did update with *228 didn't you? Basebands are location specific so what works for some may not work as well for others. I use speedtest.net. its a free app in market and it tells you how fast your 3g speed is as well as your ping results.
 
digdug.. yes, I did a *228. Since there is only 1 baseband for original 2.0.1 to select from, odd that it would be "location specific" as you and others have said as the fact there is only 1 to download in ROM Manager tells me, that was the choice.

As for my endeavor to go to 2.2 via BB 0.4.. I went well BUT I had to bail out and flash back to my 2.1 :( When I went to BB 0.4 and started using Titanium and MyBackup to restore settings, things were not taking - like settings in Handcent and my phone and all my custom tones and such. That same tactic worked perfect when I did the 2.1 root, so it caught me off guard here. As well, I screwed up and when I did the data restore I restored my gMail contacts and accidentaly hit the wrong setting and erased a bunch. My bad. On top of that, I was missing some apps AND, very oddly, was missing apps like the Alarm. The Alarm was jst gone. A generic icon was there, but no Alarm. So, I just do not have time to deal with it all now so I just booted into clockworkMD recovery and flashed back to where I was at 2.1 rooted yesterday. Now that I am understanding more it wasn't that painful and all is as it was and fine.. I am hurrying out of excitement and need to slow down and figure out some of these issue. Oh, plus the background wallpapers from 2.1 are not in 2.2 (they are here) and there was one 1 really wanted, so I got to find that. so add this all up and I just decided to roll back.. will do it again this weekend.
 
I dont use titanium back up but my common sense leads me to this ....
you cant run a back up in Vista and then load up Win7 and do a restore ...
2.2 is very different than 2.1 if it was me I would go thru the trouble to reinstall everything. then do your back up and when ever you change roms from a 2.2 to another 2.2 then restoring your backups are fine.

But I am kinda nit picky and like total clean installs. Like you I dont have time to be jacking around trying to fix bugs and such. Yes it takes more time at first but, saves me time and grief later on.
 
that logic makes some sense.

BUT, if I was putting back apps, like Handcent, I would expect the data for that has not changed. So, I want that data + app to go back. Of course I would not put back the old stock apps - browser, market, etc and such, just apps I previously downloaded AND their data. to me, since these apps are both 2.2 and 2.1 comptaible, I expect their data and the app to go. there was some loss there and it was causing issue and so, it was just best to go back.

now, why there was no Alarm? not sure.

but you see, I started getting so excited, some of this I did not 100% think through, like going from 2.1 to 2.2 and how architecture changes can have effects, though like I said above, some things should not change like my settings. if you did the OTA legit update, and had Handcent, you would not expect to come back and have all of your settings toasted and lost. again, I just need to slow a bit, have time ready, and think a 2.1 to 2.2 migration plan through a bit on how best to salvage my apps and my data. I will need to do a 1 by 1 restore via Tit or MyBackup - NOT a batch restore - to make sure I do not load up old stock apps and data. but then, I do need to make sure I can/do install old calendar data, but not an old calendar.. get it? so, time to chill and plan it out as once I do a 2.1 --> 2.2 & get my apps and my data and my settings as needed, I no longer have to worry about this. so that effort has to be done up front now, and I let it get ahead of me.
 
I do understand ... but I guess I change roms so often (a few times per month) I dont really have that much data that needs restored.
And I am a speed freak I dont have lots of apps ... maybe 40 or so
 
I just used AppBrain to take an inventory of all my apps - 90 - and I will use this list to help me make sure I do not carry over and force data or apps from 2.1 stock apps to get carried over to and overwrite or mess with stock 2.2 apps (market, calendar, phone, browser, gallery, camera, music, etc..) as it is safe to assume that many are improved and updated in 2.2. Then, once I get all MY not stock apps copied back over and install their data, I will consider going back too some of the stock apps like phone or calendar, see how out of whack they are and see about pushing JUST my data over - not the app of course as the 2.2 might have a newer version - via a 1 by 1 option in Titanium or MBP. I did not do this the first time, that was part of my issue as I rushed and it dawned on my later.

I have done a lot of tweaking of apps like Handcent - custom colors, tones, pictures, notifications - and LEDs via Missed Call and custom ringers and such for people in the Phone, etc. etc and the goal - just like the OTA would do - would be to keep those in tact and working so I have less setting up to do of all the things I have already tweaked out that work great.
 
by location specific i meant geographicaly your physical location will determine what baseband works best for you and gives you the best reception. this is tried and true by many people as far as apps being restored, i have never used another app to restore my apps after flashing a rom. i really dont have that many on my phone and most of them restore by themself anyway. i even wipped my sd card when i ws having trouble storing my apps to it on bbv.04. and it fixed my problem.
 
that logic makes some sense.

BUT, if I was putting back apps, like Handcent, I would expect the data for that has not changed. So, I want that data + app to go back. Of course I would not put back the old stock apps - browser, market, etc and such, just apps I previously downloaded AND their data. to me, since these apps are both 2.2 and 2.1 comptaible, I expect their data and the app to go. there was some loss there and it was causing issue and so, it was just best to go back.

now, why there was no Alarm? not sure.

but you see, I started getting so excited, some of this I did not 100% think through, like going from 2.1 to 2.2 and how architecture changes can have effects, though like I said above, some things should not change like my settings. if you did the OTA legit update, and had Handcent, you would not expect to come back and have all of your settings toasted and lost. again, I just need to slow a bit, have time ready, and think a 2.1 to 2.2 migration plan through a bit on how best to salvage my apps and my data. I will need to do a 1 by 1 restore via Tit or MyBackup - NOT a batch restore - to make sure I do not load up old stock apps and data. but then, I do need to make sure I can/do install old calendar data, but not an old calendar.. get it? so, time to chill and plan it out as once I do a 2.1 --> 2.2 & get my apps and my data and my settings as needed, I no longer have to worry about this. so that effort has to be done up front now, and I let it get ahead of me.

When you get a chance to flash a 2.2 ROM this weekend, I agree that you should take the time to customize it the way you want it and do whatever it takes to make it *home*. This could take a couple of hours. Use your app inventory to make sure that all your apps are accounted for, and re-download/install anything that is missing. Then make your nandroid backup of your complete system and also make your Titanium Backup backups and MyBackup Pro backups.

What this creates is a *homebase* for you - a point to return to when you experiment with new ROMS.

It's important to keep in mind that when you flash a new ROM, many of us have experienced a *break-in period* where your Droid adjusts to the new setup. Until you get through this, it is possible that you may experience homescreen redraws and force-closes. This is normal for many of us flashers :eek:. It happens every time I flash something new ROM-wise and then things settle down and smooth out.

I know everyone here seems to have their favorite ROM. It's really hard to flash a *bad* ROM, but each seem to have their own personalities and therefore its easy to like some more than others. My suggestion is that you establish your *homebase* ROM first, then try some others. Remember, you can backup each ROM after you get it just the way you like it. Sometimes for the heck of it, I'll use CynogenMod 6.0.0 RC2 (my current favorite), then do a restore on Simply Stunning and Kangerade and then Bugless Beast just for the heck of it. It doesn't take long to restore a backup and it's fun to make comparisons.
 
If you don't want to do this with SS or any other ROM, I would most DEFINITELY recommend doing this with kernels. If you try installing a kernel that your Droid cannot handle (like 1.2Ghz or something like that), it will likely cause a boot loop. If that happens, you'll want to be able to pull your battery and boot back into recovery mode and try another kernel that is not quite so fast and try that. Otherwise, you'll have to take the time to restore to your previous ROM and start all over again. It's worth putting 2, maybe 3 kernels on your SD card just as precaution.

By the way, I think Chevy's kernels are the best. :)

can I just download 3-4 kernels onto my SDcard into a directory called "kernels", reboot into recovery, and install from the SD card? I don't have to go through the whole rename to update.zip and put into the root, I can just leave the zip file what it is called (ChevyNo1-1.0Ghz-ulowV-7slot-update.zip) and install that as is from any directory I want, no?

OR

I could also install from ROM Manager and install ROM from the SD card, no?

good directions

chevy's kernels
 
cool.. going to try some Chevy's kernels right now.

starting off with ULV 1.1.. if that works, I will likely just stop there to be honest

stand by
 
UPDATE:

with CPUset I set to 250 and 1100 (do I need to check the box "set on boot" to have it remember my settings)

1.1 ULV w/ Quadrant benchmark of 1376, IIRC I use to have scores in the 300's in 2.1 and 700's in stock 2.2

I guess I will find out if it is stable in time, or would I know by now?
 
only choose "set on Boot" after you know its stable. Also make sure it is unchecked before flashing a new kernel.

you pretty much now right away but, sometimes they can cause random re-boots or extreme lag

also watch your temps .... some run hotter than others
 
only choose "set on Boot" after you know its stable. Also make sure it is unchecked before flashing a new kernel.

you pretty much now right away but, sometimes they can cause random re-boots or extreme lag

also watch your temps .... some run hotter than others

only weird issue so far is that Qudrant bails out of the test and it takes like 3-4 times to get a full test result
 
LocknLoad Wrote: "can I just download 3-4 kernels onto my SDcard into a directory called "kernels", reboot into recovery, and install from the SD card? I don't have to go through the whole rename to update.zip and put into the root, I can just leave the zip file what it is called (ChevyNo1-1.0Ghz-ulowV-7slot-update.zip) and install that as is from any directory I want, no?"


You could try that, but don't wait until you're stuck in a boot loop to need it. If you're using ClockworkMod Recovery, there's no need to change the name to *update.zip*. Also, if you're stuck in a boot loop, you won't have access to Rom Manager, and that's why when you reboot into recovery (holding X key while rebooting), you want to have those kernels easily identifiable and accessible.

If you're not stuck in a boot loop, you can certainly go into Rom Manager and select "Install Rom From SD Card" and change the ROM.
 
I never run ULV's as I have had little issues before and even got stuck on the "M" once and it took me like 10-15 attempts to get a restore to stick ..... I was as freaked as you were when this thread began :)
 
i think the best way to try out a new kernal is to use the stress test in setcpu. i read that you are supposed to run it for 15 minutes and if it doesnt reboot or get to hot then it is a good indication that you have a stable kernal.
 
I never run ULV's as I have had little issues before and even got stuck on the "M" once and it took me like 10-15 attempts to get a restore to stick ..... I was as freaked as you were when this thread began :)
i must have a charmed droid lol because i can run ulv 1.25 without any problems. i cant really see a significant improvement over 1.2 though
 
LocknLoad Wrote: "can I just download 3-4 kernels onto my SDcard into a directory called "kernels", reboot into recovery, and install from the SD card? I don't have to go through the whole rename to update.zip and put into the root, I can just leave the zip file what it is called (ChevyNo1-1.0Ghz-ulowV-7slot-update.zip) and install that as is from any directory I want, no?"


You could try that, but don't wait until you're stuck in a boot loop to need it. If you're using ClockworkMod Recovery, there's no need to change the name to *update.zip*. Also, if you're stuck in a boot loop, you won't have access to Rom Manager, and that's why when you reboot into recovery (holding X key while rebooting), you want to have those kernels easily identifiable and accessible.

If you're not stuck in a boot loop, you can certainly go into Rom Manager and select "Install Rom From SD Card" and change the ROM.

now and then I have issues with clockworkMD. a few times I have had to reflash it after going into SPRecovery as it failed to go into recovery. then it works fine again. not sure why.

it almost seems like now and then I want to try to boot into it just to make sure I can :)
 
i think the best way to try out a new kernal is to use the stress test in setcpu. i read that you are supposed to run it for 15 minutes and if it doesnt reboot or get to hot then it is a good indication that you have a stable kernal.

just did about a 14 min test, no reboot, does not feel 1 bit warmer on my skin as to when I started. reports no errors. temp was about 82.4-86

does the SetCPU widget temp reading ever change????
 
this is the single most excited thread ever.

Also try (if you care to spend the cash) on Temp Monitor for cpu/battery temps, more accurate and more options I love (like show temps when in status bar when they get to high), also it has sexy widgets now.
 
it seems on some kernels you have to refresh the widget. There is a thread on this subject.
It seems to work well on my LithiumMod rom with the stock kernel. I have not had time to load a new kernel yet and may stick with the 800mhz stock one..... undecided .... lol
 
just did about a 14 min test, no reboot, does not feel 1 bit warmer on my skin as to when I started. reports no errors. temp was about 82.4-86

does the SetCPU widget temp reading ever change????


i use the screen that the stress test is on to read my temps. when you hit the back button look at your cpu temps and battery temps

i dont use the set cpu widget there have some threads saying the widget decreases battery life.
 
I am running chevy's 1.0 LV (that comes with SS 4.6). What temperature is generally considered too much? I want to set a rule that if a temp exceeds XX
 
Back
Top Bottom