Using Elixir and QuickBoot, you can create a widget in the notifications dropdown with working buttons for power off, reboot, and boot to recovery. The attached screenshot shows mine, which also has four Audio Manager profiles.
I'm using ICS SMOOTH ICE and don't seem to have any reboot or shutdown freezes when I use the options from the power menu. Can anyone else confirm this?
Or you can use switchpro and use the reboot button.
Flash cwm touch, then flash this kernel. This fixed shutdown and reboot for me. Or just hold the power button down for 10 seconds.
http://forum.xda-developers.com/showthread.php?t=1571882
Sent from my fully functional SAMSUNG-SGH-I727 using xda premium
NightHawkUndead said:
Flash cwm touch, then flash this kernel. This fixed shutdown and reboot for me. Or just hold the power button down for 10 seconds.
http://forum.xda-developers.com/showthread.php?t=1571882
Sent from my fully functional SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
What does the expression "fully functional " mean? To me it would mean 100 % bug free, and we all know that is a pipe dream. Of course it could mean "everything works and I haven't found any bugs... yet." But that just means you haven't been using it enough, LOL!
I just got a kick out of the expression. The is a certain arrogance it conveys, though I am pretty sure that is unintentional - I think my Skyrocket will be "fully functional" when it can get up before me and make the coffee.
Freeze shutdown app in titanium. It works fine.
Sent from my SAMSUNG-SGH-I727 using XDA
My new fix
After flashing too many ICS ROM's and mods, I had the restart/reboot freeze and my screen would not automatically turn off, no matter what the timeout setting. Here is how I fixed both:
wipe data/factory reset x3
wipe cache x3
wipe dalvik x3
Darkside wipe x3
flash Superlite 4.2 ROM
wipe data/factory reset
reboot
now, so far, all works - reboot works, screen off is back to normal, ICS goodness.
There shouldn't be any shutdown freezing issues
vatipa said:
I'm using ICS SMOOTH ICE and don't seem to have any reboot or shutdown freezes when I use the options from the power menu. Can anyone else confirm this?
Click to expand...
Click to collapse
Yeah the dev fixed the problem in the ROM so that the shutdown actually worked instead of froze. On the v2 changelog it mentions the shutdown/reboot bug is fixed
Related
My phone was working fine. No changes or mods recently. I unlocked it to check my messages and it went into a reboot loop. Not just a reboot...but a reboot loop. I had to take the battery out. This I am using CM7 Nightly 25 with Og kernel.
Did you try to flash your current rom again via cwm recovery?
Remove the battery from the phone. Put it on it then press vol up plus power button and hold. Choose recovery then try to flash cm7 zip file again without the custom kernel? Does it work?
Sent from my Nexus S using XDA Premium App
What do you mean by unlocked it to check my messages ? Were you referring to SMS & screen lock ? Are you using a setCPU screen-off profile ? Generally such unexplained ghosts tend to disappear across a reboot. It simply could be because you are on a Nightly build which could still have bugs waiting to discovered. You may want to migrate to RC2 release of CM7 for better prosperity.
Hi. i just went from virtuos rom to CyanogenMod 7.1 RC1 (v1.0.4).
But now when im waking up the phone it takes about 3-5 sec for it to wake. It took like max 1 sec on virtuos. But 5 on cyanogen. Anyway to fix this?
Thanks in advance
jullejul said:
Hi. i just went from virtuos rom to CyanogenMod 7.1 RC1 (v1.0.4).
But now when im waking up the phone it takes about 3-5 sec for it to wake. It took like max 1 sec on virtuos. But 5 on cyanogen. Anyway to fix this?
Thanks in advance
Click to expand...
Click to collapse
This sounds like you are using setCPU and have a sleep/screen off mode.
Where as VU has a special O/C daemon which is much quicker at switching CPU modes and speeds and is known to have a faster wake time.
ben_pyett said:
This sounds like you are using setCPU and have a sleep/screen off mode.
Where as VU has a special O/C daemon which is much quicker at switching CPU modes and speeds and is known to have a faster wake time.
Click to expand...
Click to collapse
no. Setcpu is not installed
When you say "5 seconds to wake up" what exactly do you mean? Do you mean:
Switch screen off
Switch screen back on again
5 second pause
Lock screen displayed
???
For me the above process is literally instant (even with SetCPU underclocking the CPU to ~350MHz when the screen is off).
If you mean something different, I'm not understanding.
LaKraven said:
When you say "5 seconds to wake up" what exactly do you mean? Do you mean:
Switch screen off
Switch screen back on again
5 second pause
Lock screen displayed
???
For me the above process is literally instant (even with SetCPU underclocking the CPU to ~350MHz when the screen is off).
If you mean something different, I'm not understanding.
Click to expand...
Click to collapse
Ye, i went to play some video game and when i tried to use the phone later the problem was gone
but the problem was Switch screen back on again 5 sec delay. but it's no delay now
jullejul said:
Ye, i went to play some video game and when i tried to use the phone later the problem was gone
but the problem was Switch screen back on again 5 sec delay. but it's no delay now
Click to expand...
Click to collapse
If out only happened once I wouldn't sorry about it
Swyped from HTC Desire S using XDA Premium
Ah... I've seen this before!
Some games don't quit (or even pause) when you press the HOME button, or even when you "quit" them via the game's own menus. This means they're open in the background, sucking up CPU.
The result is it appears as though your phone has inexplicably "slowed down" a lot.
This only stops (of its own accord) when Android's app management stuff determines that the game is no longer needed, and closes it for you.
Easiest ways to ensure this doesn't happen:
1) If you're just pressing the HOME button to leave the game, don't! Keep pressing back, and look for any "are you sure you want to quit" type dialogs (obviously pressing the affirmative button should you see one). If you don't see one, hopefully the game has quit properly.
2) If you notice your phone is running unnaturally slow... go into "Manage Running Services" (I think that's what it's called) in the "Applications" options menu, find the last game you played, click on it, and do a "Force Close". With luck, your phone will run at "full speed" again immediately thereafter!
Hope it helps!
Okay. Thanks
But I found another problem. When I try to start market it says that I need to add an account. But when I press add the app just fc. :-( I tried to start gmail. To. Add an account but gmail just fc. And I went to the account and sync in setting.
But I couldn't add any gmail account
Sent from my HTC Desire S using XDA Premium App
jullejul said:
Okay. Thanks
But I found another problem. When I try to start market it says that I need to add an account. But when I press add the app just fc. :-( I tried to start gmail. To. Add an account but gmail just fc. And I went to the account and sync in setting.
But I couldn't add any gmail account
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
LaKraven said:
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
Click to expand...
Click to collapse
Okay. No I didn't install an custom kenel.but I will try to flash the zip
Sent from my HTC Desire S using XDA Premium App
jullejul said:
okay. No i didn't install an custom kenel.but i will try to flash the zip
sent from my htc desire s using xda premium app
Click to expand...
Click to collapse
don't forget to erase your cache before flashing the zip, or you'll "soft-brick" your phone!
LaKraven said:
When you wiped the data, cleared the cache, flashed your ROM, flashed the kernel (assuming you put a custom kernel on), did you then flash the Google Apps package (http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip) as well?
If not, download it, stick it on an SD card, reboot into recovery (remember the beloved "adb reboot recovery" command), clear the cache again, then flash the google apps package onto your phone.
Should solve your problem!
Click to expand...
Click to collapse
ty works
jullejul said:
ty works
Click to expand...
Click to collapse
Happy to help
Enjoy CM7!
LaKraven said:
Happy to help
Enjoy CM7!
Click to expand...
Click to collapse
Ye i will.
Sent from my HTC Desire S using XDA Premium App
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Girn said:
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Click to expand...
Click to collapse
Sounds like left over data, bad download, bad flash, or a combo of those
Girn said:
this just started happening on the new sky ics (real thing) build, and now on superlite-mx 5.1.. ill press a button and even somtimes just pulldown notifcation bar and it will restart and vibrate over and over till i press the power button to restart the phone
Click to expand...
Click to collapse
I'm going to make a shot in the dark and ask if u have uclcl5 installed as ur radio. If so I causes major flash issues for me on a fresh rom install. So much so I have to flash cla4 first, then a new from, then cl5 again to get it to work
icenight89 said:
I'm going to make a shot in the dark and ask if u have uclcl5 installed as ur radio. If so I causes major flash issues for me on a fresh rom install. So much so I have to flash cla4 first, then a new from, then cl5 again to get it to work
Click to expand...
Click to collapse
No im using cla4.. I followed all steps and did superwipe. Why is it still bad flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Girn said:
No im using cla4.. I followed all steps and did superwipe. Why is it still bad flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
sometimes for no reason band corruption occurs. I suggest the following in can
factory reset 3x
format system 3x
wipe dalvik cache 3x
dark side 2x
Odin back stock
reboot twice
Odin can
dark side again
flash custom rom
I had similar problems to you and this looking procedure cured them.
I have the same problem with my fiancée phone which I am on right now. Shuts off and starts repeatedly vibrating on a stock non rooted phone.... I never got around to rooting this phone, unless she did it and didn't tell me.but assuming this isn't rooted what do I do?
mistaashby said:
I have the same problem with my fiancée phone which I am on right now. Shuts off and starts repeatedly vibrating on a stock non rooted phone.... I never got around to rooting this phone, unless she did it and didn't tell me.but assuming this isn't rooted what do I do?
Click to expand...
Click to collapse
Could be a sticky power button
Sent from my A500 using Tapatalk 2
StolenVW said:
Could be a sticky power button
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
That
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Pull the battery plug in the USB cable and put the battery back in. Charge it. Mine did that when the batt died. Wouldn't even charge etc.. gotta trick it into booting then leave it for a while let it charge. Wipe battery stats if your rooted cwm etc...
Sent from my SAMSUNG-SGH-I727 using xda premium
Hello guys,
I've started yesterday messing with my transformer
Root is done and TWRP is flashed.
Now, I want to flash EOS 4 and KatKernel but I have some doubts.
1. The last version of TWRP is compatible with 4.2.1, right?
2. What do I install in first place? Kernel or ROM?
3. If I got a brick/bootloop, how can I solve it?
Thanks in advance. I'm used to change ROMs in my Xperia Arc S, but not in my TF
You should be running TWRP 2.3.2.3.
Be sure you wipe the following before flashing:
(Backup your data first)
Cache
Davlik
System
Factory Reset (in recovery)
Then flash the ROM first.
The rest don't matter, but flash GAPPS, Kernel and any patches.
I always wipe cache and Davlik again.
Reboot.
Enjoy
frederuco said:
You should be running TWRP 2.3.2.3.
Be sure you wipe the following before flashing:
(Backup your data first)
Cache
Davlik
System
Factory Reset (in recovery)
Then flash the ROM first.
The rest don't matter, but flash GAPPS, Kernel and any patches.
I always wipe cache and Davlik again.
Reboot.
Enjoy
Click to expand...
Click to collapse
Thanks mate!
What if I get into a bootloop?
Chances are you will not get a bootloop.
If you do, boot to recovery, wipe and reinstall. To boot to relcovery, hold VOL DOWN and POWER for 12-15 seconds until you see small white text. Release both and tap VOL UP quickly.
If you brick it to where you cannot get to recovery (which I think you will be hard pressed to do) use EasyFlasher to reinstall recovery or flash the stock ROM again.
Oh btw, I tried several times to enter recovery the way you said and the TF never turns on.
I always have to connect the charger and press the VOL DOWN for it turn on by itself, and then the small text appears
Sorry about my english man
Sounds like a faulty power button on boot.
frederuco said:
Sounds like a faulty power button on boot.
Click to expand...
Click to collapse
But it works fine if I don't try to boot to recovery.
I am not sure, but at least you can get to recovery with the power cord.
Hi, I did like you said and all went perfect, thank you Just one more thing, its safe to update the ROM using goo manager?
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
ricardocardoso said:
Hi, I did like you said and all went perfect, thank you Just one more thing, its safe to update the ROM using goo manager?
Click to expand...
Click to collapse
Yes
Sent from my Transformer TF101 using xda app-developers app
ricardocardoso said:
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
Click to expand...
Click to collapse
Turn off autocorrect in the AOSP keyboard.
Or go grab a new keyboard from the play store.
frederuco said:
Turn off autocorrect in the AOSP keyboard.
Or go grab a new keyboard from the play store.
Click to expand...
Click to collapse
I did that already.
I downloaded Kii Keyboard and at the beggining I had no problems. Then, I changed the theme in the options and now it closes again :/
Last I read in the EOS thread the theme manager had some issues. A different one was listed to use instead somewhere in the thread.
Could be related to that.
Ok, i'll search a bit. And what about the sound issue? Never heard about it?
Sent from my Transformer TF101 using XDA Premium HD app
Oops, missed that.
Try using the K.A.T Toolbox and open it, go to the audio tab and hit the FM34 DSP Reinit button.
Also, if you tick the CASCADE box, it will give you louder volume with the speakers.
That worked, thanks a lot
Sent from my Transformer TF101 using XDA Premium HD app
reboot
ricardocardoso said:
I noticed that the virtual keyboard closes after I type the first letter (in browser, games, play store, etc) and that after unplug my headphones, theres no sound, only with a reboot.
Any way to fix this?
Click to expand...
Click to collapse
you can also use this and other apps to reboot to recovery. Quick Reboot - at the play store.
scott
EDIT I use Transformer Reboot To Recovery
If you are running EOS, why use an app to reboot to recovery?
Just hold the lock button for 3 seconds, choose REBOOT, then on the next popup choose RECOVERY
Good thread, just bookmarked so I can ask some questions in here instead of cluttering up the development thread..
This is the Q&A for the unofficial CM 10.2 for the SGS4G.
Sent from my SGH-T959V using xda premium
Is it just me or is fix permission missing from CWM.
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
Yeo, it is. I didn't touch anything related to the recovery except the recovery fstab that I must update to b compatible w the new JB so idk if I have to do anything else to have that feature back or it was CWM by default then, I will find out bout it soon.
itzik2sh said:
So, apart from GPS not working, as far as you know everything basic is working well?
sent from me
Click to expand...
Click to collapse
You can say so
Sent from my SGH-T959V using Tapatalk 2
Damn... I thought there was a chance GPS would somehow be possible I'm starting to think its wishful thinking... Come on samsung
Sent from my SGH-T959V using Tapatalk 2
getochkn said:
Is it just me or is fix permission missing from CWM.
Click to expand...
Click to collapse
I believe koush decided to throw away the fix permissions button in CWM because he said it was largely placebo effect and had no real purpose anymore.
Sent from my Nexus 4 using xda app-developers app
Thanks for all the solutions and answers that I have collected from users around here, I have been able to update the OP for the FAQ (post 3) in the main thread. So either a question is answered here or not, please also have a look over the FAQ @ post 3 in the dev thread to track down the answered common questions, thanks .
Sent from my SGH-T959V using Tapatalk 2
so do you know if external mics work on this Rom?
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
http://www.android.com/about/jelly-bean/
Vismis said:
Ok guys i have flashed near every rom this phone has ever had and never ran into a bootloop problem. So i had CH 10.2 on my phone for 2 days with no hiccups. Then today after letting my phone die completely "battery death" i pluged it in and now it keeps bootlooping and i cant get it into recovery if i hold down volume down + power it loops at the galaxy s 4g starting screen. If i let it go of the power button at the correct time it just bootloops. anyone have any ideas?
Click to expand...
Click to collapse
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
1234west said:
The Recovery Is Volume Up + Volume Down + Power Button
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Vismis said:
Ok if i hold that combo it loops the galaxy s 4g splash screen if i hold the combo then let go of the power button at any time during the splash or right when it turns to black then it just normally boots into the Cyanogen boot screen then sits there spinning for going on 2 hours then i just pull the battery any ideas?
Click to expand...
Click to collapse
Battery Pull. Hold Vol Up + Vol Down + Power. Whenever The Samsung Galaxy S 4G Splash Screen Comes On, Let Go Of The Power Button And Keep The Volume Buttons Held Down. Should Take You To Recovery
Sent from my SGH-T959V using xda premium
OMG YES!!! I have no idea what i did but i pressed the combo when i plugged it into my computer and it looped the battery screen twice then went straight into CWM recovery did not go through the splash screen like a normal CWM recovery start but whatever i got to remove the rom and flash the new Slim Rom . Anyone have any idea what could have caused this just so i know what to or what not to do in the future ?
Try using adb
Sent from my SGH-T999 using xda app-developers app
To get to CWM recovery on this ROM, simply download 'Quick Boot' application and use it to get to recovery. It works.
Apex launcher crashes as well. I think issue is ROM related. Also, ROM is very heavy, I couldn't find why.
Edit: ROM is snappier after using CM performance features and letting cache do its work.
sent from me
jeffreylin_ said:
That's not very helpful if you can't get past the CyanogenMod splash though.
Click to expand...
Click to collapse
I got through the splash screen on 1st try.
You should check if you worked according to ROM instructions.
I usually always format system as well as wipe everything twice before flashing any new ROM.
I was referring to :
1. the lack of recovery button on power menu.
2. The inability to use hardware keys to get to recovery after flashing this ROM.
Heimdall One-click (in download mode) and try again.
You're right - I missed that option in developer features - it's called 'advanced reboot options'.
I'd suggest you get to download mode - one click heimdall and reflash this ROM after dowble wiping dalvik, cache, and format system.
I've flashed numerous ROMS to my phone before but have never ran into a problem like this.
-I went back to stock
-flashed CM7, as recommended from the OP
-downloaded and flashed CM10.2 but it gets stuck around 75%
I've been on this thread, and the rom thread as well as waiting a bit, hoping to find a solution or it figures itself out. Nothing! Is it unsafe to pull my battery when its at 'Installing update' (75%) for an extended period of time?
Also, i am on CWM 5.0.2.8
Thanks
I flashed it from ICS (Ultragen) and had no problem.
You can try that as well.