I can't count how many I have but I think I just did topped my list. I went to backup my Skyraider 4.0 but instead I deleted my CM7 41 by accident!! I had that puppy setup perfectly!!
c'mon..fess up
I think the most "duh" thing I've done, albeit rather minor, was spending like ten minutes wondering why a radio wasn't being recognized by HBOOT, just to realize it was still in my downloads folder on my SD card lol. Other than that, its been a very painless experience with my DI I've had her since day one, too.
Sent from my Droid Incredible running CM7.
Or the time I wanted to shut down so i could go to recovery but instead hit reboot. Thinking I could catch it just as it hit its off cycle I held the volume down and power button. Yup my phone gave me a nice little reminder not to do that by vibrating 4 times and going to the android with exclamation mark screen. Did a battery pull and all was well. And my heart still works.
DINC|CM7|INCREDIKERNEL|VB-50
Sadly it took me like a day to figure out why I wasn't operating CWM properly... I was using the power button instead of the optical device to select things -.-
xirftwx said:
Sadly it took me like a day to figure out why I wasn't operating CWM properly... I was using the power button instead of the optical device to select things -.-
Click to expand...
Click to collapse
Lol, good one
DINC|CM7|INCREDIKERNEL|VB-50
First time I OC'd my phone I forgot to take the governor off performance and hadn't saved my temp profile... yeah, my battery door was squishy
xirftwx said:
Sadly it took me like a day to figure out why I wasn't operating CWM properly... I was using the power button instead of the optical device to select things -.-
Click to expand...
Click to collapse
A lot of people I've seen on here have had that problem when they started out lol.
Sent from my Droid Incredible running CM7.
Related
can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?
rapidfire224 said:
can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?
Click to expand...
Click to collapse
Im having the same issue..weird!
Well known issue with CWR. Koush said its not high on his priorities. You could download the source and try to figure it out though.
hmmm, ok. im not an expert with doing things from source. somone else maybe, with more skills?
It's an issue when the charger is plugged in. It should shut down fine if you haven't got the charger connected.
there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.
androidcues said:
there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.
Click to expand...
Click to collapse
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App
helloelan said:
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.
DanWilson said:
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.
Click to expand...
Click to collapse
First time I discovered this bug I was about 9 hours late. I grabbed my hot ass phone n unplugged. I put it infront of the ac vent so it could cool down. After about ten minutes I powered up n the setcpu widget told me the phone was at 120 something degrees.
Needless to say my first g2 never ran right after words. Too many random reboots n odd graphical glitches.
I unrooted and cried bad hinges so tmobile would replace it.
Damn shame its not on his priorities list...
Issue: Power button won't turn screen off. Either it doesn't respond to the button push at all or it treats it as a long press and will pop up the phone options menu. Power button wakes phone just fine. Also, if I boot into recovery while experiencing this, not all power button pushes register within recovery (ouch).
It's weird because I experienced this for the first time like 2 months ago a few hours after flashing a Tiamat kernel (actual kernel may have had nothing to do with it), but after fiddling around with my phone it started working again.
Well, it started happening again on Saturday using CM 7.0.3.1 w/ GoDm0dE v5. I got it to work again by doing a factory reset, then restoring a backup. Well, it came back last night and persisted after another factory reset. It was very consistent today -- for hours it would either do nothing after pressing power or it would pop up phone options. Finally, a did a factory reset within CM7 and also within Amon-RA 2.3 and then restored a backup from yesterday and the power button functioned properly for about 1.5 hours.
Has anyone experienced anything similar?
ROM: CM 7.0.3.1
Kernel: Stock
Recovery: Amon_Ra 2.3
HW: 003
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
drgonzo712 said:
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
Click to expand...
Click to collapse
Thanks -- I actually tried the compressed air. I'm thinking it's hardware. It seems to have gotten worse in the past hour.
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
shdwboy said:
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
Click to expand...
Click to collapse
I unrooted and it actually started to do the same, but when waking the device. Brought it into Sprint and getting a replacement on Wednesday.
Had this exact same issue up until a few days ago. I took a needle and went around the power button front and back, something unjammed I guess and now it works like a charm. I've also had this with a software problem. My power button wouldn't work, even in recovery. I restored a nandroid and this fixed it. Hope this helps! Best of luck.
I had the same issue. Sprint said it wasn't the button but the board not responding to the button. Got a new phone.
Sent from my PC36100 using XDA App
For about the last 2 months my sister's Incredible has been acting incredibly wonky.
1. It is getting the infamous low application data message when she has plenty of storage.
2. The track ball does its own thing and turns pages by its self on the home screen.
3. The Power button is hit and miss. This thread explains it very well. http://forum.xda-developers.com/showthread.php?t=1091064
So what is going on guys? Its on Stock with unrevoked Root... No Custom roms or custom kernals. Any help for the above problems is much appreciated.
Sounds like the phone is just going downhill. Hope she has insurance
Sent from my ADR6300 using XDA App
Larry94 said:
For about the last 2 months my sister's Incredible has been acting incredibly wonky.
1. It is getting the infamous low application data message when she has plenty of storage.
2. The track ball does its own thing and turns pages by its self on the home screen.
3. The Power button is hit and miss. This thread explains it very well. http://forum.xda-developers.com/showthread.php?t=1091064
So what is going on guys? Its on Stock with unrevoked Root... No Custom roms or custom kernals. Any help for the above problems is much appreciated.
Click to expand...
Click to collapse
The first can easily be solved by one of the awesome custom roms available, the other two seem to be hardware problems.
Hope this helps
I would back up her SMS (use something like SMS backup & restore. Doesn't require root) to her SD card and then back up her SD card. Make sure her contacts are all synced to google and not the phone and then do a restore of the phone. Bringing it back to stock and factory will help you make sure if it is a hardware issue or a software issue. If it is a software issue, root the phone and install another ROM.
Sometimes the trackball gets dirty. Blow it clean and that may solve at lest one problem. Might help the power button too.
OK, now it is really bad. Pressing the power button does absolutely nothing. It does not bring up the lockscreen! Is there a root tweak where the trackball can turn the phone on? She is having to plug her phone in to wake the screen up!
Larry94 said:
OK, now it is really bad. Pressing the power button does absolutely nothing. It does not bring up the lockscreen! Is there a root tweak where the trackball can turn the phone on? She is having to plug her phone in to wake the screen up!
Click to expand...
Click to collapse
Yup, I know CM7 has it and I'm sure other Sense roms have it as well.
I literally have never had a problem like this with this phone, but just recently I flashed the new AOKP jb 8-29 build and after a day or two of using it I started getting random reboots where the phone would crash and then start vibrating in intervals. I couldn't get it to stop unless I pulled the battery. Thinking this was just a bug with the rom, I just rebooted to recovery and wiped and flashed the latest jedi mind trick v7. I let the phone sit for a little bit after first boot, but when I then tried to go through the setup I got the exact same problem. Now the phone crashes like this every time I boot up and even while I'm in recovery mode! Someone please help if you know what might be causing this.
EDIT: Now it's doing this every time I put the battery back in; I can't turn on the phone or go into recovery while it's vibrating like this
Sound like a faulty power button. I've seen many, many threads like yours. Almost certain that's the case. Mobiletech offers a power button service. Check them out
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile/
Sent from JMT Goodness
LoopDoGG79 said:
Sound like a faulty power button. I've seen many, many threads like yours. Almost certain that's the case. Mobiletech offers a power button service. Check them out
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile/
Sent from JMT Goodness
Click to expand...
Click to collapse
I think you're right because before every time I put in the battery the phone would turn on, but I tapped the power button a few times to loosen it up and put the battery in and it didn't turn on. Is there any way to remote start without having to touch the power button that you know of? Thanks for the advice btw
This same scenario happened to me just yesterday morning. I researched it and this issue does seem to be popping up more frequently among Samsung phones. Maybe power button design is faulty and they're starting to wear out now after a year plus of use? I sent mine off to MobileTechVideos today to be fixed. I feel so lost without my phone!
jmariconda said:
I think you're right because before every time I put in the battery the phone would turn on, but I tapped the power button a few times to loosen it up and put the battery in and it didn't turn on. Is there any way to remote start without having to touch the power button that you know of? Thanks for the advice btw
Click to expand...
Click to collapse
What I've read is no. Its not the button its self, but the circuits behind the button that mess up. Unless you are really skilled at soldering and can re wire the board, I don't see that happening.
Sent from JMT Goodness
Hey all, I was trying to ask on the related threads in the dev section, but due to my post count, it won't let me.
I have a few questions that hopefully you guys will be able to help me with.
I have a rooted S3, still on T999UVALEM. I can't do the T-mobile OTA updates since it always fails, due to the root I'm assuming. I keep getting the annoying firmware update notifications and simply can't update.
I was considering loading a custom rom, but for some reason, CWM won't work anymore. I know how to flash with odin since it's easy, but I have no idea how to use ADB.
I tried reflashing CWM serveral times, multiple versions, including the latest, and I simply can't boot into recovery mode. I hold volume up + power + home, and I'll see the blue text at the top left, but after that it loads the Samsung Galaxy logo for a few seconds and goes blank. Eventually it will reboot if I keep holding the buttons, or if I let go, it will reboot again, but I can't get into CWM anymore. Anyone have a similar issue, or know how I can fix this?
Have you tried booting into recovery from ROM manager?
Try goomanager in the playstore and install TWRP instead and see if it works. It should if you are rooted.
ingenious247 said:
Have you tried booting into recovery from ROM manager?
Click to expand...
Click to collapse
I actually haven't. Going to try this now. I didn't even have it installed.. :silly:
edit:
Just did it that way, it works. Strange how I can't do it with the button combo...
Nexus Cable said:
I actually haven't. Going to try this now. I didn't even have it installed.. :silly:
edit:
Just did it that way, it works. Strange how I can't do it with the button combo...
Click to expand...
Click to collapse
More than likely you aren't doing the button combo right. You have to let off the power button after the phone vibrates when it switches back on, but continue to hold the home key and volume up key. Glad ROM manager worked for you, it's a great tool; I have had it on my last 4 phones haha
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
colbyrainey said:
More than likely you aren't doing the button combo right. You have to let off the power button after the phone vibrates when it switches back on, but continue to hold the home key and volume up key. Glad ROM manager worked for you, it's a great tool; I have had it on my last 4 phones haha
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
Click to expand...
Click to collapse
Not true
The correct way to do it (and yes I knew he was doing it wrong that's why I suggested ROM manager) is to hold all the buttons ONLY until you see that little blue writing appear at the top of your screen then IMMEDIATELY release all three buttons. Works every time, guaranteed.
Sent from my SGH-T999 using xda premium
And just to clarify when the above poster says all the buttons, he means Vol+, Home, and Power.
Thanks for your help guys. I got everything running the way I wanted it to. Only thing now is finding a ROM that has decent battery life.
With the old stock ICS rom, I could get 30 hours with light to moderate use. Now I'm getting 12hrs or so with Frosty, even less with M2, so I reverted back to M1/R7.
Check out Leankernel. It's supposed to be optimized to give maximum battery life.
CM10 based ROMs have pretty decent battery life for me. I get 16-19 hours of battery per day with screen on time between 3-5 hours running a 1.9Ghz overclock. Can't ask for much more. If you keep your CPU clock at 1.5Ghz on Leankernel with CM10, I don't see 24 hours of on time with several hours of screen on being a problem.
Xanatos57 said:
Check out Leankernel. It's supposed to be optimized to give maximum battery life.
CM10 based ROMs have pretty decent battery life for me. I get 16-19 hours of battery per day with screen on time between 3-5 hours running a 1.9Ghz overclock. Can't ask for much more. If you keep your CPU clock at 1.5Ghz on Leankernel with CM10, I don't see 24 hours of on time with several hours of screen on being a problem.
Click to expand...
Click to collapse
Nice. The only thing is that I like TouchWiz and would like to keep it. The Frosty ROM uses it so its a plus. Would I be able to run leankernel on this ROM?
ingenious247 said:
Not true
The correct way to do it (and yes I knew he was doing it wrong that's why I suggested ROM manager) is to hold all the buttons ONLY until you see that little blue writing appear at the top of your screen then IMMEDIATELY release all three buttons. Works every time, guaranteed.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
the problem that i am facing is, if i dont let go of the power button only, the blue writing wont show.
Unfortunately not. Leankernel was built specifically for CM10/AOSP ROMs. I'm sure there's a stock based kernel that comes undervolted which will help greatly with battery life.