Phone "hangs" after hanging up? - Touch Pro, Fuze General

Sorry if this has been discussed before, but i checked some performance related threads and nobody mentioned it.
After hanging up a call, why does the entire device hang for about 10-13 seconds before I can use any other function (including making another call) ??
Anything that can be done to fix this?
Thanks for the help!

hello? I'd really appreciate someone to reply to this, just so at least I know I'm not the only one with this problem. Thanks!

did you do any radio changing?
It seems to be an issue with some radios on some phones. I have a list of radios that I use that will crash the phone after so many calls.

No, no radio changing. In fact I don't even know what that means.
The phone doesn't crash, it just hangs after a phone call for about 13 seconds like it's trying to process something. Doesn't anyone else experience this?

have you downloaded a bunch of app to run in the background of your phone?
it does sound redundant, but if you take a look at your task manager it'll show you how much of your ram is being used up. if it's somewhere high like 75% then you need to close whatever program is taking up the most memory.
another possible thing might be active sync. I heard that when active sync tries to sync while not connected it can cause slow downs and that might happen during or when you hang up a call.
good luck

Just tested it. Active directory was not on, and neither was there any background processes working according to Task Manager, and it still took 10 secs after I hung up the call before I could reuse the phone.
How long is it supposed to take for the rest of you?

a second or less. Active sync is the usual culprit for bad battery life, but it looks like something is running in teh background and making your phone calls take longer to quit.

download and install advanced config, and look in one of the settings which is called "hangup delay" or something like that default is 1500 mS (1.5 seconds) change it to 500 mS or what ever you want and see if that makes a difference

BlackAccord said:
download and install advanced config, and look in one of the settings which is called "hangup delay" or something like that default is 1500 mS (1.5 seconds) change it to 500 mS or what ever you want and see if that makes a difference
Click to expand...
Click to collapse
I've done that now, and all I've done is improve the "hang time" by the number I've reduced the "hangup delay" by. The hang-up delay was originally 3000, and I reduced it to 1000, so my "hang time" is reduced by 2 seconds, but I still have to wait around 9-10 seconds before the phone is usable again.
How come no-one else is experiencing this? There's nothing special running on my phone.

I have the Telus device and have the ' hang' problem as well. I have seen updates on the HTC website for different carrier versions that may correct this problem. None for Telus yet though.

do you have any sort of battery meter running at the top of your screen? ie tnt battery meter?
that app KILLS KILLS KILLS performance on the TP for some reason...

Yes I have a battery meter at the top of the screen, but it's the stock one. I don't know what a "TNT" battery meter is. Should I disable it, and if so how? And after I do, how would I know how much power I have left? And are you saying that those of you who did not turn of the battery meter had performance problems when hanging up?
Thanks!

monkeychucker said:
I have the Telus device and have the ' hang' problem as well. I have seen updates on the HTC website for different carrier versions that may correct this problem. None for Telus yet though.
Click to expand...
Click to collapse
Thank-you! I am also with Telus! If anyone has any suggestions - please help! This is the number one problem with the phone, as well as dropped calls on occasion. I like all the non-phone (ie. PDA) functions though (except that all my outdoor photos turn blue)

Found this which seems to help:
Dealt with HTC for the same issue you're talking about. Turn the "Auto save contact" off and make sure you wipe you call history and the issue will go away.

ajy101 said:
Yes I have a battery meter at the top of the screen, but it's the stock one. I don't know what a "TNT" battery meter is. Should I disable it, and if so how? And after I do, how would I know how much power I have left? And are you saying that those of you who did not turn of the battery meter had performance problems when hanging up?
Thanks!
Click to expand...
Click to collapse
im talking about a meter that runs across the very top of your screen so that if it's halfway across your screen you ahve 50% battery left. if you don't have any idea what i'm takling about then ignore this lol

Related

No email in standby...

Hey all,
Recently i've been having some problems with my emails coming through to my handset. I have the settings set to send/receive every 5 minutes.. but for some reason if my screen is turned off (phone on standby) no email comes through but when i turn my screen back on the emails come.
Has anyone else has this problem? I've never had this problem before it started out of no where...
Which software are you using as your email handler?
The original software that came with the phone.. I havn't installed anything on the phone its at its original state...
jayt2008 said:
Hey all,
Recently i've been having some problems with my emails coming through to my handset. I have the settings set to send/receive every 5 minutes.. but for some reason if my screen is turned off (phone on standby) no email comes through but when i turn my screen back on the emails come.
Has anyone else has this problem? I've never had this problem before it started out of no where...
Click to expand...
Click to collapse
are you using wifi or data connections? If its wifi do you have wifi enabled during standby?
i am using data...like i said if my screen is turned on theres no problems at all but its just when the screen is off in stand by mode no emails will come through..
This is a huuuuge issue which stems from the dawn of WM6. To be honest, it works sporadically for me. A few hours of no email, then a whole group arrives at a time. Sometimes it wont check by itself all day. Other times it will go 1-2 days without missing a beat. This makes it really hard to determine if what I have been doing fixes it.
Here are links to threads I have dug up:
http://forum.xda-developers.com/showthread.php?t=420513
^This is not a good fix imo, as it forces your data connection to be awake 24/7, killing your battery.
http://forum.xda-developers.com/showthread.php?t=437199&page=2
^ I am using the outlook email scheduler. Not sure if its working, or placebo. It still doesnt stick to every 30 mins, sometimes an hour late heh. At least you can have day/night settings and weekend settings. Maybe not a perfect fix, but increases email checking options.
http://forum.xda-developers.com/showthread.php?t=332362
^ Many Kaiser users had/have same problem, no solution found.
http://forum.xda-developers.com/showthread.php?t=445434
^Same problem, no fix in the Blackstone forum.
Thanks everyone for the help.
There has to be some kind of fix out there somewhere.. its unreliable
could try out the seven beta app
If I might make a suggestion...
Maybe you should edit the thread title to "No email in standby" as "Email..." doesn't really tell the story, more people will be likely to find it and post a solution
Problem solved with my Touch Pro
I also had this problem but I found the settings to change this. But you do need schaps advanced config 3 (and a regeditor) to make it happen. Now i always receive my email, it checks every 10 minutes, even in standby mode, with my own data connection.
With a registry editor go to:
HKLM - Comm - ConnMgr - Providers - [GUID] - Connections - [Connection Name] - Always On
and change this value from 0 to 1
(You can also change this setting with Schaps' Advanced Config under menu (right softkey) - More Settings - Connections.
Here you can select "Always On" for the type of data-connection that you use to receive your email)
The second thing is using advanced config and change the setting under power management:
- AC resuming from suspend timeout
- Battery resuming from suspend timeout
I have changed both to 60 seconds.
Now my touch pro is notifying me of new email, even in standby mode.
Good luck
^ by forcing the eternal data connection, are you not killing the battery? I think the phone should be able to connect, query, download emails, disconnect at set intervals while in standby. I think it is supposed to, but for some reason it doesn't do it reliably.
The way I have done it is to use SKSchema to watch for a data connection being connected and turn on the screen when this event happens. This wakes th ephone up and is able to download email. Then I use advance config to close inactive data connection after 10 seconds. As the phone is awake the data disconnects fine. As long as your phones screen is set not to power off quickly, mine is a minute it should be fine.
In the last day I got fed up with TF3D again and turned it off, email seems to check every 30 minutes. I'll let it go for a few days to make sure its not placebo effect.
Anybody here having this problem while manila disabled? Perhaps there is some obscure power saving setting running in the background of manila
Well i have no idea how to fix this problem.. i have played with my phone to try figure it out but nothing.
I will probably have to take rvjacobs advice and see if that works.
It looks like quite a few people are having this same problem.
Its weird.. If my phone is on standby no email comes through..but if its on standby and an SMS comes through, the screen doesnt wake but the email also comes through..
not sure whats happening there.
Mine does it with TF3D disabled also. Thats why I have to use SKSchema to turn the screen on when it detects an internet connection. This way, mail comes through fine and it also auto disconnects the data.
I can now confirm that the issue is still there, regardless of TF3D. Damn, I've tried everything, maybe this is a dead end... Maybe wm 6.5 will see a solution
Maybe it helps you to look for/change the following key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts]
"ACResumingSuspendTimeout"=dword:00000001
"BattResumingSuspendTimeout"=dword:00000001
If you've got these values in the registry, try to cange them to
"dword:0000001e"
It's the time in seconds the device keeps running (without turning on the display) when it's automaticly woke up from the suspend mode (i.e. to look for mails). And if the value is "1", the time might be to short for picking up your emails.
With the new value you set the time up to 30 seconds.
The key exists since WM2003 and most of roms had a higher value in the past. But in the last time more and more roms come with a value of 1. I think its because the manufacturers want to get a good standby time for the devices...
I hope it works for you and you won't have to wait for WM6.5
Thanks for that deroland! I did manage to find them in the reg but it just says "Value Data 1".. doesnt say anything like "dword:00000001"?
I am new to this whole thing so it may be a stupid mistake im making..
jayt2008 said:
Thanks for that deroland! I did manage to find them in the reg but it just says "Value Data 1".. doesnt say anything like "dword:00000001"?
Click to expand...
Click to collapse
Then your value is like "dword:00000001". This is a hexdecimal dword key.
So your device has one second to look for new mails.
Try to change it to "1e" and I hope it will help you.
jayt2008 said:
I am new to this whole thing so it may be a stupid mistake im making..
Click to expand...
Click to collapse
The only stupid thing is that there is no open support by the manufacturers of the devices and microsoft for windows mobile. They only want to make their money ignoring the problem we have by the stuff they sell.
deroland said:
Maybe it helps you to look for/change the following key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts]
"ACResumingSuspendTimeout"=dword:00000001
"BattResumingSuspendTimeout"=dword:00000001
If you've got these values in the registry, try to cange them to
"dword:0000001e"
It's the time in seconds the device keeps running (without turning on the display) when it's automaticly woke up from the suspend mode (i.e. to look for mails). And if the value is "1", the time might be to short for picking up your emails.
With the new value you set the time up to 30 seconds.
The key exists since WM2003 and most of roms had a higher value in the past. But in the last time more and more roms come with a value of 1. I think its because the manufacturers want to get a good standby time for the devices...
I hope it works for you and you won't have to wait for WM6.5
Click to expand...
Click to collapse
This is a setting which can be changed in advanced config, under power. I have mine set to 90 seconds, to no avail. I think this is what is causing it to work sporadically, as opposed to not at all.

Auto/background sync stops after battery dies

I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?
WibblyW said:
I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?
Click to expand...
Click to collapse
Are you sure that this simply isn't they power save feature kicking in?
This can be configured using various settings from within
Settings > Power > Power save
Sent from my HTC Desire S using XDA App
Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.
WibblyW said:
Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.
Click to expand...
Click to collapse
Oh, must admit that I have not noticed this, although I do use tasker application to enable and then disable my various radios and sync settings based on time in order to save battery
Sent from my HTC Desire S using XDA App
This is happening on my Desire S too.
Have you found a solution as of yet?
frosticus said:
This is happening on my Desire S too.
Have you found a solution as of yet?
Click to expand...
Click to collapse
Nope. There's a LOT about the Desire S that kinda half works properly. I find its implementation really kind of sloppy. Definitely NOT a phone I go round recommending to anyone.
To ben_pyett's comment I considered Tasker. Apart from the fact that there are lots of comments that some of it's functionality is broken in 2.3 because Google messed with their APIs, when I thought about it I was pricipally going to get it to try and fix/work around all the stuff that doesn't work well in the Desire S, rather than add functionaliy. E.g.
- Auto display brightness always has the brightness too high (esp in dim ambient light) and there's no way to adjust its 'gain'
- Cycling Buetooth and WiFi and GPS availability (using various strategies based on location and time) only to mitigate poor battery life in the standard product
- Getting it to out of power save mode properly
- Stopping it making the SMS received notification noise when it was just receiving a txt delivery receipt
Sadly there's other stuff Tasker can't 'fix'.
I find myself rebooting the phone manually every two or three days when it begins to exhibit weird behaviour. It might be crashing and rebooting between those times too. I used to have a SIM PIN activated, but it would prompt for that before allowing me to even get calls after a crash, so I missed important calls before I noticed it was in that state. Now with the SIM PIN disabled it might still be crashing but I don't spot it at least.
I was a Blackberry user for years, and should never have changed. At least the BB was stable and all its features seemed to work properly (and had excellent battery life even with WiFi and Bluetooth on 24/7). I though the extra Google integration with Android was attractive and would be worth it. How wrong I was. :-(

HOW to check your battery life ( HTC HELP CENTRE )

Today i contacted HTC Center to ask them about the battery drain issue and overheating happes after updating to ICS they didn't give me a quit good answer for all they questions but,, they give a way to check battery life ..
NOTE: if ur device dzn't pass this send it back to repair
1ST A range of 10-20 hours of battery life is normal based on individual usage patterns, you may try dialing *#*#4636#*#* to check the battery information including health and status.
To optimize the performance of the battery follow the below:
1. turn off Wireless connections (Wi-Fi, Mobile Network, Bluetooth) when not in use
2. Stop services and apps running in the background by going to menu> settings> applications> Running services> tap the service you want to close> tap stop/Close.
3. Adjust the display settings to where it uses less battery and meets your needs
Here are also some tips for you to conserve battery life if you are experiencing this issue.
? Try rebooting your phone every few hours. Rebooting your phone clears the phone internal memory and shuts down programs that may be running in the background and using battery.
? Try turning off the data connection when not in use. Data connections in the background and syncing can cause the phone to use more battery even when sleeping.
? You can set your display to brightness to auto. Allowing the phone to adjust the brightness allows for optimal viewing while conserving as much battery as possible.
IMPORTANT
You may also try the battery test, by following the instructions below:
1. Restart your device
2. Turn on Airplane Mode
3. Connect your device to the charger, and charge it fully
4. Set Screen Brightness to Max.
5. Set Screen Time out to never.
6. Dial *#*#3424#*#*, choose battery run down test, and follow the instructions.
NOTE: If the device loses more than 40% of battery in an hour, then send your device to the repair center for repair.
pplzzzz post somthing to keep the thread alive.
IF you like it HIT
THANKS​IT Manager Musa91
Sorry to burst your bubble but these step will actually reduce the battery , if your phone drains a lot and heats up you have a faulty device that's it.
If you reboot often phone consumes a lot more by loading everything AGAIN it wont save your battery at all.
Autobrightness doesn't always work , its better if you manually set it to 35%- 40%.
Turning off wireless and data will conserve battery that's like smartphone 101 , who doesn't know that?
Android and particularly ICS automatically terminates unnecessary background processes, there is no point in killing them. In fact if you do that often it will consume more battery to start them again if they are needed. Just remember to swipe away apps after you're done, ICS will take care of the rest.
As for the battery tip , after you initiate the test phone will ask you to turn airplane mode on, it will also keep the max brightness level and wont turn off the screen so there is no need to perform the steps you've posted.
posting to keep it alive lol
i didn't either convinced with there answers as i told they wasn't direct ....
this is just a test nothing else...
and about overheating and reboots it's only happen to allot of people after ICS update
i do normally after flashing any rom set the brightness to 35% ..
lol
i did the 1 hour test and my battery level get down to 74%
the battery heat was between 32.3 to 43.7 C
Pikabat said:
Sorry to burst your bubble but these step will actually reduce the battery , if your phone drains a lot and heats up you have a faulty device that's it.
If you reboot often phone consumes a lot more by loading everything AGAIN it wont save your battery at all.
Autobrightness doesn't always work , its better if you manually set it to 35%- 40%.
Turning off wireless and data will conserve battery that's like smartphone 101 , who doesn't know that?
Android and particularly ICS automatically terminates unnecessary background processes, there is no point in killing them. In fact if you do that often it will consume more battery to start them again if they are needed. Just remember to swipe away apps after you're done, ICS will take care of the rest.
As for the battery tip , after you initiate the test phone will ask you to turn airplane mode on, it will also keep the max brightness level and wont turn off the screen so there is no need to perform the steps you've posted.
posting to keep it alive lol
Click to expand...
Click to collapse
u keeped it a way way over life
Pikabat said:
Android and particularly ICS automatically terminates unnecessary background processes, there is no point in killing them. In fact if you do that often it will consume more battery to start them again if they are needed. Just remember to swipe away apps after you're done, ICS will take care of the rest.
Click to expand...
Click to collapse
While I agree with you on most of the other points, this one needs a bit of explanation. Although, the memory management in ICS is far better and is a bit like what Windows Vista and 7 do, at times you do need to kill some messy programs which play with system privileges and hog battery, like the famous facebook application.
GB and ICS use in-memory program caching like Vista and Windows 7, i.e. they keep frequently running programs in RAM and use as much memory as possible (or in sane limits in case of 7) for this task. It is freed automatically if a program requires more RAM. Thats why even when a large part of memory appears to be consumed most of the times on ICS/GB and Vista/7, large program still run perfectly well. The OS is just consuming the RAM that is lying around when no program is using it. GB and ICS even introduced a "Cached Applications" view in their "Running Apps" screen to take a look at these cached apps.
This makes the killing of background processes optimized for the OS as processes which are not used for long time can be marked inactive first and then cached. These cached processes can then be removed in cases memory is required by some program.
But there are some nasty apps like the Facebook app which not only keeps processes in background, but also keeps them active and mark the services spawned from the main executable as system services hence they are not killed at all. Facebook's background upload system, the so called "push notifications" service, all these take CPU and other resources all the time and dramatically reduce the battery life. Hence killing these manually is still required.
This is my personal experience or perception or whatever.
krazy_about_technology said:
While I agree with you on most of the other points, this one needs a bit of explanation. Although, the memory management in ICS is far better and is a bit like what Windows Vista and 7 do, at times you do need to kill some messy programs which play with system privileges and hog battery, like the famous facebook application.
But there are some nasty apps like the Facebook app which not only keeps processes in background, but also keeps them active and mark the services spawned from the main executable as system services hence they are not killed at all. Facebook's background upload system, the so called "push notifications" service, all these take CPU and other resources all the time and dramatically reduce the battery life. Hence killing these manually is still required.
This is my personal experience or perception or whatever.
Click to expand...
Click to collapse
What you're saying is true but its still not accurate. As you mentioned facebook is marking its processes as system service which means it gonna try to start again automatically. As I said before there is no point in killing, also facebook made some improvements in this area. I remember that old version was using about 40mb of ram when it was idling but now it uses about 8-9mb. As for the push notifications I've disabled them so I cant comment on that but I do know that its not always working.
Pikabat said:
Sorry to burst your bubble but these step will actually reduce the battery , if your phone drains a lot and heats up you have a faulty device that's it.
Click to expand...
Click to collapse
You may as well talk to a wall.
This guy makes stuff up and posts it as fact, then begs for thanks for his posts. He claims he's an expert but doesn't know the most basic things about how Android phones work.
I mean for crying out loud....ICS is well known to add about 20% to battery life. It's one of the best features of the new version. There were countless threads about the improvement people saw when first switching to ICS a few months ago when it first started to come out. Yet this thread basically suggests that it's a known fact that ICS causes increased battery drain.
Taking his advice is somewhere between counterproductive to your goals and downright dangerous to your device depending on what he's suggesting.
Guys, please stay on topic. There is no need to call this guide "dangerous".
His points might not bring any advantage but they are not dangerous either.
Neutral discussions are okay, but please don't start attacking each other.
We are in a forum were we want to help each other and not having contests on the best guides or whatever.
I won't comment every single point made here, but both sides have their rights and wrongs.
So please keep this technical.
Personal attacks are not tolerated on XDA.
Diamondback said:
Guys, please stay on topic. There is no need to call this guide "dangerous".
His points might not bring any advantage but they are not dangerous either.
Neutral discussions are okay, but please don't start attacking each other.
We are in a forum were we want to help each other and not having contests on the best guides or whatever.
I won't comment every single point made here, but both sides have their rights and wrongs.
So please keep this technical.
Personal attacks are not tolerated on XDA.
Click to expand...
Click to collapse
When you suggest mixing and matching elements of different versions of hacked firmware, that most certainly is dangerous. (For the phone anyway)
So much can go wrong doing a thing like that.
And when someone is recomending doing that as a sollution to every new problem someone suggests without regard to ROM, current firmware, the specific problem, android version, etc etc.....that is irresponcible.
Thats what this guy is doing in several other threads. This thread isnt one of the damgerous ones. Its one of the counterproductive ones I mentioned.
Someone will screw up thier phone with this advice. Pointing this out is not insulting to 1 person. Its being helpful to hundreds.
If we just sit silently and not say anything about bad advice, we wouldnt be very good forum members.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Skipjacks said:
When you suggest mixing and matching elements of different versions of hacked firmware, that most certainly is dangerous. (For the phone anyway)
So much can go wrong doing a thing like that.
And when someone is recomending doing that as a sollution to every new problem someone suggests without regard to ROM, current firmware, the specific problem, android version, etc etc.....that is irresponcible.
Thats what this guy is doing in several other threads. This thread isnt one of the damgerous ones. Its one of the counterproductive ones I mentioned.
Someone will screw up thier phone with this advice. Pointing this out is not insulting to 1 person. Its being helpful to hundreds.
If we just sit silently and not say anything about bad advice, we wouldnt be very good forum members.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Click to expand...
Click to collapse
you are a 1 of two ::: either u r racism or u can't read coz this is not me invented this way of test IT's HTC HELP CENTER AS I WROTE IN THE TITLE READ well
"Today i contacted HTC Center to ask them about the battery drain issue and overheating happes after updating to ICS they didn't give me a quit good answer for all they questions but,, they give a way to check battery life .. "
and the other thread you talk about is proofed with video and photo's and cleared how to use it with the right firmware with specific ROM so stop this chasing out and don't make ur self looks like a hero we all here support each other to provide a good solution for other's so keep it that way end of discussion.
Ok final warning regarding attitude to all.
If I see any more of this there will be consequences to all.
Consider this a final warning...
Skipjacks said:
When you suggest mixing and matching elements of different versions of hacked firmware, that most certainly is dangerous. (For the phone anyway)
Click to expand...
Click to collapse
Not true. No documented cases of it harming the Sensation. 3.12 and 3.32 are very similar. Also, with the development mode flash fix coming out any day now, even if someone bugs up their hboot or something, it'll be recoverable similar to how Samsung phones to use ODIN to completely flash back.
.......
sshede said:
it'll be recoverable similar to how Samsung phones to use ODIN to completely flash back.
Click to expand...
Click to collapse
i completely agree with you since i experanced that myself many times when i 1st buy the sensation so many wrong flashes then it's recoverd and back to work just fine

[Q] Battery life horrendous

Hi all
I've tried 2 Surface RT's now, and both have horrendous battery problems. I've tried refreshing them, resetting them, installing all updates, turning off Bluetooth and many of the live tiles, but still the battery lasts at most 24 hours. There's nothing much installed, just a few apps (ebay, Flixster, a book reader), I have two email accounts (Hotmail and an exchange account), and that's about the lot. All updates have been performed, but still, on two separate units, the battery life is so bad that I'm thinking I can't use this as my daily tablet.
I've done the powercfg -energy test, and I get 2 errors - one is that the Nvidia Wave Device driver is preventing the system from sleeping, and the other being for high utilisation (between 18%-30%). If I turn the volume off, the Nvidia driver warning disappears, but the battery life is still poor and I don't know why the volume would need to be off when not in use. I can't find any other apps that rely on this driver (it's a speaker driver as far as I can tell), so I'm well and truly stumped.
Does anyone have any ideas on how to fix this Nvidia driver problem?
Thanks
Do you use any music apps or web pages on the tablet? If music is playing, or even paused, the app may prevent sleep. However, generally speaking, such apps should be suspended when idle for any meaningful period of time.
Even with some third-party Win32 programs running in the background on my Surface RT ("jailbroken" and then installing things like MirandaIM, which don't get suspended automatically) the tablet lasts at least three days if fully charged when I put it to sleep (I don't usually try to push the battery life, so I'm not sure what the max is) and without background network-connected processes it lasts for over a week.
Hi
Thanks for taking the time to reply. No music apps are or have been running. Since wiping it all and starting from scratch just last Thursday I've only used it for emails, web browsing and reading books on a book reader. Just can't understand why I've had such bad battery results with two separate units!
My guess would be along the lines of what GoodDayToDie said, some app you use is probably holding a wakelock on the device.
Can you list out the non-MS apps you're using to see if we might be able to find out if it is one or not?
Morning
The only apps I've installed from the store are ebay, Flixster, Book Bazaar Reader and Facebook.
Maybe I'll try to uninstall these, running the powercfg -energy report after every uninstallation. I'll report back!
tjjpowles said:
Morning
The only apps I've installed from the store are ebay, Flixster, Book Bazaar Reader and Facebook.
Maybe I'll try to uninstall these, running the powercfg -energy report after every uninstallation. I'll report back!
Click to expand...
Click to collapse
Right, all apps listed above removed, ran the powercfg -energy report and still getting the Nvidia driver error, and processor utilisation at over 20%. No apps were running in background, and same results even when volume was off.
Am completely at a loss now!
Have you run Windows Update? Normally it's not even optional (you can disable it if you use the registry, but that's the only way) but the only thing that comes to mind is that your tablet may be missing some required driver update or something... that's very odd though; I haven't heard of any such problem from anybody else.
Given that the nominal runtime of Surface RT when not in sleep mode is 8-12 hours, you're definitely not going to have a good experience if sleep mode isn't working. Technically you *can* shut down the tablet between uses - it boots up very quickly, at least - but that's a pain compared to sleep mode.
GoodDayToDie said:
Have you run Windows Update? Normally it's not even optional (you can disable it if you use the registry, but that's the only way) but the only thing that comes to mind is that your tablet may be missing some required driver update or something... that's very odd though; I haven't heard of any such problem from anybody else.
Given that the nominal runtime of Surface RT when not in sleep mode is 8-12 hours, you're definitely not going to have a good experience if sleep mode isn't working. Technically you *can* shut down the tablet between uses - it boots up very quickly, at least - but that's a pain compared to sleep mode.
Click to expand...
Click to collapse
Hi
Yes, I have run all updates, including the firmware update dated early April. I have looked for updates in both the normal 'tablet' mode and also by going into the update section of the desktop. So everything is uptodate, all of my apps from the app store have been uninstalled, but still the Nvidia driver error reports that it won't enter sleep mode and processor utilisation remains high.
As stated in my first post, I currently have two of these tablets to play with, and I have exactly the same issue on both, so I think we can rule out hardware problems, leaving some sort of software glitch. I did see this Nvidia problem on another forum, but the guy who posted it later reported that it simply went away, so that doesn't ger me anywhere.
It seems like a great piece of kit, but it'll be going if I can't resolve the battery issue.
Hi
Although I don't have any battery drainage I have to confirm that I have the same 2 errors despite the fact that I have all the updates. Can anyone else confirm if they have these errors?
That's odd. If you have the same errors but not the same battery drainage, I wonder what is causing my battery drainage and how I could check this out?
It does definitely seem to be linked to my driver error. The same problem has returned - the Nvidia driver error reporting its preventing sleep mode when the volume is on. When volume is off, that error disappears and battery life seems a little better.
Have played around with it some more, but same issue still present on both of the Surface RT's I have - battery drain unbearable. I have to ensure volume is off whenever closing the lid/pressing power button to put it into sleep mode just to try and see sleep mode actually kicking in.
If I had installed lots of third party apps I could understand some battery loss, but given they have both had full wipes, all updates installed and haven't got any apps installed other than pre-loaded ones, I just don't understand how I have the same issue on both machines. Only other thing to try would be removing my email accounts, but then there would be no point at all in keeping it!
Does anyone have any suggestions at all? If not, I think it will be time to see them going.
My only thought is incredibly bad luck and both devices have the same hardware fault.
My surface sips battery. Have never had any issues with battery
cx1 said:
My surface sips battery. Have never had any issues with battery
Click to expand...
Click to collapse
That must be nice, both of mine use so much juice they render themselves useless!
I can't think it's a hardware issue on both, especially as the huge loss of power seems linked to when the volume is on 2 or above and sleep mode is for some reason prevented.
Anyway it seems there may be no solution to whatever software glitch I have, and all of this has very much made me look at the Surface with a huge amount of disgust, so I think I'll go back to my Galaxy Note which just doesn't have such ridiculous issues as these units.
Well no-one else seems to be experiencing these issues so whatever is wrong is something with your devices. I would contact the vendor.
SixSixSevenSeven said:
Well no-one else seems to be experiencing these issues so whatever is wrong is something with your devices. I would contact the vendor.
Click to expand...
Click to collapse
The same hardware fault on two devices when the error report is linked to Nvidia wave device driver error preventing the units from going into sleep mode? Doesn't seem all that likely to me. I still think it's a software error, as this was reported also by somebody on a different forum, but with no clear resolution.
Thanks anyway.
Apart from the error, good practice for saving battery life can also be setting the screen brightness to low. In your Nvidia settings do you have the option to enable and disable power saving?
tjjpowles said:
The same hardware fault on two devices when the error report is linked to Nvidia wave device driver error preventing the units from going into sleep mode? Doesn't seem all that likely to me. I still think it's a software error, as this was reported also by somebody on a different forum, but with no clear resolution.
Thanks anyway.
Click to expand...
Click to collapse
One could argue that the software error is environmental, as it only seems to be a minority experiencing this issue. There could be a hardware fault though, don't discount just because it is two devices, you could have been incredibly unlucky and received two devices that just happen to have the exact same fault.
Well I've done some more playing about with the device, and it seems my battery drain issue seems linked with my work email account. If I am just running my normal Hotmail account, battery drain seems fine. When I add my work Exchange email/diary account, the battery drains like nothing on earth. Not sure if this has anything to do with the fact that to even get this work email account working, I had to get our IT chap to send me the security certificate for me to install.
Not sure if anyone might be able to suggest a way of having push emails still running on my work email account without the battery draining hugely?

Cyanogenmod bugs

Can someone please explain to me whats meant by cdma bug? And also what wifi mac adress is? I mean how will these affect the device.. Not looking for technical info simple and short
Thank you
The CDMA thing is just if your mobile network uses CDMA, and that's just an issue where you have to set preferred network type on first boot.
The MAC address is the address that your device uses on a wifi network (a bit like an IP address). The issue is that it's randomised every time you reboot, so some router things like QOS and whitelisting won't work, but for normal use it doesn't really matter.
Hope this helps ☺
SniperShotgun said:
The CDMA thing is just if your mobile network uses CDMA, and that's just an issue where you have to set preferred network type on first boot.
The MAC address is the address that your device uses on a wifi network (a bit like an IP address). The issue is that it's randomised every time you reboot, so some router things like QOS and whitelisting won't work, but for normal use it doesn't really matter.
Hope this helps
Click to expand...
Click to collapse
THANK YOU I will give CM A try then I thought the CDMA meant no signal lol and the MAC address thing meant no wifi or would limit both the capabilities
b3ava said:
THANK YOU I will give CM A try then I thought the CDMA meant no signal lol and the MAC address thing meant no wifi or would limit both the capabilities
Click to expand...
Click to collapse
Well if you don't set the thing at first boot it is no signal, so remember
I have another thing to report:
The headphones are set to VERY high volume. Even if i turn the volume to the minimum during a call, it is still too loud.
I often have awake and screen on, but i dont actually have screen turned on. How can i see which process is doing this or fix it?
AgiZ10 said:
I have another thing to report:
The headphones are set to VERY high volume. Even if i turn the volume to the minimum during a call, it is still too loud.
I often have awake and screen on, but i dont actually have screen turned on. How can i see which process is doing this or fix it?
Click to expand...
Click to collapse
Does the "double tap to wake" set to on ?
it maybe because of that
tomhtg90 said:
Does the "double tap to wake" set to on ?
it maybe because of that
Click to expand...
Click to collapse
It is, yes. But i was most active on phone that day from 8-16, and in that time you can see that awake and screen-on just kept increasing and didnt "shut off" at all later that day even though not much was going on with the phone. If i remember i even restarted the phone (that sliver missing on the graph).
Right now i have this kind of usage, the way it is supposed to be (ok, not sure whats wrong with the signal, but lets leave that alone for now)
Could it be some app not letting the phone go to sleep or what?
AgiZ10 said:
It is, yes. But i was most active on phone that day from 8-16, and in that time you can see that awake and screen-on just kept increasing and didnt "shut off" at all later that day even though not much was going on with the phone. If i remember i even restarted the phone (that sliver missing on the graph).
Right now i have this kind of usage, the way it is supposed to be (ok, not sure whats wrong with the signal, but lets leave that alone for now)
Could it be some app not letting the phone go to sleep or what?
Click to expand...
Click to collapse
I dont know what happen. But what i saw from your 1st SS, the screen doesn't go to sleep.
U can see what apps that use much battery by simply go back from History details.
On my Battery use stat, Screen always be gonna be the biggest usage (and that's normal). If l lock the phone, the phone does go to sleep (means screen is off and not using the battery until i turn it back on).
On Cyanogen dev thread for our device, some people have bad battery life when double tap to wake is on (me too).
Maybe it's not well implemented yet. So that's why i rather choose not to use that feature for a while until it well implemented.
Ok, thanks for your thoughts. I didnt chech which app used the most power, but perhaps it was Exchange not being able to sign in. I will monitor the behavior (during weekend it should be a lot longer battery life).
Yeah, i think dt2w is not optimised. As long as i have full day of battery it should be enough and for now that is the case.
The volume bug is annoying though.
is it only me that has an issue with Notifications on this phone? It seems that when I am on wifi my internet stops or something.. is there a setting or something I have missed?
No, a lot of users are reporting this bug. I suggest you try the app "Heartbeat fixer for GSM" or "PNF Root" which could fix this. I install one or the other as soon as I get a new phone, and I don't have issues with push notifications that I've noticed so far, but I haven't tested the Mi4C on WiFi yet.
b3ava said:
is it only me that has an issue with Notifications on this phone? It seems that when I am on wifi my internet stops or something.. is there a setting or something I have missed?
Click to expand...
Click to collapse
xdadevet said:
No, a lot of users are reporting this bug. I suggest you try the app "Heartbeat fixer for GSM" or "PNF Root" which could fix this. I install one or the other as soon as I get a new phone, and I don't have issues with push notifications that I've noticed so far, but I haven't tested the Mi4C on WiFi yet.
Click to expand...
Click to collapse
Did you try from scratch?
I put on TWRP, deleted EVERYTHING (system, data, cache...) then put on CM and gapps (opengapps - ARM64 - pico) in one go and for me it works like it should.
About my awake problem: I have left the phone more or less alone during the weekend and it seems it works like expected. I will observe if i find any more strange behaviour like i did a few days ago.
Seems that it sometimes works and sometimes it doesn't the two apps that are mentioned above don't seem to be making a difference.. The funny thing is when I am not connected to WIFI the phone seems to be running fine (notification wise). But when the screen is off and I am on wifi the device seems to be going into some sort of deep sleep most of the times. I think after 2-3 days it hasn't been as bad, but I do get 1 or 2 random hangout notifications not appearing at all..

Categories

Resources