[ROM]CM9 4.0.4 ICS Liberty[09.Jul.2012]

Search This thread

artlov

Senior Member
Dec 17, 2008
161
46
I've never seen filtered values lower than 33 on my Gratia (even in the very dark room). Is it OK, or sensor fault?
 
Last edited:

KillerBeaver

Senior Member
Oct 19, 2010
241
42
I think you not understand how that working in our aria. Aria hardware sensor have only 10 fixed steps (0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF) and nothing more! In kernel its defined same! To understand, you can watch at top of screen raw sensor value (filtered/raw) that is filtered directly from hardware!
In android settings: there is 4 rows: lower, upper, screen, buttons. Lower and upper mean "range" for screen and buttons: for example 0 to 32 giving light level66 for screen and level 255 to buttons, 33 to 76 giving 96 for screen and 255 for buttons... etc
You need to know. Buttons have only 2 levels:0 is "buttons light off" and 255 in "buttons light on" !!!
But for screen its diferent. Screen have range from 0 to 255... so you can adjust screen lights for your needs!
You can change only screen and buttons levels for your needs, but do not change first row (lower) because these raw values is in kernel (confirmed raw values from aria sensor!)

So for example: if filtered/raw value from hardware (look at top of screen to get idea) is 33 (that will set your screen level light to 96 and turn your buttons light on), if you not like screen level 96 and you no want your buttons to be "on" when raw value is 33, you can adjust these in 3rd and 4rd row for your needs. For example you can increase or decrease light level for screen to for example 111 (or 255 or whatever) and if you want buttons off, set buttons value to 0...

Understand now?

Ok, i understand the reason for the values. but, if there are two ranges that share the same limit, then won't that make one, like the first row, never get used?

Sent from my Liberty using XDA
 

dylantep

Senior Member
Apr 28, 2012
60
10
phone unresponsive during calls

Hey guys, if im on a call and my screen goes off, it wont turn back on regardless of what button I hit. anyone else have this problem? or a solution?
 

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Ok, i understand the reason for the values. but, if there are two ranges that share the same limit, then won't that make one, like the first row, never get used?

Sent from my Liberty using XDA

If I understand you... there no two ranges that share the same limit (for example if raw filtered value is 33, than will be used range 33 to 77, so display value and buton key value will be used from column 3 and 4). You never will see raw/filtered values for example 36, or 47...etc, these values from sensor have always step 33,77,...etc, so do not edit first column. Expose your phone over light and you will see what I mean. I don't know why Cyanogen opened first column for write/read option instead of read only like seccond column, but first column I set/is set default, same as a defined in kernel so you do not touch these values in first column, only you can experiment with 3rd and 4rd column)
 
Last edited:

KillerBeaver

Senior Member
Oct 19, 2010
241
42
If I understand you... there no two ranges that share the same limit (for example if raw filtered value is 33, than will be used range 33 to 77, so display value and buton key value will be used from column 3 and 4). You never will see raw/filtered values for example 36, or 47...etc, these values from sensor have always step 33,77,...etc, so do not edit first column. Expose your phone over light and you will see what I mean. I don't know why Cyanogen opened first column for write/read option instead of read only like seccond column, but first column I set/is set default, same as a defined in kernel so you do not touch these values in first column, only you can experiment with 3rd and 4rd column)

So, what you're saying is the first row is useless. Right? Because the lowest raw value the phone can hit is 33. So it will display values from the second row (33,76).

Sorry for the confusion.
 

Rumy91

Member
Nov 15, 2011
14
2
Some problem here..

Is the latest ROM deodexed? Cause i had the hard time which is my aria does not compatible with Reloaded ICS. FC of Systemui and something..

Sometimes my aria stuck at the boot animation. And the default overclocking 806mhz making my aria freeze.

By the way, thanks to dev!

::pstt, recently i heard about Linaro will be added into cm9..
 

CaptainMaki

Senior Member
Jun 26, 2011
237
12
Hey guys, if im on a call and my screen goes off, it wont turn back on regardless of what button I hit. anyone else have this problem? or a solution?

did you replace the digitizer? sounds like a problem with the proximity sensor.

@Munjeni: Could you please post the MD5 signature for the new update? thx.
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Hey guys, if im on a call and my screen goes off, it wont turn back on regardless of what button I hit. anyone else have this problem? or a solution?

Thats problem only with 3g networks (after latest changes in my kernel for sleep policy)... try 2g network.

Anyone noticed better deep sleep mode in phone (increased phone usage in comparation with working hours)??? In my tests -> http://desmond.imageshack.us/Himg19...ename=screenshot2012061116121.png&res=landing phone is in sleep mode 78hours (battery is stil ~50%)... Please let me know!
 
Last edited:

bjoswald

Senior Member
Aug 10, 2011
171
44
Ocala
Battery drain is an inherent problem with Android. This ROM isn't any better or worse than the rest. When we improve how batteries work we will improve battery life.
 

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Battery drain is an inherent problem with Android. This ROM isn't any better or worse than the rest. When we improve how batteries work we will improve battery life.

Battery is not problem than backround proceses in background, clocks, de-clocks, hw states... :) ...ok your opinion ! Waiting opinions from other guys, especialy for power management :)
 

xam247

Senior Member
Apr 5, 2011
61
6
Definitely having issues with deep sleep. From the looks of the battery settings, wifi won't suspend at all. Is this normal? I believe it is keeping my Aria awake far too often, resulting in a battery that drains without use in roughly 10hrs.
 

Attachments

  • Screenshot_2012-06-07-15-44-55.png
    Screenshot_2012-06-07-15-44-55.png
    65.6 KB · Views: 139
  • Like
Reactions: munjeni

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Thanks for info! So from your tests I see wifi is not disabled by power manager!

Ok, my tests was: wifi off, gps off, bluetooth off, mobile network off, 2g on, 3g off. In sleep mode I got ~78 hours (battery drained ~50%). With "current widget" (market app) I geting 7mA in sleep mode (so thats very very good thing!). Cpu spy app reporting ~90% is in deep sleep mode (see screenshoot few posts back). Other tests I not tried like with enabled wifi...etc! I can confirm my phone sleeping with these settings!
 
Last edited:

CaptainMaki

Senior Member
Jun 26, 2011
237
12
Seems like another great version, installing now.

is there a way to hide the text scripts that runs on boot? very frightening to the girlfriend...
 

rawrv42

Member
Dec 30, 2011
40
3
Lowell
Is anyone else having issues with the gmail widget? On the first boot it was in the widgets list and functioned properly when placed on the home screen, but when I rebooted my phone the widget disappeared from the home screen and disappeared completely from the widgets list. This only happened on the latest version of the ROM (June 7th). Any ideas?

Excellent ROM otherwise, thanks to the dev.
~Rawrv42
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 70
    Sorry, I do not want to make confusion with two different roms (munjeni/Winsuk), currently Winsuk github source in comparation with my localy source is much different, also kernels is diferent, so I opened this thread from that reason! Will update this thread soon!

    CM9 4.0.4 ICS Liberty (Ice Cream Sandwich)

    This is a port of CM9 (Ice Cream Sandwich) for Aria/Liberty based on WinSuk repo

    Screenshoots:
    http://img845.imageshack.us/img845/340/screenshot2012040818074.png
    http://img585.imageshack.us/img585/8750/screenshot2012040818081.png
    http://img442.imageshack.us/img442/491/screenshot2012040818083.png

    Currently working and not working:

    What works:
    • Auto-brightness
    • Bluetooth
    • Browser
    • Capticive buttons (with backlight)
    • DSPManager
    • Headphones/Headset (with buttons)
    • Keyboard
    • Market downloads
    • MMS
    • Notification light
    • Overclocking
    • Phone radio (calling, sms, data)
    • Sensors (light, proximity, rotation, acceleration, compass)
    • Sound & Mic
    • Superuser
    • Tethering (Bluetooth untested)
    • Touchscreen (with multitouch)
    • Trackball
    • USB Mass Storage Device
    • Vibration & Haptic feedback
    • Wifi
    • Gallery
    • Wifi sleep
    • Built-in data usage meter - full working now
    • Hardware acceleration (EGL)
    • Live wallpapers
    • Screenshots
    • Screen off/on animations
    • Wallpaper scrolling
    • wake by trackball
    • bootanimation - have right size now including cm9 logo
    • Wifi signal strength bar on status bar (wpa_supplicant_8)
    • GPS
    • Camera shoots and preview
    • Fast gps lock (qcom-librpc + new gps.conf)
    • Mobile networks choosing in Select Network

    If something missing or not working please let me know!

    What working but not good:
    • Camera panorama
    • Camcorder (can not stop recording)
    • HQ Videos... have frezes (we need hardware bassed decompresion instead of software bassed to get fully working videos)
    • FM radio have no audio


    Google Apps for Ice Cream Sandwich:
    You need to find an stable gapps for your needs!
    But I use this and it's stable for me -> http://goo.im/gapps/gapps-ics-20120422-signed.zip :)

    My Aria android git: https://gitorious.org/ics-on-htc-aria/master/commits/master
    My kernel git: http://gitorious.org/ics-cyanogenmod-2-6-35-kernel-msm7227-for-htc-aria/ics/commits/master

    Download old cm9 rom - 07.Jun.2012.:
    http://www.2shared.com/file/R6uEJBP4/cm9_liberty-ota-engroot_07Jun2.html
    md5: C25F74D11F0C1E03BC72927ABCA8E686

    Download new cm9 rom - 09.Jul.2012.:
    http://www.2shared.com/file/pUT_xRG1/cm9_liberty-ota-engroot_09Jul2.html
    md5: 269880B7DC6224E28325F273F91451E7

    WARNING for new cm9 rom!
    Rom have scripts that will erase all nand partitions needed for clean install! Android folder and .android_secure folder will be deleted from sdcard allso, so backup your data if you have something inside!

    Thanks:
    First, big thanks to Qualcomm and their user space library that was needed for HW acceleration!!!
    Google - for both Android and their search engine, which are awesome
    CyanogenMod Team
    WinSuk
    s0be
    modpunk
    Everyone who has shared their working ICS source - It has helped a lot in fixing things
    30
    Instruction/fixes/changelog is here:

    10.Apr.2012:
    • Wifi signal icon is fixed

    13.Apr.2012:
    • source totaly cleaned after some tests (pull reguest from Cyanodenmod cm9 repo + very small changes (like untached)), right key is in board_device_liberty :)
    • gps fixed (I'm not tested)
    • very fast and smooth response on everything
    • lightsensor fixed
    • libcamera.so is patched from msm7k to msm7x27 but not working (need to port old QualcommCameraHardware.cpp)

    27.Apr.2012:
    • Camera preview and camera shoot is fixed, not stable but working good [credits to modpunk, WinSuk and all who shared their source]
    • Ics librpc for gps fixed [credits to modpunk]
    • kernel updated [there was problem with memory allocation, so camera not worked from that reason...]
    • a lot of framework changes/cleanups is fixed by Cyanogenmod team so... [all credits to him]
    • maybe I forgot something? :)
    • light sensor/backlight is fixed and tested, please read this:


    • How to enable utomatic backligh:
      - go to settings/display/brightnress and set it to automatic
      - go to settings/display/automatic_backlight select use custom
      - go to settings/display/automatic_backlight/edit_other_levels and set 0,33,77,220,308,397,485,698,860,1023 seccond column 66,96,103,115,130,152,152,255,255,255 third column 255,255,0,0,0,0,0,0,0,0, than save&apply
      - go to settings/display/automatic_backlight and select allow light decrease
      - go to settings/display/automatic_backlight/decrease_hysteresis and set it to 50%

      Now its totaly automatic for me...​

    28.Apr.2012:
    • rom is deodexed now!

    03.May.2012:
    • New kernel with realigned Aria memory layout (heap size is increased for 8MB {adsp_size have 4MB more, gpu_size have 4MB more})... no more (sometimes but very less) force closes
    • New kernel modules (cifs, tun, nls_utf8, bcm4329.ko)... its needed for mounting network folders :)
    • New camera updates (Thanks WinSuk)
    • New memalloc and gralloc lib (disabled annoying "debug" log for memalloc... now its only "info" and "error")
    • Video still is not fixed (my wrong sorry... some HQ videos working but most of HQ videos not working :()... I think maybe reason is not good because googleOMX is msm7627 ?

    10.May.2012:
    • New kernel with new allocators (not fully ported from kernel 3 "contiguous memory nomap" only part of it :()
    • Kernel, enabled SLOB, enabled KSM, enabled LZO compresion needed for zRam... and a lot of other... you can see all changes on my git!
    • New camera upstream updates + camera timer + updates from WinSuk git (Thanks WinSuk, s0be, cm team and all who working on camera)
    • A lot of fixes from upstream
    • No force closes (added some scripts to init.d like zram automout, zram auto free, free pagecache, free dentries and inodes, modules automount, gps permission...)... but in prevention of force closes, you need to free memory sometimes to get android stable(I use airdroid app and his great memory releaser) :)
    • Old librpc + new gps.conf (gps have fast lock now)
    • First config screen on first boot :)
    • Video still is not fixed
    • Camera recorder is not fixed
    You need to enable "kernel same page merging" in setting/performance. To get full working autobacklight you need to enable "allow lights decrease" in settings/display/automatic_backlight. You do not need to enable zram, it's enabled by default by script until compcache_enable is fixed android side, kernel side it's good. This build is more stable for me!

    13.May.2012:
    • Logo for my kernel :)
    • Some tweaks for ram (you will have constantly 90mb amount of the free memory, so... less force closes or maybe no force closes:))
    • Camera recorder is fixed but... :( ((camcorder recording but no one cm9 rom for Aria have video encoding/decoding hardware bassed, its software bassed... 15 fps... we need hardware bassed compresion/decompresion to get fully working recorder and youtube videos)

    07.Jun.2012:
    • Mobile networks choosing in Select Network
    • zRam full fixed, you can enable/disable/set_size from settings menu
    • A lot a lot a lot of Cyanogenmod upstream changes :)
    • kernel: Framebufer console during boot (Its for fun... if you not like it I will disable in next build)
    • kernel: VR IO scheduler
    • kernel: InteractiveX governor
    • kernel: deep sleep mode

    09.Jul.2012:
    • All new Cyanogenmod upstream changes
    • kernel: Framebufer console during boot disabled
    • kernel: deep sleep mode (reverted back to like previous build)
    • some progress with FM radio (all is fixed and working but only have no audio :(... maybe some one have some programing skills to find what is wrong with audio? Or maybe to manually send command to kernel to get fm audio routing to headset?)
    12
    Kernel improvements: deep sleep mode working now (7mA battery drain :eek:) -> http://img525.imageshack.us/img525/1629/screenshot2012052019050.png ,new gsensor driver with support for android temperature sensor ;)...etc
    11
    New build is out, enjoy