Database Info

OTA Update 1.132.405.6

Just checked my system update and there is a new one available.
System Upgrade 1.132.405.6 (18.1MB)
-Update: Improve screen control and Youtube client performance connection.
I'm guessing the youtube part is perhaps a solution to the crash error in the latest youtube update when you try to go back from landscape mode viewing. Screen control improvement possibly a Proximity Sensor fix?
Yet to download it but will try tonight on WiFi and update on what else seems to have changed.

just checked my had and found same update,,,here goes hope it fixes things and dont break anything (battery should last 5 days with new update )
wishfull thinking

Same here!

I can confirm this fixes the Youtube bug! Don,t have the prox. sensor issue, so can't check this!

+1 Fingers crossed

If you can't see it in the update section of your phone I've uploaded this RUU and others to:
http://mcgh.ee/DHD

Have just installed it, has made a definite improvement to the proximity sensor. Not holding my breath for the next couple of days though.

trevfee said:
Have just installed it, has made a definite improvement to the proximity sensor. Not holding my breath for the next couple of days though.
Click to expand...
Click to collapse
+1 here

got it here and it fixes youtube, one thing you have to say about HTC is that they sort out software issues pretty quick .The phones been out about what 10/14 days and 2 updates already , while some say there should not be faults, i look at it that at least they get their finger out and sort them

I like this "bug solving speed" too, compared to 5 months of solving 2.1 bugs in case of Motorola Milestone (which was extremly annoying as one of the bugs was a random reboot bug).

Nice seeing some updates but the sync problems on Exchange 2010 are still the same. I cant use the phone without this feature.

Yes, the Exchange Server 2010 Problem is still unsolved :-(

update, same as all, you tube fixed. i didnt have any issue with sensor ever so...

Can confirm that this update has new radio version: 26.03.02.26_M, HBoot remains at version: 0.85.0007
VISIONary still working nicely. I guess we will see exactly what they mean by "SCREEN CONTROL" in the update as the days move on.

mousey_ said:
If you can't see it in the update section of your phone I've uploaded this RUU and others to:
http://mcgh.ee/DHD
Click to expand...
Click to collapse
But 1.32.405.6 is missing there..

Lame old tmobile.. I get kicked from my data connection if I try to download the update.
And by kicked I mean lost all data for least 10th mins.
Sent from my Desire HD using XDA App

would like to hear more thoughts on the proximity sensor. did this fix it for anyone else?

whulfcastle said:
Lame old tmobile.. I get kicked from my data connection if I try to download the update.
Click to expand...
Click to collapse
Me too, I thought it was my signal at first and restarted the phone twice, I'll wait until I get home and use the WiFi

Just out of interest are people doing hard resets of the phone after an update? I had to do it after updating when I first got the phone and it solved a lot of the problems I'd started getting since the update but it just seems like effort to do it each time without a decent whole phone backup and restore facility in place.

yes confirm the update did download and install normally....I don't have the prox snsr issue, but seems to fix the youtube bug....
all go here.....love my device....
;-)

[Q][Solved] Problems on Nexus S i9023

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?

..

is there a sensor fix yet?

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.

Problem with my OnePlus One's Screen!

Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!

I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.

welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases

I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?

Try going back to cm11s and then check...
Sent from Android (a google product)

Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.

Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!

One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?

naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?

Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.

donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/

vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.

I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.

donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..

vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.

Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!

Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk

anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.

donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk

Just bought this

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.