Battery Meter and Temp reading "Fix" (workaround) (6/22 Update)

[sovereignty03]

Originally Posted by Unknownforce

Sure, it just shows the animation, but when you go into the spare parts and look at the battery percentage (without my latest release) it's at least 40% higher than it should be... This is why I manipulated the code to forcibly bring that number lower. Because of this, you can charge it a lot more accurately while charging with android. I set it to be a FEW percent higher than the reading android has while on discharge, so that it will hit 100% when it's more like 95-97 and, if the code is correct, STOP charging at that percent and not fry the battery or something.

WITHOUT this fix, it would ready 100% when it's more like 50-60% and not charge beyond that because it thinks it's are 100% because of the extreme increase in the voltage reading while on the charger.

Ah, now I know why you are doing that. Good.

Originally Posted by Unknownforce

The problem here is that I don't think it's reading the proper discharge values as WinMo does... WinMo I believe pulls the mA that's currently being discharged and uses it in it's calculations among the temp and voltage readings, now that COULD be calculated FROM the temp and voltage readings, but again, I don't know... I still haven't had much time to do much with the dll file and see exactly what's going on... and with my limited knowledge of ARM ASM... it's going to take quite some time... which is why I'm only guessing at numbers for now to at least get it CLOSE to what it should be reading.

Have you found which address WM is reading for voltage, current, and temperature in the ASM you are looking at? This is the first step to assure we are looking at the proper values. Then work on calculations.

[Unknownforce]

Originally Posted by sovereignty03

Ah, now I know why you are doing that. Good.





Have you found which address WM is reading for voltage, current, and temperature in the ASM you are looking at? This is the first step to assure we are looking at the proper values. Then work on calculations.

Unfortunately no, I haven't had any time to look at it in the last week or so, so when I get time to look at it again, I'll have to re-trace my steps and get back into it, I don't know when I'll have the time to do that, I'm working 2 jobs right now and I can barely even get any sleep, I'm replying from work right now, haha...

Hopefully I will get some time here soon to take a stab at it, but if not, I have a week off in the beginning of July, and I'll probably be able to dive into it then and hopefully figure it out.

[Unknownforce]

Brought up to date with the changes from 6/14. sorry for the delay, work is killing me.

[LBushnell]

Thanks Unknown! This is a huge help man, keep up the good work.

[Unknownforce]

Added some stabilization code to hopefully level out the battery level and not be so erratic. THIS IS A BETA of this code, I plan to add more stabilization routines in eventually, but alas, I am just too busy. However, because this is beta type code, I have left the 6/17 update up for download incase this does not work.

To understand what it does and why it's a beta, have a look at the first post.

Thanks, and please let me know results and/or problems.

[AndroidTroll]

how far is the hardware accelaration from being activated? Anyone know? The regular htc touch has it activated. Does anyone know if theres any build of android has the accelaration activated?

[Unknownforce]

Originally Posted by AndroidTroll

how far is the hardware accelaration from being activated? Anyone know? The regular htc touch has it activated. Does anyone know if theres any build of android has the accelaration activated?

Firstly, wrong thread. This thread has nothing to do with hardware acceleration.

Secondly, hardware acceleration doesn't need to be "activated," it needs code to properly initialize and interact with the hardware. The hardware inside the TP2 is different than most other HTC Devices, including the TP1. So it can't just be "activated." We have to learn how it works and then adapt the android kernel to work properly with it. This is no easy task, and there is never a real ETA. You can't put a set time on discovery of the correct functionality, it just happens, there's a lot of trial and error. It could be today, it could be a year from today.

Please read a little before posting, and please post in the correct thread.

[xicloe]

Is this fix work with the froyo 2.2 just added at 1 juli ?, or maybe I should try and report back

[Unknownforce]

Originally Posted by xicloe

Is this fix work with the froyo 2.2 just added at 1 juli ?, or maybe I should try and report back

Possibly, assuming 2.2 uses the same zImage type interface. I will have to test it out.

[NeoMatrixJR]

Actually, you're kernel seems to be the only way to get 2.2 working on a TP2. CONTACT ME. (or another dev). We need to get you merged in or something)