[HD2 Android SD Development] shamez23:
That's something I've experienced several times. I don't know if that is actually what is happening but it feels like the build needs some time to settle in.

I've had some weird problems before, that I just couldn't solve, no matter what I tried. When I finally gave up and decided to live with them, they vanished on their own, after a while. Not all do, but some.

That's why I stopped being too keen on updating all the time. There have been times, when a new build came out almost daily. In the early days there were major bugfixes and you had to update but lately it has mostly been updates containing stuff the cyanogenmod team did in the background. Nothing concerning me, so I stopped doing every possible update and rather did stick with a build that worked for me, until there came up some really big changes that warranted an update.

You may not like to hear it, but I think from the devs point of view this build is as good as it's ever going to get. I can't imagine there could be any major breakthroughs still waiting for us. Not with gingerbrad anyway. Lets see if Icecream Sandwich will be ported to the HD2.

Some minor fixes perhaps.

Sure, I get it. No problem with your English, it's really good.

I never looked at it this way.

I don't know if it is possible to easily change the volume range.

Maybe there is some file, like the build.prop file you just have to open and you can change it but I haven't heard of it.

Soundproblems have always been a part of all Android builds. In call volume, robot voice, media sound being too low, being too high, etc. . With almost every new build you get some minor changes and there is always someone not happy with them.

You are not happy with the distortions and the fact that the volume steps are too big for your taste. If the devs would change that in the next build, I can guarantee that someone will complain about it, because he doesn't care about the distortion, as long as he can hear the ring of his phone in the loud environment he's working in. He needs the volume to be as high as possible.

You can't make everyone happy.

Have a look at the settings. There is is a plethora of possibilities. Especially have a look in settings->cyanogenmod->sounds. The volume gain may be a way to get close to what you want. Not perfect but better than nothing.

You have to play around with those settings. I never experimented with them because the volume never bothered me.

Hm, I guess I use my phone differently. When I go to a cinema or happen to be in some other place, where I want it to be quiet, I want it to be absolutely quiet. Vibration only. I use a widget to do that.

It has three settings:

1 Volume on

2 Volume off, vibration only

3 volume off, no vibration

For the rest, as I said, experiment with volume gain and try to find some kind of balance. Android is different in that aspect than winmo. It's not ACA but the OS.

I'm not a dev, just a user. There seem to be two different "ways" for data connection the old one, that wasn't flaky but only allowed slower speeds and the new one that probably all recent builds use, that is a little problematic at times, especially in areas where reception isn't perfect, but gives higher speeds.

Don't ask the devs of this build to incorporate the the old "way". They won't and they won't react kindly if you try to press them.

They did a great deal of work to get it as far as it is now.

In the beginning people would lose connection completely and only a reboot would get it back. After that, came a time, when it would reconnect on it's own but with a huge gap in between. Nowadays it doesn't lose connection nearly as much as it once did and it comes back pretty fast in comparison.

Yes, get current widget and check it everytime you take your phone out of standby.

In my experience it's usually an app, that keeps your phone from going into deep sleep, draining your battery.

You really have to check your apps for such things. If you have google sync set to syncing every minute, or your emails get checked every minute, etc. Your phone will always be active although the screen is off and it looks like it's in standby. Sure those things in themselves won't take a lot of power but your phone can only step the CPU so much. The battery has 1230mA if you get a constant drain of 60mA/h because your phone doesn't get into real standby (with 5-10mA/h drain), your battery will die after 20hours even if you don't use it in any other way. No calls, no messages, screen always off, only standby. And that's when it stays at 60mA/h. Listening to mp3s and the drain will be around 100mA/h. Volume doesn't really matter in this. Do the math.

Current widget will help you to see if and when that happens and if you use a task manager to selectively kill apps that are active in those instances of high drain, you should be able to find the culprit. You then can either erase it, keep killing it or use an app to freeze it, which is a viable option for apps that you only need occasionally.

I always have my data connection turned off, I don't need it. Well, almost always. Sometimes I need it for navigation with google maps but that's a rare event. I have a "shortcut" in the pull down menu for those moments. One flip of the thump, the pull down opens and a press on the data connection icon and I'm online.

GPS is off, Wifi only on when I need it. No constant feeds, weatherupdates or constant email retrieval for me.

I listen to music or audiobooks quite a bit though.

This way I easily get through a day with one charge and I usually have about 50% charge left at the end of the day.

Maybe not exactly the kind of use a smartphone was meant for but well, that's me.

However, it's not only the HD2 that has poor battery life. Just today I watched a review of the brandnew motorola droid bionic on pocketnow.com. A real Android phone with a battery that holds more than 1700mA. With medium to heavy use, you will have to recharge it after half a day. Granted, it's a dualcore phone but aside from that, the specs are not too different. Same screensize and the screen is one of the biggest power users in our phones.

I think Google has still a long way to go to make this OS perfect. Especially the way apps get handled. There have been quite a few improvements in gingerbread over its predecessors concerning that issue but there is still something wrong with it.

Many people will tell you that using a task manager to kill apps is a stupid thing to do, since reloading an app will cost more energy than having it run silently in the background and Android is handling apps on it's own. I agree to that logic, the problem is, not all apps stay quiet. That's way I still use a task manager. Not on automatic, but manually, as soon as current widget shows unusual drain in standby, I kill all apps that started themselves without me doing anything.

Some people have the same problem. There is no real solution for this because noone knows the reason for this behaviour. It is a minority that has it, which makes it hard for the devs to find a solution.

Reinstall perhaps, maybe it will be one of the things that will go away after the build has settled. Sorry.

You can always try other builds, if you like. That's the beauty of SD builds. No risk and fairly easy to set up. ACA may be one of the best builds, maybe even the best build and it may still not work for you. Some other build might. There are too many unknowns in this game. The hardware of our phones should be the same but there are minor differences. The radio you use, the winmo ROM you have installed, the apps you use, settings made, etc..

This whole thing is experimental. Either you have the time and patience or you don't.

Ah well, same thing I did. Skype really made a mess out of this. It's the same with their PC and Mac versions. Why can't they keep it simple?

---------- Post added at 03:41 AM ---------- Previous post was at 03:32 AM ----------

Did you create that folder while you where in Android?

That won't work.

You have to do that using a cardreader or doing it out of winmo.

This build will put a "." in front of the root folder you created in Android during shutdown of the phone. During reboot any folder with that "." in front won't be recognized and your sound won't get copied into the system.

The devs included that so the file won't get copied into your system over and over again during each reboot. May not sound interesting when it comes to a notification sound but you can make major changes to the system this way too and if the folder doesn't get kept from working, you might get unexpected resets of settings.