For past Three days I'm getting this Dialog window on every reboot.
It says your phone Has some internal problem. Contact your vendor.
Kindly Tell Me is this a serious problem or how to solve this issue?
Honestly - it's telling you there is an internal fault. Contact Oneplus, I suspect a return.
Related
Hi - it's windows device, so from time to time it hangs so much it requires the soft reset. (Other than that though, i love the device)
When it fires up again, it just completely flips out. Vibrating, constant repition of the 'calendar reminder' sound, goes on for about 5 - 10 minutes!
Then will either reboot itself, or come up all ok.
It's almost like it has 100 un-acknowledged reminders, i havn't dismissed and it's firing them at me. No messages on screne though.
Any ideas? without me having to do a full reset?
Thanks - Jam
I'm having ery strange issues on restart as well. I'm about to contact 02 about it as it's really ecoming unacceptable.
Issue i get is when the phone is switched on or restarted and there is a reminder or alert he phone boots through to the pin enty screen (required for email access on our servers) the alert pops up and phone imediately resets itself again, It did this today for over 30 minutes in a constant loop then starts working ok. I fly a lot so switch the phone off then on when I arrive and if I'm waiting for a pickup it's a real pain !
Any ideas on possible solutions?
Sounds like there is a problem with the Notification Queue on the Orbit (I have had similar problems on mine, when an alarm went off but I wasn't able to dismiss it.
There is a program called CheckNotification available at http://scarybearsoftware.com/cn_overview.html which allows you to view the queue and delete the recalcitant message. This program was not written for WM5 and you need to be careful when using it. In particular, do not use the "Clear" button or it will stop ActiveSync from working.
Same Problem PLEASE HELP!
Hi,
Please can someone help us! I'm so glad that it's not just me experiencing this weird behaviour.
My Orbit is going into a continous reboot cycle with it popping up reminders for me to dismiss, but before they can be dismissed the Orbit reboots again. The reminders come up just before you're required to enter the device passcode. It's a nightmare.
Also randomly occuring is the fact that the date gets put back to October 2006. Is anyone else experiencing this? Perhaps it's related?
Rob
I ended up getting a replacement phone from 02, this one seems to be ok but I've explicitly not set it up for mail yet (it seems that the problem was when it hit the start up pin that's required for email security). I'm going to try it on the WM6 upgrade and see if that helps.
I've had some problems with my phone recently as it keeps rebooting itself (sometimes when charging and the battery gets hot.. sometimes randomly). When this happened a few months ago it got to a point where almost everything stopped working.. I did a factory reset but no joy so I took it to a phone shop and the guy said he flashed it and everything seemed to work again for another couple weeks then the rebooting started again but less frequently. Its now become a daily thing and today everything has stopped working again.. my call list.. text & emails won't update if a new message comes in I can't see anything in the list. I keep getting a popup telling me that Open Sense Plugin Manager has unexpectedly stopped along a couple of other error messages. I can't install anything either.
Any suggestions on how to solve this? I'm getting more than streesed by this!
Is it still rebooting? You could use an RUU and it might solve the issue but it might not. A bit of hit and miss if you ask me. If it is still rebooting because its getting hot, give HTC a ring.
Meaple said:
Is it still rebooting? You could use an RUU and it might solve the issue but it might not. A bit of hit and miss if you ask me. If it is still rebooting because its getting hot, give HTC a ring.
Click to expand...
Click to collapse
What's an RUU?
It got to a point last night where it wasn't turning on at all just getting to the T-Mobile screen and then back to the HTC screen continuously. I managed to do a system reboot which stopped the error messages I was getting but it was still doing a number of reboots. Seems to have settled now but obviously there's still an underlying problem there.
Will def be giving HTC a call in a while but want to avoid sending it to them unless absolutely necessary.
Telephone year. About a month ago, has become periodically cut down without any reason.
And while waiting, and while listening to music / talk on the phone and on the charging ..
The day turned off up to 10 times ...
After switching displays "Phone has just been rebuilt after an incorrect reset. Send error report to HTC to determine the cause of the problem?".
Reports are sent each time, but all to no purpose.
Somebody faced a similar problem?
I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?
Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.
Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?
Hey there.
I'm not sure how common or widespread this issue is, but some Zenphone 6 / Asus 6z users have been experiencing crashes, reboots and bootloops after they make or receive phone calls.
According to a user from this support thread, the issue seems to have cropped up around their Android 10 firmware update. it seems as though different users experience slightly different behaviour, but the cause of the problems all seem to coincide with phone calls.
The problems wouldn't always be immediately apparent. After ending a phone call, the system would gradually reach a point of instability leading to a crash and a bootloop. Suffice it to say the error will eventually present itself within the same day of a call. This seems to affect custom ROMs like LineageOS, which lead me to believe issue was caused by either hardware or vendor firmware.
In the thread linked above, a support technician suggested the issue would be resolved with an upcoming OTA. At the time of writing, this was around January. I had installed the vendor firmware for the December Android 10 OTA (WW-17.1810.2011.183) and was still experiencing the problem.
I wasn't able to discern anything of clear value from adb logcat, though I did remember one thing: the system made a reference to the SIM slot number. For whatever reason I had my SIM card in slot 2 but logcat was showing warnings for slot 1.
I only use one SIM on the phone so I decided to swap it over to slot 1. I've been making phone calls for a couple of days now without any issues, so I'm guessing my phone has a hardware fault which I believe has also been acknowledged by Asus support staff in the thread above.
If any of on Android 10 are suffering crashes due to phone calls, please check which SIM slot you're making calls from and let me know. If any of you haven't experienced a crash of this nature, could you please try to swap over to slot 2 and see what happens?
Thank you for reading
Kind regards,
Vik
i remember this call problem (phone unresponsive, restarting and bootlooping)
its gone since i switched to android 11 (asus fw)
I had it in lineage too, now 1/3/21 seems gone
Iused sim 1 slot