Related
So I've been using the same ROM (in my sig) on my T-Mobile TP2 for 2 weeks now. Last night I tried to wake my phone (it was on for 8 hours already; being used 4 hours prior to make a PowerPoint using JetCet Presenter 5), and the phone wouldn't wake up. I pressed the soft reset button on the side, and everything was fine. I pressed the power button again before I put it in my holster. Ten minutes later, I pressed the power button to wake it, and it wouldn't wake up again! I did the soft reset thing, and battery was down 5-10%, so I know the phone was on the whole time.
I did a hard reset, and still had same problems. I was going to return it with warranty, so I flashed the stock T-Mobile WM6.1 ROM and everything was fine (I couldn't replicate any of my problems). I went to a different ROM (the latest Valkyrie Leo 23815, I believe?), and I got the same "can't wake" problem.
Now my real problem is the fact that I can't replicate it on the stock ROM. I think it's not the custom ROM because I've used the same one for 2 weeks. I don't know how I can get a warranty swap in this situation... It's not like I can say "Look, I have your stock WM6.1 ROM and it works. How come it can't work with a custom ROM?!"
*I confess I did just download the JetCet Presenter5 cab from these forums just two days ago. I made a PPT (as stated in the first paragraph) for a class and I saved it on my SDHC card. It was working afterwards, but the "can't wake" problem only occurred 4 hours later, and still persists after the hard reset.
Can I please get any help here? I really need a working device with a custom ROM and I don't know how to do a warranty swap in this situation.
Thanks.
SOLUTION: post#19.
(I replied this also on TmoNews forum)
What do you have to do create this problem...just wait and it happens eventually? Or does it happen right away the first time it goes into standby, or you put it in standby? Or is there a specific sequece of events?
How long did you wait after flashing the stock WM6.1 to see if the problem came up?
Maybe you could try flashing the "hidden" official WM6.5 rom...just on the chance that it might fix/delete whatever is wrong. Or it might show the problem so you could return it...after the Jan-20 official release.
Good luck
MCbrian said:
(I replied this also on TmoNews forum)
What do you have to do create this problem...just wait and it happens eventually? Or does it happen right away the first time it goes into standby, or you put it in standby? Or is there a specific sequece of events?
How long did you wait after flashing the stock WM6.1 to see if the problem came up?
Maybe you could try flashing the "hidden" official WM6.5 rom...just on the chance that it might fix/delete whatever is wrong. Or it might show the problem so you could return it...after the Jan-20 official release.
Good luck
Click to expand...
Click to collapse
(Replied this on TmoNews, but this might help others willing to help out)
On the custom ROMs, the first time it goes into standby, I can't wake the phone anymore and I just noticed that it won't recognize the USB cable (no charge from the outlet; no sync with the PC). If I soft reset and prevent it from going to standby, everything's normal (even the USB problem).
I flashed the stock WM6.1 ROM one hour before my first post. Everything is fine except for the annoying old Start Menu and the small, non-finger-friendly buttons!
I'll try the "hidden" official ROM now, just in case. I just don't know how I'll survive without WM6.5.x until after the official release date!
Thanks! I'll need the luck.
...So I think after all the testing I've done, and the weird problems others have posted [in various threads], I believe the problems I've experienced were a result of the new Sense2.5 build 1922 ROMs.
I just flashed the old EnergyROM Dec.4 Leo 28008 (Sense2.5 build 1921) and the problems are no longer present.
Newbie to WM!!!
Having similar Problems with my TP2. My phone has had several "wake up" probs since I have the phone. I installed directly after purchasing the WM 6.5 ROM directly from HTC-support (german). My real problems are right now that my alarm clock is not working properly (sometimes it works, sometimes not) and my phone often does not wake up after stand-by. Last night watched the clock at 04:30 and almost got problems caused by a non working alarm clock... (phone was connected to power supply)
anyone knows more about it? Is it a bug? user faults?
additional added software: Brians Task bar, Mort-player and powerbutton 12.
Just wanna get sure, that the phone is not damaged from hardware's site (warranty)...
Well.. I have (in this days) this problem.. It seems that it's getting worst day by day.
First of all: I've never used a "cooked" rom!
I had the original HTC rom (6.1).
I had this problem so I flashed the 6.5 update and it magically was solved!
Everithing was fine till 4-5 days ago: I can't understand what is the problem..
But I had only one time an "alarm problem".. But maybe was my fault..
I don't know what is the problem but it is NOT related to "cooked rom".
The worst thing is that RADIO MODULE IS ON!
So people call you, write you.. AND THEY KNOW YOUR PHONE IS ON!!!!!
This is totally unacceptable!!!
I would try a coked ROM.. But, as I can read, it would be useless..
And anyway: What is the most STABLE ROM in this jungle?
I'll write to italian HTC support.. I don't know if they will solve anything..
To: chrizz.o and DJ Palmis
chrizz.o: The alarm clock in WM is unreliable sometimes. You could download a 3rd party app alarm clock like Klaxon or G-Alarm.
DJ Palmis: You could also download an alarm app (see my response to chrizz.o). I don't know if you're talking about you can't turn your screen on after it goes into standby (my problem).
I don't know if you guys are confused but my problem is: I can't turn on the screen if the phone goes in standby (screen goes off). The phone is still on, but the screen is permanently off. This only happens to me in the new custom Leo ROMs. It doesn't happen in stock ROMs or old custom ROMs, so I cannot return it.
DJ Palmis, I don't know why it's happening in a stock ROM. You can try a hard-reset (wipe device) by pressing/holding Power button, Talk/Send key, and End key at the same time when the phone is off. That might help. If it doesn't, return it to HTC.
BTW, I think the most stable ROMs are the EnergyROMs, ValkyrieROMs, and the Rhodium_AF (ark666) ROMs.
Same issue w Att Tilt 2
I'm experiencing the same issue, occasionally the screen won't come on from standby when I know the phone is on. It shipped with 6.5 and it remains with the stock rom.
The issue is so hit-&-miss that it is difficult/impossible to trouble shoot.
sumflipnol said:
chrizz.o:I don't know if you guys are confused but my problem is: I can't turn on the screen if the phone goes in standby (screen goes off). The phone is still on, but the screen is permanently off. This only happens to me in the new custom Leo ROMs. It doesn't happen in stock ROMs or old custom ROMs, so I cannot return it.
Click to expand...
Click to collapse
I think we have the same problem, indeed. And i don't want to hard reset because i did not change anything in the last weeks.. I'm only using my phone more frequently.. So more text messages, videocall and so on..
But this does not justify this problem.
It would be nice to know what happens during this "freeze".
Maybe it is related to notification queue (that's why a new rom "solves" problem for a while)?
Well.. Anyway I had this problem on my old HTC Universal.. So it is related to WinMobile or Qualcom..
when i had a issue similar to that. i just hard reset my touch pro and flashed a whole new rom. and hard resetted again and i was bug and error free.
charlieb620 said:
when i had a issue similar to that. i just hard reset my touch pro and flashed a whole new rom. and hard resetted again and i was bug and error free.
Click to expand...
Click to collapse
The OPs issue must be a little different.
He tried flashing several different roms -- stock and custom -- and only the stock T-MoUSA WM6.1 or WM6.5 roms or custom roms that were a month or two old would stay "fixed".
sumflipnol said:
chrizz.o: The alarm clock in WM is unreliable sometimes. You could download a 3rd party app alarm clock like Klaxon or G-Alarm.
Click to expand...
Click to collapse
Cheers for upadating me. Appreciate it. Will try another alarm clock in a while. BUT: I use mort's player as an additional "alarm", as well, and even that does not work propperly. Might be, that it is no real alarm clock. strange and weird.
But it is good to know, that the "will-not-wake-up" problems are more or less known by several other users. I almost thought it is my stupidity to use a win mobile phone *lol*
Does anybody know, eventually, if there's a more stable rom (maybe with the new manila like on HD2) for germany which might solve the freezing problem?
thxx for updates
I'm also getting will not wake problems on the leaked official TmoUS WM 6.5 Rom. I would get it about twice a day. My stock tmobile US 6.1 never had this issue.
A fix that works for me:
Change the power settings to always on for a like 10 minutes and put the default settings back. You would have to do this after every soft reboot.
HTC Italy told me to set Band selection to auto (booth choices) and to change network selection (auto if set to manual or manual if auto) and then they told me to soft reset by button.
I'll write you if I have news.. But i think they know something more than us about this problem. And they are on the way of solving because i noticed that this problem happens in bad quality signal areas and ALWAYS when phone is ON.. So it is related to radio module.
I think it may be related to SIM card, too.
Because they told me to change SIM.. And at last to do an Hard Reset..
Maybe my 3 card is not fully compatible with my radio version?
Hey,
thxx for the updates. Indeed, I have quality differences in our flat, bandwidth switching between HSDPA, 3G and GPRS, depends on, in which room I am.
Asking HTC Germany about this problem, they told me, it is a not known issue. The more I follow up here, I cannot believe that.
Do you really think, it may also be caused by the SIM-card? Mine is about 2 years old (VF GER).
chrizz.o said:
Do you really think, it may also be caused by the SIM-card? Mine is about 2 years old (VF GER).
Click to expand...
Click to collapse
Mine too!
What I know is that i had this problem on my old HTC Universal... So maybe problem is not in the "age" of SIM card.. But in some technical compatibility between SIM and Qualcom.. (You know: 64 KB, 128KB and so on..).
Maybe Qualcom has some problem on european SIM card? I don't know..
DJ Palmis said:
I think it may be related to SIM card, too.
Because they told me to change SIM.. And at last to do an Hard Reset..
Maybe my 3 card is not fully compatible with my radio version?
Click to expand...
Click to collapse
I read somewhere in a ROM thread (I don't remember exactly where) that some people are experiencing constant freezing on their phones after a few weeks of use. Someone recommended taking out the SD card because it might be corrupt, and that interferes with the phone's performance. Some people said it worked; they found out their SD cards were actually corrupt, and using a new one made the phone function well.
Having used ValkyrieROMs before, I remember a pre-installed app (I forgot the name) that let you format your SD card. When I tried it (even after I formatted my SD card to FAT32 on my PC), the app said my SD card was corrupt and cannot be located. The last time I used the app was 1+ months ago. I think I'll try to flash a ROM without the SD card when I have time.
...But I still don't know how the SD card would give me a problem with a (new) ROM that I had on my phone for 2 weeks...and no problem on an older ROM (that I have now)...
sumflipnol said:
SD card because it might be corrupt,
Click to expand...
Click to collapse
Well I don't know, What I can say you is that till now i have no problem with HTC istructions.. Maybe i solved.. I hope..
SOLUTION!!!
I finally got my phone working with new ROMs again!
It was the SD card! I connected my TP2 to the PC as a "Disk Drive" and I went to My Computer > [right click] Removable Storage (SD card) > Properties > Tools > fix... something something (I can't remember exact words). It fixed the corrupt SDHC card I have; now my phone is working again!
This might help you, too, DJ Palmis...
Just had done this right before the last freezing-problem. My SD-card was not corrupt, so this did not solve my problem.
At least I swapped my SIM-card, made another hardreset and checked my SD-card again. Let's see what's happening...
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!
after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys
i noticed the same thing...i had to reboot the phone few times...
Same issue here!
You can wait till christmas, but nothing works to get your keyboard back..except booting..
Yes same issue here. I've mentioned it not long after the Developer Edition received the OTA.
It's not even something that we can recreate, it's just completely random. It stays that way until a reboot and then it's fine again. Very irritating.
try to clear data in app settings, that work for me :/ 4 days no problems
vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
do other keyboards work?
vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
not an expert here; can you explain how/where/what?
Donky1973 said:
not an expert here; can you explain how/where/what?
Click to expand...
Click to collapse
go to ;
settings-apps-all-htc sense input- clear data
mxisme said:
do other keyboards work?
Click to expand...
Click to collapse
They've never worked for me... unfortunately.
vahica said:
go to ;
settings-apps-all-htc sense input- clear data
Click to expand...
Click to collapse
ah...the sense-input thing...makes sense...thanx!
No problems here.
Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..
Donky1973 said:
Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..
Click to expand...
Click to collapse
Hello, the same problem with the keyboard .On any firmware, I have 6 different firmware problem persists.
p . s . TEL Verizon
Still having this damn problem.. Anyone know if it's isolated to Verizon phones? I'm on Verizon 5.0.1 stock, both the HTC and Google keyboard do it. Completely random, about once every day to 2-3 days. So annoying.
I'm having trouble with my HTC one M8
vahica said:
after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys
Click to expand...
Click to collapse
I had a problem with the keyboard lagging which got worse after the lollipop update, I was considering a warranty claim or rooting the phone and then the microphone packed in and the decision was made, I called the network who advised me to send it to HTC for repair which I did, it also had a few sync problems too, I asked the technical support guy about this problem and he said it would have to be reflashed, I sent it to them and they did the work, replacement microphones, replacement receiver, replacement lower board, replacement rubber something or other which I was told is something under the screen, replacement camera and a few others and of course it was flashed, I got it back after 8 days expecting my otherwise brilliant phone to be as it should be as I have come to expect from HTC, I switched it on and did the initial stages of making it work, I let it restore the last backup I made (off the phone with faults) which reported had failed but it started to restore the backed up apps, settings and my contacts, everything restored to how I had it before minus a couple of apps and a few notification settings, I have been using it for 2 days now however the keyboard has not been fixed by flashing it, unless the errors could have been brought in by the restoration? I have experienced the screen freeze and start jumping, jumping to the all open apps page, keyboard lag, keyboard is inaccurate, I went into the EE shop and they said that it should go back to HTC again, I haven't tried to hard reset it and go back to the factory settings and not restore the backup image this time, I've never had any problems with the 3 HTC phones I've owned, it is a good phone otherwise
Damn, I just went back to Dev Edition and sure enough it happened to me. Has this ever been fixed? This is way too annoying for me.
Possible Fix
For what it's worth, I went into App Manager to clear the Sense Input data as suggested by a previous poster (thank you) but did not have a 'Clear Data' button. There was a 'Settings' button though where I was able to turn off HTC Sense Input, after which my Swype keyboard immediately started working again. First time I've been able to resolve this SUPER annoying issue without rebooting the phone. Time will tell if it's a real fix; I'll update this post if not.
Phone is a brand new M8, still on stock 5.0.1
I randomly realized my G4 wasn't rotating the screen anymore and I have since tried everything - factory resetting, calibrating the sensor (doesn't work) and even the banging phone on table method, none are successful.
This may indicate that it is a hardware issue but if I hold the phone landscape and open the camera the buttons do rotate, but if I rotate whilst already inside the app nothing changes so I'm not exactly sure what is going on. When I use the app CPU-Z to track the accelerometer value it stays static until I turn the screen off and move the phone a bit, when I turn it on the value changes again but stays still.
Any idea what the cause is??
does booting into safe mode make any difference (i know you said factory reset, but I'm curious).
Also, probably won't, but is there any difference whilst the phone is charging?
Throwing this out there. Did you debloat? On the Samsung models, if you uninstall the Hub app, rotation gets broken for some weird reason. I don't know what that would be on the G4, but maybe? Just a random guess.
lawrence750 said:
does booting into safe mode make any difference (i know you said factory reset, but I'm curious).
Also, probably won't, but is there any difference whilst the phone is charging?
Click to expand...
Click to collapse
I'll try booting into safe mode, and there's no difference while charging.
pre4speed said:
Throwing this out there. Did you debloat? On the Samsung models, if you uninstall the Hub app, rotation gets broken for some weird reason. I don't know what that would be on the G4, but maybe? Just a random guess.
Click to expand...
Click to collapse
I believe I did remove a few apps but since I factory reset and flashed a fresh image I believe they should be restored?
wilfred888 said:
I'll try booting into safe mode, and there's no difference while charging.
I believe I did remove a few apps but since I factory reset and flashed a fresh image I believe they should be restored?
Click to expand...
Click to collapse
Not necessarily. I know a factory reset doesn't restore any previously removed apps, and flashing factory a fresh image depends on how it's flashed I've discovered. Only a CSC restores the phone to factory specs, while other methods didn't for me.
pre4speed said:
Not necessarily. I know a factory reset doesn't restore any previously removed apps, and flashing factory a fresh image depends on how it's flashed I've discovered. Only a CSC restores the phone to factory specs, while other methods didn't for me.
Click to expand...
Click to collapse
Safe mode didn't help, and I actually don't know which ones I removed but they looked pretty normal, how do I check or compare vs stock?
wilfred888 said:
Safe mode didn't help, and I actually don't know which ones I removed but they looked pretty normal, how do I check or compare vs stock?
Click to expand...
Click to collapse
I think I recall seeing a debloat list somewhere. See if you can find it and compare what you've got. I'm not saying this is the problem, but it could be.
pre4speed said:
I think I recall seeing a debloat list somewhere. See if you can find it and compare what you've got. I'm not saying this is the problem, but it could be.
Click to expand...
Click to collapse
Yeah I found a few lists but they only have apps that are safe to remove and don't warn or mention possible ones that cause problems which I may have already removed
wilfred888 said:
I randomly realized my G4 wasn't rotating the screen anymore and I have since tried everything - factory resetting, calibrating the sensor (doesn't work) and even the banging phone on table method, none are successful.
This may indicate that it is a hardware issue but if I hold the phone landscape and open the camera the buttons do rotate, but if I rotate whilst already inside the app nothing changes so I'm not exactly sure what is going on. When I use the app CPU-Z to track the accelerometer value it stays static until I turn the screen off and move the phone a bit, when I turn it on the value changes again but stays still.
Any idea what the cause is??
Click to expand...
Click to collapse
I had the exact problem a few weeks ago, thought my hardware was already flaking. Don't remember what I did to get it working, but it wasn't overly complex.. Rebooting didn't help, I think I pulled the battery, waited a bit, and then rebooted and then went to calibration from there.
Do you happen to have xposed installed by the way?
Sent from my LG-H812 using XDA Free mobile app
strikelight said:
I had the exact problem a few weeks ago, thought my hardware was already flaking. Don't remember what I did to get it working, but it wasn't overly complex.. Rebooting didn't help, I think I pulled the battery, waited a bit, and then rebooted and then went to calibration from there.
Do you happen to have xposed installed by the way?
Sent from my LG-H812 using XDA Free mobile app
Click to expand...
Click to collapse
Hey thanks for your reply, I am trying now the battery pulling method, did you then calibrate through the sensor in display settings?
And yeah I do, hmm not sure if it stopped working after that actually.. but I remember after I flashed a fresh .kdz even without xposed it still doesn't work.
wilfred888 said:
Hey thanks for your reply, I am trying now the battery pulling method, did you then calibrate through the sensor in display settings?
And yeah I do, hmm not sure if it stopped working after that actually.. but I remember after I flashed a fresh .kdz even without xposed it still doesn't work.
Click to expand...
Click to collapse
Yea would have been the calibration from the regular settings.
As for xposed, flashing a kdz will keep user data and settings.. It might have been gravitybox causing the issue for me, which if you uninstall that, reboot and reinstall it, might help. Same goes for any other modules you had enabled.
Sent from my LG-H812 using XDA Free mobile app
strikelight said:
Yea would have been the calibration from the regular settings.
As for xposed, flashing a kdz will keep user data and settings.. It might have been gravitybox causing the issue for me, which if you uninstall that, reboot and reinstall it, might help. Same goes for any other modules you had enabled.
Sent from my LG-H812 using XDA Free mobile app
Click to expand...
Click to collapse
Oh yeah it did but I factory reset as well so... I never installed gravitybox since I heard there were some problems with it but I'll see if there are any modules causing issues.
Silly question: Have you tried clicking the rotation icon in the pull-down notifications bar?
alamo76 said:
Silly question: Have you tried clicking the rotation icon in the pull-down notifications bar?
Click to expand...
Click to collapse
Yeah I have I don't even know there are signs that point towards it being a hardware or a software issue tbh.
Problem happened to me too. Started yesterday, sometimes worked, sometimes stuck on portrait.
Shutting down and pulling the battery for a few seconds seems to do the trick. It works properly now..
Have you been used apps which could calibrate the accelerometer before?
etc. some games that needs to be controlled by rotating the phone on its axis..
onotor said:
Have you been used apps which could calibrate the accelerometer before?
etc. some games that needs to be controlled by rotating the phone on its axis..
Click to expand...
Click to collapse
Me? Not that I know. Some new apps yes, but still proper screen rotation.
This problem happened on my g4 today...
Stock ROM?
LG 4 not rotating??
quick fix which worked for me was just take the battery out, wait 30 seconds, put back in switch on and problem solved...
hope this helps guys.... regards Steve
Hi guys,
Im here to speak about my mi 10t who got some sound/mic issue.
Everything was working good but one day, the phone muted himself on stock Rom.
When i tried to use the tap recorder, the app said "verify if an app is using the microphone an try again."
I try to put a Custom rom on it but it's the same with Lineage Os.
Now, internal and external speaker stoped working. Microphone too.
the bluetooth connect well to a device but when i play a song, no sound happen.
Even on twitter or reddit, when i tried to play a video its say, Error to load the video.
When i tried to call someone, the app close immediately
I can only send sms and read them.
Please helps
Hello,
I have the same problem just like you 1 month now,tried everything , even install custom ROMS but the problem remains.
Did you drop your phone down? I cant remember that i did , but if i shake my 10T pro near my ears i can hear that something is moving inside my device.
The temporary fix that i had was to reboot many times my device and reopen it , clear the data from phone services , but couldnt find any permanent fix though.
Does anyone else has this?
glixbourkt said:
Hello,
I have the same problem just like you 1 month now,tried everything , even install custom ROMS but the problem remains.
Did you drop your phone down? I cant remember that i did , but if i shake my 10T pro near my ears i can hear that something is moving inside my device.
The temporary fix that i had was to reboot many times my device and reopen it , clear the data from phone services , but couldnt find any permanent fix though.
Does anyone else has this?
Click to expand...
Click to collapse
Hey!
I am running lineage and the problem is still there !
Ahah, a friend just remember me that i threw a whole beer on it during a party like 3 months ago..
I totaly forgot that and i think i was too drunk to remember.. unfortunately!
But the phone is like new and nothing is moving inside
Yes if i reboot/wipe data 363637x time it has a chance to work but the problem come back fast
I use a second phone where i put my sim on it and play with the mi10
It's sad because that 144hz screen is fkin good
And i still can't Say if it's a software or an hardware bug.
Because if i open the phone, change the internal/external speaker for nothing i will be a bit pissed
But still a good phone even muted aha
Shlagito said:
Hey!
I am running lineage and the problem is still there !
Ahah, a friend just remember me that i threw a whole beer on it during a party like 3 months ago..
I totaly forgot that and i think i was too drunk to remember.. unfortunately!
But the phone is like new and nothing is moving inside
Yes if i reboot/wipe data 363637x time it has a chance to work but the problem come back fast
I use a second phone where i put my sim on it and play with the mi10
It's sad because that 144hz screen is fkin good
And i still can't Say if it's a software or an hardware bug.
Because if i open the phone, change the internal/external speaker for nothing i will be a bit pissed
But still a good phone even muted aha
Click to expand...
Click to collapse
Hey,
Thanks for the answer.
I had a similar accident as well . My question though is what causes the sound issue. if i try to reboot/wipe this (which i dont want to wipe all my data every week ) there is a change also for me to work.
Do you have any idea how can i fix this ? should i give it to somebody who can open it for me as its a hardware issue?
I have the same problem, has anyone found the solution?
glixbourkt said:
Hello,
I have the same problem just like you 1 month now,tried everything , even install custom ROMS but the problem remains.
Did you drop your phone down? I cant remember that i did , but if i shake my 10T pro near my ears i can hear that something is moving inside my device.
The temporary fix that i had was to reboot many times my device and reopen it , clear the data from phone services , but couldnt find any permanent fix though.
Does anyone else has this?
Click to expand...
Click to collapse
Entirely unrelated to the issue, but just to calm some folks
The Mi 10T Pro model rattles because the camera has OIS (the camera module itself moves). This can also give a slight rattling effect when playing very loud music
Don't worry about it
Dobsgw said:
Entirely unrelated to the issue, but just to calm some folks
The Mi 10T Pro model rattles because the camera has OIS (the camera module itself moves). This can also give a slight rattling effect when playing very loud music
Don't worry about it
Click to expand...
Click to collapse
Yes i found it out as i opened myself the phone with no luck fixing it.
Its now somewhere collecting dust 3-4 months now. Cant fix it....
if anyone has any solution or any idea just let us know.
Lhpmira said:
I have the same problem, has anyone found the solution?
Click to expand...
Click to collapse
Try to open the phone x50 times and dont let it close again....This is the only way that i found out , but cant/ dont have the time to switch it off x50 times.
same problem here...
i've dropped my phone one time and after that, no sound at all.
the assistance shop said that all the components were good, but the problem remains
my last try was to flash the xiaomi stock rom, but no results
Had a similar issue.
Even multiple factory resets also didn't help.
However tried another sim and did a reset and it was working fine.
Now then after few days it again happened
Now this time I probably understood what was triggering the issue. I had paired my headphones(Bluedio Turbine) with both my laptop and phone. Using one at a time it was working fine. However if there's a call from both laptop and phone then the phone went into this state.
Again tried resetting multiple times. This time tried replacing the sim with a different sim. Different from the one in previous attempt and the sim change trick also did not work. Then tried again with the same sim which had fixed it earlier and it worked.
So in short these are the steps that helped me. Seems like only sim might have worked however don't know for sure.
Take proper backup of your data. Also this may or may not work for you.
Factory reset from settings.
Shutdown phone.
Press volume up and power button and hold them for some time till the phone starts up.
Use power button and volume key to wipe data.
I did this 3-4 however I think so it is t required.
Replace your sim with another sim. I had replaced my Airtel sim with a different Airtel sim and it worked for me. However replacing Airtel with jio did not help.
Start the phone.
Setup the phone.
Phone might start behaving fine.
CameraPhone123 said:
Had a similar issue.
Even multiple factory resets also didn't help.
However tried another sim and did a reset and it was working fine.
Now then after few days it again happened
Now this time I probably understood what was triggering the issue. I had paired my headphones(Bluedio Turbine) with both my laptop and phone. Using one at a time it was working fine. However if there's a call from both laptop and phone then the phone went into this state.
Again tried resetting multiple times. This time tried replacing the sim with a different sim. Different from the one in previous attempt and the sim change trick also did not work. Then tried again with the same sim which had fixed it earlier and it worked.
So in short these are the steps that helped me. Seems like only sim might have worked however don't know for sure.
Take proper backup of your data. Also this may or may not work for you.
Factory reset from settings.
Shutdown phone.
Press volume up and power button and hold them for some time till the phone starts up.
Use power button and volume key to wipe data.
I did this 3-4 however I think so it is t required.
Replace your sim with another sim. I had replaced my Airtel sim with a different Airtel sim and it worked for me. However replacing Airtel with jio did not help.
Start the phone.
Setup the phone.
Phone might start behaving fine.
Click to expand...
Click to collapse
Ignore this. This again happened after the last fix. Now again I can not use the mic. In CIT check if I try to test any of the mics, top or main the app crashes. Seems to be related to the mic. However don't understand how come event Bluetooth calls fail.
Another thing that I tried was putting the phone in refrigerator for around 10-15 mins. The phone was switched off before being put in the refrigerator. It generally works after that.
However it is generally good only till a restart.
Try at your own risk.
Must be something to do with the firmware only. And problem seem to be happening at the time of a reboot. Right at the time when MIUI logo appears during a reboot, if you dont hear the bootup sound, then the system audio wont work.
What fixes for me is multiple reboots until you hear the bootup sound. Most of the time, it takes just a couple of reboot. Max it has taken for me is 7.
Problem with loading of audio driver?!
Hi all,
Is there any update on that issue ? I still have that phone doing nothing at the moment. So i was wondering if there is any chance to use it.
I have the same problem.
Abdu55799 said:
I have the same problem.
Click to expand...
Click to collapse
New Mi10T Pro - No Sound at all
Brand new device. Flashed custom OS (Arrow OS and google pixel)- no sound at all. No Youtube sounds, no call sounds, no media sounds, even Bluetooth, even with headphones. Phone are silent absolutely. Please help. Thanks in advance, guys!
forum.xda-developers.com
you may find a solution there.
I still have the error
Still same problem here. I even updated to a custom rom, but no difference. Even sound via bluetooth does not work nor sound via USB.
Anyone has a theory how that could happen?