hi there guys, before you ask, i've already searched the forums for solutions to my problem without any success, or even finding an answer did not apply to my device or it would not work.
I flashed CM9.1 stable since it was released, BLN worked great, I even got the chance to test between D3vil and semaphore kernels (kept D3vil), and didnt have any issues. Then one day I realized that my notifications did not generate blinking even when the blinking was on on BLN Pro and in the kernels config apps
I tried fiddling with the BLN Pro app, and kernel config app (both, devil script manager and NSTools) and did not solve the issue, then unninstaled BLN and tried again, nothing. reinstaled BLN, nothing. Re-flashed kernel in the same version, nothing. unninstaled BLN again and reflashed kernel, nothing. Changed kernel to semaphore, nothing. upgraded D3vil kernel from 1.3.x to 1.4.1, also tried the two versions of the d3vil kernel the one with CMC and the one with VC nothing.
I tried to mmake it work in any way i knew possible, BUT, when testing in the BLN app in the option to test the blinking, it did not work, also used a friends phone to send me messages, no dice.
At this point I dont know what else to do, if someone is having or had the same issue and found a solution please let me know, i really use the BLN function because i leave my phone away from me all the time (and often with dirty hands) and its easier just to look at it that getting the phone after cleaning my hands and having to wake it to see if there are any new notifications, that its why is so important to me.
If you need any other details in order to help me dont mind asking.
Thanks. downhiller900sl
Phone: GT-i9000
ROM: CM9.1
Kernel: D3vil 1.4.1
Related
When I am in the call sometimes i cant hear other side,my front speaker doesnt work I can only hear it when turn on speakerphone,If I reboot device my problem is gonne but only for a while... After some time same problem is back. Does anyone have some suggestion? I am at serendipity ROM with voodoo kernel...
i would say the rom and kernel is down to this problem.
check you are running the latest version of both, and if you are ask in the thread to see if anyone else has this issue.
a reset may work, but chances are the problem will come back.
a lot of sound related issues come from the kernel. so its always worth checking for updates
Thanks for suggestion,i will try to update or change kernel. I was on Darky's rom with voodoo kernel before and I had same problem so maybe you are right...
Hey,
I have this problem with Wifi not going to sleep (yes it's set in options to sleep while screen goes off).
I had it on stock JVP (darkcore) and now i got this on Criskelo v70 (darkcore also).
please help me cause it's really annoying
cheers
Try to ask help from Darkcore's kernel thread so that same kernel users could help you with your problem.
Wait, you cannot post yet on the development forum, right? Maybe you could PM some of the darkcore kernel users...
Well i dont really think it's kernel related since no one else seem to have this problem on dark core.
I tried changing a kernel and just as i thought it didnt help, then i wiped the device and still the same thing...
i have no idea what could'v cause it and it seems im the only one with this problem
i think i can try going back to older GB release and than flash jvp again, but i will wait some time for an answer first
edit: i forgot about one important thing: when the phone is connected to the charger Wifi goes to sleep normaly, weird..
edit2: FIXED!
this was my case:
http://forum.xda-developers.com/showthread.php?t=774507
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.
Hi,
i have a i9001 and use broodrom (4.1.2 version). I've tried some different roms, but there is always the problem with the "email" program provided by google: When i start the program it sometimes works and sometimes it crashes telling me, that the app was shut down. It always crashes when I try to answer an email. I've tried different email accounts with no effect. I tried different email apps and all have the same problem. Does anyone figure out, how to fix this? (i like broodrom and this is the only real issue)
There are mutliple threads about problems like this but i didn't find one that describes or solves a related problem. I tried out some things, cleared the cache, reinstalled the rom, i checked the gapps version to be the right one and honestly: I'm clueless...
gan
I tried some more things and finally i decided to try out invendors CM10 version. This one works.
Thank you to all the guys out there, that make such roms. Great work!
Hi all,
Previously I remember disabling Capacitative button led in Kernel Aduitor, (I forgot which build, I was using one of SHADE's unofficial CM13 build).
Now after updating, however it seems like the option is no longer in Kernal Aduitor. The Button option under settings does not work and my LED remains off no matter how I set the brightness/timeout for Buttons LED.
Can anyone tell me how to ge tmy button led to work again? (I also tried flashing to stock miui8 but it did not work either). Perhaps can someone also point out a build that is available to download that might still have this setting in Kernel Aduitor so I can try to re-enable it. Thank you.
I think if you wipe everything and flash the latest MIUI rom through fastboot, it should resolve any problems you are facing because of earlier change in kernel settings.
ishangoyal said:
I think if you wipe everything and flash the latest MIUI rom through fastboot, it should resolve any problems you are facing because of earlier change in kernel settings.
Click to expand...
Click to collapse
Hi ishangoyal, I've tried everything, doesn't work
Does anyone have any idea on which rom/kernel that enables Kernel Aduitor to edit capicitative led settings? I just can't seem to find it anymore and am wondering is my capacitative leds are really dead.
@Harrynowl Hi Harry I notice you are programming a new kernel, can I request to add capacitative leds settings so that kernel aduiter can adjust it? Thanks for you help.