Related
Hello Everyone,
Many times while searching the internet for Nexus information, the search keeps having me come to this forum so I decided to become a member. Just got for my G-Nexus the other day, its replacing a Droid 3. Nothing really wrong with the Droid (well), but it was my first physical keyboard phone and I wasn't feeling it, and I heard so many good things about the Nexus I knew I had to have one.
I've had it less then a week now, and so far I love it. Though the one thing I must say I am not crazy about, which seems to be a common complaint, is the battery. It drains WAY too fast. Today though seemed more then ridiculous. I left my house @ 8:45 am @ 100% (right off the charger). Made some use of it on the bus, but nothing much (no calls, no video, no music). Already by 11:30am, I was @ 39%! I mean come on, I didn't even use it that much. Yes, I did notice I left the WiFi on, but it should not have drained that fast. Tuesday I used the device moderately and I was able to go home after having the device on for 9 hours and still have around 40% to spare. Its a shame they cannot make a battery that can accommodate such a great phone.
So some questions: Is it really necessary for me to root this thing to get its full potential? I never rooted a phone before. When I bought the phone, I got a shiny gel case that Verizon sells for like $20 - if I did get the extended battery and door, would this case still fit? I am thinking no. Is the ext. battery even worth getting?
I have more questions, but I will peruse the forums and see what everyone else is saying. So in all I just wanted to intro myself and say I am happy to be part of the forum!
Your battery should definitely not be draining this fast. Install better battery stats(look around XDA) and look at what partial wakelocks you have. Try to remember any recent apps that might have been causing the drain
The 2100mah battery will fit. If you're looking at the 3900mah extended batteries, those have their own custom backplates and won't fit.
I've read that the 2100mah battery adds about an hour of juice.
nickzkcin said:
Your battery should definitely not be draining this fast. Install better battery stats(look around XDA) and look at what partial wakelocks you have. Try to remember any recent apps that might have been causing the drain
Click to expand...
Click to collapse
Sorry to sound dumb, but what do you by "battery stats"..?
And I am not sure what a wakelock is either - if you could explain
Hey,
I got my Galaxy Nexus this week too. This is my third full day of using and I get good 10+ hrs of usage each day. I use it a lot too. At least 2-3 hrs of talking, about 50+ texts, synching 4 emails, and browsing/streaming an hour or two each day.
You should check what drains your battery the most and go from there.
Sent from my Galaxy Nexus using Tapatalk 2
Wavester said:
Sorry to sound dumb, but what do you by "battery stats"..?
And I am not sure what a wakelock is either - if you could explain
Click to expand...
Click to collapse
'better battery stats' is an app. go look for it. there's an XDA version
your phone goes into 'deep sleep' to conserve power. wake locks are when something refuses to let it get to that state and locks it awake. This is major cause of battery drain.
Better battery stats is available on the Play Store (ugh hate that name) but the dev is nice enough to give it to xda members for free:
http://forum.xda-developers.com/showthread.php?t=1179809
Aside from looking at wakelocks, go to Settings>Battery, then look at the list of stuff (in descending order) that's eating your battery. I went to watch a movie once at 90%, when it was done the battery was at 18% and I never even touched my phone. I checked that list and apparently Facebook killed the battery. Try and look for apps that might be using up a lot and either uninstall them, replace them, or trun off features that might be causing the drain
As someone new to this forum you should learn questions go in Q&A
Please read forum rules before making threads
Thread moved
FNM
Do me a favor.
Settings>Battery>click that graph.
Screenshot it (volume down+power)
and upload here.
I'll let you know if you have a problem...and if you do...we'll diagnose it.
Root it?
It's a Nexus man. They're fantastic for root users.
All the roms are AOSP...
And bug free (or...mostly. AS bug free as any google build, generally).
Jubakuba said:
Root it?
It's a Nexus man. They're fantastic for root users.
All the roms are AOSP...
And bug free (or...mostly. AS bug free as any google build, generally).
Click to expand...
Click to collapse
I agree with you that the Nexus is fantastic for root, but it's not necessary for all users. I rooted mine because I was use to with my old HTC HD2, but ,except for changing rom, it's useless when you just get your phone.
I think that you can keep the stock rom, and don't root it. One day you will maybe need it, but the stock rom is very nice, it's enough to start (that's what I did with mine).
I noticed you are on Verizon, bad cell reception can chew your battery for lunch too.
There's something floating around in the development section (sprint I think) called battery mod.
Of course, youd need to root and unlock your device to get it working (takes all of about 5 minutes).
I also had this battery draining problem, but installing a custom from with a power saver governor and the battery mod, it'll drain 1% every 30min-1hour. Its essentially in "deep sleep", as the CPU winds down to 0mhz, instead of the standard 350. With this comes a lower CPU voltage, so less energy is wasted.
All in all, this is a great phone once you tame it.
Look for Black Ice ROM. Its probably one of the best here because it let's you choose a stock look or a custom look
Sent from my Sprint Galaxy Nexus CDMA using XDA
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
I wanted to edit typos and add that use GO Launcher EX so the launcher features of the ROM are irrelevant. Don't see an edit option...
Sent from my Amazon Kindle Fire using xda app-developers app
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
sharonbw said:
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Rooting and installing ROMs may not be everyone's forte, but there is nothing to fear if you've done every step correctly. Many of these CM builds are nightly builds; that is they release one every short interval of time fixing small bugs encountered in the previous release. If you really want to enjoy CM, you could go for the latest stable build.
To your first question: Yeah, switch back to an older ROM. That's generally more stable and you have the whole thread to sort through if you get into some tough spot. You've been pretty lucky to have gotten so far without bricking your device, I must say. I don't recommend reverting back to stock; you'd miss a lot of the features that aren't there on the KF.
To your second one: that's totally up to you. I confess, I don't own a KF, but with the phones I've had, I've always been experimenting with them. My old Moto Razr, my Moto Ming, my Nokia 5800, my Nokia N8...the list goes on. Changing ROMs, it's kind of like an hobby of mine.
You could lean towards a better UI( I really like the one on stock KF though) or a rock solid feature rich performance ROM. It's up to you.
As to your third question: I can't really answer that sorry. I'm a Galaxy Tab user, so I don't know much about KFs. As to testing ROMs, well, you said it. Test them. There's no other way to know if you're going to like them or not otherwise.
Yes, install Jandycane. It's not pushing your luck. There's no room for error unless you're so excited that you even make silly mistakes.
You can modify posts by tapping on it, selecting Modify, then edit.
Hope I helped you some.
One ****ing minute! - Billie Joe Armstrong at iHeartRadio Music Fest 2012
It's not luck if u spent time reading n following the rooting tutorial, it's ur work, though small compared to developers. I'm exactly like u, 1st time ever use an android device, but with experience with my Nokia5800, it's easier for me to solve problems, not to panic when rooting a device .
For me, keep rooting different Roms until the most suitable for personal use is enough. As time passes, I feel tired of doing the setting again after installing every new Rom. I stick with twa 's Linaro 'til now.
I think the risk of experimenting new Rom is small because the device memory is very hard to malfunction. As long as ur PC and KF is there, u don't have to worry.
There's still a lot to learn abt android, not only rooting, I think. Right now I'm learning about OTG and how to use external devices with KF, like flash drive or microphone.
All credits and thanks to our developers such as hashcode and twa.
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That's what you get for a $200 tablet sorry. You could look around your device forum asking for prop.build tweak that optimize battery life.
You'll understand all the big dev terms sooner or later. Its just a matter of time.
Sent from my GT-S5360 using Tapatalk 2
zelendel said:
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
x10knight said:
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
Click to expand...
Click to collapse
There are many things that could go wrong when rewritting the OS on your PC that could make that not an option.
Sent from Arkham
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Aesrys said:
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Click to expand...
Click to collapse
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The KF on stock ROM operates between 400-800 MHz. It is set that low on all Custom ROMs, whatever the device may be (That is, if they have their own kernel). There is no normal frequency. It's like a car. You go in third gear or fourth gear as you wish. There are no steadfast rules that you have to go in fourth gear on a road and the fifth in another. CPU governors are how you set the frequencies. I don't know what you get on the KF, but on the other devices that I have tried, "Blackcats" is the one for day-day usage. Not too much, not too less.
Yes, that's the thing about having a fancy ROM. I have a completely transparent ROM on my Galaxy Y and sometimes, the thing goes bonkers. Since my phone doesn't have CM yet, these fancy transparent ROMs are the best bet for a flashy and beautiful ROM. On stock, I get around 1-2 days, but on these transparent ROMs, I get like 5-6 hours a day. Not too bad, considering that my completely transparent W7 laptop only stays for an hour on battery.
Sent from my asus_laptop using Tapatalk 2
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Aesrys said:
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Click to expand...
Click to collapse
It's too early to know for sure but no SoD since I upped it. I've done clean several installs and i've had it since the first iteration using twa_priv's CM10. I'm currently running 20120923.
I'm still a little unclear on what clocking is but I guess that's a deficit in my knowledge of physics.
UPDATE: Well came back to my kindle after watching tv and it was in the SoD. Force power off and reboot and I'm back in business. I'll leave the clock speed at min 300 since I didn't notice any difference.
I'm going to do a search but anyone want to give me a link to a 'how to' for doing a logcat? (Is that even the right term? ) I don't know that the developers want to hear from me but I could at least post the log when I experience SoD.
Edit: nevermind. I found how to logcat.
Sent from my Galaxy Nexus using xda app-developers app
So I flashed the latest and "greatest" Android 4.3 on my Galaxy Nexus. After all, this is why we get our nexus devices for, right -- getting the latest updates without begging cell phone vendors or carriers. But Android 4.3 on Galaxy Nexus is driving me nuts -- A full charge won't last me for half a day without much usage at all. The phone intermittently wakes up and won't go back to sleep again, and after I press the power button to put it to stand by, it wakes up a few seconds later. Granted, it's not like that all the time, but it's often enough to be annoying and it's eating the battery alive. Before you ask, yes, I did do a clean install with root.
Very frustrated with this update, and come to think of it, the Android updates of late have not been stellar -- I experienced system random restart when 4.2 hits, and now this...
Sorry for the ranting but I'd like to know if anyone else has experienced similar problems. I googled around and there's an reported issue of Galaxy Nexus battery drain but given the discussion on there I don't think Google is going to dedicate any resource to fixing that.
Which JB point release do you guys think is the best for Galaxy Nexus?
Maybe battery life is not the best one, but you should let the phone settle some days.
The wakening problem is not 4.3 related. Indeed maybe its a usb port/pin problem.
kevinjqiu said:
Which JB point release do you guys think is the best for Galaxy Nexus?
Click to expand...
Click to collapse
4.3
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Same here. Been downgrade to 4.2.2 after frustrate with 4.3 battery. Full charge at morning and low battery arround 5pm. 4.2.2 with 4.3 features also drain battery alot. Now I'm running on TeamEOS 4.2.2
Turn of mobile and network location in location settings and try it for a day
Sent from my Galaxy Nexus using Tapatalk 4
Have you narrowed out that it's none of the apps causing issues?
kevinjqiu said:
So I flashed the latest and "greatest" Android 4.3 on my Galaxy Nexus. After all, this is why we get our nexus devices for, right -- getting the latest updates without begging cell phone vendors or carriers. But Android 4.3 on Galaxy Nexus is driving me nuts -- A full charge won't last me for half a day without much usage at all. The phone intermittently wakes up and won't go back to sleep again, and after I press the power button to put it to stand by, it wakes up a few seconds later. Granted, it's not like that all the time, but it's often enough to be annoying and it's eating the battery alive. Before you ask, yes, I did do a clean install with root.
Very frustrated with this update, and come to think of it, the Android updates of late have not been stellar -- I experienced system random restart when 4.2 hits, and now this...
Sorry for the ranting but I'd like to know if anyone else has experienced similar problems. I googled around and there's an reported issue of Galaxy Nexus battery drain but given the discussion on there I don't think Google is going to dedicate any resource to fixing that.
Which JB point release do you guys think is the best for Galaxy Nexus?
Click to expand...
Click to collapse
As personal experience, much of what you describe did happened to me some time ago and it was cause for some apps that were not optimized for the newer Android API version.
That said, you could try boot into Safe Mode (keep pressed the "Turn Off" at the shutdown screen) and see if keep happening the issues you describe
Use Wakelock Detector app to identify what's draining your battery unusually..
Way ahead of you, I need my tethering.
Sent from my Galaxy Nexus using xda app-developers app
The waking of the phone is most likely caused by a USB malfunction. 4.3 isn't great because Verizon hasn't updated the Nexus radios so the signal is very bad. It goes from LTE to 3g to no signal and back. It does this so ,much that the battery takes a big hit. Find a ROM where you can turn on and off LTE, that should improve your battery.
Sent from my Nexus 10 using Tapatalk 2
The battery drain is because of "always searching for nearby wifi" option
Just disable it ...
Sent from my LG-P500 using xda premium
ive been happy with 4.3 on my VZW Gnex except for constantly having data issues. i downloaded a couple 4.2 roms again to see if they help any. I'm guessing it's because VZW doesn't officially have 4.3 on the Gnex which is why we are seeing data problems. I don't know specifics, maybe binary problems, i dunno. All i do know is it's annoying. I can't even stream iheartradio or pandora at work without it constantly cutting out. then i'll lose data all together and have to reboot the phone to get it back.
kevinjqiu said:
So I flashed the latest and "greatest" Android 4.3 on my Galaxy Nexus. After all, this is why we get our nexus devices for, right -- getting the latest updates without begging cell phone vendors or carriers. But Android 4.3 on Galaxy Nexus is driving me nuts -- A full charge won't last me for half a day without much usage at all. The phone intermittently wakes up and won't go back to sleep again, and after I press the power button to put it to stand by, it wakes up a few seconds later. Granted, it's not like that all the time, but it's often enough to be annoying and it's eating the battery alive. Before you ask, yes, I did do a clean install with root.
Very frustrated with this update, and come to think of it, the Android updates of late have not been stellar -- I experienced system random restart when 4.2 hits, and now this...
Sorry for the ranting but I'd like to know if anyone else has experienced similar problems. I googled around and there's an reported issue of Galaxy Nexus battery drain but given the discussion on there I don't think Google is going to dedicate any resource to fixing that.
Which JB point release do you guys think is the best for Galaxy Nexus?
Click to expand...
Click to collapse
I just had this exact problem and spent a day working on it. It actually has nothing to do with android 4.3; its actually the usb port on the phone, as stated a bit earlier in this thread. More specifically, the pin inside the port is likely shorting with the outer surface of the port, due to it bending slightly. This causes the phone to have funky voltages being detected at the port, and results in the phone behaving as you described (the waking up when the screen is off is actually it thinking its going into charging mode). There are two things to do to fix it. Firstly, take some compressed air and thoroughly clean the port out. Dust that accumulates in the port can cause problems like this, and blowing it out is a relatively simple task. If that doesn't work, the next thing to do is to bend the pin up a bit. Note that this requires you to be a bit gentle, but is not overly difficult. Turn the phone off and remove the battery first, then wedge a very small flat head screwdriver between the pin and the bottom of the port. Very gently apply a bit of pressure, just to bend it up a bit. This doesn't need to be by a lot, in fact when i did it, i could only barely even see a physical difference. Put the battery back in and power the phone back up, and see if it was enough. It fixed all my problems when I did it a week ago.
Don't know what seems to be the problem here
Lasts me 1.5 days with 4hrs On Screen Time Every Time
Don't blame 4.3 if it's an app messing with your battery life
Thanks everyone for chiming in. Here's an update. I uninstalled Go battery widget and now the battery lasts longer. Not as long as I had hoped but better. I installed wakelock detector (thanks for suggesting it) after I uninstalled Go battery widget so I don't have the evidence to prove that Go battery widget is the culprit but the phone seems to be running better now. I also haven't experienced any random wake ups.
Would the data issues more likely be a factor of radio, rather than ROM?
chrisinsocalif said:
Have you narrowed out that it's none of the apps causing issues?
Click to expand...
Click to collapse
Why do that when you can complain on a new thread on xda?! 4.3 sucks because crappy Go apps create wakelocks!
Sent from my Galaxy Nexus using Tapatalk 4
I had the same issues with battery life when I upgraded to 4.3. However, I largely attribute that to T-Mobile's horrible reception in College Station, TX. I used PA, CM10, Purity, Avatar, and a few others but the battery life and performance was not respectable even though they claimed the contrary. This phone is reaching its the end of its product life and no matter how many "optimizations" go under the hood, the hardware is just not apt for ROMs designed for higher end phones.
In the end, I flashed a stock rooted ROM, no more "optimizations", "tweaks", or "improvements"...just a clean ROM. Granted, I in no way mean to offend any developer and their hard work but my experiences with their ROMs left a bitter feeling towards them.
Battery life improved significantly. What used to be 100% to 30% in 8-9 hours turned into 100%-50% in 14 hours. Do keep in mind I'm not a power user. My phone serves as a music player for my ~1 hr commute from and to school, occasional text messages, random redditing, and the random news article before class. In all, I average a little under 2 hours screen time before I deplete the battery to 5-10%.
It's also important to use the appropriate radio for your market.
TL;DR - Try stock and a different radio.
Kernel
I have always seen major differences between Kernels and attributed the majority of battery life to that. Some kernels just work better than others. For example, I know that TONS of people love Franco's kernel, but on my phone battery life is terrible on it. Personally, I like Golden and it seems to really improve battery life.
Same here. I've been having constant data issues with 4.3. So much so that I've just lock myself to 3G and so far, that's been good. 3G->4G or back doesn't work half the time and requires either toggling airplane mode on and off, or rebooting the phone outright.
Going to have to agree. I have VZW and all the 4.3 ROM's I've tried have been less than impressive. I obviously appreciate the dev's work but nothing i've tried is ready to be my DD
We all love to rag on Touchwiz for being a bloated lag beast and pray for the day we can flash CM to get rid of it. However, there is a way to compare stock Touchwiz vs stock Android on two devices with exactly the same hardware specs and surprisingly, the difference is not that significant.
The takeaway is that Touchwiz seems faster loading video while stock Android is faster loading web content - I have a theory for this based upon how Touchwiz parses javascript, but that's another thread . On a benchmark basis the two are within a few hundred points of each other.
Anyway, here is an interesting video of a guy testing the S4 Play Edition (pure Android) vs the S4 Touchwiz Edition, both all stock and brand new with no rom optimizations or debloating. It's interesting and shows that while stock Android may be a bit faster overall, the difference is far less than one might have imagined. Of course the results may be different on the Tab S.
Nice, but surprising report. Guess the skeptics will need something else to complain about.
Sent from my SGP512 using Tapatalk
If only those 2 models were comparing Exynos vs Snapdragon.....then we would have a better understanding.
But I can say for sure, in daily use, Touchwiz is noticeably slower than stock.
kenkiller said:
If only those 2 models were comparing Exynos vs Snapdragon.....then we would have a better understanding.
But I can say for sure, in daily use, Touchwiz is noticeably slower than stock.
Click to expand...
Click to collapse
The thread is about TOUCHWIZ Vs ANDROID not Exynos vs Snapdragon. In this test anyway there doesn't appear to be much difference between the 2 running on the same platform. YMMV.
Apparently, Kitkat 4.4 introduced aggressive cpu throttling at much lower temps than prior Android versions. This may be something that is causing slowdowns you have perceived with prolonged use. While this increases battery life, it crushes performance. Fortunately a good kernel should be able to address this. In this case the hardware is fine, it is the OS which is screwing things up. I guess Google saw that people care more about battery life than blazing performance.
Anyway, here is the article. Interesting.
http://www.tomshardware.com/news/sa...at-performance-cpu-throttling-dvfs,26414.html
Again this is for the S4. Not sure how it applies to the Tab S.
Here is a thread by a dev who was able to disable the DVFS throttling on the s4. He claims that is to blame and not KitKat directly. Will research to see if thee is anything similar for the Tab S.
http://forum.xda-developers.com/showthread.php?t=2674928
Ok, I see that using Wanam Xposed you can disable Samsung DVFS in Advanced Settings. No idea if this works on our Tab S but I disabled it and nothing seemed to break on reboot. This should not increase benchmarks, just stop excessive throttling. One would guess you will see better performance and worse battery life.
We'll see.
mitchellvii said:
Ok, I see that using Wanam Xposed you can disable Samsung DVFS in Advanced Settings. No idea if this works on our Tab S but I disabled it and nothing seemed to break on reboot. This should not increase benchmarks, just stop excessive throttling. One would guess you will see better performance and worse battery life.
We'll see.
Click to expand...
Click to collapse
Hi Mitchell, did the battery life turn out worse?
Still deciding whether to root my tab our not (root loses a tv streaming program in belgian which is quite handy)
All I have to say is load up my alpha rom and see for yourself. It's like the difference between a tablet that came out this month (CM) and a tablet that came out three years ago (TW) performance wise.
I've gone from thinking about selling it to wondering how many years its going to be before they can produce a tablet that makes me want to upgrade.
eousphoros said:
All I have to say is load up my alpha rom and see for yourself. It's like the difference between a tablet that came out this month (CM) and a tablet that came out three years ago (TW) performance wise.
I've gone from thinking about selling it to wondering how many years its going to be before they can produce a tablet that makes me want to upgrade.
Click to expand...
Click to collapse
Soon as you're ready to pop out an 800 I'll be on it.
mitchellvii said:
Soon as you're ready to pop out an 800 I'll be on it.
Click to expand...
Click to collapse
There is a pre-alpha build up for the t800. Unfortunately I don't have one to debug but I hear it boots, touch screen works, but no wifi.
eousphoros said:
There is a pre-alpha build up for the t800. Unfortunately I don't have one to debug but I hear it boots, touch screen works, but no wifi.
Click to expand...
Click to collapse
Oh cool. I'll hold off on trying it until WiFi gets going but will watch for it.
mitchellvii said:
Oh cool. I'll hold off on trying it until WiFi gets going but will watch for it.
Click to expand...
Click to collapse
It will probably be a bit. I don't own the 800 and mainly posted that to show it was possible. If I finish the 700 before the baby is born and no one else has picked it up then I'll try to get it finished.
thomas_pieps said:
Hi Mitchell, did the battery life turn out worse?
Still deciding whether to root my tab our not (root loses a tv streaming program in belgian which is quite handy)
Click to expand...
Click to collapse
You can use rootcloak + xposed module. the tv streaming app will not detect your root.
mitchellvii said:
I guess Google saw that people care more about battery life than blazing performance.
Click to expand...
Click to collapse
Yes and this is one reason why I get sick of people moaning about battery life all the time. It's a mobile device constrained by current technology and what size battery can be squeezed in.
Yet people still expect 3 days battery, super duper speed and a nice slim light device.
For me I accept the limited capabilities of a battery in a mobile device and think they do a pretty good job as it is.
I want a mix of performance and battery, but I'll gladly sacrifice a bit of battery life for a lag free , smooth device.
However the more people moan about battery life the more the scales will tip to battery life at the cost of performance.
I would be willing to except a tablet a mm thicker to have a bigger battery
Sent from my SCH-I545 using XDA Free mobile app
thomas_pieps said:
Hi Mitchell, did the battery life turn out worse?
Still deciding whether to root my tab our not (root loses a tv streaming program in belgian which is quite handy)
Click to expand...
Click to collapse
you can use a root hider application to hide that application from root
I am curious as to why there is very little dev's supporting the lg g3. The samsung on the other hand is being supported alot almost make me think i made a mistake getting the lg g3 but i do really like the phone. I guess i was spoiled before the lg because i had all htc phones and there was an unbelievable amount of support for the evos. so what do you guys think are we at the height of our support or will there be more devs picking this phone up?
garrettstump said:
I am curious as to why there is very little dev's supporting the lg g3. The samsung on the other hand is being supported alot almost make me think i made a mistake getting the lg g3 but i do really like the phone. I guess i was spoiled before the lg because i had all htc phones and there was an unbelievable amount of support for the evos. so what do you guys think are we at the height of our support or will there be more devs picking this phone up?
Click to expand...
Click to collapse
Yes, more people bought it, so there are more devs.
What exactly you want developed for G3?
Kernels? Nah, you can't jump higher than lg did. It's already optimised. You can, of course, add some GCC flags, change toolchain, etc etc etc... For a marginal improvement, at best. Well, you can add undervolting, some modules (ntfs, gamepads, etc), advanced sound control... What else?..
Roms? Well, developing "only for G3!" roms isn't the best idea. Besides, some popular AOSP roms are already ported to g3, ones that haven't been ported don't even have stable 5.0 builds yet. Modding stock rom is almost impossible right now, apktool doesn't fully support neither 5.0, neither lg's special apk's (two apk's with id of 127 sharing resources? LG-way, lol.), so good custom roms aren't even possible yet.
And no, we won't get more support. If you want tons of support - buy Samsung.
I didnt get that too comming from nexus 5 i was expection great dev support for G3 as i consider it the best smartphone specially compare to Lagsung devices...but most of android users see only benchmarks so they go and buy that plastic piece of awfulness....but G3 has a great support..its better to have little and good rather than have 30 same kernels like it was on N5 community...the only thing i can't get is why at least CM isn't official supported!!
pikachukaki said:
I didnt get that too comming from nexus 5 i was expection great dev support for G3 as i consider it the best smartphone specially compare to Lagsung devices...but most of android users see only benchmarks so they go and buy that plastic piece of awfulness....but G3 has a great support..its better to have little and good rather than have 30 same kernels like it was on N5 community...the only thing i can't get is why at least CM isn't official supported!!
Click to expand...
Click to collapse
i agree with both of the posts here and to really answer the first question, there is nothing that i specifically want developed i just was kinda confused as to why the forums are not filled with roms and kernals but you made a good point about saying quality over quantity.. I do really enjoy this phone and consider it the top of the line right now but we will see......
Honestly we have a fair amount of roms at this stage and it will only get better and better but as far as kernels goes I'd wish to see some more with overclocking/undervolting/profiles features in them ..
Sent from my LG-D852 using XDA Free mobile app
Ive had the phone for a month or so now and while the design specs etc are top notch
The performance is not
I find it to be slow and laggy especially the stock messaging app (i know i can use an alternative)
I have the 16gb version and it always seems to be using 88-90% ram at all times with very minimal apps in use
Cant see it being the fact i have the 2gb ram version as previous phones with 2gb ram have performed much better.
Considering getting rid for anther device
^^
Agree fully, had my g3 for just over a week. Bought it from amazon so I have a month to decide.
Phone is terrible for lag, battery usage is woeful.
Perhaps my expectations were too high.
Won't go back to Samsung. Knox has ruined that.
The Moto G Play looks fantastic but no European release.
HTC is speculated to have fantastic new models.
Think the G3 might find itself replaced in the New Year
Sent from my LG-D855 using Tapatalk
nc35 said:
^^
Agree fully, had my g3 for just over a week. Bought it from amazon so I have a month to decide.
Phone is terrible for lag, battery usage is woeful.
Perhaps my expectations were too high.
Won't go back to Samsung. Knox has ruined that.
The Moto G Play looks fantastic but no European release.
HTC is speculated to have fantastic new models.
Think the G3 might find itself replaced in the New Year
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Been offered a straight trade for HTC one M8 might take them up on it
As a person coming from Samsung S2, S3, Note 3, I can say that Lg is doing a great job with the G2/G3 stock software! Way better than Samsung! Yes you'll find fingerprint features and some other useless bells and whistles, but LG software is solid, almost lag free, and battery life is king!
During my lifetime with Samsung, I spent most of my time cheating its software with Cyanogenmod.
So, would I be sad to not have the same amount of support on S5? Definitely no! I think what we have is valuable and I haven't felt yet that I need to run away to CM11/12.
manemzjum said:
Ive had the phone for a month or so now and while the design specs etc are top notch
The performance is not
I find it to be slow and laggy especially the stock messaging app (i know i can use an alternative)
I have the 16gb version and it always seems to be using 88-90% ram at all times with very minimal apps in use
Cant see it being the fact i have the 2gb ram version as previous phones with 2gb ram have performed much better.
Considering getting rid for anther device
Click to expand...
Click to collapse
I guess my question with those who see terrible battery life, what is it exactly you expect? I always here "terrible battery life", or "laggy". But no one backs it up with examples.
So, for those that are seeing poor battery life, answer these questions:
What is "poor" in your mind? Please provide a measurement such as you expect x amount of hours.
Exactly what are you using your phone for? Are you playing games for hours, shooting and/or viewing HD videos? Listenting to music?
After x hours of usage, how much battery is left after use (and whatever you were doing)?
For those with lag, answer these questions:
How are defining lag? Where are you seeing it and how are you perceiving it?
What apps do you have installed and how many?
What is the amount of storage you have left?
I know some have stated they see lag in the UI such as when they open a drawer, or swipe between screens and such. I guess I've never noticed that before, so maybe they come from a different phone that responded better in their eyes. Things that can help are possibly reducing the animation, but a possible issue could be the screen size. This phone packs a lot more pixels in it than the S5, so I could see how rendering on a screen with a larger pixel density could cause this. However, for me, I don't really notice it, and even if it is there, it must not be a huge amount or else I'd notice it.
As for battery life, I don't know what people are expecting. I get at least a days (24 hours) worth. Now, granted I'm running Greenify which has helped me on other phones, so I'm sure that has a hand in it. However, there was a time I wasn't running Greenify at first with this phone and I remember having the phone charged at 100% when I went to bed, took it off the charger, left it on (I used it as an alarm clock plus as my on-call phone) and when I woke up 6+ hours later, it was STILL at 100%. Adding Greenify has helped to prevent apps from wake locking, but that's not the phone's fault. That's how some apps are written and that in and of itself can cause battery drain, but it's even worse if you out-right kill the app/service all the time.
I make and take phone calls (not all day, mind you), I send and receive texts (not every minute). I do play games (Game of War a lot) and that does drain the battery, but that's going to happen on any phone. I've listen to music on my phone, especially when driving to/from work and other errands. One time, I must have logged over 2 hours on Power Amp. I wanted to see how much it drained the battery, so I kept note of where the battery was at when I started listening and where it was when I stopped listening. Over a two hour total period of listening to music, the battery drained 2%. Not bad if you ask me.
I'm just curious because right now, with this phone, I'm getting better battery life than I did with my RAZR MAXX and my RAZR HD phones. This phone I could possibly go two days before charging. After about 36 hours, I'm at 40% battery, so I could probably go another 12 hours, but when I get to 40%, that's when I start charging back up again.
I'm not trying to dispute what people are saying. I'm just curious as to what people are expecting vs. what they are getting (or perceive as getting) from this phone. Again, most of the time, we get generic statements as "battery life sucks" or "it lags". Great. Please back that up with examples because otherwise, it's all in the eye of the beholder as to what great or sucky battery life is and/or what lag is.
Just to show, im currently at 60% after 21 hours of use. That's with phone calls, playing Game of War, texting, etc. I've attached the screenshot as well.
Just comparing to my Note 3, with stock FW but apex launcher.
Battery would last in excess of a day with quite heavy use, games Internet browsing etc. BT always on auto brightness.
Apps would also open instantly or as expected.
The G3 can has a battery life of less than 4hrs with little or no use. Consumes 18-19% in 7hrs overnight.
Finding myself charging the phone at every opportunity.
I know the Note 3 didn't come with qi, but the qi on the G3 is sooo picky. 1mm off and it doesn't charge.
Using stock launcher just pressing home, first the wallpaper loads followed by the icons then the widgets. No what would be called snappy.
And OMG does it get hot!!! For no reason at all. Not playing games, just emails and Web browsing.
So now I am left wondering if the phone is faulty.
Sent from my LG-D855 using Tapatalk
iBolski said:
I guess my question with those who see terrible battery life, what is it exactly you expect? I always here "terrible battery life", or "laggy". But no one backs it up with examples.
So, for those that are seeing poor battery life, answer these questions:
What is "poor" in your mind? Please provide a measurement such as you expect x amount of hours.
Exactly what are you using your phone for? Are you playing games for hours, shooting and/or viewing HD videos? Listenting to music?
After x hours of usage, how much battery is left after use (and whatever you were doing)?
For those with lag, answer these questions:
How are defining lag? Where are you seeing it and how are you perceiving it?
What apps do you have installed and how many?
What is the amount of storage you have left?
Click to expand...
Click to collapse
I have both "issues".
"poor" is g3's screen-on time on 5.0 while browsing using 4g. 5-5:30 hours on latest firmwares isn't much. It was nearly 7 hours on 4.4.2... I always set brightness to 20% auto, lighting conditions are always same.
I use phone for browsing and listening to locally stored music via Bluetooth. No watching or shooting videos or playing games.
After 5 hours of 4g web browsing i am left with empty battery.
Lag:
I define lag as "animation stuttering". I am seeing it everywhere: Vkontakte, Google Play Store, while opening drawer, switching tasks, etc... It lags often, but not always.
I have 47 user apps installed, 0 additional system apps.
The only apps that keep background services or use alarms are: Aqua mail, LMT, SBH52 smart headset, Titanium backup.
There are 4 apps using GCM for push.
There are 6 accounts (Google, Shazam, Skype, VK, tutu.ru and one money app) at sync section.
And i have got 5.4 gb free out of 25 on intsd. Shouldn't slow down writing much.
A perfect setup, right? But it still lags on official firmware.
I would assume you aren't running anything like Greenify, etc. What it sounds like is there are a lot of wake locks going on. That's where Greenify comes in. I also turn off a lot of syncs as I don't need them. As you can see with my screenshot, 60% is where I was at after 21 hours so thus phone can definitely get good battery life. But, if you do a lot of stuff for hours, no phone can keep it's battery life for long. Also, with the quad hd screen this phone has, that is a big drain, but even then, I'm getting great battery life.
Another thing with going to 5.0, it's best to start fresh. Do a factory data reset and start from scratch. Going from 4.x to 5.0, especially with Lollipop, had a lot of changes underneath the hood. There are others getting better or the same battery life, but i also think it all depends on usage.
I dont know with other guys here.but i am very happy with the lg g3 forums
Sent from my LG-D855 using XDA Premium HD app
I already dumped mine at a huge loss. I would say worst phone ever, but that goes to my first Android, the Moto Backflip. Thank goodness my other phone is a M8.
Battery is kinda the only area i don't really have a problem with the phone its not the best but its not the worst
As someone has previously said i also came from a note 3 which in performance blows the G3 out of the water snappy and quick with no lag and instant app openings
Greenify shouldn't be something you should need to do to get rid of lag on a quad core 2.5ghz device with 2GB of ram
Out of the box the thing uses 88% ram considering the actual ROM itself is like 1.6gb just HOW is that possible if the entire contents of the ROM was loaded it into RAM should still only use 76%
Its a high end high spec device extremely poorly calibrated i have an old galaxy S3 that out performs it
To say im bitterly disappointed with this device is an understatement
Only thing i'm having problems with is the fact that the ram is always overload. Used titanium to remove and freeze alot of stuff but still the ram usage is about 1.3 to 1.6gb.
This is on stock rom which is very good to me with no lag and everything an launcher needs.
Battery life from the G3 is very good, on my previous phone I was affraid to leave the house if the battery wasn't filled to 100% with the G3 i left yesterday at 62% and returned from work with still 46% (off course with no heavy use) while my data is always on.
Conclusion for me after a month of use, good value for the money.
manemzjum said:
Battery is kinda the only area i don't really have a problem with the phone its not the best but its not the worst
As someone has previously said i also came from a note 3 which in performance blows the G3 out of the water snappy and quick with no lag and instant app openings
Greenify shouldn't be something you should need to do to get rid of lag on a quad core 2.5ghz device with 2GB of ram
Out of the box the thing uses 88% ram considering the actual ROM itself is like 1.6gb just HOW is that possible if the entire contents of the ROM was loaded it into RAM should still only use 76%
Its a high end high spec device extremely poorly calibrated i have an old galaxy S3 that out performs it
To say im bitterly disappointed with this device is an understatement
Click to expand...
Click to collapse
Greenify isn't for lag. It's for battery life.
Again, each to his own. I think it all depends on the perception of the user and what they expect and what they've gotten in the past from other phones.
Form me, this phone blows the RAZR MAXX and RAZR HD out of the water, which is what I came from and I get great battery life (well over 36 hours) before I have to recharge. And even then, at 40%, I probably could go another 12 hours but I choose not to.
Just last night, before I went to bed, the phone was at 100%. When I woke up 6 hours later, it went down only 2%, so I had 98% battery left. I've since used it to check email, read the news, played about 45 minutes of Game of War and did some updates via Google Play and I'm at 90%. That's after 9 hours since I last charged. I'd say those are pretty darn good stats for me.
Again, mileage may vary from user to user and what they expect. And from the responses I'm seeing, that's what I'm gathering. Some are saying the phone is great, others say it's okay, and others say it's awful coming from another phone. So, that definitely shows that it's all in the eye of the beholder.
But I appreciate what everyone has posted. It does appear that some who didn't like this phone have been able to find a phone that works great for them. I always try to state why a phone works great "for me" because that's what it is. It's not necessarily going to work great for someone else, but I also don't want to steer someone towards this phone if it doesn't meet their needs, so I try to explain why and how it works for me as I'm the user of this phone, and everyone else might use it differently.
Ciao!
I don't get why a lot of people are complaining about lag and support and s*** like that.
You are getting lag probably because:
(A) You don't know how to use your phone.
(B) You picked up the 16GB model (which only has 2GB RAM
(C) You're not rooted (seriously, who doesn't root their phones nowadays)
When I got this phone, I didn't have it rooted for a month. Everything was smooth despite having a lot of apps installed. It only became a lag machine when I installed Facebook and its Messenger app.
Yes there are lags from time to time, but do iPhones not lag? Of course they do, all phones do. I don't see all you guys' point.
A good phone doesn't need any sort of custom ROM and kernel, etc etc. Mine has always been on Stock ROM and Kernel, minimal lag. iPhone-like smoothness, I must say (but plus good multitasking. iOS multitasking is s***) In fact, when I upgraded to Android 5.0, it got even better.
I have stayed stock most of the time but I always have Greenify installed, (but battery life was still great before rooting and installing Greenify)
You people are just picky.
Not sure why people are seeing 18%+ drop in battery overnight in standby mode. Must either have a lot of synching going on or a misbehaving app or two.
Me, when I'm at home, WiFi is turned on. I have minimal syncing (apps, calendar, google+, photos).
Here is a screenshot I took this morning. When I first woke up, I was down to 98% overnight (was at 100% when I went to bed at midnight and when I woke at 6:30 am, it dropped only 2%).
At the time I took this screenshot, I had already read the news, did some updates, checked emails, and played about 30 minutes of Game of War and I was down to 94%. That seems like good battery life to me.
Of course, if you really want to improve the battery life of this phone, maybe you can go to Amazon and get this upgrade for the G3:
http://www.amazon.com/Warranty-Zero...id=1411938311&sr=8-1&keywords=zerolemon+lg+g3
:silly: :laugh: