[DISCUSSION] Fixing the OB's softkeys - LG Optimus Black

Hi,
I just wanted to create a centralized thread for all the discussion surrounding the work of fixing the softkeys.
Many users are reporting, including myself, about the softkeys not working properly after some time on the ICS roms.
My 25 cents:
Is it a kernel issue? ROM issue? I have tried multiple ROMs but none have fixed the issue.
Multiple kernels tried too, to no avail. I suspect it is a software issue though. It's as if the buttons go into some state of sleep mode in the software, and after a few minutes come back for a few milliseconds. Just my thoughts into it.
-
Sergio

After facing the issue, i smartflashed gingerbread, there also softkeys not worked.

It is a kernel issue for sure. Worked great on GB, but I think they messed up the driver in ICS. Have you tried my blue kernel already? Dont know if I fixed it there, but it is worth a try. Or compile your own kernel, but use the GB Softkey files. Should work just fine with some mods here and there
Sent from my XT1052 using XDA Free mobile app

Has anyone successfully fixed this issue?
I am facing the same problem after flashing ICS on my OB.

i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.

Maybe
hackerse7en said:
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Click to expand...
Click to collapse
I don't know about that though, mine works excellent through the CM key test. Just fails in the OS. And I can't use the kernel by Nooby, I'm on Nameless KK. But before that I tried IZS, GB, 2.1, etc to no avail.

I'm gonna research this and try and fix it in the Aeroi Kernel

Related

[ROM][BUG]ROM to determine the origin of SoDs bug present on Zeus ROM...

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

Galaxy note boot up is driving me nuts!!

So I was on iMilkas rom for a bit. I decided that I really needed Skype and netflix to work so I went back to stock for a bit while I decided what to do. Everything went back fine. However whenever I reboot my phone it plays a tune over and over for about let's say, 6 MINUTES!!! It loops over and over and over. I go into my sounds and my default ringer is set properly and my notification sound is set. (neither is this annoying tune btw). Any ideas why this phone keeps doing it. Also I swear it gets a little longer with every reboot.
version: 2.3.6
baseband: DDLB1
kernel: DDLB2
oh and the song it repeats over and over is the one of the defaults: "Over the Horizon"
Does sound like a funny bug. I swear I heard something similar a month or so ago and a reflash of the rom solved it. Someone may be able to determine the exact problem for you though
Sent from my GT-N7000 using XDA
notegalaxy said:
Does sound like a funny bug. I swear I heard something similar a month or so ago and a reflash of the rom solved it. Someone may be able to determine the exact problem for you though
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Symptoms of improper flashing mate.Try factory reset if it doesnt work try to reflash the rom again
hard reset it or flash it again
Man I was hoping that wouldn't be the best solution although in the back of my head I think it is. Considering this, I might just downgrade again and re-enable root so I can restore with TB. Since this is where I'm heading I guess i'll spend the rest of my time in the developer forum finding the most suitable rom to jump on board with. Any suggestions from people on GB roms? ( I can't go to ics as I need Skype to work for "work".
Best rom to go with is rocketrom v22 its a gb rom and you can get the ics look with a matching theme put franco kernel 9 and you are ready to roll into awesomeness!!
rocket rom comes in miui theme by default but in the opening post of the rom u will find a perfect ics theme to go with!!
the best combo is rocket rom plus ics theme plus franco kernel
SHOT from my LOADED GT-N7000!!
I've seen similar problems mentioned with early versons of SuperSU.
have you updated to this recently?
some were able to resolve the issue by disabling the notification toasts, and/or granting SU access as default.
I installed MIDNOTE 2.0 yesterday and I must say that it is a flawless ICS rom. I dont have any problems at all!!!

Screen displaying wrong things

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.

CM10/JB Memory leak problem (solved?)

I really find it too difficult to follow the recent cm10/jb/aokp based 4.1.1 roms as there is a new one or two everyday. Is the well known memory leak cured by now? Can anybody with knowledge comment on that? Because its the only reason to keep me away from cm10 jb based roms from my note
Thanks!
nope, and im saying this after testing 3 different roms (all not older than a week)
but without the leak its fast n smooth
to be honest the memory leak problem seems to have gotten worse.
Mid day I'll have to reboot to start smooth again or else my programs will crap out and freeze or not respond.
i've been on the latest nightly and flashed maybe 10 times already.
4 CM10/AOKP JB roms tested and problem still here.
Are there any new information on this issue? I also noticed the memory leak problem and as this question was asked over a month ago now I'd like to know if it still persists.
Thanks in advance,
experience7
experience7 said:
Are there any new information on this issue? I also noticed the memory leak problem and as this question was asked over a month ago now I'd like to know if it still persists.
Thanks in advance,
experience7
Click to expand...
Click to collapse
Yes it is solved thanks to new drivers. All cm10 based roms have them now.
check this rom
http://forum.xda-developers.com/showthread.php?t=1936311
Hah, thank you guys very much
- experience7

[Q] [ROM][4.2.2] RemICS-JB[v5][30/05/13] - Random reboot

Hi, I have installed the Remi-ics v5 for the first time on my i9000 and now i noticed a random reboot of the phone for a couple of times in the past week. Anybody have any clue what could fix the issue, is it kernel related maybe? I've came from stock sammy rom(jw9) and am using just a few apps apart from remi's like facebook...? Anybody? Thank you
Well its probably a kernal issue. It might be the rom clearing ram. Im hoping this helped

Categories

Resources