I have an att xt1097 unlocked with sunshine. I installed the debloated stock marshmallow ROM for xt1097 (from Brazil I think) ROM was great, no problems, I got bored installed a cm based ROM, again, everything great. Then I installed some different kernels, ending back up on the stock based ROM running the krait kernel, but now, my CPU all cores never dip below 1000 MHz and the phone stays hot. I have done a complete wipe, reinstalling the stock based xt1097 ROM several times,yet the problem persists. Anyone got any ideas, or know of a script or program to get rid of residual scripts or anything that may be causing my issue? I am away from a PC, won't be near one for days to be able to do a complete wipe of all my downloaded files and everything.
Related
I've been experiencing random reboots since I bought my Developer Edition but today I think it hit me real hard with the random reboots in short intervals.
this kind of reboots happened to me both on completely stock and custom rom but today heavy reboots occurred when I was on Insert Coin 2.0.3 (S-Off).
According to someone's advice, I installed catlog and try to record the events until the phone reboots. So I post my logs here and hope some one could save me from this misery.
the first file was recorded with "write to disk every 200 lines" so it may miss some very last event when phone rebooted. The next ones were recorded with "write to disk every 100, 20 and 10 lines". I hope some devs could have a clue on what is happening with my phone.
I also save the log file AFTER phone reboot but they were too big to attach. If you think those might helo, I'll post them somewhere else.
Might be something to do with Xposed
BenPope said:
Might be something to do with Xposed
Click to expand...
Click to collapse
Yeah, I've noticed that some custom ROMs got issues with Xposed on S-Off device. However, as I mentioned earlier, this happened to me while I was on completely stock rom, too.
I've made a few observations and found out that I haven't got a single reboot on AOSP for a whole day but AOKP still gave me random reboots (not as frequent as on InsertCoin but still).
Any help would be very appreciated
might be worth trying to install sense rom again stock or custom and do full wipe, cache and dalvik. strange that an aosp rom works fine. must be something caused by a sense rom, drivers or framework. was this problem introduced when you started using 4.2.2 roms? have you updated to the new firmware.zip?
well, my habit of installing new roms is always do a full wipe so I think the cause of reboot should not be related to that.
After getting no reboot on AOSP roms (carbon, cm 10.1), I decided to go back on custom sense roms but no luck. reboots just came back no matter what roms I was on (renovate rev 45, insertcoin rev36, rayglobe 4.3).
I went to stock again with RUU dev edition (.16 one). Phone gave me a reboot right after I finished setting up (as new phone). However, it has been running stable up to now (3 hours).
Should the reboot have any thing to do with Sense, i'm wondering. I would be very thankful if any devs can help me on this issue. I'm willing to make as many logs as required or install any custom, stock roms if neccessary.
Sincere
hello, i have locked moto and wonder do i need 4.2.2 root to install this rom or 4.4 cause i get bootloop after installing the rom.
Are you currently running jellybean? Sounds like you are not running the KitKat kernel.
Sent from my XT1060 using Tapatalk
Same Bootloop
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
d33pblue said:
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
Click to expand...
Click to collapse
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Info
nitroglycerine33 said:
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did not do a factory reset wipe the first time. I did the second time. Same situation.
The kernel I'm using is:
3.4.42-g3385454
- Jan 23 17:09
System Version:
164.55.2.ghost_verizon.Verizon.en.US
Build #:
KXA20.16-1.25.2
I appreciate you taking the time out to look at this, thank you.
My Xperia SP has a problem: when running benchmark software, when updating multiple apps from the store and sometimes when running stock camera app, the screen turns reddish, slowly dims until it turns off, and the phone restarts, getting very hot in the process. From what I see it's not above 43 degrees, but I think that when it locks up the temperature monitor app also freezes so it doesen't exactly record the actual heat.
When the phone cools off, it's good to go, but until then it restarts all over if I try to use it.
I had this problem using Arch Xperia, CM 11, and a few other ROMS. Now I flashed stock 4.3 CE, using Flashtool, and I have the same problem.
The phone was bought second hand, so no warranty.
Can I do anything about it?
I saw this on my phone in the past but only way this happend to me was that:
1. I was on williamskernel (i dont know how it performes to another people but to me its quite unstable)
2. I was on alpha cm12 and that happened to me under load
btw on cm11 and stock for me ist perfectly stable, phone never crashed like that but when i play heavy games like portal then i have 45-55 degrees celsias .
If you have this problem on stock flashed by flashtool from PC i think that it may be a HW problem.
i had this problem in 4.3 .205 stock and other customs roms based on .205 kernel.
Now i am on .207 kernel with archxperia 1.0.5 and i havent experienced something like this.
Also im using undervolt to 1566 to avoid high temperature during gaming.
I think is your ftf , which one are u using?
I downloaded the ftf from here:
http://forum.xda-developers.com/showthread.php?t=2311964
Yesterday, when I posted my problem, I had 12.1.A.1.205_CE1 - JB 4.3
In the mean time, I decided to try 4.1.2 JB and flashed 12.0.A.2.254_CE .
This one seems to have worked fine in the last couple of hours. I tried to run as many apps as possible to determine it to restart, but it just warmed up a little and kept going. So it seems it's ok.
Also, I had an unlocked bootloader and before I flashed 4.1.2 I locked it back again. If that has anything to do with it.
The problem is that it askes for a system update and if I do it, it will probably take me all the way to 4.3, and maybe the same problems. That notification is so annoying
That sounds like a hardware problem. Is your phone in a case? Maybe it's restricting the airflow to the device.
b3cks89 said:
I downloaded the ftf from here:
http://forum.xda-developers.com/showthread.php?t=2311964
Yesterday, when I posted my problem, I had 12.1.A.1.205_CE1 - JB 4.3
Click to expand...
Click to collapse
download 4.3 using flashtool (devices/check updates) and try
Yes, it is in a case. But with 4.1.2. it doesen't seem to have problems anymore so I hope it's a software issue.
Nathan rd said:
download 4.3 using flashtool (devices/check updates) and try
Click to expand...
Click to collapse
Will try this today. It should take me to 207, right? The phone OTA update service gives me an upgrade to 205, which I understand is problem-prone.
205 was alright, I think it was 201 that had problems. Still, it's probably best that you go for the latest firmware, which is 207.
I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.
Octa_core said:
I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.
Click to expand...
Click to collapse
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?
anmolkakkar said:
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?
Click to expand...
Click to collapse
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.
Octa_core said:
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.
Click to expand...
Click to collapse
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?
anmolkakkar said:
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?
Click to expand...
Click to collapse
Like I said, I have been doing full stock installs, meaning everything is wiped off and I always set everything up from scratch, no backups.
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
umby75 said:
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
Click to expand...
Click to collapse
Sounds like you are suffering from the same symptoms I have. After over a years worth of usage and a couple "dirty" flashes to improve speed / stability my device was suffering from random reboots, slowdowns and lag spikes. In the end the only real solution is a factory reset
I've tried wiping cache, re flashing roms / kernels, trying different kernels (even though I need the zerolemon fix) all without any meaningful success
I'm unsure of the exact cause of the lag though. Even completely stock devices will experience lags / slowdowns after several years and the recommended fix from the manufactures themselves is a factory reset. This is only exasperated by flashing custom roms, kernels and patches which may introduce memory leaks, data leaks or other instability.
Personally I went back to a stock (debloated) Samsung based rom with Emotion's Zerolemon kernel, restored most of my apps and re-setup everything system related. It's now running like-new again.
Sadly there is no "quick fix" for this issue and, like me, your attempts to solve issues regarding speed / reliability by flashing various patches and fixes have come back to bite you.
So:
Backup userapps in Titanium (Do not backup / restore systemdata)
Perform a Nandroid Backup
Flash the rom of your choice (Do not flash the kernel yet)
Factory reset (Wipe system, Cache, Dalvik Cache in recovery)
Boot into android and perform the initial set-up
Flash the kernel in recovery (No need to wipe anything)
Boot back into android and begin restoring user apps and setting everything back up the way you like it.
I know "factory reset" probably isn't the answer you were hoping for but it's the only option I have found which fixes these issues for longer than a couple days..