Database Users

Incredible 2

With my DInc getting the 5 vibrations and green LED of death, I'm in the market to get a new phone soon. Hopefully, I can replace it with the Inc2.
Anyone else here thinking of a switch? I could care less about 4G and dual core anything, I'm just in need of a new phone and the Inc2 meets all my wants and needs.
-CM7 ADR6300

I would get these every now and then with CM7 when I would reboot. traditionally a battery pull would resolve the issue.

I've never heard of the 5 vibrations and green LED of death. I'm surprised.
Sent from my ADR6300 using......blah blah you get the idea.

I get it multiple times every day now. I can't stand it.
-CM7 ADR6300

You must be doing something wrong if its in debug mode. What's your hboot and radio? What ROM?
Sent from my ADR6300 using XDA App

i may have had this vibration thing. pull your battery,, worked for me.

Smokeey said:
You must be doing something wrong if its in debug mode. What's your hboot and radio? What ROM?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
.92, 9.01, CM7.
BTW, debug mode is when it's off and you hold power + volume up.
The 5 vibrates + green LED is an error.
*EDIT*
Also, battery pulls work ~40% of the time. Usually it does it again and again.

dpwhitty11 said:
.92, 9.01, CM7.
BTW, debug mode is when it's off and you hold power + volume up.
The 5 vibrates + green LED is an error.
*EDIT*
Also, battery pulls work ~40% of the time. Usually it does it again and again.
Click to expand...
Click to collapse
RUU and re-root. Should fix the problem.
FYI. Volume up+Power is Qualcomm diagnostics. Not debug mode.
via Evervolv GB

AdhvanIt said:
RUU and re-root. Should fix the problem.
FYI. Volume up+Power is Qualcomm diagnostics. Not debug mode.
via Evervolv GB
Click to expand...
Click to collapse
If its off its the diagnostic mode
If u do the volume up + power during the boot animation it will moot into safe mode
Sent from my ADR6300 using XDA Premium App

Back to the Dinc2... I just picked up my Incredible a few weeks ago knowing that the new one would come out in the near future. Why? Well, besides getting sick of my previous phone (blackberry) and the killer deal Verizon gave me (free phone and no activation fee), I just didn't think the new version was that much of an upgrade.
Is there anything the new phone can do that the "first gen" can't?

Front facing camera, larger stock battery, next-gen snapdragon, larger screen in the same-ish form factor, rotating soft buttons, some others.
-CM7 ADR6300

IMPORTANT!! Regarding VisionKernel 1.2

This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
NOTE: It appears that MANY users are suffering from this issue and haven't realized it yet (because they haven't yet shut their phone down). If you reboot to flash another kernel, please know you may suffer from this problem so do so at your own risk. This is extremely unfortunate as this means there's no way to prevent the problem from getting worse.

ok..hmmm..so I saw this thread and decided to power off my phone and go back to genocide since visionkernal has been acting weird here and there anyways..so i power off my phone and now it doesn't turn on lol
DO NOT PANIC AND POWER OFF/REBOOT THE PHONE OR YOU MIGHT BRICK!!! WAIT TILL A SAFE METHOD TO TURN YOUR PHONE OFF IS CONFIRMED!!!
If YOU ALREADY BRICKED, POST IN HERE:
http://forum.xda-developers.com/showthread.php?t=1043240
--
SO FAR THE FOLLOWING METHODS WERE CONFIRMED TO BRICK:
Power down/Reboot via menu
Battery pull
BRICK DOES NOT HAPPEN FOR EVERYONE, AND MAY HAPPEN AFTER TIME BUT IF IT DOES HAPPEN TO YOU ITS A PERMA BRICK

I work for sprint, If you don't have insurance and the screen is cracked take it to a tech center and they will fix it for $35. If it is a larger crack than 2 inches they might give you some hassle just haggle with them or go to a different store cause my store does it no problem
Sent from my harmonious Bonsai 4.0.1 tree

trobertson said:
This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
Click to expand...
Click to collapse
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App

Custodian said:
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
For me what I noticed was phone randomly shut off at night even though it was stable all day long...
The battery was good...like lost 3-5% in 7 hours of idling and stuff..then when I turned it on after it crashed it instantly lost 50% battery.

You can't get your phone replaced for problems unrelated to cracked screens???
I was actually hoping to brick my phone some day

Dude, WTF!
My phone has acs rom 1.1 and visionkernel 1.2. It started hanging on me so I held down the power button and pressed reboot. Now it wont turn on, and it won't charge either! WTF I AM SO ANGRY RIGHT NOW. IT WAS JUST FINE.

Finally I'm not alone.. I had this issue as well and fixed it by pulling my sd card and battery out a few times and then pressing the power button. After I finally got the phone back on I had to odin back to eclair. Hope this helps...
Note: I also formatted my sdcard. Because just pulling the battery didn't work. So I suspect something on the sdcard was making the phone not turn on..

Hmm..,maybe powering off is the cause of the issue..hmm..I think its safer maybe to crash the phone rather then turning it off/rebooting it then reflash another kernal..

I had an issue flashing 1.2 also. Got stuck at a boot loop after first installing, had to do a battery pull that corrupted everything. None of my back up works so I had to start fresh with eb13 then flash the ec05 modem and then flash my backup after all of that. Glad I had a back up but still a bit of run around having to odin first.

I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.

cerchiara said:
I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.
Click to expand...
Click to collapse
which kernel? also I tried with taking out the sd card altogether and putting in a new one..didn't work....

it has been working fine for me and I only used Voltage and overclocked only to 1300. What applications are you guys using to set your speeds/governor?

Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing

To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?

quik99 said:
Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing
Click to expand...
Click to collapse
Well bricks happen..its nothing new..mostly when experimenting with things...
What other kernel was causing perma bricks?
fhurricane said:
To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?
Click to expand...
Click to collapse
nope, my phone didnt charge, tried it already

I think I just joined
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.

Light does not turn on when plugged in, tried two different full batteries, can't even turn it on to get to recovery or download mode.

hussmanne said:
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.
Click to expand...
Click to collapse
you did "power off" or "reboot" via menu right?
if so can op update the OP telling people NOT to power off their phones! cause thsi thread make get more people to brick their phones as is...it made me break mine lol

I think I chose power off from menu, I remember the phone vibrating faster than usual before turning off. Twas its last breathe.

***For those who are experiencing freeze ups***

Hello people, I thought I would inform you all of a much better and effective method to deal with your phone freezing. Many of us are using custom kernels such as nemesis2all's OTB or imnuts peanut butter jelly time in which have a tendency to freeze our phones due to the overclocking/undervolting. Or, we are on JT's new CM7 mtd or Andmer's GB MIUI and our screens will turn off and nothing that we do will turn them back on. The natural reaction to this occurrence is to take the back off the phone and pull the battery out. But, this is not good for it to be abruptly pulled in the midst of supplying power to your phone. Not to mention the severe battery drain that comes along with doing this, as I'm sure many of you have already noticed to be the case. No matter what rom/kernel you are on and no matter how frozen your phone is, if you simply hold both the volume up and volume down buttons and the power button at the same time for about 10 seconds, your phone will do a hard reboot. Problem solved without doing harm or damage to your phone and without excessive battery drain. This method even works for CM7 MTD/GB MIUI MTD. This is not the same thing as the three finger method that you are warned not to do with these roms. This method will lead to overall better battery life and phone life. Not to mention, a lot less frustration.

I think just vol UP + power works, but either way.. it's a useful trick to know!

And especially helpful if you have a case on
Sent from my SCH-I500 using XDA Premium App

Good to know. I broke my case by taking it off and on so many times. It's still useable but this will prevent further damage, and save me some time.
Sent from my SCH-I500 using Tapatalk

elarson006 said:
I think just vol UP + power works, but either way.. it's a useful trick to know!
Click to expand...
Click to collapse
+1. This is what I use. Just had to do it this morning as a matter of fact.

elarson006 said:
I think just vol UP + power works, but either way.. it's a useful trick to know!
Click to expand...
Click to collapse
Indeed. I never do battery pulls personally.

verizon techs have had me do battery pulls a couple different times lol.

droidstyle said:
verizon techs have had me do battery pulls a couple different times lol.
Click to expand...
Click to collapse
Yea, but not while the phone is on and in a frozen state with a steady stream of battery power being supplied to it, I assume. That is very different.
Sent from my SCH-I500 using XDA Premium App

kidserious said:
Yea, but not while the phone is on and in a frozen state with a steady stream of battery power being supplied to it, I assume. That is very different.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Power on but not frozen... but I agree its not good to pull battery in frozen state... volume up and power button is what I do in that situation. My SF has only froze two times and that was from overclocking... not very stable over 1200 on the stock rom. Srry hope my last post did not offend, I meant as verizon was dumb for having me pull the battery with power on!

droidstyle said:
Power on but not frozen... but I agree its not good to pull battery in frozen state... volume up and power button is what I do in that situation. My SF has only froze two times and that was from overclocking... not very stable over 1200 on the stock rom. Srry hope my last post did not offend, I meant as verizon was dumb for having me pull the battery with power on!
Click to expand...
Click to collapse
No, post was not offensive nor was it was taken that way. Sorry if I gave the wrong impression.

landshark68 said:
+1. This is what I use. Just had to do it this morning as a matter of fact.
Click to expand...
Click to collapse
It's what I use as well, power+both volume buttons does nothing for me, I think technically power+volume up is a soft reboot, but, it works.

I will use this next time... My phone froze up this morning. I thought I was going to have to pull the battery and just as I was tapping the battery out of the phone I saw the bootlogo. When I put the battery back in my /data was gone. Phone would boot, but there was no data partition. It was toast.
Had to Odin back to stock and start all over. My last Titanium Backup is from more than a month ago. I have a Super Manager backup from ~ a week ago. Will give it a shot.

Great its frozen

Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.

Kermode said:
Running fine for a day, then suddenly when i looked at the screen it was at the "Asus" screen (with the logo and spinny thing below) - i touched the screen and it froze.
And now its frozen.
And I had just charged it...grrr - do i really have to wait 12 hours or however much it takes before the battery is depleted.
I wonder if there is a way to reset it.
Click to expand...
Click to collapse
Hold the power button down.
Sent from my Galaxy Nexus using XDA App

Happened to several guys.
Did you try to press and hold power for ten or more seconds? It should power off and you should be able to power it on again.

this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.

fone_fanatic said:
this is happened to me 3 times so far.
Hold the power button to power off and reboot.
For mine after it boots it'll run ok for a minute or so, then run horribly slow until the launcher crashes. after the launcher starts back up it'd be ok.
Did you hard reset before the OTA? Where you stock, stock rooted, cwm flashed? Just trying to get more info.
Click to expand...
Click to collapse
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App

Just an idea but what if you use something like SetCPU and up the lower frequency. Had this issue on a kanged ICS rom for my phone. It wasn't the deep sleep that was the problem but the lowest frequency was too low to re-initialize the apps that were cached once you woke it up.
I did a full complete wipe and updated from .13 to ICS and am not going to jinx myself by saying what I am implying. If you know what I mean.

Interesting, and I do agree that there are too many threads, since I am trying to get some idea of how common this is. I think I was the original poster on this, but in any case in my particular situation I tried holding the power button down, resetting it through the reset hole, and holding the power button in while pressing the volume button down (this did give me the option of reformatting which I tried) but in every case it simply flashed the eedpad screen. The battery finally appears to have died and I'm trying to recharge it now, but so far it is now completely dead. All of this happened after it went into deep sleep. This tablet is 100% original, never been rooted or tampered with in any way so, unless this is a coincidence or a combo of ICS and one of the apps I have in it, I expect this to become a very common occurence. Anyway, I'll let it charge for a bit and see what happens. I already have an RMA (the service person didn't seem too surprised and didn't really try much trouble shooting - when I asked if he had heard of this before he kind of said I wasn't the first) so I'm sending it back to Asus on Monday so that when I get it back I can sell it, but I'm just wondering what percentage of people are having this problem. Heck, if it's even just 5% Asus is going to have a major expense on its hand.

I had the dreaded Asus logo freeze twice now, since the ics update. Both times when I wasn't using the tablet.
Sent from my Galaxy Nexus using Tapatalk

Mine has frozen 2x already since the ics update. I performed a factory reset before and after the update.
Screen just goes black/blank and would have to hold the power button for 10secs.
Sent from my Transformer TF101 using Tapatalk

Hey thanks, I thought I had pressed power down for long enough - but apparently not.
I was on normal HC and just accepted the update when it prompted me for it.
But if a lot of people are seeing this i guess Asus made a little blunder in this version.

I just came in after leaving my Transformer asleep for about three to four hours, and found the asus logo flashing on for a few seconds and then off, repeating over and over. Had to do a reset with power and vol down to get it to reboot. Seems OK for now except it really drained the battery.
I guess there will be a few ICS bugs to work out.

jparity said:
We are having way too many threads for the same issue...
Mine still experiences the problem after a factory reset.
As everyone mentioned, holding down the power button fix it temporarily.
Someone else reported that you can avoid the random reboot problem by disabling deep sleep using no sleep widget, although it's a crude walkaround.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App

msaraiva said:
About the "No Sleep" widget, that was me. Well, this seems to be a widespread issue. Asus should take the update back and stop offering OTA...this is a pretty big issue.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Well asus is good about providing prompt follow up updates so I wouldn't be surprised if we start getting bugfix updates in the coming weeks.

Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App

It's next to the hdmi port.
jparity said:
Yea seems like the TF only goes crazy when it's in sleep/not being used.
Mine is not rooted so I don't really want to go through the trouble changing processor frequency.
Where is the reset hole btw?...
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse

r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium

eminembdg said:
Isn't that the mic? I don't believe that's a reset button. I could be wrong though
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
There isn't holding the power button for 15 seconds resets it.
Sent from my Transformer TF101 using Tapatalk

r_nt said:
It's next to the hdmi port.
Click to expand...
Click to collapse
I thought it's the mic too... Does your voice record still work after you "reset" your TF?...
Edit: Saw the dreaded Asus loading screen again when I came back from dinner... 3rd time today... It's getting on my nerves a bit now. Such a pity that the TF is perfect besides this issue... I don't care if it reboots every hour or so, as long as it doesn't hang and depletes the battery.

Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.

fone_fanatic said:
Just to clarify, and so others don't break their microphone,THERE IS NO RESET HOLE! if your device is frozen, hold the power button to reset.
Are we certain its the deep sleep causing this?
Didn't happen to me this morning. I stopped using it around midnight and woke up fine the next day.
Click to expand...
Click to collapse
How do you it didn't happen? It doesn't get stuck at the ASUS logo for me, it simply reboots. Try leaving something open, like a browser window, turn off the screen and come back sometime later. If it's back to the homescreen and there are no recent apps, then it rebooted.
I don't know if it is the deep sleep that is causing it. All i know is that the bug is only triggered while sleeping. Every logcat i get stops at an AlarmManager event, before the reboot.
Sent from my Transformer TF101 using XDA Premium HD app

Phone shuts off and freezes

2 days ago my phone (for the first time) just shut off and wouldn't turn back on even if I held the power button. It turned back on after plugging it into an outlet and holding the power button. The same thing happened today.
I'm using the stock battery (I just bought the Anker battery because I figure it's the battery causing issues) and I'm on Scott's CleanROM. I've had the phone since July (brand new) and haven't had any problems since.

How long have you been on this rom/release version? Got a new kernel or try any new kernel settings? Maybe try using the new battery for a few days to see if that's the problem?

xBeerdroiDx said:
How long have you been on this rom/release version? Got a new kernel or try any new kernel settings? Maybe try using the new battery for a few days to see if that's the problem?
Click to expand...
Click to collapse
+1. Sound kernel related. Did you mess with any voltage settings?
Sent from my SGH-I337 using XDA Premium HD app

AT&T - S4 - CleanROM 1.5 is the exact ROM I've had since I installed it. I'm not too sure what "kernal" means so I didn't change any voltage settings or anything like that.

Br4nd3n said:
+1. Sound kernel related. Did you mess with any voltage settings?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
iTech02 said:
AT&T - S4 - CleanROM 1.5 is the exact ROM I've had since I installed it. I'm not too sure what "kernal" means so I didn't change any voltage settings or anything like that.
Click to expand...
Click to collapse
OP, test that secondary battery out and see if that's your problem. keep us posted.
Br4nd3n, your device configuration is almost identical to mine. cheers.

Great setup isn't it? Cheers!
Sent from my SGH-I337 using XDA Premium HD app

iTech02 said:
2 days ago my phone (for the first time) just shut off and wouldn't turn back on even if I held the power button. It turned back on after plugging it into an outlet and holding the power button. The same thing happened today.
I'm using the stock battery (I just bought the Anker battery because I figure it's the battery causing issues) and I'm on Scott's CleanROM. I've had the phone since July (brand new) and haven't had any problems since.
Click to expand...
Click to collapse
I had a problem like this too, running a different ROM, CM 10.1, a nightly - I removed my battery and fully charged it in a stand-alone charger and returned it to my device and haven't had an issue since.

FourPointedFreak said:
I had a problem like this too, running a different ROM, CM 10.1, a nightly - I removed my battery and fully charged it in a stand-alone charger and returned it to my device and haven't had an issue since.
Click to expand...
Click to collapse
I think I just got unlucky with a defective OEM battery. The new battery comes in tomorrow so I'll stick it in there and let you guys know what happens.
Ironically, my phone has this issue when the battery discharges to around ~40%. It's fully charged right now so I want to test that theory as well.

iTech02 said:
I think I just got unlucky with a defective OEM battery. The new battery comes in tomorrow so I'll stick it in there and let you guys know what happens.
Ironically, my phone has this issue when the battery discharges to around ~40%. It's fully charged right now so I want to test that theory as well.
Click to expand...
Click to collapse
Well whatever works for ya. I'd hate to be that one case of a bad battery. Let us know.

So that didn't fix anything since I got the same issue again today with the Anker battery. I have a feeling it's the "hover your hand over the phone" gesture since this happens when the phone is in my pocket pressing against my wallet.