Very strange thing happened to me today, went to wake my phone up from lock screen but I pressed the power button and nothing, no wake! I knew I had lots of battery left, but thought maybe it died for some reason, plugged in charger, no response still could not turn on, even holding the button down did no change, nor opening keyboard.
I then removed the battery and re-inserted, booted up and its working fine again
What happened?!
It just happens This happens to my Desire Z every month or so, no matter what rom I use. Recently I changed the radio the latest release, but it won't help I suppose... we'll see.
It seems nobody knows why this happens, many questions are scattered around the the forum about this hang and no answer
sorry for my english
gps make this problem (+ google maps + all google maps based programs)
just turn gps switch off
when you have to use gps, turn it on, use it, turn it off, reboot
and DZ should work fine
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=69305f1c1e5f8c31&hl=en
Not sure what causes this, but it happens occasionally to me too. Maybe once a month or so... Happened earlier today. Hadn't used Google Maps nor do I have any apps that use GPS to track my location.
Happens to me all the time, in average about once every 1-2 days. I put my phone on my desk with screen off, and an hour later it does not respond to the on/off button at all. Sometimes it will reboot when I press the button for over 15 seconds, but most of the time I have to pull the battery, which is a drag since I have a silicone phone protector. I have also noticed that every once in a while, the battery will be fully discharged when it does this. This morning my phone was at 80% battery power, I used it for a minute to check mail, then put it down. 15 Minutes later it was dead, and when I pulled the battery, all I got was a little screen saying 'Please connect charger immediately'. Kinda scary.
I've seen lots of posts about this too on androidforums.com and on MoDaCo. My wife has a Samsung Galaxy Ace on Android 2.2.4 and she has the exact same problem. I haven't found a solution yet, but it seems to be software-related (since it's not limited to Desire-Z), and more specifically Android-related (as it also happened on stock phones without any third-party apps installed). I upgraded to Android 2.3.3 last week and that did not solve it.
Other suspicions I found on other fora:
Correlation between 'phone sleep' and 'WiFi going to sleep' (some people report they benefit from keeping WiFi always off unless they really need it, some people report success keeping WiFi always on; for others - like me - it does nothing or made it worse)
Correlation between phone and SD card (phone does not work properly if the SD card is not the original one, or has not been formatted on the phone)
Correlation between WiFi and SD card (people report reformatting the SD card on their device helped, after they've turned WiFi off)
I have heard people that have had their phone replaced 7 times and all 8 phones did it, some others got the problem solved with one replacement, so it seems not all devices do it.
Check out this thread: http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
A personal observation of mine - and maybe hardware gurus can comment on it - involves the micro-USB connector. Not only is it a pain to connect (compared to mini-USB), but I have noticed that it very easily 'jitters' if there is a slight bend in the cable or if you move the phone while it's connected. The plug will then sit slightly crooked in the connector and the phone will stop charging. And actually, I'm pretty sure that the first time it 'died' on me was when this happened. Would it be possible that this triggers the event? And that the micro-USB is the common cause?
I wonder what radio all these dying phones were running? I had 12.28b.60.140e_26.03.02.26 , now I'm running latest radio, but only a few months will tell if that helped or not...
Update: it's been about a week now since I've disabled GPS and I haven't had a single SOD since! Seems that at least in my case GPS was the culprit, like others on here already suggested. Can anyone else confirm?
Sent from my HTC Vision using XDA App
Grrruk said:
I wonder what radio all these dying phones were running? I had 12.28b.60.140e_26.03.02.26 , now I'm running latest radio, but only a few months will tell if that helped or not...
Click to expand...
Click to collapse
It's not the radio
Sent from my HTC Desire Z using XDA Premium App
Spastic909 said:
It's not the radio
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
+1.... no way it can be
Sent from my HTC Vision using XDA App
I also have random shutdown issue... Not sure it is related to the rom... But it happens when i get out of my house, maybe caused by wifi disconnect issue.. it happen just a few days ago... Now i off the wifi seems ok...
Sent from my HTC Vision using XDA App
SteRo said:
Update: it's been about a week now since I've disabled GPS and I haven't had a single SOD since! Seems that at least in my case GPS was the culprit, like others on here already suggested. Can anyone else confirm?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i have the same since a few weeks
SteRo go plese to the google link in my post (#3) and report gps problem
gandalf15 said:
i have the same since a few weeks
Click to expand...
Click to collapse
my GPS on 24 hours already is ok... but Wifi is a no... i come out of the house this morning... it hangs again... totally black screen and it boot up again when i press the power button so my story tells me never on the wifi when you do not needs it... maybe i'll sent it to HTC SC for checking when i get a new phone... i duno whether i can survive 3~5 working days without it...
try this for a week or too:
have gps allways off when you dont use it.
when you have to use gps, turn it on, then after use turn it off and reboot the phone
and notice how many times you phone hangs in this too weeks
Hello,
i have the same issue with my Desire Z. Many people say its GPS related, i think so, too.
I never hat issues with GPS while navigate. But because the issue is probably caused bei GPS, i have a idea.
I use the wipe efs-data using for GPS from here: http://forum.xda-developers.com/showthread.php?t=1028405
I never had freezes since this. Maybe it helps everyone. Please try and give feedback. Thanks.
Yesterday my Desire Z did exactly that. For the first time. First I thought the battery would be dead, but connection it to the charger didn't even make the orange LED turn on. So only taking out the battery and re-inserting it brought my phone back to life.
I had WiFi turned ON and GPS NOT turned OFF (though no Maps or anything running, so there was no satellite icon in the status bar the last time I had used it).
I will keep watching it, if GPS OFF or an EFS-WIPE might help. But right now it has crashed the first time in about two weeks, so it will be hard for me to tell any improvement before at least a month has passed. ;-)
Tronar
Addendum: after finishing this post, I went downstairs to pick up my phone. And it was dead again! Seems to be happening more often at the moment, than I thought. So I'm going to do an EFS-WIPE now.
Tronar said:
no Maps or anything running
Click to expand...
Click to collapse
google maps is running still in background (also when You try to kill it with taskkiller it will stand up) and use (or try to use) gps for example for location for weather forecast. it can happen that the gps icon cam in notifications bar only a few seconds so You can't see it
it is possible that another apk use (or try to use) gps to get Your location, geotagging photos or so.
just have always gps off (when you haven't to use it and reboot after using) it helps
Bad News, wiping efs-data did not resolve the SOD . Yesterday it happens again.
My gf has the Desire Z and loves the phone - cept for this random issue of her phone freezing on standby. After a bit of screwing around I found out it is definitely related to the GPS module. Whether it's a hardware or memory leak it doesn't matter to her. You can crash her phone anytime by simply using the GPS and any software (she likes google maps / navigation) when she's done whether she turns off the gps or not, makes no difference - within a few hours at the most - it'll crash every time.
The short version, after using your GPS you'll have to restart your phone and you'll never have it crash again.
1moreCyberdude said:
The short version, after using your GPS you'll have to restart your phone and you'll never have it crash again.
Click to expand...
Click to collapse
exactly as i allready wrote in the #3 post
Related
I have I really annoying problem, when I use sense roms (only sense, not AOSP) my phone freezes almost instantly when going to sleep.
This results in the phone not ringing when people call me, and first receiving texts after i reboot the phone.
And the only way to reboot it, is to remove the battery.
If anyone knows what is causing this, please let me know how to fix it, this problem have made me miss many really important calls.
Thanks in advance
i had the same problem with official 2.2 sense rom (don't know with 2.3, i switched yesterday) , but only when i was on a place with bad network.. In big town like Paris no problem, but when i moved to smallest town with bad network i experienced same freeze...
When you hit a button only the button backlight turn on?
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
KasperHermansen said:
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
Click to expand...
Click to collapse
Did you use setcpu?
Usually it happen when you use setcpu and you make screen off profile 128 mhz.
Sent from my HTC Desire using XDA Premium App
Not anymore, because I had the same idea that that could be the problem, but it still freezes
Thanks for the reply
Today it has frozen 4 times.
And every time with massive battery drains, about 15% in a short period of time.
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
Hey guys,
A year after replacing my Desire with an S2, I wanted to set up the old girl again, giving it to a friend of mine as her first smartphone. Well, now, all of a sudden I have several issues.
First of all: it worked absolutely fine before, up and including the day I turned it off for the last time. Back then, I took out the battery, SIM- and SD card and stored it in its box in my desk. It's rooted (no idea how I did it, hell, t'was over a year ago. I do suspect superoneclick though) and was running 2.2 until last night (more on that later).
Put it together, turned it on, sure thing: battery almost dead, so I plugged it in while checking it out. Turned on wifi, set up market so I could install some apps & updates. Well, I was in the middle of downloading some updates, when it told me there's some minor update for 2.2. I had no SD in, which was mandatory for the update, so I decided to turn it off and put in a card (while the app updates where still coming in). Well here's where it all went downhill. After reboot:
- No more wifi ("error", wifi-symbol turnes greyed-out green)
- No more Bluetooth (just won't turn on, no notification whatsoever)
- Calling one of my other phones resulted in the screen turning off, with no way of getting it back on (although the phone kept working fine, left a message on my answering machine with dead screen)
- mobile networks was activated, yet would not show in notification bar/actually connect.
Out of desperation, I then installed the official HTC 2.3.3 Rom, which - hey presto - got rid of the calling screen and mobile networks bugs.
I researched online, read a lot, and I just don't know what's going on. Bluetooth and wifi errors seem to be connected, but there's two kind of threads on that online (and here): People who run custom Roms and have that problem (I am on stock Rom, with no modification other than root) , and people who just had wifi magically turn on again after two weeks. I don't even understand how it can go from totally fine to being this busted. Was it rebooting while updating? All it updated was apps like Flash & Google streetview, after all.
But honestly, without wifi this is as good as a brick to me. I can't figure out what's wrong. I thought it was a hardware issue, because pretty much all communication was shot, but the major update to 2.3.3 sorted out two of the four issues. Well, I really need wifi. If Bluetooth is shot, I can live with that.
Is there anybody who can tell me what's busted and point me towards the next step? I'm absolutely out of ideas and can't seem to find anything that applies on Google and/or xda.
Thanks a bunch for ANY help & suggestion!
Sent from my GT-I9300 using xda premium
And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium
Vortagh said:
And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I think it is your best shot to flash custom recovery such as 4ext and to wipe everything (you can flash it via app so no fastboot required, and it is probably best recovery). By everything, I mean every single partition including sdcard. Then try to install some other rom, for example oxygen and then test the phone. If you need instructions just say.
First of all, thanks for the quick reply!
Yeah, I was thinking about flashing cyanogenmod at one point, but all these bugs put doing that at the end of the to-do list.
Regarding instructions, I'm a bit intimidated about formating the whole thing, simply because I've never used anything like 4ext before. So if you could point me to a good tutorial...
Sent from my GT-I9300 using xda premium
Ok, battery is apparently totally dead, so I have to wait till I can borrow one from a friend.
A question though. You mentioned "format everything". I assume this is, what CWM lists as "format boot/system/data/cache/sdcard/sd-ext"? All of that? Including boot? Just making sure here.
Thanks a bunch!
Well, finally got to ordering a new battery. No change. Phone won't start up, no charge light (although the battery, just like the last one, gets warm).
Guess I'm looking at a major hardware failure and thus a brick
Sent from my GT-I9300 using xda premium
Hi guys
I've been getting fairly decent battery life, however am now connecting my phone to the car daily via bluetooth.
I've noticed some battery drain and after checking the built in battery stats and also better battery stats app, my Bluetooth is not turning off when I'm selecting it.
IE, connected on the drive to work, get to work, disconnected then turned off, but showing as constantly on.
Any ideas what could cause this?
Sent from my HTC One X using xda app-developers app
I have noticed the same thing when viewing battery stats although I never use bluetooth and it's always off.
Sent from my HTC One X using xda premium
Any updates or anyone else having the same problem?
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Earlier this week connected to my boss' car radio for bt aux, this is the first and last time I used bt. Switched it on&off from settings, nothing changed.
SH26CW, running 4.0.4
Might be useful to give the serial no's since it is useful information about the production site and date.
Sent from my HOX via xdapp
thekillingroad said:
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Sent from my HOX via xdapp
Click to expand...
Click to collapse
Same issue here, and same Android version. GSam always reports the same Bluetooth on time as the time unplugged, ie. it's saying that BT has been on all the time, while it's clearly off. I've tried different ways to switch off BT (using widget, using settings, going into Airplane mode and back) but to no avail.
Part of me is suspecting that GSam might be reading the wrong value and falsely reporting it as Bluetooth. But perhaps someone with a different battery monitoring app could check on this and confirm?
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
I faced the same problem? But does that use battery? Actually.the Bluetooth is off.
Sent from my HTC One X using xda app-developers app
neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Sent from my HTC One X using xda premium
Glad I'm not the only one
I do find a reboot fixes it, but I don't want to have to reboot my phone every time I get out the car.
I'll get my serial number when I'm home and see if its the same
Sent from my Nexus 7 using xda app-developers app
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
thekillingroad said:
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
Click to expand...
Click to collapse
Hahaha, that's funny and more towards Apple ideology.
Bluetooth was designed to be efficient. But, if its running then it consuming energy ,and that's something I don't like.
I already checked logcat/kmsg ,but nothing about this Bluetooth issue.
I didn't see anyone on JB came to complain about this, let's see what the offical JB has to offer.
hatemk said:
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Click to expand...
Click to collapse
Try to disable "fastboot", and give it a try.
I am afraid nothings more can be done on stock, other option is to wait for JB and hope it already fixed.
thekillingroad said:
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
Click to expand...
Click to collapse
Safe mode is a mode in Android, that will will disable all the 3rd party installed apps. Similar to safe mode in Windows. After your turned on your phone, just press on the volume key and it will get you there.
Beside that, I never trust customer support, and I never had a good experience with any of them.
The only good thing is about companies offering customer support, is they add job opportunities into the economy.
This problem just crept up on me. I noticed the battery was lower than normal, I checked BBS and it seems like BT never turned off. A reset would solve the problem until I turn BT back on again.
Does anyone know if this has been fixed with 4.1?
sefuwl said:
Does anyone know if this has been fixed with 4.1?
Click to expand...
Click to collapse
It seems so, at least on my One X G Sam is now reporting the correct BT on-time, whereas pre-JB it was continually on, clock ticking even after turning it off.
Sent from my HTC One X using Tapatalk 2
bluetooth
no probs here:good:
I browse xda alot and stumbled up on many weird issues.
Maybe this thread could be an advise-thread like "don't use your Gnex with a Netgear N Wifi AP"
If there is no interest in this thread, just let it die
This is not a thread related to a specific ROM. More for flashaholic people like me who encounter little issues that occur on many different ROMs.
I will list my issues so you get an idea why I started this thread:
- If I connect my Gnex to the charger and use it, almost every time PIE will break and I cant navigate anymore (AOSP-PIE) - I have to reboot my phone.
- If I connect my Gnex to my schools WiFi (CISCO Hardware) I have constant data-download activity and my battery drains in no time
- Sometimes if I connect my Gnex to the charger it behaves like it gets plugged in and out very frequently
- At home, connected to my WiFi (Netgear Router) I have to constantly wake my Gnex to receive new messages (Whatsapp, Mail, etc.)
Maybe we can help each other with tips?
- cheers
I have none of these issues but one. The last one. I thought I was the only one! It happens randomly to me.. I tried to find a fix but havent come across any. Nice idea for a thread it helped me already
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
I have none of these issues but one. The last one. I thought I was the only one! It happens randomly to me.. I tried to find a fix but havent come across any. Nice idea for a thread it helped me already
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Do you own a Netgear router?
This randomly happens to me on a FritzBox too....
Sent from my SM-T310 using xda app-developers app
I have not faced any of these issues. Been changing ROMs ever since the day I bought the phone (A year and a half back).
That charging issue alone cropped up once. But I was able to fix it by pushing the pin in the charging port up by a bit using a safety pin
1. My volume down is busted. Pressing it on normal mode, nothing happens. In Safe Mode, it works though I have to press real hard. Due to this, cant do screenshots anymore.
2. I can connect this gnex to my computer fine but the phone does not detect the charge.
3. Much much more wakelocks when using original battery compared to a china branded replacement battery
azlan96 said:
3. Much much more wakelocks when using original battery compared to a china branded replacement battery
Click to expand...
Click to collapse
well, that's interesting! I'm planning a replacement because my phone is two years old and so is the battery.
While using certain kernels with Trickster Mod and "set on boot" option, I get a reboot if the screen is off when Trickster applies it's settings. Took me a long time to figure this out. If the screen is on when Trickster applies kernel settings it works just fine. Never could figure out why this happens, but I use tasker to keep the screen on for 2 minutes after boot to prevent it.