Related
So this has happened a few times to me. While I'm at work I'll leave my TB in my pocket and only check it during my two 15 minute breaks and 45 minute lunch and even then I only use it lightly. In between those breaks, I've noticed about 2-4 times already that the phone starts to heat up when it's in my pocket. I go in to work at about 9am and by noon or 1pm, the battery is in yellow despite me never even turning on the screen.
I checked the battery usage screen and it shows that the display accounts for ~70-80% of the battery drainage. My screen is set to auto lock at 1 minute and I have Auto-sync turned off on everything so what could be causing this?
Classick206 said:
So this has happened a few times to me. While I'm at work I'll leave my TB in my pocket and only check it during my two 15 minute breaks and 45 minute lunch and even then I only use it lightly. In between those breaks, I've noticed about 2-4 times already that the phone starts to heat up when it's in my pocket. I go in to work at about 9am and by noon or 1pm, the battery is in yellow despite me never even turning on the screen.
I checked the battery usage screen and it shows that the display accounts for ~70-80% of the battery drainage. My screen is set to auto lock at 1 minute and I have Auto-sync turned off on everything so what could be causing this?
Click to expand...
Click to collapse
Are you rooted or unrooted? If you are rooted try another kernel.
As someone else said, if you're rooted, try another kernel.
If you're stock and haven't made any modifications, then it's probably defective. It's pretty abnormal for a Thunderbolt to overheat like that. I'd suggest exchanging it. This should fall under the manufacturer warranty; no need to use your insurance if you have it.
I'm actually unrooted. I guess I'll drop by my Verizon store tomorrow. Hopefully they'll swap it out on the spot and not force me to go phoneless for weeks.
Classick206 said:
I'm actually unrooted. I guess I'll drop by my Verizon store tomorrow. Hopefully they'll swap it out on the spot and not force me to go phoneless for weeks.
Click to expand...
Click to collapse
Don't worry, this isn't an iPhone.
Morning, gentlemen.
I'd like to give you a break down of the 44~ hours I've had this phone as of right now and the troubles I've had with it. I'll preface this post with the fact that I work a corporate IT job and even as I may believe everything posted to be correct, please correct me if I state anything incorrectly. Thanks
I received the HTC Rezound around 3PM EST on Friday. Out of the box, I was unable to active the phone. I was coming from a 3G Droid X via an alternate line upgrade, and I had played with the Droid Bionic and had some issues activating there. I'll chalk up activating issues to needing to activate the 4G SIM card over the phone because of it being a corporate account. After 25 minutes on the phone with our Verizon representative, we were successful in activating the phone. Immediately afterwords, the phone rebooted. I believe that it did because of the PRI programming, but I'm also not terribly familiar with the back-end of the 4G activation.
At 3:30 PM EST it was at 35% out of the box after activation. I figured that I'd let it drain entirely to zero out the battery and charge it to 100% later on that night. After getting home and around 7:30 PM, the phone battery gave up and shut down. I plugged in the phone (HTC charger, HTC cable, surge protected outlet) and at 9:00 stood in front of the phone watching it go from off, to the HTC white boot screen, to the unlock screen where it would be completely frozen, and approx. 30 seconds later, would loop that process again and again until I pulled the battery. I go to pick up the phone and it's very hot. Not uncomfortable just yet, but hotter than any phone since the droid 1 had gotten in my hand. Pulled the battery, let it cool down, and booted to the HTC recovery (power + vol. Down) and wiped the phone. After booting, the battery was only at 14%. Strange since it had been on the charger, but I supposed bootlooping might hinder the ability to charge. After verifying that it was not bootlooping any further and using my old fascinate charger (same voltage, same microUSB connector), I went to bed.
Saturday morning 8AM, the phone was bootlooping again. Pulled the battery, let it boot up afterwords after and it was at 100% battery. Strange. Fast forward to 5PM: Phone has rebooted twice throughout the day maybe around noon and 2PM, but no looping. Battery was at 50%, and at 5:15 PM it begins to bootloop again. Pull battery, turn it back on, battery is at 9%. I plug it into the HTC charger using the HTC cable again to a grounded power strip. Plug it in at 5:30 PM and walk away.
At 7PM, I go to pick up the phone and it's bootlooping again and it is so hot it's literally uncomfortable to hold for more than literally a couple seconds. Immediately unplug it from the cable and pull the battery, also very uncomfortable to hold. I decide that the HTC charger is having many problems, and put it away so I don't use it by accident. I've uploaded a video on my Facebook (http://www.facebook.com/photo.php?v=1661452940302) so that you can see what the screen was doing after it heated up that much. I didn't have any other problems with the phone after one FINAL reboot for last night.
This morning, I placed it on the charger: Same deal of massive overheating and the screen doubling. EDIT: I've also noticed that for the most part, it overheats if it charges past 50%
Simply put: This is a beautiful phone, a wonderful speakerphone, great at texting. But seriously: I haven't seen anything else like ANY of this online anywhere yet. Anyone else seeing issues like these?
Thanks.
Dan Manners
Nope.
Try pulling the battery and putting it back. Do not power up. Connect to charger and let it full charge. Disconnect charger and boot it
If it is super hot during any of that take it back.
DanManners said:
Morning, gentlemen.
I'd like to give you a break down of the 44~ hours I've had this phone as of right now and the troubles I've had with it. I'll preface this post with the fact that I work a corporate IT job and even as I may believe everything posted to be correct, please correct me if I state anything incorrectly. Thanks
I received the HTC Rezound around 3PM EST on Friday. Out of the box, I was unable to active the phone. I was coming from a 3G Droid X via an alternate line upgrade, and I had played with the Droid Bionic and had some issues activating there. I'll chalk up activating issues to needing to activate the 4G SIM card over the phone because of it being a corporate account. After 25 minutes on the phone with our Verizon representative, we were successful in activating the phone. Immediately afterwords, the phone rebooted. I believe that it did because of the PRI programming, but I'm also not terribly familiar with the back-end of the 4G activation.
At 3:30 PM EST it was at 35% out of the box after activation. I figured that I'd let it drain entirely to zero out the battery and charge it to 100% later on that night. After getting home and around 7:30 PM, the phone battery gave up and shut down. I plugged in the phone (HTC charger, HTC cable, surge protected outlet) and at 9:00 stood in front of the phone watching it go from off, to the HTC white boot screen, to the unlock screen where it would be completely frozen, and approx. 30 seconds later, would loop that process again and again until I pulled the battery. I go to pick up the phone and it's very hot. Not uncomfortable just yet, but hotter than any phone since the droid 1 had gotten in my hand. Pulled the battery, let it cool down, and booted to the HTC recovery (power + vol. Down) and wiped the phone. After booting, the battery was only at 14%. Strange since it had been on the charger, but I supposed bootlooping might hinder the ability to charge. After verifying that it was not bootlooping any further and using my old fascinate charger (same voltage, same microUSB connector), I went to bed.
Saturday morning 8AM, the phone was bootlooping again. Pulled the battery, let it boot up afterwords after and it was at 100% battery. Strange. Fast forward to 5PM: Phone has rebooted twice throughout the day maybe around noon and 2PM, but no looping. Battery was at 50%, and at 5:15 PM it begins to bootloop again. Pull battery, turn it back on, battery is at 9%. I plug it into the HTC charger using the HTC cable again to a grounded power strip. Plug it in at 5:30 PM and walk away.
At 7PM, I go to pick up the phone and it's bootlooping again and it is so hot it's literally uncomfortable to hold for more than literally a couple seconds. Immediately unplug it from the cable and pull the battery, also very uncomfortable to hold. I decide that the HTC charger is having many problems, and put it away so I don't use it by accident. I've uploaded a video on my Facebook (http://www.facebook.com/photo.php?v=1661452940302) so that you can see what the screen was doing after it heated up that much. I didn't have any other problems with the phone after one FINAL reboot for last night.
This morning, I placed it on the charger: Same deal of massive overheating and the screen doubling. EDIT: I've also noticed that for the most part, it overheats if it charges past 50%
Simply put: This is a beautiful phone, a wonderful speakerphone, great at texting. But seriously: I haven't seen anything else like ANY of this online anywhere yet. Anyone else seeing issues like these?
Thanks.
Dan Manners
Click to expand...
Click to collapse
I watched that video. I have NEVER seen anything like that and I have seen some weird stuff on my phone trying some weird modifications. (I have gotten massive screen tear and other stuff but that is due to the things I have done).
I would suggest returning the phone and getting a new one. I imagine that one is a lemon. You could try restoring the phone via the RUU in the shipped rom thread in the developement section but I think you should just return that one.
Unless you have messed with it aside from what you have told us (I doubt it though) I would return that one.
Easy
Return it.
My first Incredible did this, and my current incredible is doing this. Something in your phone is causing a thermal overload, which triggers a reboot, which gets only so far in the reboot until the thermal protection loads, it notices it is hot, and triggers a reboot [repeat].
In my case, the hardware radio (on both Dincs) was damaged/defective/finally gave way. 10 seconds on the internet will do this to me.
Return it. Do not diagnose it. Do not follow other peoples recommendations for testing. Return it. You must get rid of a phone like this.
Of course, this is one of my huge fears because I am leaving my Dinc for this phone; and now I am seeing that lemons are in this batch as well.
jdmba said:
Return it.
My first Incredible did this, and my current incredible is doing this. Something in your phone is causing a thermal overload, which triggers a reboot, which gets only so far in the reboot until the thermal protection loads, it notices it is hot, and triggers a reboot [repeat].
In my case, the hardware radio (on both Dincs) was damaged/defective/finally gave way. 10 seconds on the internet will do this to me.
Return it. Do not diagnose it. Do not follow other peoples recommendations for testing. Return it. You must get rid of a phone like this.
Of course, this is one of my huge fears because I am leaving my Dinc for this phone; and now I am seeing that lemons are in this batch as well.
Click to expand...
Click to collapse
Definitely what I'm planning on doing. Debating on whether I want to hold of until tomorrow so I can show my boss though. I usually mess with my droid phones (Alternate roms, overclocking, undervolting, etc) and he always gets annoyed. For once, STRAIGHT OUT OF THE BOX it's acting like this. I suppose it's Karma
DanManners said:
Definitely what I'm planning on doing. Debating on whether I want to hold of until tomorrow so I can show my boss though. I usually mess with my droid phones (Alternate roms, overclocking, undervolting, etc) and he always gets annoyed. For once, STRAIGHT OUT OF THE BOX it's acting like this. I suppose it's Karma
Click to expand...
Click to collapse
Just show him that video haha. That convinced me immediately. If it is really getting that hot there is a real problem and I would be getting it out of my hands ASAP.
you either just got a faulty phone or a faulty battery. as the others are saying, return/exchange it.
I personally got a dead pixel and the touch screen is a tad off(I'll click on a link and it'll think I clicked on the link right above(or below).... not all the time though.
right now I'm just sitting in front of Verizon waiting for them to open.
Mine gets fairly warm, especially when working while being plugged.
My first phone had a problem with the bezel coming apart, but it also ran warmer then the second one I have, it was always warm in my pocket, the new one isn't.
If you guys use LTE OnOff you can turn off the antenna you don't need/use be it CDMA or LTE. It will run cooler and battery life will last longer.
AtLemacks said:
If you guys use LTE OnOff you can turn off the antenna you don't need/use be it CDMA or LTE. It will run cooler and battery life will last longer.
Click to expand...
Click to collapse
I always leave it off, LTE really is overrated. A wonderful nicety, but I don't NEED it.
...
With total and complete respect for the immediately preceding couple of posters, I CANNOT STRESS THIS ENOUGH ... do not use tricks to cool your phone down.
You do not want to wind up on the other side of the 14 days with a phone which otherwise overheats from general use. DO NOT FOLLOW ADVICE SUCH AS TURNING OFF LTE.
Sure, if you have a working phone, and you think that will help your battery, then go for it. If you have thermal issues do NOT use bandaids.
(This has been a public service announcement).
LOL. I'm watching this very closely.
If the device isn't currently overheating turning LTE off isn't going to hurt it, lmao. They wouldn't bake in a feature that is going to make your phone melt down. Now, if you have problems CURRENTLY then you should warranty replace it. But 14 days doesn't have anything to do with it, you can call and warranty your phone anytime in the first year, 2 if you have the extended warranty. So it is NOT bad advice to turn it off if it is of no use to you. Don't scare people into killing their batteries just because they don't currently have an issue.
To the OP: I am currently on my SECOND DEFECTIVE Brand new Rezound.
The first one gave up on having any sort of vibrate function whatsoever (yes, the battery was pulled, factory reset, blah blah). Haptic feedback, softkey vibration, and all vibrations in general were completely dead. I took it back and got a brand new one since it's only 6 DAYS old. It only started having this problem this morning.
Got the new one at about 11AM today, and it starting having the power cycling issue that you're having about an hour ago. The phone is literally 7 HOURS old and wont stay on for more than 30 seconds before it reboots itself. I am VERY disappointed. Now I have to find the time to go in yet AGAIN to Verizon. I was on the phone with the tech and tried battery pulling it and factory data resetting it to no avail. It wouldn't even Factory Data Reset from HBOOT!
Sigh.
voxigenboy said:
you either just got a faulty phone or a faulty battery. as the others are saying, return/exchange it.
I personally got a dead pixel and the touch screen is a tad off(I'll click on a link and it'll think I clicked on the link right above(or below).... not all the time though.
right now I'm just sitting in front of Verizon waiting for them to open.
Click to expand...
Click to collapse
Why don't you go in and calibrate the keyboard if it's off?
OP
I think you should have added a "None of the above" as a selection for your poll. would have a lot more than 2 people.
My first phone and my second phone are set up the same, both factory reset both with LTE on and the second one makes little to no heat when idle, the first was warm all the time.
zeroxg4 said:
To the OP: I am currently on my SECOND DEFECTIVE Brand new Rezound.
The first one gave up on having any sort of vibrate function whatsoever (yes, the battery was pulled, factory reset, blah blah). Haptic feedback, softkey vibration, and all vibrations in general were completely dead. I took it back and got a brand new one since it's only 6 DAYS old. It only started having this problem this morning.
Got the new one at about 11AM today, and it starting having the power cycling issue that you're having about an hour ago. The phone is literally 7 HOURS old and wont stay on for more than 30 seconds before it reboots itself. I am VERY disappointed. Now I have to find the time to go in yet AGAIN to Verizon. I was on the phone with the tech and tried battery pulling it and factory data resetting it to no avail. It wouldn't even Factory Data Reset from HBOOT!
Sigh.
Click to expand...
Click to collapse
I tried to go to Verizon today, but they refused to do anything since it's a corporate account and 48 hours old. I'm really up in the air about whether I'm going to stick with the Rezound or go back to the Droid X.
DanManners said:
I tried to go to Verizon today, but they refused to do anything since it's a corporate account and 48 hours old. I'm really up in the air about whether I'm going to stick with the Rezound or go back to the Droid X.
Click to expand...
Click to collapse
Wow, that's ridiculous. They had no issues whatsoever replacing mine (and the one I'm replacing tomorrow) because it's within the first 14 days of purchase. I guess it works differently for corporate accounts.
Honestly, though.. I can't imagine them saying anything other than "Sorry, we'll give you a new one". How can you be sold a product that is OBVIOUSLY defective (and certainly NOT cheap) and be told that there's nothing that can be done? It just doesn't make any sense to me.
I'm actually pretty upset that I keep having to go get replacements, even though they're new. I've been looking forward to getting this phone for a while and actually would like it to work correctly. It's just disappointing to see that 2/2 have been defective so far. Hopefully it ends there.
zeroxg4 said:
Wow, that's ridiculous. They had no issues whatsoever replacing mine (and the one I'm replacing tomorrow) because it's within the first 14 days of purchase. I guess it works differently for corporate accounts.
Honestly, though.. I can't imagine them saying anything other than "Sorry, we'll give you a new one". How can you be sold a product that is OBVIOUSLY defective (and certainly NOT cheap) and be told that there's nothing that can be done? It just doesn't make any sense to me.
I'm actually pretty upset that I keep having to go get replacements, even though they're new. I've been looking forward to getting this phone for a while and actually would like it to work correctly. It's just disappointing to see that 2/2 have been defective so far. Hopefully it ends there.
Click to expand...
Click to collapse
Corporate allocation and stock is different than the consumer market.
Hi all!
One thing drives me nuts about my wife tab - it turns screen on in the middle of the night, I guess when battery is completely charge.
Is there any way to disable or completely remove this behavior?
I use AutomateId to disable sounds, but there is nothing to turn off screen completely.
I checked few custom roms and do not see one fixing this problem. So, any suggestions will be appreciated!
Keep the tab switched off while charging
ansonantonym said:
Keep the tab switched off while charging
Click to expand...
Click to collapse
Uh, yeah. That'dprobably do it. ;-)
On a somewhat related note... Is there a danger of overcharging? It always says, "Device fully charged. Please unplug charger." Is it unreasonable to expect smart charge capability?
Sent from my GT-P7510 using xda premium
That is an option, unless you need it on for something else, like an alarm in the morning ;-)
However, sumsung phones developers let say, were able to work around in custom roms, so I was in hope, that may be I missed something...
JM_I said:
Uh, yeah. That'dprobably do it. ;-)
On a somewhat related note... Is there a danger of overcharging? It always says, "Device fully charged. Please unplug charger." Is it unreasonable to expect smart charge capability?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
the message to unplug is purely an energy saving measure. It doesn't mean unplug from the tab, it means unplug from the wall to prevent "vampire power drain".
I agree about it being sodding annoying, though; the point of charging overnight is that it's fully charged come morning not fully charged at, say, 1am and partially drained by morning! /rant
chaosdefinesorder said:
the message to unplug is purely an energy saving measure. It doesn't mean unplug from the tab, it means unplug from the wall to prevent "vampire power drain".
I agree about it being sodding annoying, though; the point of charging overnight is that it's fully charged come morning not fully charged at, say, 1am and partially drained by morning! /rant
Click to expand...
Click to collapse
Ah, well... Aside from being somewhat econazi-ish, that makes sense. The "wake-up-on-full-charge" thing doesn't really annoy me too much because it's in the case almost all the time. Closed cover = no problems.
CNemo7539 said:
Hi all!
One thing drives me nuts about my wife tab - it turns screen on in the middle of the night, I guess when battery is completely charge.
Is there any way to disable or completely remove this behavior?
I use AutomateId to disable sounds, but there is nothing to turn off screen completely.
I checked few custom roms and do not see one fixing this problem. So, any suggestions will be appreciated!
Click to expand...
Click to collapse
Wow! I thought I was the only one. This drives me nuts! I just thought it was one of those random custom ROM bugs. I'd love a fix because then I could just set my setCPU profile to clock down when the screen is off, but since it comes on, I have to make more complicated settings (or else it overheats inside the case!).
I think I figured it out by a chance...
There setting "Never turn screen off when charging" or something like this. I do not have tab in front of me.
Removed that check and didn't see screen on this night.
If it help to anybody else please post here to confirm.
CNemo7539 said:
I think I figured it out by a chance...
There setting "Never turn screen off when charging" or something like this. I do not have tab in front of me.
Removed that check and didn't see screen on this night.
If it help to anybody else please post here to confirm.
Click to expand...
Click to collapse
If you figure out where the setting is will you update this thread? Also, update the OP to make it useful to others (including me!)
settings>applications>developments>stay awake, unmark the box, I hope your problem will end. I unmarked it as soon as I got my P7500 while checking settings and never experience this.
I have this option unchecked as well. I can confirm that the tablet turns on when it is completely charged and then goes back to sleep after a short while again.
Regards
Achim
Yeap, it does that. But like you said it shut the display in a short while, if it the option unchecked.
It's usually disabled in custom roms but if you have the skills and time try to make it yourself, although it's annoying that at 4am you hear the tablet buzzin' you that it's fully charged...
I had the same screen switching on over night problem with stock 3.1 ROM.
The tab switched on automatically, and never switched off.
It happened while it was charged and while was not charged, or after rebooted.
I work in front of the tab, and it switched on more and more often.
Once I set the screen off time to another, shorter value, it solved the problem for that afternoon, but in the morning the screen was on again.
Finally I removed 50 rarely used apps, and the problem is almost fixed. It happened only once since then. I think I permitted some app to administer the device in the menu, and those caused this.
sedward said:
I had the same screen switching on over night problem with stock 3.1 ROM.
The tab switched on automatically, and never switched off.
It happened while it was charged and while was not charged, or after rebooted.
I work in front of the tab, and it switched on more and more often.
Once I set the screen off time to another, shorter value, it solved the problem for that afternoon, but in the morning the screen was on again.
Finally I removed 50 rarely used apps, and the problem is almost fixed. It happened only once since then. I think I permitted some app to administer the device in the menu, and those caused this.
Click to expand...
Click to collapse
I think my screen problem is also related to the multimedia dock. When the tab is in the dock and the dock is NOT connected to the charger, then few times it switches on the screen after some time.
I put my tab into silent mode and close the cover.
No noise no light.
Alarm still makes noise even in silent.
But there really should be an option to turn this off.
My wife's Rezound (.605, ClearnROM 4.5) has been stable for weeks and weeks. Then, in the last 72 hours or so, it suddenly started ripping through its battery in minutes -- fully charged to dead in 90-180 minutes, even if the phone is just sitting on a desk, untouched, screen off. There doesn't appear to be anything running in the background to account for the drain (no Facebook or anything like that).
Any ideas? Really don't want to have to return it to stock, exchange it with VZW as defective, go through setting up a new one.
Thanks in advance...
a silly question but have you tried to over clock or under volt it recently?
Sent from my ADR6425LVW using xda premium
jldeitch said:
My wife's Rezound (.605, ClearnROM 4.5) has been stable for weeks and weeks. Then, in the last 72 hours or so, it suddenly started ripping through its battery in minutes -- fully charged to dead in 90-180 minutes, even if the phone is just sitting on a desk, untouched, screen off. There doesn't appear to be anything running in the background to account for the drain (no Facebook or anything like that).
Any ideas? Really don't want to have to return it to stock, exchange it with VZW as defective, go through setting up a new one.
Thanks in advance...
Click to expand...
Click to collapse
best thing to do is go into settings and see what has been using the phone. Go into apps, too and see what has been running.. Finally, an app like better battery stats can really help you see what is killing it.
Often in cases like yours, its a recently updated app that is keeping the phone awake for some reason.
lancasterv3 said:
a silly question but have you tried to over clock or under volt it recently?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
topgun1953 said:
best thing to do is go into settings and see what has been using the phone. Go into apps, too and see what has been running.. Finally, an app like better battery stats can really help you see what is killing it.
Often in cases like yours, its a recently updated app that is keeping the phone awake for some reason.
Click to expand...
Click to collapse
No to overclocking or undervolting. Haven't really had the need to do either since moving off our Droid Xs some months ago. But that was a good thought.
The screen appears to be what's killing the phone. For some reason, it keeps setting itself for Sleep/Never, meaning the screen is on all the time. The last time spent changing that setting seems to be working. Not sure why it keeps toggling back to that setting. May have to reset the phone, reload a ROM and see if a fresh start makes a difference...
First off, I'm rooted and have already patched my Omate TrueSmart Developer Edition with Lokifish Marz's security patch.
Device: 1900 1/8 TrueSmart Dev Edition
ROM/Firmware version: Latest
Changes made to stock firmware (if any): A few Xposed mods
Issue: See below, freeze, drain, screen not functioning.
Steps Taken: Restart, antivirus check
One day I turned my TrueSmart on (while off my wrist), went back about 15 minutes later to it and the screen wouldn't turn on. I though "Ahh, that's strange. I thought I turned this on." I pressed the power button multiple times to try to turn it on. It was already on, but the display would not turn on. The battery was charged already and at about 85%. I held the power button and felt the haptic feedback - no screen on.
Earlier that week, I'd noticed that the TrueSmart's battery was draining a bit faster than usual on WiFi alone, no SIM or GPS on. When the screen wouldn't work, I held down the power button for about 10-16 seconds (some Android Devices will restart, but not all, so I gave that a shot). - Nothing. I then left it alone for a day (didn't feel like playing with it after a long and busy work day). I tried to turn on the screen - nothing. I still got haptic feedback so I knew it was on. "Crap - now I have to void the warranty by doing a battery pull." Removed the screws, found the crappy water seal, did a battery pull, and turned the device back on. Screen worked - phew. The past two days it had been draining rather fast and the watch was overheating even though I kept it in about room temperature conditions.
I thought something was up so I ran avast! Anti-virus (I'm not playing the Linux OS' don't need antivirus software game - so let's not go there.) and the definitions/database took over two minutes to update (usually just 15 seconds) on a strong WiFi connection - strange. I ran the scan - nothing showed up but the scan mysteriously kept going away and I had to restart the scan a few times. Finally it worked even though I had to turn my WiFi on the watch off.
My question is - am I being completely paranoid or has my watch been hacked? Fast battery drain, connection issues, screen not responding, overheating - those are signs of spying and wiretapping, am I wrong? For the time being I removed the battery so that way if I am being spied on or hacked, the watch can't be powered on.
I've had the watch for only a few weeks, never installed any strange apps - all legit stuff. Am I crazy :silly: or is this something to be worried about?
deedscreen said:
First off, I'm rooted and have already patched my Omate TrueSmart Developer Edition with Lokifish Marz's security patch.
One day I turned my TrueSmart on (while off my wrist), went back about 15 minutes later to it and the screen wouldn't turn on. I though "Ahh, that's strange. I thought I turned this on." I pressed the power button multiple times to try to turn it on. It was already on, but the display would not turn on. The battery was charged already and at about 85%. I held the power button and felt the haptic feedback - no screen on.
Earlier that week, I'd noticed that the TrueSmart's battery was draining a bit faster than usual on WiFi alone, no SIM or GPS on. When the screen wouldn't work, I held down the power button for about 10-16 seconds (some Android Devices will restart, but not all, so I gave that a shot). - Nothing. I then left it alone for a day (didn't feel like playing with it after a long and busy work day). I tried to turn on the screen - nothing. I still got haptic feedback so I knew it was on. "Crap - now I have to void the warranty by doing a battery pull." Removed the screws, found the crappy water seal, did a battery pull, and turned the device back on. Screen worked - phew. The past two days it had been draining rather fast and the watch was overheating even though I kept it in about room temperature conditions.
I thought something was up so I ran avast! Anti-virus (I'm not playing the Linux OS' don't need antivirus software game - so let's not go there.) and the definitions/database took over two minutes to update (usually just 15 seconds) on a strong WiFi connection - strange. I ran the scan - nothing showed up but the scan mysteriously kept going away and I had to restart the scan a few times. Finally it worked even though I had to turn my WiFi on the watch off.
My question is - am I being completely paranoid or has my watch been hacked? Fast battery drain, connection issues, screen not responding, overheating - those are signs of spying and wiretapping, am I wrong? For the time being I removed the battery so that way if I am being spied on or hacked, the watch can't be powered on.
I've had the watch for only a few weeks, never installed any strange apps - all legit stuff. Am I crazy :silly: or is this something to be worried about?
Click to expand...
Click to collapse
As long as the apps that you have installed are legit, you should be fine.
I guess my only concern would be...how long did you use the device before installing Loki's patch? Did you connect to any network prior? It's your BT on? Is it set correctly?
As far as the overheating and other issues...I had the same. When I went to the latest Operative 20140318v2, most of the issues fixed themselves. Now, the overheating happens only if I am on a call for more than 10min.
Battery issues have become almost not existent when I patched up. However, I did find that of you upgrade to SL PRO...the juice seems to run out quicker....
I would install a good battery app that monitors ALL processes and hardware using power. I was able to solve a few issues this way.
But, overall, I really don't think you're being watched.
Good luck....
Sent from my HTC One using Tapatalk
Well I already know you're crazy but...
Even with Ensec or Operative the firmware is still unstable. I randomly get greatly increased battery drain yet even when connected to WiFi with full packet logging nothing stands out as odd. The screen not waking up happens from time to time as well as soft locks are being caused by some apps. I suggest you install a system monitor app and see if a particular app is to blame. On one TS, G+ randomly sits there and updates the feed for hours without ever actually updating. One another, it's weather, then on yet another, no issues at all yet all three are on the same firmware and same patch version and option.
The probability that your TS is hacked is fairly low and I suggest looking at the more likely causes first.
Perfectly normal behavior of Android device
BTW - force (hard) restart on many Android device is vol up + power.
Vol down + power will take screen shot.
Of course, there's many Android devices so maybe that combo also works...
TS is half finished device and we are all lucky we have Loki here...
If we were depending on Omate that wouldn't be good...
I'm still waiting my October 2100 1/8 release and I'm quite sure I won't even open it...
I'll sell that and develop for something else...(don't like when someone treat me like idiot)
Sent from my C6903 using Tapatalk
funky0308 said:
I'll sell that and develop for something else...(don't like when someone treat me like idiot)
Click to expand...
Click to collapse
Hopefully another Android based smartwatch. Idea man has ideas.
Lokifish Marz said:
Hopefully another Android based smartwatch. Idea man has ideas.
Click to expand...
Click to collapse
Absolutely another smartwatch...
I was really patient with Omate but this is too much...
If I have to wait almost eight months for Xperia Z2 I would f***ed them off and that's device that will work fantastic from the box.
But to wait something eight months to have 30% finished device (in a hardware and software way) - naaah...I'm (probably) out...
That's too bad, I really liked that idea and specifications but, if anyone wants to be honest - it just don't worth all that "hype"...
To completely relay on XDA devs to fix tethering and paring, to patch their incapacities and mistakes...to found their company and then wait for them while they are selling watch (newer and better) for a months...
Way tooooo much for me...
Sorry guys for spamming thread
Sent from my C6903 using Tapatalk
@funky0308 - Totally hear you. Maybe the Neptune Pine (quite a bit larger but still) may be better when it's finally released. The TrueSmart is unstable in some ways.
Sent from my SGH-T999 using Tapatalk
deedscreen said:
@funky0308 - Totally hear you. Maybe the Neptune Pine (quite a bit larger but still) may be better when it's finally released. The TrueSmart is unstable in some ways.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Lokifish Marz said:
Well I already know you're crazy but...
Even with Ensec or Operative the firmware is still unstable...
Click to expand...
Click to collapse
Haha, we all are a bit crazy. Could make sense.
@mghtymse007 - I used it for a few days before the patch but I should do a factory reset and try to re-patch just to be extra safe.