yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Burag:
Thank you.

I was aware of this bad block since looong time - I have used the same partition layout with GB roms and even mostly the same apps, so there shouldn't be any difference in size occupied by them, but I wasn't experiencing panics with other ROMs...

Anyway, I will try to track down this bad block and skip it as it was described here when I will have more time.
[HD2 Android NAND Development] MarsHD2:
Wow finally a ROM that works perfectly on my phone, I feel like I just bought a new phone! Thank you and great job :)
[HD2 Android NAND Development] MarkAtHome:
I engaged you in conversation because you appeared to be open to it. My apologies if I am swamping you and not being clear enough. Will work on that in the future. Sorry.

FWIW, as articulate as you are, I would not have known that English was not native to you.

Would not reading Chainfire's logcat give a clue by looking at the last lines before the crash? Note that I do not know the answer. ;)

Prior to ICS, I was always using Interactive, and when I found Tytung defaulting to Smartass2, I decided to let it be for the time being. Haven't had anything eventful happen, but I don't use the phone under extreme loads.

Aside from no more freezes (which is reason enough), have you noticed any other differences between the two governors?
[HD2 Android NAND Development] Luggruff:
Sorry, but I'm having a really hard time getting this:

From searching the thread, I find a lot of posts regarding ext4 partitions (as I have very little internal memory on my european HD2).

So I'm gonna put it simple and hope for a simple answer:

I'm currently using the NexusHD2 ROM. I just had to make a ext4 partition and install through .zip in boot.

can it be done as simply, with this rom?
[HD2 Android NAND Development] dogans:
Have been using this ROM since 1.0 and it has only gotten better.

However, I've been having 2 annoying issues that I can work around but haven't seen posted here.

* Whenever I lock my device when the keyboard is up and showing and then unlock my phone a moment later, the keyboard gets stuck and I can't do anything on the keyboard.

* Notification signal and vibrate stops working after a while. And sometimes rebooting doesn't help.

Still loving this ROM. Thanks for your hard work Tytung!
[HD2 Android NAND Development] the_scotsman:
Thread cleaned - please stop with the crap.
[HD2 Android NAND Development] evilbarcode:
Please refer to the FAQ in my signature for a2sd scrips and partitioning. The is also a separate thread here just for these discussions.

Cheers,

Evil.
[HD2 Android NAND Development] famewolf:
You need to ask in the a2sd thread which is listed in the op's first post. Their wiki also has some instructions.
[HD2 Android NAND Development] walts:
How to deal with bad blocks

I'm posting this here instead of one of the "bad blocks" threads since a lot of what they are discussing in those threads appears to relate to other ROMs like CM7, not ICS. My troubles started with ICS, although I admit that it could be coincidental, just caused by a lot of flashing.

I've just spent the last two hours reading several threads about bad blocks. Most of the discussions relate to fancy ways to move partitions around to "avoid" the bad blocks.

MTTY info 8 tells me that I have about 20 bad blocks, scattered all over memory, so the repartitioning approach won't work for me.

I still haven't found an answer to my basic question - is there any way - automatic or otherwise - to mark or remap bad blocks so that the system won't use them?

Here are some of the theories I've found:

- YAFFS does this automatically.

- Task29 does this when you run it.

- run Windows, since it deals with bad blocks correctly.

- the linux kernel deals with bad blocks automatically

- flashing a new ROM will mask out the bad blocks

About the only thing I know since it's been independently corroborated, is that there is a table of bad blocks that were identified when the memory was manufactured. Is there a way to add to this table?

Tytung, anyone, can you confirm or deny any of the above? I really don't want to run Windows and ICS from SD :(

Frustrated,

Walt
[HD2 Android NAND Development] trex3300:
Bad blocks has little (if any) to do with ICS. If you are running a rom that requires system partition of 150MB or less, you may be lucky enough to avoid bad block symptoms like reboot if your bad blocks are not located in a critical area, however, once you flash rom that requires larger partition, you risk having some of your bad blocks fallen into your system partition and when that happens, you are definitely going to have reboot and other bad block symptoms.

So it all depends on how many bad blocks you have and the size of your rom. Given enough time, our beloved HD2 will die from bad blocks or something else. As far as I know, nobody has been able to find a way to reverse bad blocks or created a program that can isolate bad blocks from been used. All the great minds on XDA including Cotulla are aware of this problem. That is another frontier in android development that is yet to be conquered.

With 20 bad blocks on your HD2, it is a matter of time before you run into reboot and other bad block problems, sorry.
[HD2 Android NAND Development] saap:
Help me, please. I have problem with sound, when I call someone. Very high volume.
[HD2 Android NAND Development] trex3300:
Check Wiki for possible solution.
[HD2 Android NAND Development] famewolf:
I browsed it and that problem does not appear to be covered.
[HD2 Android NAND Development] trex3300:
If the call volume issue is on the caller's side, volume+ app might be able to fix it.
[HD2 Android NAND Development] Chitown021:
Did I just read that Android 5.0, Jelly Bean, is getting ready to be released in the next fe months? Didn't ICS just come out not to long ago?

If/when full hardware acceleration is implemented on this rom it will be perfect for my uses. Even without it it's still gets about 90% of the things I need it to do done.
[HD2 Android NAND Development] trex3300:
I should have known better, you hardly miss anything. When you have some free time, please consider adding the fix to tytung_R14 kernel for the benefit of your loyal Gingerbread fans.

Thanks.
[HD2 Android NAND Development] hattmoward:
First, to explain some things about YAFFS2 --

YAFFS2 originally didn't store anything about the entire filesystem -- filenames, directories, block maps -- in one place. When YAFFS is mounted, it scans through and rebuilds this kind of thing in memory. During the mount-scan, it detects bad blocks and you should see as much in the kernel output. It uses both what the NAND controller says is bad and what it marks as bad in a block's OOB info.

The current release of YAFFS2 stores a snapshot of filesystem data, and will only do the slow mount if the filesystem wasn't unmounted cleanly, so note that you won't see the bad block messages if it isn't doing a mount-scan this time.

Since it knows a block is bad, it happily works around them when writing to the disk. If the NAND controller decides a block is bad during a write, YAFFS marks the block bad too, and the data is still in memory to be written to a good block. You just lose 1 block of available space in the partition, everything else is happy.

Sometimes the NAND controller doesn't report an error until a read, and YAFFS can't do anything about that - a block of data is trash, with no spare copies. I've seen YAFFS2 truncate files at the last good block, or error through the bad block and return to normal once you read past it. I'm not sure which is the intended behavior, but either way files going corrupt will hurt.

In other words, blocks that go bad in system can cause problems, but if you write new data -- restore system from backup, reflash the same rom release, or something completely new -- the only harm in bad blocks is a bit less space in the partition, so you might need to increase that partition to acommodate.

The data partition is ext3, which isn't privy to NAND controller information, but is still able to find and ignore bad blocks. Once it knows of bad blocks, it works around them just fine. The only thing is that it may not detect bad blocks on the fly as well as YAFFS2, but "e2fsck -c" can run an explicit scan and mark new bad blocks. I'm not sure if any android systems use -c in startup scripts anywhere -- I've done so manually, myself.

Anyway, bad blocks are more likely to make the ext3 partition choke, but you can still hedge against them pretty well. If you keep gratuitous backups, and then suspect a block failure is now causing you trouble, restoring from backup will more than likely get the filesystem working around the bad block at the same time it fixes the now-corrupt file.

The only point where bad blocks will really make your phone unusable is when there isn't enough good/free space left for a functional OS, or if a vital block near the start of the NAND device fails, where the system has no workarounds.
[HD2 Android NAND Development] Dr_Grip:
That's simply not true. The HW accel code should be more or less the same on the Desire, the N1 and the HD2. It has nothing at all to do with the radio code.

The problem is that most HD2 kernels are based on the Linux 2.6.32 or 2.6.35 codebase which means that patches like texasice's HW accel can't just be applied but have to be backported because they are made for newer kernel versions (2.6.38 in the N1's case).

The more interesting question thus is which kernel version the miui_au guys use. If they use a 2.6.35 kernel and if they really got full hw accel working, the code should slot right in with any of the ported 2.6.35 kernels for our device. But that's a lot of ifs and shoulds.

That's correct. As I said to warrenb the other day, we should wait until it is more or less stable, then try to backport it into one of the 2.6.35 kernels.
[HD2 Android NAND Development] timekeeper:
Has anyone flashed the rmnet_to_ppp_update.zip (linked in OP) and then resulting in no data connection? It was working with 1.1 or 1.2, then I lost data one evening, and only flashing back to rmnet fixed it. Now, even on 1.3, flashing the zip makes me unable to get a data connection. Does it need to be updated for the new versions?

EDIT: hmm, took a look through the google files for the nexushd2, and found a rmnet_to_ppp_for_magldr.zip which I flashed and got data back.
[HD2 Android NAND Development] walts:
THANK YOU!!!!:):):):)

If the "Thanks" button worked more than once for each post......

This is the first explanation I've read on the subject that makes sense to me.

One question, though. I tried the e2fsck command on /data/ and was told it was a filesystem, not a device, so I ran mount:

# mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 rw,noatime,nodiratime 0 0
[COLOR="RoyalBlue"]/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0[/COLOR]
/dev/block/mtdblock4 /mnt/cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.seventeenbullets.android.island-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#

so it looks like /data/ is also yaffs2.

Summing up what you've said, the various filesystems we use properly take care of bad blocks, but we will still have occasional problems with blocks that become bad since the last reboot. Frequent backups (Thank you, Titanium!) will protect against serious data loss, but we will have to learn to live with the rebooting issue.

When you say that

does this mean that whenever we get a spontaneous reboot (and i"m assuming they are caused by bad blocks detected upon read, as you discussed), we should either reflash the current ROM or restore from a backup?

Walt
[HD2 Android NAND Development] horowae:
Hello, my HD2 hangs at "android" bootlogo and didnt start. Please help. thx
[HD2 Android NAND Development] nonpaq:
About random reboots, don't rule out that they may be caused by a bad SIM card. I changed my TMobile SIM over three weeks ago and have not had a reboot with any ROM since. I don't know if the 3year old SIM was damaged or maybe it has corrupt data on it. If there is a way to "Format" or "Factory Reset" a SIM card, perhaps someone can try that for reboots.
[HD2 Android NAND Development] walts:
Yes, I did that, also about three weeks ago. Replaced a 3+ year old, obsolete design SIM. It did not help, although others have reported that it did. I think it's a good idea in any case, and T-Mobile will do it at no cost, at least in the company-owned stores.

Walt
[HD2 Android NAND Development] famewolf:
So I totally misunderstood Tytung in http://xdaforums.com/showpost.php?p=22411859&postcount=3054

when he said:

The radio code is what prevents us from just being able to compile the new kernels. It's the primary reason everything has to be backported to kernels that DO support the radio.

If I'm mistaken in any of this please explain further.
[HD2 Android NAND Development] Dr_Grip:
It works either way round:

a) you port the radio code to the 2.6.38 or 3.0.0 codebase or

b) you backport all hwa-related changes to 2.6.32/2.6.35

Both ways are possible, as the fact that 2.6.32 and 2.6.35 kernels for the HD2 exist prove.

So if (and I don't know that) Sandvold's Desire kernel is 2.6.35-based the changes should work with warrenb's or fhasovic's kernels with little or no change.

fhasovic is already looking into that.

What I am arguing against is the notion that the radio driver is some kind of magic token that automatically means all kernel driver developments on related devices are worthless for our device.
[HD2 Android NAND Development] famewolf:
As I recall there were additional issues with the 3.x codebase for the hd2.....and something made them choose to backport vs moving the radio code forward. I hope you are right and they get us newer versions of the kernel but I know that the 2.6.35 kernel's I tried on tytung's roms were MUCH more unstable then the 2.6.32 one's to the point he reverted back to 2.6.32.

In any case however these developers do it, I continue to be amazed at the functionality they've given us for our "obsolete" hd2's.
[HD2 Android NAND Development] KevlarTheGreat:
Maybe I really misunderstand the current state of things...

How can someone port the radio code when we don't have the radio code? Do you mean that the wrapper around the windows mobile driver needs to be ported? (I'm assuming that's how we are using the WM driver? ). Isn't there anyone who could write a native driver or modify a similar one?

Is there a separate PPP and RMNET driver? Is either of them native or both are wrapped WM drivers?
[HD2 Android NAND Development] soulz:
Hey guys I'll be reverting back to this ROM from EVOHD within a hour. I couldn't make phone calls on that and I loved it's speed.

Although this rom is more eye friendly but the one thing I'm going to miss is the notification system.

Is there any to get rid of "Included lights.htcleo.so_from_Gpc_GB_ROM.zip to support the blinking amber light when getting a notification. (Credits to gpc)" and move back to the original. a simple editing i can do myself? The reason I ask is, I react better to a light that stays on than blinks and I confuse myself ><

Thanks so much :)!!
[HD2 Android NAND Development] famewolf:
My understanding is they do use a wrapper. The default for windows was ppp but the default for android is rmnet.

---------- Post added at 01:48 AM ---------- Previous post was at 01:47 AM ----------

You might try installing something like "Led Me Know" app and see if it gives that option.
[HD2 Android NAND Development] mosio:
Yesterday, about 4 times I got the notification with triangle icon saying "Sign-in error for********@gmail.com" with information that my password or login is incorrect and asking to sign again into gmail account.

After signing in everything worked fine for about 2 hours and then the same notification appearead.

Cleared cache, dalvik, fixed permissions and I still experience this issue. Anyone got this before ?
[HD2 Android NAND Development] rmetanes:
Please help,

My HD2 keeps rebooting, I run the Rom and clk 2wce each, but am Not sure I gave it enough time to settle b4 I started installing apps as suggested in one of the forums.

If I recall correctly, I partitioned the memory as follows 200/5. Heres what I see when I enter system settings > Storage = total space 205MB

What am I missing.

Applications keep crashing as well.
[HD2 Android NAND Development] legolas93:
Mmmm..i think that your is a partition layout error :D

I think that "Total Space" is not the "System" partition.

Try to repartition with HD2 Toolkit with correct layout!
[HD2 Android NAND Development] Dr_Grip:
One has to keep three things in mind here:

1. The 3.0 kernel is just a renamed 2.6.40 so the changes are not that drastic. Still, forward-porting all modifications (not only for the radio, but many other tweaks for our phone) made to the current .32 kernel gets harder with every new kernel release as the upstream codebase changes evermore.

2. If I recall correctly, the last major problems with the 2.6.32 kernels were fixed with tytung's R14 back in November 2011. The porting efforts for the 2.6.35 kernel started in late September 2011 - so the fact that the 2.5.35 kernel was less stable than the .32 one last time you tried it has nothing to do with kernel releases and their compatibility with the HD2, but with development time.

Right now I am running fhasovic's latest kernel without any issues and according to bluetooth poweruser ph03n!x warrenb's 2.6.55 port is the only kernel (including tytung R14) that's "no sound" bug free in any given case.

3. tytung is one of the most talented developers working on our device, like him or not. Imagine how much momentum the .35 line of kernels would gain if he would finally abandon his codebase and move over.
[HD2 Android NAND Development] geenyous:
No need to apologise, I simply didn't understand what you meant and the "swamping" was out of actuallity because of your "needs to be proven" comment... ;)

Thank you, sir! :D

Hmm, I am not sure if we are talking about the same app here.

The one I found is called [root]live logcat and shows the actual logcat output at boot.

This won't help me at all as my freezes happen during use. Afaik, there is no app around that could help with this problem.

I had one more freeze since changing governors, so still not perfect but an improvement.

I didn't notice any differences at all. Of course, the frequencies used most are 245 and 998, not much inbetween (different to smartassV2, where most of the freqs were used), but performance or battery wise it feels the same.

Btw, I have never seen any dramatic changes based on the governor in regards to battery life or performance, I only had more or fewer problems ;)
[HD2 Android NAND Development] rmetanes:
Meaning I have to install all from the start? That will delete every thing on my phone, wont it? and what is the best partition layout again?

Thanks
[HD2 Android NAND Development] legolas93:
From OP

Yes, It will delete all your data if you don't backup your things before ;)
[HD2 Android NAND Development] 84DGR:
HTC SENSE

hey guys might be the wrong forum but i cant find anything in the threads

is there are a sense UI coming out for the HD2??

is there anything i can do to try this myself??
[HD2 Android NAND Development] FELON1908:
I have the same problem

When i do everything from this link http://xdaforums.com/showpost.php?p=21195341&postcount=207 it won't work :(
[HD2 Android NAND Development] freionluc:
Please read previous post before you ask

REBOOT AND FIX PERMISIONS

TWICE
[HD2 Android NAND Development] shumilov.max:
As far as I know - only fixing permissions

And not wiping Dalvik cache
[HD2 Android NAND Development] GhostKlart:
Thanks, that worked, now I can go to sleep
[HD2 Android NAND Development] mpis:
In this thread is solved min 20 times!!!

Fix is:

reboot to CWM

fix permissions

reboot - sound is OK
[HD2 Android NAND Development] RRRAM:
I'm coping thit .apk in /system/app/ and russian downloader. And My HD2 download any Dictionary.

Mast have any people

Thenks!!!!!! I'm happy man:D
[HD2 Android NAND Development] Archeronx:
wap push support?or how enable sory my bad engilish
[HD2 Android NAND Development] EndUser2012:
Sweet loading this on my spare HD2 when I get home for some play before I use it main stream
[HD2 Android NAND Development] + Que PPC:
Wipping data (Both of them), applying the rom, apply the zip firmware downgrade you gave me tytung then fix permissions... i cant pass the setup process :s it cant connect by my ISP and make wifi not works.

I will boot completely then apply the firmware will report back

on my third chance :s

I have the Tmobile version of HD2 maybe we have that issue :s

Edit: The wifi becomes... disabled cant even push it :p its a no go for me the V1 :(
[HD2 Android NAND Development] cmoe:
Endless Boot animation

Hi,

did the install twice now with package from both mirrors and with HSPL 3.03.HSPL and 2.08.HPSL but I am getting endless boot animation screen on 1st boot.

I am using 512Leo with CLK 220/5 and 5.0.2.6 CWM (HD2Toolkit). Beta 10 worked just fine but I am getting an endless Boot Animation screen here. Did Task29, then CLK install, then Recovery install, wipe SDEXT, install rom, install clk kernel and reboot -> endless boot anim... any ideas?

P.S.: From time to time, animation gets faster and then slower
[HD2 Android NAND Development] malisha1:
Great work, amazing rom. Its kind of hard going from a sense rom to a non sense rom where a lot of the basic features that i'm used to aren't present like sending mms to multiple ppl.
[HD2 Android NAND Development] eterno13:
hey tytung can you make a fix for the blurry mms ?
[HD2 Android NAND Development] watercooled223:
http://xdaforums.com/showpost.php?p=21187928&postcount=109
[HD2 Android NAND Development] earthworm1102:
+1 Unfortunately it cant discover (find) my computer. Weird.

Edit: Now bluetooth working with my computer... i just restarted and fix permission!!
[HD2 Android NAND Development] apeatan:
gallery - most the time crashes, is there a fix for this?

player pro - not working
[HD2 Android NAND Development] salvoplatania:
SD version ?

You can have the SD version? thank you very much
[HD2 Android NAND Development] steliosk:
Sorry for my question, what about FM radio?
[HD2 Android NAND Development] manemzjum:
Fix permissions read replys and you would have found answer

Also new problem when watching YouTube videos they play very choppy
[HD2 Android NAND Development] lan78691:
Hey if you are doing without a fresh install you said to run the scripts and fix permission and reboot the system twice... as in use the command in CWM "reboot system" twice or actually boot into rom and reboot and then do it again?
[HD2 Android NAND Development] aby1:
poor phone reception

great work ,love this rom. but notice poor reception . i have latest radio.