• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[NIGHTLY][Full HWA] CyanogenMod 9 [4.0.4][Kernel: cmhtcleo/tytung]

Search This thread

kylew1212

Senior Member
Dec 1, 2011
485
281
Alabama
www.memoryx2.com
I've noticed this is (probably) one of few roms that comes by default for CLK with a patch for MAGLDR (most do the other way around, patch for clk).

Assuming i don't wan't anything with Android on SD, or Windows Mobile/Phone, would you advise CLK instead of MAGLDR ? I've heard a few issues with data, is this still true today ?







PPP is pretty stable in ICS & cLK 1.5, at least for me. Not that I had any issues in Gingerbread and cLK 1.4..x or 1.5 either. However, a lot might depend on where you are.

@milaq - a related question. Are we using the b4 or b5 version of the cLK ril wrapper, can you tell please?

I am a huge clk fan, especially since 1.5 has been released. However a few days ago I switched to magldr to do some testing with wifi calling. I have been using magldr for a little over a week compared to probably 1+ years of clk (1.3, 1.4, 1.5) and my data connection over the last week has been unbelievably better. I like everything about clk better but I can't deny the better connection I've had recently. Magldr has been better on connections in every way. In remote areas, and good service areas.

Sent from my HTC HD2 using xda premium
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
sites.google.com
we're using 0.8b5 by cedesmith

clk is default mostly because magldr doesnt support boot.img style kernel/ramdisk (yet).

Sent from my HP TouchPad

MAGLDR v1.13 supports boot.img style more than one year.
Please read README file DAF.txt.
However all ROM chefs use "yboot" instead of "rboot" because MAGLDR v1.12 only supports "yboot" and is not necessary to change it to "rboot" in v1.13.
Code:
    types:
        "ya"  - YAFFS2 partition. MAGLDR can show root directory context or read kernel/initrd from it. 
        "raw" - RAW data.     
        [COLOR="Blue"]"yboot"  - this partition contains zImage and initrd.gz for kernel boot in YAFFS2 format[/COLOR]
	"yrecov" - this partition contains zImage and initrd.gz for recovery boot in YAFFS2 format		
        [COLOR="Red"]"rboot"  - this partition contains zImage and initrd.gz for kernel boot in RAW (like in native Android devices) format[/COLOR]
	"rrecov" - this partition contains zImage and initrd.gz for recovery boot in RAW (like in native Android devices) format
 

davidk91

Senior Member
Aug 9, 2009
239
24
www.fcb.cz
Hi all,
could you help me? I would like to try this ROM, but I am on Magldr and when I tried flash this ROM I got that kernel did not find or something like that...how should I proceed?
 

ph03n!x

Senior Member
Dec 18, 2010
2,158
1,586
we're using 0.8b5 by cedesmith

clk is default mostly because magldr doesnt support boot.img style kernel/ramdisk (yet).

Sent from my HP TouchPad

@milaq- I usually had a better connection with b4. I was wondering if anything changed right from when I started using the nightlies, as I never had a glitch when switching between 2G and 3G modes- the data connection would reconnect almost immediately, and that was not so with the stock nightlies. I flashed the 4th nightly with b4 and sure enough, data seems better in this ~12 hour I am using it...

All who are having trouble with data connection, try the wrapper 0.8b4 to see if it works better for you :)

_
Swyped from my HTC HD2 (ICS 4.0.4)
 

bipinsen

Senior Member
Sep 16, 2007
871
82
I am a huge clk fan, especially since 1.5 has been released. However a few days ago I switched to magldr to do some testing with wifi calling. I have been using magldr for a little over a week compared to probably 1+ years of clk (1.3, 1.4, 1.5) and my data connection over the last week has been unbelievably better. I like everything about clk better but I can't deny the better connection I've had recently. Magldr has been better on connections in every way. In remote areas, and good service areas.

Sent from my HTC HD2 using xda premium

Haha.. I had gotten so frustrated by cLK that I made this post here. I went back to cLK because of the awesome feature of on-the-phone partitioning. So now I'm back to living with data drops. Oh well. When will magldr 2 ever come out... :rolleyes:
 

milaq

Inactive Recognized Developer
Feb 24, 2009
638
2,643
milaq.net
MAGLDR v1.13 supports boot.img style more than one year.
Please read README file DAF.txt.
However all ROM chefs use "yboot" instead of "rboot" because MAGLDR v1.12 only supports "yboot" and is not necessary to change it to "rboot" in v1.13.
Code:
    types:
        "ya"  - YAFFS2 partition. MAGLDR can show root directory context or read kernel/initrd from it. 
        "raw" - RAW data.     
        [COLOR="Blue"]"yboot"  - this partition contains zImage and initrd.gz for kernel boot in YAFFS2 format[/COLOR]
	"yrecov" - this partition contains zImage and initrd.gz for recovery boot in YAFFS2 format		
        [COLOR="Red"]"rboot"  - this partition contains zImage and initrd.gz for kernel boot in RAW (like in native Android devices) format[/COLOR]
	"rrecov" - this partition contains zImage and initrd.gz for recovery boot in RAW (like in native Android devices) format

hmyeah thx.
but the default is yboot (that is why i was a tad confused)

but nevertheless to all MAGLDR users:
we moved to the unified updater-script architecture.
please read the second post carefully for instructions
 
  • Like
Reactions: Bologna and Burag

nygmam

Senior Member
Oct 15, 2007
872
209
New York, NY
Interesting, I have been using cLK for a long time, and while I did have some Data issues on GB builds, This ICS seems to have rock solid data. Never had an issue, although now having posted this, I expect I will spend the rest of the day loosing my data connection :eek:
 

Burag

Senior Member
Jun 29, 2009
295
102
Interesting, I have been using cLK for a long time, and while I did have some Data issues on GB builds, This ICS seems to have rock solid data. Never had an issue, although now having posted this, I expect I will spend the rest of the day loosing my data connection :eek:
I second that, never had any issues with data @ cLK.
I can even calim that data seems for me the same in MAGLDR and in cLK.
 

nygmam

Senior Member
Oct 15, 2007
872
209
New York, NY
yeah, that one slipped in todays build :/

i fixed it earlier today. tomorrows build should be fine again

Irony or irony... Irony can be quite ironic sometimes. Never had issues with data before on cLK. While flashing last nights build, I thought I would post how solid Data is on cLK, only to have no data after I posted. Very funny actually... I even had a feeling I was tempting fate with my first post. No matter, Still love flashing nightly builds. Getting a SG3S at the end of the month, but don't think I will give up flashing and toying with my HD2, it is such a great phone...
 

ph03n!x

Senior Member
Dec 18, 2010
2,158
1,586
Lol.. I flashed 4th Nightly with 30th May ramdisk and Marc1706's kernel v0.1.2, and with clK data wrapper 0.8b4 - all worked fine, so didn't even though this bug existed :D

@milaq - Tytung seems to have done some changes in his latest kernel's usb drivers and ramdisk (from the changelog)for native usb tethering to work. Can we have it imported in the nightly's too? WIred Tether works great, but not having an app and using the native functionality 'feels good' :)
 

tytung

Senior Member
Jun 21, 2010
3,574
15,005
sites.google.com
Lol.. I flashed 4th Nightly with 30th May ramdisk and Marc1706's kernel v0.1.2, and with clK data wrapper 0.8b4 - all worked fine, so didn't even though this bug existed :D

@milaq - Tytung seems to have done some changes in his latest kernel's usb drivers and ramdisk (from the changelog)for native usb tethering to work. Can we have it imported in the nightly's too? WIred Tether works great, but not having an app and using the native functionality 'feels good' :)
Native USB Tethering fix
http://forum.xda-developers.com/showpost.php?p=26930603&postcount=1756
 

ph03n!x

Senior Member
Dec 18, 2010
2,158
1,586

Awesome! This worked pretty well for me. Like you had mentioned in your Kernel thread, I enabled USB Tethering twice, and it tether just fine - posting from it.

I used Tytung's R3 kernel with the modified initrd.gz (based on 4th June nightly) and the init.d script - am attaching the ramdisk and script I used in case someone wants to try. Note that I had changes the default CPU Frequencies to be 128 MHz to 998 MHz and the default governor to smartassv2 in the ramdisk.

On a separate note, marc1706's kernel v0.1.2 refused to boot (reboots at second boot logo) with this ramdisk. I modified the ramdisk from 23rd May (which I was using earlier) to have USB Tethering - it booted fine, but it did not tether.
 

Attachments

  • USBTethering.rar
    164.2 KB · Views: 11

milaq

Inactive Recognized Developer
Feb 24, 2009
638
2,643
milaq.net
Lol.. I flashed 4th Nightly with 30th May ramdisk and Marc1706's kernel v0.1.2, and with clK data wrapper 0.8b4 - all worked fine, so didn't even though this bug existed :D

the bug was in the ramdisk you probably replaced ;)

@milaq - Tytung seems to have done some changes in his latest kernel's usb drivers and ramdisk (from the changelog)for native usb tethering to work. Can we have it imported in the nightly's too? WIred Tether works great, but not having an app and using the native functionality 'feels good' :)


thx :)
already did the ramdisk and kernel stuff yesterday;
https://github.com/cmhtcleo/android_kernel_cmhtcleo/commits/ics/
and
https://github.com/cmhtcleo/android_device_htc_leo/commit/c65823004b01882d0b36cd56f83334dbf84646cc

will add the initscript soon

i'm using yboot instead of rboot and have no issue at all.. is this just for the latest nightly ?

tomorrows build requires this :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 131
    xNnWC.png



    Welcome to the unofficial CyanogenMod 9 nightlies

    The releases will co-inside and the build start time is at 00:01 UTC, and by 01:00 the builds should be uploaded. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP

    These builds are compiled from the latest CyanogenMod repos and device repos on device and vendor files.

    Furthermore these builds are multiDPI, i.e. you can run the rom at any dpi between 160 and 240 while having hi-res assets. Also Phone.apk won't crash anymore if a DPI < 190 is set.

    kernel/ramdisk packaged boot.img style
    if you are on magldr see second post for instructions

    System partition size currently required:
    Without Gapps 155MB
    With Gapps light 190MB
    With Gapps standard 195MB

    Download nightly builds here

    or via GooManager
    Google apps
    Latest Gapps LIGHT (2012-03-17) for ICS
    (picoTTS folder removed to save some diskspace - can be downloaded to SD later if needed)


    Tip: If you want to have your softbuttons and/or density settings persist over updates and don't want to edit build.prop with every update, use local.prop.
    create a file named local.prop in your /data root (i.e. /data/local.prop) with the following contents (for example):
    Code:
    qemu.sf.lcd_density=160    # overrides ro.sf.lcd_density in build.prop
    qemu.hw.mainkeys=0    # activates the softbuttons

    • arif-ali - for his huge contribution to the cmhtcleo project and beeing a indispensable part of the Android community
    • securecrt and Rick1995 - for their awesome work on a full HWA kernel and other great contibutions to the Leo codebase
    • copenhagen - for support with CM7 and now with ICS/CM9
    • warrenb213 - for support with CM7 and now with ICS/CM9
    • charnsingh_online - For starting this great project for porting to CM
    • tytung - Continued dedication of his work to the HD2 Thanks for you kernels
    • texasice - For creating the first HD2 compitable ICS through passion/bravo
    • ankuch - thanks for the HW accel, codecs and Camera
    • zivan56 - your input for the headphone fix
    • Bexton - The fix for USB Mass Storage
    • michie - Your work on ICS for the HD2
    • cyanogen - For starting this great project
    • Google - This wouldn't have happened without the releases of Android from you

    Visit us in #cmhtcleo on freenode
    Webchat


    ---------- brought to you by the cmhtcleo team ----------
    arif-ali | milaq | zeusk

    34
    MAGLDR instructions

    Although we have an unified updater-script for both cLK and MAGLDR you need to take care that your MAGLDR partitioning is correct.

    We are using boot.img style kernel/ramdisk (as everyone else should be).
    For MAGLDR users that means that you need to specify your boot partition as rboot.

    The following flash.cfg is recommended (system size can vary)

    Code:
    misc ya 1M
    recovery rrecov|ro|nospr filesize recovery-raw.img
    [COLOR="Green"]boot rboot|ro 5M[/COLOR]
    system ya 190M
    cache ya 2M
    userdata ya|asize|hr allsize

    Instead, you can also download this package:
    http://milaq.exnet.me/downloads/android/leo/magldr_part_cm9.zip

    Extract and run DAF to flash the layout above
    26
    Building from source

    I thought it would be a good idea that I just give a quick run through on how this is compiled.

    First we need a Linux environment, preferably Ubuntu >= 12.04 or a recent Debian

    Follow the simple Howto here, to just get an idea of the pre-requisites

    To initialize the common cyanogenmod repos, run the following command
    Code:
    repo init -u git://github.com/CyanogenMod/android.git -b ics

    then to get device specific repos for the HD2 you need to pull in a local manifest.
    you can use this one
    Code:
    curl https://raw.github.com/milaq/android/ics/local_manifest_htc_leo.xml > .repo/local_manifest.xml
    (you can of course tailor your own too)

    then you need to sync the repositories
    Code:
    repo sync


    You can also run repo sync -j 4, say if you had 4 cores to speed things up, you may also need to add a -f, to make sure that it continues to the end even if you get any error messages. You may need to repeat this process 2 or 3 times to make sure everything is synced. This will take a long time to synchronise, so be patient.

    next run the following command to gets some prebuilt apks (doesn't need to be done with every build)
    Code:
    vendor/cm/get-prebuilts

    so after this, you need to run the following commands

    Code:
    . build/envsetup
    lunch cm_leo-userdebug
    make -j4 bacon

    This has changed from lunch cyanogen_leo-eng to lunch cm_leo-userdebug, this is the new method from CyanogenMod team for CM9

    In the end you will get a zip file in out/target/product/leo/full_leo-ota-eng.root.zip.
    17
    I'll look into what can be done for tether, hopefully it should be helpful for upstream (tytung) too, other than that i notice no noticeable change in the .35 kernels (personal opinion).

    I have fixed usb tethering.
    16
    Hi all,

    Some of you guys must be thinking that maybe I have deserted this project.

    Nope.

    I have been busy at work, family etc... Real Life can sometimes take over; I have been doing the occasional testing, but not getting that far.

    The code that tytiung, nexusn1, uses code from AOSP, and some of the code is cherry-picked from CM, and codeaurora, so everything seems to be working. It also seems the compilers may be slightly different as well, therefore the pre-compiled HW accel stuff doesn't work.

    I on the other hand am trying to get CM (core) to work, It could be that I need to port the adreno200 code from what they are using to the CM code, and go from there, and see if we can get it working. Even I am getting blank screen with no HW accel :(; although touch screen is working.

    So at the moment I am stuck at the HW accell and display drivers from 4.0.3. When I have news I will get back.

    regards,
    Arif