Database Info

On my second inspire now... And I have gps problems again

I traded in my first Inspire for a replacement after the GPS started working less reliably after a couple weeks.
Now, a couple weeks into owning this one, I am (frustratingly) experiencing weird problems again.
Yesterday I tried using the GPS to navigate to a club in Baltimore... On the way down, I never got a solid gps lock in navigation. And, oddly enough, on the way back home, the lock was rock solid all the way.
I'm beginning to wonder if this is a defect with the Inspire itself, even though I haven't heard of many people having the same problems. The only "weird" thing I do with my GPS is use c:geo, a geocaching application... I'm wondering if this somehow tampers with GPS settings and starts to affect the gps tracking itself?
I do not use a case. I have not rooted or flashed the phone (nor did I on the previous model).. I really can't think about much else that I might be doing that coudl be affecting the gps.
Anyone have any ideas?

magnumforce2006 said:
I traded in my first Inspire for a replacement after the GPS started working less reliably after a couple weeks.
Now, a couple weeks into owning this one, I am (frustraingly) experiencing weird problems again.
Yesterday I tried using the GPS to navigate to a club in Baltimore... On the way down, I never got a solid gps lock in navigation. And, oddly enough, on the way back home, the lock was rock solid all the way.
I'm beginning to wonder if this is a defect with the Inspire itself, even though I haven't heard of many people having the same problems. The only "weird" thing I do with my GPS is use c:geo, a geocaching application... I'm wondering if this somehow tampers with GPS settings and starts to affect the gps tracking itself?
I do not use a case. I have not rooted or flashed the phone (nor did I on the previous model).. I really can't think about much else that I might be doing that coudl be affecting the gps.
Anyone have any ideas?
Click to expand...
Click to collapse
Go into your settings, location and then uncheck "use wireless networks". Try that and see how it works.
Sent from my Desire HD using XDA Premium App

I will try this later, but I hesitate to say that'd be the problem, when GPS test was only pulling 3-4 satellites earlier today. (under normal conditions it will get twice that easily after a few seconds).
I feel like if this hardware problem was this widespread (that an entire generation of GPS' started going bad on the inspires) more people would be talking about it... And yet I see very little discussion of this happening. Are people just not using their GPS' that much? lol

In my ecperience not all Roms have the greatest GPS for whatever reason.
Use various ones, the one in my signature is a good place to start.

legend221 said:
In my ecperience not all Roms have the greatest GPS for whatever reason.
Use various ones, the one in my signature is a good place to start.
Click to expand...
Click to collapse
As I said in the OP, I am not even rooted. Using the stock ROM.

Never mind. Re read the op....
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

Intermittent quality all the way home from work, even with "use wireless networks" turned off. By the end of the trip it could no longer hold a lock.
So frustrating. I would return this one, but for what? Another couple weeks and I'll be having the same problems.

Welp, rooted and flashed last night to Stock ROM Optimized, flashed LeeDroid 2.2.2. Kernel, applied this fix http://forum.xda-developers.com/showthread.php?t=997647, and I still couldn't get a strong lock on the way to work today.
This is baffling to me. I guess I just won't be using the Inspire's GPS a whole lot, which is a shame, because it's a perfect phone otherwise.

magnumforce2006 said:
Welp, rooted and flashed last night to Stock ROM Optimized, flashed LeeDroid 2.2.2. Kernel, applied this fix http://forum.xda-developers.com/showthread.php?t=997647, and I still couldn't get a strong lock on the way to work today.
This is baffling to me. I guess I just won't be using the Inspire's GPS a whole lot, which is a shame, because it's a perfect phone otherwise.
Click to expand...
Click to collapse
Flash the new miui and follow the setup instructions exactly. Lock was a second or 2 for me!

mj0528 said:
Flash the new miui and follow the setup instructions exactly. Lock was a second or 2 for me!
Click to expand...
Click to collapse
Could I have a link to exactly what you're talking about?

magnumforce2006 said:
Could I have a link to exactly what you're talking about?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=969436

magnumforce2006 said:
Welp, rooted and flashed last night to Stock ROM Optimized, flashed LeeDroid 2.2.2. Kernel, applied this fix http://forum.xda-developers.com/showthread.php?t=997647, and I still couldn't get a strong lock on the way to work today.
This is baffling to me. I guess I just won't be using the Inspire's GPS a whole lot, which is a shame, because it's a perfect phone otherwise.
Click to expand...
Click to collapse
I have this exact same setup on my phone, same Rom, same kernel, and my gps didnt work. I reflashed the stock radio and now i get a lock in under 3 seconds. Give that a try.
Almost forgot I used THIS method to flash the radio, if that matters...
*BE VERY CAREFUL WITH THIS PROCESS YOU CAN BRICK YOUR PHONE WITH A CORRUPT RADIO.IMG*
To flash a radio using hboot with radio S-OFF you can simply take the zip file PD98IMG.zip from the hack kit (Thanks ATTN1) and remove the radio.img file from it using winrar or 7zip, and put a new radio.img from elsewhere in the zip named radio.img and using store (NO) compression. Make sure it is named exactly PD98IMG.zip and put it on the root of your sdcard. Reboot your phone into hboot and the new radio will prompt you to load. Press volume up on the phone and it will load automatically and ask you to press power to reboot.
Click to expand...
Click to collapse
Since your flashing the stock radio no need to take any radio.img file out or put a new one in, just simply flash the PD98IMG.zip in hboot

tdesbien31 said:
I have this exact same setup on my phone, same Rom, same kernel, and my gps didnt work. I reflashed the stock radio and now i get a lock in under 3 seconds. Give that a try.
Almost forgot I used THIS method to flash the radio, if that matters...
Since your flashing the stock radio no need to take any radio.img file out or put a new one in, just simply flash the PD98IMG.zip in hboot
Click to expand...
Click to collapse
Yeahp, I'm gonna give this a try tonight, fingers crossed.
What did you use before the Stock Rom Optimized (and leedroid kernel)? I came straight from stock, and was already having problems so... hmph.

magnumforce2006 said:
Yeahp, I'm gonna give this a try tonight, fingers crossed.
What did you use before the Stock Rom Optimized (and leedroid kernel)? I came straight from stock, and was already having problems so... hmph.
Click to expand...
Click to collapse
I ran alot of other roms, and noone of them were working for me, never got around to trying anything to fix it until i came across someone who reflashed the radio and it worked using the Stock Optomized rom in the thread, so figured id give it a try low and behold it worked for me as well.

Re-flashed the radio last night, don't think it made much of a difference.
Navigation to work today was spotty... Hanging at spots, and never getting a very solid lock (the circle around the little blue arrow would remain probably 20-30 meters large or more). When viewing GPS status I'll usually be anywhere from 4-8 satellites.
I dunno... maybe I'm expecting too much? It has been cloudy/rainy here the past few days, and maybe that's just really affecting it.
I just know that when I first got this phone (and the last one) I'd have strong locks very quickly that would stay strong for the majority of the trip... And it never seemed very weather dependant. *shrugs*

Be happy you get a GPS lock lol, i owned the Captivate for about 5 months and got 1 lock the entire time mo matter what fixes i tried, and the 1 lock was the day i got it.

tdesbien31 said:
Be happy you get a GPS lock lol, i owned the Captivate for about 5 months and got 1 lock the entire time mo matter what fixes i tried, and the 1 lock was the day i got it.
Click to expand...
Click to collapse
Yeah, I guess inconsistently functional is better than nothing. I just don't get why I'm having these problems, when most Inspire owners seem to have perfect GPS still.
I might try trading in for ONE MORE model, just to see what happens... HTC's warranty should cover me for 9 months, right?

magnumforce2006 said:
Yeah, I guess inconsistently functional is better than nothing. I just don't get why I'm having these problems, when most Inspire owners seem to have perfect GPS still.
I might try trading in for ONE MORE model, just to see what happens... HTC's warranty should cover me for 9 months, right?
Click to expand...
Click to collapse
Your guarantee from AT&T itself is 30 days exchange for anything policy regardless. Trade it in for a different phone or another Inspire.
Just make sure you follow the back to stock flashing instructions in development thread before you take it in just in case they want to be assholes about you having alternate software running.

You should try GPS Status from the market.
https://market.android.com/details?id=com.eclipsim.gpsstatus2&feature=search_result
It downloads new AGPS info like once a day if you want it to and has quickened up my fixes a whole bunch. I would try D/L'ing the app, clearing the exsisting AGPS data through the app, and D/L'ing the data new.

Faster fix from the market works awesome to and always fixs my gps after a new rom install .
Sent From My HTC Inspire 4G | [ROM] CoreDroid HD FROYO v3.3 | [KERNEL] LeeDrOiD v2.2.8 OC @ 1.5Ghz

[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?

..

[Q] Gyroscope

I am not sure if the Gyroscope sensor is active in this rom. based on Gyroscope testing apps from the market, no data is present to show the gyro is active.
I just downloaded and installed Android 4.2 Camera and everything works great except for the photosphere. Photosphere does not seem to know where I am moving the phone to take a photo as if there is something not going right with the gyroscope.
All the other sensors work except for the gyro
According to Phone Tester app form the market;
Gyroscope: waiting for data.... No data appears
Properties:
NAME: R3GD20 GYROSCOPE SENSOR
VENDOR: ST
VERSION: 1
POWER: 6.1 mA
RANGE: 34.906586
RESOLUTION: 6.1
I just flashed king Kang with the latest kernel.
I got the same problem going on, no Gyroscope.
How the hell does the Gyroscope break on a band new phone?
Could a sensor be broken by rooting the phone improperly?
I ask because the HTC boot up logo screen says in red text “This build is for development purposes only Do not distribute outside of HTC without HTC’s written permission. Failure to comply may lead to legal action”. Is that normal?
EDIT: I just tried Z-Device Test from the market and the Gyroscope WORKS!!
All 3 axis show a working sensor.
But the raw data numbers do not show
So what the heck is going on for other apps to not read the Gyro?
Atleast I know its not a hardware failure

Same problem!
Dude I have that exact same problem, I've been looking all over the place for more info
I actually make an account just so I could reply to you
I'm currently on Paranormal Android 2.5.1 jelly bean ROM
I flashed the 4.2 camera and everything works fine, pictures, videos, gallery, all except the photosphere
As soon and I click photo sphere it shows that grey grid that looks 3D and a blue dot where I'm supposed to align so it can take the 1st picture. The blue dot moves very very slow and I have to move my phone way too much to get it aligned, then after the 1st picture I try to move to the right or left but I can't the phone doesn't respond. I can only make it move up or down but super slowly so the 1st picture taken is straight ahead but then I basically have to move my phone backwards so the little blue dot gets aligned and take a picture that's nowhere near where its supposed to be. So I just stop it and it renders the photo sphere and I could see it in the gallery but its only the 2 pictures I was able to take that are way off.
I also noticed that after I fail at the photo sphere my gyro and accelerometer are all retarded because I can no longer play tilt based games because the phone wont respond to my tilts. But when I restore my backup I made before I flashed the new camera, I could play tilt games, I still can't use any compass app because the gyro isn't responding. When I run androsensor it just says waiting for update.
Also if I flash the 4.2 camera I could still play tilt game they work but as soon and I try the photo sphere it messes everything up and the tilt games no longer work
So yea you're not alone on this one buddy
EDIT: I just used the z device test and it shows the gyro as working because it moves when i love the phone its just not registering any of the data like how it does on the accelerometer test where it shows the little lines that move up or down when I shake the phone.
I wonder if going back to stock rom would fix this?
---------- Post added at 02:44 PM ---------- Previous post was at 02:35 PM ----------
davidalindsey said:
I am not sure if the Gyroscope sensor is active in this rom based on Gyroscope testing apps from the market, no data is present to show the Gryo is active.
Do you think going back to stock ROM would fix this problem?
Click to expand...
Click to collapse

AHH i'm not the only one.
Everything you just described is the exact thing that happens to me. The exact!
I have searched and searched and found nothing about the OneX Gyro failing.
I am quite frustrated with this issue. I have tried flashing other roms, fixing permissions, clearing cach, data, reboots, and I have gotten nothing.
I am to the point of RUU'ing to a stock ATT rom, relocking the bootloader unrooting and flashing Stock OEM rom.
I made another thread here: [Q] Stock OEM factory rom
Please keep me informed on this issue as I wil do the samel If I come up with anything.

davidalindsey said:
AHH i'm not the only one.
Everything you just described is the exact thing that happens to me. The exact!
I have searched and searched and found nothing about the OneX Gyro failing.
I am quite frustrated with this issue. I have tried flashing other roms, fixing permissions, clearing cach, data, reboots, and I have gotten nothing.
I am to the point of RUU'ing to a stock ATT rom, relocking the bootloader unrooting and flashing Stock OEM rom.
I made another thread here: [Q] Stock OEM factory rom
Please keep me informed on this issue as I wil do the samel If I come up with anything.
Click to expand...
Click to collapse
Me too I was going crazy because there was nothing about this anywhere that I looked.
I wouldn't mind going back to stock but I have no idea how to do so. I made a backup of my stock ROM with twrp before I flashed paranoid android. But since I had to flash the boot.img to get paranoid android to work I don't know if I have to do the same with my stock backup.
Can I just go into twrp and restore the stock backup that I made? Or do I have to flash the boot.img as well? I copied my stock backup to my computer and opened it but there isn't a boot.img file in there so I don't know what to do
I'll be sure to check out your other thread

Well I never made backup of my stock rooted rom, so I have no ideal about flashing the backup stock rom concerning the boot.img.
I am just will to go back to factory spec and RUU the phone and reroot.
I wish some more people have come accross this to see if there is a fix.

delete
double post

Well thanks I'll just keep on searching
Yea I hope more people read this maybe they can help
I don't even care about the gyro until photo sphere haha
Oh I noticed that on Google maps if I go into street view then menu and tap on compass mode it doesn't work either, I move my phone around but it doesn't move.
You mind checking on yours to see if it works?

I can confirm that compass mode does not work on main map and street view with Google maps.
Compass does not work on GPS status app either.

davidalindsey said:
I can confirm that compass mode does not work on main map and street view with Google maps.
Compass does not work on GPS status app either.
Click to expand...
Click to collapse
Well then we basically have the same phone haha
Any luck on going back to stock?

I am trying to hold off on RUUing cause I just got eveything set up the way I like.
It is going to be a pain in the ass to start all over just because of one little issue.
I might try tomorrow seeing that I am off for the day

Mine works fine. EVERYTHING.
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.

I just went thru the RUU process and now my gyroscope is working great.
All sensors are working.
Now I have to unlock bootloader and reroot.
I wonder how the heck this one sensor got screwed up during the rooting process?

davidalindsey said:
I just went thru the RUU process and now my gyroscope is working great.
All sensors are working.
Now I have to unlock bootloader and reroot.
I wonder how the heck this one sensor got screwed up during the rooting process?
Click to expand...
Click to collapse
That's great to hear! I think I'll do that as well
That is very weird that the sensors would mess up like that, maybe the ROMs don't have the nessessary drivers
Are you going to flash another ROM? Im going to flash an ICS ROM maybe they won't mess up the sensors

Yes I really like RebelMOD 2.0 with rohan kernel build 5.
This rom according to post does not have any issue's with sensor.

Concerning to the OP... That red message appears after you lock the bootloader. It's evident on all of our phones.
I'm a developer and I've flashed MANY ROMs. Many. And my gyroscope is still functional. I had the CM Nightly flashed last night, and the gyro was working great. Something must not be displaying data properly, but I highly doubt the gyro was "broken" and magically fixed with the RUU.

I am having the same problem but only on aosp ROMs. The gyroscope works perfect on sense ROMs but I prefer aosp. I have been looking everywhere to find a solution but came up empty.
Sent from my One X using xda premium
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
I am also coming from the 2.20 with hboot 1.14 if it matters.
Sent from my One X using xda premium

HTC_Phone said:
Concerning to the OP... That red message appears after you lock the bootloader. It's evident on all of our phones.
I'm a developer and I've flashed MANY ROMs. Many. And my gyroscope is still functional. I had the CM Nightly flashed last night, and the gyro was working great. Something must not be displaying data properly, but I highly doubt the gyro was "broken" and magically fixed with the RUU.
Click to expand...
Click to collapse
Thanks for the clarification concerning the red message.
I swear to you that the gyro went crap after flashing a jelly bean rom.
Then like magic after the RUU it worked.
I am in the process of rooting my phone again right now.
I hope it doesnt do it again..

Keep us posted please.
Sent from my One X using xda premium

Okay So I have a unlock rooted AT&T phone, no rom yet.
I checked gyro and it functions as it should.
I will be flashing rebel mod 2.0 with rohan kernel build 5 and report back.

Gonna keep an eye on this, curious to see your findings.

[Q] Touch sensor randomly stops working

Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.

Did u over or under clock..flash a mod to control kernel? That's what it sounds like

I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita

Wow. I never knew there was an issue with stock kernel...what's causing that anyways?

Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago

Look under Tims sig

marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita

timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly

You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita

SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.

Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda

There's a way to diagnose it. Download an app called sensor on play store

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.