I'm rooted on the stock ROM (.55) with the doomlord's kernel, busybox pro, and fauxclock installed. I set a few of his recommended options but didnt change the governor or scheduler.
Ever so often, when I go to turn on the screen, the phone is unresponsive and I have to reboot. Not sure what's causing it. I'll turn off some stuff and see if that helps.
Anyone else having any freezing probs?
Sent from my D6503 using XDA Premium 4 mobile app
Hmm odd
Have you edited developer settings and if so tell me
And with faux clock what settings are you using?
I had GPU rendering on but thats all. I turned off Dev Options last night.
In Fauxclock, I only enabled recommended options:
CPU Clock - disabled hotplug
Thermal - enabled intellithermal
GPU Governor - enabled msm-adreno-tz
IO Scheduler - disabled Entropy
Today the phone has behaved though. I do need to check if it stays off when I power off though.
EDIT: Doesn't stay off. Goes into a boot loop.
EDIT 2: Uninstalled Faux and phone shutdown ok. Meanwhile, seeing a 'Error Initializing USB' message on boot up.
Sent from my D6503 using XDA Premium 4 mobile app
I kind of had that issue, from romAur thread:
Mr.R™ said:
Anyone having an issue where when they press the power button to sleep the device won't wake up for about 30secs after? Not sure if it's going from 2 to 2.1 or an xposed module so thought I'd ask
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
As you are using a stock rom we only have the kernel in common so that could be the culprit although as I said mine seems to come back to life within a minute or so
Sent from my D6503 using Tapatalk
Mr.R™ said:
I kind of had that issue, from romAur thread:
As you are using a stock rom we only have the kernel in common so that could be the culprit although as I said mine seems to come back to life within a minute or so
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Interesting - I don't think I waited to see if it came back up to this point. If it didn't respond, I'd just reset it. But yah - I'd suspect that something about the custom kernel was causing issues. OR, there are certain options in Faux that were causing problems - for ex. CPU Governor or IO Scheduler choices. It would take some experimenting - and changing only one parameter to really get an accurate fix on the problem.
I'm currently trying to figure out how to create a flashable stock kernel from the firmware sources (that was downloaded from Sony update); so I'll probably flash the stock kernel back once I figure it out.
Otherwise, since last night the phone is behaving OK. Current setup:
- CWM + SU 1.94 (root)
- Doomlord's v5.0 kernel
- Stock .55 ROM (relocked the bootloader, did phone repair, re-un-locked the bootloader)
- No other tweaks
Still not sure what is causing this but when I replied to you I forgot I had updated romAur so was on default kernel which was when it would wake up 30 secs later, now on romAur and doom kernel I am getting the same issue where it just won't wake up even when a call is incoming. Might be an issue with. 69, it's actually starting to drive me nuts, bring on the cm/AOSP builds I say haha
Sent from my D6503 using Tapatalk
Mr.R™ said:
Still not sure what is causing this but when I replied to you I forgot I had updated romAur so was on default kernel which was when it would wake up 30 secs later, now on romAur and doom kernel I am getting the same issue where it just won't wake up even when a call is incoming. Might be an issue with. 69, it's actually starting to drive me nuts, bring on the cm/AOSP builds I say haha
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yeah - It's been a challenge to get this phone to behave completely stable; but at this point, it's down to a few random issues:
- the charge LED staying on after using the magnetic charger in my car
- the camera app FC'd a few times in the evening while I was at the gym; clearing the app's data and a reboot seemed to fix it.
Honestly, running the stock .55 firmware with root and the .55 stock kernel has been the least glitchy combination for me. I may try some of these new ROMs and Doomlord's kernel again after the next Z2 software update. It looks like another update will be coming in the next month (hopefully).
I've posted the .55 firmware and the stock kernel (to reflash after rooting) in the General section if you wanna give that a shot.
Related
I'm currently running Siyah 2.6.6i and Shep's MIUI 2.1.6v2. I'm having a weird issue that I've seen mentioned in the dev forums for the Siyah kernel, but nobody has mentioned a fix or suggested anything to try. Basically, when the screen on my device turns off while running on battery, the data connection turns itself off will not re-enable itself until I wake my phone, and sometimes I have to toggle airplane mode to get it to come back. This would be fine, as I'm on wifi 95% of the time, except when the data connection gets disabled, I no longer receive text messages, even on wifi. I've tried running both the OnDemand and Lulzactive scalings, but neither have made a difference. The only thing I've been able to do to fix this myself is to flash back over with the default MIUI kernel that comes with the build and not use the Siyah kernel.
Does anyone have any suggestions on how to fix this?
Looks like nope
Sent from my páhhōniē
roll back to 2.6.6... seems that 2.6.6i is nothing but trouble for a lot of people.
2.6.7 works fine..
Sent from my SAMSUNG-SGH-I777 using xda premium
It must have been an issue with 2.6.6 and 2.6.6i. I installed 2.6.7 this morning, and it seems to have fixed the issue with text messages, however my battery life is suffering a little bit. I don't mind, as long as I can keep communications coming in.
Thanks for the suggestions!
As the title suggests.
Having a very strange issue at the moment where my phone will randomly switch off when it's in deep sleep, then when I've restarted I'll find some of the more recently installed apps have been deleted/uninstalled.
What on earth could be causing this?
Using siyah kernel 2.6.11 and wanamlite rom V7.8 (2.3.6)
Sounds like a to low under volt,(you may not have undervolted)... try neak kernel, its the best by far..
I think that will sort your problem out.
If not then wipe and reflash your rom.
Sent from my GT-I9100 using XDA App
haven't undervolted at all, and it's set at 200-1200 MHz..
I'm not 100% sure if I had the issue with void echo (kernel I was using before), or an older siyah build but it's definitely possible.
What could explain the uninstalled apps though? it's really bizarre...
I'm going to go ahead and bump this as its happening yet again, but slightly differently as well.
I downloaded a game around 3 days ago and have rebooted once since then (yesterday) and just found that I could not launch the game (got a FC pop-up), but it was actually still installed. I then transferred the game installation to my SD card, and it launched. I then rebooted as I switched back to a different kernel via recovery mode, and now the game is uninstalled (along with at least two other apps I've noticed so far).
What is happening??? Surely someone has an idea.
Hello guys,
To get right to it, everything was fine when I was on MIUI 2.5.18 but when I updated to 2.6.1 the issue started happening. I will try to explain the issue to the best of my ability.
About 4-5 times a day my phone will just out of no where become ungodly slow as in it takes the phone ~45 seconds to recognize a touch on the screen or push of a button. So when this starts I have to reboot, and normally I have to Hard Reboot (hold power till GT-i9100 screen appears). I was running Neak at the time so I switched to Siyah and it as still an issue, I also updated to 2.6.8 but that did not help either. Last night, I changed to AOKP thinking it may be a ROM issue and even on the stock Kernel I still have the issue...
At this point I believe it may be a phone issue. Has anyone had something like this happen? How did you fix it if so? Should I attempt a flash back to Stock and run that for a while and see how it goes?
I will try and get a video today if my room mate comes home.
Thanks in advance!
tory13579 said:
Hello guys,
To get right to it, everything was fine when I was on MIUI 2.5.18 but when I updated to 2.6.1 the issue started happening. I will try to explain the issue to the best of my ability.
About 4-5 times a day my phone will just out of no where become ungodly slow as in it takes the phone ~45 seconds to recognize a touch on the screen or push of a button. So when this starts I have to reboot, and normally I have to Hard Reboot (hold power till GT-i9100 screen appears). I was running Neak at the time so I switched to Siyah and it as still an issue, I also updated to 2.6.8 but that did not help either. Last night, I changed to AOKP thinking it may be a ROM issue and even on the stock Kernel I still have the issue...
At this point I believe it may be a phone issue. Has anyone had something like this happen? How did you fix it if so? Should I attempt a flash back to Stock and run that for a while and see how it goes?
I will try and get a video today if my room mate comes home.
Thanks in advance!
Click to expand...
Click to collapse
I had the random slowdown issues with NEAK - but never had that on CM9 or Siyah kernels and not on ktoonsez's MIUI kernel as well.
Basic stuff - did you do a complete wipe - cache, dalvik cache, format /system and ran Jivy's kernel cleaning script just to be sure?
Does it happen during a certain activity e.g. opening a certain app or anything else? Do you have any memory management apps installed?
May need to try the cleaner script but yes complete wipe with both cache's and system when I went to AOKP
and no its totally random just when ever it feels like it. As far as memory management I went through the agonizing long steps when it was slow and only about 500mb of memory was being used and only on occasion does it go over 600mb
What are some good memory management programs?
There are so many variables I would say flash back to.stock completely, (wipe first obviously) then see if problem persists. If it does then u know its a hardware issue.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
i had a similiar problem on my captivate after installing a eurokrank rom. i found that if u have the govenor set to powersaver it made my phone really slow/ laggy. once i changed it to ondemand or performance it picked right back up. maybe tinker with that and see if it maybe clears it up a bit
Cleaner script seemed to work! Never thought I would ever have to use it but oh well.
It has not happened all weekend, so we will see how it goes the rest of the week!
Thanks again guys!!!
Today i wiped cache/dalvic cache/battery stats, then i started browsing the XDA Forum, suddenly the phone froze,then for two seconds a continious clicking noise appeared near the camera /cpu?/,after that the device restarted,but very quickly-without showing the siyah logo...This has happened once before, i was using ICS 4.0.4 with stock kernel...
Currently i'm with JB/siyah 6.0b5;
The device seems to be working just fine now,but i'm a little worried.Have you encountered this one before?
Sent from my GT-I9100 using xda app-developers app
umex said:
Today i wiped cache/dalvic cache/battery stats, then i started browsing the XDA Forum, suddenly the phone froze,then for two seconds a continious clicking noise appeared near the camera /cpu?/,after that the device restarted,but very quickly-without showing the siyah logo...This has happened once before, i was using ICS 4.0.4 with stock kernel...
Currently i'm with JB/siyah 6.0b5;
The device seems to be working just fine now,but i'm a little worried.Have you encountered this one before?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Nope, the only time I've ever heard a clicking noise was using the CM torch, I decided to try the 'high' setting. Clicking started so I turned the torch back to normal brightness. Never had it since. Keep an eye (ear?) on it.. If it happens again then I'd flash a fully stock ROM & see if it happens on full stock. Have you undervolted/overclocked at all? Could be something to consider if you have.
Hopper8 said:
Nope, the only time I've ever heard a clicking noise was using the CM torch, I decided to try the 'high' setting. Clicking started so I turned the torch back to normal brightness. Never had it since. Keep an eye (ear?) on it.. If it happens again then I'd flash a fully stock ROM & see if it happens on full stock. Have you undervolted/overclocked at all? Could be something to consider if you have.
Click to expand...
Click to collapse
Yes, I have undervolted with two steps, using CPU ADJUSTER, but for the last three days the phone was OK.And the first time this thing happened to me I didn't even know what is undervolting...It could be from the kernel, I just flashed JB with Siyah 6.0b4 (the previous version)...I'll see how the device behaves without undervolting...If it happens again, i'll flash fully stock rom...
I've this strange problem, it only happens when i screen off my i9300 and let it in sleep mode, the phone will restart itself. I've tried both CM10.1 and Stock rom, but gave the same problem. I was able to minimize the auto-reboot-in-sleep-mode by writing an app to prevent the phone going into deep sleep by locking in the wakelock and send four threads to occupy the quad core cpu. Using this app drains battery, it did solve my problem somehow, i still get auto-reboot but the frequency was minimized by 90%.
Any idea of what causing this?
edwin3210 said:
I've this strange problem, it only happens when i screen off my i9300 and let it in sleep mode, the phone will restart itself. I've tried both CM10.1 and Stock rom, but gave the same problem. I was able to minimize the auto-reboot-in-sleep-mode by writing an app to prevent the phone going into deep sleep by locking in the wakelock and send four threads to occupy the quad core cpu. Using this app drains battery, it did solve my problem somehow, i still get auto-reboot but the frequency was minimized by 90%.
Any idea of what causing this?
Click to expand...
Click to collapse
Using any custom kernel?
Sent from my Nexus 7 (2013)
chrismast said:
Using any custom kernel?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I've tried from cm10.1 to Stock rom, kernel which is what im using right now. All gave me the same result.
Having exactly the same issue, using partial wake lock app to prevent it but also drains battery, have you found a cure for this? I{m on CM10JB but happening the same on stock
edwin3210 said:
I've tried from cm10.1 to Stock rom, kernel which is what im using right now. All gave me the same result.
Click to expand...
Click to collapse
Havin same issue, any clue?
.
try CM11 with a custom kernel like boeffla for CM...and do a full wipe even the internal storage and see if it goes better
Is it solved ?
PearOfSteel said:
try CM11 with a custom kernel like boeffla for CM...and do a full wipe even the internal storage and see if it goes better
Click to expand...
Click to collapse
Hi, Has anyone tried this solution ?
Did it worked ?