Related
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
hi guys i am wondering about that unexplained problem:
some times my SGS I9000 is shutting down!?! i don't know why, by the way my device is "unlocked to work in Algeria" and it was on firmware 2.3.3 BUJVB and now i use 2.3.6 XXJVU
*my device shuts down "sometimes" when i:
-make or answer phone call
-video recording for a time "more then 10 minutes"
-some times just itself
also my device does not want to move apps to USB storage, and is being hot when i use it for a long time "like playing games"
ThAnk you guys, always you are the best in all
trust me bro the ICS that not from sammy it's more stable than sammy rom
give it a try u will really like it and will fined it smoother than sammy rom and faster and now there is more support from dev to ICS
try AOKP with devil kernel very stable and u will never look back to sammy GB
samhawk said:
hi guys i am wondering about that unexplained problem:
some times my SGS I9000 is shutting down!?! i don't know why, by the way my device is "unlocked to work in Algeria" and it was on firmware 2.3.3 BUJVB and now i use 2.3.6 XXJVU
*my device shuts down "sometimes" when i:
-make or answer phone call
-video recording for a time "more then 10 minutes"
-some times just itself
also my device does not want to move apps to USB storage, and is being hot when i use it for a long time "like playing games"
ThAnk you guys, always you are the best in all
Click to expand...
Click to collapse
Only certain apps can be moved to SD. Most apps cannot be. It's up to the developer.
All computers get hot when you run heavy programs on them.
No idea about the shut down problem unfortunately. Typically a factory reset should fix the problem, but that's rather drastic. When did this problem start? Did you install something before it all began?
yahyoh said:
trust me bro the ICS that not from sammy it's more stable than sammy rom
give it a try u will really like it and will fined it smoother than sammy rom and faster and now there is more support from dev to ICS
try AOKP with devil kernel very stable and u will never look back to sammy GB
Click to expand...
Click to collapse
thank you bro
-but i am on JVU 2.3.6 how to get good base befor get in ICS?
-or how to get away from this shet of XXJVU and get in stable ICS?
thank you again
snapper.fishes said:
Only certain apps can be moved to SD. Most apps cannot be. It's up to the developer.
All computers get hot when you run heavy programs on them.
No idea about the shut down problem unfortunately. Typically a factory reset should fix the problem, but that's rather drastic. When did this problem start? Did you install something before it all began?
Click to expand...
Click to collapse
thank you man
i have used 2.3.3 BUJVB for 2 or 3 days and i didn't see any problem, i guess it showed up after i get on JVU 2.3.6. do you think it's going to be a material kinde problems
Hi Guys
I have this problem when i instal different kernel than basic. I can't watch my recorded videos in gallery, but they stops in first second and gallery stops working too.
I still do cache partition, dalwik cache, and than i'm installing kernel
With CM9 and other roms i haven't this problem, but I want this rom without this bug
Thanks, and sorry for my poor english
Edit: I tryed fix, but didn't help
the break of 720 video is always described in the kernel ... read the description of the kernel carefully
I know that's described in versions with bigger mem., but i didn't know that can happen in normal version.. when i asked in other forum, people had no problems with combo Slim ICS+ Semaphore 1.2.2
Yes this is a kernel "feature". The 720p breaking comes free with all bigmem kernels (i think).
I however am running slim 3.9 with devil2 kernel (Devil2_0.94_i9000_CFS_BLN_CMC_20120524)
720p is no problem....
That's i told about. Nobody has problem like me... I don't underestand
the problem is in the kernel....change the kernel and take one that support 720 recording....
i tryed semaphore, devil, mnics, and it didn't work..I don't know which one could work good
And record works good, but i can't play recorded video
you can download the mod that is fixing the 720P break...
http://forum.xda-developers.com/showthread.php?t=1575485
I dont know if it helps, but on my phone with Devil2_0.94 with default settings, playback was broken too. The video opened but after a second or so whatever video app I used, it would just stop.
As I like this kernel very much I didn't want to change.
In this version, Devil2 kernel comes default with standard RAM (378MB) and somehow this was breaking playback.
As usual I went to xl mem setting (391 MB), now everything is fine!
If you're using Devil2 kernel, read the second post of that thread and you will see how to change that setting.
You can download "Scripter" from market and paste the commands into the app to make things easy.
Read the kernel instructions....you need to instal the "s" version!
+ 1
slaphead20 said:
Read the kernel instructions....you need to instal the "s" version!
Click to expand...
Click to collapse
Thank You so much!
I was finding reason everywhere, but i'm blind apparently
Hello, I got a serious problem with my Galaxy S..
something must be wrong here, when I'm on ICS, photos are displayed like they had a very poor quality or something like that..
I'm running SlimICS and tried devil kernel with and without Voodoo color, this didn't change anything.. even when I changed the VC values..
When I start my phone, at the point of boot up when the devil kernel boot screen appears, it first appears usual and within a second changes to some strange view, like you can see on the photos...
http://db.tt/qIhJejyu
these are pictures of the devil kernel boot screen, the other photos are pictures viewed on the phone. I hope you can help me
when using other kernels/roms(ics) the same thing appears so it's not kernel related
am I maybe posting in the wrong section?
can nobody help me?
Looks like a VC issue, have you tried some stock/custom GB roms?
Ajoslaf said:
Looks like a VC issue, have you tried some stock/custom GB roms?
Click to expand...
Click to collapse
GB is fine, but I want to have ICS goodness
ICS rom without VC has the same problem... I also tried Devil without VC...
But on GB rom it is OK? ... maybe you should try clean install of Slim ICS, that means - flash stock 2.3.6 jw5 (link to gb flash kit is in ics333 thread in development section), root it, flash newest cm9 nightly, and then slim ics and kernel, first try semaphore, then devil3 ...
yes, it's perfectly fine in GB..
already did this 100 times
Maybe you are doing something wrong if not, it may be a hw problem, but I don't think so...
don't know whats wrong with the device, ...#
EDIT: Okay, I guess I got it, as this device is pretty new, I got it replaced due to a warranty case, I think it has a newer display or something, which isn't supported by the drivers used in all AOSP based roms (CM7 also doesn't work)... pretty bad
Interesting... don't you have a Galaxy SL? It is SGS but with normal TFT screen, not with SuperAMOLED...
No, I don't have this ****..
Real SAMOLED I9000
darkcheater said:
No, I don't have this ****..
Real SAMOLED I9000
Click to expand...
Click to collapse
I'm facing the same problem. With GB kernel it looks fine, but with any ICS or JB kernel colors go really wrong
It's the first time I see it.
Any idea?
Seems to be a driver issue
I am having this issue too.
There is a video in youtube titled "CM9 on Samsung i9000 framebuffer bug ('blue color bug')" showing the same issue.
In the comments they say it's a problem with framebuffer (fb) driver.
I have been taking a look to Samsung's kernel fb for tl2796 lcd panel (which I suspect it's ours) and there is a feature called ACL which is missing in CyanogenMod's fb driver. This feature seems to perform some colour corrections.
I am willing to solve this issue but I have no knowledge about kernel drivers nor graphics drivers. I have been reading about it in different manuals and articles but I'm still lost.
I would thank any developer to point me to the right documents to learn how to solve this issue.
Maybe pawtip or stratosk could help.
Hey guys
So i am currently on the official ICS 4.0.4 V30A ROM by Civato 's awesome Flex Icer..
Got a bit bored of the LG things and all and wanted to try out CM10 (since 10.1 isn't stable). All i need is STABILITY.
As in no bootloops and Radios working perfectly etc (just the way this ROM works)
I haven't seen a clear cut answer till now regarding the stability of CM10 on SU660 KOREAN 2X.
If any of u have tried it out please let me know ur experiences and the stability too
Also tell me regarding Paranoid Android
One more thing
Will i be able to revert back to the ROM by mere flashing of ROM and the Kernel used with it?
Thanks
Sent from my LG-SU660
I don't know on su660, but I'm supposing it's at the same state as its brother p990, which I have.
If you're looking for stability, stick on stock ics. Cm10 is not totally unstable, but far from being totally stable. Hdmi doesn't work, and for Bluetooth you will have to flash pengus kernel. And that kernel is great, but bugged since it uses ramhack, so apps with hard gpu use crash, e.g. HDR camera every time you try to use it at 8mpx. And it makes the device reboot! I also had this behaviour using flipboard, dlna server or playing flash video on browser.
I make all these things systematically on dm1.4 with civz 2.3 kernel, and my device stays without a single boot for more than a week easily. This is stability.
Do not say "thanks"; just press it under here.
louiscypherbr said:
I don't know on su660, but I'm supposing it's at the same state as its brother p990, which I have.
If you're looking for stability, stick on stock ics. Cm10 is not totally unstable, but far from being totally stable. Hdmi doesn't work, and for Bluetooth you will have to flash pengus kernel. And that kernel is great, but bugged since it uses ramhack, so apps with hard gpu use crash, e.g. HDR camera every time you try to use it at 8mpx. And it makes the device reboot! I also had this behaviour using flipboard, dlna server or playing flash video on browser.
I make all these things systematically on dm1.4 with civz 2.3 kernel, and my device stays without a single boot for more than a week easily. This is stability.
Do not say "thanks"; just press it under here.
Click to expand...
Click to collapse
Thanks alot bro... Will DM ROM work on the SU660 by using Civz 2.3 kernel for the SU660?
Sent from my LG-SU660.
WasifSal said:
Thanks alot bro... Will DM ROM work on the SU660 by using Civz 2.3 kernel for the SU660?
Sent from my LG-SU660.
Click to expand...
Click to collapse
You're welcome. I think it'll work, just do not forget to flash the su660 kernel before rebooting or you'll get bootloop
Do not say "thanks"; just press it under here.
but WIFI when o2x is in idle mode, in setings is "work wifi when phon is idle" is not working wifi! why?