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

Search This thread

yar2

Senior Member
Feb 12, 2012
136
18
Capacitive key backlight

Great work!

So far I have only noticed one issue: The capacitive keys backlight works initially, but after installing some basic apps and rebooting several times, they stop working. I have checked all the settings and they appear to conform with the settings listed for prior versions of this ROM.
 
  • Like
Reactions: dimon2242

CaptainMaki

Senior Member
Jun 26, 2011
237
12
Great work!

So far I have only noticed one issue: The capacitive keys backlight works initially, but after installing some basic apps and rebooting several times, they stop working. I have checked all the settings and they appear to conform with the settings listed for prior versions of this ROM.

if you are already testing it: did you used the google apps in the link? I haven't seen them installing on the previous version when I've used the google apps in the link.
 

Ngong0

Member
Nov 26, 2010
37
5
Is there a way to force the one time init after installing gapps after rebooting once? If I install gapps without rebooting it does it, but the phone acts strange. but if I do reboot, it doesn't run. Thanks in advance.:)
 

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Great work!

So far I have only noticed one issue: The capacitive keys backlight works initially, but after installing some basic apps and rebooting several times, they stop working. I have checked all the settings and they appear to conform with the settings listed for prior versions of this ROM.
Why not use automaticbacklights ? Its full fixed in my build. Try these settings:
Code:
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%
If you disable autobacklights I'm not sure who controling your key lights (kernel or android), so on clean install you don't need to touch backlight settings, only you need to enable option "allow lights decrease" and thats all, your lights levels will be automaticaly controled and increased/decreased in darken roms or lighten roms ! But if you not like autolevels, sorry, I not going to fix problems with keylight (it working perfect for my needs). Why Cyanogenmod enabled autolevels as a default ? I think because same thing. And do not install third part apps in order to control light levels because I think that will break compatibility between cm9 framework (that allready in cm9) for lights...
 
Last edited:

yar2

Senior Member
Feb 12, 2012
136
18
Auto brightness fixed it. I had used the power widget to change the screen brightness and didn't realize that would affect the keys backlight.

Again, thank you for all your hard work. Its truly amazing what you have accomplished with this "old" phone. I have been using an ATRIX while trying to fix a reboot problem with my Aria, and you are way ahead of what the have been able to accomplish with this more advanced phone.

Sent from my MB860 using XDA
 

KillerBeaver

Senior Member
Oct 19, 2010
241
42
The second number in the first column should be 34 not 33 for the auto back light.

Sent from my Liberty using XDA
 

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
The second number in the first column should be 34 not 33 for the auto back light.

Sent from my Liberty using XDA

No... see levels in hex format = { 0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF },
so in dec format it is: 0, 33, 77, 220, 3...
 
Last edited:

ZeroSigea

Member
Aug 28, 2010
25
14
Hello all.

Installed this ROM and I'm loving it. Some thoughts concerning cpu frequencies though.

So, out of curiosity, does anybody use the frequency settings below 400-480 Mhz? In my experience, that range is either completely useless or it results on FC's and/or "(x) has stopped working." messages on this ROM. I stuck with the default CPU settings for the first day or so, then I increased the min to 480 and any messages like the above have stopped. Also, 864mhz seems a bit high. I don't mean to remove it, using it is entirely up to the end user, but just to use a lower max freq out of the box. 864mhz causes my Aria to run too hot and hardlock if used for too long.
 

KillerBeaver

Senior Member
Oct 19, 2010
241
42
No... see levels in hex format = { 0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF },
so in dec format it is: 0, 33, 77, 220, 3...

I don't know about the hex to decimal conversion. But, just looking at the "upper" "lower" label it appears that the the lower limit for the second row should be greater than the upper limit for the first row. This is the pattern that is followed for all the subsequent rows of settings. Why is this not followed through in the second row?
 

CaptainMaki

Senior Member
Jun 26, 2011
237
12
Hello all.

Installed this ROM and I'm loving it. Some thoughts concerning cpu frequencies though.

So, out of curiosity, does anybody use the frequency settings below 400-480 Mhz? In my experience, that range is either completely useless or it results on FC's and/or "(x) has stopped working." messages on this ROM. I stuck with the default CPU settings for the first day or so, then I increased the min to 480 and any messages like the above have stopped. Also, 864mhz seems a bit high. I don't mean to remove it, using it is entirely up to the end user, but just to use a lower max freq out of the box. 864mhz causes my Aria to run too hot and hardlock if used for too long.

Are you sure these are the default speeds? last version was set on 245Mhz -806MHz
 

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
Hello all.

Installed this ROM and I'm loving it. Some thoughts concerning cpu frequencies though.

So, out of curiosity, does anybody use the frequency settings below 400-480 Mhz? In my experience, that range is either completely useless or it results on FC's and/or "(x) has stopped working." messages on this ROM. I stuck with the default CPU settings for the first day or so, then I increased the min to 480 and any messages like the above have stopped. Also, 864mhz seems a bit high. I don't mean to remove it, using it is entirely up to the end user, but just to use a lower max freq out of the box. 864mhz causes my Aria to run too hot and hardlock if used for too long.

Where you found 864mhz ? Its removed from kernel 2 months before! Which kernel version is in your cm9?
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,720
22,375
I don't know about the hex to decimal conversion. But, just looking at the "upper" "lower" label it appears that the the lower limit for the second row should be greater than the upper limit for the first row. This is the pattern that is followed for all the subsequent rows of settings. Why is this not followed through in the second row?
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?
 
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