Hi,
I have a MTCD-KGL for over an year now. The only issue I have with the device is that after power up, sometimes, not always it freezes after start.
Precisely:
- This happens once every 2-3 boots
- This happens regardless if it does a real power up or wakes after a sleep
- The freeze usually happens 10-15 seconds after startup, however sometimes it might happen immediately or take up to 3-5 mins to freeze
- When I set it up to sleep instead of shut down (after car power off) and the radio app has been turned on before shutting down, after power up of the car and device it would usually start the radio app again and turn on the sound and freeze only after this. Same is true for my navi app (Here to go) i.e. it would start the navi app after boot and then freeze. Sometimes I'm able to make a click or two before it freezes
- If it makes cold start (i.e. had been shut down) then it shows the launcher UI
- When it's frozen I could reset it via the reset button, however I can't power it off via the power button
- When it's frozen, the touch screen doesn't respond at all, while hardware buttons only make beeping sound. However nothing changes, no matter what button I press. Turning the volume knob makes multiple beeps, however the volume doesn't change. Pressing back, home or anything else also makes beep but no effect
- Shifting to reverse doesn't show the revers comer either
I have updated to numerous different firmwares, both KGL and others as well numerous KGL MCUs, however with all combinations the problem persists.
The device is not rooted yet, I could do it if it would be from any help.
Any idea? I don't know what might be causing this freeze, which is keeping the last snapshot on the screen and buttons beep, radio plays, but nothing else happens. Apparently it's not software problem, because updates of the firmware and the mcu would have solved it. So it should be a hardware one. Any idea where to look at?
Thanks and regards
flyzepp
flyzepp said:
Hi,
I have a MTCD-KGL for over an year now. The only issue I have with the device is that after power up, sometimes, not always it freezes after start.
Precisely:
- This happens once every 2-3 boots
- This happens regardless if it does a real power up or wakes after a sleep
- The freeze usually happens 10-15 seconds after startup, however sometimes it might happen immediately or take up to 3-5 mins to freeze
- When I set it up to sleep instead of shut down (after car power off) and the radio app has been turned on before shutting down, after power up of the car and device it would usually start the radio app again and turn on the sound and freeze only after this. Same is true for my navi app (Here to go) i.e. it would start the navi app after boot and then freeze. Sometimes I'm able to make a click or two before it freezes
- If it makes cold start (i.e. had been shut down) then it shows the launcher UI
- When it's frozen I could reset it via the reset button, however I can't power it off via the power button
flyzepp
Click to expand...
Click to collapse
Its an older unit and I would tend to think that your system is running out of memory.
I tried doing a System Update on mine but the dang head unit can't find the .img file in any slot nor usb port.
Related
Sometimes my handy randomly lock and unlock. It's like the power button gets pressed automatically. also sometimes the APM shows up, and if i press back, it appears again and again, mostly 3 times, then the system starts new.only the system. If i charge it, the screen also randomly shows lock screen and a second later it's dark again.
It's like a ninja pressing my power button to troll me.
Could it be a voltage problem? Or a battery problem?
I'm on stock battery and OrDroid 3.0.1 and this problem appears since 4 days
DesperadoX93 said:
Sometimes my handy randomly lock and unlock. It's like the power button gets pressed automatically. also sometimes the APM shows up, and if i press back, it appears again and again, mostly 3 times, then the system starts new.only the system. If i charge it, the screen also randomly shows lock screen and a second later it's dark again.
It's like a ninja pressing my power button to troll me.
Could it be a voltage problem? Or a battery problem?
I'm on stock battery and OrDroid 3.0.1 and this problem appears since 4 days
Click to expand...
Click to collapse
Hi,
Sounds more like a problem with the actual power switch to me, but perhaps the following thred will be helpful for you. I haven't read through everything, but some of the posts report similar issues.
http://forum.xda-developers.com/showthread.php?t=1235382
Good luck!
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I am finding that the sound will work fine after a restart for as long as I use the device but then, after it has gone to sleep (screen off for five seconds) all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility; what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
edit:
Oh, device info:
Boot logo shows GT-I9300T
Back cover and system info says GT-I9300
Android version 4.1.2
Baseband version I9300XXELKC
Kernel Yank555 JB 3.0.54
Build number null_10
Network: Vodafone Australia
Downloaded stock rom, problem remains
I've uploaded a log of the following, maybe someone who knows about these things can have a look for anything suspicious?
Press volume up three times (phone goes beep beep beep)
Press power button
wait three seconds
Press power button
Unlock
Volume up three times (beep beep beep)
Press power button
wait TEN seconds
Press power button
Unlock
Volume up three times (no beeps :*( )
Log is here
http://pastebin.com/guJjdTwp
Device: HTC One M8 running Liquid Smooth from may 13th.
This is rather odd - All day, my phone was working just fine. As I was listening to some music (through the speaker... or should i say speakers boomsoundhighfive:highfive, I pushed the power button to unlock the phone to text somebody, except all I could see was the music app (apollo) in the background with a dialogue saying that android system UI has stopped. Every time I hit "ok", it popped right back up. I'm assuming that that was because it was trying to restart, and it just kept crashing.
A bit later, it was still doing the same thing when all of a sudden I could no longer turn on the screen. However, my music is still playing, and I can control the volume with the vol buttons. The only other thing I can do is double tap the screen to get a bit of hepatic feedback from double tap to wake. Also, the low battery notification LED is now flashing, as it was at fairly low battery when this started (around 30, it's been about 45 minutes since this started).
I can't reboot through ADB as usb debugging isn't on, and I tried holding down the power button for about a minute with no luck.
Anybody got any advice? My current plan is to wait for it to die and hope it reboot normally... Otherwise I might boot straight into recovery and restore a nandroid...
Alright, sorry for creating this thread - it died, I plugged it in and turned it on. It appears to be completely working. Anybody know why this would happen? It seems a bit odd.
Hi, I started having the strangest issue 2 days ago. Phone model is Samsung Galaxy A50.
I have been unable to unlock my phone once I pressed the lock button or if it went to sleep (screen off).
The only way out of the issue is to restart it by pressing volume down and power for 5 seconds. I put the screen timeout to 10mins (which is the maximum). But no long term solution. Whenever the screen turns dark it stays dark. If a call comes in, the phone vibrates (or ring) but any interaction with the phone is impossible. If I play music, the music continues once the screen is off. The sound can be turned up or down, but it's the only thing that can be done.
While the screen is on, changing the volume via the buttons affects the actual volume of the music, but there is no UI indication that the volume changes, no popup nothing.
So all physical buttons are working correctly.
I have trie "reset parameters", I have tried "reset all data" (backed up everything through Smart Switch). It doesn't change a thing. The phone is reset (still on android 11 though, although I bought it on android 10...) but the issue remains.
Now something very interesting :
Just now, I setup Phone Link for windows 10, so that I am able to see and answer texts and phone calls while at the office. Which works, it sort of defeats the purpose of a "cellular" phone but well...
HOWEVER : while my phone is connected to my desktop through Phone Link. I can lock and unlock at will, change volume and see the UI pop up (via the windows interface or directly on the phone, same behaviour) It's basically fixed. I thought it was fixed for good, so I disconnected my phone from Phone Link. The screen went black as before and there was nothing I could do except reconnect it via Windows 10 (then it immediately starts behaving as usual again...).
My guess is it's definitely software. I just don't understand why a factory reset didn't do the trick...
I wanted to try and reset through the bootloader, but I never managed to effectively get into the bootloader (through volume up and power while the phone is off).
I do not recall making any updates or installing anything just before these symptoms occured. I did install a firmware update that was available after these symptoms started but to no avail
Has anybody seen this before ? Thanks in advance
It used to happen every few days, not a massive deal, but it's happened five times today. Including overnight, meaning my alarm failed to go off.
Ambient display stays on - sometimes the clock even keeps running - but none of the buttons do anything. Only escape is press and hold power until it reboots. Or, sometimes I'll be doing something on the phone and it'll just completely freeze. Again, press and hold power is all I can do. Weirder, sometimes I can click on an app, and it'll just pull up the start of the load screen for that app, I can hit home or switch apps and that acts fine, it just won't actually open any of my apps or do anything in them. Again, have to press and hold power to reboot.
Rooted, Android 12, no other modifications to the OS that I'm aware of.
koberulz said:
It used to happen every few days, not a massive deal, but it's happened five times today. Including overnight, meaning my alarm failed to go off.
Ambient display stays on - sometimes the clock even keeps running - but none of the buttons do anything. Only escape is press and hold power until it reboots. Or, sometimes I'll be doing something on the phone and it'll just completely freeze. Again, press and hold power is all I can do. Weirder, sometimes I can click on an app, and it'll just pull up the start of the load screen for that app, I can hit home or switch apps and that acts fine, it just won't actually open any of my apps or do anything in them. Again, have to press and hold power to reboot.
Rooted, Android 12, no other modifications to the OS that I'm aware of.
Click to expand...
Click to collapse
Backup all your data while you can, you may be in the beginning stages of hardware failure. Some people with the following problem had freezes before the phone failed completely.
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
If that is not your problem, completely wiping the phone and flashing a new image may help.
It's been years at this point, I'd be very surprised if it all suddenly died in a way connected to this. There's nothing on my phone that's critical that I don't have backed up, though.
Not sure if there's any way to determine if I might have or get the EDM thing?
koberulz said:
It's been years at this point, I'd be very surprised if it all suddenly died in a way connected to this. There's nothing on my phone that's critical that I don't have backed up, though.
Not sure if there's any way to determine if I might have or get the EDM thing?
Click to expand...
Click to collapse
Not until it fails.