• 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

c1cl0n

Senior Member
Jan 30, 2010
642
805
c1cl0n asked me to test the ported ROM for magldr boot and I am very impressed with the build, it is fast and smooth. Just a +1 for permissions:) Nice work.
Edit; +1 for permission for c1clon to post the new thread that is:)
Thanx Robbie
CM9 Unofficial is really promising, clean, fast and smooth
Now I have 2 edition of this port - Standart and GApps included, of course with 2 Kernels - Milaq and tytung r2.4_uniMAC
All editions working fine, but I still can't share it without granted permissions
:(
 
Last edited:

nygmam

Senior Member
Oct 15, 2007
872
209
New York, NY
Tonight's version 053012 didn't seem to work for me. Downloaded twice with no luck, I just get a boot loop.

Shall I try a third?

Sent from my CM9 HTC HD2 using xda premium
 

nygmam

Senior Member
Oct 15, 2007
872
209
New York, NY
Why can't you attach logcat when you report this, it's so hard ? How do you expect people to magically know what is causing bootloops ? :confused:

It's like saying please fix my car but you can't touch it.

First step was to confirm it is an issue and not just me.

Read my post, I didn't ask what the cause was, just wanted to confirm it wasn't a bad download, and if I was alone...could have been bad rom, bad, flash, wiping issue, etc...

Now its confirmed, next step is to figure out the why. Although heading to work now, so wont get to do it until tonight, att which point I'll probably just try 53112.
 

pathologo

Senior Member
Jul 26, 2008
658
49
Anyone else having trouble toggling 2G and 3G in the recent nightlies?
No, not on 20120528. But after having WiFi on for a longer period and then turning it off won't establish a mobile data connection.
Toggle airplane mode, toggle radio, toggle data connection, toggle 2G/3G - nothing works, a reboot is required to get mobile data working again.
Google still didn't fix that? In ICS... the newest Android??
 

kylew1212

Senior Member
Dec 1, 2011
485
281
Alabama
www.memoryx2.com
Are you guys running clk or magldr? I know this is a long running argument but that could possibly affect your mobile data connection..
I prefer clk 10-1 over magldr, and I've been using it for months. However I've been using magldr for about two days to do some testing on wifi calling and I've had a much better data connection. With clk I have had the issues you are describing.


Sent from my HTC HD2 using xda premium
 

ph03n!x

Senior Member
Dec 18, 2010
2,158
1,586
No, not on 20120528. But after having WiFi on for a longer period and then turning it off won't establish a mobile data connection.
Toggle airplane mode, toggle radio, toggle data connection, toggle 2G/3G - nothing works, a reboot is required to get mobile data working again.
Google still didn't fix that? In ICS... the newest Android??
I have a proper data connection, and I am able to get a data connection back right after I turn off wireless - all that works. What I am not able to get to work is manually choosing if I want to connect through 2G (EDGE) or 3G (HSDPA). I have a Notification Widget for toggling between 2G/ 3G/ 2G+3G, and now no matter I do, it always stays in 2G+3G. Even if I choose "Use only 2G networks" in settings > wireless & networks > mobile networks, it automatically unchecks itself if I get back to the same menu, and I get 2G. This is if I set the build.prop property ro.telephony.defauly_network to 3 (GSM PRL mode). If I set it to 0 (WCDMA preferred), it automatically picks HSDPA as long as there is a 3G signal. I am not able to change this property using *#*#4636#*#* either - it automatically falls back to what I had set in build.prop.

Problem is I have an unlimited data plan for 2G and 2GB limit for 3G - and I use 3G when I am tethering or want to look something up real quick. I let the phone churn away in 2G mode for all sync'ing and background data stuff. Now that is being a pain.
Are you guys running clk or magldr? I know this is a long running argument but that could possibly affect your mobile data connection..
I prefer clk 10-1 over magldr, and I've been using it for months. However I've been using magldr for about two days to do some testing on wifi calling and I've had a much better data connection. With clk I have had the issues you are describing.


Sent from my HTC HD2 using xda premium
I swear by cLK - Have used Magldr only during the initial days of NAND, have been on cLK ever since. Am currently on cLK 1.5.

Can you enable the Notification Widget for 2G/ 3G toggling (settings > system > notification drawer > Widget buttons - check Toggle 2G/ 3G, scroll down and choose 2G/ 3G Only/ 2G+3G in Network modes) and see if it toggles without problems between 2G and 3G?

I will be hooking up my phone to the laptop in a few, and will see if logcat has anything. But I remember this working just fine on the 15th nightly.
 
  • Like
Reactions: Burag

kylew1212

Senior Member
Dec 1, 2011
485
281
Alabama
www.memoryx2.com
I swear by cLK - Have used Magldr only during the initial days of NAND, have been on cLK ever since. Am currently on cLK 1.5.

Can you enable the Notification Widget for 2G/ 3G toggling (settings > system > notification drawer > Widget buttons - check Toggle 2G/ 3G, scroll down and choose 2G/ 3G Only/ 2G+3G in Network modes) and see if it toggles without problems between 2G and 3G?

I will be hooking up my phone to the laptop in a few, and will see if logcat has anything. But I remember this working just fine on the 15th nightly.


I would check it, however I am currently testing paranoid Android for wifi calling. I prefer call, but I can't deny I seem to have had a much better data connection today. I live in the country and service changes from g - e - 3g depending where I am at and I think that with magldr I've had a more stable data connection because it has not dropped yet even on g I have a stable connection. Don't get me wrong I'm a huge call fan!


Sent from my HTC HD2 using xda premium
 

pathologo

Senior Member
Jul 26, 2008
658
49
I have a proper data connection, and I am able to get a data connection back right after I turn off wireless - all that works.
Even after really long periods of nonstop WiFi? E.g. after a whole night and longer?

Even if I choose "Use only 2G networks" in settings > wireless & networks > mobile networks, it automatically unchecks itself if I get back to the same menu, and I get 2G.
I assume fix_permissions also doesn't help?
This happened with various builds already?
Do you make any changes to the ROM before flashing?
 

ph03n!x

Senior Member
Dec 18, 2010
2,158
1,586
I would check it, however I am currently testing paranoid Android for wifi calling. I prefer call, but I can't deny I seem to have had a much better data connection today. I live in the country and service changes from g - e - 3g depending where I am at and I think that with magldr I've had a more stable data connection because it has not dropped yet even on g I have a stable connection. Don't get me wrong I'm a huge call fan!


Sent from my HTC HD2 using xda premium
Lol, I guess autocorrect is changing cLK to call. For my usual places of travel/ home/ offices, I have had no issues whatsoever with cLK and data.
Even after really long periods of nonstop WiFi? E.g. after a whole night and longer?

I assume fix_permissions also doesn't help?
This happened with various builds already?
Do you make any changes to the ROM before flashing?
Yes, I have Wifi on if I am around a access point (Home and office), and data comes up when I am away - Wifi is usually always on, and it has always switched to data when am not around an access point.

I have already done a bunch of troubleshooting, including fix permissions. I make a few changes before flashing - like add gapps to the ROM's zip, delete a few apps from /system/apps, etc. I will be flashing a stock ROM later today after backing up to make sure it is not something I am doing that is causing this.

I have seen this happening on the 23rd build and the 29th build. Before that I was on 15th build, which worked fine for me. And I did not flash any builds in between...
 
  • Like
Reactions: Burag

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