Trying to figure out cause of not awaking from sleep mode
im on the latest beast with chevs 1.0 kernel
for my setcpu profile everything is set for 550 max under those certain cases and 250 min
i have 5 widgets
i have about 56 apps
it doesnt happen every day but it happens often enough that its bothersome..everything else runs smooth it just doesnt wake up sometimes and have to do battery pull
ive had this problem with previous versions as well so i figure its gotta be one of my settings or something
This may offer some help. I did the wipe twice/nandroid install of beast 0.8 with NO oc kernel updates and was experiencing the exact same thing I decided to wipe twice/nandroid back to 7.4 beast and haven't had a single issue waking up from sleep
Device(s): See my signature...this section isn't big enough anymore!
Thanks: 1,729
Thanked 1,521 Times in 810 Posts
Warning...this will wipe your system/data/cache...but it is probably needed
I have started in the past month or so...using ADB to "clean" up my partitions and for me...I have had greater success and less of those stupid little problems like the one you posted.
When you are going to load a new ROM back up to a different ROM, etc. Do the following:
- Boot phone into recovery:
- With ADB, type the following in your computer:
Code:
adb shell
# format DATA:
# format CACHE:
# format SYSTEM:
The data and cache you do all the time I'm sure...but most people don't ever format their system. This is where you are writing all of your system files to and if your switching from ROM to ROM...you are leaving fragments and possibly other files behind. Like I said...I have had less of these problems performing this EVERY time I restore a new backup or ROM...If you want to keep data but you are moving to a new ROM...just format the system and cache.
__________________
Myself: Galaxy Nexus, Droid 4, Transformer, Logitech Revue, Sony Blu-ray Player with Google TV
Wife and Kids: iPhone4, Apple iPad, Galaxy Player 4.0, B&N NookColor
Retired: Thunderbolt, Droid Pro, Fascinate, 2 Motorola Droids (the OG), Galaxy Tab (7" WiFi), Archos 70
Last edited by UBRocked; March 20th, 2010 at 10:25 PM.
Device(s): BAMF, Sense 3 RC3... DreamKernel-2.2.2Beta-SENSE... waiting for my turn to brick.
Thanks: 3
Thanked 18 Times in 18 Posts
I always do a cache wipe and a data wipe.... for every ROM I install. And my problems are very limited. The one's I have had a mainly due to JIT issues... which are easily remedied.
I would do a full Nand of your present setup... make sure you select everything. Then try doing a full wipe of both cache and data... twice.... and load up BB0.9.
I know it a pain... but it's the cleanest way to go. I can setup my whole phone now.. with all 7 screens full of icons and widgets completely working and configures in about 30 minutes now... I've done it so much. lol.
EDIT: UBR is correct... matter of fact I am seeing a newer better cleaner way to do this from now on.
Thanks again UBR..
Last edited by DroidSuks; March 20th, 2010 at 10:32 PM.
Warning...this will wipe your system/data/cache...but it is probably needed
I have started in the past month or so...using ADB to "clean" up my partitions and for me...I have had greater success and less of those stupid little problems like the one you posted.
When you are going to load a new ROM back up to a different ROM, etc. Do the following:
- Boot phone into recovery:
- With ADB, type the following in your computer:
Code:
adb shell
# format DATA:
# format CACHE:
# format SYSTEM:
The data and cache you do all the time I'm sure...but most people don't ever format their system. This is where you are writing all of your system files to and if your switching from ROM to ROM...you are leaving fragments and possibly other files behind. Like I said...I have had less of these problems performing this EVERY time I restore a new backup or ROM...If you want to keep data but you are moving to a new ROM...just format the system and cache.
thanks for the suggestion ill try this tomorrow
is that all i have to do step wise if you can dumb it down step by step cause ive done very limited things with adb so far
Device(s): BAMF, Sense 3 RC3... DreamKernel-2.2.2Beta-SENSE... waiting for my turn to brick.
Thanks: 3
Thanked 18 Times in 18 Posts
That looks about right.
Make your in SPRecovery before you start typing the commands in adb. From there you should be able to load your ROM of choice.
And MAKE SURE!!!... you put the raw Nandroid restore of the ROM you want in the Nandroid directory BEFORE you start the process.... otherwise you'll be stuck high and dry re-flashing whatever your have in your Nand directory. I always keep 2 or 3 full nands of my favorite up to date builds in my nand dir. Just in case..
The Following User Says Thank You to DroidSuks For This Useful Post:
Device(s): See my signature...this section isn't big enough anymore!
Thanks: 1,729
Thanked 1,521 Times in 810 Posts
Quote:
Originally Posted by iamloco724
thanks for the suggestion ill try this tomorrow
is that all i have to do step wise if you can dumb it down step by step cause ive done very limited things with adb so far
Can you get to adb shell (you type in "adb shell" and the command prompt returns with #)?
If so, that is it. The commands (format DATA: format CACHE: and format SYSTEM are all built into SPRecovery. so getting to adb shell is all you need to worry about.
Note: When I wrote:
# format DATA:
You don't need to type the '#' It will already be there.
Device(s): See my signature...this section isn't big enough anymore!
Thanks: 1,729
Thanked 1,521 Times in 810 Posts
Quote:
Originally Posted by DroidSuks
That looks about right.
Make your in SPRecovery before you start typing the commands in adb. From there you should be able to load your ROM of choice.
And MAKE SURE!!!... you put the raw Nandroid restore of the ROM you want in the Nandroid directory BEFORE you start the process.... otherwise you'll be stuck high and dry re-flashing whatever your have in your Nand directory. I always keep 2 or 3 full nands of my favorite up to date builds in my nand dir. Just in case..
Good point...I don't think of this because I always have several files in the nandroid folder. Good news is that even if you miss this step, you can get back to SPRecovery and then mount SD card...then put a backup in the sdcard/nandroid folder.
Can you get to adb shell (you type in "adb shell" and the command prompt returns with #)?
If so, that is it. The commands (format DATA: format CACHE: and format SYSTEM are all built into SPRecovery. so getting to adb shell is all you need to worry about.
Note: When I wrote:
# format DATA:
You don't need to type the '#' It will already be there.
Make sense?
yea i can get to adb fine i just wanted to confirm thats all that had to be done..thanks again hope all of this helps the problem if not ill post back lol
When you guys wipe to put on new roms you manually install all apps or use Something like titanium?
Titanium is the way to go - restoring the app and app data. I would advise not to restore system data (even with similiar ROMS). I have gotten to the point where I have flashed ROMS and reconfigured my system while stuck in traffic (yup, while the car is stopped).
__________________
____________________________
Neil
Currently hooked on GB (rooted, overclocked and deoxed). Tomorrow, who knows
Last edited by shrink57; March 21st, 2010 at 12:55 AM.
Warning...this will wipe your system/data/cache...but it is probably needed
I have started in the past month or so...using ADB to "clean" up my partitions and for me...I have had greater success and less of those stupid little problems like the one you posted.
When you are going to load a new ROM back up to a different ROM, etc. Do the following:
- Boot phone into recovery:
- With ADB, type the following in your computer:
Code:
adb shell
# format DATA:
# format CACHE:
# format SYSTEM:
The data and cache you do all the time I'm sure...but most people don't ever format their system. This is where you are writing all of your system files to and if your switching from ROM to ROM...you are leaving fragments and possibly other files behind. Like I said...I have had less of these problems performing this EVERY time I restore a new backup or ROM...If you want to keep data but you are moving to a new ROM...just format the system and cache.
im trying to do this now and im getting
format_root_device: cant resolve "data" and the same for system and cache
I had this issue before when I was using Adamz low voltage kernels, by going to his medium voltage version the issue stopped.
My suggestion would try a new kernel
Same issue and result here... Using UltimateDroid v8 (customized) - switched to one of Adamz medium voltage kernels and the problem seems to have gone away.
this happened to me the first few days with AdamZ new v6 rom. i was trying setcpu at 250/250 when sleeping, then upped it to 250/400 and it hasn't happened since.
I have only had this problem when not properly formatting before flashing a new ROM, like UBRocked said.
__________________ So I'm guessin' there's questions that need addressin' like how he fresh in the adolescence and wreckin em' Rules & Guidelines, Zero Tolerance Policy.
well i was able to do the format thanks to ubrocked and now have everything back to how it was and im trying out adamz low voltage so we will see what happens now
Device(s): (soon) Galaxy Nexus, HP Touchpad, RAZR, Thunderbolt, Incredible, D1
Thanks: 195
Thanked 702 Times in 290 Posts
Quote:
Originally Posted by DroidSuks
That looks about right.
Make your in SPRecovery before you start typing the commands in adb. From there you should be able to load your ROM of choice.
And MAKE SURE!!!... you put the raw Nandroid restore of the ROM you want in the Nandroid directory BEFORE you start the process.... otherwise you'll be stuck high and dry re-flashing whatever your have in your Nand directory. I always keep 2 or 3 full nands of my favorite up to date builds in my nand dir. Just in case..
Ive done that before, and if your ever in that situation just go into mount and then select the 'enable mass storage device' and then load up the file, hit the button again and then to a nandroid... but be warned its usb 1.0 and its slooooowwwww
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
Trying to figure out cause of not awaking from sleep mode
