Hi,
I have KLD6 unit. tryed some Malaysk 4.4.4 ROM and after 2 weeks of use the touch screen has started to not respond sometimes. Upgraded to Malaysk 5.1 and still the same.
Downgraded back to OEM 4.4. Was working fine for a week but now it still happening.
Sometimes restarting the unit works, sometimes not.
Sometimes I can use the unit for a while and than after some minutes of use it's not working anymore.
Physaical buttons are working fine all the time even when the touch screen isn't.
Anyone have an idea? Maybe a software issue? Incompatible app?
Thank you all
Chamuelm said:
Hi,
I have KLD6 unit. tryed some Malaysk 4.4.4 ROM and after 2 weeks of use the touch screen has started to not respond sometimes. Upgraded to Malaysk 5.1 and still the same.
Downgraded back to OEM 4.4. Was working fine for a week but now it still happening.
Sometimes restarting the unit works, sometimes not.
Sometimes I can use the unit for a while and than after some minutes of use it's not working anymore.
Physaical buttons are working fine all the time even when the touch screen isn't.
Anyone have an idea? Maybe a software issue? Incompatible app?
Thank you all
Click to expand...
Click to collapse
Happened to me. Reinstalled MCU firmware and that cured the problem... Don't ask why ROM is messing MCU but it looks like it happens... So just try flashing you original or latest MCU for your device type. Of course first carefully read info on how to do that and be sure to use right MCU for your exact HU type. And write down Factory Settings as they may be messed after MCU reflash. And final note: I would also recommend Factory Reset or Clean all data/cache after MCU flash.
pa.ko said:
Happened to me. Reinstalled MCU firmware and that cured the problem... Don't ask why ROM is messing MCU but it looks like it happens... So just try flashing you original or latest MCU for your device type. Of course first carefully read info on how to do that and be sure to use right MCU for your exact HU type. And write down Factory Settings as they may be messed after MCU reflash. And final note: I would also recommend Factory Reset or Clean all data/cache after MCU flash.
Click to expand...
Click to collapse
Hi,
Thanky you for the idea.
tried any public MCU for my HU.
2.83
2.85
2.91
Also tried couple of factory reset and wipes.
Noticed that the kernel has remaind the rooted one. Maybe that what causes the problem?
Related
So I have a slight issue... I flashed RTM Mango when it came out a month ago and the stock HTC headphone remote for volume, end call, and the microphone stopped working which is understandable since the build had no firmware, so when I flashed the stock TMOUS 7.0.7004.0 I thought they would work again, but they didn't so I started updating officially through Zune Desktop and every time it updated I checked to see if they worked and they didn't... I checked on 7.0.7008.0, 7.0.7392.0 and finally on Mango 7.1.7720.68 and they didn't work on any of them... so either I damaged my firmware permanently or something happened to the headphones (which is highly unlikely)... any help is appreciated thanks!
I had the same situation , now I lost the HSPL and not able to reintall any other rom, as far as I know there is no way to fix that , in siple words phone is "soft bricked" ....
sealexm said:
I had the same situation , now I lost the HSPL and not able to reintall any other rom, as far as I know there is no way to fix that , in siple words phone is "soft bricked" ....
Click to expand...
Click to collapse
Is there anyway for anyone at T-Mobile to pick up on something like that? I'm gonna see if warranty will cover it...
I got mine from uk handtec and been use four days without any problem
but today it reboot two times alreday without any touch.
did anyone have that kind of iusse any suggestion?
I haven't root my phone and I updated to 534 firmware
paullu said:
I got mine from uk handtec and been use four days without any problem
but today it reboot two times alreday without any touch.
did anyone have that kind of iusse any suggestion?
I haven't root my phone and I updated to 534 firmware
Click to expand...
Click to collapse
you might need to do a factory reset then update the firmware again, I think the update to 534 didn't go too well... also happened to my samsung phones preiously after updating to latest firmware...
Morlock O said:
you might need to do a factory reset then update the firmware again, I think the update to 534 didn't go too well... also happened to my samsung phones preiously after updating to latest firmware...
Click to expand...
Click to collapse
I was just about to post about the same issue. Twice now when driving I have noticed that the phone suddenly reboots. It's sitting in a passive car holder (no power, NFC, bluetooth etc). But it's just in my line of sight so I quickly notice when it suddenly boots.
I have no idea if it does this the rest of the day or not as well. But this is not a good sign.
if resetting to factory setting then re-updating the firmware does not work, try to re-flash the stock firmware using FTF files...
http://forum.xda-developers.com/showthread.php?t=2459365
http://forum.xda-developers.com/showthread.php?t=2464389
this usually happens when there is some conflict with the firmware.. very common issue with all android phones...
I'd flash it with flashtool.
I did a "reflash" of the latest firmware using the PC companion software that came with the phone. Will report back in it helped or not.
I did a factory reset.hope will solve it
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.
Hi,
with the newest builds of LineageOS for the OnePlus 3T im facing similar problems like in this post here ...
https://forum.xda-developers.com/oneplus-3t/help/lineage-os-bluetooth-crashing-op3t-t3561225
This applies both for the 20/03 and the 24/03 build. When I enter the settings and go to the Bluetooth section and there enable BT, the phone becomes unresponsive for some time and then reboots. What I found out is that if I enable BT via the status bar shortcut, everything is fine and my previously connected device (gear s2) reconnects stable. But if I then enter the settings and just click on the BT section entry, same story again, phone becomes unresponsive and then reboots. I flashed the ROM and then the OOS Firmware 4.1.0. Phone is rooted with SuperSU.
Have you tried a clean flash?
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
greg1977 said:
not yet. just dirty flashing with wipe cache and dalvik so far. i guess I'll give it a try then.
Click to expand...
Click to collapse
Report back with results plz
sakumaxp said:
Report back with results plz
Click to expand...
Click to collapse
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
greg1977 said:
I don't know what did the trick now but this is what I was trying...
I cleaned the cache + data of the Bluetooth system app and reinstalled BusyBox, then rebooted. The problem seems to be gone, no more crashes and freezing OS. Will leave it like this for me now. Just wanted to let you know as I don't seem to be the only one with this issue.
Click to expand...
Click to collapse
All,
just wanted to give an update on this topic and hope for a solution
As the problem was coming back I decided to go for a full wipe and clean flash of the latest LineageOS version for the OnePlus 3T from this thread here: https://forum.xda-developers.com/oneplus-3t/development/rom-lineageos-14-1-t3547024
After I restored my apps I activated Bluetooth on the device and flawlessly connected my Smartwatch, a Gear S2. All good, all fine, all working.
AFTER that, when entering Settings => Bluetooth on the OP3T, there are 2 possible scenarios:
1) No other Bluetooth devices are around and emitting, the search stops after a few seconds saying that "no other BT devices are detected" ... makes sense.
2) There are other Bluetooth devices around and emitting, and based on my experience only one device is sufficient. The search goes on and on and on, after a while the screen freezes, and then the phone warm resets.
I was able to reproduce this inside my car when I tried to connect to the car audio system and also with my Bluetooth headset. Devices turned off => scenario 1, devices turned on and ready to connect => scenario 2.
Any idea here?
Hello,
I have a motorola G6 that after bad root get stuck on bootloop.
I flash the phone with two roms but the phone after flash dont have sound during calls, the earpice dont work even in loudspeaker, but the phone rings when is receving calls.
anyone already have this problem?
tanks
This question is probably in the wrong section but anyway...I did. I never checked the phone prior to rooting so I'm not sure if a "bad root" was the cause or not. However, I experienced the exact same problem as you. I was originally on build OPS27.82-19-4 so I reflashed stock OPS27.82-19-4 as described here. But I still had the same problem. On a whim I randomly flashed build OPS27.82-19-4 following the same instructions. The phone has been working great ever since (I have it rooted, xposed. etc...). Not sure why there was a problem, or if reflashing the newer build "fixed" it or not...but as I said, all is good now. FWIW, when I check the sim status in settings>about phone, the network section is blank. It was blank when I had problems too.
Perhaps this will help you..
PS When I reflashed the firmware, the phone would boot into fastboot mode, then when I selected "Start" it would boot to the OS. If you run into that, here is how it was fixed. See posts 5, 6, 7, & 8.
Good luck!
I had a similar problem, I did the root, TWRP, I ended up giving up and flash again on the stock of the bike G6 Play (Brazil) available here in XDA, to my surprise, he made and received calls normally, the speaker for music and connections of other applications (Whatsapp, Messenger, Hangouts, etc.), but it did not work for the rom dialer.
I thought I had a problem, it was when a system update appeared, I installed it and it worked again.
I figured it was some rom bug I installed.
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Multiredes said:
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Click to expand...
Click to collapse
That's because a custom rom or GSI does not have all the necessary files. 99.9% of the time, flashing stock will fix a problem.