yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] SamStone:
I just installed the AmeriCan Android SD version and it worked great out of the box. It looks to me like the LCD density is set to something other than the usual 240. I see a folder in the build labeled 240 LCD, do I need to do something with this to make the build 240 density? Thanks
[HD2 Android SD Development] uzi2:
You could ask theos0o if it is possible to add it to his list of tweaks for skype.

http://xdaforums.com/showthread.php?t=1148708
[HD2 Android SD Development] uzi2:
By default the LCD density is set to 167. You can change it to whatever you require by editing the value in startup.txt - the details are included in the changelog section of post#1.
[HD2 Android SD Development] rufffus:
I don't want to jinx it but it looks like you've solved my problem. Cheers mate!

I've also changed scaling to "performance". I hope it will solve Endomondo/GPS problem as well.
[HD2 Android SD Development] RobE.:
Originally Posted by prattjo...

It happens when screen goes off. You must set minimum CPU speed to 245 and not 128. You do it with SetCpu application or with Cyanogen settings.

Technically speaking, prattjo (certainly with his heart in the right place) Didn't solve your problem. He pointed you in the right direction of making some changes... and personally imho, 245 MHz, is still too low a number for this type of CPU to give any real meaningful performance. Still that low speed has it's place in the nature of things.

Give yourself an education about the different CPU Governors, and what they do... https://github.com/CyanogenMod/cm-kernel/blob/android-msm-2.6.37/Documentation/cpu-freq/governors.txt

Essentially, by setting the Governor to 'Performance', you locked the CPU in to the highest speed on the Min/Max scale of operation. That's why your issues resolved; You solved your own problem.

"The CPUfreq governor "performance" sets the CPU statically to the

highest frequency within the borders of scaling_min_freq and

scaling_max_freq."

For a 1GHz CPU, speeds underclocked below the 500 MHz range aren't very effective for for many apps, but they'll save some battery power and are good for charging. True... 128 MHz is a real dog and 245 is certainly preferred as a better low speed setting. I'd go a step higher still, as a bare minimum. But that's just me, and just my $.02, fwiw.

Rob
[HD2 Android SD Development] bernard.bb:
For information: To save battery power, after many tests, I found "2x Battery" on the market brought about a real bonus.
[HD2 Android SD Development] powinmo:
Hi all. I help maintain the TP2 Wiki/FAQ over @ PPC. I've been using American Android on my TMO HD2 for some time now but have stayed behind the scenes; trying to catch up on events and information when time permits.

I thought I'd offer to help some by creating a new wiki/faq right here on XDA:

http://xdaforums.com/wiki/index.php?title=AmeriCanAndroid_AOSP_HD2

If this oversteps docent's efforts or others, I apologize and will rescind the information there.

Right now there's just a barebone listing of items that concern me currently or I've seen posted recently and often. I'll be making touch ups off and on the next few days. Maybe we can merge in any current or relevant information from prior faqs to this one at some point.

Comments, assistance, etc appreciated.
[HD2 Android SD Development] ahkow:
Like to share with all, I managed to "fix" the high current drain with below steps:

1. Google Backup Transport - then click clear data

2. Google Partner Set Up - then click clear data

3. Google Services Framework - then click clear data

4. Market - clear cache

5. Reboot the phone.

I was using data.img file from previous 0818 built. With above steps my current drop to 8ma....
[HD2 Android SD Development] powinmo:
All of my usual tricks (using the battery calibration app, waiting 48 hours, deinstall a random app along with the gazillion reboots) to ditch the battery spike after upgrading to 0828 a few days ago have failed... until I tried your tips. I can confirm, at least for me, this worked! After 48+ hours of 50+ma, I'm back down to < 6ma.

If this helps others, I'll post it to the newer faq.

*edit* just for disclosure, the high drain was on a totally fresh install of 0828 with a crisp new data.img and minimal app installs.
[HD2 Android SD Development] shamez23:
About the battery calibration.

I've seen it mentioned here countless times. Many think that this is some kind of monster trick that will solve all problems.

It is not.

In fact, I believe that it is of almost no use at all for our SD build powered phone.

Calibration is something that might help with systems that don't change.

The file that gets created and used to determine how much power the battery can hold and therefore can lead to wrong informations about the level of the battery will not change in a real Android phone like the HTC desire hd. Or in our case, when we talk about the original winmo ROM. At least it won't, as long as you don't use custom ROMs that you update a lot. It doesn't matter if you use an SD build or Android NAND or WP7. It's about the time you use your phone, meaning the age of the file.

I'm talking about users that buy the phone, use the stock ROM, do no hardresets of their ROM or anything of that kind. For them it can happen that the file containing the information grows old and no longer describes the real state of the battery health. The battery will get weaker over time and no longer hold the same amount of energy it did, when it was new. If the file stays the same, your phone will shut off before the aloted time.

But we are talking about a long timespan here. The battery doesn't die in a month it probably won't even decrease noticeably in that time. We are talking about a year or even longer.

If the file somehow gets corrupted you will get a wrong reading aswell but I don't think that does happen a lot and it will probably the least of your concerns since chances are very high that if one file gets corrupted others will too and your phone won't run in a usable fashion anyway.

But back to the SD build. Most of us update with almost every build. That means about once a week. Even those of us that use their old data.img for a long period of time will sooner or later have to create a new data.img. Usually when Android changes considerably like with a jump from 2.3.4 to 2.3.5.

As soon as you create a new image, the file containing the battery information will get a fresh start. Pretty often in our case.

There is no need to force this with the battery calibration. I doubt that this is of any use in 99 out of 100 cases it is mentioned here.

Sure it won't hurt but it still is a waste of time and misleading to everyone that is looking desperately for a solution to their high battery drain. There are other reasons behind that.
[HD2 Android SD Development] phatphat:
Thanks for the response and detailing the solution, but honestly, if you don't check this thread for a day, it fills up so fast that searching for a specific string is just not a viable solution to find one specific solution. It should be in the FAQ and it's not, especially seeing as it's been a very common problem.

It looks like the problem had been solved now anyway.

@uzziah0 - regarding the skype option on the dialer; when I dial, it gives me the option for both but then below that there was a tickbox to set the default. once I did this it never asked me again, the dialer just dials.

One other thing though about skype - After i use skype, the dialler will not work (has a lag of 5+ seconds for each number pressed) then I get force close messages. I have to reboot to get the normal phone dialler working again. It basically means If I want to use skype, I can't use the phone until a complete boot cycle.

Anyone having this problem?
[HD2 Android SD Development] mr_billionaire:
How can I change the splash screen?

I mean, it's very nice, but I want to add my own flavor to it.

I'm using the SD build by the way.
[HD2 Android SD Development] maneken25:
If some know how good this build works with Toshiba sd hc card 8gb class 4?

Bought new card but have unluck to install aca build on her even after checking card on few other android phones and after formating with sdformater.

Is there some preferable type of format which i need to use?

Second thing, tried last 3 builds and can confirm that call hanging and loosing sound after could be cause of using also Viber app (voip app). Just fyi if someone is hooked on that app. I love it but seems i will not be able to use for now.
[HD2 Android SD Development] mihaid:
appointments disappear

I have synchronised my appointments via Myphoneexplorer and they were showing in calendar events on my HD2. However after a few hours they seem to have just vanished. This is the second time this happened. i'm on amcan gb234
[HD2 Android SD Development] hensond67:
Question guys and gals. Can we change the image size to 1.5gb anytime before restarting into android? Would doing that delete the files on the existing 1gb data img?
[HD2 Android SD Development] satan!:
some do not understood

you want to replace the existing data.img?

everything we write in a terminal emulator.

go to the folder with data.img

go in the folder and write the following :

e2fsck -f -y data.img
resize2fs -p data.img 1512
e2fsck -f -y data.img

where "resize2fs -p data.img 1512" will be changed to 1.5 Gb

if you want to create a data.img size before installation, edit "Startup.Txt"

set cmdline "rel_path = Android nand_boot = 0 data_size = 1024"

where data_size = 1024 (1Gb), change the example to the desired size, such as 512Mb

data_size = 512
[HD2 Android SD Development] hensond67:
Sorry what I meant was. Since I'm running out of space, is it possible to change the startup text to add more data space?
[HD2 Android SD Development] d3m0n1:
You can't increase data space by editing the startup.txt.

You need to download toporesize (search this thread for link), extract it, and in there you will have the 2 files, satan! mentioned.

Copy your current data.img to your pc in a folder, where those 2 files are, open a command prompt, and run the commands from satan!'s post. That way you will get a re-sized data.img with all your data intact. Now copy back your data.img into the Android folder on your card (but first make a backup of the original, just in case), and boot android.

B.R.:

d3m0n
[HD2 Android SD Development] uzi2:
Satan has answered your question.

If you edit the startup.txt you will create a fresh data.img

Follow his commands in terminal and you will increase the size of your data.img without losing tour data.

@d3m0n1 - there is no need to download toporesize or use PC, the commands are native to android.
[HD2 Android SD Development] hensond67:
Nice! Thanks guys
[HD2 Android SD Development] d3m0n1:
Didn't know that. I knew that the commands are available in Linux, just didn't know it made it's way into Android, too.

B.R.:

d3m0n
[HD2 Android SD Development] satan!:
You can resize without losing data data.img as I described.

if you edit the "startup.txt" then changes will not happen if you release from your own data.img. respectively by removing a crowded data.img remove all that it was (if not delete and move on a PC)
[HD2 Android SD Development] dttung80:
With 28Augst, i have many SOD and trouble with USB mass storage.

Back to 17Augst.

Thank.
[HD2 Android SD Development] satan!:
principle:

1. Copy your data.img to pc (just in case)

2. use the terminal and the commands that I wrote.

cd /sdcard/android [enter]
e2fsck -f -y data.img [enter]
resize2fs -p data.img 1536 [enter]
e2fsck -f -y data.img [enter]

3. obtain the desired data.img updated by size

4. restart the PDA

enjoy.

all commands are native to the android because there is no need to use a PC for these actions

ps. I'd add that such operations are more properly done by the android without using third-party programs or senior linux, in order to avoid possible trouble. I change about the size of the establishment or data.img data.img
[HD2 Android SD Development] vasoprino:
i fix the USB mass storage deleting an HTC phone installed erroneously in windows 7 peripherals
[HD2 Android SD Development] uzi2:
I am sure many users would be interested to hear what profile you use in SetCPU for day to day running.

Here is mine just to set the ball rolling...

In order of priority (high to low) - max-min

Temp>44.9C - 499-128

In Call - 1190-883

Screen Off - 499-128

Charging - 1190-128

Battery<33% - 768-128

All Scaling is Interactive

This works fine for me with no freezes or crashes etc. That doesn't mean that it will work for you as not all CPUs are born equal. If you have problems I would first look to scale back the maxima (CPU is rated at 998) and then increase the minima. Those who use in car navigation should almost certainly set the charging max to 998 in order to prevent overheating.
[HD2 Android SD Development] crtopher:
Usb host?

good

this room work for you the USB Host or know if you have room in sd usb host

thank you very much
[HD2 Android SD Development] scorpion44:
SET CPU

To max battery life here is my setup.

screen off pr. 95:245-245

temp>39.5c pr. 90:460-245

in call pr. 85:844-245

charging pr. 80:844-245

battery<50% pr. 75:652-245

Scaling is Interactive

No freezes or crashes
[HD2 Android SD Development] NYLimited:
Thanks for posting this. One question:

Do you have (Advanced / set on boot set) and if you do did you change the default 80000 setting?
[HD2 Android SD Development] scorpion44:
SET CPU

No is set to 50000, I remember reading about this setting but haven’t tried it.

What would be the advantage with 80000?
[HD2 Android SD Development] general1977:
This file only relates the measured battery status to a percent reading. Since this is individual to each battery and each phone this information has to be aquired individually for each installation.

Batterystats.bin is not located within the data.img but in the system.ext which gets "renewed" with every update of ACA you do. In fact, we all get the same batterystats.bin, which is probably the one off of copes HD2. The information in this file is more or less useless for us. So what I do is wipe batterystats.bin after the installation of each update and charge the battery to 100%. This way battery percentage readings are best for me.

To clarify again: this file has nothing to do with how long your battery lasts or with the drain measured by Currentwidget (for example). It is only needed to translate the voltage readings of the battery into a percentage that is shown in the battery icon.

Regards

Achim
[HD2 Android SD Development] NYLimited:
I have never touched this setting - mine indicates that the default is 50000 but the number showing in the box is 80000. The set on boot is not set on mine.

Since I am not really sure I fully understand this setting I left it as it was - unchecked.
[HD2 Android SD Development] NYLimited:
Good info - thanks for explanation!
[HD2 Android SD Development] shamez23:
Unless your battery is a long way from beeing OK or far different from copes battery this still doesn't explain or help with extreme battery drain.

I think I've read in the forum that cope bought a new battery recently. If the file is from copes phone it is fairly save to assume that the file will let your phone expect a battery with around 1200mah. Unless you got a much better battery than that and I think most of us don't, the percentage shown should be higher than it actually is, not lower or in other words your phone should appear to drain slower than it really does, not faster, a lot faster in case of unusual drain.

So calibration will give you a more acurate reading but it is no use for those with phones that will only last a couple of hours before it runs out of juice.

But thanks for clarifying on where the file is located. I never gave much attention to the matter and didn't know it was to be found in system.ext.
[HD2 Android SD Development] RobE.:
Originally Posted by RobE...

For a 1GHz CPU, speeds underclocked below the 500 MHz range aren't very effective for for many apps, but they'll save some battery power and are good for charging. True... 128 MHz is a real dog and 245 is certainly preferred as a better low speed setting. I'd go a step higher still, as a bare minimum. But that's just me, and just my $.02, fwiw.

Uzi2, (Honestly) It's my sincere feeling that you've forgotten more about the Android environment & OS than I'll probably ever know. I'd happily defer to your own knowledge & experience nine out of ten times, (OK... at least eight). :)

I'm not so certain (m)any users would be interested in knowing my own SetCPU settings... but as long as you've asked... I have a few things I can volunteer.

SetCPU permits great flexibility of configuration. Who knows what's best for each individual? Oftentimes it's simply, trial & error, one's best guess... following anothers example (which can often be the blind leading the blind) or hopefully, just plain knowledge & common sense.

There's a very nice and informative post here, that might be of benefit to some... Maybe not the best ever written, but I've found it helpful...

http://androidforums.com/eris-all-things-root/153501-setcpu-step-step-instructions.html

My own menu settings in CyanogenMod > Performance > CPU...

Governor: Interactive, CPU Max: 998, Min: 652 - SetCPU (as you know, overrides these 'defaults'). I also enable the Dalvik JIT, and set the Compcache RAM to 26% (max).

SetCPU profiles (I keep at a minimum), but I'll make changes from time to time if I sense they're necessary.

Charging - 921 max, 537 min, priority 60, Interactive

Temp >44.6 - 652 max, 499 min, priority 55, Interactive

Screen Off - 806 max, 537 min, priority 50, ondemand

Battery <20% - 768 max, 537 min, priority 45, ondemand

I have no performance issues that I'm aware of. I'm not advocating 'my' settings for anyone else; perhaps they're not nearly ideal. This is a PERFORMANCE device, and I see no reason to underclock it further to save a bit of battery. In car (GPS, & Bluetooth on), it's always being charged. With 20% battery remaining, I drove about fifty miles; the trip took about 80 minutes with traffic, and the HD2 battery was at 100% when I arrived at my destination.

When I'm out, I'll always carry a spare battery. When I'm gone from home for a few days, I'll carry three spare batteries, D/C charger in car and A/C battery charger in a spare case, along with an A/C USB charger for the device.

All in all, I'm still learning... I've built and overclocked and stress tested my own desktop PC's for years. These days I don't bother to O/C. I'm content to let the CPU run where it's intended to be run. I know mild overclocks are always OK, but my HD2 is a lifeline, and I depend on it so... I just won't O/C it. I don't see the need. I've found some time ago that OEM batteries DO last longer than 'replacements' (Thanks Cope!), and replacing an old SIM card with a brand new one markedly lessened the battery drain.

So there you have it... another long partially useful and possibly useless post by yours truly. :cool:
[HD2 Android SD Development] xavierh:
How do you have your screen brightness settings setup? I noticed that the screen brightness does affect the battery life. I have mine set to minimum and that only becomes an issue outside in direct sunlight
[HD2 Android SD Development] RobE.:
Agreed. The display probably sucks more juice than anything else. For me, indoors as low as is comfortable. Outdoors to the max. I typically don't use it outdoors for long, but daytime in-car, it's charging, so no matter.
[HD2 Android SD Development] warrenb213:
The file is generated when you make a data.img or delete your old bin file.

Not at all included in our build....
[HD2 Android SD Development] mihaid:
anyone can shed some light on this ?

anyone had issues with the above?
[HD2 Android SD Development] general1977:
So the batterystats.bin is located within the data.img respectively the data partition? If that is the case, why doesn't the battery percentage remain correct after an update to the build? After an Update I always have to wipe batterystats.bin and charge to get an accurate percentage reading.

Regards

Achim.
[HD2 Android SD Development] walidhazem:
Guys can u take a look at this pic ...I'm not sure if its a graphic glitch or its because of launcher pro...does anyone know?? Nevermind guys
[HD2 Android SD Development] uzi2:
batterystats.bin can be found in data/system and so is not overwritten by an updated build.

You will be using power in the update process, which could over time affect the accuracy.
[HD2 Android SD Development] shamez23:
I've been using ACA and its predecessor for quite some time now.

That also means I had a lot of updates. Usually with a fresh data.img, sometimes using an old image.

My percentage reading seems OK and I only calibrated my battery once, when the matter first came up a long time ago. There was no improvement back then so I didn't try again.

Maybe you should try giving your phone a day or two of normal use to get its bearings after an update before you calibrate the battery. It could well be that the percentage readings will go back to normal without calibration.
[HD2 Android SD Development] mgw_atom:
I may sound a bit dumb but where do I find these?
[HD2 Android SD Development] mgw_atom:
I have no knowledge of Linux or even Android. What does the data.img hold? Will I lose all installed apps when I have it recreated?

Also, when I change the file size form 1024 to 2048 will this swipe the old file or just increase it?
[HD2 Android SD Development] mgw_atom:
Have found Terminal Emulator on the phone, but how do I "go to the folder with data.img" and "go in the folder"? - Thanks!

Edit: found the information after posting a few posts later. - Thanks again!
[HD2 Android SD Development] mgw_atom:
How to delete batterystats.bin?

How do I go about deleting batterystats.bin? What tool do I need to do this? Opinions about where the file is located seem to be differing, so where is it really? - Thanks!
[HD2 Android SD Development] shamez23:
What exactly are you trying to achieve?

Increasing the image size. Why? 1GB is a lot of real estate. Do you really need more than that? Have you ever checked how much space you are already using?

Erasing battery stats? Why? Are you having trouble with your battery or better, problems with the percentage reading?

This build is made in a fashion that a regular user doesn't have to do anything to use it. If you are just playing around, also play around with the search function of the forum and increse your knowldge about the inner works of Android and this build.

If you have a certain problem, tell us about it and we will see how we can help.

At least I am reluctant to spent time giving answers without having been giving a reason.

As warren, one of our two developers, has stated, the battery file is inside the data.img. If a dev says so, it's save to assume that that is were the file is to be found.

Use a file manager with root rights to get to that file. There are also apps in Android market that will do the erasing part for you.

But I'd advise against doing such things without having a good reason to.
[HD2 Android SD Development] fei001213:
USB storage problem

When I connected the mobile to PC, turned on USB storage, and copied files to the mobile, it looked fine. then I REMOVED the drive from PC, turn off USB storage, and check the files on the mobile, they were not there! reboot can't help.
[HD2 Android SD Development] p107r0:
Known issue, search the thread for more info, untill resolved use WinMo or card reader for large files, or sth like File Expert (copying over WiFi) for small ones
[HD2 Android SD Development] p107r0:
Settings / Applications / Manage applications / All