First of all, I expect that mrs. reinbeau doesn't close this post, I feel it necessary in order to solve the main problem of my ROM.
This post is intended to all of you that have the problems so called SoD (Screen of Death), when the phone sleeps but don't awake... and the frozen screen problems too...
It's a new ROM progressively created from scratch in order to determine where is the problem.
Please, use it and comment here if the SoD issues are gone or remains; everything you want to say but ONLY RELATED TO THIS PROBLEM.
The instructions are easy:
- If you come from Test 2, or Test 2.1, simply flash Zeus v5 Lite over it. It won't wipe your data.
- Otherwise, make a wipe data / factory reset before flashing Zeus v5 Lite
- AFTER INSTALL IT, IN BOTH CASES, FORMAT /CACHE (--> mounts and storage --> format /cache).
- Once you have Zeus v5 lite, directly flash Zeus v5.03 over it.
- Zeus Test 2 (full wipe, complete ROM): d7fc02c423df42ecbdc4a9a2a0f7255c - Mirror
- Zeus Test 2.1 (dalvik and cache wipe, complete ROM): a3c20899db2d59e09fab60dd6aeb6094 - Mirror
- Zeus v5 Lite (dalvik and cache wipe, complete ROM): c55155a8aac4e5300b8239c08e739bd6 - Mirror
- Zeus v5.01 Lite (dalvik and cache wipe, update to Zeus v5 lite): 9a2907c9aec64857495fec093495afd1 - Mirror
- Zeus v5.02 Lite (dalvik and cache wipe, update to Zeus v5 lite): eee81e29f285d261fe442a370bb4dffb - Mirror
- Zeus v5.03 Lite (dalvik and cache wipe, update to Zeus v5 lite): f52fc7b9c2534da91c09f937c13b13f5 - Mirror
Changelog:
Test 2: Initial base ROM lightwighted, with original kernel and some opts.
Test 2.1: Fully themed Test 2, additional cleaning and some opts.
Zeus 5 lite: Prerelease, test it please... It has a lite zeus script, txpower, some opts, new Google Play Store...
Zeus 5.01 lite: To flash over Zeus 5 lite. Stock kernel recompiled with Linaro (unaltered, with stock configuration), with a new runtime parameter to enable/disable led dimming (thanks to sergey1369) and with led supply current reduced in a 20% to save battery. Updated zeus script with options to enable/disable led dimming and to change lockscreen. Fixes symlink to 'cp' busybox command.
Zeus 5.02 lite: To flash over Zeus 5 or 5.01 lite. Same features as 5.01 + cache again with ext4, new optimized mount options and fixed the auto enable/disable dimming at boot.
Zeus 5.03 lite: To flash over Zeus 5, 5.01 or 5.02 lite. Same features as 5.02 + new governors(interactiveX, Smartass2 and OndemandX[default]) + deadline + total control of the leds (high intensity, low intensity, enable/disable dim, timer) + txpower stock by default (touch it if you want) + runtime enable/disable fsync() enabled by default + upgraded zeus script... look into it!
Regards and thanks!
About 12 hours with your fix and everything is OK. I have v3.2b.
Pr3dator? said:
Is there a way to fix this on cyanogenmod
Envoyé depuis mon LG-P970 avec Tapatalk
Click to expand...
Click to collapse
What do you understand with ONLY RELATED TO THIS PROBLEM?
pk76 said:
About 12 hours with your fix and everything is OK. I have v3.2b.
Click to expand...
Click to collapse
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
tsakaji30 said:
Now I have a worst problem: after the SoD, I did try to restart the phone by pulling out the battery and now it doesn't want to start again! When I push the ON/OFF button, the 4 leds start to blink but the screen remains in black (not off, is there a difference).
Then after 5 or 6 tries, it start and show me the CWM menu, I did apply your fix and still the same thing (doesn't want to pass from the LG logo, and sometimes even doesn't show the LG logo!).
What do you think is happening? I think is something related to the Graphics driver, maybe something changed in the Kernel to give more graphics performance or something, I really don't know...
Click to expand...
Click to collapse
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
And no, there's no strange changes to kernel to boost anything that can harm your phone.
Regards.
Huexxx said:
Hi,
if i have readed well, first you have the problem, and after that you have flashed my fix, isn't it?
Maybe you have any corrupted at /system, and the fix doesn't fix a ROM, only change certain things in the ROM to look for the SoD problem.
Try to flash V3x, then V3.2x and then the FIX 1.
Regards.
Click to expand...
Click to collapse
Ok, I'm going to try this again from scratch.
Another important thing: I was having the same problem since V2, then I flashed V3 and it was gone by 2 or 3 days, then, yesterday my phone restarts itself and after that is a chaos hehehe
If is not something related to the graphics, then maybe is something related with the way your version commit data in the memory and maybe there is a data corruption that makes the phone behave weirdly.
Anyway, thanks a lot for your big effort, I regained the thrust in my phone after testing your zeus rom (i was just to sell the black and buy a Nexus hehehe).
Regards!
Thread cleaned
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Huexxx said:
Hi,
forgot the last fix posted on the other post... this is a new fix. Although you don't have problems with the oder fix, there supossedly are people that have problems...
Regards.
Click to expand...
Click to collapse
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
reinbeau said:
No worries, I won't close this thread, let's keep it on topic - and I'm a Mrs, not a Mr.
Click to expand...
Click to collapse
Sorry!!!!!!!!
pk76 said:
So, you recommend me to use the newer version "b" fix or i can stay with the older one. Thanks for your great work. :thumbup:
Click to expand...
Click to collapse
Everyone can do what he want! The "old" fix was a quick attempt to fix the problem. While you don't have the problem, don't try this stuff becuase it's intented to catch the problem; no problem -> no catch...
Someone said that with the "old" fix the problem persists, so I have created this post to progressively approach the problem to know where is it, and then erradicate it!
- If people try this fix and the problem persists, it will be at the ROM itself, not in the kernel/boot.img/build.prop -> then we'll try to find it on the ROM.
- If people try the fix and the problem is gone, the problem is at my latest kernel/boot.img/build.prop, so I'll change progressively that stuff until we get the error again...
There's no other way IMHO.
Regards.
already activated fsyn and flahs ur fix, I ll give my feedback in a few hours, just let my try...
With my fix (THIS FIX, ON FIRST POST) there's no possibility of deactivate fsync because it's a diana kernel feature and wiht my fix you will have the stock kernel...
Thanks!
First of all, I'm not using this rom, I'm using cm7 temasek's build BUT I think somehow is related because this "SoD" is happening at the new builds...
And I wonder why? well I don't know but, it may be something with the rom itself?
Zeus is "official" and cm7 is "mod" but they're both based on gingerbread so there must be some connection.
I'm not trying to complicate things but trying to help, because this is not an isolated issue from zeus, this is present at cm7 new builds too.
Sorry but is not the same IMHO...
- CM7 are constantly changing and for whatever reason the most recent builds have this problem. So, different builds...
- my rom comes from stock rom (that doesn't have the problem, or that's what we hope...) and in a certain moment with some modification (of my own) the problem has emerged, WITH THE SAME BUILD.
When I find my problem, I hope it can allow cm7 people to fix the problem, but I'm afraid there are a lot of reasons why it can happen.
This thread is to test my rom with different things trying to find the bad change made to my rom, not a thread to discuss about Screen of Death.
Thanks anyway.
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
I also never faced this SoD with your ROM (3.0n) and I'm using it for a while now. I skiped 3.1 patch and installed 3.2 yesterday and no SoD. But with cm7 I had this once don't know what version.
On the other hand a colleague at work have this issue with 3.1n a few days after install. I installed the 3.2n and we'll see.
yesterday I got 2 frozeen displays and have to remove battery,
Today (like about 5 hours ago) flash this fix and until now I dont have that problem at all... I just want to give my feedback, but I ll post again 5 hours later to say if donst get the problem again.
Sry about my pretty bad english.
Hackpb said:
Hi Huexx!
First of all thank you for your patience and for your excelent work whith this phone.
About all this things of SoD, I whant to ask you something: have you ever faced it?
I don't know but I'am using your Rom since first and have installed the 3.0 then the 3.1 and then the 3.2, and I have never faced the SoD. How offten are this SoD's happening?
I'am using interactivex whit deadline and Fsync enabled.
Click to expand...
Click to collapse
I've faced only one SoD, thats the reason i need people that have experimented more sods because their way of use the phone.
Sent from my LG-P970 using XDA App
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
henriqueberthem said:
Hello friends.
I have a Galaxy S 9070 almost 1 year old and he is currently rooted and the Cocore 9.8 TWRP and use Cocore Manager to adjust the kernel options.
From a while now he began to crash randomly, sometimes crashes when squeegee Facebook app, Whatsapp app, in the middle of a video in Youtube app.
It is very annoying having to restart the phone to continue what I was doing!
Could anyone help me figure out what might be happening?
Click to expand...
Click to collapse
Did you overclocked it? If you did - that is the reason.
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
henriqueberthem said:
I'm not using overclock.
Min clock: 200mhz
Max clock: 1000mhz
Hovernor: pegasusq
I/O: sio
Click to expand...
Click to collapse
Try using CoCore 8.2. And revert settings that you have changed to default and see what happens.
Deepsleep should be 3 or 4, on 5 it gives same result that you are getting. Freez and reboot on some time.
My deepsleep is "3".
henriqueberthem said:
My deepsleep is "3".
Click to expand...
Click to collapse
Then do first thing I told you before that. Without any customization, and with 8.2 version.
Ok, I'm going to flash to 8.2 cocore and keep the default configuration for testing
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
henriqueberthem said:
I tested version 8.2 with the settings in stock and did not freeze in no time.
But I think this version a bit outdated. Could test a newer version?
I looked today launched a new version of cocore, I think I'll install it and test.
In my archives I also have the 8.3, 8.6 and 9.6.
Click to expand...
Click to collapse
Try that newest.
8.2 was pretty good. No matter if it is old.
I tried the newest (Cocore E-v10) and still suffering from random freezes, causing the responses to touch are noticeably slower.
At this time I will flashing to version 9.6
Hello friend.
I tested the newest version of the kernel (refresh-r08 @ 14-Jul) and a few days ago that had no reboot.
But before I used the app tweek (cocore manager v2.1 or Kui) and believe they left is that my system unstable, because after that they uninstalled and I started to tweek the command promt using the Busybox my system has become lighter and reliable.
So it leads me to believe the problem was in the app customization.
Hello everyone, I'm currently running bliss rom, despair kernel, also got xposed (amplify, greenify, powrnap) and I'm looking for solution of this weird problem (screenshot). What should I do?
seruss said:
Hello everyone, I'm currently running bliss rom, despair kernel, also got xposed (amplify, greenify, powrnap) and I'm looking for solution of this weird problem (screenshot). What should I do?
Click to expand...
Click to collapse
Close all that running apps.
Try Advanced Taskkiller
The phone was on standby and no apps were launched ?
You had Facebook running, or are you getting notifications through Chrome? If the former, uninstall it and get your notifications through Chrome.
Also, Xposed and its modules could be a cause. Try uninstalling them and see if battery life improves.
get rid of xposed, then reflash your rom and kernel
Hello
I have a G800F with nougat RR installed, xposed, Spookcity kernel 1600MHz and some apps. I feel it extremely laggy. I tried also to freeze all apps except the minimal apps I use for work, disable xposed, restore stock keyboard, but the phone is still laggy. It's the hardware so limited or if I revert to MM or change someting else it could be more responsive?
Thank you
Alefello said:
Hello
I have a G800F with nougat RR installed, xposed, Spookcity kernel 1600MHz and some apps. I feel it extremely laggy. I tried also to freeze all apps except the minimal apps I use for work, disable xposed, restore stock keyboard, but the phone is still laggy. It's the hardware so limited or if I revert to MM or change someting else it could be more responsive?
Thank you
Click to expand...
Click to collapse
Try whipping the Cache. It seems to help on my girl friends old S5 mini that was also extreme slow.
Alefello said:
Hello
I have a G800F with nougat RR installed, xposed, Spookcity kernel 1600MHz and some apps. I feel it extremely laggy. I tried also to freeze all apps except the minimal apps I use for work, disable xposed, restore stock keyboard, but the phone is still laggy. It's the hardware so limited or if I revert to MM or change someting else it could be more responsive?
Thank you
Click to expand...
Click to collapse
have you done a clean install? i use RR 5.8.5 with spoocity kernel and i have no problem. what cpu governor are you using?