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 all
i was downloading the new kitkat update for my n5100 when i read about the many issue in this update and still couldnt find a fix from samsung
so do u advise me to update or stay with jellybean??
If you plan on keeping it unroofed, kitkak will be better with battery life but soon will be better over all with apps. Seems like developers spring into action late Dec through Feb for new devices under the tree. If you root, JB can be tweaked to be very stable and reliable.
Now that í have two devices running both kitkak and BJ, both are rooted' as there is no other way to live with them happily... I can say both are about equal, just JB needs system tweaking, while Miriam needs fixing and proper app builds from Google.
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
If you plan on keeping it unroofed, kitkak will be better with battery life but soon will be better over all with apps. Seems like developers spring into action late Dec through Feb for new devices under the tree. If you root, JB can be tweaked to be very stable and reliable.
Now that í have two devices running both kitkak and BJ, both are rooted' as there is no other way to live with them happily... I can say both are about equal, just JB needs system tweaking, while kitkak needs fixing and proper app builds from Google.
I just heard about bugs in kitkat
is it true?? And the spen bug too
and thnx for replying
I don't know about spend bugs... Never seen it not work in my apps. If you have calibration issues, as what many complain about with all samsungs, just do a calibration.
Yes there are a few bugs with Miriam... Xposed modules will clear up most of them.
Yes, S-Pen went funky on me in 4.4.2; How to Calibrate?
My S-Pen ended up with horrible offset after doing the 4.4.2 update provided by Samsung. I no longer use the pen as a result, which sucks. I keep hoping for an update/fix from Samsung, but will probably eventually root and try custom ROMs that apparently resolve the issue.
In the meantime, gooberdude - you refer to a calibration? Have you done this on a Note 8.0, and if so, how? I've heard it referred to, but have never had any success in finding a way to do any kind of calibration.
-Mike
gooberdude said:
I don't know about spend bugs... Never seen it not work in my apps. If you have calibration issues, as what many complain about with all samsungs, just do a calibration.
Yes there are a few bugs with Miriam... Xposed modules will clear up most of them.
Click to expand...
Click to collapse
To calibrate... Open Shots and create a new note with spend.
Go from the upper corner along the edge of the screen and follow along to the next corner, and so on until you have made it back to where you began. You want to make n outline of your screen corner to corner in straight lines.
You may have to repeat a few times, but once you get the knack of it, it will be easy to perform again if needed.
I have a gorilla glass so depending on angle of spend my view of pixel my be distorted by the thickness of my screen protector. As it is very thick.
Try to keep your spen tip at a 45 to 60 degree angle, as it helps with calibration.
I have already updated my n5100 to 4.4.2 and I have no problems with spen.
the most important issue you will have after updatevto 4.4.2 is that you you will not have full access to the external sd card.
also you will have 4.4.2 bootloader with knox that if you root or ... your device the knox will
be tripped and your warranty will void.
the choice is yours .
It is worth to upgrade only if you are willing to run custom kernel.
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
I have rooted sm n910p with freeza's kernel.
Last week my device sometimes locked it's screen up by itself.
I am using fingerprint to unlock it.
So why does this happen and how to avoid this?
Sent from my SM-N910P using Tapatalk
Try a different kernel if you think its that.
Sent from my 0x1 Note 4...... I love tep
Mine was rooted but I never rooted it again since upgrading to 5.1.1 and suddenly the last few days my phone locks up really bad and has even began power cycling on lock-ups. I've factory reset twice and it does it even without apps installed yet.
I think it's a memory issue. Thankfully it's still under warranty and is going back to Samsung. Hoping they find out whatever's wrong and repair or replace it.
Your issue might be related to root but I think it's coincidental that we both began to see similar lock-ups around the same time.
When did you buy yours? I bought mine October 2014 so I'm at a year now.
touch_rules said:
Mine was rooted but I never rooted it again since upgrading to 5.1.1 and suddenly the last few days my phone locks up really bad and has even began power cycling on lock-ups. I've factory reset twice and it does it even without apps installed yet.
I think it's a memory issue. Thankfully it's still under warranty and is going back to Samsung. Hoping they find out whatever's wrong and repair or replace it.
Your issue might be related to root but I think it's coincidental that we both began to see similar lock-ups around the same time.
When did you buy yours? I bought mine October 2014 so I'm at a year now.
Click to expand...
Click to collapse
Could be battery or shameful ItsOn service tasking resources. I believe you can see if ItsOn is running by viewing the ##DATA# options. Mine is not there anymore to say where it's at.
Maybe OP didn't disable ItsOn? It may not be an issue with the kernels required to have root on OG5; not sure if kernel alone keeps ItsOn from running or trying to run?
True, the memory management can be too aggressive for some vital services while ignoring some that shouldn't run all the time. But that shouldn't be causing lockups or power cycling. Too late to fix Lollipop; I hope they get Marshmallow right.
If OP's lockups are black screen or wake issues, may help that in build.prop with this line added (if it's not there already):
ro.HOME_APP_ADJ=1
You may find reasons to root again, depending on what you find. Best wishes.
Sent from my SM-N910P using Tapatalk