Related
Since I did the ICS update via the LG software updater my phone operates extremely slow(screen refresh, typing entry delay, etc...) and battery life is significantly lower. I do see other threads about different software versions and don't really know what a lot of it means. I also see advice on doing a factory reset after upgrading, but is this really necessary with the stock update? It's my understanding that my phone should scream because of the processor that it has. should I go back to GB or is there something I can do to make it a fast, powerful device?
Mine is 4.0.4 Android version and LG -P930-v20c-JUN-25-2012 is the software version.
Thanks in advance
Factory reset will probably solve all the problems you're having.
And the processor in this device is not a "screamer", it was about a year ago, but not any more unfortunately. It performs worse than the galaxy s 2 in most cases, mostly due to the added resolution of the screen.
That being said, I still quite like this phone, and running CM10 on it has me very happy. Once they sort the black screen of death issue (which is apparently present on many devices) it'll definitely keep me happy till I can afford a new phone (Or maybe christmas)
If you follow the steps posted here to root your phone (you'll have to unbrick it, follow the guide), and install CM9 on it, I'm sure you'll be far more impressed with your phone. The LG software sucks many dicks in my opinion, CM9 is WAY better.
hereric said:
Factory reset will probably solve all the problems you're having.
And the processor in this device is not a "screamer", it was about a year ago, but not any more unfortunately. It performs worse than the galaxy s 2 in most cases, mostly due to the added resolution of the screen.
That being said, I still quite like this phone, and running CM10 on it has me very happy. Once they sort the black screen of death issue (which is apparently present on many devices) it'll definitely keep me happy till I can afford a new phone (Or maybe christmas)
If you follow the steps posted here to root your phone (you'll have to unbrick it, follow the guide), and install CM9 on it, I'm sure you'll be far more impressed with your phone. The LG software sucks many dicks in my opinion, CM9 is WAY better.
Click to expand...
Click to collapse
Thanks for the reply. Can you tell me what CM9 is? i will definitely try it.
thanks again
Try factory resetting first. Yes, you have to reconfigure almost everything. But you'd have to do that anyway if you try CM9. A lot of people say that the ICS update is good after you do a factory reset, so you may like it just fine.
CM9 is Cyanogenmod9, which is a custom ROM that can be installed on this phone. But it's not the easiest process for beginners.
When you factory reset, you'll lose things like text message history and contacts (unless contacts are synced to Google, then they'll reappear after you log back in after factory resetting -- or on your SIM card).
Thanks for the info on the ROM. I'll look for a link to instructions and try it when I can afford to be without it in the event of a failure. I am technical...just not with phones.
Thanks drumist
update...reset made a significant difference in the speed. keyboard & screens work great now. still have an issue with battery though; but that seems to be standard on ics.
thanks!
MichaelWayne_71 said:
update...reset made a significant difference in the speed. keyboard & screens work great now. still have an issue with battery though; but that seems to be standard on ics.
thanks!
Click to expand...
Click to collapse
It takes a while after a fresh install of this rom for the battery life to settle in. After about a week the battery life improves significantly
Sent from my LG-P930 using xda app-developers app
Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card
Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.
I have some thumb rule, never update to the newest firmware, and reed the comments. Also at home I have a router, that the manufacture update the firmware from time to time, but I used to run one firmware before the last one. It just an example, but since all the Lollipop, people complain, so why bother? Can't you wait for a while, till Google resolve all the issues? Do you consider Kitkat was perfect then? Or does Lollipop runs perfect on Nexus 6 & 9? I'm starting to think, it intentionally, like iOS 7 on iCrap 4, on iOS 6 it was fine, just think of it, maybe Google do it intentionally, to make us buy a new device? Or they just do a bad optimization job for older devices, and put all effort toward new devices? Any thoughts? I know we all nexus user, are a free beta testers, but if running latest firmware, means it brick out devices, it's hard to thrust Google like that, so I think it's better to stay on Kitkat till better times.
Sent from my hammerhead using Tapatalk
The people who's tablets work fine (the vast majority I'd guess) don't complain. You only here from the people who have problems.
I've been on lollipop since the preview and it's been great. I'll be flashing 5.1.1 the second it's out. Kitkat is dead to me, and very ugly looking back. It certainly was not perfect.
If my device gets the brick people are talking about it would suck but I really, really doubt it has anything to do with the firmware. Some hardware failure most likely. No reason to stay on an old release.
5.0.2 was horrible. While I disregard majority of users complaining of battery life, some of them weren't spewing nonsense.
5.1 is an improvement. I'm one of the guys who do not post every complaint or dissatisfaction I encounter with the Nexus 7. I know what the problem is, I know where to ask for help to pinpoint the cause, now it's my turn to make a decision, stay on Lollipop? or revert to KitKat? Or remove the cause, in other words the app itself.
Back to the OP, there is no risk updating to 5.x. Your device won't magically break. If you like to play it safe, maybe it's better for you to wait for user feedback and ignore the OTA.
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
I wouldn't take an ota myself. Not because of "the brick," I think thats a hardware problem, I feel it's a cleaner update with fastboot and if something fails I'll know what.
And you can (and should) make full nandroid backups in a custom recovery (cwm, twrp etc.).
But to the poster aboves comment it just goes to show you people are having different experiences. 5.0.2 was fantastic for me, great battery life, best it's ever been actually (still as good on 5.1 ~8 hours screen time over two days.)
The memory leak was/is a problem. Oh no I had to reboot once a week. Huge headache. On 5.1 I'm at 270 hours uptime and system ram's at 479. It is creeping up slooowly but better than 5.0.2
I guess it depends what you do with the tablet and especially what apps you have installed. I use my **** pretty heavily though so I don't know why I'v had no problems.
donisan969 said:
OTA you say...
All I hear ate 2 things "Memory leak" & "Bad battery life", be it Nexus 4, 5 or 7, all after the "Lollipop", ...mostly the "Memory leak thing, that told to be solved after each update
Is it safer to flash from ADB? or the "dead" devices dyed in both ways? be it ADB on clean device, after reset, or just OTA? I personally, never thrust OTA updates, I wish there was an easy way, to make a full backup, like a "Norton Ghost" for PC's, I know it can be done with ADB, the question is, if there's any difference, between flashing "with wipe" or without? or maybe the "dead" devices was : 1. rooted, 2. bootloader unlocked, 3. encrypted, or something else? I mean, Google do test all new FW on real devices? don't they?
Click to expand...
Click to collapse
Hard bricks have been reported from both OTA and ADB updates, but very seldom from users of custom ROMs... Most likely cause is eMMC failure due to faulty hardware, though the issue is present on nexus 4 and 5 as well... Possibly faulty bootloader software too.
^Bootloader faults could be possible.. that has pretty low level access. I don't know low enough to corrupt the chip. I don't know. Asus/google probably does but guaranteed you'll never hear a word from them.
I hope it's not something like the infamous s2 brickbug. Then you're just playing russian roulette. Maybe entropy can help lol.
What emmc chips are the 4 and 5 using? I'll have to look.
I'm not sure this is true but if you use Greenify I think the memory is kept in check better, although it requires root. I still see the occasional launcher redraw but not nearly as bad as it was in 5.0. I was on 5.0.2 for several weeks and wouldn't have updated if I hadn't read about the hardware failures.
Well if you don't update your tab, than you don't need a Nexus, buy some cheap chinese tabs for 70-100$, almost all of them are on kitkat, most of them vanila android, no updates, and they all work fine.
This is Nexus.It's a developers tab, for testig, trying, people who like the freshest system on their device, who like clean android....if something's not working, there's always an image of the old system or a bunch of ROMs to test and use...
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
donisan969 said:
I know, I myself for now test windows 10 on work PC, and a server 10 preview, but computers and tablets are different things, because you not have that much control for both. All I say, is, that I see same threads for any nexus device, I had a Galaxy nexus before, so I know. About s2, there was a rumor about some other Samsung devices back than.
Sent from my iPhone 4 using Tapatalk
Click to expand...
Click to collapse
Device OEM is irrelevant in that regard, the quality of internal components is really the crux of understanding hardware failure IMO. of the major android OEMs, all of them have in the past put forth devices that were predisposed to early hardware failure, mostly due to choices of components used during the manufacturing process. Hardware revisions on individual devices of the same model is also a valid form of comparison.
I'm not sure if it's a software problem or a hardware problem that's not the motherboard.
This is my phone's original stats, as I have written down.
N7105
ROM: DN3 v3.2
kernal: AGNi v3.9
bootloader: 4.1.2
Recovery: Philz 6.07.9
The problem is that the phone just randomly stopped waking from sleep. Not all the time, but it just started one day and slowly increased in frequency. I eventually figured out that the phone was simply not waking up, causing the phone to (presumably) freak out, because if the freeze happened hours ago, then the phone would be very warm when I picked it up and, after forcibly rebooting via the power button, the battery would be way down.
I noticed IndexServices was using a lot of battery power, and google tells me that it freaks out at files over 200mb in size, but best I can tell, I have no such files. I can't recall anything that would change this when the freezes started happening. It may not be relevant at all.
I could live with the forced reboot for a while, but having my battery capacity killed for no reason sucked.
Screw this, I thought, I have a spare motherboard, I'll figure out the problem later or never.
Nope.
My phone's current stats.
SGH-t889
ROM: DN3 5v2 final slim
kernal: default
bootloader: 4.1.2
Recovery: TWRP 2.8.0.0
I swapped the motherboard in and used Titanium to restore my most-used apps and their data. Unfortunately, the problem seemed to have followed the change, although in a different way. The phone just freezes and doesn't accept any kind of input- no touch, no buttons, nothing. I have to pull the battery to reboot. It doesn't just happen when asleep. I've had the phone literally just stop responding as I was scrolling through a webpage. It seems to happen mostly at night and early morning, which is no bueno. I can't use it as an alarm anymore. But it's still better than leaving it alone only to find the battery down 40%.
It also occasionally reboots on its own. I haven't found a pattern to any of these problems.
I played with this motherboard when installing the ROM and such and never had the above problems, so it may or may not be related to the problem I had with the other motherboard.
It's not my SD card. I pulled it when I still had the N7105 motherboard in. It didn't make much of a difference.
I installed SysLog and got a bunch of logs from the N7105 motherboard right after one freeze/reboot. But I'm not entirely sure what I'm looking at nor what to look for. It's been a while since I've fiddled with my phones, so I'm not very enthused at the idea of reflashing my phone.
What can I do to better pin down the root of the problem, short of reflashing everything and hoping the problem goes away?
I would flash stock rom and kernel without apps restoring just to see if it's hardware or software issue.
there is service menu where you can test sensors *#0*#
you can try to overclock cpu, I remember that some time ago it helped to similiar problems with waking up
Yeah, I think I'll probably have to reflash at some point, just to make sure. But I'm going to avoid it for now, since I have other concerns.
I forgot about the service menu! That's a good idea, thanks!
I've never overclocked a CPU, computer or phone, so I'll read up on that. Not sure it'll help with the t889 motherboard, but it might work for the N7105 motherboard.
Thanks again for the suggestions!
For what it's worth, I have the same problem. It started a few weeks ago. I was using Dr. Ketan's rom and thinking that it might be a rom problem, flashed Resurrection Remix 5.1.1. CM 12.1. For a week there was no problem, but now it's back again.
If the phone is left untouched for a while, it won't wake up and is warm to the touch. And yes, the battery is greatly reduced...
I'll be interested in anything that is discovered....
Thanks.
Well, this is mildly frustrating and not at all helpful, but the weird freezes on the t889 motherboard seem to have stopped by themselves. I didn't do anything beyond poking around the service menu. Everything looked ok there. The freezes continued a while longer, and yesterday I noticed that it had been over a day since I had to pull the battery to force a reboot.
My best guess is that an app update caused a minor hardware incompatibility, and some update this past weekend resolved that incompatibility. I'm going to give it another couple of days before swapping the N7105 motherboard back in and seeing if some app update fixes that problem.
Update: I swapped the N7105 motherboard back in and ran all my app updates. No go; the problem showed up again while I was charging the phone. On the other hand, I was able to confirm without a doubt that it's a problem with this motherboard and not the headphone port that causing the lack of sound output with headphones in. The phone acknowledges the headphones when I plug them in. It just doesn't play anything through it.
Indexservice is still using up far more battery than it should. It might be higher than normal due to all the app updates, but it really shouldn't be as high as it is, so I'm tentatively declaring it related or the cause. Since it's not a file size problem, it may be a corrupted file, which means a reflash in my future, if I want to keep using the N7105 motherboard.
It's possible that all these problems mean that the motherboard is failing. It's two years old. It might just be its time.
Hopefully, reflashing everything will fix the problems. If not, at least I had another motherboard to fall back on.
I'm still having the same problem and haven't found a solution. It often won't awaken and needs a long push on the power button to boot. After booting, if we use it a lot it seems to be fine, but if we leave it alone for a while, it won't wake up.
Is that what you are getting? My wife wants another phone!
We always leave in on the charger all night long (as I have done with all my phones). Can that have damaged something?
I could try flashing a stock rom, but fear this may be a hardware problem. I don't see many participants in this thread...
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
---------- Post added at 06:45 PM ---------- Previous post was at 06:22 PM ----------
That service menu that you quoted above doesn't work on my phone. Could it be misspelled?
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Yes, that is exactly it. As long as I'm actively using the phone, it's fine. It's only when I leave it for a while that it won't wake and I have to press the power button to force reboot.
I also leave my phone on a charger all night, but I hardly think we're the only ones to do this. It might be related, but I kind of think it's not.
You could swap out the motherboard like I did. I imagine they're much cheaper now then they were when I bought mine ages ago. The Note 2 is very easy to take apart.
The service menu as written above works for me. Not sure why it won't work for you.
Did the new motherboard solve the problem completely? I see replacement motherboards for $45 online. They offer both 7100 and 7105. What is the 7105? I now have a 7100 European model.
I downloaded the EMMC check program. My phone does not have the "Insane Chip" that causes the Sudden Death Syndrome, but it has eMMC chip VTU00M -for what that's worth.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Phenomenal. I'm going to order a 7105 motherboard. It will take a while to arrive and my wife will grumpy until it is installed.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Selofain said:
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Click to expand...
Click to collapse
When you installed the new motherboard, did you have to do anything with your imei number?
In reading above it sounds like you changed motherboards several times and during that time the problem went away, but was it really the different motherboard? There are motherboards for sale in China, but I don't see any indication that they are Samsung manufacture. They are compatible, may be used actually, and although they cost 45€, shipping will be 38€ more unless I want to wait 2 months for the free shipping by mail.
Did you try reflashing a stock rom? I am tempted to try that first.....
Regards
I only have two motherboards, and I only swapped them out a couple of times. I had minor problems with the t889 motherboard at first, but the problem went away on its own after a week or so. It had actually been nearly three weeks before I swapped the N7105 motherboard back in, and I didn't leave it in for long, just long enough to determine that the problem was still there. I'm back to using the t889 motherboard now, and haven't had any problems with refusing to wake from sleep.
I haven't flashed a stock rom yet. I found that I couldn't restore the data of one of my apps to the new motherboard, and the data was something I spent hours inputting, so until I find a way to save that data, I won't be reflashing.
I didn't do anything with the imei when I installed the new motherboard, but I was prepared to transfer the imei if necessary. I backed up my old one and would have restored it to the new motherboard if necessary, but it wasn't necessary, so I didn't do anything. I bought my motherboard on ebay, which has both advantages and pitfalls. I'd say definitely try reflashing first, since that won't cost you anything but time.
My girlfriend has had the same issues for around one week (exactly the same symptoms_freezes when left untouched, especially at night, and she has to reboot). She has been on revolution HD 31 rom for months without problem ; she hasn't installed anything lately either... an update is probably the cause. I flashed ditto N4 (after factory reset) but the issue has shown up again... It's a european n7100.
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Weird thing, I got that insane chip but my note doesn't seem to randomly reboots overtime.. I experienced some reboots using some rooms, though, mainly with 5.1.1 releases. Is there any trusty app that really informs me the right chip? Thanks.
Enviado do banheiro
Oh, great! It's good to know that it was a software error rather than a hardware error. Let us know if you figure out which app is causing it. It can't be too common an app, or we'd see more people here in this thread.
So far, the phone is behaving perfectly. My wife is thrilled because she is used to the look and feel of Samsung roms. She didn't like AOSP which is considerably more buggy. Yes, with CM12 roms, random reboots are common. Little by little, we are adding essential apps. We don't even have the phone rooted and may not ever do that since my wife likes to keep it simple.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
quijote1 said:
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Click to expand...
Click to collapse
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
oliwek said:
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
Click to expand...
Click to collapse
I used the latest TWRP recovery because the AOSP roms seem to like that better. Otherwise I have always preferred Philz. I always froze hangouts but our whole family are heavy WhatsApp users. I have now frozen most of the Samsung and Google bloatware and the phone is very happy. Today root and more apps. Oh, I also use Greenify and it's working fine.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher