Develop Bugs

Wake Lag/How to unroot?

I am curious, how come on rooted roms the wake lag is so much worse than stock? Literally takes 2-3 seconds extra to unlock vs stock. Same thing with opening apps, seems slower. Tried midnight rom, viper, etc.
I am thinking of unrooting and just flashing a rooted kernel. Anybody know how I can get unrooted stock image to flash via odin?

afive720 said:
I am curious, how come on rooted roms the wake lag is so much worse than stock? Literally takes 2-3 seconds extra to unlock vs stock. Same thing with opening apps, seems slower. Tried midnight rom, viper, etc.
I am thinking of unrooting and just flashing a rooted kernel. Anybody know how I can get unrooted stock image to flash via odin?
Click to expand...
Click to collapse
Have you, I dunno, looked in the development section? I happen to know of two on the front page, one for odin one for CWM.
---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------
http://forum.xda-developers.com/showthread.php?t=1282415
Sorry, I don't mean to be a ****, but, it was right there man.
I recommend this one. Do a factory wipe, boot do download mode, ODIN this and you are rooted on stock kernel with BB installed, everything else stock. This always fixes things when I screw up my Wimax and Wifi.

daneurysm said:
Have you, I dunno, looked in the development section? I happen to know of two on the front page, one for odin one for CWM.
---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------
http://forum.xda-developers.com/showthread.php?t=1282415
Sorry, I don't mean to be a ****, but, it was right there man.
I recommend this one. Do a factory wipe, boot do download mode, ODIN this and you are rooted on stock kernel with BB installed, everything else stock. This always fixes things when I screw up my Wimax and Wifi.
Click to expand...
Click to collapse
I saw that one, but isn't that bad as I will have a rooted rom and then will flash rooted kernel on top of it?
But any idea as with the wake lag? Do you think it's due to frequences to conserve the battery?

afive720 said:
I saw that one, but isn't that bad as I will have a rooted rom and then will flash rooted kernel on top of it?
But any idea as with the wake lag? Do you think it's due to frequences to conserve the battery?
Click to expand...
Click to collapse
I believe that will install the stock pulled kernel, reinstall /system, leave /data alone....put stock recovery in too I believe. If you do a factory wipe and then flash that via ODIN it's as close to 'bone stock' as you can get (until we get a stock RUU)....plus root.
I don't know about the wake lag. Sometimes my phone does it, most of the time it does not. I've had an SDcard in there the entire time. It's a little annoying at times (like today when I wanted to take the 'perfect picture', but it was ruined by the extra 2 seconds it took to unlock)...it's never bothered me much though.

[Q] Phone isn't bricked, but nothing will revive it!

Hi everybody, I was hoping to get some help here. Be warned, this is a long story.
I was running CM10.1 fine. My phone was lagging for some reason. A quick search told me to clear my cache. I did. I flashed the Darkside cache wipe. Now my phone wouldn't boot. There would be a Samsung Splash screen, then nothing and my phone would (try to) reboot. Again and again.
My (external) SD card had been acting up a lot. It wouldn't be recognized, copies would be slow, and all sorts of problems. So I formatted it. It worked fine. I assumed my phone was back to normal.
I restored my phone to stock via ODIN. It would reboot at first, but I That worked fine. I was happy until I needed my Wifi hotspot back. I rooted via Odin. The Deleting of tethering provision no longer worked. I flashed the Darkside ICS Rom. That worked fine. I missed Jelly bean/stock android. I flashed CM10.1 along with a fresh download of the Darkside cache and data wipes.
The phone didn't boot. Same problem as before. I assumed same solution. I got a PASS! and unplugged the phone. At this point, It showed the stock splash screen (Galaxy SII, Android 4G etc.) and then an animation of the Android with some blue 3D figure spinning in his belly. The %age status bar at the bottom reached 30ish% then stopped. The animation continued and the bar remained at 30% for a very long time. I tried to reboot normally, which would result the Splash screen with a %age bar at 99%, frozen, and to enter recovery which gave me a splash screen then this:
-- Verifying internal MMC block...
Not need checksum confirmation
already executed!!...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC
This is character to character what I read, and there seems to be a dead android with a red triangle in his belly in the back ground.
I can consistently reproduce these two situations, both of which are disturbing. I could try to restore via Odin for the third time, but I risk making things worse.
Thanks for reading the essay. Until I can somehow fix this, I'm stuck with Hercules in a coma.
Any help is appreciated.

step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end

What are you restoring your phone to...ics or jb?
Sent from my Infamous Hercules.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
ClaireH said:
step two, wipe everything except external sd
Click to expand...
Click to collapse
Are you trying to make him wipe his internal storage as well? :sly: lol
Sent from my Infamous Hercules.

ClaireH said:
step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end
Click to expand...
Click to collapse
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.

sauprankul said:
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.
Click to expand...
Click to collapse
Glad to hear you're phone is fully functional...stock jb touchwiz isn't too bad in my experience especially now since a lot of the newer cm10.1, pacman and carbon nightlies are having SODs and RRs.
As far as twrp vs cwm...in my experience twrp has a much simpler user interface which makes it easy to wipe amd theres no need for the darkside scripts. Although if you want to flash a custom touchwiz jellybean ROM then you would need the infamous wipe scripts which are similar to dark side but they've been updated by Jamison.
Sent from my Infamous Hercules.

Hi everybody,
I flashed CWM via ODIN, then I flashed the TWRP .zip. It was easy enough. Then I flashed CM 10.1, gapps and a custom boot animation by nozerogravity (keywords CMX boot animation). All went surprisingly well, and the welcome screen alleviated my concerns.
There still remains the problem that originally worried me something was wrong with my phone: it would lag during the simplest of games. Until I tried other ROMs I didn't know that this was a known issue with CM 10.1. I simply had to lock and unlock to temp fix this problem.
TWRP is much simpler and cooler than the classic CWM. Also, why did CWM conk out on me so? That is the real question. The evidence seems to point to CWM, however, I am reluctant to blame such an established piece of software, esp. considering the fact that it's free.
Thanks everybody, for the help!
*Nota bene: No wiping scripts were needed with TWRP, neither Darkside nor Infamous (I'm not familiar with the latter)

[Q] Sony Xperia S Charging Problems

Hello,
my xperia s has been playing up or is about to die on me. My batterys is fine once charged to 100 etc last a decent time and everything but as soon as the batterys is dead and im out, ill come back and charge the phone only to find no red charging light no screen light or anything. I have managed to get it charging some how by leaving in on the wall charger for about one hour or two then i find itl turn on and charge normaly. This is happening more and more now, i dead when my phones dies its taking the mik to charge from a dead battery!!
Does anyone know whats happening... im using the latest jb stock rom .... i've even used cyangenmod which was fine for ages then my phone kept on restarting and it dead... same problem wouldnt turn on.. so thats how i've now got the stock rom. fully restored no restarting of the phone but it takes like three hours to charge if completly dead!! help anyone?!!?!?

wipe absolutely everything (including internal storage) and flash an ftf and start over
Sent from my AOSP 4.3 Xperia S via Tapatalk

It need sometime to charge battery. It will not turn on imidatly.
Leave it on chargher for some time and it will be god.
This happens to me all the time, no panic anymore.
Sent from my LT26i using xda app-developers app

Ben36 said:
wipe absolutely everything (including internal storage) and flash an ftf and start over
Sent from my AOSP 4.3 Xperia S via Tapatalk
Click to expand...
Click to collapse
Everything has been wiped except storage because i dont see why that would matter? to the other guy thanks but my phone will litterly take 6 hour to even START charging.. there must be something wrong with it, my nexus charges straight away from the wall plug

have you tried different chargers?
Sent from my AOSP 4.3 Xperia S via Tapatalk

Ben36 said:
have you tried different chargers?
Sent from my AOSP 4.3 Xperia S via Tapatalk
Click to expand...
Click to collapse
yh i have

Xperia SP and S roms
Hey mate! I've seen this problem before, and mostly it's because you installed a rom wrong. Try installing the rom again via cwm or twrp, and do an absolute FULL WIPE... format the system, data, cache, delete cache, delete dalvik cache etc and make sure you install the rom properly, that way you shouldn't have this problem anymore hope it works! - if you are not using roms, the reinstall and original firmware via flashtool, that might solve your problem... After that, you can try to charge your phone to 100% then drain it to 0% and charge it again, see what it does. Come back with feedback!
---------- Post added at 07:40 AM ---------- Previous post was at 07:06 AM ----------
I remember having the same problem, and the reason was that i was using a wrong kernel or something. The kernel can be a badass on battery drain, you might want to check that out too

luptatorul said:
Hey mate! I've seen this problem before, and mostly it's because you installed a rom wrong. Try installing the rom again via cwm or twrp, and do an absolute FULL WIPE... format the system, data, cache, delete cache, delete dalvik cache etc and make sure you install the rom properly, that way you shouldn't have this problem anymore hope it works! - if you are not using roms, the reinstall and original firmware via flashtool, that might solve your problem... After that, you can try to charge your phone to 100% then drain it to 0% and charge it again, see what it does. Come back with feedback!
---------- Post added at 07:40 AM ---------- Previous post was at 07:06 AM ----------
I remember having the same problem, and the reason was that i was using a wrong kernel or something. The kernel can be a badass on battery drain, you might want to check that out too
Click to expand...
Click to collapse
I dont think its that because i was using cyangenmod 9 for ages without problem then like 7 months later boom, phone kept on restarting and when it dead it wouldnt charge. so as i said i relocked my phone and put the laitest stock rom on it and the problem charging still occurs

Missing Toggles after flash back to stock!

Hey guys,
Looking for some guidance on a seemingly simple issue.
I had jedi rom installed shortly. Then I actually did a full erase, data wipe, cleared out the whole phone and then flashed to stock through odin. Re-rooted, customized a bit with Wanam exposed, etc. Phone ran fine for a month then the last couple days I started getting a ridiculous amount of force closes on several different apps and on touchwiz.
So i attempted to restore to a backup through TWRP.
BOOTLOOP!!
Tried Reflashing backup, formatting the entire phone again and fresh install of stock Rom Through odin...nothing worked, still BOOTLOOP
Finally, flashed bootloop fix script and all fixed. Back to fresh stock OS.
EXCEPT!!
...When I flashed stock first time (following jedi rom), I still had mobile data & wifi hot spot toggle in my notification panel.
Now, after flashing the same exact stock Rom file, I am missing those two toggles!!!
Wth, how!????
Really curious if anyone knows why this would happen and also how to get those 2 toggles back

Those toggles don't show on factory roms .it not supposed to.
TWEAKED 1.0 NOTE 3
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2576151
TWEAKED 1.0 NOTE 3

BACARDILIMON said:
Those toggles don't show on factory roms .it not supposed to.
TWEAKED 1.0 NOTE 3
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=2576151
TWEAKED 1.0 NOTE 3
Click to expand...
Click to collapse
That's why I don't understand how they were there on their own after completely wiping my phone the first time and flashing back to stock

wrestlerkid said:
That's why I don't understand how they were there on their own after completely wiping my phone the first time and flashing back to stock
Click to expand...
Click to collapse
Because when you wiped you did not format your internal as you should when heading back to stock with Odin. It a step skipped by most
TWEAKED 1.0 NOTE 3

BACARDILIMON said:
Because when you wiped you did not format your internal as you should when heading back to stock with Odin. It a step skipped by most
TWEAKED 1.0 NOTE 3
Click to expand...
Click to collapse
I was almost certain that I did format the internal. Cleared out all of my TWRP backups and all. Obviously I screwed up somewhere tho..
Anyway, Thanks for the link to guide! I followed the steps for adding the code lines to "feature.xml" and rebooted but still no data toggles. Read that the solution to this was a dalvik cache wipe, but ideally a full wipe.
I wanted to avoid this so I revisited sqlite. When I originally tried to get the extra toggles through sqlite editor, I was getting a database error (code 14). Luckily, I was able to correct this and move on to finish the process. Rebooted and toggles are finally showing

wrestlerkid said:
Hey guys,
Looking for some guidance on a seemingly simple issue.
I had jedi rom installed shortly. Then I actually did a full erase, data wipe, cleared out the whole phone and then flashed to stock through odin. Re-rooted, customized a bit with Wanam exposed, etc. Phone ran fine for a month then the last couple days I started getting a ridiculous amount of force closes on several different apps and on touchwiz.
So i attempted to restore to a backup through TWRP.
BOOTLOOP!!
Tried Reflashing backup, formatting the entire phone again and fresh install of stock Rom Through odin...nothing worked, still BOOTLOOP
Finally, flashed bootloop fix script and all fixed. Back to fresh stock OS.
EXCEPT!!
...When I flashed stock first time (following jedi rom), I still had mobile data & wifi hot spot toggle in my notification panel.
Now, after flashing the same exact stock Rom file, I am missing those two toggles!!!
Wth, how!????
Really curious if anyone knows why this would happen and also how to get those 2 toggles back
Click to expand...
Click to collapse
Yea for some reason stock data and stock wifi tethering toggles dont show on stock roms.

Battery Issue (?) Weirdest thing ever. HELP!

Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*

Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home

Hnk1 said:
Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home
Click to expand...
Click to collapse

2000ftt said:
Click to expand...
Click to collapse
Hi
well, I have had used different variants of LG G3s and I found that some ROMS had certain bugs. Like in Fulmics and Cloudy, if you turn off your device on AT&T variant, you can not turn it on again unless you replace the battery again. Even that used to occur on a reboot so it depends really which bugs you might face.
It could be your battery but I will suggest you few things you can do. Firstly, charge your battery to 100% and wait half an half more before you unplug your charger. Next thing, You calibrate your battery as well, maybe there might be an issue. You can find battery calibration tool by Nema in the playstore.
Next thing I would suggest you to move back to STOCK Lollipop / Marshmallow which you can flash via TWRP or KDZ or TOT method. See if that works for you or not. When I faced the issue of my device not booting after a restart or power off unless i reinsert the battery, this helped!
Last, clear dalvik cache / etc and see that helps too. (Would be done if you flash the KDZ)
Also, if you are flashing roms, for example lollipop stock before you flash a new custom rom, make sure you restart in betwee. i.e
flash lollipop stock via twrp. Restart and then install custom rom of your choice. Flashing over sometimes does not work well.
Good Luck and I hope you have a better story for me where everyone lives happily ever after!