Related
Hi all, just installed the new 1/16/12 cm9. There was a post in the developer thread indicating that this version breaks face lock. Just wanted to pass along my experience. I did not have this issue. Facelock is working great. I did a full wipe data/dalvik/cache using the rogue cwm.
The only issue i Seem to be having is with the browser and ics browser plus. They seem very slow to respond to loading pages, and entering text (like searching in Google). Has anyone else experienced similar problems? I did not see this problem when I was on EOS nightlies build 36. Any suggestions or information would be greatly appreciated.
Also I did flash the latest gapps that was posted with cm9
Good to hear 1/16 did not break facelock for you.
I can confirm that 1/15 Kang did have oddities around certain apps closing. For example, if you close Google Currents, Youtube, B&N Nook, Kang 1/15 would pause before closing the apps (minimized). Browser and others did not exhibit this issue.
As for your specific issue, 1/15 did not have browser load or other performance issues. IMHO, 1/15 had full functionality except for those apps closing.
There are some visual artifacts in "Burn the City" game where the screen would intermittently flash on 1/15.
Same here (Installed CM9 from 1/16 with new GAPPS). No issue with the browser lagging. Did you wipe/reset your data before installing CM9 and GAPPS? If not, try wiping, then install the ROM and immediately install the Google apps (make sure you have the latest from 1/18 which is version 5.2) after the ROM without rebooting in between. Then reboot at the end. Hope this helps.
Overall 1/16 Kang is smooth. But I've had some weird app closing issues but only a few (Google Currents, B&N Nook Reader, YouTube).
When you're in the App and press HOME, the Xoom shrinks upper and lower by 1/3 and then waits for about 1/2 a sec then minimizes/closes.
On some games like "Burn the City" it causes intermittent screen flashing.
Other apps seem to run fine. Have other people seen this too?
Tempted to restore to stock and flash the official release.
Let me us know how it goes with the official release. BTW I saw on the Development threads that there's a rooted version of the official release that can be installed via Recovery so you won't need to return to stock first (saves a few steps).
reboot isues
my xoom ever since th 26th update has had restarting issues not all the time bout 4 times in a 24 hour period every time i update i wipe everything and start over but im still having this issue updating to the 29th update today i hope this fixes it has anybody else had this issue
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.
Having an issue with Google Navigation (maps is ok), but whenever it goes 3D mode it crashes shortly after :|
Currently on HBoot 2.14
Have noticed E/Sensors (973): MLUpdateData error (code 31) a couple of times throughout the logcat, is this G-Sensor related?
Phone slowing down after Viper 3.1
Did anyone who installed Viper 3.1 experience phone slowing down after the install? There is a lag when the notification bar is pulled down or switching between screens.
Being a noob, this is what I did -
1.) fastboot flash boot boot.img
2.) wiped cache and dlvik cache
3.) flashed viper3.1.zip
4.) I haven't tinkered around with the kernel. It should be the stock.
In effort of speeding up the device, I went to Venom Tweaks --> CPU and switched to "Performance". Not sure if that was the right thing to do.
Reading the Forums, everyone seems to have buttery smooth experience, not me
Any help is appreciated.
knowskillz said:
Having an issue with Google Navigation (maps is ok), but whenever it goes 3D mode it crashes shortly after :|
Currently on HBoot 2.14
Have noticed E/Sensors (973): MLUpdateData error (code 31) a couple of times throughout the logcat, is this G-Sensor related?
Click to expand...
Click to collapse
This is something I've noticed from Jelly Bean in general ( Cyanagenmod, AOKP, and Sense 4.5 ). Devs keep saying they'll address it before it eventually gets swept under the rug. Between that and signal issues I was having I've switched back to running stock (I'd rather have a working phone with a little bloat and a few less features). If you have to have Google Navigation you may want to do the same. Or maybe someone could set up a bounty to have devs actually do something about it (if there is something that can be done). Or you can go back to sense 4.0 for the time being. Sorry to sound like a negative Nancy.
red3gunner said:
This is something I've noticed from Jelly Bean in general ( Cyanagenmod, AOKP, and Sense 4.5 ). Devs keep saying they'll address it before it eventually gets swept under the rug. Between that and signal issues I was having I've switched back to running stock (I'd rather have a working phone with a little bloat and a few less features). If you have to have Google Navigation you may want to do the same. Or maybe someone could set up a bounty to have devs actually do something about it (if there is something that can be done). Or you can go back to sense 4.0 for the time being. Sorry to sound like a negative Nancy.
Click to expand...
Click to collapse
just tried rooted stock rom, seems like an issue with my phone and JB... was working fine on ICS :S
red3gunner said:
This is something I've noticed from Jelly Bean in general ( Cyanagenmod, AOKP, and Sense 4.5 ). Devs keep saying they'll address it before it eventually gets swept under the rug. Between that and signal issues I was having I've switched back to running stock (I'd rather have a working phone with a little bloat and a few less features). If you have to have Google Navigation you may want to do the same. Or maybe someone could set up a bounty to have devs actually do something about it (if there is something that can be done). Or you can go back to sense 4.0 for the time being. Sorry to sound like a negative Nancy.
Click to expand...
Click to collapse
I'm on 3.1 and don't notice any lag smooth as butter hboot 1.11 only thing is the text selector jumps around some times
knowskillz said:
Having an issue with Google Navigation (maps is ok), but whenever it goes 3D mode it crashes shortly after :|
Currently on HBoot 2.14
Have noticed E/Sensors (973): MLUpdateData error (code 31) a couple of times throughout the logcat, is this G-Sensor related?
Click to expand...
Click to collapse
Try WAZE it's in the app store free too
sriramll said:
Did anyone who installed Viper 3.1 experience phone slowing down after the install? There is a lag when the notification bar is pulled down or switching between screens.
Being a noob, this is what I did -
1.) fastboot flash boot boot.img
2.) wiped cache and dlvik cache
3.) flashed viper3.1.zip
4.) I haven't tinkered around with the kernel. It should be the stock.
In effort of speeding up the device, I went to Venom Tweaks --> CPU and switched to "Performance". Not sure if that was the right thing to do.
Reading the Forums, everyone seems to have buttery smooth experience, not me
Any help is appreciated.
Click to expand...
Click to collapse
No lag what so ever
Sent from my HTC One XL using Tapatalk 2
sriramll said:
Did anyone who installed Viper 3.1 experience phone slowing down after the install? There is a lag when the notification bar is pulled down or switching between screens.
Being a noob, this is what I did -
1.) fastboot flash boot boot.img
2.) wiped cache and dlvik cache
3.) flashed viper3.1.zip
4.) I haven't tinkered around with the kernel. It should be the stock.
In effort of speeding up the device, I went to Venom Tweaks --> CPU and switched to "Performance". Not sure if that was the right thing to do.
Reading the Forums, everyone seems to have buttery smooth experience, not me
Any help is appreciated.
Click to expand...
Click to collapse
The lag when pulling down notification is because you have quick toggles enabled. Disable them and it will be much faster.
Sent from my HTC One XL using xda app-developers app
On the topic of the Notification bar, I have the Horizontal Quick Settings, has VQS been ported over as well or only HQS at this time? ViperXL 3.1.0
Cheers.
Waze is what I always use on JB roms, works like a champ. Its sweet, one of the coolest apps in the market. So another one who recommends waze
Experiencing crashes in various apps. New to this revision.
EOS4 173 - Xoom Wingray
I am also running EOS4 011913 (173) nightly, and I've been experiencing lag in almost every animation - launcher, notification pulldowns, desktop switches, and especially the app drawer opening and closing. These problems were mostly able to be mediated with a combination of a third-party launcher like Nova, and some gentle adjustments to the System/Performance settings in EOS Control Center.
But I digress. My biggest problem is that there is noticeable audio lag, almost everywhere in the system. Music starts a split second after I hit Play, games' sound effects happen just after the events (Jetpack Joyride is atrocious about this one), and most aggravatingly it seems to be cumulative; running an app longer makes the lag worse. Music and videos don't seem to have it quite as bad as games, but it's still noticeable.
I tried to isolate the problem (wipe everything, reflash, try apps without changing anything first) and it's still recurring, as badly as before. I don't want to give up on EOS yet, but to my knowledge after diligent Googling I am the only person who seems to be suffering this sound delay problem.
It is my sincere hope that the devs will pick up on this two-post thread, or that someone more qualified reports this problem somewhere more noticeable.
-K
--EDIT
"Stock" EOS4 173 was still having the audio lag with all the settings default (and I would hope that none of the settings, which are mostly for the interface, would create this lag), but some other users (whom I'd like to thank, but can't) suggested adding the boot.img (kernel) from CyanogenMod 10.1's latest nightly into the .zip for this, and it seems to have worked like a charm. It remains to be seen if the problem will resurface with prodding into the settings (which I'd really like to do!) again, but there it is.
donrull, I don't know if your problem would be fixed by using the different kernel, but it seems to have fixed a multitude of problems for other users
I noticed the same lag in launcher when I still had the Xoom with EOS4, but I kindda found another workaround(there is a set of tweaks mentioned in the main EOS thread which is a little too much modification for me) to that.
The last option in Power options will hide both the status bar and navigation bar, with those bars gone, launcher just becomes "butter" again.
I then used GMD gesture for all the actions and it was much more acceptable to me, hope this helps with the launcher lag for you too
I wanted to return to weigh in on my trial and error process, in the hopes that it helps someone else:
In this order:
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery.
Flashed the 'stock rooted' JB 4.1.2 to get root, something that was missing before. I don't honestly know if it'll help these issues, but it seemed relevant that I hadn't done that yet. Worth noting, the stock rooted ROM has the absolute smoothest launcher/desktop/app drawer animations I've seen, even over the stock OTA 4.1.2.
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery. (Always, between all flashes.)
Flashed the lastest EOS nightly (20130126-174), followed by the latest Gapps package (20130105). Launcher/desktop/app drawer lag was back, and my earlier mentioned SEVERE audio lag (almost half a second) was back, on the keyboard and in apps.
Nova Launcher with 'Fast/Fast/Jelly Bean' animation settings and all the animation settings in Dev Options set to 0.5x was, and remains, the best-looking solution to the launcher lag. App drawer still has a slight, but noticeable, lag, even with only stock apps inside. Switcher lags, sometimes severely, even when entering or exiting a less intensive app like Google Play Music.
This audio lag, though: It appears to be isolated to EOS's updated Tiamat kernel, as it was fixed (as mentioned earlier) by replacing it with the latest from CM10.1. This fixes the audio lag and slightly alleviates the notification bar pulldown lag, but the launcher/desktop/app drawer still needed Nova to seem close to 'butter' again. This also disables OC, the kernel doesn't support it but EOS's settings will still 'let' you, minus the 'lagfree' governor showing up; the only noticeable effect is about 100MB less available RAM at all times, and choppiness in places as a result.
Mentioned earlier, but the audio and video lag I tested BEFORE I started messing with settings like OC; even a brand-spankin'-new flash of this ROM suffers from it. Mentioned this too, I was using Jetpack Joyride to test, because its sound effects are very punctual. Tried some other apps, they suffer the same lag but I guess it isn't as noticeable. (Fruit Ninja you can hear the fruit being tossed AFTER you see it.) No messing about with the settings seemed to alleviate it, which is why I tried the kernel swap.
So basically where I'm at now is either stock-rooted 4.1.2 that looks and sounds gorgeous, but it feature-barren, or EOS's 4.2.1 that technically runs faster, but looks choppy and awkward and sounds about a half second off at all times, or EOS + CM10's kernel, that splits the difference, still suffering the animation lag and the lack of OC, but with OK audio. After five days of messing with this on 173, and today's struggle on 174, I'm about ready to give up on being 'satisfied' with EOS. I really hope this lengthy post reaches someone who can do something about it, since I am not enabled to post in development forums and cannot privately message anyone just yet.
Edit: the 'stock rooted' update is 4.1.2, not 4.1.1 as I posted previously. This seemed like kind of an important oversight.
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!