yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] mbunal:
Ynt: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

But there was lots of error fixed. I think linux fsck more powerfull or efective then android partition check. Just my opinion and my experience.

NexusHD2 cihazımdan Tapatalk 2 ile gönderildi
[HD2 Android NAND Development] NYLimited:
Re: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

About 100 mb....

Primarily Google Apps including Google Now.

And the minimum system requirements are overly conservative.

---

Don’t take life too seriously, nobody gets out alive anyhow.
[HD2 Android NAND Development] scottspa74:
Re: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

You guys really do have the greatest device ever. The king of devices. Leo is a well suited codename. It always blows me away all the OSs you guys can run. Often running current versions of android that actual native android devices can't even get running yet.

Congrats to you all. Hail Leo.

From my Evo LTE, yup.
[HD2 Android NAND Development] aberean:
Hopefully last question for a while, thank you NYLimited for your help. what is the best way to go from nativesd to data-on-ext. do i need to wipe device or is there a better/quicker method?
[HD2 Android NAND Development] NYLimited:
Re: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

I hate to say it but I don’t know of any simple way to migrate.

NativeSD is located in entirety within a directory on the sd-ext partition. None of it resides in NAND to my understanding.

You will have to partition and, therefore wipe NAND memory and create a brand new installation.

If you have Titanium Backup create a backup first.

You do NOT have to erase the NativeSD directory. That gives you a nice option to return to a working installation should a problem occurs.

If you plan on using DataOnExt method I would suggest you completely ignore some of the partition size recommendations. Specifications, make the recovery partition at least 7 mb (I use 10) and the system partition 400.

The reasoning is simple. First, since data partition is going to the sd card none of the NAND memory normally assigned to data is used. You might as well make use of it. Making recovery 10 MB will afford you the opportunity to try newer recovery apps which have need more space. Making system 400 MB (hopefully) eliminates likely bad block issues.

If partitioning and installing recovery software is not clear you need more homework. :)

Once you finish installing the ROM to NAND test it and make sure it runs ok. Once happy with it start Titanium Backup (don't forget, you have to reinstall it) and selectively restore your apps and data. When done, most things should be running cleanly.

---

Don’t take life too seriously, nobody gets out alive anyhow.
[HD2 Android NAND Development] marco.palumbi:
Although "e2fsck -p" is run at every boot on the ext4 partition, there are some error that can't be fixed this way.

in such events, you must run e2fsck interactively. You can do it booting in recovery and connecting with adb .

Using a linux box is another good solution.

-
[HD2 Android NAND Development] NYLimited:
Good information, thanks! One quick question.. In such a case as you described would there be a mention of this problem in the fsck log file? I auto email it to myself on every boot so I don't forget to look at it..

---

I’m as confused as a baby in a topless bar...
[HD2 Android NAND Development] Osprey00:
FYI to anyone that it may interest... I was a happy user of this ROM, but wanted newer CM10 sources, so I went looking for an alternative. Zejsters' JellyTime ROM, it turns out, is almost exactly like this ROM (CM10 + Gapps, no customization or tweaks), just more up to date. One thing that it seems to fix, at least for me, is the low notification noise. I was also having a problem where Torch wouldn't always turn on or off with NexusHD2 that seems to be fixed in JellyTime. Other than those things, I notice no differences. It's just as smooth. So, I recommend it if you're pondering moving on from NexusHD2 to a ROM that's getting updates still.

Oh, one other difference is that, with JellyTime, it takes a few seconds for the backlight to turn off when locking the phone, but that turned out to be easily fixed by going into Settings->Developer Options and setting Window Animation Scale to 0.5.
[HD2 Android NAND Development] marco.palumbi:
Yes, it is. The statement will report something like: you must run e2fsck interctively.. (if i remenber...)
[HD2 Android NAND Development] mdolphins99:
Re: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

You soooo right dude this ROM is identical to tytungs, but with all of the small issues corrected.... Thanks!!!
[HD2 Android NAND Development] euoaga:
I have installed ROM in mode NATIVE and after fix audio, ROM Ok but fix audio not work.

How i do installed a fix ? After wipe?

Thanks...... the ROM is fantastic
[HD2 Android NAND Development] Geeba:
Managed to pick up another HD2 after my last one the screen gave up :D

How is this ROM compared to tytung's ICS? I'm running that at the moment.... is this still being developed?
[HD2 Android NAND Development] arthurcswang:
Dear Tytung,

Thank you for your great ROM !

I'm HD2 user (I use Magic before), Now I'm trying to understand Android CTS recently.

I tried to run 3 part of test case, here it is the results :)

Test Summary by Package

Test Package	Passed	Failed	Total Tests

android.core.vm-tests-tf	3098	0	0	0	3098

android.media	269	18	0	0	287

android.mediastress	87	3	0	0	90

Test Failures (21)

For study debugging purpose, I think I need source code to go further.

Can you provide source code info to me?

Regards,
[HD2 Android NAND Development] mare.djurdjev:
Anyone knows if Tytung is coming back? This ROM is amazing,fastest ROM I've ever used. Ty Tytung :))
[HD2 Android NAND Development] Robbie P:
Can anyone confirm whether installing MusicFX, cures the no sound after call bug?

( http://xdaforums.com/showpost.php?p=38371546&postcount=64 )
[HD2 Android NAND Development] nestleomega:
Anyone of u having problem using data?

every morning when I woke up, i will get disconnected from my data, the bars is grey with H sign.

turning off and on data settings will not work, only a soft reboot will remedy this.

Seems like a problem if i let my phone idle for some time
[HD2 Android NAND Development] sathara:
Re: [Dec. 9, 2012][ROM][720p] NexusHD2-JellyBean-4.1.2-CM10 V1.3a [NativeSD]

Can you tell me how to do it
[HD2 Android NAND Development] trex3300:
You are not alone with this problem. I have two HD2 and one of them is having this issue, the other is working perfectly.
[HD2 Android NAND Development] mare.djurdjev:
How to reduce battery drain,its really high,only 2 hours since last charging and it has 66% battery? please help
[HD2 Android NAND Development] NYLimited:
Have you looked through this (and other) thread?

There has been a lot of suggestions to find that issue..
[HD2 Android NAND Development] mare.djurdjev:
I never had issues with battery on android before,dont know where to watch. Can you please help me?
[HD2 Android NAND Development] NYLimited:
There is no simple or single answer for identifying battery drain issues.

There are many, many reasons for it, not the least of which might be user settings, apps (such as Google apps, talk, gmail, facebook, twitter, etc.) and hardware.

Some of the typical reasons for battery drain include:

Your screen!

Applications, especially those that keep running in the background)

Apps that require constant data connections to stay updated (e.g. facebook, twitter etc.)

Sync-ing data too frequently

Location services running in background

You need to figure out what is using the battery. There are several apps that can help. You can start by looking at the system's battery option which will give you a rough idea of what has been using the battery. Not extremely accurate but a starting point.

Is something keeping your device awake? That can be a battery killer!

Lastly, you can freeze all apps you installed (not those that part of the ROM) and see if the drain goes away. If it does, start to defrost them one by one and note where the drain returns. Hint - the last app defrosted before the drain returned is a problem! :)

Unfortunately, these are but starting points since the possible reasons for battery drain are so many...
[HD2 Android NAND Development] mare.djurdjev:
I see that my screen is using 75% of battery,but i put automatic brightness,dunno how to change that? the rest of the apps are using 2,3%,nothing that big. :)
[HD2 Android NAND Development] NYLimited:
I trust you realize that the percentages are not of battery capacity but of battery usage, yes? In other words, your battery has 100% capacity, of which let's say 40% was used up when you looked. The 75% means 75% of the 40% used up...

For better screen brightness / battery usage take a look at

Lux Auto Brigtness

- a cool app! There are other apps which do similar functions but this one happens to be the one I am using.

Anyway, if you are showing 75% screen that means you were using the device quite a bit at the time so the result is not very useful. Charge it to 100% and unplug it just before you go to sleep. Once you unplug it don't use it at all (do not turn the screen on) for several hours. If you let it 'sleep' for some 7 or 8 hours that display will be a lot more meaningful.

If the above doesn't give you any directions you might want to try

BetterBatteryStats

or a similar app to figure out what is using the battery.

Your SD card could also be causing a drain. As

mbunal

pointed out you might try to run FSCK for your card. If you have an ext partition run e2fsck. Also, check the fat32 partition. You may find errors that are causing issues.

You may also consider a complete nandroid backup, a factory reset and format all partitions and restore everything. Don't forget to copy, format and restore the fat32 partition if you do this. This is a lot of work with absolutely no guarantee of results but it may help a little.
[HD2 Android NAND Development] abdallahlabeeb:
Can u please explain in details how to do it ???? I mean fsck for my sdcard.
[HD2 Android NAND Development] NYLimited:
If you want to check your ext partition you need to to run e2fsck interactively and your ext partition must not be mounted. You can do it booting to recovery and connecting with adb or, easier, use a Linux box. If this is not clear you probably should not attempt it until you read a lot more, sorry.

You can check your FAT32 partition on your PC and a card reader or in Android Terminal with the following command:

su
fsck_msdos /dev/block/yourdevice
[HD2 Android NAND Development] abdallahlabeeb:
You are great as usual. Do you have any useful links about fsck and e2 fsck ????? Thanks in advance.
[HD2 Android NAND Development] jonnyjett:
Help

After installing I get:

AROMA INSTALLER Finished...

E:Error in /sdcard/JellyBean ROM/NexusHD@-JellyBean-CM10_V1.3a.zip

(Status 0)

Installation aborted

I've tried rebooting but it gets stuck in a rebootloop. What should I try next?
[HD2 Android NAND Development] NYLimited:
I don't know about the 'great' part but I know you are asking for trouble when you ask about links! :D

Let's see.. I can probably just

Google that

quickly or point to a couple of somewhat interesting reads

here

or

here

or perhaps

here

... Now, aren't you sorry you asked? :laugh:

​

First guess would be that you have a bad or damaged ROM Zip file.

Have you checked the MD5 of the file?

Try downloading it again and check the file on the PC before copying it to the SD Card.

If it is OK on the PC and the problem persists check your card or try another card...
[HD2 Android NAND Development] Ethan_93:
Solved with fresh install.
[HD2 Android NAND Development] mrpierrec:
I installed this ROM on my EU HD2 using option 2 and the installation went OK.

I had problem with SU but I solved it installing apk mentionned in previous messages.

The ROM is realy nice, really smoth and stable.

However, I faced FC when configuring Elixir 2 widgets. Each time I press menus in this application, there is a FC.This is bad for me as I use Elixir widgets on many screens..

Anyone using Elixir 2 and having the same problem..and a solution for the problem ?

Thanks tytung for your great job for this ROM
[HD2 Android NAND Development] wega007:
Text-to-Speech not working

Text-to-Speech isn't working. Tried Pico TTS and Google Text-in-Speech. Any idea how to fix this?
[HD2 Android NAND Development] Proficamper:
Hi,

is the following the right way to flash with clean install from my recent NEXUSHD2 Rom v.2.7 to JB V1.0:

1 Backup the phone

2 Repartition with HD2 Toolkit MAGLDR 320 MB / 7 MB Cache (this also will format the phone, right? i heard that i should avoid task29)

3 Repartition the SD Card with 14 GB FAT32 / 2 GB EXT4 MiniTool Partition Wizard

4 Flash the ROM with CWM install from SD card with option 2

5 Flash the missing MAGLDR kernel zip

6 Flash superuser v 3.2

7 Reboot and set up the phone

Is it all or did i miss anything or is this the wrong way?

Mhh, i'm wondering how i'm getting cwm on the phone...

Long time ago since i completely set up the phone...sorry..

Thanks!
[HD2 Android NAND Development] chshrm:
thanks a lot for your information, I'll give a try and hope your new version of miui v4.1 coming soon.
[HD2 Android NAND Development] NightyNight:
Is anyone else having frame rate issues and general studdering and performance drops? My homescreen scrolling seems to very sluggish, while the app drawer is smoother than the ICS Rom. Any advice?
[HD2 Android NAND Development] chshrm:
i met root problem when i port miui v4.1 on this base, what my solution is repacking the initrd.gz under root environment on ubuntu. and everthing is nomal now.
[HD2 Android NAND Development] ad2003:
Sorry for asking but could someone please just post the softkeymod native? Thanks in advance. Ad
[HD2 Android NAND Development] french-anonymous:
Same problem. The homscreen is very laggy in HWA roms (even with other launchers like nova, apex, go launcher ex, zeam...) but the rest actually looks well hardware accelerated.
[HD2 Android NAND Development] NightyNight:
NexusHD2 ICS Rom homescreen works fine, I dont know why this is so laggy.
[HD2 Android NAND Development] lenstan57:
which parition?

Question, I haven't used this Rom in a while and see there have been a lot of changes.

I'm a TMOUS user and was looking to change my current Rom.

Want to try the Download JB 4.1.1 CM10

Do I use this Partition size ??

AROMA Installer for three types of installations:

NAND

system@NAND, data@NAND, boot@NAND

For TMoUS HD2 (LEO 1024)

Please visit my ICS NAND thread for the installation steps

Minimal partition size table when installing the rom to NAND (Options 1 and 2):

Code:

misc ya 1M

recovery rrecov|ro|nospr 7M recovery_leo.img

boot yboot|ro 5M

system ya 320M

cache ya 2M

userdata ya|asize|hr allsize

OR the 170 system partition stated in the ICS NAND thread??

Do I need the Magldr Fix for V1.0??
[HD2 Android NAND Development] utrecht56:
+1, also have this problem using NativeSD. :(

Apart from that, still very happy with this very stable ROM.
[HD2 Android NAND Development] smokin901:
Open voice search ask for what time is it then hit volume up as it tries to display result you may have to try couple of time
[HD2 Android NAND Development] abumaha:
not work bro flashed zip still no root what sproblem
[HD2 Android NAND Development] rehan@exchange.bgu.ac.il:
Upgrade native sd on hd2 wp7

I have a JB (4.1.1) Native SD installed on my HD2 together with WP7. I would like to upgrade the Native SD to a newer rom version - is it possible or do I have to go thru the process as is If install a new Rom from the beginig ?
[HD2 Android NAND Development] chshrm:
if you flash on EXT4 partition of SDcard, please try this initrd.gz below, i solved my root problem with this one, i only give a root permission to this one, hope it will solve your problem. just replace the initrd.gz in sdboot folder of the ROM before flashing.

View attachment initrd.gz only for flashing on EXT4 of sd card.
[HD2 Android NAND Development] wis1152:
No don't do that I will have it:D:D:D
[HD2 Android NAND Development] AthenaLod:
Thank you for the great rom as always. was wondering about the "stay awake" dev option. I can't see to find it! Anybody with where it went or how to keep the screen awake while charging?
[HD2 Android NAND Development] molann:
it should be under "Developer" section in options
[HD2 Android NAND Development] materoprodutions:
hello i'm switching from nexus ICS rom. I would like to keep CLK as I've been using it a long time. what is the correct project to flash?

I think is task29, repartition and install CLK then flash. Now I have Tmobile 1024 HD2 but I would like to have extra space for apps using dat2ex4 to sd but keeping everything else on NAND. What is the best way to do this?

I have a 16gb class4 SD card and I would like to have a 4GB ext4 partition just for apps on it but I'm a little confused about flashing for it. can you help me? Thank you
[HD2 Android NAND Development] jonnyjett:
First guess would be that you have a bad or damaged ROM Zip file.

Have you checked the MD5 of the file?

Try downloading it again and check the file on the PC before copying it to the SD Card.

If it is OK on the PC and the problem persists check your card or try another card...

I actually checked the MD5 of the ROM zip file on the SD Card itself and it checks out ok. Is it an issue that the zip file isn't at the root of the SD card and in a folder?

---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------

I don't know how that can be an issue because when I place the zip in the root folder and am in CWM and select

-choose zip from sdcard

I only get a list of folders and I can't see a zip listed. I have to open a folder to see a zip file.

---------- Post added at 04:02 PM ---------- Previous post was at 03:54 PM ----------

Also, I'm copying the zip file using a USB memory card reader, NOT by mounting the SD card and transferring the zip while the card is still in the phone. I'm assuming that doesn't make a difference.

---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------

Could this be a partition problem? I wouldn't think so since the Aroma goes through it's entire installation process.
[HD2 Android NAND Development] NYLimited:
Interesting. I can see this will be a little more challenging than simply a bad zip file. :)

A number of things come to mind, in no particular order so let's give them a try..

Taking another look at what you wrote I notice that Aroma was finished. The Aroma installation script does not contain the string "E:Error" anywhere. Nor does the ROM updater script. And, to make things more confusing I am noticing a "Status 0" which suggests no error from someplace. Yet, the installation is aborted by something. Trying to figure things the next guess would be the installing program, ClockworkMod Recovery if your signature is correct:

Although I cannot be certain I might take a guess that CWM Recovery v3.x *may* be reporting some problem. Having said that, I would definitely try v5 or v6 with some caveats that follow below.

Read slowly now! ;)

You are coming from a Gingerbread ROM according to your signature. So..

Did you change your partitions?

If no, skip that rest of the notes - that is your problem.

If yes, how and to what? The correct answer here depends on the installation type you are trying to do: NAND or DataOnEXT. Also, minimal or full or... ?

Your device probably has some bad blocks. The system partition guidelines are in post 1 are very conservative. Whether installing minimal or maximum apps you should make the partition larger than recommended.

If installing all to NAND you need to be somewhat conservative since you need space for the data partition. I would start going up from the 170 minimum - 190 or more.

If installing DataOnEXT you have no need for a data partition in NAND - I would make system 400 MB

I would definitely upgrade to v6 or at least v5 of ClockworkMod Recovery. You cannot do this without changing partition sizes since your v3 partition is too small. You need to repartition the entire device anyway to accomplish this.

If you are planning on a DataOnEXT installation download and use this DAF.EXE (

DAFEXE_399.zip - 5.17 MB

) which will re-partition you larger and also install a newer Recovery app for you.

Until we eliminate these possible issues my suspects for now are your recovery program and/or partition sizes.
[HD2 Android NAND Development] jonnyjett:
It's the partitions.

I searched for hours for a step by step instruction on how to alter the partitions and only learned how to download the text file (from a random place on the net) and alter the values in Notepad. I never figured out what to do with the file after being altered. So the partitions were never changed. I downloaded the toolkit but I don't know how to use it. Again, I couldn't find instructions how to use it.
[HD2 Android NAND Development] NYLimited:
Okay, we made good progress. I know it may not seem like that just yet but we did. :good:

How big and what speed is your SD Card? You need to decide if you are using straight NAND or DataOnEXT installation method. Personally, I prefer DataOnEXT (you should have a good Class 4 or 6 card for this) but others like NAND as well. So, this is up to you. With install method 2 (DataOnEXT) you are using two devices (NAND memory and your card) at the same time.

Either way, first make sure you have a good NANDROID backup. Since it is saved on your SD Card I suggest you make a copy of the crad's FAT32 partition on to a PC, just in case.

Now you are ready to clean house, so to speak. For the sake of this text we'll assume you will use DataOnEXT, install option 2. If you elect to use option 1 instead you simply modify the flash.cfg file (more on that later).

Make sure that you have an ext4 partition on your card. Should be 1-3 GB depending on the size of your card. Note that this step is not required if you decide on install option 1 (NAND only). If you do not have an ext partition

go to this thread

and read post 2 which has a lot of info about formatting and partitioning. Don't forget that this will wipe the content of your card! Post 2 of that thread also has good info about backing up, if interested.

If you haven't yet, download this zip file (

DAFEXE_399.zip - 5.17 MB

) and unzip it to a folder on your PC.If you will use install option 2 go to step 3 now. For install option 1 edit the FLASH.CFG file and change the line which has "system on it from

system ya 399M

to something like

system ya 200M

for a minimal install (I really recommend at least 220 MB!) or to 285 for a full install (I recommend at least 300 MB). If you intend to try a full install and you have many bad blocks you may need to go beyond the 300 MB size which will pretty much push you into install option 2 anyway.

Reboot the HD2 (or power up) while holding the volume down key to the HD2 into the multi-color bootloader. Connect the usb cable and run daf.exe on your PC. Follow the prompts on the PC till done. When the process is completed you should have a clean, re-partitioned device with a much newer ClockworkMod Recovery on it.

You are now ready to flash your ROM via Magldr option 8 and ClockworkMod Recovery, hopefully without any errors!

Have fun!
[HD2 Android NAND Development] jonnyjett:
I've replied below inline in blue:

OK, let me try this all out now and I'll let you know what happens as soon as I get some results.

---------- Post added at 11:37 PM ---------- Previous post was at 10:44 PM ----------

I'm getting this error from DAF:

An error has occurred

Read below for more information

Error Description: USB init failed

Info: .\RSPL\RSPL.cpp (736)

This is after rebooting into HSPL on the phone and it going into USB mode.

---------- Post added at 11:49 PM ---------- Previous post was at 11:37 PM ----------

OK, I figured out that I had to boot into MAGDLR and then go into USB Flasher mode. I ran DAF and it worked. Now I'm going to attempt the ROM upgrade.