I flashed Android Andis OmniRom 4.4.4 over the existing 4.4.2 -
After that, original smart cover did not work. The display doesn't turn off.
Sensor Problem? After flashing single Blackhawk NEXT Kernel 1.7, it is now working again.
Related
Hello. I have a problem whit my galaxy nexus maguro device. When i install something different then stock google images 4.1.2 or stable "cm-10.0.0-maguro.zip" i have a problem whit screen when i'm during my phone call. Every time i install something different for exp: stock 4.2.1 or 4.2.2 or every custom rom (xylon,pa,xenon,slim bean etc. etc. ) and when i starting a conversation my screen of course is off but when i geting off my phone from ear screeen whant to turn on and it is almost every single time i having a phone call.I was trying every basband,rom, kernel and always i the same result -screen issue. Of corse when i'm on 4.1.2 or cm-10.0.0-maguro.zip there is no problem. so my question is WTF ? Please try to forgive me for my english - this is not my thing
?
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
?
ryza666 said:
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
Click to expand...
Click to collapse
And i've changed animation window to 0.5 and it's not working. PLS help MEEEEEEEEE !
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
irizwan said:
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
Click to expand...
Click to collapse
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
ryza666 said:
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
Click to expand...
Click to collapse
And sorry for your "quick" response:angel:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
bk201doesntexist said:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
Click to expand...
Click to collapse
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
ryza666 said:
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
Click to expand...
Click to collapse
Is your screen protector covering the proximity sensors? My screen protecter once covered them and I had the same issues but when i removed it, it worked again
If you are using a custom kernel, try up-ing you min screen off setting in trickster mod.
I used to get a lot of these problems. But not any more since I am on Diamond series of AK kernel.
I am using these settings: http://forum.xda-developers.com/showpost.php?p=38030897
I have recently flashed CM 11 ROM on my LG E975 . It's working okay but It has one big bug i.e. whenever my phone sleeps when an app is already running(say Bluetooth,camera,dialer,instagram etc) ,at times it happens when it is idle;on pressing power button it won't show the lockscreen or display and I have to reboot it .It is annoying and drains my battery help me
PS i have also installed CM11 update as well, No good!
faizigenious said:
I have recently flashed CM 11 ROM on my LG E975 . It's working okay but It has one big bug i.e. whenever my phone sleeps when an app is already running(say Bluetooth,camera,dialer,instagram etc) ,at times it happens when it is idle;on pressing power button it won't show the lockscreen or display and I have to reboot it .It is annoying and drains my battery help me
PS i have also installed CM11 update as well, No good!
Click to expand...
Click to collapse
hi,
I had too many problems with CM11, including quite a few demigods crash and the infamous deep sleep problem (yours apparently), maybe because on the LGOG, the QC modem chipset is buggy and you need to disable C1 & C2 sleep states (maybe C2 & C3) .
to do that, you could install FAUXCPU.
Another option (much better I believe) is to install VANIR or another AOSP based ROM. Personally, since then, no system crash, everything is rock solid.
D
danette57 said:
hi,
I had too many problems with CM11, including quite a few demigods crash and the infamous deep sleep problem (yours apparently), maybe because on the LGOG, the QC modem chipset is buggy and you need to disable C1 & C2 sleep states (maybe C2 & C3) .
to do that, you could install FAUXCPU.
Another option (much better I believe) is to install VANIR or another AOSP based ROM. Personally, since then, no system crash, everything is rock solid.
D
Click to expand...
Click to collapse
Thanks but I am actually new at rooting & flashing ROM(it's my first time). Kindly guide me about better and stable kitkat ROMs if you can.
And elaborate if you can about solving this problem without flasing another ROM
im planning to root the the phone....dont wanna go to 7....wanna see the rom and rooting first with android 6
what is the best option for this phone on 6 ?
To be honest, there is no "good" Marshmallow ROM for this phone.
The stock ROM is a nightmare, regardless of whether you use the Marshmallow or Nougat one.
The "best" ROM in my eyes is the newly released Oreo AEX alpha build posted by Firelord, the only downside it has is that fixing the LED lights on it is a bit of an hassle and that NFC isn't working (yet).
If NFC is important to you, you should go with Firelord's Unofficial LineageOS 14.1 build, that one has working NFC and the LEDs can be fixed the same way as the Oreo build.
The main reason I suggest you to go custom ROM here is because the stock ROM itself has a series of critical bugs that I consider even more severe than the two I just mentioned.
If you are into mobile gaming with a gamepad for example, forget about doing it on the stock ROM, as Lenovo has done something to the framework that makes every kind of HID interface freeze randomly.
MrColdbird said:
To be honest, there is no "good" Marshmallow ROM for this phone.
The stock ROM is a nightmare, regardless of whether you use the Marshmallow or Nougat one.
The "best" ROM in my eyes is the newly released Oreo AEX alpha build posted by Firelord, the only downside it has is that fixing the LED lights on it is a bit of an hassle and that NFC isn't working (yet).
If NFC is important to you, you should go with Firelord's Unofficial LineageOS 14.1 build, that one has working NFC and the LEDs can be fixed the same way as the Oreo build.
The main reason I suggest you to go custom ROM here is because the stock ROM itself has a series of critical bugs that I consider even more severe than the two I just mentioned.
If you are into mobile gaming with a gamepad for example, forget about doing it on the stock ROM, as Lenovo has done something to the framework that makes every kind of HID interface freeze randomly.
Click to expand...
Click to collapse
thanks for your info....i dont care about NFC or even LED also.....all i want it is a great rom with no battery drain or bugs..working normally and good cpu+ram management... >>> to start fixing the audio problem
Any Suggestion ?
You dont want Marshmallow because of nonce krack buig. Amazes me how open source can break in newer versions.
My paranoia says Gov agencies wanted this bug in the newer Android software.
I am facing this wired issue where my fingerprint scanner is not working even though my phone is encrypted. I have tried multiple roms since this issue had started but it hasn't helped me yet. Hope someone helps?. thanks for reading
I have the same issue I just switched ROMs as usual but this time my fingerprint scanner didn't work I'm on latest resurrection remix 8.1 rom
I have the same issue too. I reinstalled the latest stock Lenovo Rom and the fingerprint sensor started to work again. Unfortunately It stopped working while I was recording my fingerprint for the device locking. With a reboot the sensor restarted to work but now always stop responding after a couple of minutes. Rebooting the phone is the only (temporary) solution. It's not a software problem but (in my case) an hardware problem!
I have to live without fingerprint sensor.
Now i have this issue which my fingerprint seems that it only work on stock rom only and don't work on any other custom rom and that is not norma i used to work on RR 8.1 for two month without any issue it happened when i went for miui pro port rom and was working fine in it and broken when i got back to RR 8.1 again and worked again when i flashed stock rom deodexed so it's only work perfect on stock rom only can any one help me with that ?
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
kerberos666 said:
Is there please someone who can help me?
I have an unlocked willow device.
But when I install any custom rom (AOSP like - Android 12 or 13) the display will not light on first power button press after going to deep sleep or display lock. It will take several button pressing, until the display will come alive/wake up.
Sometimes it seems, that the display is unlocked, but is at lowest brightness level. The hardware is okay. I changed the power button pcb already.
The latest MIUI firmware rom (from xiaomifirmwareupdater.com) runs without bug. Its a A11 image.
Is this a bug maybe in the vendor file? Is there any other solution than staying on stock rom MIUI A11?
Thx for your feedback in advance!
Click to expand...
Click to collapse
if it's not a hardware issue it's the firmware or you did a dirty flash ?
No dirty flash. Always clean install. I think that there could be a major bug in all custom images for Willow devices. I tested several custom rom. None worked correctly.
Is there noone else with a Willow and the same problem?
And is it the vendor Image part i should flash over custom rom's vendor part? Then the custom Image does not boot anymore...
Any help is appreciated. Thx!
This evening I mixed up dtbo, modem, efs partitions from MIUI official A11 rom with a current A13 custom rom. Now the display works as expected.
Maybe I messed something up myself some months ago. Now i have a backup of a working system. That is good!
Gonna try flashing some custom A13 rom(s) again and test If it will break the "display wake up" again.