yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] fras-xda:
Hello,

I want to try this kernel too, but

Dorimanx says that for other roms a change in the file

initrd.gz is needed, and I don't know how to do this.

The file that you uploaded is ready to flash with our rom (tytung) ???

If not, please can you include these mod?

Thanks
[HD2 Android NAND Development] Yank555:
The file I posted above is

exactly

that, it includes the init.gz of NexusHD2 v3.2a ;)

Hence the end of the filename "Kernel-Dorimanx-V3.9-ULTIMATE-HD2-MAG-CLK-NexusHD2.zip" :D

JP.
[HD2 Android NAND Development] Yank555:
Hi,

I just had 2 problems with Dorimanx 3.8 kernel :

- bluetooth car kit connected, but couldn't place a call

- black screen of death

I'm back on 3.2, will try 3.9 tonight.

JP.
[HD2 Android NAND Development] Yank555:
Flashing kernel 3.9 right now ... let's see how it works out ...

JP.
[HD2 Android NAND Development] Yank555:
Hi,

OK, first impressions ...

The bluetooth car kit problem is still there, it's not that bad, actually I generally get a "Dial Up Failed.", but a few seconds after that the call is placed.

Didn't have a Black Screen of Death (yet) which I had on 3.8, so it's better.

But, I forgot to set the lowest CPU frequency to 96, it was still at 128.

I also have a wakelock at around 70mA :( I guess it must be related to the bluetooth issue since I haven't used the HD2 since booting 3.9 for anything else.

I just gave a look at BetterBatteryStats which shows a wakelock "proximity", so it also might be related to the proximity sensor...

On the other hand, 3.9 is incredibly damn fast ! Really a huge improvement over 3.2 or stock NexusHD2 kernels (r13, r14).

I will now reboot and keep giving it a chance, the performance improvement is just impressing, so it's well worth trying some more :D

JP.
[HD2 Android NAND Development] Macelangelo77:
Hi JP,

Thanks for repacking 3.9 with the proper initrd.gz

My best guess would be that the wakelock is indeed related to your bluetooth issue. I don't use bluetooth and have been on 3.9 for some hours now, but no sign of wakelock. Thanks for the tip about betterbatterystats. Went to the market, couldn't purchase (incompatible with Nexus One), search XDA and found the app here :)

Sincerely,

Mac
[HD2 Android NAND Development] fras-xda:
Thanks jp, but I can't download the file. Is there any problems with xda servers?

Enviado desde mi Nexus One usando Tapatalk
[HD2 Android NAND Development] fras-xda:
Forget it, I finally get the file

Enviado desde mi Nexus One usando Tapatalk
[HD2 Android NAND Development] KrewsialNL:
I dont get it... I keep getting high standby drains with tytung r14 and the Dorimanx ones. 127mA and 70mA ... never had this before. Even with wifi and gps off.. :S
[HD2 Android NAND Development] Yank555:
Hi,

Just posted

this

in Dorimanx's kernel thread.

JP.

---------- Post added at 10:06 AM ---------- Previous post was at 10:03 AM ----------

Very strange ?! Have you changed something specific, added an app, updated some apps ... ?

I never get drain above 10mA in standby (except with a wakelock like with Dorimanx's 3.9 kernel (see post above).

Try to use "BetterBatteryStats" (you can find it on xda quite easily), it helps pointing toward what is keeping your device running.

JP.
[HD2 Android NAND Development] KrewsialNL:
I did not change anything.

I will look into the above, thank you, sir :)
[HD2 Android NAND Development] corrsea:
@yank 55

Just experienced a kernel wakelock on dorimanx 3.9. Better battery stats showed 'proximity'.

Not Bluetooth related.

presumably linked to the proximity sensor after making a call?

Otherwise everything about the kernel has been sweet.
[HD2 Android NAND Development] KrewsialNL:
For me its clearly the wifi.

When i dont use it after restart, 4mA. As soon as I use it > 70mA in standby (with screen off profile). When I turn wifi off..same drain.

After a reboot, its ok again.
[HD2 Android NAND Development] pappadj:
Thank you, I kept thinking it was my Bluetooth or GPS or sync that was lingering but sure enough, its wifi. I'm using typhoon's latest so I am assuming it is either kernel side or an android design flaw. I will have to restart more frequently now but I have a workaround... thank you!
[HD2 Android NAND Development] Yank555:
Hi corrsea,

Yep, also saw "proximity" first time I had a wakelock (I posted it here).

I think both might be related ... when the lock occurs, maybe the proximity keeps the HD2 awake because you carry the HD2 on you ... ?

When I place a call via bluetooth (having the phone on me) it is turned on, so proximity is activated, and maybe it stays activated by whatever turned it on, so it keeps showing up in BetterBatteryStats ... ?

Proximity isn't even listed now in my BatteryStats (I have no wakelock either at the moment).

But it seems to have worked better this last few hours ... will keep it on 3.9 for now and observe what happens.

But anyhow in the kernel thread there are quite a few having this kind of drain (60-70mA) and all seem to identify a different origin to the problem :?

Eventually it'll be found, I'm confident :D

JP.

---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------

Hi,

Just place a call (no bluetooth involved), the wakelock is there again !!

So you were right, it is not bluetooth induced, but placing the call via bluetooth had the same effect obviously !

No proximity in BatteryStats yet, will leave the wakelock going for a little bit longer, I just set a custom ref point.

JP.

---------- Post added at 03:13 PM ---------- Previous post was at 03:02 PM ----------

Proximity it is, look at my post in the kernel thread :

http://xdaforums.com/showpost.php?p=21880315&postcount=1416
[HD2 Android NAND Development] Superdod:
When I flash the NexusHD or even CM7, why do I have low quality ( 8bit? ) textures for widgets and for some interface parts?
[HD2 Android NAND Development] chrisqck:
Hi Everyone, sorry about this post.. i've search and read multiple posts in this thread bt don't seem to be able to locate one that applies to me. this is my first time flashing HD2.

What I've done so far:

1. Downgraded to HSPL 2.08

2. Install MAGLDR 1.13

3. Installed MAGLDR_CWM_Recovery_v3.2.0.0_for_NexusHD2_135M.zip

4. Boot to MAGLDR then AD Recovery

5. In CWM, Wipe data/factory reset

6. then Wipe cache partition

7. then Advance then wipe Dalvik cache

8. then reboot

9. copy ROM to SD

10. repeat 4. to go to CWM

11. In CWM install from zip file then choose Zip from SD Card

Then it went through the steps up till installing package then it just prompted "Installation aborted".

What do i do now ? Thanks in advance for help and guidance~!!!

**chris
[HD2 Android NAND Development] corrsea:
First I would check that you don't have a corrupt download of the ROM zip file. Second something may have gone wrong when you transferred the zip to the sd card. Did you do it in magdlr or recovery? Magdlr is notorious for corrupting files. If you have a card reader its best to just transfer the zip to your sd directly.

You could also try a more up to date recovery. I've attached the latest touch recovery. Just copy the zip to your card. Boot into recovery and install it the same way you tried to install the ROM. Then reboot into recovery and try installing the ROM again. No need to wipe caches etc.
[HD2 Android NAND Development] philou15:
Hye,

I have a big problem :

I'm french, and I have FREE MOBILE, and when i put my SIM CARD in my phone, i have some reboot.

You are are in france with this rom and FREE MOBILE for confirm the problem ?

En Francais :

Depuis que j'ai ma carte sim free mobile j'ai des reboot aleatoire, j'ai tout formater, tout tester idem.

Possible que le reseau free face planter le telephone ? pb de rom radio ?

Bref je chercher des gens sur free pour savoir si tout marchez chez eux ?

tks
[HD2 Android NAND Development] chrisqck:
@ corrsea : guess what solved the problem ? i re-formatted the SD card & re-copy the ROM zip file and now it works~!!! i'm running Gingerbread on my HD2 now~!!! woohoo~!!! :D
[HD2 Android NAND Development] corrsea:
good you got there :-)

Enjoy the ROM
[HD2 Android NAND Development] KrewsialNL:
Its a color banding issue. Try flashing Tytung r14 kernel (that works for this rom) to fix it.
[HD2 Android NAND Development] KrewsialNL:
I found the reason for my high drain. Bad mobile reception, causes constant switching between 2 and 3G. When I set 2G...drain is a magnificent 2mA.

I only have to do this when at home (bad reception inside my appartment). When outside or anywhere else for that matter, with 3G/wifi/gps/sync on it draws 5-8 mA.

I had to do a clean install, boot with original kernel, reboot into cwm, flash r14, problem solved :)

Thanks for thinking along guys :)
[HD2 Android NAND Development] wearefree:
@ KrewsialNL,

Unless you need constant data connection, you can try juice defender from the market. It shuts off the data connection during standby, and only re enables that every 15 min (free version, cannot customize) or whenever you start to use your phone.

In situations like yours, it will save a lot of battery power.
[HD2 Android NAND Development] corrsea:
You can also try entering #*#*4636*#*# on your dial pad. This will bring you to a set of menus.

Under phone information scroll down until you see a drop down menu. It should show 'wcdma preferred' try changing this to 'gsm auto prl'.

It works for me
[HD2 Android NAND Development] Marchino73:
For months I use this rom with no problems. Now my camera does not work. I have installed MIUI cam whit the same result: it starts, but does not work. How do I install the original cam? thanks
[HD2 Android NAND Development] corrsea:
Try just reflashing the ROM over your current setup.
[HD2 Android NAND Development] corrsea:
Dorimanx Ultimate 4.0

For those who want to try.

See kernel thread for changes.
[HD2 Android NAND Development] afr33s:
Several people are saying data not working for this kernel! But this is discussion for the kernel thread! ;)
[HD2 Android NAND Development] sblar:
What is the difference in the two methods?
[HD2 Android NAND Development] degrecelsius:
Yes, y have the same symptoms with NexusHD2-Gingerbread_V2.6_NAND__Android-2.3.3 and Free Mobile.

I just installed version NexusHD2-Gingerbread_V3.2a_NAND_(Android-2.3.7)

and wait to see if it's better.
[HD2 Android NAND Development] Yank555:
Hi,

I'm on Dorimanx's 4.0 kernel...

An MAGLDR, no data either :(

--> Back to good old 3.2 ...

JP.
[HD2 Android NAND Development] Macelangelo77:
Should be solved in 4.1. Can anyone post a flashable zip, so I can test it? Unfortunately I don't know how to repack it in my Mac and I don't have access to a pc...

Thanks in advance.

Sincerely,

Mac
[HD2 Android NAND Development] corrsea:
Supposedly on the gsm auto prl setting the phone does not constantly try to switch between 2g/3g in areas of poor reception thus causing battery drain. I came across the suggestion in another thread and it seems to work for me.

I doubt if it has any effect if you have good coverage.
[HD2 Android NAND Development] corrsea:
@Machelangelo77

Heres Dorimanx 4.1.

I've not tried it yet but posts on the thread indicate the data problem has gone.

I've just flashed fikret 2.0 so will probably leave that on for a day to see how it goes. I also really want to try Tytung's r1 kernel to see what its like so I guess it will be a couple of days before i get to this.

Too many kernels - not enough time :-)

I've just had a thought. Perhaps someone with better technical knowledge could comment. If we created a flashable zip containing just the initrd.gz for this ROM would it then simply be a matter of downloading and flashing a kernel, flash the initrd then reboot. Everything could then be done just from the phone without having to use a pc. Please don't flame me if this is a stupid idea :-).
[HD2 Android NAND Development] Yank555:
Hi,

I'm on 4.1, works like a charm ;-)

And a flashable initd.gz would work just fine ! Good idea ! I'll make one and post it here.

JP.
[HD2 Android NAND Development] namelessrabbit:
Great rom, very smooth, so far no bugs found, in one word: perfect!

If there wasn't this tiny little thing which actually irritates me quite heavily....

It seems like there is no application out there that is able to achieve the maximum brightness of the HD2's LED flash like the WinMo Flashlight did. Some people mentioned the culprit could be the kernel used. Is there a way to avoid getting a new kernel AND make the LEDs go full brightness?
[HD2 Android NAND Development] Yank555:
Hi,

Here it is, the NexusHD2 GB v3.2a initrd.gz reflasher, so you can just flash Dorimanx's kernel (and probably others, too) and just reflash Tytung's initrd.gz afterwards.

I have tested this on a fresh install of NexusHD2 GB v3.2a and Dorimanx's kernel 4.1 on a MAGLDR HD2, it worked just fine.

I can't test cLK at all, so if anyone is willing to take the dive, let us know if it works, it is way more complicated than with MAGLDR to replace the initrd.gz file, so the risk is real ! At worst, reflashing the ROM should bring you back up & running, though.

Be careful, use this on your own risk !! Do a NANDROID Backup before you give this a shot !

JP.
[HD2 Android NAND Development] corrsea:
I'll give it a go with a Clk kernel and let you know. I'm guessing it should be ok as I believe that it is simply accomplishing the same thing as running the commands in Clk.

Will get back in a minute.

Ok everything went fine with fikret clk r2- disk image unmounted, creates new image and remounts it. Boots up ok.
[HD2 Android NAND Development] bogdatov:
if I'm on tytung r14 kernel, can I install dorimanx 4.1 and then install this init.gz from attachments ?
[HD2 Android NAND Development] corrsea:
Yes it should instal no problem but it would be quicker to use the already modded 4.1 I uploaded a few posts ago. :-)
[HD2 Android NAND Development] corrsea:
I've been testing the new fikret kernel v2 on the advice of another member.

I can report that it works very well -fast and smooth, especially with the hyper governor the Dev provides.

It does not like set CPU or battery monitor widget but you can reset the governor with ROM toolbox or other apps. This is a known bug.

It didn't recognise my sd card at first but once I reinserted it I was able to remount it.

Battery life is at least as good as r14 or dorimanx.

Anybody who wants to test can find it here.

http://xdaforums.com/showthread.php?t=1408237

Just flash in recovery (it will appear to stall but it is just automatically clearing the dalvik cache). Then flash the initrd with yanks tool before rebooting.
[HD2 Android NAND Development] bogdatov:
Thanks. Can somebody give me an idea why Dorimanx kernel v4.1 is better than tytung v14 ? For end-user like me. Is it worth to upgrade ? Better battery, faster ROM, etc ?
[HD2 Android NAND Development] Macelangelo77:
It's incredibly fast, everything feels more fluid. It has the possibility (with SetCPU) to lower min value for CPU to 96Mhz (for example in screen off profile) which makes your phone lose less battery power during screen off. For example: with r14 my drain would be at 3-7mA (which was great). With Dorimanx 4.1 my drain is 2-5mA. This may seem a small difference, but if your phone is idle a lot, this will extend the time your battery will last. Furthermore, Dorimanx keeps his kernel updated at all time, with tweaking and tuning, so it's (one of) the best kernels around for our HD2.

If you want to try, just make a Nandroid Backup, clear cache partition/dalvik cache and flash the kernel and the initrd.gz (see above for instructions). First boot will take somewhat longer, because your phone will rebuild the dalvik cache (which you just wiped). Let the phone settle for a few minutes and enjoy. If you don't like it, just revert to your nandroid backup, to restore your phone as it was before flashing.

Sincerely,

Mac
[HD2 Android NAND Development] Yank555:
Glad to hear it works, since I had quite a few things to understand, some to research, as it's easier to create an image with a new kernel and a new initrd.gz. Here I had to extract the current kernel and build an image with the current kernel & new initrd.gz, a bit tricky to do it just theoretically and hope it's all correct ;-)

Thanx for testing !

JP.
[HD2 Android NAND Development] ZghiBy:
is there a problem if i use 200MB system and 10MB cache? i came from NexusHD2-ICS-4.0.3-CM9 V1.2 and ai forget u resize
[HD2 Android NAND Development] corrsea:
No you will have no issues. I use 200/5 for the same reason. It makes it easier to switch between roms that require different size partitions. You lose some memory in nand to system. For me that's not an issue as 1 have a tmous so even with 150 or so apps I've still got over 100mb free. should not be an issue either for euro users with an apps2sd script.

It also means that you are theoretically less likely to be effected by bad blocks (if you have any)
[HD2 Android NAND Development] bogdatov:
Mac,

Can you, please, share your setup for SetCPU ? I'm in constant search for saving battery and yes, every mA counts !
[HD2 Android NAND Development] Marchino73:
I have the same result.....it's work fine with camera 360 prog only.
[HD2 Android NAND Development] Macelangelo77:
Still playing around, but for now:

General settings:

96-998 Mhz, governor Ondemand

Screen off profile

96-245 Mhz, governor Conservative

I use Tasker to disable WiFi whenever I leave home (no polling, network location based)

My phone is not really stable when I overclock CPU above 998 Mhz, currently trying to setup a profile with 1190 Mhz while temp is below 42 C, otherwise fall back to 998 to cool down.

Sincerely,

Mac

---------- Post added at 11:05 AM ---------- Previous post was at 11:01 AM ----------

Can anyone tell me whether there's an easy way to disable/remove the option to reboot in the power menu (long press end key). I want to prevent corruption while using a2sdx by accidently rebooting instead of shutting down. Mostly the wife forgets it... ;-)

I suspect shutting down properly unmounts all mounted drives, and rebooting does not, with the possibility of corruption. I saw JP mentioning it before, so I assume he's right, allthough I haven't found a source yet.

Thanks in advance,

Sincerely,

Mac
[HD2 Android NAND Development] KrewsialNL:
Doesnt the 96mA standby value cause wake up lag? I noticed this when I unlocked the screen,and thing didnt go very smooth. Could be just my setup, thats why I am asking :)
[HD2 Android NAND Development] Macelangelo77:
Hi KrewsialNL,

[off-topic]Still confused about the dutch flag and the location beneath your avatar, but that could just be me...[/off-topic]

I don't have lag with 96-245 Mhz screen off profile, maybe because I use conservative governor instead of powersave governor? Off course it is somewhat slower, compared to without a screen off profile, but there's no noticeable lag. It's still a lot faster, compared to the unlock delay we experienced a year (or so) ago.

For the record: I'm not a SetCPU expert, just a noob who's playing around to get the lowest drain possible ;-)

Sincerely,

Mac
[HD2 Android NAND Development] Yank555:
Hi,

Only issue I have with 96MHz is my car's handsfree kit giving an error message "Dial Up Failed." before the call goes through all the same, this doesn't happen when I use 128MHz as min. frq.

So I stay at 128MHz.

But other than that, 96MHz worked just fine for me !! So if you don't have an issue like I do, I'd stick to 96MHz.

JP.

-------------- Edit :

Was on conservative screen off governor when I had the bluetooth calling problem. Will test 96MHz but with smartassV2 as governor in screen off... see how that works out ;)
[HD2 Android NAND Development] KrewsialNL:
Dutch flag because I am Dutch, but I live in Bucharest, Romania. I don't really see the weirdness ;-)

Thanks for the explenation above!
[HD2 Android NAND Development] schlox:
Is there a way to install Turkish Dictionary support to this ROM?
[HD2 Android NAND Development] kyrunter3:
What changes do i have to make to boot the SD version of this rom via MAGLDR ? (android on nand)

I've searched the thread and found similar posts but has anyone yet successfully booted it ?

Thank you in advance
[HD2 Android NAND Development] KrewsialNL:
Start from scratch? Install Magldr and go from there? There are stickies available to show you how. (Sorry, im mobile...otherwise i would have looked them up for you)
[HD2 Android NAND Development] Macelangelo77:
JP,

Just to let you know, the initrd.gz reflasher works like a charm, and it is of great use to me. Thanks for the initiative.

Maybe Tytung can add it to the OP?

Sincerely,

Mac
[HD2 Android NAND Development] Yank555:
Glad to hear that ;)
[HD2 Android NAND Development] Macelangelo77:
For the second time in 2 weeks I've had the "Inconsistent System UID's" error, followed by Android advising me to wipe my phone. This morning I flashed two kernels, cleared cache partition, wiped dalvik cache everytime as usual.

Not sure whether it's related but for some reason, after a couple of hours, my phone got in a SOD, only hardware keys would light up. I rebooted and got the error. I've searched and noticed in several forum this could be related to fresh installed apps, but this doesn't apply to me (didn't install any new apps, only two kernels).

I tried fixing permissions from CWM, but that didn't work out. I restored my nandroid backup and all was fine. No issues in the past 8 hours.

Where causes this error? Can I do anything to prevent it? Is it related to a2sdx? Or..?

Probably not related to NexusHD2 GB build, but I don't know where to post elsewhere. If it should be in Q&A, let me know, I'll have a mod move it.

Sincerely,

Mac
[HD2 Android NAND Development] Yank555:
Oops :eek: Never had that...

JP.
[HD2 Android NAND Development] corrsea:
I think you did the right thing using your backup.

I've no idea about the cause of the problem though.
[HD2 Android NAND Development] bogdatov:
Preparing SD card ...

With this ROM after every reboot or turning on/off USB storage mode I have this message "Preparing SD card ... Checking for errors". It stays on for a long time 10-15 minutes and during that time SD card is not available. After messsage goes away I can use SD card as usual.

I never had this problem with ANY of Froyo ROMs or ANY GB Sense-based ROMS, only with this AOSP.

Is that normal ? My microSD is fairly new 16GB SanDisk. I'm on T-Mobile (US) HD2 with no EXT3/4 partitions. No applications moved to SD card
[HD2 Android NAND Development] kyrunter3:
@bogdatov

That is normal my friend ;) nothing to worry about ;)
[HD2 Android NAND Development] general1977:
I wouldn't call this normal. I get the message "Preparing SD card" after every reboot but not after unconneting USB-Mass-Storage. Also I never got the message "checking for errors". Preparing the SD card takes about 10 to 15 seconds on my HD2 with a Sandisk 16GB class 2 card with FAT32, EXT3 and swap partition.

Regards

Achim
[HD2 Android NAND Development] corrsea:
Just in case anyone has not discovered it yet there is now a thread with loads of themed touch recoveries.

http://xdaforums.com/showthread.php?t=1477171
[HD2 Android NAND Development] Macelangelo77:
That is certainly not normal. Even with a2sdx (or any other a2sd/d2sd I tried) it takes max 10 seconds, with a large amount of apps or data installed on sd-ext.

You don't mention what speed your card is, but I've tried Class 2, 4, 6 and 10 cards and have settled for class 6.

I would advice you to backup the data on your card, format it with SD Formatter (https://www.sdcard.org/downloads/formatter_3/), with option Full, Overwrite (or Erase but my Card doesn't support it) and Format Size Adjustment on. After the process completes, restore your data back to the card.

I suspect there's something with your SD-card, as it seems Android has serious trouble mounting your card and/or accessing your data.

Sincerely,

Mac