Related
Occasionally, I'll pull my Charge out of my pocket and hit the power button expecting to see the unlock screen pattern, but instead it goes straight to my launcher home screen. Once this happens, the lockscreen never comes back without a reboot or hot-boot. Also, when this happens, the power button menu dies. No matter how long I press and hold it, no menu for shutdown, etc, just turns the display off.
This started happening a month or so ago, on two different ROMS (gummy and humble), even after full wipes and fresh rom installs, it eventually will happen again.
I have 7 active Android devices (N1, NS, SGS, SGS2, Thunderbolt, Charge, Nook Color), all of them using the same Launcher Pro with similar setups, and the Charge is the only one to have this happen to it.
I'm not even sure where to start troubleshooting this. It's a major security risk for me…way too much personal information on the device to risk it randomly unlocking itself for anyone who happened to pick it up.
I've had the Charge since day 1, and it's never been a pleasure to own until the latest round of GB ROMs came out. I was actually starting to use it as my daily driver, but with this security hole, it's looking like back to the desk drawer for it unless I can figure it out.
The only things I've tried so far are removing AutoKiller memory tweaks from the Charge (thinking maybe the process was being killed) and full wipes/resets. I'll also try running a different launcher (that would suck, I really like LP).
Any ideas?
I can just say that its happened to me as well only way i found to fix it was to restart but then it hasn't happened again i was running 2.3.5 leak just rooted.
Sent from my SCH-I510 using XDA App
I have been running humble 5.0 since release, and also running launcher pro plus, I have not had this issue. So possibly a rogue app is killing it.
~Sent using my Humble Charge~
Ive never used it before or looked anything up but in your setting under location and security you can pick between numbers, create your own lock screen etc. Not sure if that is just for when the phone first starts but maybe look into that. Then find out why your other one isnt working.
Use logcat to figure out what is causing it to die and stop working.
Alright I'm pretty fed up with this phone. I've had it for a year now, having probably 4 of them now due to replacements (GPS problems, static phone call problems, etc.) that Verizon has replaced. The same problem I have had on ALL of the Samsung Charges I have had is terrible terrible general lag, especially with the keyboard.
I have to restart my phone at least 6 times daily just to be able to use it, if I don't it lags so much I can "click" on an app just like the web browser and it will take 15 seconds to load up, same for messaging etc. It's mostly noticeable with messaging where I can start up the messaging app and click on a text message and it will take 20 seconds to load, then I click on the text entry box and the keyboard doesn't show up for another 20 seconds and from there each key I press only happens seconds after I type them, not instantly like it should be.
Things I have tried:
- Task killer apps to free up memory
- Cache cleanup apps
- Resetting the phone to factory defaults (this has happened on EVERY charge I have received so it doesn't seem to be local to my specific phone at least)
- Erasing the SD card / using the phone w/o a SD card
- New keyboard apps
- Updating (has been like this through various versions of android)
Things I'm getting close to trying:
- Throwing my phone at a wall
- Running over my phone with my car
- Hitting my phone with a bat
- Using my phone as a lightning rod
When I clear the memory (usually at around 320/373 MB being used) it only goes down to around 270/373 MB being used. I barely have any apps installed apart from the default phone apps. My phone is using that much memory even a minute after restarting it, doing so only fixed the problem for the short while before it starts up again. It happens directly after a factory reset as well so it's not like I have any super big apps I downloaded that are causing it.
My keyboard process actually hangs at times and errors leaving me with no keyboard at all until I restart my phone:
"The application Samsung keypad (process com.sec.android.inputmethod.axt9) has stopped unexpectedly. Please try again."
It's seriously pathetic, I used to have the Droid X, Incredible, etc. and never had any problems like I have with this phone. I would rather have my old Env touch back with just general web browsing, at least it could text without erroring.
Any help or suggestions would be greatly appreciated.
How about flashing it with a different ROM?
haza12d said:
How about flashing it with a different ROM?
Click to expand...
Click to collapse
Not really into the whole doing things that can brick the phone, if I do that I'm stuck with it and Verizon won't take it back because I did "fowl play" things.
Unfortunately this phone is horrible stock, but fortunately flashing another ROM is super easy. Also it's pretty hard to brick this phone. And if you did is also pretty easy to fix it back to stock. This phone really is pretty amazing with a custom ROM
Sent from my SCH-I510 using XDA
toups5 said:
Not really into the whole doing things that can brick the phone, if I do that I'm stuck with it and Verizon won't take it back because I did "fowl play" things.
Click to expand...
Click to collapse
No guts no glory. Or usable phone, in this case.
Sent from my SCH-I510 using xda premium
toups5 said:
Not really into the whole doing things that can brick the phone, if I do that I'm stuck with it and Verizon won't take it back because I did "fowl play" things.
Click to expand...
Click to collapse
Custom rom is definitely the way to go. There are plenty of places to look and read to get an idea of what you're doing and there is almost always step by step instructions. It makes a world of difference and is like a new phone when you're done. Read up on Tweaked 2.0 and the custom FP1 (PBJ) kernel. And if something goes wrong there are plenty more places and people that can help you get it back to stock so that Verizon will be none the wiser that any "fowl play" was involved. Not difficult at all (if you follow the instructions exactly) and is WELL worth it. As KV said: "No guts, no glory"
toups5 said:
Not really into the whole doing things that can brick the phone, if I do that I'm stuck with it and Verizon won't take it back because I did "fowl play" things.
Click to expand...
Click to collapse
Just root it then and remove the Verizon bloat. Stock rooted runs well without all of the useless crap.
Sent from my SCH-I510 using XDA
Get a different phone. The problem seems to be between you and the Charge!
Stock works really well since FP1. My only major complaint is the camera on the replacement I have doesn't focus worth a damn!
Gotta agree with the guys here.
Root and ROM, bro. The Charge, otherwise, blows.
I would do Tweak2.0, but debloated stock FP1 would be great too.
The Charge is a great phone with proper software. Software seriously makes it or breaks it.
There are plenty of us on the forums to give advice if you get stuck.
Some tips on flashing the Charge:
I use Odin 1.85
Run Odin as Administrator is Windows 7 or Vista
Remove SIM before flashing
PUT BATTERY IN before flashing
Use a USB port on the back of the computer (not the front ones)
Use the OEM USB cable
Download your ROM file with Getright or verify MD5 checksum
BACKUP any info (your contacts should be synced with Google)
Format SD card (before you Odin a ROM ) as FAT32 with 32K size (you don't have to format, but I do)-- note that you can format the sdcard with Windows with the sdcard in the phone if you have mass storage on
NEVER, EVER use the phone button in Odin, you MUST use PDA
Be patient when flashing, it seems to take 7 minutes or so.
Be patient on first first, it has to build Dalvik cache, etc.
If you need help, ask!
xdadevnube said:
If you need help, search!
Click to expand...
Click to collapse
Fixed that for you.
Sent from my SCH-I510 using xda premium
if you suspect the keyboard app could be the issue, have you tried another one, or tweaking your keyboard settings? I use ICS keyboard - works great for me. sounds like there could be a conflict somewhere in there..
jco23 said:
if you suspect the keyboard app could be the issue, have you tried another one, or tweaking your keyboard settings? I use ICS keyboard - works great for me. sounds like there could be a conflict somewhere in there..
Click to expand...
Click to collapse
yeah I tried that..
Got too fed up last night I flashed it, used this:
http://forum.xda-developers.com/showthread.php?t=1406951
It is much faster however still not perfect w/ messaging (the main problem as its what I use the most and therefore notice it the most on), still takes some time for the messaging app to load up and additional time to load each thread and then time to load the keyboard once in a thread.
Also if anyone knows that flash and knows the answer to these new questions that would be great, have tried searching...
- When using speech to text on the new keyboard I get an error "Could not connect" to the microphone instead of getting the usual "Speak Now"... persists through restarting
- Can you still screenshot with the charge on this flash? Used to be back + home button, no longer works. (found people talking about "Tweaktools" but found nothing of what they are, where to get them etc. )
About your last one - go to Terminal Emulator (may have to download from play store) type su, press enter, type tweaktools, press enter. I personally would recommend getting something like ShootMe as the stock service isn't very reliable (back button and home have issues)
Sent from my SCH-I510 using xda premium
I'm running Eclipse 2.0 and it's hands down the best phone I've ever owned. Although this is the first phone I ROM'ed...
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.
My MT4GS has some serious RAM issues. I even think it may have leaky or bad RAM. Basically, Android will close background apps to make room to run new apps, right? So here's what mine does: When I load an app, Sense closes. And when I try and play games like Draw Something which require a second app (FB mobile) to log in, it closes Sense AND Draw Something. So I'll tap Draw Something, it'll load, then switch to FB Mobile, log in, then switch back to Draw Something but because it closed Draw Something it has to start loading from scratch, requiring a new log in, then when it does that it closes Draw Something again. It basically creates an infinite loop, if I let it run without hitting back (several times) or home. And then I get to wait for Sense again.
I've tried third party RAM apps and they don't seem to help. (I don't understand how they could anyway.) So I'm hoping someone has a solution outside of rooting.
But if not, I've never rooted a device of any kind before. So I'm really apprehensive to try it without detailed knowledge of every step required. And if I rooted, I'd probably want a new ROM, yes? I've heard Bulletproof is nice, but I don't know a lot about others.
All help is appreciated. Thank you.
Rooting is no big deal. We could have you rooted in 15 minutes. I believe achieving "S-Off" is what you're trying to avoid......even though it's not too bad either. But it sounds like you may have used up any swap file your system has & could stand a bit more. Probably installed quite a few apps that are running in the background. You could probably reformat your SD Card to Ext4 and get rid of the issue but you'll need a custom recovery. That's how it sounds to me anyway.
WeekendsR2Short said:
Rooting is no big deal. We could have you rooted in 15 minutes. I believe achieving "S-Off" is what you're trying to avoid......even though it's not too bad either. But it sounds like you may have used up any swap file your system has & could stand a bit more. Probably installed quite a few apps that are running in the background. You could probably reformat your SD Card to Ext4 and get rid of the issue but you'll need a custom recovery. That's how it sounds to me anyway.
Click to expand...
Click to collapse
I do have a few background apps, but I've tried to avoid a ton and I only have one widget running.
I'm willing to do what I need to to get my phone working the way it was intended.
GiftigDegen said:
My MT4GS has some serious RAM issues. I even think it may have leaky or bad RAM. Basically, Android will close background apps to make room to run new apps, right? So here's what mine does: When I load an app, Sense closes. And when I try and play games like Draw Something which require a second app (FB mobile) to log in, it closes Sense AND Draw Something. So I'll tap Draw Something, it'll load, then switch to FB Mobile, log in, then switch back to Draw Something but because it closed Draw Something it has to start loading from scratch, requiring a new log in, then when it does that it closes Draw Something again. It basically creates an infinite loop, if I let it run without hitting back (several times) or home. And then I get to wait for Sense again.
I've tried third party RAM apps and they don't seem to help. (I don't understand how they could anyway.) So I'm hoping someone has a solution outside of rooting.
But if not, I've never rooted a device of any kind before. So I'm really apprehensive to try it without detailed knowledge of every step required. And if I rooted, I'd probably want a new ROM, yes? I've heard Bulletproof is nice, but I don't know a lot about others.
All help is appreciated. Thank you.
Click to expand...
Click to collapse
Ouutside of root...factory reset and watch what you install...there's little chance for a permanent fix outside of root though...inside root...or once your rooted...use es task manager and es startup manager...my mytouch was doing something very similas until rooted...also the v6 super charger will definitely help once your rooted...
1inspire2flipout3huaweiAscend?4transform5Evo6Sensation7backflip8xperiaPlay9xPlayR800i10OneX11GalNexus12HTCamaze13Evo3D14samInfuse15MyTouch 4G Slide
If you root (Very easy to HBOOT unlock, flash recovery, flash root if you use the Toolkit in the development forum) then you can check out an app like Greenify maybe.
try the app "fast reboot" by great bytes software. Been using it since i got a doubleshot, it really helps.
I've done all of the above and flashed miktouch. It's much faster. Ands I'm giving fast reboot a go.
Sent from my MikTouch_4G_Slide using xda app-developers app
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!