So guys I created this thread because I am very angry! I have on my nexus the latest paranoid Android build and it is annoying as hell. It reboots often and gets so slow that u can't imagine. Can anyone explain that to me. I tried so many things to fix this but nothing really helped. -.- by the way I am on ak kernel purity v30
Sent from my Galaxy Nexus using xda app-developers app
Try a different kernel
Why don't you flash the stock 4.2.2 update. It's fantastic,very smooth, very responsive , and quick. A hell of a lot better then 4.1
ironside2011 said:
Why don't you flash the stock 4.2.2 update. It's fantastic,very smooth, very responsive , and quick. A hell of a lot better then 4.1
Click to expand...
Click to collapse
It's more interesting in terms of new features indeed. Unfortunately is by far more sluggish and buggy than rock stable jzo54k. Scrolling lag that comes after a while take away all the joy of using 4.2.2. It actually made me downgrade to 4.1.2. I've never thought I would admit that but deodexed CNA_3.8.0 feels much smoother and lighter than odexed stock JDQ39 (that feels really smooth right after reboot)
Try latest ak v014 kernel, sounds kernel related, either way that's the best kernel currently for galaxy nexus an more dramatically improve your gnex speed an performance.
Sent from my Galaxy Nexus using xda premium
Franco
Sent from my Galaxy Nexus using Tapatalk 2
Sveke said:
Franco
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm using over clocked at 1.4GHZ running everything smoothly
Why do people keep suggesting switch kernels? With the quantity of people with lag issues, it's definitely AOSP related. All switching kernels will do is sometimes wipe cache and dalvik or the users usually wipe cache and dalvik which supposedly helps for a bit along with the reboot which definitely helps for a bit. Custom kernels may help performance a bit but they don't clear whatever's happening in the code that causes the issue for many?
tiny4579 said:
Why do people keep suggesting switch kernels? With the quantity of people with lag issues, it's definitely AOSP related. All switching kernels will do is sometimes wipe cache and dalvik or the users usually wipe cache and dalvik which supposedly helps for a bit along with the reboot which definitely helps for a bit. Custom kernels may help performance a bit but they don't clear whatever's happening in the code that causes the issue for many?
Click to expand...
Click to collapse
Its probably not directly AOSP related or else every single android device would have the issue on an AOSP ROM.
If I had to guess I'd say that people just aren't maintaining their phone. They let garbage data build up in the internal storage, collect tons of apps that they almost never use and almost never reboot. With just a little upkeep I've had almost none of the issues people are complaining about and when I did it was gone as soon as I did some tidying up.
I mentioned it very often now in different thread as it seems a very common issue - did you try lagfix from PlayStore? This helped me.
http://forum.xda-developers.com/showpost.php?p=39273944&postcount=21
Not a final solution, but it works (for some time) and I hope Google fixes it in Android 5...
hudl said:
I mentioned it very often now in different thread as it seems a very common issue - did you try lagfix from PlayStore? This helped me.
http://forum.xda-developers.com/showpost.php?p=39273944&postcount=21
Not a final solution, but it works (for some time) and I hope Google fixes it in Android 5...
Click to expand...
Click to collapse
Actually it fixed my all problems related to performance
I had these slow down problem too for almost 2 months because my available storage was too low (around 1gb).
Then I realized that its related to trimming problem.
So far the combo of lagfix and seeder is working good.
No lag n other problems at all
Sent from my Galaxy Nexus using xda premium
063_XOBX said:
If I had to guess I'd say that people just aren't maintaining their phone. They let garbage data build up in the internal storage, collect tons of apps that they almost never use and almost never reboot. With just a little upkeep I've had almost none of the issues people are complaining about and when I did it was gone as soon as I did some tidying up.
Click to expand...
Click to collapse
It can be very true. However I use my device in exactly the same way I used to do while running previous versions of JB. I have installed the almost exactly the same amount and sort of apps. I try to keep my gnex clean. I've never had less free memory than 4 GB. To be honest I don't remember when I had to reboot my nexus before 4.2.2 was released cos I've never had this low fps scrolling issue until JDQ39. I am not trying to advertise any rom. I've always been huge fan of stock due to its stability and smoothness, but Purity Rom was the only one I haven't noticed this bug so far.
No response from Thread creator, he is no care with our comments...lol..
Sent from my Galaxy Nexus using Tapatalk 2
i'm using Rootbox, it's amazing!
Related
I want to try one of the 2.3 Roms based off of the leaks but I wanted to check with you guys and see what's the best Rom?
Sent from my SPH-D700 using XDA App
jworkcoo said:
I want to try one of the 2.3 Roms based off of the leaks but I wanted to check with you guys and see what's the best Rom?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well, there's no perfect answer to this question. The best 2.3 ROM is the one that works best on your phone. Every ROM performs just a bit differently on each person's phone. Apps added and other changes made can also effect this. Our Epics can be like a second girlfriend...one minute giving you all kinds of love and happiness and the next minute can be a real pain in the ass...wait maybe I need a new girlfriend!
Sent from my SPH-D700 using XDA Premium App
JohnCorleone said:
Well, there's no perfect answer to this question. The best 2.3 ROM is the one that works best on your phone. Every ROM performs just a bit differently on each person's phone. Apps added and other changes made can also effect this. Our Epics can be like a second girlfriend...one minute giving you all kinds of love and happiness and the next minute can be a real pain in the ass...wait maybe I need a new girlfriend!
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
HA! Perfect description John.
To the OP there are several good ROMs like Bamboozle, Bonsai, Scrambled Eggs...back up your phone and start flashing. I went to GB and never looked back.
kennyglass123 said:
HA! Perfect description John.
To the OP there are several good ROMs like Bamboozle, Bonsai, Scrambled Eggs...back up your phone and start flashing. I went to GB and never looked back.
Click to expand...
Click to collapse
^^^^
This. Just try them all and see what happens
Sent from my SPH-D700 using XDA Premium App
Esteway.619 said:
^^^^
This. Just try them all and see what happens
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yup, its all about trial and error. I can't tell you how many times I have tried a ROM and its worked perfect only for other users to report constant force closes. When you do find the ROMs that work perfect you will be a very happy camper. It pains me to run a stock setup now.
Sent from my SPH-D700 using XDA Premium App
Thanks! I will try a couple later on. It will be hard to leave the Regeneration Rom though....I love it.
Sent from my SPH-D700 using XDA App
jworkcoo said:
Thanks! I will try a couple later on. It will be hard to leave the Regeneration Rom though....I love it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's one of my two daily setups as well. CompKid nailed it. The other is SRF 1.2 by the way
Sent from my SPH-D700 using XDA Premium App
OP, you should make this a poll.. im curious to see which one everyone uses
ksmullins88 said:
OP, you should make this a poll.. im curious to see which one everyone uses
Click to expand...
Click to collapse
I agree. I have been wondering what a lot of people are using as their dailies.
Sent from my SPH-D700 using XDA Premium App
CM7.
jk. But I'd check out acs bamboozled...best gb rom I've used so far.
I've tried two (or three) 2.3 based roms and there has been a couple of things that have always caused me to go back to SRF 1.2:
No custom kernels = no overclock - I'm not a huge overclocking type of guy, but I always like to have it clocked at 1.12 or 1.2 ghz, just enough to keep it smooth but not high enough to run it hot or drain my battery.
No custom kernels = Cannot use Galaxy Tuner - I use Google Music as my primary source of car music, which means I needed to find an external app to use as an equalizer. Voodoo sound didn't work and Tuner froze on me every time I tried to use it.
Still Very buggy - I've run into a few bugs that have always irritated me, no matter how small they were. Whether it's something that freezes my phone or just kills the frame rate, I've just always been bugged (get it?) by bugs.
But where there is bad things, there have been a lot of good things that I absolutely loved about 2.3, almost enough to stay with it:
Live Backgrounds - For me, they've seem to have gotten better (stock ones anyways) and, as far as I could tell, they don't murder my battery or frame rate. The one I loved the most was this awesome looking clock that was a bunch of circles. It's hard to explain...
Screen off Animation - More eye candy, but awesome eye candy. Not much to say other then I love watching my phone turn off
Everything just seemed so smooth - Scrolling, opening apps up, etc, just seemed so fluid and clean, even if the frame rate was dropping for some reasons.
------
Those are some of my personal pro's and con's on deciding whether to run 2.3 at this time or not. For me, the con's on top were more important then the pro's on the bottom. Needs are different for each person so I'm sticking with 2.2 for now until either the official release of 2.3 is out or we can start adding kernels and themes (etc etc).
T-980 said:
I've tried two (or three) 2.3 based roms and there has been a couple of things that have always caused me to go back to SRF 1.2:
No custom kernels = no overclock - I'm not a huge overclocking type of guy, but I always like to have it clocked at 1.12 or 1.2 ghz, just enough to keep it smooth but not high enough to run it hot or drain my battery.
No custom kernels = Cannot use Galaxy Tuner - I use Google Music as my primary source of car music, which means I needed to find an external app to use as an equalizer. Voodoo sound didn't work and Tuner froze on me every time I tried to use it.
Still Very buggy - I've run into a few bugs that have always irritated me, no matter how small they were. Whether it's something that freezes my phone or just kills the frame rate, I've just always been bugged (get it?) by bugs.
But where there is bad things, there have been a lot of good things that I absolutely loved about 2.3, almost enough to stay with it:
Live Backgrounds - For me, they've seem to have gotten better (stock ones anyways) and, as far as I could tell, they don't murder my battery or frame rate. The one I loved the most was this awesome looking clock that was a bunch of circles. It's hard to explain...
Screen off Animation - More eye candy, but awesome eye candy. Not much to say other then I love watching my phone turn off
Everything just seemed so smooth - Scrolling, opening apps up, etc, just seemed so fluid and clean, even if the frame rate was dropping for some reasons.
------
Those are some of my personal pro's and con's on deciding whether to run 2.3 at this time or not. For me, the con's on top were more important then the pro's on the bottom. Needs are different for each person so I'm sticking with 2.2 for now until either the official release of 2.3 is out or we can start adding kernels and themes (etc etc).
Click to expand...
Click to collapse
You know there can be no custom kernels until source code is released. But as for overclocking, many have had success with Tegrak from the market that has allowed overclocking on the GB leaked ROMS.
kennyglass123 said:
You know there can be no custom kernels until source code is released. But as for overclocking, many have had success with Tegrak from the market that has allowed overclocking on the GB leaked ROMS.
Click to expand...
Click to collapse
Yea, I'm slowly learning all that, I just didn't know at the time. As for Tegrak, I heard it's a major drain on the battery for some reason, but maybe results vary from user to user. Overclocking wasn't a huge concern for me, it was the other two on there that kind of got to me. I'm still happy with 2.2 so that's why I've decided to wait it out
Install acs updater and try them all
Its in the market
Sent from my SPH-D700 using XDA Premium App
hmm i never tried compkid's regeneration or inception roms. How are they?
as for the topic we are on now, i left acs1.2 the day eg22 came out and yeah al though for some things i would love to go back to acs1.2 but the scale is heavier for me on the gb side.
I used go green, team era's scrambled eggs and tried all the randomrom 2.3 versions (eagle, egret, osprey). The most stable rom for me is randomrom osprey. It is fast enough, great on battery and everything works well with it (other lauchers, apps, etc). As for scrambled eggs, man i loved how snappy that rom was. It was extremely quick upon the click but unfortunately it wasnt working that good with a few launcher and apps and way too many force closes but still fast. Even though i feel scrambled eggs was snappier than osprey, i did receive much higher quadrant scores with osprey (not that quadrant actally matters to me, just for the sake of seeing the scores).
GoGreen was meh for me and i am definitely anticipating an update for scrambled eggs..
I first went with Bamboozle, and it was good. Then one day there are 3 EG22 Roms here it seemed.
So I tried RandomRom and I was having an awful time after 2 days with FC's and reboots.
I then loaded Scrabmled Eggs yesterday and I have been clean (other than google Nav). I am checking battery life now, but I am doing better now than I was with RandomRom. I have to think I was doing something wrong with RandomRom cuz my battery life was terrible and the FC's. I did the same thing each time I installed them, but as said before, each phone is different.
Good luck!
Neckberg said:
I first went with Bamboozle, and it was good. Then one day there are 3 EG22 Roms here it seemed.
So I tried RandomRom and I was having an awful time after 2 days with FC's and reboots.
I then loaded Scrabmled Eggs yesterday and I have been clean (other than google Nav). I am checking battery life now, but I am doing better now than I was with RandomRom. I have to think I was doing something wrong with RandomRom cuz my battery life was terrible and the FC's. I did the same thing each time I installed them, but as said before, each phone is different.
Good luck!
Click to expand...
Click to collapse
Curious, how did you go about flashing RandomROM? It was the first EG22 rom i tried when it initially came out and all the updates since have worked flawlessly for me.
Sent from my superEPIC 4G using XDA Premium App
I was running the scrambled eg22v4, just installed v7 this morning and so far it seems a little better. Only complaint is my battery seems to be going down a little faster, but it could be cuz I've been messing with loading stuff and resetting everything up. I'll give more feedback when I've had it a few days. ACS Go Green wasn't bad either.
Compared to the other phones I have used I have noticed that browser performance on my GNex seems slow. I have used both stock browser and Chrome. Has anyone else noticed this or have any tips on increasing browser performance? I am using a pretty clean rom (MMuzzy 4.2.1).
+1 this, both the default browser and especially chrome is very slow, I've had better results with third party browsers (dolphin browser, firefox etc.)
Never noticed any problems on my galaxy Nexus. Used cm + Franco. Buttery smooth since day one
Sent from my Nexus 4 using xda premium
I should try Franco kernel. I have never done just a kernel swap before. I'll have to read up on the procedure and any risks.
zephiK said:
Never noticed any problems on my galaxy Nexus. Used cm + Franco. Buttery smooth since day one
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
What other devices have you used for comparison? Comparing to an iphone 4s, which i got for my wife the same time i got my gnex, it is night and day how much faster the browser is.
kineticbits said:
I should try Franco kernel. I have never done just a kernel swap before. I'll have to read up on the procedure and any risks.
Click to expand...
Click to collapse
It won't make a difference.
Sent from my Galaxy Nexus using Tapatalk 2
kineticbits said:
I should try Franco kernel. I have never done just a kernel swap before. I'll have to read up on the procedure and any risks.
Click to expand...
Click to collapse
There really any risks. It's the same process as flashing a ROM.
Boot into Recovery, Wipe Dalvik and Cache, Flash Kernel.
Upon flashing a new ROM, you will need to reflash the kernel after flashing the ROM as flashing the ROM will override your existing kernel with the packaged kernel that comes with the ROM.
What other devices have you used for comparison? Comparing to an iphone 4s, which i got for my wife the same time i got my gnex, it is night and day how much faster the browser is.
Click to expand...
Click to collapse
I have a iPod Touch 3rd Generation (really just use it for music nowadays), Transformer, NS, GN, N4.
The only browsing problem out of those devices I had was my Nexus S where stock browser was laggy but it may of been fixed in 4.0.X. On GB, the experience wasn't very good. iOS browsing is definitely smooth, but I can't bother to use it anymore because the screen is way too small.
I don't use the GN anymore, I gave it to a family member but the browsing has been nothing but exceptional. I can't even choose whether to use AOSP browser (stock on GN) or chrome.
It won't make a difference.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Better than doing nothing. It would make a difference on the overall phone performance that's for sure. Use Trickster Mod with Franco Kernel to customize the kernel in terms of color, sound, frequencies, etc.
zephiK said:
There really any risks. It's the same process as flashing a ROM.
Boot into Recovery, Wipe Dalvik and Cache, Flash Kernel.
Upon flashing a new ROM, you will need to reflash the kernel after flashing the ROM as flashing the ROM will override your existing kernel with the packaged kernel that comes with the ROM.
I have a iPod Touch 3rd Generation (really just use it for music nowadays), Transformer, NS, GN, N4.
The only browsing problem out of those devices I had was my Nexus S where stock browser was laggy but it may of been fixed in 4.0.X. On GB, the experience wasn't very good. iOS browsing is definitely smooth, but I can't bother to use it anymore because the screen is way too small.
I don't use the GN anymore, I gave it to a family member but the browsing has been nothing but exceptional. I can't even choose whether to use AOSP browser (stock on GN) or chrome.
Better than doing nothing. It would make a difference on the overall phone performance that's for sure. Use Trickster Mod with Franco Kernel to customize the kernel in terms of color, sound, frequencies, etc.
Click to expand...
Click to collapse
I highly disagree that using a custom kernel on Android 4.2.1 will make a noticeable difference. It is my humble opinion that Google has optimized this device as far as possible to the point that these third-party developers can't squeeze out anymore performance - if it was possible the Google engineers would have done it themselves.
I use to be a huge Trinity fan, used it since the ICS days and swore up and down by it - now I just run with stock. Do I notice a difference? NOPE.
akira02rex said:
I highly disagree that using a custom kernel on Android 4.2.1 will make a noticeable difference. It is my humble opinion that Google has optimized this device as far as possible to the point that these third-party developers can't squeeze out anymore performance - if it was possible the Google engineers would have done it themselves.
I use to be a huge Trinity fan, used it since the ICS days and swore up and down by it - now I just run with stock. Do I notice a difference? NOPE.
Click to expand...
Click to collapse
By saying that you're implying that NO custom kernel on 4.2.1 on ANY phones it would make a difference. So you're calling everybody a liar in kernel threads because they feel a placebo? It certainly makes a noticeable difference in overall phone performance as well as battery.
Google has not optimized the device as far as possible by ANY means. There are always room for improvement in every device and software that is ever released. As more optimizations are done, it is harder to optimize but there is ALWAYS room for improvement. ALWAYS.
On the Nexus 4, your statement is outright wrong. Google didn't optimize the kernel by any means, there are many problems with it. It is stable for sure, but there is so much Google could of done to improve the kernel where kernel developers are doing quite the job on improving upon it. This goes the same for the Galaxy Nexus as it is the Galaxy Nexus forum.
Colors on stock kernel vs. custom kernel with Color Control... difference? YUP.
Benchmark differences? YUP. (benchmarks dont really mean anything for real-time performance but for some people they are so 'woah' about it)
Improved WiFi performance? YUP. Proved in many threads with newer sources.
Not to mention the PGM module? PGM is so awesome for the Galaxy Nexus that it can't be given up
For me the speed on Stock Android JB 4.2.1 browser is really good but I have issue with uploading:
When I upload files to e.g. xda-developers, ge.tt, mediafire, etc. uploading will fail what have not happened on JB 4.1.2 and older Jelly Bean ROMs.
So if I want to upload file to internet I have to use Chrome.
I use 3G on my Nexus pretty much and the speed is really good compared to other browsers e.g. Chrome, Dolphin.
if there is one thing where the galaxy nexus is really great is browser performance, the stock browser works fantastic, stock or with some custom kernel, the browsing experience is almost the same.. if your browser performance is bad may be your connection or any other issue, because atleast in my case it works perfect.
I just recently switched back to Dolphin after giving Chrome a good month or so to wow me. I don't think it is a lot faster than Chrome, but it is faster. Plus, extensions.
I've used Quick ICS Browser for ages and it's great. Recently started using Opera and it's pretty sweet too, although nut as feature-packed.
Sent from my Galaxy Nexus using Tapatalk 2
Hello whoever is reading this,
I'm getting real tired of how slow my phone has consistently been slow for months now. I've tried a bunch of roms and kernels in combination, and while it seems to work smoothly after a clean flash, it slows back down to its usual laggy state within a few days (or even hours!)
I partially blame the age of the phone, as it's old processor probably can't handle all of the customizations being thrown at it that are really being developed for the Nexus 4. But aside from that, everyone in every rom or kernel thread is always raving about how "buttery smooth" or "lightning fast", or whatever else their phone is, claiming performance is awesome. It could just be that all those users are just used to some lag, but I'm really starting to feel like I'm the only one who has such performance issues.
For this reason I'm wondering if it's possible that something hardware-wise might be starting to die, similar to how "cheap memory is killing off Google Nexus 7". Is this possible?
Is there any app that can run hardware tests to check for things like that? I would love to see if my suspicions are correct or totally wrong. Is there anything else I should try?
I'm currently running the latest ak47 rom (AOKP Milestone 2 on top of VANIR (linaro), and using Fancy Kernel. I've found the performance is pretty good compared to other roms I've tried but I still find myself waiting seconds for the app drawer to open, to scroll through pages in the app drawer, etc.
Any help would be much appreciated. Thanks.
Hmmm... if it is anything related to what was happening with the Nexus 7, then you've probably heard what Android 4.3 did for it. I'm writing this from my Galaxy Nexus, and it hasn't been faster since 4.1; whatever 4.3 did for the Nexus 7 has a similar effect on my GNexus. It took a couple days, but I have my butter back!
Before the update, I was in the same boat as you. Even the keyboard was ridiculously laggy. Now? Buttery. Not Nexus 4 buttery, but buttery.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
CWalkop said:
Hmmm... if it is anything related to what was happening with the Nexus 7, then you've probably heard what Android 4.3 did for it. I'm writing this from my Galaxy Nexus, and it hasn't been faster since 4.1; whatever 4.3 did for the Nexus 7 has a similar effect on my GNexus. It took a couple days, but I have my butter back!
Before the update, I was in the same boat as you. Even the keyboard was ridiculously laggy. Now? Buttery. Not Nexus 4 buttery, but buttery.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
I didn't hear what 4.3 did, but I gather that it improved the speed? Sweet, maybe I'll try that. My issue is I'm too addicted to AOKP
But I'll have to try a stock 4.3 rom or something and hopefully I'll find the same results as you. Thanks for your input!
My question about an app that runs hardware integrity tests still stands.
jakis39 said:
I didn't hear what 4.3 did, but I gather that it improved the speed? Sweet, maybe I'll try that. My issue is I'm too addicted to AOKP
But I'll have to try a stock 4.3 rom or something and hopefully I'll find the same results as you. Thanks for your input!
My question about an app that runs hardware integrity tests still stands.
Click to expand...
Click to collapse
No problem! And it provided a lot of behind-the-scenes improvements for graphics processing. It also made FSTRIM turned on by default in the system; it will run whenever the battery is above ~70% and the device is idle. It basically stops the device from needing to perform multiple actions in the storage whenever it needs to read or write. You only notice the effects of it NOT being present over many write cycles, which is why performance may seem to have deteriorated over time.
And yeah, custom just gives you so many choices! But a few days with 4.3 should REALLY ramp up your performance. It takes a little while for FSTRIM to do it's magic. App drawer opens after 0.7 seconds or so, and swiping between pages is quite fluid and responsive.
Glad to be of service! Hope it helps out.
Sent from my Nexus 10 using Tapatalk 4 Beta
Aside from 4.3, I've found that if you goto Developer options, and lower the Transition, Window, and Animator scales from 1x down to .5x things seem to move more smoothly. Albeit they only reduce animation times, the visual effect may be enough. I also use Nova Prime launcher and turn animations to "Nova" speed. Things like the app drawer open instantly. Absolutely zero lag. What I'm running is in my sig...
jakis39 said:
Hello whoever is reading this,
I'm getting real tired of how slow my phone has consistently been slow for months now. I've tried a bunch of roms and kernels in combination, and while it seems to work smoothly after a clean flash, it slows back down to its usual laggy state within a few days (or even hours!)
SNIP
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
This frustrated me for a long time until I came across this app (root needed):
LagFix Free: https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en
XDA thread: http://forum.xda-developers.com/showthread.php?t=2104326#fm
"Some Android users suffer from poor performance after some days/weeks of heavy usage. This is due to a well-known TRIM bug affecting these devices. The source of the problem is that internal storage is not properly TRIMmed when needed. It is also well-known fact that running fstrim Linux tool from time to time fixes the issue until internal memory runs out of free blocks. LagFix is a user-friendly implementation of fstrim utility. It allows you to select which partitions to trim (you should leave defaults unless you know what you are doing) and run the process easily."
Android 4.3 finally implements this fix, so if you go a 4.3 ROM, you won't need this.
Yep, like they all said, 4.3 fixes that with things like TRIM, and I can attest to that firsthand.
Sent from my Galaxy Nexus using xda app-developers app
I must say that the phone is faster on 4.3, but my battery life is horrible when comparing to 4.1.1 or even 4.2.2, especially when using the phone.
I don't know if it's true or I'm too bugged about it. Could someone please confirm it to me?
rafa1696 said:
I must say that the phone is faster on 4.3, but my battery life is horrible when comparing to 4.1.1 or even 4.2.2, especially when using the phone.
I don't know if it's true or I'm too bugged about it. Could someone please confirm it to me?
Click to expand...
Click to collapse
infact my battery life is improved a lot after 4.3
sent from my sexy Nexy
paarthdesai said:
infact my battery life is improved a lot after 4.3
sent from my sexy Nexy
Click to expand...
Click to collapse
^^^that^^^
and for some reason, one screen time was BETTER than 4.2
I guess it's just bad luck haha.
Gonna test it calmly to be sure.
I have read conflicting reports that some say 4.3 is GOOD on battery for our VZ nexus and some say it was horrible....
what are your findings? better? worse? same?
Most battery comments are subjective in nature.
If you perceive worse battery life then try a different kernel or get a new battery.
dvigue said:
I have read conflicting reports that some say 4.3 is GOOD on battery for our VZ nexus and some say it was horrible....
what are your findings? better? worse? same?
Click to expand...
Click to collapse
Its always subjective. Try it yourself.
Sent from my Galaxy Nexus using xda app-developers app
I tried 4.3 and it was faster and with different kernel like mpokang it had good speed and battery life compared to 4.2.2. You just need to make sure you turn off wi-fi scanning even when off and something else in search or 4.3 will suck the battery down. My only complaint is my favorite ROM it's still 4.3 and the 3G to 4G tower switching doesn't work properly and as I travel allot this is a deal breaker for me as it drops calls so had to go back to 4.2.2 ROM. I heard the ROM's that are updated to 4.3.1 don't have the radio issues. This issue is also only on Verizon due to no new radio's yet from what I understand.
I've been using the Galaxy Nexus strictly on wifi for a while now. I recently updated it to 4.3, and while performance is GREAT, battery life is suffering, but I've felt no need to change anything because I'm always near a charger.
For me it's only been a bit of an improvement during regular every day use. Although If I try I can actually go almost a full day with one charge.
When i charge it peeps my phone
I was using 4.3.1 and battery seemed stellar. The radios is the big problem. It doesn't like bouncing between cells and 4G didn't seem to work.
http://droid-hive.com/index.php?/to...-aokp-sabermod-49-03-optimizations-11113-431/
His Rom was here but he recently moved.
-sent from my LG G2 using XDA Premium 4
I revisited slim 4.3 build 2 seems to be working good will see Monday when I go to work and start jumping towers. Really want to be on PA but didn't work good for me and hasn't been updated in awhile. Hopefully Verizon releases 4.3 and they will revisit and fix it. I think us toro users are not going to get a good kit kat because of Verizon radio deal
Sent from my Galaxy Nexus using Tapatalk
Lmao @4.3. Try 4.4 on ART. I've been on it all of a day but wow! You should have flashed 4.3 a long time ago. Its old news. Battery AND speed are crazy with ART. Could be placebo so I'm gonna wait a week or two to pass judgement but so far so good.
Mandelbrot.Benoit said:
Lmao @4.3. Try 4.4 on ART. I've been on it all of a day but wow! You should have flashed 4.3 a long time ago. Its old news. Battery AND speed are crazy with ART. Could be placebo so I'm gonna wait a week or two to pass judgement but so far so good.
Click to expand...
Click to collapse
Is that a Verizon rom? Because it's the Verizon that was only updated to 4.2.2 and has issues with 4.3+
I looked through the Verizon Dev forums but nothing as you described. If a 4.3+ rom has a fully working non-wonky cellular radio, then please link.
-sent from my LG G2 using XDA Premium 4
player911 said:
Is that a Verizon rom? Because it's the Verizon that was only updated to 4.2.2 and has issues with 4.3+
I looked through the Verizon Dev forums but nothing as you described. If a 4.3+ rom has a fully working non-wonky cellular radio, then please link.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
Yes its a Verizon ROM. I don't think any of the 4.3 ROMs had RADIO issues. The Verizon Nexus was Updated to 4.3 through asop including Binaries so there shouldn't be radio issues.
A couple people are reporting issues with 4.4 but it looks like they didn't flash new radios.
Maybe we aren't talking about the same thing? Could you link what you are talking about?
If you want me to link all the ROMs with working radios on 4.3+ that would be to many ROMs.
The problems I have is low signal areas if I have good signal I have no problems on 4.3
Sent from my Galaxy Nexus using Tapatalk
tshelby73 said:
The problems I have is low signal areas if I have good signal I have no problems on 4.3
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
This is probably true. I don't have any problems in my home town but in was in another big city and I had great signal but often kept finding my phone unable to grab a data connection. I had to keep resetting to restore it. Toggling airplane mode wouldn't resolve it.
The only I could think of is I was going through a nonserviced area and dropping data and it never reconnecting.
-sent from my LG G2 using XDA Premium 4
Mandelbrot.Benoit said:
Lmao @4.3. Try 4.4 on ART. I've been on it all of a day but wow! You should have flashed 4.3 a long time ago. Its old news. Battery AND speed are crazy with ART. Could be placebo so I'm gonna wait a week or two to pass judgement but so far so good.
Click to expand...
Click to collapse
Not sure where the 4.4 comment came from...especially since there aren't any stable 4.4 Roms for the GNex yet.
I have bad battery on 4.2 and 4.3. Performance is better though.
Sent from my Galaxy Nexus using xda app-developers app
Mpokang with nephelims seem to give me better battery life on 4.3 vs 4.2.2 might be that you can only use 1080 version on 4.2.2 I use cm version on 4.3
Sent from my Galaxy Nexus using Tapatalk
nnbengboy2 said:
Not sure where the 4.4 comment came from...especially since there aren't any stable 4.4 Roms for the GNex yet.
I have bad battery on 4.2 and 4.3. Performance is better though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
There are some slight graphical issues and reboots but for being dropped by Google the 4.4 ROMs aren't bad. Hopefully with the new GPU Binaries from TI those issues can get fixed.
The 4.4 comment came from the fact the OP is asking about 4.3 while 4.4 is being tested. I was pointing out he's a little late to the game and to get on it!! :silly:
Feels the same to me, same crappy GNex battery life lol
But it's not worse if that's what your wondering OP
Back on 4.2.2 4.3 still had some small data issues in low signal areas. Really the only thing I want is Bluetooth from 4.3 it works right and id tags come through to my stereo. Wonder if it can be back ported.
Sent from my Galaxy Nexus using Tapatalk
I've had my Galaxy Nexus almost since the beginning, and I've tried a lot of roms.
You probably notice a lot of stuttering and general slowness on your Gnex. The Gnex was fine on 4.0. Something happened in 4.1, and it became slow as death. The only thing that ever seemed to fix this was doing a factory reset on your phone, wiping the data, and reinstalling your rom. People came up with varying ways to fix this slowness problem (root always required, of course), including modifying the dalvik heap growth limit and readahead sizes. Other people used a program called LagFix in the Play Store that basically was a manual TRIM, because there was a problem with certain Samsung phones where they refused to trim the filesystem.
Jelly Bean 4.3 fixed all of that. Google committed some changes to the source that built trim into Android. To put it in perspective, my random read speeds on my phone were 0.4 Mb/sec before installing 4.3. My speeds now are 1.6 Mb/sec. Sequential read/write improved by an order of magnitude.
If you're not on Android 4.3, yet, you really need to do it. Android 4.3 helped my battery life not necessarily because it inherently consumes less power, but because it dramatically improved my I/O speeds; when my phone wakes, it doesn't have to wake as long to access random pieces of storage.
On top of this, ever since I can remember, the radio switchoff between Wi-Fi, 1X, 3G, and 4G on the Verizon Galaxy Nexus has been atrocious. Ever since I got the phone, it would regularly take me 30 seconds to a minute for data to come back up as soon as the phone switched to a different wireless standard. The latest Shiny rom (10/11/13) finally was able to fix that, so my radio switches happen in less than 10 seconds, now.
Finally, I've tried random kernels, including Franco, Trinity, Lean, Tiny, Golden, and GLaDOS. All of them have affected battery life and speed marginally and in various ways (and some of them caused me a lot of reboots after a week, or so, of use), but the one that has really--actually--improved the snappiness of my phone has been the BIGMEM version of Fancy Kernel. Fancy Kernel's thread is here; I'm running on version pre44-3-big.
I'm not sure if this is something that happens to a lot of you Nozomi users, but I can always ask for advice.
I skip from custom ROM from time to time just to know what my options are, either experimental or close-to-stock. And quite frankly it is bugging me, that my ROMs always feel sluggish, even when others say it should be quick or smooth.
I just want to have the smoothest, most stable, least sluggish ROM out there (I tend to demand a lot), and it should stay just that. Not that it's blazing fast to begin with, and decreases in speed in a matter of days.
Also, cleanest way to install said ROM? I want to rule out all possible factors.
I hope you can help me along with this,
rc_enzo
Almost all stock roms will eventualy slow down
All them error codes just gather up
Clearing your cache and dalvik fixes some of it
Also stock based roms will always be sluggish, it seems all stock kernels have a entropy issue
There are tonnes of other reason
If you want a smooth and stable rom, i dont necicarily recomend my rom, each device is slightly different, these nano diferences have a bigger effect
Just try out different roms till youn find one you like
If not that unlock your bootloader and install cm10 or aosp
Letamas aosp is about one of the quickest but its buggy and FXP cm10 is great in performance and feels great
BUT YOU HAVE TO KNOW TO REPERCUSSIONS OF UNLOCKING YOUR BOOTLOADER
(Although unlocked bootloader = freedom)
If you need anything just ask, i didnt cover everything surrounding your point and question
Sent from my LT26i using XDA Premium 4 mobile app
I know how stuff works, trust me.
Unlocked my bootloader pretty much the instant I got the phone, and I've run a great number already. I guess FXP works great, but I've read the weekly updates don't add that much anymore...
Sent from my Nexus 10 using Tapatalk
rc_enzo said:
I know how stuff works, trust me.
Unlocked my bootloader pretty much the instant I got the phone, and I've run a great number already. I guess FXP works great, but I've read the weekly updates don't add that much anymore...
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Hmmm...
You could try miui?
Or maybe the 4.4 project (once started and finished)
Letamas 4.3 is i think the faststest running rom on xperia s but there are some openGL issues which makes gaming a no no
And kitkat 4.4 is designed for devices with 512mb of ram, xperia s has 1gb but some for hardware and gpu as we know
I suggest either using letamas 4.3 (few not working things)
Or waiting for a 4.4 build
Im not to sure about opensemc, i dont realy remember not to sure about some others too
Conclusion:
Stock = always slugish
CM10-11 = Good but some builds are buggy
AOSP - amazing but buggy and no fully working builds ive seen yet
Sent from my LT26i using XDA Premium 4 mobile app
I'll give letama's a shot then, and we'll see about KitKat. I have a hunch that we will be getting one fairly soon.
Sent from my Nexus 10 using Tapatalk
rc_enzo said:
I'll give letama's a shot then, and we'll see about KitKat. I have a hunch that we will be getting one fairly soon.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
RaymanFX i think he said he got it to boot already but he is a super dev like letama
Me and some other people are trying to get Official CM11 (4.4) for xperia s, (petitions blah blah blah)
Me and some other devs are working on AOSP 4.4
So you should see alot of 4.4
Also - read through the bug list of letamas 4.3 build and also notice there are some graphics bugs but everything else is fine as far as i remember
Using letamas 4.3 then going back to stock, stock felt like very slow
Sent from my LT26i using XDA Premium 4 mobile app
rc_enzo said:
I'm not sure if this is something that happens to a lot of you Nozomi users, but I can always ask for advice.
I skip from custom ROM from time to time just to know what my options are, either experimental or close-to-stock. And quite frankly it is bugging me, that my ROMs always feel sluggish, even when others say it should be quick or smooth.
I just want to have the smoothest, most stable, least sluggish ROM out there (I tend to demand a lot), and it should stay just that. Not that it's blazing fast to begin with, and decreases in speed in a matter of days.
Also, cleanest way to install said ROM? I want to rule out all possible factors.
I hope you can help me along with this,
rc_enzo
Click to expand...
Click to collapse
You can always make a clean install.. Wiping everything, format everything and then flash.. That's the best way to avoid any sort of problems in any ROM.. As Envious_Data said, there are lots of advantages of unlocking the bootloader.. And btw if you are going with Stock based ROM, i would suggest u try eXistenZ Ultra and Trintity ROM first and when it comes to AOSP/CM ROMs you can try letama's AOSP 4.3 or RaymanFX's CM10.2 alpha3.. I am currently on CM10.2.. Its very smooth and fluid for an alpha.. I am getting better battery backup too.. Although i have to sacrifice 1080p recording for now, but the ROM is definitely a daily driver.. Go ahead and choose to flash any ROM.. Welcome to Xperia S section..
No offence guys, but I'm not new at the Xperia S, have had the device since november last year, running ROMs since early january.
Thanks for the advice anyway.
I've got the same, my phone runs smooth right after flashing the ROM, but then... I don't know, maybe its because of the way we use our phones?
I have compared my XS to my friends XS - his was very smooth and mine - you know. I have unlocked bootloader to make GTA III run smoothly.
And now - I just got used to this, but I hate my phone
Running letama's 4.3 AOSP, and @Envious_Data thanks for the suggestion, it feels truly rapid and it looks like it will do fine for me. That games and 1080p recording don't work properly, is no burden for me anyway.
Good luck on your developing endeavours, I hope 4.4 progress is good
(this is for future reference)
the Reason why our phones on the stock roms is the same reason why windows slows down
error codes build up and one way to fix half of it is to wipe your cache, (one advantage of apple IOS, does not generate error codes and thus can last a straight 2 months of constant running)
AOSP /CM10/11 are much cleaner then stock and will take alot more time to slow down, and the same goes with Stock ICS, it will slow down a bit but no more then that
GB was about the best, it was perfectly coded , no errors
JB was coded by Sony DEV team B and team B is the ones to F***ed up almost everything they have touched
although Xperia Z run almost the exact same firmware as xperia s it got messed up when they ported it
its why i discontinued my rom, i couldent fix alot of the errors that my self and sony had caused