[16.AUG.12][ROM] CyanogenMod 9 [20120816]

Search This thread
S

sportsstar89

Guest
Hi i managed to get a nice device tree and all for cm on our ruby and i do in fact have a booting build all. I am quite Amazed by cm9 (sorry bad pun) Official discussion thread is here Well heres a general idea of what's working
  • Working:
    * Boots
    * GSM
    * Touchscreen
    * Sensors
    * Very quick
    * Music Playback (headphones, speaker)
    * Gallery
    * CPU management!
    * BOTH Internel and SD card
    * Wi-Fi
    * NFC
    * Bluetooth
    * Camera/Camcorder

    Bugs:
    * Data
    * GPS

Video (Thanks EclipzeRemix)

GITHUB

Downloads
Mirror for latest build Thanks Hasoon

  • Credits:
    CM
    cretin45 (CM-Ruby Team)
    intervigil (CM-Ruby Team)
    Sportsstar89 (CM-Ruby Team)
    And everyone else in this forum

Changelog :
  • 20120816
    * Fix Camera/Camcorder
    * Fix UMS
    * USB OTG
    * Fix Face Unlock
    * New kernel
  • 20120812
    * Fix GSM
    * Camera HAL loads
    * Re-work pretty much the entire tree
    * New kernel
    * Updated Adreno drivers
  • 20120713
    * Fix Wi-Fi
    * Fix NFC
    * Fix Bluetooth
    * Re-Work Init
    * AOSP Kernel
  • Build 1
    * Initial Release
 
Last edited:
S

sportsstar89

Guest
Screenshots

259bgus.png
14y7r89.png
2uo6plk.png
30ab7g5.png
2r3bmuu.png
29f80ep.png
2je8xap.png
1UpYZ.png
4gEE8.png
wnNMG.png
 
Last edited:
S

sportsstar89

Guest
Changelog

TEST 1
* Initial Release
 
Last edited:
S

sportsstar89

Guest
Uploading............
Edit: Its up
 
Last edited:

ryuken11221

Senior Member
Dec 4, 2010
368
17
Alexandria
well good looks man ill keep a close eye on this im downloading now ill give you a heads up and let you know what works and what doesnt work thanks for the hard work man
 

RickyG3188

Member
Mar 22, 2010
28
3
El Paso
I've been waiting for this since my two past devices had been a Nexus One and Nexus S. Great work man and I look forward to everything great you bring to the table with this one :)

Sent from my HTC_Amaze_4G using xda premium
 

dubt17

Senior Member
Feb 26, 2010
612
171
Google Pixel 6 Pro
Google Pixel 6
Anyone tried flashing both ROM and boot.img via 4EXT Recovery?

Sent from my HTC Ruby 4G using Tapatalk 2

Yes, worked perfectly. Turned off while installing the first time, just booted back into recovery and reinstalled, kernel and all!

---------- Post added at 07:52 PM ---------- Previous post was at 07:43 PM ----------

Status Report:

What works and works well:

-Music Playback (headphones, speaker)
-Graphics (WAY Smoother than any ROM for this phone out right now)
-Gallery (plays back video and shows pictures well / no lag)
-Calculator (Mmmmm, numbers are added and subtracted perfectly)
-CPU management! I can change clocks and governors without it crashing!
-BOTH Internel and SD card

What works almost:

-Movie Studio (opens, loads a project, but can't import video. My guess being the format we recorded in gingerbread doesn't play well with it, but I can watch them fine in the gallery)

What doesn't work:

-Camera (But when I open camera, instead of a force close, it says "Can't connect to the camera", which is nicer than it not opening at all!)
-ANY GSM (NO data, calls, text)
-Wifi (Kernel / hack needed)
-Bluetooth (Kernel / hack needed)
-DSP Manager (I'm guessing libs needed somewhere, because it doesn't force close, it just doesn't effect audio either through headphones or speaker.)


All in all, very stable ROM, and the fastest I've seen yet on this device! Cannot wait for at least GSM functions for a daily driver ;)

---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------

Advance power menu also working!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    ok guys i started with this task, i have looked for a couple of hours and i will have a tweaked build.prop tomorrow (half way). something i did just out of curiosity is open terminal emulator and type netcfg, below are the results, shouldn't it be rmnet0 the one getting a MAC address?? o_O

    Code:
    [email protected]:/ $ export PATH=/data/local/bin:$PATH
     [email protected]:/ $ netcfg
     lo       UP                                   127.0.0.1/8   0x00000049 00:00:00:00:00:00
    [B] dummy0   DOWN                                   0.0.0.0/0   0x00000082 7a:d1:c1:be:ab:40(why are we using dummy instead of the one below?)[/B]
     [B]rmnet0   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00(this is what's specified on the build.prop)[/B]
     rmnet1   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet2   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet3   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet4   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet5   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet6   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet7   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio0 DOWN                            100.206.232.94/30  0x00000000 00:00:00:00:00:00
     rmnet_sdio1 DOWN                            100.206.232.94/30  0x00000000 00:00:00:00:00:00
     rmnet_sdio2 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio3 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio4 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio5 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio6 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio7 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     sit0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
     ip6tnl0  DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00

    with WiFI enabled
    Code:
    [email protected]:/ $ netcfg
     lo       UP                                   127.0.0.1/8   0x00000049 00:00:00:00:00:00
    [B] dummy0   DOWN                                   0.0.0.0/0   0x00000082 7a:d1:c1:be:ab:40(why are we using dummy instead of the one below?)[/B]
     [B]rmnet0   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00(this is what's specified on the build.prop)[/B]
     rmnet1   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet2   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet3   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet4   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet5   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet6   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet7   DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio0 DOWN                            100.206.232.94/30  0x00000000 00:00:00:00:00:00
     rmnet_sdio1 DOWN                            100.206.232.94/30  0x00000000 00:00:00:00:00:00
     rmnet_sdio2 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio3 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio4 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio5 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio6 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     rmnet_sdio7 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
     sit0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
     ip6tnl0  DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
     [B]wlan0    UP                               192.168.1.XXX/XX  0x00001043 00:d2:8b:43:9f:fd(WiFi activated)[/B]

    when dialing *#*#4636#*#* the test with and without wifi says at the bottom GSM disconnects: ========DATA======== , wouldn't this be either PPP or RMNET or any other type of gateway? also the Network type says HSDPA:9 , correct if i am wrong but wouldn't the value be 11 for HSPA?

    i based the data type on this table i found on another thread which i lost by accident....ill find it again

    UNKNOWN = 0; "G"
    GPRS = 1; "G"
    EDGE = 2; "E"
    UMTS = 3; "3G"
    IS95A = 4; "1x"
    IS95B = 5; "1x"
    1xRTT = 6; "1x"
    EVDO_0 = 7; "3G"
    EVDO_A = 8; "3G"
    HSDPA = 9; "H" or "3G"
    HSUPA = 10; "H" or "3G"
    HSPA = 11; "H" or "3G"

    probably you guys are going to laugh at my "findings" but ill keep trying and see if any of the changes i did on the build.prop will work, total noob here but anything just to keep things moving forward, i do understand some term , the ones i don't a simply google search will do.
    10
    Christ its easier to set up 1AESS, even if you're doing noob work it still helps, anyways, how exactly does data work on regular rims? What if sport did a new port from htc villa (if it has cm) wouldn't it be. faster with slightly more work?

    Sent from my tee pee.

    For what I know people is busy with their personal side and sportstar is probably busy so I'm taking a look at this to see what I can find , I'm not claiming to be a dev but even if it doesn't work for anybody at least it works for me on the learning part.

    Currently I'm looking into the ril , many people around claimed to have the same data issue on cm9 so I'm reading asking qestions about certain things and most have said is the ril.

    Tonight I will more time to take a look at this Rom again.
    7
    [Stock 'HTC Sense' Network Info Dump:
    ==============================

    =====
    netcfg
    =====
    lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
    dummy0 DOWN 0.0.0.0/0 0x00000082 56:24:78:4a:86:94
    rmnet0 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet3 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet4 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet5 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet6 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet7 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio0 UP 21.154.32.85/30 0x00000041 00:00:00:00:00:00
    rmnet_sdio1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio3 DOWN 0.0.0.0/0 0x00001002 1a:ac:d6:09:ab:90
    rmnet_sdio4 DOWN 0.0.0.0/0 0x00001002 4e:1e:2a:35:da:b8
    rmnet_sdio5 DOWN 0.0.0.0/0 0x00001002 82:17:f3:9c:1a:f4
    rmnet_sdio6 DOWN 0.0.0.0/0 0x00001002 22:13:ae:f2:f0:e5
    rmnet_sdio7 DOWN 0.0.0.0/0 0x00001002 96:d3:4d:b6:c5:e0
    sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
    ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

    =============
    busybox ifconfig
    =============
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:280 errors:0 dropped:0 overruns:0 frame:0
    TX packets:280 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:19568 (19.1 KiB) TX bytes:19568 (19.1 KiB)

    rmnet_sdio0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
    inet addr:21.154.32.85 Mask:255.255.255.252
    inet6 addr: fe80::e473:ca64:454d:f093/64 Scope:Link
    UP RUNNING MTU:1440 Metric:1
    RX packets:3551 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3818 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1311326 (1.2 MiB) TX bytes:658292 (642.8 KiB)

    ===========
    busybox route
    ===========
    default 21.154.32.86 0.0.0.0 UG 0 0 0 rmnet_sdio0
    21.154.32.84 * 255.255.255.252 U 0 0 0 rmnet_sdio0
    21.154.32.86 * 255.255.255.255 UH 0 0 0 rmnet_sdio0

    ============
    busybox netstat
    =============
    busybox netstat
    Active Internet connections (w/o servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 ::ffff:21.154.32.85:52643 pb-in-f188.1e100.net:5228 ESTABLISHED
    tcp 24 0 ::ffff:21.154.32.85:49851 ::ffff:66.211.180.109:https CLOSE_WAIT
    tcp 24 0 ::ffff:21.154.32.85:43799 svcs.g.ebay.com:https CLOSE_WAIT
    tcp 1 0 ::ffff:21.154.32.85:44083 pd-in-f102.1e100.net:https CLOSE_WAIT
    tcp 1 0 ::ffff:21.154.32.85:59842 pd-in-f102.1e100.net:https CLOSE_WAIT
    tcp 0 0 ::ffff:21.154.32.85:51231 api-slb-ecmp-06-prn1.facebook.com:https ESTABLISHED
    Active UNIX domain sockets (w/o servers)
    Proto RefCnt Flags Type State I-Node Path
    unix 3 [ ] STREAM CONNECTED 3293 /data/radio/qmux_client_socket 121
    unix 3 [ ] STREAM CONNECTED 5551 /data/radio/qmux_client_socket 138
    unix 2 [ ] STREAM 6712 /dev/socket/dbus_bluetooth
    unix 2 [ ] STREAM 3156 /dev/socket/aepls001
    unix 2 [ ] STREAM CONNECTED 46011 /dev/socket/dnsproxyd
    unix 3 [ ] STREAM CONNECTED 45940
    unix 3 [ ] STREAM CONNECTED 45939
    unix 3 [ ] STREAM CONNECTED 45930
    unix 3 [ ] STREAM CONNECTED 45929
    unix 3 [ ] STREAM CONNECTED 42194
    unix 3 [ ] STREAM CONNECTED 42193
    unix 3 [ ] STREAM CONNECTED 40121 @jdwp-control
    unix 3 [ ] STREAM CONNECTED 40114
    unix 3 [ ] STREAM CONNECTED 40113
    unix 3 [ ] STREAM CONNECTED 40110
    unix 3 [ ] STREAM CONNECTED 40109
    unix 3 [ ] STREAM CONNECTED 40100
    unix 3 [ ] STREAM CONNECTED 7361
    unix 3 [ ] STREAM CONNECTED 7360
    unix 3 [ ] STREAM CONNECTED 6742 /dev/socket/dbus
    unix 3 [ ] STREAM CONNECTED 6741
    unix 3 [ ] STREAM CONNECTED 7190 /dev/socket/displayd
    unix 3 [ ] STREAM CONNECTED 7189
    unix 3 [ ] STREAM CONNECTED 6054 /dev/socket/rild
    unix 3 [ ] STREAM CONNECTED 6053
    unix 3 [ ] STREAM CONNECTED 6172 /dev/socket/zygote
    unix 3 [ ] STREAM CONNECTED 5688
    unix 3 [ ] STREAM CONNECTED 6152 /dev/socket/vold
    unix 3 [ ] STREAM CONNECTED 5674
    unix 3 [ ] STREAM CONNECTED 4089 /dev/socket/netd
    unix 3 [ ] STREAM CONNECTED 5658
    unix 3 [ ] STREAM CONNECTED 4084 /dev/socket/dbus
    unix 3 [ ] STREAM CONNECTED 4083
    unix 3 [ ] STREAM CONNECTED 3720 /data/radio/qmux_connect_socket
    unix 3 [ ] STREAM CONNECTED 5528 /data/radio/qmux_connect_socket
    unix 3 [ ] STREAM CONNECTED 5349 /dev/socket/installd
    unix 3 [ ] STREAM CONNECTED 5525
    unix 3 [ ] STREAM CONNECTED 5355
    unix 3 [ ] STREAM CONNECTED 5354
    unix 3 [ ] STREAM CONNECTED 3138
    unix 3 [ ] STREAM CONNECTED 3137

    ===============================================


    Ok, the above is the output of the major network commands, while connected by T-Mobile data, with WiFI OFF...

    Using the busybox versions of course, the 'android' versions are pretty dense

    Note:
    IP addy assigned to rmnet_sdio0, but no MAC.
    MACs assigned to rmnet_sdio 3 - 7, but no IPs.
    Almost as if 'rmnet' is a PPP style protocol, or a bunch of things are bridged... However, 'ifconfig' shows no evidence of bridging.


    Turning ON WiFi, and letting it connect produces the same results as at home.

    Even with Data ON, when WiFi is ON and Data is ON, a WiFi connection results in an 'ifconfig rmnet_sdio0 down' (or equivalent):

    IN Data Coverage, Data 'On', WiFi 'On' and authenticated to access-point:
    =============================================================
    netcfg
    lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
    dummy0 DOWN 0.0.0.0/0 0x00000082 56:24:78:4a:86:94
    rmnet0 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet3 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet4 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet5 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet6 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet7 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio0 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio1 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio2 DOWN 0.0.0.0/0 0x00000000 00:00:00:00:00:00
    rmnet_sdio3 DOWN 0.0.0.0/0 0x00001002 1a:ac:d6:09:ab:90
    rmnet_sdio4 DOWN 0.0.0.0/0 0x00001002 4e:1e:2a:35:da:b8
    rmnet_sdio5 DOWN 0.0.0.0/0 0x00001002 82:17:f3:9c:1a:f4
    rmnet_sdio6 DOWN 0.0.0.0/0 0x00001002 22:13:ae:f2:f0:e5
    rmnet_sdio7 DOWN 0.0.0.0/0 0x00001002 96:d3:4d:b6:c5:e0

    sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
    ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
    wlan0 UP 192.168.99.6/24 0x00001043 18:87:96:3f:90:84
    =============================================================

    Note: Unlike the CM9 Netstat, there is NO IP Addy assigned to the rmnet_sdio0 interface with WiFi active.

    running 'busybox ifconfig rmnet_sdio0 up' does switch 'down' to 'up', but no IPv4 addy is drawn (just that gawd-awful abomination known as IPv6. Whoever thought to use GUIDs for network addys... UGH!)

    running dhcpcd on rmnet_sdio0 results in an APIA address (169.254.0.0/16 subnet)

    It appears RMNET is a proprietary Qualcomm protocol that performs a function similar to PPP, and the rmnet_sdio interfaces are not 'real' physical interfaces, but rather something like a 'ppp0' interface (for those who didn't know).

    It also appears that some other 'ports' of Android (eg, to WinMo devices like the HD2) have used PPP in leiu of RMNET, because they couldn't get RMNET working... Don't know how well that will work for UMTS & HSPA speeds, vs GPRS....

    http://tenderloin.bricked.googlecod...04eb44768b/Documentation/usb/gadget_rmnet.txt

    http://forum.xda-developers.com/showthread.php?t=790756
    http://forum.xda-developers.com/showthread.php?t=1694012&page=64

    It appears that qmuxd (which is not OSS) is responsible for operating the rmnet interface, similar to 'pppd' on a PPP connection....

    So, now that you guys have read this whole blob... Does it help?

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

    BTW, whoever had that cm9 phone with the original netcfg (That got me going on this) showing rmnet_sdio0 with a public IP...

    Hook the thing up via USB, go into ADB Shell, and do an 'ifconfig rmnet_sdio0 up', followed by an 'ifconfig wlan0 down', and a 'ping 8.8.8.8'

    Post the results...

    ---------- Post added at 06:02 PM ---------- Previous post was at 05:58 PM ----------

    BTW, network engineering/systems admin is my 'thing' - along with a good bit of VoIP/SIP, but my coding experience is limited to 1 term each of C++ & java in college (back about a decade ago), and a good bit of VBA/MS Access afterward...

    So some of the background stuff dealing with the nitty-gritty of phones/radios/kernel-coding... I may write what I find & it may be something everyone knows...

    Just trying to see if this data stuff is possibly a config-error vs a coding/kernel/RIL problem....
    7
    Let's stop this nonsense. Only development related posts. If what you say isn't related to fixing or working on this ROM, then don't say it at all.

    Sent From My HTC Amaze 4G Via Someone's Room ;)
    6
    Here is a modified ext.jar - it was missing all of the htc specific flags to make certain things work - namely data. It simply couldn't work without the files I added to it.. if anyone is willing to test, either replace it in the original zip before flashing, or push it to the /system/framework and reboot
    I can't be 100% sure it WILL fix data, but I know without these mods data simply cannot work.