yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] zsandras:
Same as you, but I always clear before and after flashing cache and Dalvik cache and than than fix permissions.

As I see battery drainage is perfect and it's a bet faster as the previous version.

Thx TAYTUNG for the nice job.

You are always grate.
[HD2 Android NAND Development] BD002:
Updated with MAGLDR from 3.0 to 3.1. Did no wipes and booted up without problems. So thanks for the nice Rom, cheers mate.
[HD2 Android NAND Development] cariocap:
tytung said here that it's not necessary to clean dalvik cache.
[HD2 Android NAND Development] jjrumph:
Flashed 3.1 with CWR over 3.0. No issues. Wifi picked right up and away we go.

Nice Job again Tytung..
[HD2 Android NAND Development] CROrION:
does this rom support croatian language?

I'm on miui now, how to flash this one over it?
[HD2 Android NAND Development] cariocap:
There is Hrvatski language, I'm not sure but I think it's croatian.

In the first post you find the install instructions.
[HD2 Android NAND Development] Macelangelo77:
I did a clean install:

- Task 29

- Installed cLK

- Installed CWR with recommended partition layout

- Used SD Formatter (Full/Overwrite) for my SD-card

- Used Minitool to create a FAT32 (primary) and an Ext4 (primary) partition

- Power off my phone, reinserted sd card

- Copied ROM to my SD-card

- Booted into Recovery

- Clear data/factory reset, clear Dalvik Cache

- Installed ROM v3.1

- installed cLK-ppp update

- installed dtapps2sd

- Cleared data/factory reset, clear Dalvik Cache again

- reboot

--> Boot loop at Nexus One bootanimation

- Removed battery

- Booted into recovery

- Formatted /system and /boot

- Clear data/factory reset, clear Dalvik Cache

- Installed ROM v3.1

- installed cLK-ppp update

- did not installed dtapps2sd

- Cleared data/factory reset, clear Dalvik Cache again

- reboot

--> Boot loop

- Removed battery

- Booted into recovery

- Formatted SD card with recovery > Advanced > 1024Gb, no swap

- Formatted /system and /boot

- Clear data/factory reset, clear Dalvik Cache

- Installed ROM v3.1

- installed cLK-ppp update

- did not installed dtapps2sd

- Cleared data/factory reset, clear Dalvik Cache again

- reboot

--> Boot loop

As I am serious case of ORD, I can basically install new ROMs with my eyes closed, it seems that there is something with (at least the cLK-edition of) v3.1

This has never happened to me before...

Going to try installing v3.0 (as I came from MIUI/CM/Pyramid stuff and want to go back to my roots :D)

Sincerely,

Mac
[HD2 Android NAND Development] scorpion44:
SD version of 3.1

SD version of 3.1 can’t go further than boot animation for more than 30 minutes.
[HD2 Android NAND Development] asb_:
Downloading ...
[HD2 Android NAND Development] cariocap:
Have you tried to format your SD card with Panasonic SDFormatter ?
[HD2 Android NAND Development] luismendez:
SAME HERE!
[HD2 Android NAND Development] Macelangelo77:
That probably won't matter... The same issue is reported for MAGLDR/cLK/SD versions, so apparently there's something wrong with the build. I haven't seen anyone with a clean install, installing it with success. It seems like the only ones running v3.1 are those who upgraded.

Just wait until Tytung wakes up... he'll figure it out.

Sincerely,

Mac
[HD2 Android NAND Development] Mrakes:
confirming boot loop with fresh install on clk
[HD2 Android NAND Development] Macelangelo77:
Just repeated the full procedure as described above, started from scratch again, same issue with v3.1 MAGLDR: boot loop.

So people, as we have confirmed issues with MAGLDR/cLK/SD-version, please hold back on installing untill Tytung responds. Upgrading seems to go fine though (see earlier posts).

For now, I'm installing v3.0 MAGLDR, as I need a working phone and changed the partition layout (so my Nandroid backup is useless...)

EDIT: Just installed v3.0, went fine, so it's something with v3.1. Will try installing v3.1 on clean install over v3.0. For now, restoring Gentle Alarm, as my alarm goes off within 5,5 hours...

Sincerely,

Mac
[HD2 Android NAND Development] w0nz3r:
Boot loop on X screen

Fresh installation CLK
[HD2 Android NAND Development] jeoffrey:
Boot loop on X screen

Fresh installation Magldr
[HD2 Android NAND Development] cheezusweezel:
I got the "clean-install-bootloop" too, but the answer is to flash 3.0 and after first boot flash 3.1 over fresh 3.0 install ... :cool:

MAGLDR version for me.
[HD2 Android NAND Development] corrsea:
Definitely no problems with upgrade from 3.0 to 3.1 clk (not wiping or backing up anything)
[HD2 Android NAND Development] dicksonjoe:
I have (Android-2.3.5) and I want to upgrade to (Android-2.3.6).zip

How do i do it? thanks.
[HD2 Android NAND Development] mskip:
Ok this is confirmed that there is a Bootloop on the 'x' screen when coming from another Rom straight to v3.1.

However if you first flash v3.0 and then after a first boot flash v3.1 over it without wiping anything it will boot up fine.

Please dont clog up the thread with anymore bootloop posts and wait for Tytung to fix v3.1 or just flash v3.0 and then upgrade.

Mark.
[HD2 Android NAND Development] mskip:
If you have v3.0 then boot into Recovery and flash v3.1 over it without wiping.

Mark.
[HD2 Android NAND Development] w0nz3r:
CONFIRM

1. Install 3.0

2. Install 3.1 without wipe anything

3. Reboot with no loop

Thanks =)

EDIT: CLK version
[HD2 Android NAND Development] astaccz:
I love this vanilla rom. The only thing is that the battery goes down kinda fast. Anyway to fix that?
[HD2 Android NAND Development] kcfong2:
Speaker volume too high, causing dropouts in voicemail message playback

Hi Tytung,

Beginning with the r12 kernel, I noticed that the speaker volume (when using speaker phone), is set much higher than in r11 kernel. This is causing a problem when I play back my voicemails via speakerphone. The playback keeps dropping out... it appears that the volume is so high that the mic picks up feedback or vibrations and confuses it with someone talking. If I mute the mic, all playback is fine. Of course if I drop the volume some, it helps too, but it's still not as "perfect" as it was with the r11 kernel.

I flashed back to r11 kernel with the current rom, and the problem went away.

Can you advise what files, parameters and settings, etc you changed in r12 that affects volume and gain? This way, I (and others who may have this problem), can still flash your 3.1 ROM, but just "back out" the volume related changes in r12.

I can "record" a sample of what I'm experiencing if it will help you, but I think I was clear enough with the above explanation.

Thanks again!
[HD2 Android NAND Development] slbenz:
You need to give us more information. What radio are you on? Version? Using overclock? Apps running in background, using GSM auto PRL, etc. Giving us more information will help us help you. On v3.0, I was seeing 2-5mA standby battery drain. My early findings for v3.1 show the same. This with the NAND version.
[HD2 Android NAND Development] Sunmj:
I have the same problem and confused for some days
[HD2 Android NAND Development] Rick_1995:
Android 2.3.7 out, lol. Altough nothing much instore for non NFC devices.
[HD2 Android NAND Development] astaccz:
I'm on radio 2.15.50.14. No overclock. Version 3.1. Fresh install 3.0 after boot, rebooted flashed 3.1. No apps yet. I don't use titanium backup. I fresh install everything. Mag not clk. The auto pro GSM I don't know what you mean I'm really new to android. Switched from windows mobile.
[HD2 Android NAND Development] slbenz:
Could you give us an indication how much battery drain you are seeing?
[HD2 Android NAND Development] MartyLK:
I'm getting a bootloop at the quad-colored X on this latest cLK ROM. I've flashed twice, each time doing Task 29, and it just won't boot.
[HD2 Android NAND Development] slamming_sammy1:
little more apps/widgets?

I love this rom because it's so fast and light. but being light, i guess that's why it's so fast as well. anyone know if it's possible to download all the htc widgets somewhere? or any chance some of these widgets and apps can be built into maybe a richer version? thank you!
[HD2 Android NAND Development] trex3300:
Here is the solution:

http://xdaforums.com/showpost.php?p=17862259&postcount=7496
[HD2 Android NAND Development] astaccz:
About 10 percent in maybe 15 minutes. I'm waiting till it gets very low then I'm going to do a full charge. Maybe its because for the past few days I've been taking my charger off with out it getting a good charge.
[HD2 Android NAND Development] MartyLK:
Eh...I did a backup of V3.0. I will restore it and wait for whatever is wrong with V3.1 to be resolved.

By the way, I flashed V3.1 directly on a wiped HD2...wiped with Task 29. I didn't flash V3.1 directly from V3.0.
[HD2 Android NAND Development] corrsea:
Search for the battery calibration thread and follow the instructions there. You may need to flash the clk version or flash back to Winmo so that you can fully charge your battery while the phone is switched off in order to recalibrate it.

This problem trends to arise if you flash an Android ROM and your battery is not fully charged.

There are also some apps on the market that claim to be able to calibrate the battery. Search market for battery calibration.

Normal battery consumption for this ROM is 20-30 hours with light to moderate use and about 10 hours with heavy use so please persevere.
[HD2 Android NAND Development] seanyuan62:
I am assuming that mobile hotspot/tethering is still working since it is only parts of the 2.3.6 base? Thank you
[HD2 Android NAND Development] Wafong:
don't know why, you can install the zip, but after you reboot, it just stuck in the reboot screen and can not go into the system. BTW, before update to 3.1, i have wipe all the data and reset the factary...

any one have the same problem?
[HD2 Android NAND Development] TheInVisibleGoD:
Your answer is not to far from here, just 2 pages back...

http://xdaforums.com/show...postcount=7496
[HD2 Android NAND Development] osenevp:
Thanks for pointing me out. This is definitely router issue. Now at my office, there are no WiFi disconnects at all. I can say more, @office HD2 connects to Cisco AP1131AG access point, @home to Cisco 871W soho router. Software versions are different:

Cisco IOS Software, C1130 Software (C1130-K9W7-M), Version 12.4(25d)JA

Cisco IOS Software, C870 Software (C870-ADVIPSERVICESK9-M), Version 15.1(1)T3

I'll try to play around with router's configuration/update software on router. If no joy - downgrade to V2.8.
[HD2 Android NAND Development] asb_:
Just download the ZIP, copy to SD card and install.

It's running 100%.

Thanks
[HD2 Android NAND Development] hutc:
android 2.3.6 build problem

i think this build along with miui build 9/23 too has boot problems both are in boot loop checked twice on my htc hd2 and conffirmed that you dont see it if you upgrade your preexisting system.

by the way best build of android with no add ons the video recording is the best compared to all other builds and so is the camera thank you mr tytung very much i switched from desire hd base to nexus hd2 for good its fast quick and damn stable.
[HD2 Android NAND Development] watnuweer:
Dutch language is gone

I noticed in this version that the Dutch language is not correctly loaded.

When I select it I still get english.

Other languages seem to be fine, and in previous versions I had no trouble at all.

Can I do anything about it?
[HD2 Android NAND Development] tytung:
From memin1857's post.

I think you can try to lower speakerphone mode gain.
[HD2 Android NAND Development] tytung:
Android 2.3.7 for Nexus S 4G is out before Android 2.3.6 for Nexus One is out.

But as you said, the updates of Nexus S 4G is mainly for NFC.
[HD2 Android NAND Development] tytung:
I didn't try v3.1 clean install before.

I will try it later.

Maybe someone can provide logcat before I go home and try clean install.
[HD2 Android NAND Development] clyder:
@tygung. Can you give your opinion about this?

I am typing this here because this is an issue on all the roms I tried, including NexusHD 3.0.
[HD2 Android NAND Development] w0nz3r:
12% in 8h

Standby mode

Data mobile on

Push GMAIL

Push Whatsapp

Configured 4 Exchange account with sync disabled

CLK Version

Regards
[HD2 Android NAND Development] mikegee:
Greetings tytung and congrats on developing a great rom!

i was wondering if there is any way to have different LED color blinking lights for different notifications. for example on a missed call have a green blinking light and for a low battery an amber one (as it is now). I know that cm7 provides that capability through its cm settings but i was wondering if aosp branch does as well.

Cheers!
[HD2 Android NAND Development] Cheech1976:
I don´t have a clue if this can be setup in the system somewhere, but you might want to try LedMeKnow (free from the market), there you can set it up the way you want to.
[HD2 Android NAND Development] trigonX:
Dear tytung :)

This rom is the very best! Thank you for that! I have only one suggestion - please do not boost volume any more in next releases or we will soon turn deaf. :D

Have a nice day!
[HD2 Android NAND Development] pepemonje:
Hi everyone.

Like many of you, I got stuck with 3.1 until I upgraded from previous version. But now the problem is that I get continuous reboots when I try to install anything from market.

Could you please tell me if it is happening to you too...........

Thanks and regards,
[HD2 Android NAND Development] Macelangelo77:
How can I provide a logcat when boot looping? Is there a trick to do that?

Sincerely,

Mac
[HD2 Android NAND Development] w0nz3r:
+1

how can we report log if the system is not started?

regards
[HD2 Android NAND Development] stirkac:
connect phone to PC

open cmd -> adb logcat ;)
[HD2 Android NAND Development] tytung:
adb tool

You can get Windows version of adb command tool here.

Type adb logcat > D:\temp\logcat.txt in Windows Command Prompt (executable name cmd.exe ).
[HD2 Android NAND Development] Macelangelo77:
Ah, I see. Can't do that at work either, so we'll have to see who gets home first ;)

Sincerely,

Mac
[HD2 Android NAND Development] hesian:
I just successfully upgraded from 2.9 to 3.1 without a 'boot loop', for anyone else a release behind.
[HD2 Android NAND Development] theforceguy:
I could not get the Nand version installed I had to install WM and do a SD version install Well it runs flawless on SD but I would like to get the real deal :o
[HD2 Android NAND Development] nvidiaati:
use mag v3.0 and flash TYTUNG_R12

incall or outcall background very noise

thanks
[HD2 Android NAND Development] Achen_su:
love this rom. fast. and stabil. and support add on chinese keyboard and htc keyboard.

hope some one can make add on for htc messager(Sms/mms)

i success move dalvik cache to sd ext. and after install rom the free space of internal 266mb. use a2sdgui.

hope some one can move system/app, framework to sd(sys-parts/app, framework, lib. . to make nand internal free space more.
[HD2 Android NAND Development] w0nz3r:
Logcat boot loop

Hello,

i've logged the loop boot with new installation of 3.1 Version

You can see it in attachment

Regards

EDIT:

What is this?
[HD2 Android NAND Development] p0is0nb0x:
hey friend thanks so much for you extreme effort... I have been following this thread for almost a month now and am planning to setup android very very soon... but, one question is triggring me a lot... and it is that while the T-MOBILE HTC HD2 is Window based it has a screen resolution of 65K so, what would it be when android rom is installed... please take time and let me know the result.. it wouldn't matter a lot but, it is just the eagerness thats forcing me to ask these...!

anyways once again thanks a lot of putting up soooooooooooo much effort in developing a rom for HD2 as u are really giving it a new life....
[HD2 Android NAND Development] tytung:
Thanks.

You save my time. :)

It's system apk signature mismatch issues.

I will fix it when users do a clean install.
[HD2 Android NAND Development] darkony:
what users I wanna boot sd version clean or update but no help make root folder with auto install fix no need to reupload whole build
[HD2 Android NAND Development] MrNova:
Your defintaly not the only one, i also updated to this 2.3.6 version but the first thing i noticed was that the Dutch languages is wrong loaded or totally gone. The update went good btw, but i did switched back to 2.3.5 because of the languages bug. I must say awesome roms you make, use them all the time! :) Tytung is there maybe a change that you can look into the 2.3.7 rom and see if the Dutch languages gets correct loaded in there? Great work again!
[HD2 Android NAND Development] Macelangelo77:
You just beat me by 20 minutes :) Thanks for the logcat. Glad Tytung figured it out.

Sincerely,

Mac
[HD2 Android NAND Development] :
I have the same bug for SD NexusHD2-Gingerbread V3.1 SD version
[HD2 Android NAND Development] ChitownWingMan:
Installing 3.1 on SD Card to auto boot with magldr

Do I need to copy the magldr boot ("boot magldr.rar") files on top of the SD download (NexusHD2-Gingerbread_V3.1_SD_(Android-2.3.6).7z)?

Tytung, thanks for the amazing work.

Hopefully this will solve my crashing and FC problems.
[HD2 Android NAND Development] contactwajeeh:
Request: Can you create a DAF version of this please...

Hi Tytung,

Can you please provide me a DAF version of this beautiful release of yours. Would appreciate if you can do that. Looking forward for an positive response from you. Thanks in advance.
[HD2 Android NAND Development] maddoc1007:
boot loop

i did a clean install of rom booted up great was working good but everytime i clicked on market it went to x for few seconds and then onto homescreen ?? do i need to install 3.0 first and boot then install 3.1 ??
[HD2 Android NAND Development] tytung:
AFAIK, you can dual boot WP7 and Android SD build with MAGLDR.

But you cannot dual boot two Android if you use my SD build with MAGLDR.
[HD2 Android NAND Development] tytung:
I won't make any DAF version.

Please learn CWM install method.
[HD2 Android NAND Development] trex3300:
Hi Tytung,

I am trying to replace the Google maps in v3.1 with the one from v3.0, (I don’t want the Google maps 5.10). Do I just unzip both v3.0 and v3.1, copy the maps.apk over and zip it back? Or do I need to do anything special like fixing permissions etc.?

I also noticed another app called street.apk in the system apps, is that the Google maps street view app? Do I also need to copy that from v3.0 to replace the one in v3.1?

Finally, if I remove the maps apk completely from the v3.1 zip file, can I install that map.apk later by copying it onto my SD card like any other apk file?

Thanks.
[HD2 Android NAND Development] contactwajeeh:
@Tytung

I mean to say the DFT usb flasher version. Would appreciate if you can help me out in this regards.
[HD2 Android NAND Development] w0nz3r:
You can replace the old maps.apk and street.apk in the zip/system/app folder

If you remove completly maps and street you can install it from sdcard. But I think is better if you replace the 2 apk in system/app

regards
[HD2 Android NAND Development] ChitownWingMan:
Boot Loop

Tytung,

I believe I am in the boot loop. The phone has been on the "merging strings" screen for more than an hour.

Here is my setup:

T-Mobile USA HD2

Windows Mobile 7 in NAND

MAGLDR 1.13

V3.1 on 16 GB Class 10 SD Card.

Auto boot from MAGLDR to SD Android

Installation Procedure:

Delete Android Directory from V3.0 SD Card. All other directories off of Root on the SD card were preserved.

copy over new V3.1 Android directory

Boot.

2nd Installation Procedure:

Take above SD card and copy Boot Magldr directory over existing files in the Android directory.

Both installations result in the the animated boot screen staying running forever (for at least an hour).

Any ideas? What can I try?

Thanks in advance...
[HD2 Android NAND Development] Juno-First:
I just installed this ROM for the firs time & getting a bootloop.

This is how I install:

format ext4

task29

install RUU_signed_cLK_1.4.0.1_system_135_cache_2

from fastboot install cLK_CWM_Recovery_v3.2.0.0

from recovery install from sdcard NexusHD2-Gingerbread_V3.1_NAND_(Android-2.3.6) + cLK_ppp_tytung_r12_update

As im new to this particular ROM is there anything im doing wrong, thanks.

[Edit]

Ahh, post 1 has been updated:

V3.1 have boot loop issue if you do a clean install.

I will fix it and release v3.1a later.
[HD2 Android NAND Development] trex3300:
Tytung is going to fix the boot loop issue later and upload v3.1a when it is ready. For more information, read the first post.
[HD2 Android NAND Development] Ryukenden:
I can confirm that if u flash 3.0 ROM 1st and then flash 3.1 without wiping anything works fine.

I've done that, and thats the only way to avoid bootloops.
[HD2 Android NAND Development] Juno-First:
Heh heh yeah I just did that too ;)

2.3.6 v3.1 works now after installing v3.0/tytung11 first
[HD2 Android NAND Development] xanthrax:
what about app2sd ? are we able to move the aps onto sd ext , like ext4 ie ... ? or , does it goes automaticaly ?
[HD2 Android NAND Development] robs1971:
mms problem

Hi

Rom is running perfectly except I cant seem to send mms's, have checked apn's etc all correct....mms just sits saying 'sending'. Im on o2 uk.

Thanks in advance for help :)
[HD2 Android NAND Development] KCLT:
Have you tried changing the wifi advanced settings - sleep to never ?

If the wifi disconnects frequently it might be because of the battery saving setting.
[HD2 Android NAND Development] Panda_Face:
CWM is way better imo.
[HD2 Android NAND Development] ChitownWingMan:
SD V3.1 Install on top of SD V3.0 install does not work either.

I also tried the following installation procedure:

Take a working V3.0 SD build

copy V3.1 files on top of V3.0 replacing all files in common.

Still stuck at the animated boot screen.

Did I do something wrong?
[HD2 Android NAND Development] trex3300:
The problem is system apk signature mismatch, tytung has promised to fix it and upload a new v3.1a when ready. Read the first post.
[HD2 Android NAND Development] ChitownWingMan:
That is why Tytung recommended that I install 3.1 over 3.0. I was just informing him that tried that and it did not work and I was checking to see if I did something wrong.
[HD2 Android NAND Development] trex3300:
It works for people with Android on NAND, you just have to wait for v3.1a.
[HD2 Android NAND Development] maddoc1007:
camera

if u install camera 360 or vignette main camera on phone stops working even uinstalling will not fix this why is this? also found if you reinstall 3.1 the bootloop reappears its ugly head when ever you try and install an app which means you have to reinstall 3.0 again first before 3.1

---------- Post added at 01:19 AM ---------- Previous post was at 12:54 AM ----------

wiped cache partition data reset wiped dalvik cache reinstalled 3.0 seems that installing 3.1 has corrupted phone bootloop now on 3.0 when installing apps reinstalled 3.1 now constant bootloop on x looks like have to start from scratch???

---------- Post added at 01:38 AM ---------- Previous post was at 01:19 AM ----------

had to reinstall magldr recovery again to stop bootloop think ill leave it on 3.0 till3.1a comes out too much hassle installing and reinstalling 3.1 and 3.0 over and over again:(:(:(
[HD2 Android NAND Development] seanyuan62:
Right, I am just staying on 3.0 for now-has been stable for months now