Related
Hi there,
my girlfriend owns an o2 XDA Diamond aka HTC Diamond.
Shes totally annoyed by the screen-lock function.
When the screen is locked and some kind of event appears (e.g. incoming text message or an alarm) the lock seems to fall into some undefined state:
- sceen dark
- you can see the softbuttons for the event (e.g. Read new message and reply)
- you cannot push them, as the screen is locked.
- you cannot unlock the screen trough the pen.
Only thing that helps in those cases is a soft-reset.
This problem happens quite often ... she has to reboot the phone at least two or three times a day ...
The other problem is the overall performance of the UI (is it Manila?)
Is there a faster version than the stock version? Is it possible to install the sense UI on the diamond?
Hope these can be solved without having to flash a whole new Rom?
What are your experience with the battery?
Hers had to be replaced after two days of usage because it became hot an discharged really fast.
Same problem appeard again a few days ago.
Is there any 3rd-party battery with better performance?
Thank you guys for any hint.
Regarding the battery
from personal experience older original roms seemed to be more of a problem then the actual battery, with bad power and radio management resulting in the battery to quickly overheat. make sure you always have the latest original rom installed if youdon't want to run homebrews, you can ofc find these on the official htc homepage.
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.
[Q]
Out of the blue my Bionic just started rebooting. 8-10 time per day, who knows how may time at night. I am using the stock ROM. I am looking for a stable ROM that I can use to fix the problem. I also have the problem of disapearing apps that I move to the ext card.
Feedback on possible cures will be welcomed.
I just experienced my first unexpected reboot. It was after plugging in my USB to my computer.
This seems like the sort of thing that would have a 50% chance of being related to your hardware, and a 50% chance of an unstable app screwing something up. The stock software is at least stable enough that it's not very likely to be the cause of your issues, and flashing another ROM (which will have the same kernel) won't help if it is a hardware issue.
A factory reset followed by staggered reinstallation of apps (one or two at a time, to see if one in particular might be causing issues) would be my first step for a problem as extreme as random reboots. The next step is through warranty channels. I might even do that first- I don't think I could put up with a phone that rebooted on me.
And the cure for disappearing apps is to not use media area for storage. The phone dedicates 4gb for apps, that should be more than enough until they patch a fix.
i may have to add that my phone was completely stable until i purchased and installed the extended battery then i started to experience reboots and a few locks here and there.
i did a few factory reset on the stock but the phone was still acting up with the new battery.
i then decided to root and run roms and to be frank no locks and or reboots running the same battery that seemed to be causing the problems based on that being the only change to my phone before the reboot and locks.
i am not saying that there is something there with the stock as there would be more reports on this but rooting and going back to stock is a single click now making it a fast process to trouble shoot the software.
i am experiencing a bad or short life with the extended so in my case it could have been the battery screwing up the reads on the software (guess) but the first 3 charge from full to dead just about 3 days after that same extended only last one day.
in general it seemed that my issue could have been a bad battery and wiping data and playing with roms may had help but in the end i will be calling verizon for a battery replacement as i doubt that in two weeks the battery charge for an extended could only last 1 day of medium use.
sorry long response and by no means i'm i encouraging to root and rom just speaking out of my experience.
Hi - first post here. After 4 Thunderbolts - Verizon sent me a Bionic. Much better however, after rooting with 43v3r and de-bloating with The Black Hat App - I'm having random reboots. Initially, the reboots were several times per day increasing in frequency to several times an hour. Y u c k - My Thunderbolt could do that too.
So in troubleshooting:
1 - I've reverted to stock build - no add'l apps: No reboots in 48 hours. So - I doubt it's hardware.
2- After reverting - I then rooted w/43v3R, then debloated - just using stock apps - no reboots in 24 hours. So, I really doubt it's debloating or rooting
3 - After adding a few apps - Stitcher, Enhanced email, SVOX w/voice, Beautiful Widgets (w/clock selected) - I get a reboot.
4 - Remove everything but stitcher. No reboots - 24 hours.
5 - Add Enhanced Email yesterday
Today, I had a reboot.
6 - So culprit 'looks' like Enhanced Email OR perhaps a switching problem between 3/4g (The Thunderbolt - Stitcher used to drop connection in this particular location so, there IS an issue w/3G-4G.
Questions:
1 - If it's not a 3g/4g issue; could it be related to where Enhanced email or Stitcher chooses to install itself?
2 - Is there a log somewhere where I could find 'boot' times and any issues relating to reboots? Like a 'minidump' in Windows...
thanks
I, too, have started having unexpected reboots. I can't pinpoint it exactly, but I have also recently isntalled Enhanced Email (trial version).
Reboot Logger
Hey Google is our friend - don't know why I didn't look before but I found this in Android Market.
"Reboot Logger" by Watanabe,Masayuki.
Just installed it - will report back after Thanksgiving (in the U.S. - Thursday)...
(I would post a link but I'm a noob here - and, now I know why I hate myself.)
Looks like promising -
Have yall installed any themes or different battery icons, or anything like that to yours? Mine is 43v3R rooted with the liberty romv2. I was changing a cpl of the icons and experienced a reboot just out of the blue. I got rid of the icons I changed and stayed with the icons that came with the liberty rom and have no issues at all. I do not have enhanced mail on mine.
most bionics will turn off and wont turn back on till you do a battery pull. Its a known issue, all you have to do is google it and it turns up. From what ive read putting the battery on performance mode and putting on detect in pocket will help. Personally it doesnt help, i had the issue with the stock battery so purchased a extended thinking it was the battery, but after doing research i found out it isnt. They say the new OTA should fix it
icons - reboot logger
Thanks - haven't changed any icons BUT I am using HTC Thunderbolt wallpaper. I had a Thunderbolt that had a reboot problem until the OTA before Gingerbread - Verizon offered me the Bionic when I called about my Thunderbolt issues (I had three replacements - all with the same issues).
I will try different wallpaper -
Reboot logger works well but doesn't offer a clue as to what is causing the reboots. Mine has rebooted 2-3 times per day since I installed Reboot Logger(RL).
3 times a day is tolerable but, I would like to get to the bottom of what's causing it.
What IS helpful with RL is that it does show that the reboots are not occuring in any obvious time sequence.
They may be related to push emails coming in from my Exchange server. Not sure - I'll post more as I learn more. Hopefully the upcoming OTA will fix - though my experience with HTC's OTAs does not give me a lot of hope.
Update - Last night, I uninstalled Stitcher - Stitcher frequently throws errors requiring a FORCE CLOSE. I also have kept Blueooth off.
No reboots in 24 hours -
Will reinstall Stitcher in the morning (I need it at the gym)...
Update tomorrow/Monday
Turned Bluetooth ON - no reboots in 36 hours so, It looks like Stitcher may be the culprit - I wonder if Stitcher has issue with the internal/external SD storage scheme.
As I noted previously, Stitcher reports 'force closes' frequently - especially when it's not even active (when I have not loaded it or used it).
(No sooner than I posted this - my phone rebooted. And again, and again will switch off BT - I'm in my office so, there's could be an issue with 3g/4g switching or other interference...)
Have you tried setting the phone to run strictly 3g? I have had no issues at all with mine jumping back and forth between 3g/4g.. I leave mine on 3g to keep it from trying to search for a 4g signal. I never turn bluetooth on, nor do I ever really use the compass. hmmmm... Can you tell me everything you have done to the phone. Apps you have installed, what ROM you using, if you have .886/.893 etc? I'm willing to see how close we are as for as how our phone's are setup and help as much as I can. I have not had a single issue with mine other then that one reboot after changing the battery icon.
After nearly two weeks of monitoring restarts - it appears that the problem is more related to where I am. At my home, restarts are rare and related to Stitcher.
At work in Beverly Hills, CA; restarts occur frequently. I assume it has something to do with 3g/4G switchover/crossover or interference.
I had lots of problems with the Thunderbolt dropping data connections in 90210. I could not use the hotspot. On the Bionic, the hotspot functions really well. I've used it up north near Fresno in 3G only land, here in BH and at home where I have decent 4G coverage.
When I remove Stitcher, the reboot problem disappears. Sometimes when I 'wake' the phone, there is a dialog apologizing for Stitcher having 'force closed' even if I haven't used it for days. Market reviews indicate anecdotally that Stitcher has a problem with force closes. This behavior must also be at the root of some of the reboots.
I've also set all programs not to update automatically - this may have reduced the reboots as well. On average, I'm getting 2-3 reboots per day. More than I would like but, tolerable.
So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!
ShrekOpher said:
So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!
Click to expand...
Click to collapse
Many have had similar issues, for example:
http://forum.xda-developers.com/note-4-tmobile/general/marshmallow-updates-issues-t3415914
http://forum.xda-developers.com/note-4-tmobile/help/major-phone-issues-reboots-freezes-t3440870
A proposed solution has been to downgrade to LP, although some people have reported it not fully fixing the issues.
Hi,
first of all sorry for my bad english and screenshots with german text .
The situation:
I have a total of two Tab S2 (T-813). The first is 4 years old, the second is less than 2 years old. The newer is now causing problems.
The reboots occur:
- When using the tablet. Definitely with a high load, but also sometimes with only light loads
- When it is charging
- completely random
Edit1: reboots are not related to the battery percentage
Edit2: never experienced a reboot while in TWRP.
I didn't really find anyone with the same problem on the Internet. It is not a boot loop. Sometimes you can use the tablet for hours/ days. Then again not at all, because it starts again after a minute. To narrow down the problem, I formatted both tablets and installed the same lineage version and firmware. Since it restarts, log files are unusable, right?
Is there any way to narrow down the error?
I suspect overheating, but I would like to know if I have any way to isolate the fault exactly. Maybe there is also another (hardware) forum, which can help better in this case, then I would also be grateful for a tip.
I would have no problem opening the tablet. I've already done this with my smartphones.
Thx for your time.
Solution:
It is an overheating problem if you have exactly the same problems as I had.
You can test it simply like this: fill a plastic bag with cold water and some icecubes. Use it like a pillow for your tablet so it can rest on the bag while you use it. I had no problems at all while doing this.
I send it to Samsung and they repaired it.
It's just as new now.
I actually have the same problem, just only when its at 15 or less battery
Hi.
Well, it sounds for me like a different problem, cause it's battery related. My battery is fine and I have reboots not related to battery status.
Have you tried anything (factory reset, newest lineage and firmware,...)?
Hi,
same here. A SM-T813 running LineageOS that started with random freezes and reboots about a week ago. Sometimes I can use it for about half an hour without problems, next time it reboots while rebooting ...
Seems to be completly random, only thing I noticed that it never reboots while in TWRP.
Cleared and reinstalled LineageOS, but didn't change anything. First time rebooted while still in the setup wizard, next time I could finish the wizard and install serveral apps before the next reboot.
Maybe a problem with the memory?
Yes, that is exactly the same.
I never experienced a reboot in TWRP. No problem with reinstalling lineage.
But while reinstalling Android, it reboots while configuring and while reinstalling apps.
The last days I could watch Amazon prime every evening. Now it reboots after a minute even without using it. I shut it off and hope it will work this evening again.
I have the same issue, sent it in for repair asked to flip battery and swap mainboard. Got it back. Worked a few days, then had random reboots again. I am 100% sure it is a battery issue, and when you get under a specific voltage, maybe when it gets under 30% or so, the chance for reboots rise dramatically, with high cpu or flash memory usage. It happens more often when doing a update in Google Play store for example. So totally have no idea, if Samsung flipped the battery or not, but this was my last Samsung product ever. I would assume there is an issue with too much current drain and then it reboots, and the battery used in them are not designed for the units properly.
same to me. i was on stock rom. never root or anything. and got random reboots most of them when i open google play or google chrome. now im on lineage and same. also i notice that the tablet didnt reboot until i install gapps. and the tablet never reboot on recovery or TWSR. reboots on high or low battery. and if it was overheating maybe the tablet will reboot on recovery. dont know its weird. i will try lineage with out gapps to see what happend.
just testing lineage without gapps no reboot. run browser and netflix with no problems. then i install youtube from aptoid store. and reboot start again. o unistall youtube and no reboot for now.
Same here. I have random reboots but also wifi disconnections (unable to reconnect until i reboot the device)...
Not evident cause...
Someone got a solution for this?
Have the same problem on my T813
You can find the solution for the problem I described at the end of the first post.