yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] RobE.:
For you guys whose phones are locking-up... (whether you're using either SetCPU or CM7's CPU Performance menu), if you even know the answer... which GOVERNOR's are you using?

This setting alone might very well have something (or everything), to do with your freeze-up issues. It's not so much the CPU speed. If you're using CPU scaling - which is built-in as default for this CPU's operation. Scaling could be limited... or even eliminated. The main point of scaling is to save (battery) power, other reasons as well (but I'm not claiming any expertise)... It's the Governor that determines the responsiveness of the CPU. If the CPU can't keep up with the demands placed on it by the system... It's going to freeze up. It can only scale up & down so fast. If more cycles are needed it scales up in speed, and if there are less demands placed on it, it scales down in speed. How fast it responds is the Governors job.

Yeah ok, there are battery considerations here - some settings use more or less power, but to me... I need the OS to be RESPONSIVE. I'll always suggest folks use the Ondemand or (even better) Interactive Governor setting. The Performance Governor (I believe) forgoes scaling and keeps the CPU at the highest speed (I'm not suggesting you need to use that). The Powersave, and Conservative settings - SOUND - good but don't let the name's fool you.

If you're pushing your Android to give you any kind of real performance, those two are not the settings to use.

Of course - as always - I could be entirely wrong about all of this. But until I'm corrected by someone else who knows better or more - which I'll welcome leaning BTW. Ya'll should consider checking your Governor settings. The wrong ones could be the reasons for your performance issues.
[HD2 Android SD Development] RobE.:
Sure, try the Netflix app. (I already have it installed) but when I reset the build.prop to stock... the only edited fields being the region set to 'us' and lcd_density set to 240... the market displayed the Netflix app... listed it as Installed - (you know how it displays) - and the text underneath said "This app is incompatible with your HTC Android." (nickname displayed in menus) while the market account settings (which are pulled from the phone) showed the device Model as an HD2. And that's the reason it wouldn't be installed if I didn't have it already. Try the Optimum app. Try an Android (market) app if your bank offers one and see if it's listed as compatible with an HD2 (Windows device).

Love to hear what you find out.
[HD2 Android SD Development] shamez23:
I'd say it's the app, not gps itself.

Apps that need a lot of processing power will heat up your phone.

RobE. might be on the right track with his post.

If your phone for some reason doesn't scale down as often as possible, it'll overheat pretty fast. Especially in a car where it may already be battling with the sun.

Try to play with the governor settings and maybe also limit it to 800MHz if that doesn't impede the app and governor changes are not sufficient.
[HD2 Android SD Development] JMG01:
The BBC iPlayer app wont install (even when in UK it is incompatible in market).

can the phone show it's self as something other than an HD2?
[HD2 Android SD Development] RobE.:
Yes the HD2 can show itself to the market under another alias. Search a bit, read a bit more... you'll be surprised by what you'll learn.

You might need a few more 'tools' & info, than what's posted in these links, but it's a start.

Many apps, before incompatible... will become available but NOT everything. There will still be (for reasons beyond me) some apps that just won't be listed as compatible. I'm not in the eu or uk. My device settings I've fixed to the US. That BBC iPlayer is listed as incompatible with my device; The reason being shown to me is, "This item cannot be installed in your device's country." - I'm almost certain you could get it in your location. These 'fixes' aren't 100%, no guarantees... but definitely more app availability.

http://xdaforums.com/showpost.php?p=16496343&postcount=14830

http://xdaforums.com/showpost.php?p=16813337&postcount=15342
[HD2 Android SD Development] JMG01:
Many thanks. Yes I am watching the cm issue also, but what build is that issue about? Looks a mix (nightlies, etc). That cm issue started in April, when we also had the issue, but the ACA builts that used the zImage from 30th June all worked with VPN, and using that zImage in later builds of ACA also makes VPN work, even with the current build 0817.

Unless the zImage also comes from CM, then I don't see this is so clear that it is a CM issue. I'm more guessing that WarrenB and others share code in these kernels, and somewhere between 0630 and 0714 something was disabled in the code for the zImage. the error log we get is the same as an older issue http://code.google.com/p/cyanogenmod/issues/detail?id=855

In comment 17 it was fixed "Somehow a kernel option got disabled.Should be fixed for 4.2.12"

So what is in 0630 zImage that is changed after 0714??? I'm still hoping Warren can solve this one!;)
[HD2 Android SD Development] JMG01:
Thanks Rob, I'll take a look later. iPlayer is also not available in Norway, but we are allowed to move around...
[HD2 Android SD Development] geenyous:
2.0 RPC

What version of tytungs gps libs are you using?

I had the same behaviour with 2.0 NMEA (btw, many others have tha same issue), had to arrange my phone infront of the ac fan to get it working for a longer period.

Since I switched to 2.0 RPC I haven't had any issues since and have been navigating for 2 hours this saturday with the phone in direct sunlight. But to limit the CPU might also be a very good idea, will try that next if it happens again.

Find 2.0 RPC here.
[HD2 Android SD Development] backlashsid:
finally flashed the NAND Magldr version and full time Android !! wooot !! :D:D
[HD2 Android SD Development] evo1rs:
+1 on this,

Using GPS, GPRS/3G and having the screen on all the time + usually charging all the time will put a large strain on the phone and overheating will lock it up.

If you have A/C, blow it at the phone to keep it cool and it will work for a helluva lot longer!

Sent from my HD2

Running AmeriCanAndroid

AOSPHD2GB235CM7
[HD2 Android SD Development] xlr8me:
Great rom however have 2 issues:

1. 3G connection keeps disconnecting after usage....not sure why and then reappears.

2. The current battery drain in standby is playing up around 74mA and then sometimes 3~5mA. What is causing this>???

If anyone can assist with the 2 issues this would make it very awesome.
[HD2 Android SD Development] backlashsid:
man for me the battery life so far has been great...after 12hrs since charge...i am still 80% with a good usage !
[HD2 Android SD Development] iPAQ 6515a User:
Interactive as suggested by ACA team and SetCPU creators :-)

Anyhow, thanks for your reply.

NMEA, will switch to RPC

Thanks for the tip
[HD2 Android SD Development] tarkboffin:
GPS not tracking when screen off

Hi,

I used to use the GPS on ACA to track my workouts when cycling and running. After a period of 2 months of enforced rest after an injury I tried tracking a hike yesterday, using both Locus Pro and SportyPal Pro and the GPS would not track with the screen off.

Checked all the settings I could in LocusPro and Sportypal, and left GPS Status running, to no avail.

After a while the power bar GPS icon kept flashing even when GPS Status showed that GPS was connected.

On 0817 and new data image.

Any ideas?

Thanks

M.
[HD2 Android SD Development] bernard.bb:
Hi, About the battery drain i have the same problem??), otherwise this rom is great :)

Thanksss

BB
[HD2 Android SD Development] JustX:
Battery drain has more variables to take in account besides the build.

The age of your HD2 hardware (battery).

The strength of the mobile data connection.

The age or condition or brand or AGE of your SD card.

Maybe look into those reasons as well if you are having problems.
[HD2 Android SD Development] bernard.bb:
Yes It's thrue, I am also looking on that side. Thanks for help
[HD2 Android SD Development] iPAQ 6515a User:
No dice :(

I guess the search for the solution continues
[HD2 Android SD Development] soapbox23:
I was having random reboots with the GPS libs 1.7 and greater. The only thing that worked for me (and is currently working now) is using the 2.0 RPC libs, and editing the governor in CM settings to "conservative" and the min frequency to 245. I don't know if this impacts battery life at all and i know that "interactive" is the recommended setting, but conservative is the only one that keeps my phone stable. maybe give that a try?
[HD2 Android SD Development] clarkg:
I'm not sure it was one issue. I still had a working vpn after the April issue, but I use a different kernel. I think Warren fixed that in his later, but sometime in June I lost the ability to connect to my vpn as well. I think that one (which is still with us) was introduced in one of the nightlies then. One of the posters in the issue log for 3353 pinpointed the build number where it stopped working, so it just needs someone at CM to check those code commits.
[HD2 Android SD Development] uzi2:
GPS overheating

All of the proposed solutions are useful, in that the HD2 on constant charge and under a heavy workload is expected to get hot, so any attempt to cool it down has got to be good. I was going to add that it is placed in a cradle which isn't going to help in keeping it cool.

However, no such problems were seen using navigation software with WM6.5, so the underlying problem is buried somewhere deep in the implementation of android on the HD2.

If a solution is found, it will probably improve a number of other issues as well.
[HD2 Android SD Development] clarkg:
Try "Tracker Booster"... free from the market.
[HD2 Android SD Development] MarkAtHome:
FWIW, I am unable to change my selection away from ONDEMAND with the latest nightlies (as of this morning). I normally use INTERACTIVE.

I've heard rumblings that is not ROM specific.
[HD2 Android SD Development] oainot:
you may try MyPhoneExlorer http://www.fjsoft.at/en/

it would be fine.
[HD2 Android SD Development] dttung80:
I think it not the best solution.

Copy 2-5Gb by wifi connect ?... that not acceptable. I think the USB function have problem. :)
[HD2 Android SD Development] RobE.:
Hard to say what your USB problem might be. Did you install the android ADB USB driver onto your computer? When you connect with USB are you turning on USB storage after the USB is connected? (It's not automatic and some programs require it) Do you turn off USB storage before you disconnect.

I use Android Commander to xfer files via USB between the HD2 and my PC. That's not only one way of doing it, and I know I don't have all the answers. Getting USB to work on my PC with android was at first, a mystery to me. With windows it's easy... with android, it took some reading and some effort. Once it's setup correctly; I know the UBS file transfer function works well.

The USB function doesn't have a problem. It's something else you left out, or aren't doing correctly. I wish I could help you more, but it's not the device, and it's not the ACA build (all things being equal). Maybe your connector or plug is defective? - It's not the build, that's for certain.
[HD2 Android SD Development] JMG01:
If you fancy trying an older ACA build there are old builds here:

Ipaq's link: http://uploading.com/linklists/debamfea/ACA

A couple of the K refs look inaccurate, but it's a very useful archive.

The zImage files are not updated with every build, and I find any build that used one from 0630 worked for VPN. It's still strange that using that same zImage with later builds also enables VPN (but has other incompatibility issues). These are the various zImages that come with the recent official builds.

Build	DIR	Date	time	Size	File
070511	\AmeriCanAndroid 070511\AmeriCanAndroid 070511\Android	06.30.2011	09:22	1,647,916	zImage
070811	\AmeriCanAndroid 070811\AmeriCanAndroid 070811\Android	06.30.2011	09:22	1,647,916	zImage
071511	\AmeriCanAndroid 071511sd\AmeriCanAndroid 071511SD\Android	07.14.2011	22:35	1,711,096	zImage
072511	\AmeriCanAndroid 072511(sd)\AmeriCanAndroid 072511(sd)\Android	07.26.2011	02:46	1,717,852	zImage
072911	\AmeriCanAndroid 072911(sd)\AmeriCanAndroid 072911(sd)\Android	07.30.2011	08:08	1,717,812	zImage
080711	\AmeriCanAndroid 080711(sd)\AmeriCanAndroid 080711(sd)\Android	08.08.2011	01:07	1,717,812	zImage
081211	\AmeriCanAndroid 081211(sd)\AmeriCanAndroid 081211(sd)\Android	08.12.2011	08:20	1,717,812	zImage
081711	\AmeriCanAndroid 081711(sd)\AmeriCanAndroid 081711(sd)\Android	08.18.2011	04:41	1,717,892	zImage

How come you are using Ty?
[HD2 Android SD Development] geenyous:
I don't agree, the solution is not that deep. I never had it before the AGPS implementation and I used to do a lot of navigating. Its something with the new libs that let the phones get very hot. At the end of the day, if it doesnt imporove, I might go back or at least keep the old set of libs handy. I'd much rather wait a few mins before having a fix to then have a reliable navigation system than an instant fix and a dead phone after 30mins.

Wrong mate, the USB function does have a problem and for quite some time now (since going from 2.3.3. to 2.3.4 if I recall correctly). We never had to use another program to get it to work. Sometimes it still works, but you have to reboot to see the files and sometimes it just only copies half.

Never the less, having the stock usb storage function corrupt your data.img is a first and was hopefully an isolated case.

Actually, its not as someone said before. Every kernel has some .ko files that come with it (for stuff like wifi, BT and so on). If you don't have the correct kernel - .ko files combination some things won't work. But extracting the right ones is not that easy. If the dev doesn't support you with the right combination, then I am afraid you cant really test the kernel.

Have a look at a tytung kernel release to see what kind of files are needed.
[HD2 Android SD Development] JMG01:
@geenyous

Thanks I was not sure where to look for other parts of the Kernel.

I meant it was strange that an older zImage could make VPN work. I don't think it strange that most other things didn't!
[HD2 Android SD Development] antiquezip:
First of all I would like to express my thankfulness to Cope and Warren for such a great build. I am using AMA since March and constantly update with new version without a single problems

However, beginning with August builts I am experiences a lot of data drop and sometimes it tooks minutes to reconnect

Anyone having the same problems and solutions / suggestions would be highly appreciates

Thank you
[HD2 Android SD Development] uzi2:
This Rom defaults to interactive. The one you are using defaults to ondemand. Both Roms will respect the profiles you set in SetCPU.
[HD2 Android SD Development] uzi2:
It depends on your definition of deep, or whether you believe that the problem is caused by the new libs or just exposed by them. I believe that there are underlying problems in the implementation of android on the HD2.

AGPS but only with potential overheating.

Good sound, but only with high mic gain

LED notification, but not with custom brightness

Voip, but potential sound and dialler problems

I'm sure there are more...

Is Viber now working for you? The recent changes to libaudio implemented by CM7 allowed skype to work, but then there was a new version of skype which reintroduced the sound issues :(

Edit: I see that there are a number of additional changes to libaudio in the pipeline from CM7 to be included in the next nightly. Then it will be time to try the new version of skype again.
[HD2 Android SD Development] flashy:
Thanks to you guys, this is the best SD Android build ive found, and not found any graphics glitches yet!
[HD2 Android SD Development] geenyous:
Ok, you are right in that it depends on the definition :D

I like AGPS for a short post of my location in whatsapp for example, that was not possible before as it took ages to get a fix. But, for long time navigation I need a stable GPS lib. So if the problems others and myself with NMEA have had will come up again with RPC, I will copy the old libs back before doing heavy navigation. Costs me 4mins with reboot and wont happen that often anyway.

Regarding sound, I have put back the old default.acdb because the louder sound was not good at all, much too shrill and way too loud on the lowest setting while on the phone.

LEDs are no issue for me, they work perfectly.

And regarding VOIP, since I am using the libaudio from audio_fix_v2 I never had any problems anymore, except the bad connection on viber in general, but no more crashes.

BUT, note that I am still on JUL07!

I made my own adjustments like new GPS libs, kernel, default.acdb, libaudio.so, gps.conf and ramscript and now its the best experience I ever had on my HD2. I have a drain going down to 4mA (!) with all the radios enabled and have never seen a drain higher than 550mA, even while running navigation and trapster in the background at the same time (without charger connected of course ;)) Usual drain while browsing is at around 150-250.

If I now find another solution for the USB mass storage it will be perfect.

Don't take this as an advice to what you should do, I just experienced very bad drain on 2.3.5 (60mA+ in idle and 750mA+ in use) but that very well may be a set up problem on my side. Nevertheless, I am more than happy and will most probably not update in the forseable future, unless something big will happen.
[HD2 Android SD Development] uzi2:
Nand - you have perfection :D
[HD2 Android SD Development] dttung80:
Thanks for your guide. But the early builds ACA before August, i used USB function ok, still 12-12Augst have always problem when use USB Mass storage function. :(
[HD2 Android SD Development] dttung80:
Some times my SD data have problem, i'm so worried that the NAND have problem and my phone is becomed a beautyful brick. :mad:
[HD2 Android SD Development] maneken25:
You dont need to worry, this build doesn't have gfx glitches, only others hd2 dev builds with use htc sense 3.0 have it. :)
[HD2 Android SD Development] PlayStation:
I always have a my custom winmo rom (LEOIMG.nbh) saved in the root of the Sd card. Should something terrible happen to the Nand rom when I am out there and with no PC anywhere nearby it is a simple question of flashing the winmo rom via the micro sd method.

I also have an Android rom saved in the sd so that should it become necessary to flash the winmo rom I can similarly dual boot Android sd rom until such a time that I can sort out the nand problem. Easy does it. :cool:
[HD2 Android SD Development] backlashsid:
I am a new NAND User of this ROM and I have a few questions for other regular users who have been using this ROM for quite a while now.

How is the battery life on your device ? What other steps have you taken to increase the battery life in any way ?

When I installed the NAND Rom I did not format the SD card when I came from Windows Mobile for I had pictures in it. Do you think this is a problem and I should have formatted it for it has anything to do with the Android performance/battery use ?

Which software/app would you recommend for backups ?

Also do I need to install LED me know BETA ? Or is the ROM made in such a way that it handles the notifications well enough with the lights.

Kindly answer my queries I have.

Much Appreciated.:)
[HD2 Android SD Development] xavierh:
i am using 40% brightness only enable wifi or bluetooth when you actually need them.

for backups I use titanium backup.

you do not need led me know.
[HD2 Android SD Development] uzi2:
You are using an outdated version of android with an outdated kernel with an obsolete audio fix. Perhaps you should be looking to the full releases of CM7 rather than this nightly build?
[HD2 Android SD Development] sth_safal:
Yeah.. sure.. I have attached here.. Check it out.. I dont use WP7.. :)
[HD2 Android SD Development] alaindev:
liboemcamera.so : leo vs bravo

Hello copenhagen,

my original post :

your answer :

Yes, however there was an inversion in my post, that I corrected later :

in fact, it's in the fix where "bravo" has been replaced by "leo "

which makes a lot of sense since this build is described as "pure leo".

Thus, something SOMEWHERE in the build is looking for a leo, but the original liboemcamera.so (BEFORE the fix) only contained a bravo instead. That's why people, when they changed the device name in the build.prop file from leo to bravo where also able to cure the green tint.

Hey, seems you can't refrain to put a doubt everytime I (we) report something ;) I'll do all my tests with a fresh clean install, SD reformatted and no previous data.img nor titanium backup restoration.

Don't worry, your latest build [MAR01], that I just started to test, seems so brilliant that I don't mind. I'll report my findings later.
[HD2 Android SD Development] copenhagen:
when you are releasing something that several hundred people are going to put on their phone and use as an everyday OS.... this cannot and should not be avoided.

everything must be verified.. checked... stress tested.. and approached from all angles before making a final descision.. this is why the doubt factor exists.... it doesnt however mean that I dont trust your findings :)

im thurough.. .and that is never a problem :) or shouldnt be concidered so :)

thanks again for the feedback!
[HD2 Android SD Development] alaindev:
PowerAMP still crashes

Thus, let's continue with this issue I mentioned in following post:

http://xdaforums.com/showpost.php?p=11675372&postcount=1093

In your answer, post #1102, you replied :

Unfortunately, here also, it had nothing to do with old data.img, as I was testing from a clean install.

Now, I have repeated this experiment with your latesd build [MAR01], freshly installed a couple of hours ago (again: no previous data.img).

I was hoping that the DSP Manager fix, which I applied following your instructions, would also cure the PowerAMP crash, but it didn't.

Here I have to put an emphasis :

PowerAMP does not crash when you first install it: it works perfectly right after the first install. PowerAMP crashes at each subsequent reboot !

I mean, you don't have to launch PowerAMP, it is kind of a service which starts automatically after the boot, and crashes with the message "The application PowerAMP (process.com.maxmpz.audioplayer) has stopped unexpectedly".

It is not something urgent, I can live with the workaround I have described in the original post, but it would be nice if yourself or Warren could have a look at it. Thanks very much.

(by the way, you can easily download the free (trial) version on the market, if you haven't used it before, it is the nicest player I know on Android, just have a look at the equalizer...)
[HD2 Android SD Development] titoxperiax10:
Yeah!!!... the two fixes (one for the camera tint green, and for the DSP ) works like a charm.... thanks guys... I love this ROM, fastest, and my battery life is so good... (like 2 days)...
[HD2 Android SD Development] ataf:
Is it only me with 3g not working?

This is the biggest issues for me

Battery consumtion is 200% more than 02-21-11
[HD2 Android SD Development] StarLog:
I have to say, this build is great, battery drain is very low, I can run for almost 24 hours, without recharge.

All I need is working, thanks
[HD2 Android SD Development] nygmam:
Two posts contradicting each other back to back, which is it. I tend to believe it is acceptable, based on my past experiences. Thanks for the update, loading it now. I think i may go with a new data image this time...