Hello guys, i just bought this device a couple of days ago, for just 49.900 KWD = less than 150 USD, for its specs this is a steal.
Anyways, the device is awesome , but the development is dead, whats going on here.
I had poco f1 back on 2018 and it's development is going on.
Now i have poco f2 pro, but i liked the u12+ design.
The problem is the battery doesn't last 4 hours of sot during the day!
Is there any solution for it?
lol, me too Mostafa, i bought mine from FCC for 49KD
I unlocked the bootloader and flashed the beta viper rom, android 11
battery is the same, it's how it was built, it never lasts longer than 4hrs sot, but im hoping it will be improved once the viper rom goes into stable release
if you need any help you can pm me your phone number
Hahahahahahah.
The device is awesome bro, i unlocked and rooted too, but checked viper and read it has some issues, can u tell me your experience.
As i want to use the device as my main daily driver.
mostafa asal said:
Hahahahahahah.
The device is awesome bro, i unlocked and rooted too, but checked viper and read it has some issues, can u tell me your experience.
As i want to use the device as my main daily driver.
Click to expand...
Click to collapse
You can def use it as a main driver, get Viper, it's great.
If you check the last page in there or perior, i posted a reply mentioning few bugs, and most of them i fixed, rest are minor bugs that wont affect your usage that much, hence why i said once stable is out, the rom will be amazing
PS: What are you using right now if you dont mind me asking ? Stock n rooted ?
Yup stock and rooted.
I will try it today , thanks a lot bro
managed to flash it after a couple of failed tries an hour ago.
first impression >> amaaaaaazing.
mostafa asal said:
managed to flash it after a couple of failed tries an hour ago.
first impression >> amaaaaaazing.
Click to expand...
Click to collapse
Mostafa, did you perm-flash TWRP & root after flashing Viper Beta ? If yes can you please PM me with the steps you followed ?
Inpain said:
Mostafa, did you perm-flash TWRP & root after flashing Viper Beta ? If yes can you please PM me with the steps you followed ?
Click to expand...
Click to collapse
Mmmmm okey , i'm really not sure cuz i flashed the rom 3 timed till now, and every time it worked with a different order of steps
But the last time which i fell it more stable.
-Booted twrp
-Adb pushed all the files and fixes i needed.
even the system.img as i don't know why it never worked for me to flash it from download mode.
- flashed twrp img then magisk 21.1
as the newer version cuzed bootloop for me( idk i might be wrong and the reason is something else)
- flashed all the fixes i wanted.
-Entered download mode erased userdata, system.
-Rebooted to recovery
- flashed system.img and gapps.
- rebooted
- never really cared about cts so haven't done it's fix.
Anyways cbk app and kuwait id app always detect root even after activating hide in magisk
Last thing the only way i found to get ytvanced working is to flash the old magisk module for it.
Old but better than not working at all.
Have you found a fix for auto rotate, and the broken auto brightness or the in calls bluetooth headsets?
mostafa asal said:
Have you found a fix for auto rotate, and the broken auto brightness or the in calls bluetooth headsets?
Click to expand...
Click to collapse
Auto-rotate isnt broken, just goto settings > Edge Sense > Holding gesture & turn off Smart rotate
As for the Auto Brightness, i never had an issue with it, what's your issue ?
Bluetooth is working fine for me if i connect through the AUX BT dongle that i have in my car, never tested headsets.
Inpain said:
Auto-rotate isnt broken, just goto settings > Edge Sense > Holding gesture & turn off Smart rotate
As for the Auto Brightness, i never had an issue with it, what's your issue ?
Bluetooth is working fine for me if i connect through the AUX BT dongle that i have in my car, never tested headsets.
Click to expand...
Click to collapse
yup, you're right about the auto rotate.
but i have a very strange behavior regarding auto brightness, may be the rom needs one more time flashing, lol.
cuz each time i flash it , it gets more stable.
mostafa asal said:
yup, you're right about the auto rotate.
but i have a very strange behavior regarding auto brightness, may be the rom needs one more time flashing, lol.
cuz each time i flash it , it gets more stable.
Click to expand...
Click to collapse
That does not answer my question what is the auto-brightness issue you're facing ?
Also, re-flashing the ROM multiple times isn't going to make it stable-ER
Inpain said:
That does not answer my question what is the auto-brightness issue you're facing ?
Also, re-flashing the ROM multiple times isn't going to make it stable-ER
Click to expand...
Click to collapse
the issue i have is the auto brightness is uncontrollable, sometimes it reaches it's peak and never cool down, and once you lower it down manually, it never goes up !
there's a certain point it operate within , even when i slide it below this point it goes to zero again.
i will upload a vid for it.
mostafa asal said:
Click to expand...
Click to collapse
I see, well you can try something, go back to stock, and see if it behaves the same, if it does, then your sensors aren't working and you'll need to take it to FCC, just make sure you re-lock it before you do so
If it's normal on stock, then yeah, it's a ROM issue.
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Inpain said:
I see, well you can try something, go back to stock, and see if it behaves the same, if it does, then your sensors aren't working and you'll need to take it to FCC, just make sure you re-lock it before you do so
If it's normal on stock, then yeah, it's a ROM issue.
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Click to expand...
Click to collapse
On stock it works perfect, so there's no issue with the sensor.
The bad thing about this device if you relocked it. It says ( relocked ), they will know anyway.
Unlike my poco f2 pro, before i sent it to blooms for cleaning the speaker, i had to relock it, and it says locked.
Why htc made such thing!!
Yesterday, i was in Fahahel and i found FFC store and asked them about a cover and screen protector for the device, they said they don't have!!!
They are the only one selling the device in kuwait and they don't have covers for it.
But if you dying for it they can import it from UAE for 7 KWD
It to
Inpain said:
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Click to expand...
Click to collapse
Maybe if you waited for the stable rom, thay can solve the issue, or maybe there's a workaround.
For me i'm using it as a secondary device for music n videos.
And it's elegant design and color.
Related
As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
sorry to make another thread on this but anyway, lets get to the point
my sensation (and others, as well) has problems with the proximity and light sensors.
sometimes the proximity sensor works, but after a while it stops reading it. this is most likely not a hardware issue. with the ambient light sensor i have no idea whether it works or not but im assuming this is also a software related.
any fixes yet or is this a problem with all sense4.0/ICS ROMs? its really irritating when i have to change brightness all the time or when my face hangs up or mutes a call haha
i heard some people tried fixes, tried reverting to sense 3.6 or even GB ROMs but the problem persisted.. i hope its not completely and permanently damaged, i just bought this phone
DonDizzurp said:
sorry to make another thread on this but anyway, lets get to the point
my sensation (and others, as well) has problems with the proximity and light sensors.
sometimes the proximity sensor works, but after a while it stops reading it. this is most likely not a hardware issue. with the ambient light sensor i have no idea whether it works or not but im assuming this is also a software related.
any fixes yet or is this a problem with all sense4.0/ICS ROMs? its really irritating when i have to change brightness all the time or when my face hangs up or mutes a call haha
i heard some people tried fixes, tried reverting to sense 3.6 or even GB ROMs but the problem persisted.. i hope its not completely and permanently damaged, i just bought this phone
Click to expand...
Click to collapse
Turn off fastboot. This was the fix I used when I experienced this in ARHD.
kgs1992 said:
Turn off fastboot. This was the fix I used when I experienced this in ARHD.
Click to expand...
Click to collapse
i turned off fastboot, shut down my phone, then turned it on face-down in a dark room and both proxi and light are working again..
the thing is, others have tried this and it ends up failing eventually. i really hope this is just a software/kernel issue and will be resolved with updates.. if its a hardware issue, i think im gonna have to step away from HTC after all these years..
DonDizzurp said:
i turned off fastboot, shut down my phone, then turned it on face-down in a dark room and both proxi and light are working again..
the thing is, others have tried this and it ends up failing eventually. i really hope this is just a software/kernel issue and will be resolved with updates.. if its a hardware issue, i think im gonna have to step away from HTC after all these years..
Click to expand...
Click to collapse
Software issue for sure. don't worry!
i did a "superwipe" using the file from the ARHD thread
then i installed the base from the same thread
Then i installed ARHD and both sensors are working
then i did a superwipe again and installed the PKMN ROM and both sensors are still working after several reboots... hmmmmm...
im gonna try ordroid again, hopefully they dont mess up
im really really really really glad this is not a hardware issue
DonDizzurp said:
i did a "superwipe" using the file from the ARHD thread
then i installed the base from the same thread
Then i installed ARHD and both sensors are working
then i did a superwipe again and installed the PKMN ROM and both sensors are still working after several reboots... hmmmmm...
im gonna try ordroid again, hopefully they dont mess up
im really really really really glad this is not a hardware issue
Click to expand...
Click to collapse
Does your sensors still working? did you figured out what was the problem?
tamirsh said:
Does your sensors still working? did you figured out what was the problem?
Click to expand...
Click to collapse
yea it didnt work.. it stopped working by the end of the day. i think the t-mobile firmware is from a different country
so this time i did the same thing but i used the latest T-mobile US firmware that came out a week or two ago (since my phone is t-mobile from US)
process:
- superwipe
- install firmware
- install ordroid
things have been good for the past few days. im getting worse service with the radio but im gonna change it and see if it affects it
i guess these phones are very small hardware variations that different firmware addresses differently. its been working for days now so i think its fixed for good
DonDizzurp said:
yea it didnt work.. it stopped working by the end of the day. i think the t-mobile firmware is from a different country
so this time i did the same thing but i used the latest T-mobile US firmware that came out a week or two ago (since my phone is t-mobile from US)
process:
- superwipe
- install firmware
- install ordroid
things have been good for the past few days. im getting worse service with the radio but im gonna change it and see if it affects it
i guess these phones are very small hardware variations that different firmware addresses differently. its been working for days now so i think its fixed for good
Click to expand...
Click to collapse
To be honest, SuperWipe is not the best way to clean up the phone.
I'd recommend the "Format all partitions except SD Card" option in 4ext.
Also, this is unnecessary if you are switching between ROMs having the same Android version & Sense version. In that case, just back up as you usually would before switching a ROM (NANDROID+ Apps + Messages + Contacts), wipe cache & dalvik, then proceed to install the ROM.
Should you face any problems, format all partitions except SD Card & re-install.
Hope this helps.
kgs1992 said:
To be honest, SuperWipe is not the best way to clean up the phone.
I'd recommend the "Format all partitions except SD Card" option in 4ext.
Also, this is unnecessary if you are switching between ROMs having the same Android version & Sense version. In that case, just back up as you usually would before switching a ROM (NANDROID+ Apps + Messages + Contacts), wipe cache & dalvik, then proceed to install the ROM.
Should you face any problems, format all partitions except SD Card & re-install.
Hope this helps.
Click to expand...
Click to collapse
i usually just do a full wipe.. the superwipe thing does the same thing expect it also wipes system
Are you guys finding its not just the prox and light sensor but the gyroscope, accelerometer as well?
dtyson said:
Are you guys finding its not just the prox and light sensor but the gyroscope, accelerometer as well?
Click to expand...
Click to collapse
oh man i hope not
the proxi and light sensors are pissing me off, they dont last. sometimes as long as you dont turn your phone off or restart, theyll last forever but its so annoying
i think my gyro and acc are working.. not sure how accurate they are but they are taking measurements so i guess thats good enough
My phone was stuffed, no sensors (acc,gyro,g-senor,prox,light,magnetic etc etc), then the next thing was the earpiece got all tinny sounding (on both stock and custom roms). HTC Australia did a straight handset swap, 4 business day turn around. hopefully I wont get the same prob again
Fastboost on or off????
After experiencing the same problem most of you have: light sensor and proximity are not working, I checked some posts. Espescially when in direct sunlight my Auto Brightness wasn't working and when hanging up a phone call my screen stayed black.
All posts had to do with Super Wipe, change kernels, flash ROM's etc etc
Then I saw that somone said: turn Fastboost off.
But my Fastboost was already off. So...I turned it on....reboot and......it works again!!!!
Hope it stays this way. Everybody....good luck!!
BTW: Sensation is Super CID, 4.0.3 Sense 3.6, software version 3.33.401.6
So...
Got the same problem here...
All of my sensors "died" and the backlight on the buttons as well...
I've tried everything said over here...
I realy do hope its a software issue and getting fixed fast
accelerometer, gyroscope not working
First of all, sorry to pull back a really old thread but I thought this thread had the most relevant discussion.
My Sensation's accelerometer and gyroscope sensors are not working. They stopped working the first time I tried unlocking the bootloader of my phone and installing a custom ROM. That was almost a year back and I have been trying to live with the phone like that. Since then, I have also installed multiple different ROMs. Currently, I am on Cyanogenmod 10 nightly. Its a good ROM and everything works except the Gyroscope and accelerometer sensors but I need to get these sensors working again. I have tried different kenels, firmwares, ROMs, etc etc.
Any suggestions?
aslambhai said:
First of all, sorry to pull back a really old thread but I thought this thread had the most relevant discussion.
My Sensation's accelerometer and gyroscope sensors are not working. They stopped working the first time I tried unlocking the bootloader of my phone and installing a custom ROM. That was almost a year back and I have been trying to live with the phone like that. Since then, I have also installed multiple different ROMs. Currently, I am on Cyanogenmod 10 nightly. Its a good ROM and everything works except the Gyroscope and accelerometer sensors but I need to get these sensors working again. I have tried different kenels, firmwares, ROMs, etc etc.
Any suggestions?
Click to expand...
Click to collapse
Try to go to stock again by flashing a ruu and check again
Sent from my Nexus 7 using xda premium
ganeshp said:
Try to go to stock again by flashing a ruu and check again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks Ganesh. I will try doing this.
Can you share some reliable site for the RUUs? I found some, but am not sure about the authenticity of the ROMs given that the MD5 cheksum is missing at the download locations.
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.
ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too
sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.
I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.
Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.
http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html
Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you
I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'
i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...
I got ipega 9055 game controller and noticed moving keys don't right. Keys get stuck or not register. Controller works in other phones.
This problem seems to be in other lenovo phones also.
I found some other people have similar issues:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/lp05_en/thread-id/923/page/2
In lenovo forums fix seems to be changing region to RU what seems weird. I have not tried this yet.
I was thinking does anyone else have game controller and issues like this?
Yes I do! And it drives me nuts trying to play Mario Kart. ?
Been trying everything to fix it...
titaniumfish said:
Yes I do! And it drives me nuts trying to play Mario Kart. ?
Been trying everything to fix it...
Click to expand...
Click to collapse
I'm going to flash custom rom because of this. I tried everything i can think of with no result..
This issue has been pretty long and Lenovo is probably not going to do anything about it.
It would be nice to know if problem persists in custom rom. I strongky think its software related but i will see after 14 days...
Been tempted to stay clear of rooting this one for the likes of sky go and android pay so let me know how you get on with the flash. See if it helps. I was checking the Bluetooth specs on my P2 compared to other devices and it doesn't seem to be that. So I'm stumped. It appears the joystick is the only thing not responding properly. One press and it appears to be stuck in that position. I know for a fact it's not the joystick. Works a treat on my old S5.
titaniumfish said:
Been tempted to stay clear of rooting this one for the likes of sky go and android pay so let me know how you get on with the flash. See if it helps. I was checking the Bluetooth specs on my P2 compared to other devices and it doesn't seem to be that. So I'm stumped. It appears the joystick is the only thing not responding properly. One press and it appears to be stuck in that position. I know for a fact it's not the joystick. Works a treat on my old S5.
Click to expand...
Click to collapse
I also wanted to stay stock for awhile longer..
Im also positive there is nothing wrong with my gamepad, tested mine with S6.
I let you know how it goes.
I can tell you now that nothing's wrong with your gamepad. In the MegaN64 app there's an option in input, controller, controller diagnostics to check the button and directional pushes. As you can see from the first screenshot the left joystick pushed down (AXIS-Y) is stuck on +0.67. Somewhere between half and a whole push. I had released the joystick while I took this screenshot. It's just stuck there. In the second screenshot I pushed the right trigger button (AXIS_GAS) Which cancelled the stuck joystick position but then that trigger button got stuck on +0.40. Nearly half a push. I had also let go of the trigger button while I took this screenshot. Personally I think it's down to Lenovo using cheap Bluetooth hardware. That's my guess. I'd love to be proved wrong though.
titaniumfish said:
I can tell you now that nothing's wrong with your gamepad. In the MegaN64 app there's an option in input, controller, controller diagnostics to check the button and directional pushes. As you can see from the first screenshot the left joystick pushed down (AXIS-Y) is stuck on +0.67. Somewhere between half and a whole push. I had released the joystick while I took this screenshot. It's just stuck there. In the second screenshot I pushed the right trigger button (AXIS_GAS) Which cancelled the stuck joystick position but then that trigger button got stuck on +0.40. Nearly half a push. I had also let go of the trigger button while I took this screenshot. Personally I think it's down to Lenovo using cheap Bluetooth hardware. That's my guess. I'd love to be proved wrong though.
Click to expand...
Click to collapse
Thanks for testing.
I really hope its not hardware problem.
I'm sad that this is pretty common problem with Lenovo phones and there is no support from their part.
How did you get on with the flash?
Any custom ROMS have any better result?
titaniumfish said:
How did you get on with the flash?
Any custom ROMS have any better result?
Click to expand...
Click to collapse
I have not yet flashed because of waiting period. Still 8 days remaining.
But in dev section i got answer that custom rom will fix issue.
Please check here: https://forum.xda-developers.com/showthread.php?t=3592706
page 4 #38
Then again I suppose there's no Knox counter on P2 haha. I'm assuming you can unroot if necessary?
Are you going to install that custom ROM in the link? Or another?
No knox counter but OEM lock what you can unlock from dev settings(waiting time 14 days). After that you loose warranty.
I was thinking to try AOSP extended(same as link) but i have not decided.
I suppose you can unroot and go back to stock but warranty is gone.
edit: Now im on Resurrection mod. No problem with bt controller what so ever.
Kiryo24 said:
No knox counter but OEM lock what you can unlock from dev settings(waiting time 14 days). After that you loose warranty.
I was thinking to try AOSP extended(same as link) but i have not decided.
I suppose you can unroot and go back to stock but warranty is gone.
edit: Now im on Resurrection mod. No problem with bt controller what so ever.
Click to expand...
Click to collapse
I was going to update anyone else on stock ROM. Just received a Gamesir WIRED controller and it's STILL experiencing the same issues. So after all that it's not been a Bluetooth issue at all. Just software. Great news that the Custom ROM worked for you. Think I might have to go down the same route. Which ROM was it you went for?
titaniumfish said:
I was going to update anyone else on stock ROM. Just received a Gamesir WIRED controller and it's STILL experiencing the same issues. So after all that it's not been a Bluetooth issue at all. Just software. Great news that the Custom ROM worked for you. Think I might have to go down the same route. Which ROM was it you went for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/development/7-1-1-resurrection-remix-v5-8-2-lenovo-t3575669
Ah that would explain why my Drone was acting crazy yesterday when I was flying it with my USB Gamepad, I thought the gamepad was shot ! It never crossed my mind that the P2 might be at fault...oh well a few more days to wait before I can unlock it.
I wonder if they'll just ever release Nougat for it? Haha. They're slacking big time.
btw if there is still people using stock system and want issue fixed, Lenovo has asked me for log info. I couldn't wait and flashed custom rom. Here is thread link if anyone is interested:https://forums.lenovo.com/t5/P2-P2a42-Smartphones/bluetooth-controller-problem/td-p/3652943
Nice one, Kiryo. I'm still on stock for Android pay as it's come in so handy. ? Already had developer options enabled as I thought there might be an extra Bluetooth setting to adjust to try and fix the issue but there wasn't. So I've enabled bugging reports now. I'll send them a report over as soon as I get the controller connected later on. ?
Kiryo... Just curious. How are you getting on with the Custom ROM? Does it still have the same features the stock ROM has? Such as VR mode and dual app mode? Cheers...
titaniumfish said:
Kiryo... Just curious. How are you getting on with the Custom ROM? Does it still have the same features the stock ROM has? Such as VR mode and dual app mode? Cheers...
Click to expand...
Click to collapse
Well there is all that i need. I have no need for VR mode but i guess it works in apps normally.
I also dont use dual app mode but i guess there is mutitasking option there.
Custom roms offer much more configurations than stock.
Im overall happy. There is still some issues with volume echoing with speaker and volume sliders during call etc.. but nothing too serious.
I'm just happy with functional bt controller.
Yeah I bet. Thanks for the info. ?
I'll look into making a nand backup as well I think. (If that still exists)
Tested via Xiaomi built-in QC, Look at mark 0:15, the number stays 0 after I removed my hand from the sensor.
Another user on reddit is facing similar issue.
https://www.reddit.com/r/PocoX3/comments/m43121
There are a lot of people who are facing this issue with the Poco NFC. There are usually 3 problems and you need to try all of them.
1: Hardware issue : Cannot be fixed in software and requires device replacement in warranty.
2: Screen Guard that's dirty or too large covering the sensor area.
3: A bug in the software that can be fixed with a factory reset.
The proximity sensor is located on the top left of the camera punch hole near the LED light. So make sure nothing is clogged in that area or the screen guard is not scratched or covering that area. You will be able to see the sensor if it's working if you make a call and point another camera at it and notice a blinking light. I'm hoping it's just dirt or debris and that you don't have to get a device replacement.
Me having exactly same issue. Screen doesn't turn off during calls when I put my face near or touch the sensor.
****ty thing else
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via fastboot the previous one and stay with it or go to custom rom (with 12.0.7.0 or older firmware/vendor)
fonz93 said:
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via fastboot the previous one and stay with it or go to custom rom (with 12.0.7.0 or older firmware/vendor)
Click to expand...
Click to collapse
Good to know, but I'll wait for the next update and hopefully they will fix it.
fonz93 said:
The problem is the new miui update 12.0.8.0, the new firmware/vendor is somehow broken (indeed if you go on custom ROM the bug will still be there), to fix it i went back to MIUI 12.0.7.0 via fastboot (just to assure being clean, i don't know if the problem is in vendor or firmware)
edit: i did some tests and miui is 100% safe till 12.0.7.0, the only one broken is 12.0.8.0 so if you are having problems flash via
Click to expand...
Click to collapse
MrPotatoBall said:
Good
Click to expand...
Click to collapse
Pocopoñy said:
Me having exactly same issue. Screen doesn't turn off during calls when I put my face near or touch the sensor.
****ty thing else
Click to expand...
Click to collapse
MrPotatoBall said:
Good to know, but I'll wait for the next update and hopefully they will fix it.
Click to expand...
Click to collapse
Okay I don't understand this new XDA reply thing... But if you guys figure out the particular trigger in the MIUI software please let me know.
What is this new complex reply system?
I can't even cancel it. Even if I clear data of the browser and log in it brings me back to this complex stacked reply system. Can anyone explain?
Anyone managed to find a solution?
Recalibrate proximity sensor.
1. open settings
2. click all specs
3. click Kernel Version 3 milion times
4. CIT menu will open.
5. click three dots top right corner
6. click additional tools
7. select option nr.10 proximity sensor
8. click calibrate.
9 go back to CIT
10. Select option nr. 15 proximity sensor to test
tuncay_93 said:
Recalibrate proximity sensor.
1. open settings
2. click all specs
3. click Kernel Version 3 milion times
4. CIT menu will open.
5. click three dots top right corner
6. click additional tools
7. select option nr.10 proximity sensor
8. click calibrate.
9 go back to CIT
10. Select option nr. 15 proximity sensor to test
Click to expand...
Click to collapse
Still doesn't work after calibrated.
RMA your device.
You have a faulty sensor.
Alrich said:
RMA your device.
You have a faulty sensor.
Click to expand...
Click to collapse
Nope, it's software issue. Many Xiaomi phone have the same problem.
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Alrich said:
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Click to expand...
Click to collapse
why should it be an hardware issue when it's clear that the bug came with a software update? so we all have a faulty proximity sensor? it's full of people having this problem... we just downgraded to 12.0.7.0 firmware and all it's solved, custom rom it's not the solution, downgrading the firmware is... then you can do what you want (installing a custom rom too)
Alrich said:
Alright you seem to be confident your problem is a "software" problem even though all the software remedies suggested to you haven't worked. Mind you, these remedies are coming from people who have the same phone as you and are on the same firmware as you.
In fact regardless of your region, since the date you posted, there have been two more system updates and your problem still isn't solved.
RMA your device or flash custom ROM.
If not you can still continue to believe it's a software problem till your warranty expires.
Click to expand...
Click to collapse
Yes, I'm CONFIDENT to say it is a "software" problem.
You obviously didn't even follow this thread.
fonz93 said:
why should it be an hardware issue when it's clear that the bug came with a software update? so we all have a faulty proximity sensor? it's full of people having this problem... we just downgraded to 12.0.7.0 firmware and all it's solved, custom rom it's not the solution, downgrading the firmware is... then you can do what you want (installing a custom rom too)
Click to expand...
Click to collapse
Well said.
There is a new update available, 12.0.8.0 Android 11 seems to fix the proximity sensor problem.
MrPotatoBall said:
There is a new update available, 12.0.8.0 Android 11 seems to fix the proximity sensor problem.
Click to expand...
Click to collapse
Yes it does, but android 11 seems to be pretty buggy/laggy at the moment...
Had this problem but for me it was the screen protector messing with the sensors i had a better one and its solved
fonz93 said:
Yes it does, but android 11 seems to be pretty buggy/laggy at the moment...
Click to expand...
Click to collapse
Android 11 is perfectly fine. MIUI is buggy