Looking for help with a butt-slow stock 4.1.1 Nexus S - Nexus S Q&A, Help & Troubleshooting

So I have the i9020T (from Wind in Canada). I enjoyed running CM9 nightlies on it, but then Jellybean came along and I went nutso over it (like so many others). I flashed back to stock ICS, and then ran the OTA update on it to JB.
My experience has been disappointing. It was unfathomably slow. It was running-Windows-7-on-a-Pentium-III slow. The new UI and features are glorious, but I need a lot of patience if I expected to use them. I'm talking about delays of around 5 seconds to start an app, switch apps, or even open the app drawer, 2-3 seconds lag when bringing up the keyboard, and 5-10 seconds to bring up Google Now.
I automatically decided to nuke everything and start from a clean slate. I grabbed the 4.1.1 stock image from Google, then formatted /system and threw it on. After the initial setup, and before I even got to rooting the thing (never mind restoring from Titanium), it was still muscle-atrophyingly slow.
I ended up just restoring all of my apps and data, and using it as-is, figuring this is what I should expect from an older device. Yet everyone online raves about how much faster JB is than ICS on the Nexus S. Either you're all trolling me really hard, or I'm doing something very wrong.
Here's some more gory details:
Like I said, I wiped /system before loading the new image. I did it on the phone using Clockworkmod recovery, then used fastboot from my computer to load the image. I did not wipe data or cache, because I figured the whole image-writing thing would be obliterating all my stuff anyway, but perhaps I was wrong?
I've been playing with the CPU usage overlay, available in the Developer Options. First off, I have no clue what the different colours mean or what scale those bars represent, but I can tell you my load is typically 2.0 (even just sitting there idle with the screen on), all the way up to 15 or so if I'm trying to do something like use Chrome while listening to Google Play Music. system_server is always the top process, and its bar is always 3-4 times bigger than the next, with the sole exception of loading up Google Play Music, in which case the mediaserver process holds the top spot with a fairly long bar. ksmd, com.android.systemui, surfaceflinger, and com.android.phone are always running, but only ksmd even has a bar long enough to be visible. Other processes pop in and out, and of course they start going willy-nilly when I actually start using apps and switching between them.
There have been a handful of times where an app will die while I'm in the middle of using it, and 2-3 times the phone has outright rebooted itself.
So there's my story. Can someone tell me if I'm just plain doing it wrong? Perhaps there's a guide on how to completely sterilize the phone before loading the stock image? Or perhaps my hardware is broken? :-/

I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.

Cool... I'm looking into it, and can't find any directions whatsoever on what I should download or how to install it. I'll keep digging, though. Thanks!

While I am not sure what is causing your issue I can confirm that stock jb should not be performing like you are describing. Except for loading up Google now. That does take some time but even that once its loaded runs OK.
Did you clear your SD card? If not back that up to a computer and wipe it. That's all that I can think of and it may actually fix it.

At first I noticed painfully slow speeds as well. Changing my min setting to 200 helped so much! I've heard the the Interactive governor is amazing with JB in terms of speed. You could try that out.
Nexus S. (GSM i9020a)
Paranoid (1.97 - 4.1.1)
Matrix (CFS - 22.5)
Ondemmand (1000/200)
Deep Idle (On - Deadline)

I've just flashed Air Kernel (I just picked one of four options, I don't know what the heck "blue color" means), then set the governor to smartassv2, and so far it feels snappier. I'll have to keep using it to see if it's the solution I need. Thanks to all who've made suggestions so far!
Sent from my Nexus S using xda app-developers app

If your phone is going crazy slow it could be a number of things like apps could be slowing down the phone in the background or the phone might be trying to sync. You could backup all of your apps and then wipe your phone fully it should speed it up quite a bit and then you can restore each app 1 by 1 to determine if its a rogue app causing it. But if you can't be arsed to do that and wipe then just try and flash Thalamus kernel and see what its like if you set the governor to interactive on that it should go crazy fast.
Sent from my Crespo using xda premium

Please provide clear advice Nexus S so slow on Jelly Bean
ronnygunz said:
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Click to expand...
Click to collapse
I can see there are many 'fixes' for slow running devices on Jelly Bean. However, I have no idea:
1. how install Air Kernel or where to get it from
2. How to change the CPU governor from "on-Demand" to "SMARTASSV2" or where to download this from
Please can someone give me the complete idiots guide to getting my Nexus S running properly again??
THANK YOU

There are a million guides on this forum for all of this. If you don't know how to flash a kernel or adjust CPU speeds, you need to familiarize yourself with these things and understand the risks. First off, try cleaning your phone up. Take all your important stuff off your external storage, and do a factory reset. My Nexus S never ever ran slow, even on stock.

Have you tried a more simple but fast kernel like marmite 4.2 from bedalus? Give it a try.

Related

Help Please

I have a strange problem with my Hero that is hard to describe. Even before I rooted my phone I had this problem which leads me to believe it could possibly be a hardware malfunction. Anyways..
The problem is that over time after a complete wipe and flash of a custom rom (I've tried several) that my phones slowly deteriorates. It will be running fast and great for a week or two and then its starts to slow down to the point where it is completely unusable and I am forced to wipe and flash again. While its acting this way I have tried killings tasks, emptying cache, hard resets... every simple solution I can think of....
The other odd thing is that I use my phone very lightly. I only install 4-6 apps and those are the basics like pandora and such...
And I'd like to add that maybe I'm wrong about my phone acted this way when I had 1.6 official on it. It's been awhile.... so maybe I corrupted something when I rooted my phone for the first time?
Really I wish you could see the way my phone acts... its ridiculous . I would take a youtube video of it if I wasnt too lazy too. Crazy stuff like it taking a whole 30 seconds to a minute for a unlock pattern to finally go through, Or how when I try and type a phone number its like 3 or 4 presses "behind" as I type ( and im not typing quickly) or when I try to scroll through my contact list it just gets stuck and then finally it "catches up" and stutters all the way down to the bottom because of how many swipes I attempted.....
...help
have you tried.....?
Have you tried to run an RUU of eith 1.6 or 2.1? if you runn an RUU it will clear out any lerking "software" issues and then just re-root and try that out then try a custom rom after that.
Try Autokiller from the market. Once you install it, run it. Set the autokiller settings to something like Optimum or Strict (if that doesn't work for you, try Aggressive).
This will adjust the low memory killer settings to a more aggressive number. This, hopefully, will help.
smash58 said:
I have a strange problem with my Hero that is hard to describe. Even before I rooted my phone I had this problem which leads me to believe it could possibly be a hardware malfunction. Anyways..
The problem is that over time after a complete wipe and flash of a custom rom (I've tried several) that my phones slowly deteriorates. It will be running fast and great for a week or two and then its starts to slow down to the point where it is completely unusable and I am forced to wipe and flash again. While its acting this way I have tried killings tasks, emptying cache, hard resets... every simple solution I can think of....
The other odd thing is that I use my phone very lightly. I only install 4-6 apps and those are the basics like pandora and such...
And I'd like to add that maybe I'm wrong about my phone acted this way when I had 1.6 official on it. It's been awhile.... so maybe I corrupted something when I rooted my phone for the first time?
Really I wish you could see the way my phone acts... its ridiculous . I would take a youtube video of it if I wasnt too lazy too. Crazy stuff like it taking a whole 30 seconds to a minute for a unlock pattern to finally go through, Or how when I try and type a phone number its like 3 or 4 presses "behind" as I type ( and im not typing quickly) or when I try to scroll through my contact list it just gets stuck and then finally it "catches up" and stutters all the way down to the bottom because of how many swipes I attempted.....
...help
Click to expand...
Click to collapse
tkirton said:
Try Autokiller from the market. Once you install it, run it. Set the autokiller settings to something like Optimum or Strict (if that doesn't work for you, try Aggressive).
This will adjust the low memory killer settings to a more aggressive number. This, hopefully, will help.
Click to expand...
Click to collapse
I agree. I use auto killer on aggressive with CM6 and it runs great forever
My phone does the exact same thing!
I first really noticed it when I flashed the official sprint 2.1 update. I think it has something to do with the buildup of cache on the phone.
I have been running CM6 for a little over a month and have recently noticed it getting slightly hung up at times, but nothing compared to how it was with the official 2.1 update. Also, remember that CM6 does not have Sense, which can really slow down the phone.
I also I agree with you that it seemed like my phone did not do this on 1.6, but it has been quite sometime since I flashed 2.1.
Does anyone know what really causes this exponential slow down; to the point where the phone is barely useable?
hm... I will try autokiller.....thanks for the advice
as for CM6..... I've tried not using sense UI but to me its my favorite part of my phone... for example the facebook/twitter/flickr integration with my contact list is invaluable.... is there a replacement for this?
is anyone else able to add anything else?
smash58 said:
hm... I will try autokiller.....thanks for the advice
as for CM6..... I've tried not using sense UI but to me its my favorite part of my phone... for example the facebook/twitter/flickr integration with my contact list is invaluable.... is there a replacement for this?
is anyone else able to add anything else?
Click to expand...
Click to collapse
Try Zen-Rom. It has all that you are looking for and is very fast and stable.
Sent from my Zen-Rom Hero!
Auto killer is the way to go. I found Aggressive setting too much for my tastes; if I was on a webpage, then went to the home screen for something else and opened back up the browser, it would have to reload it because it was killed. I set it on optimum, and get no slow down, and can still truly multi task.
chefthomas99 said:
Try Zen-Rom. It has all that you are looking for and is very fast and stable.
Sent from my Zen-Rom Hero!
Click to expand...
Click to collapse
Or NFX-Hero. I'm not a Sense guy, but I've experimented with that ROM, and it was the fastest Sense 2.1 IMO.
Just curious but does pandora have a cache file on your sdcard? I had an app that was reading and writting to a cache on my sdcard and it would slow my phone down a lot. When your phone slows try ditching some of your apps and see if maybe one could be responsible for it, if it is there are tons of options different apps that do the same thing.

Captivate: Some programs running slow

Hey everyone... I'm new here so be gentle
I'm running a captivate with the latest CM nightly (#104) - installed last night. I have AutoKiller running the aggressive preset and - for the most part - things run smooth. I didn't wipe the cache partition when I installed #104 from CWM (I forgot, but things still work a bit better than they did).
Anyways, I've noticed that some of the RAM heavy apps, most recently words with friends, seems to lag after a min or so of usage and I get the "force close"/"wait" dialog. If I wait, things go back to normal for a little bit.
When I first installed the app about a month ago everything was working great and had no issues. I'm trying to get back to that point.
Some quick background:
Was running CM7.1 RC1 prior to #104
Performance on CM7.1 was awesome until within the past week or so when stuff lagged a lot and was generally slow to respond (lots of 'wait' dialogs for many apps)... this prompted the use of Autokiller and the upgrade to #104.
I've been surfing the forums, and I don't think I'm missed anything, but I'm not sure. Any help would be greatly appreciated!
Thanks
First off don't use a task killer. Android is a smart OS and using a task killer will just dumb it down. It really does take a day or two for your phone to settle after flashing a new rom. When you flashed the new CM7 did you by chance use Titanium back up to restore apps? Sometimes when you do this they don't work right and becoming memory hogs is one of the things they do.
I would suggest a clean flash wipe everything. Then don't use a task killer. If you absolutely have to use Titanium backup or something like it only use it to restore data. Re-download all of your apps from the market and this should end up making your phone fast again.
Thanks... In the end I did just that. I futzed around with a few things and really made things run sluggishly so I finally wiped everything.
I did use TB to backup everything and I've been slowly adding the apps/data back. I also did the v6 supercharge script which has done nicely also (I didn't mess with the minifrees though since that was part of my problem in the end )
The only thing I forgot to back up were my CM7 settings, so I'm slowly putting all those back where I had them. I think CM7 can backup its settings, I just forgot to do it.
Anyways, the phone is wicked fast and responsive now. It's really nice how the phones can be wiped and put back together so fast.... comps were never this much fun to play with.

[Q] Sluggishness building over time ?

Hey guys,
I have my Nexus S (9023 variant) for some good 4 months now and I'm still quite happy with it!
Running unrooted stock 2.3.4 version.
However, I seem to feel like the phone is getting a bit jerkier / sluggish than it used to be before. I've noticed an increase in battery consumption of the Android OS process (not the system one) as opposed to before (like in a 100%-0% charge, it used to be 1-2 minutes, now it can go up to 10 mins time usage).. Sometimes going from one app to the other seems to have a noticeable lag. Sometimes the Google Music player is just slow to start playing... sometimes even the swiping of the home screens dies.
Also I used to have 2 days battery life and now some 1.5 days (which forces me to charge every night).
I would suspect than an increase on the Androis OS process would mean an increase in internal task switching.
How can one alleviate the problem ? Is there a way to sort of "cleanup" the system ? Does it degrade over time needing a factory reset or something ? I have some applications installed (some of them I hardly use though) but I suspect that even though those optimizations have their notifications disabled, they can be reacting to some kind of low-level OS events..
Anyway thanks for any thoughts guys!
What ROM are you running? And I would suspect that apps are the main problem if it persists after a reboot.
Stock 2.3.4, unrooted
Guess it's on to uninstall some apps then
Factory reset would solve all your problems I assume. Pity you are not rooted so you can back up your ROM.
I'm actually thinking of rooting soon, because I made some video recordings in a concert and they were plain horrible (distorted). So I might try to install a kernel with voodoo.
I guess I can always manually backup for once...
I have the google services backup activated... doesn't it mean that I can restore all my apps after a factory reset ?
https://market.android.com/details?id=tw.nicky.CleanCache
You can use that to clean up your caches. I suspect a lot of programs installed or one or a few that are pulling your performance down. You could go about this in a few different ways. One is to uninstall everything you've downloaded from the market. That should give you a boost. Or you can start uninstalling programs one at a time until you see your performance increase then that's your culprit. Another idea is to delete all your SMS, MMS, and voicemail. I've seen people with hundreds of texts that after deleting them, notice an improvement.
A cache and dalvic cache wipe would help speed things up. Hopefully that market app above can do both. Normally done through a custom recovery.
Sent from my Nexus S 4G using xda premium
read this http://forum.xda-developers.com/showthread.php?t=1231840&highlight=slow+crawl
it'll give you good ideas on how to make it faster again
mindwalkr said:
Hey guys,
I have my Nexus S (9023 variant) for some good 4 months now and I'm still quite happy with it!
Running unrooted stock 2.3.4 version.
However, I seem to feel like the phone is getting a bit jerkier / sluggish than it used to be before. I've noticed an increase in battery consumption of the Android OS process (not the system one) as opposed to before (like in a 100%-0% charge, it used to be 1-2 minutes, now it can go up to 10 mins time usage).. Sometimes going from one app to the other seems to have a noticeable lag. Sometimes the Google Music player is just slow to start playing... sometimes even the swiping of the home screens dies.
Also I used to have 2 days battery life and now some 1.5 days (which forces me to charge every night).
I would suspect than an increase on the Androis OS process would mean an increase in internal task switching.
How can one alleviate the problem ? Is there a way to sort of "cleanup" the system ? Does it degrade over time needing a factory reset or something ? I have some applications installed (some of them I hardly use though) but I suspect that even though those optimizations have their notifications disabled, they can be reacting to some kind of low-level OS events..
Anyway thanks for any thoughts guys!
Click to expand...
Click to collapse
Nice ideas guys!!
Think I will try to install titanium backup and backup my apps. And since I'm on it, I will also root my phone and install the net archy kernel cause the last time I took my phone to a concert I ended up with 1 hour of unusable footage due to sound issues.

[Q] Random power-downs in TriForceROM 3.0 on Samsung Galaxy s4

I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.

[Q] Ready to take the plunge, recommend a ROM? [and give me other tips]

I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Team Apex have done some great work. By now they know the hardware very well, having done the initial dev work back on CM9, all the way up to the current CM11 and now Omnirom systems. Their current efforts are focused on the Omnirom-based Omnitoad project. It's at a point where it works very well. I suggest starting there.
The stock roms and the earlier CM roms all have a bug where the compass reads totally wrong after a reboot until you recalibrate it. This was finally fixed in the CM11-based ROMs. That should help Ingress.
radwolf76 said:
I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Click to expand...
Click to collapse
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
REV3NT3CH said:
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
Click to expand...
Click to collapse
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Um dude you do know your touchboost is mpdecision based right?....look at the defconfig...and to be honest my kernel works just as smooth if not smoother than the stock kernel of omni without it...using omni on stock kernel I wald have 40% battery come 11pm my time when unplugged at 7am...on my kernel I'll have anywhere between 65% and 70% with same usage and hours
Sent from my L1QU1D R3L4Y using xda-developers app
One other thing about touchboost, which will hopefully bring us all out of ignorance of it as I am tired of the constant FUD about it. It is the 'touch responsiveness' portion of Google's "Project Butter" initiative. It is a standard Android/AOSP feature enjoyed by Nexus owners since Android 4.1.x.
One more thing. It is a UI deficiency that the performance settings apps show 1134Mhz as min cpu when using touchboost. In kernel mpdec will run the cpus at 384mhz unless something needs more, or the cores will sleep. Now you know the facts. Let's stop spreading misinformation. Thanks.
Not spreading misinformation...my builds and the community have even spoken of the better battery my kernel and ROMs have with it disabled and removed....even flashing my kernel over omni the phone instantly stopped overheating and lost maybe a percent in 2 hours with moderate use.... I just love how as soon as I came to the relay you guys judged me as a noob and all the name calling and what not....it's your teams loss...all my gain...good luck
Sent from my L1QU1D R3L4Y using xda-developers app
In my opinion, I try all the roms available for relay right now, the better performance I have was with liquid ROM and blackbird kernel. Omni is smooth but the battery its not the best for my phone with my personal use, and with GPS and plugged to the car charger i got overheating. Carbon got better battery than omni and better customization options but not smoother. Liquid have all you need in a ROM, personalization, full control and with the kernel blackbird and Wheatley and sio configuration have the better performance and battery at all ROM I try
Sent from my SGH-T699 using XDA Premium 4 mobile app
So, I tried OmniToad for a bit. Wasn't really impressed with the compass fix mentioned above, because even after flashing it was still quite ill-behaved in Ingress.
I also couldn't get the External 2 Internal SD Card swap to work -- the storage tab kept reporting my internal as 5 gig and the external as 64gig. This was after trying two different microSDs.
So, because of those two issues, and being not too far along in re installing everything, I decided to flash again, with the Blackbird Kernel and Liquid Smooth.
Now, when I try to boot. it hangs on the screen with the ApexQ green penguin. If I try for recovery mode I'll get the blue text that says booting into recovery, and then it goes to the penguin again. Trying to boot to download mode also just gives me the penguin.
Troubleshooting suggestions? Because right now, I'm without any clue as to what to do next, and without a phone for that matter.
[Edit: Just got into recovery, so going to try flashing back to OmniToad]
[Edit 2, Electric Boogaloo: Back on the Toad for now, Seems to be working. Thoughts on how to get things running on my external SD? Is it maybe an issue with KitKat based roms?]
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
REV3NT3CH said:
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
Click to expand...
Click to collapse
Recovery is TeamWin, and I was finally able to get back into it. Put OmniToad back on it for the time being. If you wanted to put up a step by step for going from Omni to Liquid, I can give it a try, because at this point, I'm pretty sure it was a "ID Ten T "error.
Magamo said:
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Click to expand...
Click to collapse
Did u just say 60+ hours of use??
How?? What do u mean by medium use?? Are you using the stock battery??
That's only possible with screen off with no use in that 60 hours and the phone going into deepsleep...either that or he's using an extended battery....with very minimal use....also proof or it didn't happen
Sent from my L1QU1D R3L4Y using xda-developers app
@radwolf76 I sent you a pm
Sent from my L1QU1D R3L4Y using xda-developers app
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Now I just have to get all my stuff put back on this thing and figure out how the extra features of LiquidSmooth are going to fit into my workflows.
One thing that seems to be a minor annoyance, probably because I just haven't found the toggle for it yet: on stock, I used to be able to wake the phone from the home button and the screen would pop on instantly. Under both custom ROMs I've tried, it seems a lot harder to wake the phone. The power button seems to be the only thing that works, and I have to stab at it repeatedly. I almost suspect that I'm waking it up and puttting it back to sleep before the screen comes on, but I can't seem to find anything that consistently works. Like I said, it's probably something I just need to toggle under settings.
The home button's actual switch is in the center of the button, while the design allows the button to tip sideways. So if you press it on a corner instead of the middle, the phone sometimes won't recognize it.
radwolf76 said:
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Click to expand...
Click to collapse
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
radwolf76 said:
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
Click to expand...
Click to collapse
well i use nova launcher.....launcher 3 and google launcher in my opinion isnt the best of launchers...there is other options i mentioned in a pm before to storing apps on sd and is alot easier than fiddling looking for the right app ....what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
REV3NT3CH said:
what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
Click to expand...
Click to collapse
This post from another user in the Mounts2SD thread. They might be mistaken, but either way, my problems started cropping up after I installed that app, and if there's a chance that poster is right about it setting those things, that's just another reason for me to uninstall it.
right now Carbon wins
I've tried them all, Liquid smooth is awesome but the latest built gave me some blackscreen issues until the next built go with carbon if you want some nice features or slim for a nice overall rom.
Don't forget to install the Blackbird kernel for a even better result.
Peace!

Categories

Resources