[Q] kwbr Wildfire 2.0 and trackball wake up??? - Wildfire Q&A, Help & Troubleshooting

Just flashed this rom for a week now. It is fantastic rom, battery performance improved significantly. Battery still 99% after a night. It used to be down to 50% with CM7 or other roms.
One thing that I missed is ability to wake the phone up using trackball. Need advice from some one to get this function back with the kwbr rom. Thanks

Related

[Q] MIUI-au expected battery life

After I installed MIUI-au 0.12.111 R2(first time installing it) I Got really bad Battery life. With the stock rom on my HTC Desire I would go 3 days before charging it(light use), now i can only get 1 day, I have looked around and did everything I could find, I reset the battery stats. made sure I let it die and charged it up fully a few times. I have tried the new version of the Radio and RIL. I have tried setcpu and I can only get 1 day with it. I love miui but I can not keep it with such bad battery life. am I expecting too much from it? or is there something i am missing/ can try?
Thanks
Anyone else have this problem? IT seems to be wasting. Battery while idle
Sent from my HTC Desire using XDA App
Im currently running the same rom as you... i'll see what battery life is like with mine over time, but so far so good.
Sent from my HTC Desire using XDA App
MasDroid said:
Im currently running the same rom as you... i'll see what battery life is like with mine over time, but so far so good.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
What version of the Radio and RIL are you using?
Not flashed RIL as the matching RIL for the recommended Radio (5.09.05.30) is already in the MIUI ROM, stock out of the box.So yes, I am currently using radio 5.09.05.30 (MIUI recommended) which has given me excellent battery life, even with FroYo roms. I have not experienced any Wi-Fi issues either.
EDIT: The information in this link may also interest you as it talks about different radio versions and associated RIL, and the effect they can have on battery life especially: http://www.miui-au.com/faq/radios-radios-radios/
Hope this helps you out.
Thanks I will try downgrading my radio and see what happens.
To further save battery life, i.e. when idle at night, you can also try enabling Airplane mode at night and disable in the morning. There are apps in the marketplace that can do this for you automatically between set periods so you don't have to bother doing it manually.
Sent from my HTC Desire using XDA App
Thanks for the help, but it still had very poor life about 6% per hr idle so I went back to the stock rom. Is it possible to install app2sd+ on the stock Rom or can you recommend a close to stock Rom with that and maybe a few other small changes?
Sent from my HTC Desire using XDA App

Gingerbread 2.3.4 huge battery sink!

Hello all. I just upgraded my HTC Merge from froyo 2.2 to gingerbread 2.3.4. I like how the new rom works, and feels and its features. But on froyo I would unplug before bed, with data off, wifi off, gps off, bluetooth off, and wake up with 99% battery life. I did a titanium backup before gingerbread. Updated with HTC Sync and used titanium backup to restore all my settings. Now when I wake up I have 37% battery!!!!
Going from 1% battery loss in 7 hours, to 70% battery loss in 7 hours is completely ridiculous. I have one a partition cache wipe, battery stat wipe and the like. I have not changed any settings. The phone is not in use over night. The stats show that android OS and system idle are both using 40% of my batter a piece. Any ideas? Could it be a bad install? Some say their battery life is better, how can mine be so much worse? I've tried most of what I've read from the thousands of other users with the same problem. I am rooted, but don't know of any custom roms or kernels for the Merge. I have a few more things to try, but just wanted to see what you guys all thought.
Thanks for the responses guys, I appreciate it.
Yea I had a similar issue that was fixed, for the most part, by changing the kernel. I guess you should try to find one custom for the Merge? Never heard of that model..

HTC WildfireS Ridiculous Battery Usage by Dialer Process

Hi All,
I have a problem with my Wildfire S A510e whereby the battery of the new phone does not last even 4 hours.
After fully charging the phone, the battery consumption is high even without using Wi-FI or 3G or GPS.
After fully charging the phone, all i did was attended a call and spoke for 2 Minutes.
After 3 hours, the phone battery was only 20% and the process that was consuming most battery was "Dialer".
This is ridiculous.
Dialer should be the one consuming least power, given that i used the phone to talk only for 2 minutes. I believe this is a problem with the Stock ROM and i hope to get an update for this problem.
I am using
Software Build Number 1.66.401.1
Kernel 2.6.35.10
Baseband 47.10g.35
Please guide.
Its a bug that exists in all wildfire s stock roms and from what i've read not just wildfire s but a large selection of gingerbread phones.
I would just ignore it, i dont think it has much impact really mate.
Sent from my HTC Wildfire S A510e
G'day Mate...Thanks for the response.
How much is your battery lasting?
And Isn't the battery getting exhausted in no time an "Impact"?
I literally am required to be plugged in to AC Point all day long. I can't go out without worrying that my battery will get exhausted :-(
it always shows 59% for me in dialer usage , stock battery never lasted long enough. it drys off to soon. made me feel like throwing off the phone in a river, so i bought a mugen power battery.. after full charge i kept it idle for 10 hours, battery remaining was "97%"
stock battery is 1230mah mugen is 1500 mah , buying new battery is beneficial.
i have no issues with battery now.
I have seen my dialer in the 90ish% battery is not great think its htc sense because now I'm using CM7 port my battery life has seemed to double and that's no exaggeration.
To get more out of your battery turn off all data sync, wifi, GPS off when not needed.
Are you rooted and are you running a stock rom?
Sent from my HTC Wildfire S
Dialer starts sapping battery after you've used the dialer interface once (dialing out / receiving calls).
You need to reboot the phone to stop it.
or kill the dialer storage process a few times to cause the phone to soft reboot (5sec reboot)
The long term solution is to S-Off and run a custom rom.
I am using htc wildfire s salsa port by jikintaru and my dialer is always at 92-95% after call
I think he is draining my battery even when my phone is in iddle state.
My battery lasts for 1.5 day with low call,wifi usage...
Is there anything i can do to fix this couse i am on nice rom?
Thank you in advance
Its a gingerbread bug, but like i said earlier ignore it, don't think it has a real effect.
My girlfriend has the same dialer issue on her htc chacha
Sent from my HTC Wildfire S using xda premium
intel007 said:
I have seen my dialer in the 90ish% battery is not great think its htc sense because now I'm using CM7 port my battery life has seemed to double and that's no exaggeration.
To get more out of your battery turn off all data sync, wifi, GPS off when not needed.
Are you rooted and are you running a stock rom?
Sent from my HTC Wildfire S
Click to expand...
Click to collapse
What CM7 port are you using, as I know no official CM7 port has been made?
On my phone it is allways showing 97% dialer battery usage, but I think it's just a false reading. If you use some other battery monitor program like Badass battery monitor you can see what apps used most power.
New Stock ROM
A new stock ROM is available
http://forum.xda-developers.com/showthread.php?t=1074445
I have installed that. Will report if that helps solve the problem.
Regards,
Guddu
If you goto the development section for wildfire s you will see the unofficial cm7 by alquez.
If your s-off and rooted check it out mate it really is good.
Sent from my HTC Wildfire S
intel007 said:
If you goto the development section for wildfire s you will see the unofficial cm7 by alquez.
If your s-off and rooted check it out mate it really is good.
Sent from my HTC Wildfire S
Click to expand...
Click to collapse
This rom is really good and very fast but has a few bugs, for example: you must turn off flash while you taking a photo beacause the app is going to crash
I recommend to use one of "jikantaru " rom
There is a much easier fix for this.
If you go into Settings>Sound and disable "Quiet Ring on Pickup", "Pocket Mode" and "Flip for Speaker" it should improve your battery life massively. All of these constantly monitor the accelerometer via the Dialer app and drain the battery. Try it!
kikuratab said:
There is a much easier fix for this.
If you go into Settings>Sound and disable "Quiet Ring on Pickup", "Pocket Mode" and "Flip for Speaker" it should improve your battery life massively. All of these constantly monitor the accelerometer via the Dialer app and drain the battery. Try it!
Click to expand...
Click to collapse
Thanks. I actually tried these after looking for more info on a Android forum but it never really helped much.
I hope they fix this dialer problem and freezing problem in this phones
Other then that i like it verry much...
I have this as well. A fix I found that seems to work is, after making a call, restart the phone. It will get rid of the Dialer process. A bit frustrating to restart the phone each time, but it does work.
And in response to turning off pocket mode, speaker, etc., they do help with battery improvement. I'd strongly recommend everyone turns these settings OFF for better battery life
Sent from my HTC-A510a using XDA App
I can confirm that the latest ruu 2.13.401.2 euro which is the latest htc rom that upgrades gingerbread to 2.3.5 and gives the new lock screen does NOT have the dialer issue.
It does not even show dialer at all in battery usage.
Edit:
Didn't realise i was charging, now im off the charger im a 98%.
Sent from my HTC Wildfire S
Figured it out!!
The issue for me was that the Maps app had not been used before and was waiting at the initial Accept screen. Once I accepted, battery usage is completely normal! The problem is in the Maps app, not in the Dialer. There must be an infinite loop around waiting for the Accept button to be clicked.
Thanks for the advice here about using Badass Battery Monitor. It helped me figure out that the real offender was Maps, not Dialer (there must be some bug here that results in the mis-reporting).
Did they fix dialer problem in 2.3.5 version?Can anyone confim this?
I am using method
"I've disable gsm proximity sensor and now this issue gone! Yeah! I've set 'gsm.proximity.enable=false' in build.prop before flashing a 2.3.3 rom."
With this method i dont have proximity sensor so when on call you have to press power button to hang-up,turn on screen or turn on speakerphone but there is no dialer issues no more for days for me...
Dialer seems ok on mine, been updated to 2.3.5 for 24 hours made and received few calls and dialer is only 13% and to be honest the battery life is an amazing improvement from HTC.
Will carry on testing. The battery is as good if not better than cm7.

[Q] Fast battery drain inconsistent behaviour

I flashed a custom ROM [unofficial CM9 ICS4.0.4]. Everything seems to be working fine, but there are a few problems and I'm wondering if this is normal for those using this. It's my first time flashing a ROM on my android and I'm not sure if it's normal. Did some searching in the forum, couldn't find much info too. Maybe I didn't search hard enough!
Anyway, here are some issues, I'm not even sure if it's the ROM.
1. Sometimes, the apps just bring me back to the home screen several times. Example: Running whatsapp brings me to home screen a few times, or when I go into a conversation, it brings me back to the conversation list but eventually it works.
2. On another occasion, every app that I ran would be unresponsive and I needed to end it. Solved it by rebooting.
3. Battery drain is very fast with little usage. I thought running a custom ROM usually provides better battery life.
I've not overclocked it, it's still in it's default value after flashing 1024. So I doubt it's anything to do with that. But since we're on the topic on overclocking. Desire HD didn't have anything beyond Gingerbread. So if we're flashing anything greater, is there a need overclock to be able to work comfortably on a higher OS? Is there a minimum or maximum for it to function comfortably?
Thanks!
Hmm, did more reading up.
Could it be I didn't calibrate my battery after flashing a new ROM?
Just flashed ARHD 6.4, will try to calibrate after that.
Appreciate any other advice though

[Q] Can't fix battery drain...

Hey guys,
my Endeavoru PVT (Tegra3 International) is now about one and a half year old, I can't remember how it was in the beginning, but now my battery drain is too heavy in my opinion.
At first I had AHRD, then I switched between some ROMs but now I am stuck at CyanogenMod 10.1.3 because as time went by, I started to hate Sense and I love the standard Android look. The thing is, since I switched from OrDroid to CM 10.2 or better said from Android 4.1 to 4.2+, the drain got heavy.
I removed all wakelocks, I use XM-Kernel with Smartmax+Row and limited the CPU freq, I turned off sync, gps and I only use 3G if I need the speed.
I mostly use whatsapp and rarely browse the internet with my phone, when I wake up at 7:00 AM I disconnect it from the charging cable, then I go to work etc. and at about 9:00 PM the battery only has 20-30% left and the average screen on time is maximum 2 hours overall and that's clearly not ok...
As I already said, I removed all wakelocks, the only wakelocks come from the kernel when the screen is active. So please do not link the ultimate battery life thread or something like that... I have no wakelocks and my settings are ok.
And when I start gaming, the battery drains 1% per minute which is insane! So I can't play any games at all.
With OrDroid and XM-Kernel I had the best battery life and almost no bugs.
Today I wanted to install Skydragon 2.0, but it was pretty buggy. So I switched to AHRD but with the XM-Kernel (17 beta for Sense5) my computer didn't detect the One X, I switched back to Stock Kernel, then it got recognized but the files were all displayed like a mess and I couln't copy any files onto the One X. Then I was pissed and restored my CM 10.1.3 backup... Is there any way to fix this??? Please no mass storage mods, these are not stable and don't work sometimes..
A few days ago I bought a One X+ battery, it should arrive next week. Maybe the battery is broken, but that doesn't explain why it drains so fkng much battery when I start to play games! And it doesn't fix my problems with Skydragon or AHRD. I would love to stay at CM, but there are the common issues which force me to switch to a sense rom.
I will probably switch back to OrDroid with XM-Kernel when the new battery arrives, hopefully it will fix the heavy drain. Can someone explain what could cause this massive drain? I mean, a phone should last at least 24 hours not 14...
Or is there any fully working AOSP rom with Android 4.1 for the One X? So I could benefit from the battery life and the look of Android 4.1.
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Go for a full wipe of your device & SD card first than try installing anew sense 5 rom and see whether the issue still persists?
donkyshot said:
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Click to expand...
Click to collapse
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
shawly said:
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
Click to expand...
Click to collapse
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself? If it's not the software it's the hardware, replace the battery.
Sent from my HTC One X using XDA Premium 4 mobile app
donkyshot said:
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself?
Click to expand...
Click to collapse
I didn't meant the part with the sd card, I meant the sentence were you said I should try a sense rom, which I already tried as I stated.
I'm sorry if you interpreted my post as an insult.
Edit: Ok I fixed the USB problem, I installed the newest HBoot and used lyapotas Kernel, now it works without problems. Now I'm going to fix all wakelocks and wait for my new battery.
I removed all wakelocks now and I got about one hour more since then, but at some times the drain is heavyer, I tried to backtrace the drain with GSAM and BBS (root) but there are no Problems with wakelocks. The battery drained from one minute to the other from 72 to 78, I don't know if the stats didn't refresh correctly, but I am now pretty sure it's the battery.
Okay, my battery arrived. I replaced it and besides I fixed my Wi-Fi with a piece of aluminium foil. The drain on the first start was heavy, but I think it has to undergo some full charges to calibrate.
But I have one more problem.. I'm on ARHD 33.1 with lyapotas LM kernel (XM beta didn't work very well), but I can't undervolt with SetCPU (paid for root version). Every time I want to save the undervolt settings SetCPU itself crashes and I don't really want to use TricksterMod for undervolting.
Is it because of lyapotas kernel?
I already reinstalled SetCPU two times..
Update: Wow, I never had 78% battery left after work! I guess it was my battery that was broken, so the thread can be closed.

Categories

Resources