Sensor Problem doesn't let me wake my OPO - ONE Q&A, Help & Troubleshooting

Hello everyone,
Whenever I try to unlock my One Plus one , it locks again by itself. Most probably because of a broken sensor ( as told in a shop) the screen turns on for a fraction of a second then locks. I can't even use touch in that second. I have tried wiping everything and installing every custom rom and it's not a problem of DT2W or kernel ( I tried in miuiv5 rom which doesn't unlock on DT2W. )
Is there any method that I can disable all the sensors from a PC provided that I can somehow manage to use adb.
(After installing a custom rom ,the screen works for 1 touch but locks after that)
I have currently installed CM13 official

Related

a strange problem

hii... I have a very strange problem....
I have an unlocked device and I have had pretty much every stock based rom that was published (from hydro to cleanerom 2.7) working perfectly....
The problem is when I try to use any cm based roms (cm10, baked, paranoid etc..) they work fine... but…….. When I connect the stock asus charger to the device, the screen immediately goes blank and can’t be turned on again... (Sometimes it turns on but as I unlock my lock screen,
it becomes black again).
As I disconnect the charger, I can go back to use the device normally...
Please help… I would like to move on to other roms and have the ability to charge the device while using it…
Thanks!! )

[SOLVED] XT1033 with 4.4.4 pre-installed has problem in rooting/custom recoveries

After searching for few days and trying different methods I came to the conclusion that there is an issue in rooting and flashing custom recoveries in XT1033 dual sim phones that were shipped with android 4.4.4 as default ( Most probably the ones sold in august 2014 in India )
In detail...
at least Im lucky because I could successfully unlock my bootloader, but for some the unlock code given by motorola gives " Password incorrect!/OEM unlock failure!" . This is the motorola forum dealing with that issue , more details are int he forum Bootloader Unlock Problems?
So, back to the point, This is the issue..
After successfully unlocking bootloader, I tried flashing custom recoveries, First i tried philz, but when i tried to enter into recovery, phone rebooted- it showed the bootlogo and then some a black blinking screen, the blinking is random, that screen remained until i long press on my power button which boots my phone in the normal way, after that whenever i try to select recovery, what i get is the black screen
This was the case all the recoveries except twrp . In that case, it showed black screen when tried to get into recovery, but if I wait for a minute, the screen times out and after waking up the display by pressing power button, what i see is the twrp recovery window saying "swipe to unlock " but unfortunately touch doesnot work, so i can not unlock it, therefore cannot use it
this issue is present only in phones XT1033 that was pre-installed with 4.4.4
I have tried almost all the recoveries, also tried modified recovery method from modaco
those who have OTAed from 4.4.2 to 4.4.4 were successful in running custom recoveries, but i couldn't find anyone with preinstalled 4.4.4 running a working custom recovery
anyway, somehow the root access can be obtained by sacrificing a working recovery
So, I post this,hoping someone will find a solution soon and if anyone has any feedback please share your suggestions and experiences
edit: problem solved
This is just to inform all those who got their phones with 4.4.4 pre-installed and were suffering from black screen when booted into recovery.
A new version of Philz recovery is released by its maintainer for moto G , which is compatible with the newest bootloader or baseband ( whatever )
Just go to Phil'z recovery and download the latest version ( only 6.57.5 or above )
Devs plz.
can any devs look into this issue, i guess every new motog users from india is facing this issue.. I found another one who bought motog today ( in india ) facing this issue, and many others too...

[Q] Touch in TWRP not working after Lollipop

I updated yesterday, everything went smooth even the flashing of the recovery which I see some people are having trouble with.
Only problem: The touch screen doesn't work while I'm in TWRP.
Only way i got it to work:
Enter TWRP
Wait till screen locks
Open screen - Then the touch works (If I manually lock it then wake it up the touch screen still doesn't work).
I've looked around and I don't think its Lollipop related as people encountered this problem before.
Any suggestions?
Thanks in advance to everyone who helps~

[Q] rom reinstall Q

I am using s5 rom by santosh. I am facing one problem that the 3 capacitive buttons backlight remains on till screen on. Earlier it used to get off after 5sec but not now.
So is it possible to install the same rom again without losing all my data? So that i dont have to install all apps again.
I have tried changing with gravity box but to no use.
Pls help someone.

Help Needed "Blank Screen Instead Lock Screen" Some Times

Hello Developers
I Have Lenovo K3 Note
Indian Variant K50A40
Updated To Latest
K50a40_s121_150813_row
I Faces Many Problems With Stock ROM (Like Touch Screen , Lagging And Network Problems ETC)
So I Decided To Flash A Custom ROM
Downloaded
Aosp ROM
Successfully Flashed With CWM Recovery
Without Any Errors
But After Few Minutes Of Using
Phone Goes To Blank Screen After Lock
(I mean Blank Screen Instead of Lock Screen)
Now Tried Many Times Lock Button
But Same Blank Screen
I Have Removed Battery And Put Again
Phone Again Working Fine
But After Few Minutes
Again Same Problem
So I Thought This Is A ROM Bug
So I Have Downloaded Other ROM
Nexus ROM
And Flashed successfully
After Using Of An Hour
Same Problem Starts In Nexus ROM
Then Downloaded The Official Dev ROM VibeUI_2.8_1540
And Flashed That
But Same Problem Again On This ROM Also
So I Have Flashed Stock ROM With SP Flashtools
In Stock ROM , There Is No Problems Like That
So I Have Flashed Again custom ROM
But Again Same Problem,, revert back to stock
Facebook Developers Says I Am First Who Facing This Type Of Issue
So Please Anyone Help
I think you have a problem in Keyguard.apk

Categories

Resources