Related
Dear community,
I noticed that LED notifications don t work very well .. it starts blinking but after a while it ends up dark, like after 4 or 5 times.
I tried differend CM7 nightlys and redy's Custom CM, still no success.
I should add, that i also vibed my device.
What could i do?
I tried agent205's method by using the "LG 2X/Black/3D Notifications" and fixing the permissions, but this app say everytime i start "this app doesn t have some needed permissions".
I love the LED notifications...ahh
Any suggestions would be very appreciated.
Thx!
No ideas. :/ ?
when you boot your phone, they'll back to the default permission, no write permission
i don't know how to keep it yet
It s a weird thing. I Mean why doesn t work it? I had no problems with another optimus black...
"LG 2X/Black/3D Notifications" seems don't work on ROM 3.2.4 V20N, can anyone make it work coz i love this app so much. Thanks.
I think you need root in order to set some properties on some files in order for BLN to work.
my phone is rooted and i try agent205's method but i try the test feedback it doesn't blink.
Like agent205 said, restarting the phone results in default file properties.
But in cm7 LED notifications are integrated. Regardless, it stops blinking after 4 or 5 times, no matter which cm7 version I tried.
What could be the problem? Is it the hardware? I Don t get it :/
The problem occurs only on latest cm nightlies for me and only on some boots. So probably some of the new commits cause it.
OT did you guys notice that the leds flash blue when charging on a switched off phone? Or is it just me? It would be cool to have different colour notifications, or is it already possible and I just don't know of it?
You can change app specific different LED behaviours in the CM7 settings.
As far as i know the dimmed blue notification (without pulse behaviours) works on OB, or better worked on my OB since this ****ed up.
But i hope your're right and it will work in another release.
I doubt this is a official known bug though. Am i right?
EDIT. Problem gone on. Nightly 63. Thx all.
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
I'm using a Z3 compact with CM12.1, that means unlocked bootloader and no more warranty. All of sudden, the main/back camera has stopped working. It is black, OSD still working, front camera still working, other camera apps don't make a difference.
I don't know if that is a problem of some recent CM nightly or something else. Browsing the web I get the idea that this symptom also appears on stock firmware, and it seems that nobody has yet found a solution (neither factory reset nor hardware replacement of camera help).
My question:
Has somebody else this problem, is it CM related?
Is there a solution other than complete phone replacement?
Is there some logfile I might consult to find out if the camera HW should be replaced? I don't want to disassemble the phone only to find out that the camera still does not work.
Thanks!
Must be a software problem related to the nightlies unstableness.
Try flashing a stock firmware to see if it gets fixed.
I'd rather avoid going back to stock. Reverting to a previous CM nightly (from a time when the camera definitely worked) did not help.
Do you have any reports of CM nightlies problems with the camera? I'd love to hear that, because it would mean that I don't have hardware problems. However, searching the web I only found many reports of the camera suddenly stopping to work, but nothing that this is related with recent CM nightlies.
But if it's a Hardware problem, there should be a logfile somewhere, or?
just did trial and error on the same problem with the black camera for 2h
i did however not install CM to cause this
I have a custom debloated rom, which worked fine.
I had to switch phones so i did a TW recovery backup.
Changed the filename on the new phone so it is found when restoring.
Restored. Everything works well, except the camera app.
When i wipe from the systems menu i lose all my data but the camera app works again.
But of course i need my data exactly the way i had it backed up.
Tried all kinds of things around the camera app, backing and restoring with and without kernel, always the same.
Back camera stays black.
This is similar to other reports I found in the web: The hardware works (which means replacing the sensor is of no use), but somehow it is no longer accessible. I tried different hw info apps, which all report the back camera with all specs and no problems, but no camera app is able to get it to work. I flashed several new CM nigthlies since, it doesn't help
I don't really know how to read logs (with 3CToolbox), however this line caught my attention. Maybe somebody here can interpret it:
07:45:48.427 caladbolg( 301)
9530027 cald_parammgr_generic.c (4299) 301 E [PRM] Fail: camera eeprom status
Since my Kernel debugging skills are also not existent i simply factory reset it and transferred my data with titanium backup.
Everything works fine now.
So my advise is to stop wasting your time with it too, just go back to working software
Unfortunately reverting to stock firmware did not repair my camera. Afraid I have some hardware defect
No resolution to this problem it seems
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
dont think its a software problem, maybe you should get your phone checked out
njuz said:
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
Click to expand...
Click to collapse
Its of course a well know bug for all mi5 roms. I read yesterday that last thursday rom update fix this:
"Fix - Accelerometer and gyroscope didn't work after and OTA update (08-12)
Fix - Accelerometer and gyroscope didn't work normally (08-12)"
The problem occured with miui as well as with unofficial CM build, what i am using now. This indicates to me that it has nothing to do with the installed rom directly.
After rebooting, everything works fine again.
I suspect apps like Pokémon go to stay in relation to the bug. Since i am not playing that game anymore it occures much rarer...
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
I was having the same problem. I dont play pokemon. Im still on vendor rom. But now the bug gone i tried to simulate the bug but it rotate normally
I have this issue. I'm on the latest CM 13 build and I get issues where the camera won't take in landscape and full screen videos won't switch to landscape when you rotate the phone. It's so nearly perfect apart from that.
shucrut said:
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
Click to expand...
Click to collapse
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
I installed a couple of Sensor Test apps and neither one can see my accelerometer sensor to even test it. So it's like the sensor isn't even there. I know it works because one of Shade.sh's beta CM 13 builds was able to detect the sensor OK! Any ideas?
Here's the sensors detected in the Check My Android app. There seems to be only two axis detectors working. How does this compare to a healthy Mi 5?
sharkyblunt said:
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
Click to expand...
Click to collapse
Yes, i actualy did. After installing developer version 6.9.18 the problem never appeared again. Now im on 6.9.22 and the rotation bug is gone
Hmm, I've just tried SlimRom and the same bug is present, presumably because it's derived from the same tree as CM 13.
I'm actually tempted to give MIUI 6.9.22 a go then if it's the only way to get this fixed.
I have just flashed the MIUI developer ROM 6.9.2.2 and my sensors are working perfectly now. So it must be something for flaky in the CM stack or Kernel version. See screenshot.