Hey,
So I've got an HTC Desire 816 running PAC-Rom (4.4.4).
Yesterday while I was using it normally, Whatsapp shows up and asks me to enter my phone number to register it, acting as if it's just been installed on the phone. I had already activated whatsapp previously, so I've no idea what that was about. Before I could react, however, the phone randomly rebooted.
While booting, it suddenly asks me for a password to decrypt my phone. However, I had never encrypted it in the first place. So I just reflashed my ROM without wiping anything and then it worked fine.
However, this morning, I when I tried to place a call, what happens is, as soon as I hit the call button, the screen goes black. I can still see and interact with the navigation and status bars, but the call screen remains black. If I try to go into quick settings, the phone freezes and the only thing I can do it turn the screen off. After that, it doesn't respond for a while, and then finally, it shows the call screen for a split second before displaying the lock screen. when I unlock it, it's as if I had never placed the call at all. The other phone I called had never recieved the call.
When I use another phone to call my phone, My phone does not recieve it at all, while on the test phone making the call, it rings for a while and then says "Call disconnected".
I've tried swapping out SIM cards,factory resetting, clearing cache and dalvik cache, wiping and disabling the dialer app and flashing another ROM, but none of hat works.
I'd love to hear suggestions from you guys
Also, as a side note: All my music which I've stored on my SD card cannot be played by any music player. DSP manager crashes when I attempt to play any song, and then the music player throws up an error
Thanks.
XDA Visitor said:
Hey,
So I've got an HTC Desire 816 running PAC-Rom (4.4.4).
Yesterday while I was using it normally, Whatsapp shows up and asks me to enter my phone number to register it, acting as if it's just been installed on the phone. I had already activated whatsapp previously, so I've no idea what that was about. Before I could react, however, the phone randomly rebooted.
While booting, it suddenly asks me for a password to decrypt my phone. However, I had never encrypted it in the first place. So I just reflashed my ROM without wiping anything and then it worked fine.
However, this morning, I when I tried to place a call, what happens is, as soon as I hit the call button, the screen goes black. I can still see and interact with the navigation and status bars, but the call screen remains black. If I try to go into quick settings, the phone freezes and the only thing I can do it turn the screen off. After that, it doesn't respond for a while, and then finally, it shows the call screen for a split second before displaying the lock screen. when I unlock it, it's as if I had never placed the call at all. The other phone I called had never recieved the call.
When I use another phone to call my phone, My phone does not recieve it at all, while on the test phone making the call, it rings for a while and then says "Call disconnected".
I've tried swapping out SIM cards,factory resetting, clearing cache and dalvik cache, wiping and disabling the dialer app and flashing another ROM, but none of hat works.
I'd love to hear suggestions from you guys
Also, as a side note: All my music which I've stored on my SD card cannot be played by any music player. DSP manager crashes when I attempt to play any song, and then the music player throws up an error
Thanks.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Memory errors maybe, if a reflashed ROM (especially if a clean flash) produces the same result. Try going back to stock to see if the problem continues.
At any rate, I am connecting you to the forum your device experts can be found:
> HTC Desire 816 > Desire 816 Q&A, Help & Troubleshooting
Please note, to respond to any replies, you will need to register for an XDA account.
Hope this helps, and good luck!
Related
Hello there!
All of a sudden I have encountered this really weird problem.
- My phone ran out of battery and turned off during the night
- I charged it and turned back on
- It didn't ask the PIN code
- I can't make a call now, it says Not registered on the network.
But what the most interesting is, that if the SIM card is in the phone the home button doesn't work properly. When I press it the screen flashes once and nothing else happens, it won't go back to the home screen. (S Voice works with the double press though. I tried turning S Voice of in case it makes the problem but didn't help...)
Without the SIM card the phone works perfectly.
The SIM card works in another phone.
Any ideas about what might cause the problem?
Thanks and regard,
~rob
Sometimes there is data loss due to power going off instantaneously. I am saying that by experience.
Try doing a factory reset.
Sent from my GT-N7100 using xda premium
I performed a clean reinstall of the ROM and it solved the problem, thanks
Hi there,
i couldn't find my problem already discussed via the board search, so i'm posting it here. i hope this is the right board, if not please relocate.
i'm using the find7a since about 1 year now. the only updates i did for colorOS were the ones that have been proposed automatically via the popups. but these i did every time.
i have alwas had several issues with the phone/os, mostly random shutdowns without any reason. but at some point, these shutdowns suddenly declined and i got used to live with the few that still occur from time to time. but now i have a much bigger problem and i don't know where it came from:
few days ago, i got the popup that a new os-update was available. i had a little time so i did it instantly. without any problems the update was installed and after that the phone booted as always and nothing strange happened. 1 day later i recognized that something had changed. i wasn't able to turn on the wifi anymore! same goes for the bluetooth. also the automatic screen rotation (when you turn the phone in a right angle) didn't work anymore! but all of them DID work for the 1 day since i made the last update. so i assumed it has nothing to do with the new os-version (which is 1.2.9 btw). i didn't change anything in the phones settings, everything was the same. but from one moment to the other these three problems suddenly came up. maybe even more that i didn't recognize yet.
although everything worked fine for 1 day since the update, i thought maybe the update could be the problem after all. so i wanted to flash another version of colorOS. i tried the 2.0.8i which was considered stable by the official oppo board admins on friday. the flashing worked fine, colorOS 2.0.8i booted, but the problems remained! still no wifi, no bluetooth, no screen rotation.
next thing i thought: maybe it's a hardware problem. so i flashed another ROM (always making a factory reset + wiping all cashes and data from the internal storage first), i tried a few. they were all flashed successfull but most of them hung up during the first boot sequence (cyanogenmod, paranoid, nameless), i always got stuck in the loading screen. last one i tried was OMNI ROM, and this one finally worked, meaning i got it started. first thing i did was checking the wifi connection and what do you know? the wifi worked just fine, my home network was found immediately und the connection went all good! which means a hardware defect should be out of the question.
this brings me back to thinking the problem lies within colorOS. which would be very sad becaue i really like colorOS and i would like to keep using it!
reproduction of the issues:
to reproduce the problems, when you are on the home screen you simply have to drag down the shortcut-menu. then tap on "wifi" and watch the symbol turn into the one for "loading" (the circling line). and then: nothing happens. the loading symbol just keeps on circling on and on. when you slide the menu up and down again, the normal "wifi-off" symbol shows and wifi is not turned on.
almost the same goes for the bluetooth. only when you tap this icon, the loading animation stops after a few seconds und the "bluetooth-off" icon appers again, this time without sliding the menu up and down. bluetooth stays turned off anyway.
for the rotation problem you just need to got to an app, where you can type in some text, f.e. whatsapp or gmail. tap the message area to make the keyboard and the cursor appear and then turn the phone from vertical to horizontal. normally the display should rotate automatically, but it doesn't it just stays in the vertical view mode. of course the rotation ist activated all the time, so no need to advice that
the rotation problem does not only occur when trying to type sth. in but also when i want to watch videos (f.e. with the vlc player app). the video stays locked in the vertical mode, making the image very small of course. this is also very annoying!
so, what do you think could be the reason for my problems? and what could i do to solve them? i hope you can help me.
i attached a log-file which hopefully shows the bugs.
my current specs are:
find 7a
colorOS 1.2.9
TWRP 2.8.6.0
greetings
tim
Phone info: LG G3, model D852
ROM: fresh install of XenonHD, 09-28-15 build for the D852
http://forum.xda-developers.com/lg-g3/development/official-xenonhd-5-1-stable-t3167293
ROM was installed fresh: wiped Dalvik, cache, system, data. Flashed ROM via TWRP, then TKGapps (09-27 release, 'stock' package), first boot took a while as expected, but went without issue. Installed a few 'normal' apps (no xposed or anything like that), and used Titanium backup to forcibly uninstall AdAway and Messenger.
PROBLEM:
Use the stock dialler to make a phone call to an existing contact. As soon as I hit the phone icon on the contact, the call initiates, and the screen goes black immediately. I can hear the call connecting, but it is extremely hard/impossible to turn the screen on: tapping the screen, clicking the power button, shaking the phone all fail to turn the screen on. If any of this does get the screen to turn on, it just flashes very briefly (showing the call in progress) and then goes black again. Once the call wraps up, the screen is immediately responsive once again.
Has anyone else have ever run into such a problem?! And of course, any suggestions on potential fixes or troubleshooting would be appreciated.
Thank you.
I think that's a problem with AOSP as a whole
I know for a fact that alot of people on the CM12 thread for LG G3 talk about the same problem as well
Hey all,
I have searched the web, but most of the info I found relates to the screen going black during calls, which isn't the problem I'm having. My screen is actually fine during/after calls.
This is happening to me randomly and is just the home screen. The lock screen and notifications are still visible when this problem occurs.
I can randomly press the screen hoping to hit an app and they open fine. Sometimes when I back out of the app, the homescreen returns to normal although it can take a few goes, sometimes I have to restart the phone. It isn't happening all the time, in fact before today the last time it happened was Wednesday. I'm just worried that it will become more frequent and as is stands I am still under the 30 days in which I can return the phone for a refund.
I was using Go Launcher Z, although I have returned to the default launcher in case that's what the problem is. Phone has all updates installed, is on 5.1 with the build number LMY47D.
I cannot boot into recovery mode to wipe the cache partition, I must have tried about 30 times. Majority of time the phone just turns on, a couple of times it came up with the option to do a factory reset.
Would appreciate any help
OK, I was with stock ROM, rooted only for use Samba File Share (I used this app for so many years on my old SII, I really like it) and was everything normal, until today, I opened the Facebook Messenger App, to send a message, and took a photo from my cat, then I received a Whatsapp message at the same time, I was aiming the camera, and the screen blinked for a sec, and the phone "freezes" - it was still showing the camera normal, but unresponsive to commands, I waited for 5 minutes, and then I forced reboot holding power + volume, and it restarted, the vib motor got stuck on, and Asus logo screen "booting" for many minutes, I waited until it restart it self again - this time everything loaded up normally - When I go to the main screen, I noticed that Messenger app was without Icon, with a SD card icon, like it was unloaded, I opened the Chrome for search, tried to reinstall the app, returned a error when installing, back to chrome, searching about it, and then the phone freezes again, crash Chrome, everything starts to crash, Google services, background services, everything, I was forced to restart - and then I got boot loop.
[email protected]%!, I tried to wipe cache, and nothing changed, so I did a wipe data, and the phone recovered fine (I think) still here installing apps, but now I'm worried. It was a random error, or maybe it will occur again? Could it be consequence from rooting? I'm on stock ROM, Lollipop 5.0 I think, could be a bug from this ROM?
Edit: I just checked, the phone still rooted even after wipe
Edit 2: I was thinking on a theory, I work with computer, repair etc, Ive seen this happening on notes.. I was thinking if the issue could be related to power problem. Like, the battery was 90% I think, but the screen was full bright, and I was using camera, and Messenger, and then I received a message on whatsapp, the screen blinked - maybe the power "failed" on the phone, and some process on background, on low level, got corrupted and it just got worse after phone processing it on background? Maybe? I dont know if it makes sense, maybe dont (?) haha