Sleep of Death while charging [Solved] - Nexus 4 Themes and Apps

Hi all, there is a small app I wrote that will solve the problem with the Nexus 4 dying while connected to the charger overnight. It's completely free (no ads also) and can be downloaded from Google's Play Store. No ROOT required, works on completely stock phones. I tried it on my phone and haven't had a SoD for 5 nights (I used to have it almost every night). Also a colleague of mine used to suffer from this and the app solved his problem too.
The app basically puts a wakelock on the phone that will allow for the backlight to go off, so the screen doesn't age, but will prevent the CPU from sleeping while charging. Once external power is disconnected, the wakelock is released and so the app does NOT consume any battery (while in automatic mode).
So if you happen to have the same issue, feel free to try the app and save yourself the troubles of returning otherwise a perfectly good phone.
P.S. I have just uploaded the app, so if it's not yet visible for your country, please try again in a few hours.
Update: Now the application checks if the power is connected when the device is powered on, because otherwise the wakelock was not acquired when powering on with charger connected. Unfortunately this requires a new permission ("RECEIVE_BOOT_COMPLETED") and the application to be opened after updating for the receiver to be registered by the system. Also I added a notification in the status bar while the application is running. You have to enable it in the settings if you want it displayed.

will test it an report back

I don't understand why anybody suffering this wouldn't just RMA their phones?

FormerSlacker said:
I don't understand why anybody suffering this wouldn't just RMA their phones?
Click to expand...
Click to collapse
+1. It's a hardware issue.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
tkolev said:
Hi all, there is a small app I wrote that will solve the problem with the Nexus 4 dying while connected to the charger overnight. It's completely free (no ads also) and can be downloaded from Google's Play Store. No ROOT required, works on completely stock phones. I tried it on my phone and haven't had a SoD for 5 nights (I used to have it almost every night). Also a colleague of mine used to suffer from this and the app solved his problem too.
The app basically puts a wakelock on the phone that will allow for the backlight to go off, so the screen doesn't age, but will prevent the CPU from sleeping while charging. Once external power is disconnected, the wakelock is released and so the app does NOT consume any battery (while in automatic mode).
So if you happen to have the same issue, feel free to try the app and save yourself the troubles of returning otherwise a perfectly good phone.
P.S. I have just uploaded the app, so if it's not yet visible for your country, please try again in a few hours.
Click to expand...
Click to collapse
Regardless your are AWESOME. Thanks for doing something about it rather than whining and complaining for a resolution from fellow members.

FormerSlacker said:
I don't understand why anybody suffering this wouldn't just RMA their phones?
Click to expand...
Click to collapse
wilsonlam97 said:
+1. It's a hardware issue.
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
Regardless your are AWESOME. Thanks for doing something about it rather than whining and complaining for a resolution from fellow members.
Click to expand...
Click to collapse
its NOT a hardware issue, software related. was VERY common on android 4.1.2, especially on the galaxy nexus. it happened to all the different nexus, nut the gnex suffered the most. 4.2.2 fixed the issue, and google did say it was a real issue. it still happens, but much rarer than before. btw, there are a few apps that bring it on for the nexus 4, one known app to bring on sod is ezekeels experience app. chew on that.

FormerSlacker said:
I don't understand why anybody suffering this wouldn't just RMA their phones?
Click to expand...
Click to collapse
Because some of us that live in countries where Google doesn't sell devices and because it's easier to solve it rather than returning the device.
Sent from my Nexus 4 using xda premium

So how does this app prevent sod?

Underground_XI said:
So how does this app prevent sod?
Click to expand...
Click to collapse
it creates a wakelock preventing the device from (deep)sleeping. its not really a solution, is just a work around for the problem.
Permissions
THIS APPLICATION HAS ACCESS TO THE FOLLOWING:
SYSTEM TOOLS
PREVENT TABLET FROM SLEEPING PREVENT PHONE FROM SLEEPING
Allows the app to prevent the tablet from going to sleep. Allows the app to prevent the phone from going to sleep.
Click to expand...
Click to collapse

simms22 said:
it creates a wakelock preventing the device from (deep)sleeping. its not really a solution, is just a work around for the problem.
Click to expand...
Click to collapse
Exactly. But it listens for charger connected / disconnected to acquire / release the wakelock and thus consumes energy only while the device is connected to an external power source (you can see it starting and stopping in the manage applications settings menu). True, that's not a "solution" (that's Google's job), but it doesn't interfere with the normal device operation and does not require any user interaction other than enabling it on install, so until there is a real solution it's the best I can come up with .
Sent from my Nexus 4 using xda premium

simms22 said:
it creates a wakelock preventing the device from (deep)sleeping. its not really a solution, is just a work around for the problem.
Click to expand...
Click to collapse
That's what i thought. Fine then, as long as the wakelocks do not continue when phone is not being charged.

wilsonlam97 said:
+1. It's a hardware issue.
Click to expand...
Click to collapse
Way to show your technical prowess :laugh: Anyone that RMA's a phone for this issue ought to be shot in the knees, and given a Galaxy S1 to replace their Nexus, as they don't deserve to own one.
It's a software issue... on a DEVELOPER PHONE... or did everyone miss the fact that the Nexus line of products is supposed to be for devs' to buy and use to test new software/hardware configurations on.
edit---> Oh, and +1 to OP, good job creating a workaround!

I have the same problem.... I test this app and hope functionally .... I
Inviato dal mio Nexus 4 con Tapatalk 2

ImWarped said:
Way to show your technical prowess :laugh: Anyone that RMA's a phone for this issue ought to be shot in the knees, and given a Galaxy S1 to replace their Nexus, as they don't deserve to own one.
It's a software issue... on a DEVELOPER PHONE... or did everyone miss the fact that the Nexus line of products is supposed to be for devs' to buy and use to test new software/hardware configurations on.
edit---> Oh, and +1 to OP, good job creating a workaround!
Click to expand...
Click to collapse
Definitely software. My problems started happening after 4.2.2 updates. I wish I paid attention to what kernel version it began on.
Anyway, I haven't had an issue since using this app. So about two days.
Thanks a million tkolev! I can use this as my alarm again.
Sent from my Nexus 4 using Tapatalk 2

billydroid said:
Definitely software. My problems started happening after 4.2.2 updates. I wish I paid attention to what kernel version it began on.
Anyway, I haven't had an issue since using this app. So about two days.
Thanks a million tkolev! I can use this as my alarm again.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm glad it helps you too!
May I ask anyone that tries it to go back to the Play Store in a few days and rate the app to increase it's visibility and possibly help others to stumble upon it while searching for a solution. Thanks!
Sent from my Nexus 4 using xda premium

tkolev said:
I'm glad it helps you too!
May I ask anyone that tries it to go back to the Play Store in a few days and rate the app to increase it's visibility and possibly help others to stumble upon it while searching for a solution. Thanks!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Sure thing, its the least one could do .
Also could you explain, to the best of your knowledge, why the sod's occur when in sleep mode?

billydroid said:
Sure thing, its the least one could do .
Also could you explain, to the best of your knowledge, why the sod's occur when in sleep mode?
Click to expand...
Click to collapse
I have no idea. My first thought was to create a Daydream as those seemed to help too, but I could not turn the display off (you can only control the brightness but that would still keep the backlight on). The strange thing is that while "dead" something in the system is still working because an application that shows the battery percentage by changing the color of the notification LED was still working. Even after I had unplugged the phone. I know that it might sound like a heresy here, but I don't want to use custom ROMs (I use my Nexus for development and keeping it stock for compatibility is a must), so trying different kernels and ROMs was a no-go.
Sent from my Nexus 4 using xda premium

tkolev said:
I have no idea. My first thought was to create a Daydream as those seemed to help too, but I could not turn the display off (you can only control the brightness but that would still keep the backlight on). The strange thing is that while "dead" something in the system is still working because an application that shows the battery percentage by changing the color of the notification LED was still working. Even after I had unplugged the phone. I know that it might sound like a heresy here, but I don't want to use custom ROMs (I use my Nexus for development and keeping it stock for compatibility is a must), so trying different kernels and ROMs was a no-go.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So this was happening to you while completely stock, minus root?
Does this always happen you? Even while on 4.2 .1?

billydroid said:
So this was happening to you while completely stock, minus root?
Does this always happen you? Even while on 4.2 .1?
Click to expand...
Click to collapse
I only recently got my hands on the Nexus 4. I live in Bulgaria and Google does not sell devices here, so I had to either wait for any of my colleagues to go to the US on a business trip while the device was in stock or pay more than 150% to buy one from a local reseller. I've been on 4.2.2 since day one. No custom ROMs, no root, not even unlocked boot loader.
Sent from my Nexus 4 using xda premium

tkolev said:
I only recently got my hands on the Nexus 4. I live in Bulgaria and Google does not sell devices here, so I had to either wait for any of my colleagues to go to the US on a business trip while the device was in stock or pay more than 150% to buy one from a local reseller. I've been on 4.2.2 since day one. No custom ROMs, no root, not even unlocked boot loader.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I see. The reason I'm asking is it didn't start happening to me until 4.2.2, but not sure what kernel revision it started on.
Just trying to establish a timeline.
Still the app is a life saver

ImWarped said:
Way to show your technical prowess :laugh: Anyone that RMA's a phone for this issue ought to be shot in the knees, and given a Galaxy S1 to replace their Nexus, as they don't deserve to own one.
It's a software issue... on a DEVELOPER PHONE... or did everyone miss the fact that the Nexus line of products is supposed to be for devs' to buy and use to test new software/hardware configurations on.
edit---> Oh, and +1 to OP, good job creating a workaround!
Click to expand...
Click to collapse
With all due respect (honestly) and not sarcastically- if this was the case wouldn't the phone come rooted already and in developer mode? I am pretty sure it is being marketed as the flagship "pure google" phone and not only for developers. That said it is easily understandable as to why this is a frustrating issue.
To the OP: A million thanks! I hope this app does the trick- regardless thanks for your efforts and making this community what it is.

Related

[Q] Extremely Slow Screen Wake Up Delay?

Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Just to make things perfectly clear, here is a video of the delay time:
http://www.youtube.com/watch?v=vqJc_nYuwac
*older update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.
mine is doing this too.. are you using a SD Card wallpaper? I am. not sure if thats affecting things.
I have not noticed any delays on mine.
I have noticed this as well. I'm using a stock wallpaper.
Sent from my SPH-D710 using xda premium
thedeadletters said:
Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.
Click to expand...
Click to collapse
You shouldn't do that, it will be detrimental to your battery. Deep sleep mode means that the processor is technically off, provided the phone doesn't have any tasks to run while the screen is off.
Its perfectly natural for your phone to wake up immediately when plugged in, because that's how samsung designed the galaxy's. No need to deep sleep when the phone's getting a charge.
By restricting your phone from sleeping (affectionately referred to as wake lock),your forcing your processor to run for nothing, most likely at 200mhz. When it's all said and done, I estimate you'll end up shaving off about 5 hours of battery life. Not worth it to me, just learn to deal with 1 sec it takes to wake up the phone.
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium
squshy 7 said:
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.
daneurysm said:
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.
Click to expand...
Click to collapse
Lol, I'm actually crying a little from laughter. The scenario you described was exactly what went through my head when I wrote that
EDIT: to the OP, this is all in jest, no offense meant. But seriously, don't wake lock your phone.
Sent from my SPH-D700 using xda premium
I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.
Don't wakelock the phone.
Voluntarily wake locking a phone? Haven't heard that before lol
Sent from my PC36100 using xda premium
Journeyjeans said:
I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.
Click to expand...
Click to collapse
Thanks for all the responses. My past Android phones (Evo and Evo 3D) didn't have any delay whatsoever, which is the origin of the original post. The power of the Galaxy S2 phones is pretty much legendary, which is why I'm surprised about this power saving feature. Reviews boast quick boot times, but I would argue that a regular wake time is much more useful and realistic to have. I do understand the basic premise that a powerful phone consumes more battery, but that didn't make any other dual core phone I've seen require this precaution.
Therefore, why is it that others forego this feature if it ultimately saves so much battery that Samsung has made it a default feature on their latest phones?
Updated the OP with a video. Please view and tell me if this is the norm.
I watched the video, mine is not that slow delay.
justwonder said:
I watched the video, mine is not that slow delay.
Click to expand...
Click to collapse
+1 return it
Sent from my SPH-D710 using XDA App
I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response
sling said:
I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response
Click to expand...
Click to collapse
Funny how mine has all my apps on it... (over 40) and a **** load of music... And for the life of me I cant get it go lag like that.... I had a refurbished evo 3d that did that... I called sprint.after factory reset and.a few battery pulls... Id just return it.
roms dont fix all bugs let alone one random wake lag problem and the op may have to deal with it as most of us dont have lag like that...
@op if you got it from a store id bring it in.... if a rep says its suppose to do that.... Tell them your older android phone didnt do it... Then ask to speak to a manager
Sent from my SPH-D710 using XDA App
Yeah... I had a feeling it was worse than it should have been. Though it's true a custom ROM could fix it, it would probably implement a fix similar to Soft Locker (which is obviously shunned for its battery draining ability). Also, I'd much rather have a device in proper working order to begin with. The Best Buy I got it from only had 2 on launch day, so here's hoping I find one that has it in stock.
Thanks for all the replies.
My delay is similar to the video. How does everyone else compare after seeing the video?
Sent from my SPH-D710 using xda premium
I had the same issue. Move the pic from ur sd card to ur internal. Open in using myfiles and set as lockscreen
Sent from my SPH-D710 using xda premium
Thanks. Stupid question but how do I move it. I only know how using root explorer on a rooted phone.
Sent from my SPH-D710 using xda premium

Sleep of death?

Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk
I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.
Evostance said:
Anyone having issues with the phone going to sleep and not waking up? Happened last night and I had to remove the battery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.
mskip said:
Most likely something that you have installed on your phone isnt liking ICS. Hard to narrow down if you have alot of apps installed.
I have had mine for 6 days now and not had a single Sleep of Death and I havent seen too many comments about it so I dont think its a problem with ICS directly.
Mark.
Click to expand...
Click to collapse
Good point.
Wonder what app it is
Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium
SweetPAIN225 said:
Happened to me too! My phone was ultra hot too! I had charged it over night with my computer. can anyone who had this issue confirm it was through computer charging?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off
Thanks! I made a wrong assumption!
Sent from my Galaxy Nexus using xda premium
Evostance said:
Nah was via wall power.
Wonder if its SetCPU stalling my phone as ive got it to drop the CPU speed right down when screen is off
Click to expand...
Click to collapse
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Exactly, it is way way too likely that turning your CPU down will result in 'Sleep of death'
matt2053 said:
Jeez man you think you might wanna test that out before you post that there's an issue with your phone?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well its still worth noting. SetCPU never did this on my DHD
I had exactly the same thing last night, I even made my own thread
http://forum.xda-developers.com/showthread.php?t=1360847&page=2
I even wrote a simple app for logging the battery temperature and time, so I'll leave it on next night and I'll see what happens. Because I'm pretty sure my phone switched off due to overheating, as it was really,really hot in the morning, after I switched it on the battery was at 46C.
I'm afraid I can confirm that I have experienced the same "sleep of death" problem twice now. I can't remember what I was doing the first time, but the second time I was only browsing and I know I didn't have any apps installed because I had previously reset my phone. I've only had the phone for two days now and if it does it again I might have to send it back.
I expected a glitch or two, but with the volume bug and other annoying things like the lack of flash and poor camera quality, I'm beginning to regret my purchase. Although I love the ice cream sandwich experience, I'm now thinking of getting the Galaxy Note instead, and waiting for ICS to arrive on that next year. At least then I will be able to watch iPlayer in the meantime.
Mines done it about 4 times. Pre installed Movie maker seems to induce it.
Rawkode said:
I've had this twice now. Both times after using Spotify, probably purely coincidence though. Battery pull and everything is OK.
Click to expand...
Click to collapse
Had a sleep of death for the first time yesterday - the only "different" thing I did during the day was use spotify so there maybe something in that!
Same again last night, woke up this morning and phone was on but wouldn't wake. Notification light was on solid. Was plugged in at wall all night, didn't seem too warm when I held it.
Time to start debugging I guess
I've had this issue twice too.
I do not have spotify installed, and the phone was NOT hot at all. Not even warm!
I was just in gmail, sent a mail, then pressed the home button, and black.... gone.
Had to pull battery.
Thinking of having phone replaced by Handtec. I know this is probably a software glitch, but the volume bug, and the fact my unit was one that handtec had "tested" etc, I might just ask for a brand new one from the new flashed batch due next week.
Wtf! Just how wide spread is this??? Seems like too many people are having this issue.
Phone hasn't even arrived yet and I'm already starting to question my purchase.
1 more bug and im cancelling my order !
Well, it's the first device with ICS so I expect there will be a few bugs in the future which will need to be fixed. That's the reason why I'll go for the Nexus ... it's a nice piece of hardware but even more important is that it will be the device which gets the fixes first.
Did anyone check to see if you've had an OTA for the volume ghost fix and this problem has spawned instead? Seems like a fairly new problem if you have followed the forum.
Sent from my X10i using xda premium

Galaxy Nexus - flawed by bad NAND!!! \data partition corruption issue

Issue: \data partititon become corrupt for no obvious reason.
Manifests itself through: Freezes followed eventually by (endless) reboots
When: Randomly when you install new apps (may be every day as it can happen only every other week/month), or setting up apps (like Twitter, mail, etc)
Temporary solution: Re-flash Samsung FW but lose ALL YOUR DATA. Attention: CWM restore will not fix the problem!
---- Here goes a link to the fabulous mskip's tutorial, you will find here everything you need to get it back up temporarily
I experienced this in 401, 402, 403 and 404, some were expecting better data integrity in 404... I confirm this is not the case
I would not go as far as saying that this is 100% the reason, but it looks like the NAND quality is craaaaaap! There is no external SD card, Android should be able to do a perfect job now at handling info and preserving quality of data.
I will contact Samsung and ask for a refund (if at all possible)... Disgusting thing to put such a piece of s''t on the market without proper testing and call it "flagship/pure Google experience". This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Any advice, I am inetersted, have tried pretty much everything so far and did not solve the problem...
DO YOU HAVE THE SAME ISSUE? Let your voice heard...
DO YOU HAVE THE SAME ISSUE?
Click to expand...
Click to collapse
No. Could it be possible you're overreacting?
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Agree as well ..seems more like rubbish
Sent from my Galaxy Nexus using xda premium
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
KWKSLVR said:
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
Click to expand...
Click to collapse
Right While i'm catching my breath, found another thread pointing to the same issue IMHO (didn't not see it initially):
http://forum.xda-developers.com/showthread.php?t=1490815
Attempting to contact Samsung already...
vulpy said:
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Click to expand...
Click to collapse
Your first post came across as a hysterical rant - this is the first I've heard of the problem so it's not affecting many phones, and ultimately Samsung are going to have the occasional dodgy NAND chip. Sounds like you got one.
If you'd had several phones and they'd all exhibited this problem you'd be right to be peeved, but it simply sounds like you've been unlucky and are pissed off about it. Have you even discussed it with Samsung's tech support or taken it back to the shop you bought it from?
And accusing an XDA recognised developer of trolling is not a great start to your time here.
I've not heard of other people having this problem with the Gnex? Who are these other people having this same problem? Maybe speak with them and see if a replacement phone might solve the problem. I really hope you can get this fixed and not give up on such a great platform.
Sent from my Galaxy Nexus using Tapatalk
vulpy said:
This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Click to expand...
Click to collapse
The burden of evidence is on you bro. That is a pretty bold claim.
David Horn said:
...And accusing an XDA recognized developer of trolling is not a great start to your time here.
Click to expand...
Click to collapse
Respect for your dev background (haven't used any of your ROMs yet), in all fairness I'm far less impressed with your communication skills... I must agree though, my message may have come across as too abrupt and you're right again, I am going to sort it out with Samsung...
Did not mean to get people horrified, rather to blow the whistle on a worrying and annoying bug and smth people may consider if they come across or consider a purchase.
For having worked in the mobile comm semiconductors space for years, I know just what sets apart a serious company from a me-too profile. Surprised to see Samsung having this king of issues. Normally they are ironed out easily though SW regression tests and HW stress processes (at least at serious OEMs).
I will let one of the moderators judge if my crime is so serious, your ego will survive, I'm sure I will come back when/if issue solved (or in good progress).
yeah, mine is fine. If it was a widespread problem I would back your corner, but I seems rather isolated. Rather then cause mass hysteria I would say you need to return your handset
Sent from my Galaxy Nexus using XDA
This happened to mine. But only once.
Quite frustrating, as my phone is my alarm clock and it was bootlooping when I needed to go to sleep!
However, a reflash of the 4.0.2 stock images sorted it out, and no problems since. I'm pretty sure I caused it by pulling out the battery at some sensitive point in a reboot or something.
If this happens to you frequently, then you need to exchange your phone.
Also, I think this could be a pretty good resource as opposed to a rant if you put your mind to it. I'm not a developer, but I'm also not a total n00b, and it took me a little while to figure out how to fix the problem, when I had it. I'm sure there are people out there who would appreciate a guide.
In this thread, op is going through that time of the month, when was his own modification back fires in his face, his explosive emotions reek havoc on an online forum.
If you want to see a device with bad nand memory, see the HTC Desire S forum .
Also the reboots and freezes I used to experience on my device were application related. Device hasn't frozen, nor rebooted in about *looks at up time* .. 27 days .
adrynalyne said:
The burden of evidence is on you bro. That is a pretty bold claim.
Click to expand...
Click to collapse
... I was actually referring to a poll in another thread (link in this thread) concluding that half of the people who answered have experienced freezes and reboots... it may be biased somewhat by the fact that people who experienced the issue are more likely to vote than those who didn't... maybe an overstatement from me.
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
First I heard about this too. I've flashed tons of roms and mods and constantly installing uninstalling apps.
The GNex has been anything but non-stable. I think I've had to pull the battery once or twice since ownership. Never heard anyone complain about randomly losing all their data... especially not daily. Perhaps on a bad flash in CWM.
Maybe you should look into a super wipe that completely erases everything, deletes the partition tables and recreates everything from scratch. Maybe it'll help but it honestly sounds defective.
Sent from my Galaxy Nexus using xda premium
Thanks Player911... Interesting idea, was thinking as well to do a total wipe and sort of a sector-by-sector reformat, but could not find a way of doing it. Is there any tool that would allow me to do it? Maybe this will isolate bad sectors...
Will check shortly with Samsung folks, thanks mate! (what slows me down is the fact that I'm currently travelling to the US and the guarantee is only European and it's Sunday= hotline is closed in Europe).
daern said:
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Uhh, I don't believe my reboots are due to this. Just saying. That whole thread does not point to your theory as the issue. I'm gonna go ahead and call this myth busted and suggest you go get a replacement because this is just another extremist "my phone is busted but I refuse to get a new one" thread.
Sent from my Galaxy Nexus using xda premium
You've been Samsunged
Sent from my Galaxy Nexus using xda premium

[Q] Strange behavior while charging

My issue does not seem to be specific to any one rom, I have flashed nearly all of them. When I try to use my phone while it is charging, the touch screen is slow to respond or extremely laggy. I use the stock USB cable and AC adapter.
Does anyone else experience this?
whewitt56 said:
My issue does not seem to be specific to any one rom, I have flashed nearly all of them. When I try to use my phone while it is charging, the touch screen is slow to respond or extremely laggy. I use the stock USB cable and AC adapter.
Does anyone else experience this?
Click to expand...
Click to collapse
Hi. Did you do a search 1st ? No, because this has been answered before. Next time don't be afraid to go thru some pages and do a search before posting a redundant question. Thanks.
Muff Burner said:
Hi. Did you do a search 1st ? No, because this has been answered before. Next time don't be afraid to go thru some pages and do a search before posting a redundant question. Thanks.
Click to expand...
Click to collapse
I did try to do a search, but the search field disappears when I try to use it on my tablet. Ever time the android keyboard comes up, the search field goes away. Could you kindly direct me to the correct post.
I finally was able to search the threads when I switched to my phone.(it had charged enough to unplug out and use) From what I gather, it is a result of a built in feature on this Samsung phone used to eliminate "ghost touches"
This doesn't help the fact that it is annoying and counterproductive when I am trying to read xda posts while at work.
Sent from my SGH-T989 using XDA App
whewitt56 said:
I finally was able to search the threads when I switched to my phone.(it had charged enough to unplug out and use) From what I gather, it is a result of a built in feature on this Samsung phone used to eliminate "ghost touches"
This doesn't help the fact that it is annoying and counterproductive when I am trying to read xda posts while at work.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
people can be meanies on here. xda search isn't the greatest thing. But it could be that the charger is faulty. Probably need a new one. T-mobile could supply you one through warranty for free. Try to ask for the cable and battery too while you're at it. they're all covered.
Teo032 said:
people can be (Mod Edit) on here. xda search isn't the greatest thing. But it could be that the charger is faulty. Probably need a new one. T-mobile could supply you one through warranty for free. Try to ask for the cable and battery too while you're at it. they're all covered.
Click to expand...
Click to collapse
Thanks, I'll give TMO a call. Worst case scenario is that I'll get a new charger. I agree about people bring pricks on here, I see it every day in the dev section. I just thought I could post in Q A without getting grief.
Sent from my SGH-T989 using XDA App
whewitt56 said:
Thanks, I'll give TMO a call. Worst case scenario is that I'll get a new charger. I agree about people bring pricks on here, I see it every day in the dev section. I just thought I could post in Q A without getting grief.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
It's not super clear what the issue is. Some people say that the issue goes away when not using the stock Samsung charger, some say the issue is a grounding issue. I personally have experienced this issue in the lock screen and it'll take like 5 tries to unlock but outside of the lock screen I don't have issues with general usage. Rest assured it's not a faulty phone, or even a faulty charger.
yoft1 said:
It's not super clear what the issue is. Some people say that the issue goes away when not using the stock Samsung charger, some say the issue is a grounding issue. I personally have experienced this issue in the lock screen and it'll take like 5 tries to unlock but outside of the lock screen I don't have issues with general usage. Rest assured it's not a faulty phone, or even a faulty charger.
Click to expand...
Click to collapse
I experience the exact same symptoms from lock screen. However, there is also a lag in responsiveness even after it finally unlocks. I'll give my wifes my touch 4g slide's charger a go. Thanks for the suggestion.
Sent from my SGH-T989 using XDA App
I plugged my t989 into my wifes HTC OEM charger and experienced no strange behavior from the phone.
Sent from my SGH-T989 using XDA App
whewitt56 said:
I plugged my t989 into my wifes HTC OEM charger and experienced no strange behavior from the phone.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Glad to hear you solved the issue with one of those solutions.
Thanks for the suggestion yoft1......+1

Touch "gets stuck" on letters while typing

Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.

Categories

Resources