Develop Bugs

[Q] NFC while screen is off?

So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.

From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.

eddie_gordo said:
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.
Click to expand...
Click to collapse
Ah, ofcourse now i see why but yeah it should be editable, though NFC is not that widely used yet i'd like to turn that security feature of until i connect a creditcard to my phone.

Pliind said:
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.
Click to expand...
Click to collapse
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.

krohnjw said:
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
Click to expand...
Click to collapse
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.

Pliind said:
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.
Click to expand...
Click to collapse
To be fair they do make it seem like that's how it would work. Who would turn their phone on, unlock it and then turn it upside down BEFORE they get out of their car just to scan an NFC tag once they got out.
I don't see that being a reality though as the rest of the demos clearly show the device on and what appears to be unlocked. Given this is how the NFC service works within ICS, I'd suspect this will be the behavior as well.

[Q] Bluetooth audio and pernament display light

Hi, i have following question: anytime i connect device over Bluetooth and start to play music, it never power off screen or locks. I would like device to do it, as it consumes battery if i forget to manually switch display off. is there some way to make this happen automatically. I have tested various ICS ROMs but this is same at each one. any hints appreciated.
thanks

x.para said:
Hi, i have following question: anytime i connect device over Bluetooth and start to play music, it never power off screen or locks. I would like device to do it, as it consumes battery if i forget to manually switch display off. is there some way to make this happen automatically. I have tested various ICS ROMs but this is same at each one. any hints appreciated.
thanks
Click to expand...
Click to collapse
Can you be more specific? What kind of BT device, which music player?

kbeezie said:
Can you be more specific? What kind of BT device, which music player?
Click to expand...
Click to collapse
i tested on Nokia BH-214 and it works ok and screen goes to lock and blank, but tested on BMW 92870 internal car kit, it remains light . so it is probably car kit and ICS compatimility issue.

x.para said:
i tested on Nokia BH-214 and it works ok and screen goes to lock and blank, but tested on BMW 92870 internal car kit, it remains light . so it is probably car kit and ICS compatimility issue.
Click to expand...
Click to collapse
It's possible, though not something I particularly heard of unless it was designed that way (i.e.: as phones in a car are sometimes plugged into the charger).
What ICS rom is it? I know some applications as well have permission to keep the screen awake, though not sure if that would be it either since you said you tried it with another BT device (assuming same app).

kbeezie said:
It's possible, though not something I particularly heard of unless it was designed that way (i.e.: as phones in a car are sometimes plugged into the charger).
What ICS rom is it? I know some applications as well have permission to keep the screen awake, though not sure if that would be it either since you said you tried it with another BT device (assuming same app).
Click to expand...
Click to collapse
I tried Andromadus, CM beta 12,13 and now i use EliteMod, looks like car kit forces light to remain and it is also when running without charger only on battery.

Which board on the nexus 7 contains the gyroscope?

So, I recently installed Lineage OS on my n7 and noticed auto rotate wasn't working. Then flashed it back to stock thinking the lineage rom was bugged, still no auto rotate, it used to work last time I used the tablet around 3-4 months ago, so im wondering did the gyroscope get fried or something?
Anyway which board contains the gyroscope, the motherboard or daughterboard, anyone know? Recently replaced the daughterboard so im thinking that may control the gyroscope? I want to replace whichever board contains the gyroscope as it doesn't even show it moving in check my android app, don't really want to waste money on the wrong board if possible, so if anyone knows for certain it'd be a huge help!

chrisg4493 said:
So, I recently installed Lineage OS on my n7 and noticed auto rotate wasn't working. Then flashed it back to stock thinking the lineage rom was bugged, still no auto rotate, it used to work last time I used the tablet around 3-4 months ago, so im wondering did the gyroscope get fried or something?
Anyway which board contains the gyroscope, the motherboard or daughterboard, anyone know? Recently replaced the daughterboard so im thinking that may control the gyroscope? I want to replace whichever board contains the gyroscope as it doesn't even show it moving in check my android app, don't really want to waste money on the wrong board if possible, so if anyone knows for certain it'd be a huge help!
Click to expand...
Click to collapse
The gyro is on the daughterboard but it never fails. Connection of the wide silver cable between the boards is the problem - see my earlier post https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3

k23m said:
The gyro is on the daughterboard but it never fails. Connection of the wide silver cable between the boards is the problem - see my earlier post https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3
Click to expand...
Click to collapse
But then wouldn't the gyroscope show as moving in apps that can test it? It shows up as stuck, and on the twitch app it acts as if i am shaking the tablet cause it just keeps going from dark mode to light mode because twitch app has a feature that allows you to shake to enable dark mode/light mode.
Anyway I have tried re-seating the ribbon cable about 20 times now and still nothing shows up on gyroscope, even tried 2 different cables

chrisg4493 said:
Anyway I have tried re-seating the ribbon cable about 20 times now and still nothing shows up on gyroscope, even tried 2 different cables
Click to expand...
Click to collapse
The gyro and compass sensors share the same I2C data line connecting the two N7 PCBs. Please check with a sensor test app if the compass works - if yes, then the gyro has failed indeed.
Some apps will show you the sensors names - N7 has:
gyro Invensense MPU-6500
compass AKM AK8963
:good:

k23m said:
The gyro and compass sensors share the same I2C data line connecting the two N7 PCBs. Please check with a sensor test app if the compass works - if yes, then the gyro has failed indeed.
Some apps will show you the sensors names - N7 has:
gyro Invensense MPU-6500
compass AKM AK8963
:good:
Click to expand...
Click to collapse
Hmm, the compass seems frozen as well I don't understand though the ribbon cable seems to be fine no matter how many times I disconnect / reconnect it nothing seems to change... Very odd

I have same issue, I use rotate app to manually rotate and also automatically rotate some apps. Eg auto rotate YouTube and media player to landscape.
https://play.google.com/store/apps/details?id=jp.snowlife01.android.rotationcontrolpro

With the silver ribbon cable connected at one end try and get it tightly moulded around the battery hold it there and connect the other end. I found this out recently after a battery swap it helps to push the connecters in a bit more those few microns matter. I was having screen rotation problems after a recent battery swap after doing this everything's perfect again.

Display wakeup issues after screen replacement

Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.

i too have this problem cant find any solution anywhere been trying for about a week now arrggghh

ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!

gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.

My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.

Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.

csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?

Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up

skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?

Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.

Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?

gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.

Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals

Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...

Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz

Mail me i have that file..
[email protected]
There is issue while sending here

Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude

Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??

Ambient Display Screen Flashes

Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.

Sounds like a hardware failure, display or mobo.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.

haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.

blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse

blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then

haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention