I've done searches and read here and on other forums. I am at my wits end. I'm using my touch pro with my laptop but the phone get's hot and turns off. It also doesn't charge while tethering. Does anyone have an actual solution to this problem? Is there a Rom that solves this problem? I love my phone but I travel 2x a month and don't want to pay for the WIFI in these hotels.
Anyone have a solution?
Thanks
Jeff
doesnt sound normal to me, did you contact sprint TS about this issue (wouldnt tell them you are tethering tho)?
get a long usb cable, put the phone next to the AC. the phone should be cooled enough to charge while tethering.
Go to Settings (WM, not TF3D)|System|Power and the Battery tab.
Make sure "When device is turned on, do not charge the battery when connected to the PC." is unchecked.
As cloudy987 indicated, get the phone into a good cool air flow. Maybe even take the back off while tethered. Plastic is not that good a conductor.
there is a hack out there from nuerom that makes it so your battery driver works differently and allows it to charge more or till it hits a little bit of a higher temp or something (too lazy to re read the posts) but there is also a over/under clocking utility on the site that works on some versions of winmo (i think on 6.5+ it causes a deadlock on boot and forces you to factory reset ) but it allows you to change the processor speed to lower while teathered and makes it so the device wont over heat...
http://www.nuerom.com
this was a issue for me while on energy roms,i had to go to tweaks and in the tool folder and disable the fast charge toggle,i have to on most custom roms,but no issues after i turn it off
could be that the USB connector is getting screwed up... the one on my Titan went and it started with not being able to tether/sync, then it progressed to not being able to charge it.
I actually melted my phone with wifirouter and had to replace it. Luckily it was under warranty. Most of the time simply placing it on a small desktop fan kept it cool. Unfortunately for mine the damage was done before I figured this out. Treat it like an overclocked PC. It needs extra cooling to keep it from cooking itself.
I allowed my Lumia 800 to fully discharge overnight. Next day, I plugged into the charger. 2 hrs later, still dead.... later that day, still dead. Next day, tried all sorts (including all in the Seida website as below) Still dead. Took it back. Returned to Nokia.
Anyone else with the same problem - it seems it might be a problem associated with software version (ie a fatal flaw). When I get it back I'm gonna fully discharge again & try to re-charge. If it bricks again, it goes back for a refund.
I'm interested if others have had the same issue, so a picture can be built of the extent of the problem...
http://www.seidea.com/2012/02/14/no...e-battery-drained-devices-cant-turn-on-issue/
Thanks!
Mine has gotten discharged once. Though it turned on as soon as I put the charger in.
Hold power button 15 seconds+.
nope...
Nope.... tried holding power button for >30 secs, tried all other button combinations as recommended. No joy.
Are you using USB power or wall outlet power?
USB...wall etc
Tried both for extended period (several hours) - absolutely nothing.
When connected via USB to my PC, and with dis / re-connecting the cable etc etc (as advised) it started to do a restore, got to 80% then died. The L800 then UTTERLY was bricked. A further day of trying to kick it into life led to nothing so it went back to Nokia. Am told to expect it back / replaced within 7-10 days (this from T-Mob where it's on contract).
I had the exact same problem with my girlfriends lumia and after reading all the posts from Nokia forum and tried everything but the one with the heating of the battery , nothing worked.
So here is the solution that worked for me: I used the USB cable with zune and placed the device on my laptop right in a warm place ) ( by mistake ) after 5 minutes it started and now I told my gf to never let the phone discharge to 0%
Hope this is helpfull to anyone , thank you
Sent from my Galaxy Nexus using XDA App
You might have hit this bug covered by anandtech: anandtech.com/show/5266/nokia-lumia-800-review-nokias-brave-new-foray-into-wp7/2
Sounds like they had to plug and unplug a few times to get it going.
demeics said:
I had the exact same problem with my girlfriends lumia and after reading all the posts from Nokia forum and tried everything but the one with the heating of the battery , nothing worked.
So here is the solution that worked for me: I used the USB cable with zune and placed the device on my laptop right in a warm place ) ( by mistake ) after 5 minutes it started and now I told my gf to never let the phone discharge to 0%
Hope this is helpfull to anyone , thank you
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
heating the phone works. Mine ran flat and refused to turn back on, I heated it with a hairdrier, plugged the USB in (attached to the mains) and it charged! Not sure how long I heated it for but it was HOT.
is it just me or....
... is it reasonable to have a device that:
(i) you have to fret about ensuring it's ALWAYS got some charge, or run the risk of killing it, and
(ii) you have to HEAT IT WITH A BL**DY HAIRDRYER to make it start... ?
The purpose of my post was to see if this is a random, could-happen-to-anyone, fault... in which case, OK, I'll have Nokia sort it... or is it a design fault that (i) I would expect to be sorted before (& certainly after) launch and (ii) means I would look to send the 800 back & select a different WP7 device.
Anyway I hope mine comes back in good shape & that's the back of the problem.
Still interested in other experiences. I'm NOT really interested in HOW people got over the problem (hairdryers, rapid plug/unplug / extended USB sessions etc) - that is now a moot point since I sent mine back. I AM interested in a straight poll on how many other people had this problem... ie is it a design issue?
Thanks!
... yes ccalpha!
Thanks for that anandtech url - that's exactly the issue. Nicely described as a 'reboot loop' - a Catch-22 where there's insufficient charge to kick start the boot / charging process so it shuts down. Exactly.
Just to add, I upgraded my 800 to the latest software version via Zune, 2-3 weeks ago, so I would say that this issue is NOT fixed by the current software.
piattj said:
... is it reasonable to have a device that:
(i) you have to fret about ensuring it's ALWAYS got some charge, or run the risk of killing it, and
(ii) you have to HEAT IT WITH A BL**DY HAIRDRYER to make it start... ?
The purpose of my post was to see if this is a random, could-happen-to-anyone, fault... in which case, OK, I'll have Nokia sort it... or is it a design fault that (i) I would expect to be sorted before (& certainly after) launch and (ii) means I would look to send the 800 back & select a different WP7 device.
Anyway I hope mine comes back in good shape & that's the back of the problem.
Still interested in other experiences. I'm NOT really interested in HOW people got over the problem (hairdryers, rapid plug/unplug / extended USB sessions etc) - that is now a moot point since I sent mine back. I AM interested in a straight poll on how many other people had this problem... ie is it a design issue?
Thanks!
Click to expand...
Click to collapse
It's kinda tacky of you to tell people that it's not ok to share their anecdotal experiences in a discussion based community.
You'd be better suited turning your thread into a poll rather than a conversation.
sorta a fair point... it is interesting to hear what people have to do to get their phones working again. But my point remains - i was clear i sent mine back and that I was interested in sensing the extent of the problem.
Thanks to all those who responded. I'm grateful. When I get my phone back and if it bricks again, I'll be sure to have a range of hair utensils ready...
http://media.xda-developers.com/images/smilies/smile.gif
battery
Actually a poll is what I wanted to establish. I'm interested in mapping battery problems to (eg) firmware or OS revision. It may be that battery problems are prevalent with a particular revision. As I reported, I had the latest OS and my battery failed me.
If there is a generic product issue, we owe it to ourselves to highlight it.
I agree that it's interesting to hear anecdotes of how people fixed (temp?) the problem but my point remains that we shouldn't have to go to such lengths to manage / resurrect / fix our nice shiny (expensive!) Lumia 800s...
battery itself is fine, try turning on airplane mode you will notice expected power consumption, iirc ~4% / 10 hours standby . either component related to radio is faulty ( and i doubt that) either nokia ****ed up something with power management ( and they are to stupid to manage to fix it)
I believe it's generally acknowledged that current crop of smartphones are pushing the limits of battery technology - witness the many forums (Nokia, LG, Apple, etc etc) where the issue of battery drain is debated.
While my L800 is in dock with Nokia for repair or whatever, T-Mobile loaned me a Nokia 2330 (not so smart-phone) and I've had it 4 days now, used it as I normally would use the 800 and it's still showing full battery.
Having said that, I suspect that the L800 is hungrier than many (for some reason) and/or there is a basic flaw that is still not addressed with latest FW...maybe I'm wrong.
So it looks like I'm suffering something similar:
Last night I was charging the phone, and it suddenly stopped being able to open any apps, attempting that just left it with a back screen with white 'loading' on.
Powered on an off, then the phone couldn't get any signal, and the app opening problem remained. Powered off, removed SIM and powered on. Phone shut itself down and has not powered on since.
Left it on charge for a copule of hours, both USB and two mains adaptors, nothing. Tried button combinations, nothing.
It appears to be a brick.
Great.
Rusty! Hmmmm sounds familiar. What version of firmware ? Did you update to the latest a couple of weeks ago?
Feels as though there's a bigger problem than just high battery drain with some devices.
Anyone from Nokia read this forum? ...And care to comment?
worst thing is that it seems almost every device is affected, this is really big fail from nokia. even their official forum has similiar threads
Hello nokia... Anyone there?
As many have said (& on the Nokia discussions) the 800 is a lovely phone, spoiled by serious battery problems.
I've had mobile phones for 20+ years (work and personal) and this is the first time I've had to return one for repair. The 800 IS a lovely phone & WP7.5 is excellent in the main BUT Nokia will suffer if users no longer trust this lovely device.
Mine is with Nokia for [repair / replacement]... I will test the one I get back very quickly after getting it home. If it fails again, it goes back for refund...
Hi All,
Firstly, I'm new here so please accept my apologies in advance if this is entirely the wrong place to open up this thread. Forgive me if I've gone into too much detail here, but thought it made sense to put as much info down - much of the following mayor may not therefore be relevant to the particular problem I'm having.
I have a Galaxy Note 3, which I've had for some 19 months now and it has generally been very good and reliable. I drive quite a lot, and my car is a VAG group car which uses rSAP to connect via Bluetooth - this too has been very stable and reliable.
About 3 months ago I noticed that my battery life had suddenly reduced dramatically, despite no change in use from my part (no new apps, not suddenly watching YouTube 24/7 etc.). I figured the battery had passed it's best, so went to the high street and purchased a new genuine Samsung battery, but this behaved exactly the same as the original battery.
I then noticed, occasionally, that while at home, my WiFi was dropping it's connection to my router, complaining that "Authentication Failed" (despite the WiFi password not having changed). Disabling the WiFi on the phone, and then re-enabling it seemed to fix this.
The following month, I had a notification from my provider that I'd used 80% of my data allowance, and a few days later another warning that I was at 90%. I get 10GB per month in my deal, and AFAIK, I've never in the past come anywhere close to using this up. A few days later, I tried to get online to google something, and landed on an EE page telling me I'd used up all my data for the month, which would reset the following day. I put this down to the WiFi Authentication problem mentioned above.
The following day, the phone told me that an android update was available. I applied this update, and thats when things started going really odd! The phone suddenly became very slow to respond. Sometimes turning the phone on would yield the lock screen with no wallpaper, other times I'd get the wallpaper and nothing else (no digits to unlock the phone for example). And I noticed that when in the car, the rSAP connection would drop off after 10 minutes or so - I put this down to the phone being unresponsive, and called EE.
EE recommended that I return the phone to factory defaults, which I did. After this, the phone is definitely more responsive, but now my rSAP connection drops out after around 2 minutes, and then re-connects. If I am actually on a call, the connection stays up for a little bit longer, but still drops out after 5-7 minutes. If I have the phone plugged into a charger in the car, it stays connected for a little bit longer, sometimes up to 15 minutes, but still regularly drops it's connection.
I noticed that this new o/s has a new feature for "Trusted devices", which I've added the car as, but this made no difference.
It is almost as if, this new version has included some sort of bluetooth power saving feature whereby if nothing much is happening (i.e. I'm not actively in a call), the conneciton drops out after a couple of minutes - unless I'm on external power, in which case it drops out after a bit longer. Prior to the update, it would stay connected, sometimes for hours at a time.
Has anyone else encountered this problem, and can you offer any suggestions as to what I might be able to do to investigate further (eg. are there any bluetooth logs I can inspect?) or better, fix the problem.
Your help is much appreciated
The problem is pretty simple: 99% percent of the time I charge the tablet with the original charger, the Internet slows down to a point it makes impossible to surf the web. No, it's not my WiFi's speed nor any Internet related problem, that would affect every device at home. Perhaps it'd be silly to tell but I haven't (yet) factory reset the tablet due to lack of time to back up my documents. What could it be the problem? This happened since the first day. It's pretty annoying, because you have to unplug the charger in order to use the Internet and it'd mean the tablet won't receive any charge. The tablet has never been hit nor dropped. It's intact and non rooted. Hope I'm not missing anything. Thanks in advance.
Good Morning/Afternoon/Evening
Really losing hope with this device as have never got it working in my existence of having it (around 6 months) for some reason have come back to try now as a pretty big waste of money when I actually would have a use for it.
I’ll do as best I can to outline everything I can think of but if anyone has any suggestions they are more than welcome.
The basics of the problem are that when I connect the box via HDMI to my TV it show the Beelink logo, moves onto a please wait animation screen, then boots to the home screen for about 0.5/1 second before signal dies completely (or at least the TV displays no signal) and nothing I do seems to be able to get it back (unplug HDMI and plugging back in (at both TV and box end), cycling extensions on my TV). I have tried around 5 different HDMI leads, 6 different TV’s/Monitors (Samsung/LG TV’s (from UK), a Chinese imported monitor and an ASUS monitor all capable of outputting at least 1080p, TV’s can output in 4K), 3 different power cables but all to the same outcome.
I have flashed different firmware versions with no issue to try rectify the problem but still the exact same thing happens, factory reset the device multiple times (although it isn’t setup anyway due to the input error), if I go into recovery the display holds perfectly, doesn’t cut out at any period of time (essentially could leave it on forever and it wouldn’t cut out as far as testing, leaving around 10 minutes and then moving option as didn’t know if it would go to sleep if I didn’t press anything but this remained on for at least 40 minutes with no issue with display).
I’m lost as to what I need to do to get the box to work and while I am tech savvy enough to get by, wondering if someone far smarter than me has any suggestions of what else the problem could be. As far as my knowledge I would think it was software related due to the screen cutting out but holding/showing recovery or boot animations fine, but could be wrong. Didn’t know if it could be something like the firmware trying to set the display to auto but all my displays not recognising whatever signal it is trying to output?
Hopefully someone might have some idea’s for me to try.
Thanks