Database Users

WiFi and Battery discharge

Hi Guys,
A weird problem I encountered with my recent play with acbPowerMeter.
In normal state my Elf consumes about 140 mA +\-20 (Due to various CPU load).
However, after turning WiFi ON this value jumps to 400mA, well nothing you can do about. So, I understand that after turning WiFi OFF, the battery drain should come down to normal value. This is not a case at all. Battery discharge stays on around 400mA.
Only swithcing Off/ON Flight mode resets WiFi module. A quite starange behaviour !
My question is anyone came across this problem and knows the solution apart of switching Radio module On/Off every time after using WiFi to save battery charge?
Thanks.

I heard this problem before and it should be fixed by flashing the updated stock ROM of htc or flashing the new onyx 4.6 ultimate.
Dont try Onyx 5.0 first.

jeremy89632 said:
I heard this problem before and it should be fixed by flashing the updated stock ROM of htc or flashing the new onyx 4.6 ultimate.
Dont try Onyx 5.0 first.
Click to expand...
Click to collapse
My Elf is way too slow on stock ROM (official HTC version you mean as I understood) neither I need all the stuff from ultimate Onyx version. Micro version is OK for me.
Before I had similar problem with Blue elves v5.
Pity, the problem still there :-(

Before using onyx, im using blue elves too.
and everytime i had an issue like that, soft reset.
But after using onyx, its so easy.

@OP: How did you figure out the exact power that your phone consumes?

cyanide911 said:
@OP: How did you figure out the exact power that your phone consumes?
Click to expand...
Click to collapse
This can be done by a free software mentioned in first post ( acbPowerMeter)
search it in forums

Here is my power consumption usage.
WiFi - 2hrs
Normal usage, a day or 1.5 days.

Warning!!! New Camera Fix fr HTC makes LED flash useless

Warning!! Do not install the new HTC Camera fix for HD2, it disable my HD2 LED flash, i can't turn it on now even after removing the FIX...
Anyone has any solution for this?

Is your battery level below 30%?

Is your battery above 30%?
Oh... someone beat me to it.

My flash is fine...

I've got the fix installed and my flash is working as before (way too bright btw)
Is your battery below 20% (well I think it's 20%)? In which case the flash won't work.
Edit: too slow

It's not by installing the hotfix but may be by installing it.
Have u tried another softreset/hard reset?
Just now I took few photos to check and I don't have issues with flash.

I remember the battery needs to be >50% for the flash to work.

Mmm... how about this: test it when the battery is fully charged

thks guys...my battery was below 20%, after charging its ok now...i reinstalled the Fix, its ok now...

kison said:
thks guys...my battery was below 20%, after charging its ok now...i reinstalled the Fix, its ok now...
Click to expand...
Click to collapse
Great.
Now, please ask some MOD to close this thread as it may bring confusion.

[Q] andriod on htc hd2 struck on black screen after a call

Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you

mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?

I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port

It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english

I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.

Bump!
Anyone? :/

I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!

I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127

I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13

Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.

Your setup works for me as well - until we`ll see a fix for it this will do

Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!

hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?

xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat

with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make

try to change the kernel. that works for me

hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^

Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .

papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired

Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.

RESOLVED : Problem with autofocus in standby mode

Hi,
For two days, I have the autofocus of the camera that works all the time in standby mode only This is "click" at regular intervals
Including when I reboot, I hear just before you see the first screen of boot ...
By cons, as soon as I leave the standby mode before, no problem except that the camera is no longer the point, the autofocus does not work ...
And really weird is that this "click" I think varies according to the occupation of the CPU because if I leave an application running and I goes to sleep, I do not hear it!
I made a task29, wipe all over the place, install new rom, and also an original rom ... Even removing the phone to see if something was not disconnected but I have not found.
Do you have an idea how to cope ?
Or maybe a way to reset the memory lowest level because I think it is software, not hardware (well I think).
Thank you to those who can give me help.
Regards.

good post
good post
lol

Always the same problem with a fresh install of sense 3 with last kernel of Rafpigna...
no one has ever had this problem of noise camera in standby mode or to boot the phone?
Is it possible that this is a hardware problem?
What is really strange is that as soon as I get out of standby mode, the noise stops! And when I want to take a picture, the autofocus does not work ...

Task29 can't help me... Always the same issue... I tried WM7 I know it's sad but it does not change (I did not expect less).
No one can help me ??

...saw a post of a xda member with the same issue on the typhoon some months ago.
He made a video:
http://www.youtube.com/watch?v=46hRUY89A0E
..do youve got the same issue?
will it also autofocus all time when you dont got a rom installed?

Hi j4n87,
This is exactly the same problem, I can see the lens moving like that...
this is just since a week. it worked fine before !
This is after installing a version MIUI (when I had already installed several versions before without problems).
I try everything but I can not recover the normal operation of the camera.
Can you help me more ??
Thank you.
Regards.
j4n87 said:
...saw a post of a xda member with the same issue on the typhoon some months ago.
He made a video:
http://www.youtube.com/watch?v=46hRUY89A0E
..do youve got the same issue?
will it also autofocus all time when you dont got a rom installed?
Click to expand...
Click to collapse

I found that if I put in airplane mode, so no use of radio, there is no noise of the autofocus ...
I will try to degraded version of the radio to see if it changes something.
Alas no, it does not change, still the noise of the camera.

RESOLVED...
yay it works thanks to Dimension2035 (thank you very much for his invaluable help).
This is what to do:
- To MAGLDR
- Download the version of tytung
- Make the phone operational by using a little (there is always noise)
- Remove the battery overnight: miracle, everything works.
I'm really happy.
Here is the solution.
Regards and again thanks to Dimension2035
manu33xtro said:
I found that if I put in airplane mode, so no use of radio, there is no noise of the autofocus ...
I will try to degraded version of the radio to see if it changes something.
Alas no, it does not change, still the noise of the camera.
Click to expand...
Click to collapse

GPS battery drain although switched off?

Hallo,
I would like to make a question about a problem I noticed...
I used androits GPS Test to check if my GPS was working correctly after I flashed a new ROM (worshiprom) + Kernel (dorimanx 2.0)!
Just a test of 30 secs or so...
Today, after 12 hours of phone usage i checked the battery status and it tells me that Androits GPS test has the biggest usage of all! Its on 66% percent!
CPU usage just 30 secs.
GPS about 12 hours!
However, the battery last quite enough.. Just a 20% drop with 1h 30mins display and some wifi and data!
Is it just a display bug or is the GPS really on???
Tried a restart now and seems that the GPS usage stopped...
Do i always have to restart after using this application so the GPS truly stops working or am I missing something??
Thank you!

It's a bug with Google maps.
Sent from my LG-D802 using XDA Premium 4 mobile app

Make a nandroid backup and try flashing back the stock rom or another custom rom and see if the Problem is still existing

The problem is not worth trying a new ROM / Kernel as everything else is working extraordinary!!
Its easier for me to restart it after a GPS use (I don't use GPS apps a lot)
I just wanted to know what causes the bug and if its possible to fix it with any changes in my current setup!
Like reflashing gapps... etc...
Nevermind. Thank you guys for your answers!
If any1 else knows a solution rather than reflashing ROM and Kernel he is welcome to post it, otherwise i will have to live with it

Same problem
Hi,
I have the exact same problem but not with Google maps. Many times, when I enable GPS for a few minutes, and then turn it back off, It keeps running according to the power settings. The only way to switch it off is actually to restart the phone.
Hope we will find a solution. I have CM11 installed and I am pretty happy with it.
zacharias99 said:
The problem is not worth trying a new ROM / Kernel as everything else is working extraordinary!!
Its easier for me to restart it after a GPS use (I don't use GPS apps a lot)
I just wanted to know what causes the bug and if its possible to fix it with any changes in my current setup!
Like reflashing gapps... etc...
Nevermind. Thank you guys for your answers!
If any1 else knows a solution rather than reflashing ROM and Kernel he is welcome to post it, otherwise i will have to live with it
Click to expand...
Click to collapse