yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] diesburg:
The rafpigna kernel you compiled isn't working for me. I am trying to use it with typhoons latest. Every time I try to start wifi, I get a reboot. That's after restoring my old install of typhoons and with a fresh install. My steps for installing were installing latest typhoon through CWM with zip file, then installing rafpigna kernel with zip you provided on post 3. I don't think I'm doing anything wrong because the same steps but with the tytung kernel provided in post 3 works just fine, just with the battery issues that were mentioned.
[HD2 Android NAND Development] arif-ali:
the changelogs here in the git repository, it is based on MDJ old kernel

http://gitorious.org/~arif-ali/linux-on-wince-htc/aa-mdj-s/commits/test
[HD2 Android NAND Development] diesburg:
I tried your kernel with typhoons, I must be doing something wrong to use it with typhoons. I flash the .zip with cwm, then I flash the zimage and initrd.gz from typhoons rom with fastboot and I get reboots trying to start wifi....
[HD2 Android NAND Development] songokussm:
after following these instructions i am greeted with boot loop. Log-cat says:

-----------------------------------------

- waiting for device -

link_image[1962]: 142 could not load needed library 'libc.so' for '/system/

/sh' (load_library[1104]: Library 'libc.so' not found)CANNOT LINK EXECUTABLE

---------------------------

both kernel were tested.

cLK for TyphoonN CM7 2.5 ram was the rom.

TyphoonN CM7 2.5 - Normal works just fine.
[HD2 Android NAND Development] diesburg:
Cool, I'm not the only one getting reboot.... same setup here except I'm not using RAM version of typhoon. Thanks for posting logcat details, that should make it easier for someone to patch it up knowing what the problem is!
[HD2 Android NAND Development] Kameirus:
so just out of wonder here

if it doesnt work on typhoons rom why mention in his thread
[HD2 Android NAND Development] songokussm:
Ram version does not. Normal version does.
[HD2 Android NAND Development] diesburg:
Probably because it was suppose to work with typhoons rom...... tytungs kernel that he patched and compiled for us works, just with excessive battery drain.

Normal version does not work, I use the normal non-ram version and I get reboots also when trying the patched rafpigna from post 3. I'm guessing a mistake was made compiling/patching it because as I stated above, the tytung one works fine, but not the rafpigna. I'm going to try a fresh install with the rafpigna kernel without ext partition on sdcard and see if that makes a difference.

songokussm, did the normal version work for you? Are you using ext partition on sd ?
[HD2 Android NAND Development] arif-ali:
For those people having issues with the phone rebooting please check the following things, as this happened to me a few months back when i was testing 1.1

check /system/etc/init.d/01modules if this is loading msm_rmnet.ko. If it is remove the line. If the rmnet driver is loading, then this will deffo cause issues.

if this still doesn't fix the problem, then check the initrd, and the init.rc file, check the line with libhtc_ril_wrapper, and check that the end of the line does not say anything to do with rmnet. If it does then remove that portion of the line. The resulting line should say

service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init

I hope that helps
[HD2 Android NAND Development] diesburg:
I got this in init.d/01modules:

#!/system/bin/sh

# Load MODULES

sleep 1

if [ -f /system/ppp ]

then

echo "Not loading RMNET module as /system/ppp exists"

else

echo "Loading RMNET module as /system/ppp doesn't exist" <--Do I need to

insmod /system/lib/modules/msm_rmnet.ko <--remove these?

fi

insmod /system/lib/modules/tun.ko

insmod /system/lib/modules/cifs.ko

insmod /system/lib/modules/nls_utf8.ko

insmod /system/lib/modules/fuse.ko

echo "+++ TUN / CIFS / UTF8 / FUSE activated +++";

Do I need to remove the 2 lines noted above?
[HD2 Android NAND Development] arif-ali:
ok, if that is the case then the file /system/ppp should be there, if it isn't then run "touch /system/ppp". plus check to make sure when you run "lsmod", that it doesn't list the msm_rmnet module.
[HD2 Android NAND Development] Kameirus:
thanks for clearing that up as we all know people wont read

and run to do this
[HD2 Android NAND Development] cedesmith:
use nand version, this thread is under nand development forum so i assumed everyone will use nand version of rom :D

make sure you wipe data in recovery, partition layout is not the same as your previous rom so userdata needs formating (done by wipe).

if you do not wipe userdata you will get loop boot screen and/or other unpredicted errors

if you need to keep your data back it up then restore it.

on rafpigna's kernel it seams i compiled wrong branch and missed wpa_supplicant and that causes wifi to reboot phone. i am trying now to compile NEWOC_NOSENSE branch of the kernel but i get errors :o
[HD2 Android NAND Development] arif-ali:
I will have a go, I am attempting now, I'll let you know how I go
[HD2 Android NAND Development] diesburg:
Awesome, will wait for updated kernel.
[HD2 Android NAND Development] arif-ali:
rafpigna kernel patched

Hi all,

here is the rafpigna kernel, can some of you test it to see if it works. This is untested by me, so not sure how well it will work

@cedesmith, do you want to add this to your post?

btw, this was compiled with 2009q3 compiler
[HD2 Android NAND Development] cedesmith:
wich branch did you use ? rafpinga said to use NEWOC_NOSENSE.

i think only that version support wifi tetering.

did you use that ?
[HD2 Android NAND Development] diesburg:
I will test right now, if everything is functional in this besides tethering(mentioned above) that would be good for me, I don't need or use tethering. I will post results of testing it in a few.

Just tested it out, it boots, wifi turned on without problems, will further test battery and do some benchmarks to see if it is getting close to same as typhoon with normal kernel and magldr. One question though, I see you don't include initrd.gz in with it, is the proper way to use this flashing the zip with cwm, then taking zimage out of the .zip you provided of the kernel, and taking initrd out of typhoons .zip and then flashing them together with the fastboot command to flash them both to boot partition?
[HD2 Android NAND Development] arif-ali:
I did, double checked my build history, and realised a typo, so re-done again and re-attached in the previous post
[HD2 Android NAND Development] diesburg:
Alright, with a few widgets running on homescreens, no use of a task killer, I am getting what looks like to be slightly lower benchmark score in quadrant than with magldr and typhoon. On 5th benchmark with OC set to 1190 maz(same as I had it with magldr) , I am getting just below nexus 2.2+ and with magldr and typhoon with rafpignas kernel I was able to reach slightly above the nexus one 2.2+ on the chart in quadrant. Battery doesn't seem great, at 11:54, had 59%, at 12:01 after a few quadrant runs, have 56%.

If there is anything else you would like me to do to test this kernel, such as a specific app or something, let me know, I will test anything you want and post results.

Just did a 10 minute run with screen off with that kernel you provided above. I left wifi on when doing the test (isn't wifi suppose to shutoff when the phone goes in standby?) anyways, at the beginning of the test, had 53% battery and 10 minutes later, had 52%

Like I said, if there is anything better I can do than my so called "tests" let me know and let me know what app I need, would love to help with getting a fully/correctly working rafpigna kernel for cLK and typhoons rom. Once the kernel seems to be working correctly with no excessive battery drain, I will make a package for cLK and typhoon like I mentioned before.
[HD2 Android NAND Development] diesburg:
I have one question that's off subject a little. If XDA is all about open ideas and stuff and peoples work and threads like mdj's and gpc's have been being taken down recently because of GPL stuff, why is dft and cotulla able to have magldr on XDA? It's closed source and maybe I'm wrong but wouldn't you think that he used code from something open source for his bootloader like tinboot or something? And I asked why mdj's and gpc stuff got taken down and possibility of malicious code was mentioned.....couldnt there be some sort of malicious code in magldr we dont know about? Don't get me wrong, I appreciate cotulla and dft teams work a lot, just a question.... It just seems like people/teams with larger contributions to the XDA community don't have to follow what people with smaller contributions have to.
[HD2 Android NAND Development] cedesmith:
kernel is under gpl so you can't get around that.

LK on the other hand is under a license that does not require that source code of final product to be redistributed so even if they take code from codeaurrora that is ok (as far as i know)
[HD2 Android NAND Development] diesburg:
Alright, I think somethings still up with that kernel or something else. After my battery tests, I flashed back to magldr and restored and my battery is back up by like 10% and I never charged it any in between flashing.....
[HD2 Android NAND Development] seadersn:
error on my side ...
[HD2 Android NAND Development] cedesmith:
take #2

i recompiled the kernels on post #3, hope this time i got it right.

updated instructions to be a little more clear
[HD2 Android NAND Development] diesburg:
It boots and wifi turns on without problems. Haven't benchmarked or had time to see if battery drain is excessive yet. I have one question though... can I restore from my install that I have backed up? I ask because you say to flash the zip for typhoons rom and didn't mention anything about restoring in the first post. I didn't try, I followed your directions exactly so I didn;t run into a problem not related to the kernel.
[HD2 Android NAND Development] diesburg:
Is wifi suppose to go off automatically when the phone screen goes off? I ask because if so, mine is not. My battery drain was at least 2% in less than 10 minutes...... but I thought maybe that's normal with wifi running? I know before rafpignas new kernel my wifi would shut off after the screen was off for a few and I know it is not now because I am getting google voice notification sounds when the screen is off everytime I get a new message.

Will the chosen governor have affect on the battery life? I have always jsut used the one selected by default which is the interactive governor. If I can maybe get better battery life with a different one, let me know.
[HD2 Android NAND Development] MotoMudder77:
Battery life should be checked after the phone is setup, rebooted a few times.

just for comparison. Im on Typhoons via Magldr. 1.5 hr, mostly in standby. battery lost 3%

default interactive governor. max 1536, min 245.
[HD2 Android NAND Development] diesburg:
There is a package up I made now with all files needed to install and use this except for the zip file of typhoons rom (figured most of you probably already have his rom downloaded) There is also a readme in the package, refer to it or post 3 of this thread for instructions on how to install. Don't thank me for this, all I did was pack it all up into a rar file. Cedesmith and anyone else mentioned in this thread is responsible for this great work!

http://diesburg.co.cc/downloads/clk.typhoon.rar

My hosting is a paid service, server is in the USA so download should be quick for people in the USA.

Feel free to mirror the file elsewhere for faster downloads outside of the US. I will have another one later, it will be the same package but with typhoons rom included.
[HD2 Android NAND Development] seadersn:
sorry for searching the error not at my side :o i must have made a mistake @ compiling; re-compiled kernel with latest arm-eabi and it looks like all is ok now :)
[HD2 Android NAND Development] crawlingcity:
another rom incoming to clk, i wnana give this some love !
[HD2 Android NAND Development] M..N:
Good to hear :)
[HD2 Android NAND Development] 2000impreza:
I've been testing CLK 1.3.1 for the last 12 hours using the setup below. So far it's been fairly solid and have not run into any problems. I also kept the rom/kernel consistent between clk and magldr for simplicity of troubleshooting.

Rom: Typhoon 2.4.5

Kernel: Tytung r6

Battery drain: Appears to be similar to Magldr with same rom/kernel. I logged 2 to 5 ma standby drain using current widget.

PPP: My biggest concern is PPP stability. I haven't used PPP since the days of SD card builds booting from WinMo. Over the course of 12 hours using the clk setup, I haven't noticed any data hangs or drops on ppp. Data appears to be fairly stable.

Performance: I haven't noticed any performance differences between magldr and clk using the same kernel and rom combination. This is purely based on "feel". I've never bothered with quadrant or linpack.

magldr to clk: The switch was fairly easy. After flashing the clk, I restored /data and /sd-ext from my last nandroid backup and retained all of my previous data.

Overall, clk appears to work fairly well. I'll probably continue to use clk for the next few days to further test battery drain and ppp stability. Props to cedesmith for bringing clk to us.
[HD2 Android NAND Development] 2000impreza:
CWM recovery mounting sd-ext

Clockworkmod recovery seems to have problems mounting /sd-ext. I can't get CWM to backup sd-ext or even manually mount. Does anyone have this issue?
[HD2 Android NAND Development] songokussm:
weird because my data crashes every few seconds. at most it lasts a minute. same setup. switching to airplane and back makes it work again, but dies shortly there after.

edit: battery drain in a little higher then normal. after 8 hours and many restarts (to get data back) i was hat 43%. Current widget reports 6ma, but its wrong.
[HD2 Android NAND Development] diesburg:
I also had the same issue. It said it wouldn't mount when I tried to restore sd-ext. I thought it still worked but after thinking about it, I think all my apps were there only because the partition still contained everything from my magldr install. I will mess with it more later and post my results. I am going to try to partition the card in CWM in CLK and see if it mounts after that. The partition before was made in CWM using magldr. Maybe that's the problem?
[HD2 Android NAND Development] crawlingcity:
My 2 active roms, Ultimate Droid (2.5 froyo, 3.0.1 Gingerbread) are ported and working on clk, ready to flash through cwm (flash - use). Tytungs kernel included, boot.img and ppp from cedesmiths post. since it's 6am, im going to sleep and tomorrow i'll release this with 2 proper threads.
[HD2 Android NAND Development] diesburg:
I formatted the sdcard in CWM, then partitioned it with an ext partition and it still will not mount it. I get this:

E:unknown volume for path [/sd-ext]

I thought maybe the problem could be that it was partitioned with CWM in magldr before but with my test I stated above, repartitioning it in CWM with cLK, it must be something else. This is not a problem for me because I have the tmobile hd2 and I have just decided to quit using ext partition to see how it affects battery life as I have read in some threads that it can use more battery if ext partition is in use for apps.

EDIT: Just messed around a little but more with the ext partition.... I wiped my sdcard without using the phone, used a usb card reader, so it had no partitions on it, then partitioned it with CWM..... made an ext parition, no swap partition.... then plugged it back into the computer with the usb card reader.... the ext3 partition shows up on the pc, so it is able to make the partition.... but why it cant mount the partition that it just created??

By the way, on the computer, I am using minitool partition wizrd 5 to see the partitions on it. It has never failed me before besides when the sdcard became corrupted(had to use hp format tool to fix corrupted sdcard)
[HD2 Android NAND Development] arif-ali:
The fstab needs the sd-ext partition adding, once this is done then the external SD card should work.

Cedesmith, could you re-compile recovery for us with the added line in fstab

In the meantime, I did write in another post on what is required, in this same thread. Search, amend the file and see if it works.
[HD2 Android NAND Development] seadersn:
i've already thought about adding this to fstab and compiling it; if he isn't faster than me, i'll try it today, in the evening. i only need the correct sources... let's have a look at it and try.

so far it runs stable, everything ok here. good work, cedesmith :)
[HD2 Android NAND Development] FrAsErTaG:
finally got some time today to flash CLK 1.3

running typhoon CM7 with the 1.8oc rapigna ppp kernal overclock.

did a fresh install, no nandroid restoring from Magldr.

all is running nice at the moment, will comment back after more time on the battery and such but so far seems to be running great and it boots like an android phone now!!
[HD2 Android NAND Development] cedesmith:
i recompiled CWM with sd-ext on /etc/recovery.fstab
[HD2 Android NAND Development] Novembre5:
Not sure if this was mentioned before, but I just flashed HSPL 3.03 and cLK runs with no problems. So that is another plus you can add to cLK over magldr. :D
[HD2 Android NAND Development] 2000impreza:
I can confirm the sd-ext mounts fine with the updated cwm recovery. I've been running cLK for the last couple days and can't find anything wrong with it. Battery life and ppp stability is good.

cedesmith, Just curious if you have plans to add the function of rebooting directly into recovery from the rom?
[HD2 Android NAND Development] cedesmith:
i had found something wrong, tethering does not work it is because multiport module is not compiled into kernel and even with a recompiled kernel ppp\\d is not in config_tether_upstream_regexs :(

i want to add rebooting in recovery/bootloader but i don't know where reboot code is saved. if no one knows/can find i can eventually patch kernel to save it at a known address so bootloader can read it.
[HD2 Android NAND Development] seadersn:
i've read, that the "misc" partition is appropiate for this. in case of commands from android itself or rommanager (reboot to recovery, flash zip file, do a backup with manually entered folder-name etc.) a file will be saved, which passes on the necessary parameters to the bootloader / kernel.

therefore I asked for leaving the misc partition and therewith make this function available.
[HD2 Android NAND Development] cedesmith:
1.3.1 has misc partition
[HD2 Android NAND Development] seadersn:
k, it was the check you've removed, didn't read correct, sry.

but is this correct? i'm not completely sure; if someone can confirm...
[HD2 Android NAND Development] diesburg:
So if I'm getting error about misc partition in CWM, does this mean I must be using 1.3.0 ? And about the battery... I flashed back to cLK from magldr after the new recovery image was posted(with the ext fix) before flashing back to cLK, my battery was like 28%, after flashing, my battery is nearly 100%, will it help to calibrate the battery reading by letting the phone go completely dead?
[HD2 Android NAND Development] seadersn:
yep, calibrating will help; offmode charging over night (not with usb on pc but with a/c adaptor), next morning boot into recovery, do a battery stats wipe and boot into android: done :) then use the phone until it dies.

regarding misc partition: the check for it (if existant) was removed, nothing more, as i understood. pls correct me if i'm wrong.

you can add the misc partition in init.c with your desired size. this removes the misc error from cwm.
[HD2 Android NAND Development] jhr5474:
Are

their more than two roms available for this or is there a tutorial on how to port them over to this? I installed today and never want to go back to Magldr!

There's just something about watching the hd2 boot directly in to Android that kicks ass! Thank you Cedesmith!
[HD2 Android NAND Development] crawlingcity:
2.5 - http://xdaforums.com/showthread.php?p=11895175

3.0.1 - http://xdaforums.com/showthread.php?p=11895247
[HD2 Android NAND Development] diesburg:
I bet we could get android on rhodium/topaz devices a ot quicker than DFT could get magldr to hose devices by porting this...lol... just an idea... I already like this way better for the hd2..... one big reason is problems found have been fixed within days..... usb mass storage mode hasnt worked in magldr since the beginning.... how many months will it take for them to release one with fixes? and the same for off charging....
[HD2 Android NAND Development] mattfmartin:
clK is the ****:p
[HD2 Android NAND Development] diesburg:
I can say that after doing a fresh install of typhoons 2.5 rather than restoring from my backup made with magldr CWM that things are much better now.... main thing is battery life... I'm not sure how(someone probably knows, maybe battery stats being saved in the backup?) but battery life is way better with a fresh install... and I now cut out the ext partition for apps.... I got the tmobile version so I don't know why I even used ext partition in the first place.... would the kernel put up for this and typhoons be compatible with the cm7 nightlies rom?
[HD2 Android NAND Development] mattfmartin:
Does cLK support backups that were made in Magldr? Because i just ran a backup and it didnt boot from it? :confused:

Nevermind wasnt thinking after i wiped, it erased the kernel:p Good to go now
[HD2 Android NAND Development] diesburg:
As far as I know, it does because my backups worked.... BUT, after you restore the backup, you need to flash the kernel again with the zip file of rafpginas kernel provided in post 3.... its because the boot.img used is differnt somehow, I'm not sure on the technical stuff on it but it's something to do with yaffs2 I think..... Anyways, restore your backup with CWM, then flash zip file of rafpginas kernel from post 3 and it should work... it did for me... but not until I flashed the zip of rafpignas kernel from this thread... and it has to be after the restore because the restore wipes the boot partition...my restore from backup had battery life problems, but I think it was because I changed something(don't remember what) that was keeping wifi on in standby..... I would recommend doing a fresh install and making a new backup just so you know that if you run into problems it's for sure not because of restoring from a backup made from magldr....
[HD2 Android NAND Development] mattfmartin:
Yea I was so used to it not being erased. When you wipe everything from cwm. Definitely love the fact it boots straight up like a native phone.
[HD2 Android NAND Development] diesburg:
Yea, me too, the splash screen straight to the android boot screen I love!! And what I mentioned before about updates for problems..... the first problem(for me) was the kernel... I got the kernel I requested for typhoons rom within a day... then the problem with it not being able to mount ext partition.... fixed within like a day....it's open source, anyone can fix it... magldr is not open source, only DFT can fix problems... as I mentioned above, the usb mass storage and charging the phone when it's off has been known since the beginning... but how many months until DFT fixes it? And the other useless functions for android users like booting to WP7, booting android from sd and so on... most of us just want android and want our device to be as close to a native android device as possible.... we can't/probably will never get this from magldr.....cedesmith, I say you get a button in your sig for donations!!! You said in your fist post "I don't have time or patience for questions and support" .... well, you have gave several people time and support... you deserve donations for this!!! I would compare DFT to motorola.... you might have to wait for a year to see your motorola device be updated to 2.2 froyo...... but if you go custom/open source rom, it will be updated way before a years time.....

Q: Should i install it ?

A: If you had to ask probably not. If has no functional benefits over magldr.

and for that, I and others do see benefits over magldr....lol