[ROM] CyanogenMod 9.1.0d (Android 4.0.4) [20130107]

Search This thread

lwxddlqkillapp

Senior Member
Feb 10, 2012
120
44
china
The main issue is that you use TI.OMX.JpegEncoder. It won't work under ICS. Don't build/include it. The standard android's software jpeg encoder has to be used. At least for now, until the TI OMX stuff will be fixed.
Minor issue are wrong permissions of /dev/lis331dlh sensor device file. Camera tries to access it but fails. What is the owner/mode of this device file on your system?

i porting it from you build . I try some time are the same problem.
 

ngonchan

Senior Member
Sep 16, 2008
295
66
Da Lat
Regarding TB: I also use it and it worked for me (i also use sd-ext so i just restore data). The problem with TB is that phone is even slower after restoration and a reboot (happend 3 times so far). Don't know if that is incompatibility issue since all backup of user apps is done on CM7 (system apps and config are from 4.0.3). If you are using older version of TB try to update it.
I'm still waiting to test this odd slowdown after restore.
Sorry but I can't help more.

Updated TB to the latest version and problems solved. Thank you all.
 

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,926
Prague
android.doshaska.net
lwxddlqkillapp: Oops, disregard what I said, it's TI.OMX.JpegDecoder what is not working. Encoder should work.

So you have two problems.
1. you're not getting preview frames from camera
Code:
E/Sensors ( 1914): Couldn't open /dev/lis331dlh (Permission denied)
E/Sensors ( 1914): LIS331DLH_IOCTL_SET_ENABLE failed (Bad file number)
E/SensorService( 1914): Error activating sensor 0 (Bad file number)
I/BATTD   ( 1713): set_charge_current=0
E/CameraHal( 1732): GetNextPreviewFrame Error/1 frame:0x0, buffer:0x0
GetNextPreviewFrame error happens just after the sensor error.
Try chmod 666 /dev/lis331dlh to test whether the permission issue is the cause.

2. When taking the picture, the raw yuv picture data are received from camera just fine, that's good
Code:
D/CameraHal( 1732): Received raw yuv 0x4533a000 size 15980544
But your dspbridge is not working at all. The TI.OMX.JpegEncoder is not finding any DSP processor.
What is the output you get when you try to initialize the dsp using this command:
Code:
/system/bin/dspexec -v -T /system/lib/dsp/baseimage.dof
I bet there is an error. dmesg might be helpful.

EDIT: I noticed that on XT720, fjfalcon is using proprietary libLCML.so and libbridge.so, not the versions built from source. Which version of those libs are you using?
 
Last edited:

lwxddlqkillapp

Senior Member
Feb 10, 2012
120
44
china
lwxddlqkillapp: Oops, disregard what I said, it's TI.OMX.JpegDecoder what is not working. Encoder should work.

So you have two problems.
1. you're not getting preview frames from camera
Code:
E/Sensors ( 1914): Couldn't open /dev/lis331dlh (Permission denied)
E/Sensors ( 1914): LIS331DLH_IOCTL_SET_ENABLE failed (Bad file number)
E/SensorService( 1914): Error activating sensor 0 (Bad file number)
I/BATTD   ( 1713): set_charge_current=0
E/CameraHal( 1732): GetNextPreviewFrame Error/1 frame:0x0, buffer:0x0
GetNextPreviewFrame error happens just after the sensor error.
Try chmod 666 /dev/lis331dlh to test whether the permission issue is the cause.

2. When taking the picture, the raw yuv picture data are received from camera just fine, that's good
Code:
D/CameraHal( 1732): Received raw yuv 0x4533a000 size 15980544
But your dspbridge is not working at all. The TI.OMX.JpegEncoder is not finding any DSP processor.
What is the output you get when you try to initialize the dsp using this command:
Code:
/system/bin/dspexec -v -T /system/lib/dsp/baseimage.dof
I bet there is an error. dmesg might be helpful.

EDIT: I noticed that on XT720, fjfalcon is using proprietary libLCML.so and libbridge.so, not the versions built from source. Which version of those libs are you using?

thanks it is very helpful
 

malborc

Member
Aug 14, 2008
7
0
Miui from CM9?

Hi guys. Somebody know if any developers is working in port Miui V4 (ICS) based in this release? Whould be pretty good. :)
 

xd_1771

Senior Member
Feb 12, 2012
99
9
I'm still getting [THIS WIFI PROBLEM] and it is very annoying.... I'm reflashing after reflashing and nothing... unofficial ROM or the official one by OP, same thing
 
Last edited:

kremx

Member
Aug 14, 2010
46
2
miui4

It would be Mega slow.
And anyway ICS is beautiful why would you need MIUI?

Sent from my Milestone using Tapatalk

+1 for miui4. I am using miui GB on the daily basis, my next phone will run miui4. some people have greater expectations than the rest of the crowd. (yeah themes mostly) And my phone's desktop don't look iphonish (thx to themes)
 

somecanuck

Senior Member
Jun 4, 2010
64
13
Alright, I've been sitting on the sidelines watching CM9 progress here. How's the status of it so far? Does it compare favorably with CM7.2?
 

Babis_ECE

Senior Member
Aug 1, 2010
911
133
Athens
Alright, I've been sitting on the sidelines watching CM9 progress here. How's the status of it so far? Does it compare favorably with CM7.2?

CM9 still needs some basic stuff fixed. I use it daily because I don't mind these bugs, but if you can't stand some redraws of the Launcher, problem with Caller ID / Caller Log and the Camera not working as in CM7 yet, you should wait a little bit more. ;)
 

hugues42

New member
Jul 18, 2008
3
0
Hello,

I have a question regarding the launcher: on my phone it take always 4s or 5s to redraw it. (I tried with different launchers trebuchet, nova launcher or apex always the same)

On CM7 I remember an option to keep the launcher in ram memory. I dont find it anymore; this option dont exist in CM9?

Can you tell me if this option still exist and where I can find it.

Thanks
 

osahitzelgsngar

Senior Member
Aug 7, 2010
465
1,001
regarding MIUI V4...

on the German Android Forum is a Beta of MIUI V4 based on android 4.0.4 look here

anyway i'm not fan of miui. i prefer CM7/9 cause of its better performance
 

zviki

Senior Member
Dec 30, 2008
1,401
212
Maribor
ok according to version 4.0.4 worked by Nadlabak and uploaded by fellow mrvek, it works great, my contribution is to be installed by default the "lightning launcher" and accessories to customize and install the widgest, is a pitcher who has served me excellently in this rom and also does not consume much ram, so I never reboot when it leaves some application so as usual with any pitcher, at least with this launcher I think if you can use the ROM for the day :). I attached some pictures for you to see how it is .. see the tutorial videos if necessary.

launcherhttps://play.google.com/store/apps/...sIm5ldC5waWVycm94LmxpZ2h0bmluZ19sYXVuY2hlciJd

So,you have all this apps on phone and it's OK?I tried the latest build from the first post and it's not for everyday use yet.

Sent from my GT-N7000 using Tapatalk
 

igna.worn

Senior Member
Dec 3, 2011
117
15
I'm using it as an everyday rom and except for the launcher redraws and the 2 secs that every app loads its more than ok.
Cm7 is still muuuch more faster but does not have the spectacular look of cm9 (even with the theme)

Sent from my Milestone using XDA
 
  • Like
Reactions: zviki

Top Liked Posts

  • There are no posts matching your filters.
  • 176
    Yes, it simply means that we (and other locked devices as well ;) ) finally have a proper graphics driver needed by ics.

    So we have fully working hwui for any app, Chrome works (though it's too RAM hungry for Milestone to be anyones favorite browser, I guess).

    For Milestone it also means one important thing: one nasty bug of the old driver is gone. It plagued Gingerbread as well as ICS - it happened on orientation change.
    Under ICS it caused parts of the screen to become black when rotating the phone while running recent Opera Mini (due to hw reset of sgx unit during the change).
    Under Gingerbread, it caused crashes in sgx libs on rotation, for which I used workarounds directly in app source (Gallery3D) or in the framework (GoogleMaps).
    So I'll try to use the new drivers also in CM7 in the future.

    It also means that I upload a new build soon, because I postponed any releases until I'll be able to get the new drivers to work despite the locked kernel.
    I'm really happy that I succeeded :D .
    143
    Main credits:
    Obviously, it's the CyanogenMod team and all CM contributors in the first place.
    Besides that and my own humble work, CM for Milestone would not be where it is now without the essential works of Skrilax_CZ (2nd-init, OpenRecovery, custom kernel, 2ndboot fixes and more), Czechop (hack to the kernel usb initialization code that allows to keep BP working after 2ndboot to custom kernel), f_pasha (gkisystem semaphore patch), Tiago Sousa (author of the original overclock kernel module) and contributions from others that I forgot to list here ;) .
    Also worth mentioning is a lot of notable work done by the Defy developers: Epsylon, Quarx and Maniac103
    The original 2ndboot code is by Dmitriy Taychenachev and Eugen Maksimov.

    Please note that Milestone is not officially supported by CyanogenMod.

    Source: https://github.com/nadlabak
    Home page: http://android.doshaska.net/cm9
    Build from source: http://android.doshaska.net/cm9build

    Download:
    CM9.1.0d: http://d-h.st/7eH
    gapps 20121225: http://d-h.st/xd0
    OpenRecovery 2ndbootOR: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_1.zip

    Because of limited space in system, gapps are installed to /data/vendor. But if ext partition is present on sdcard, they are moved to /sd-ext.
    Therefore ext partition is highly recommended for CM9, otherwise the space for apps in /data will be too limited.
    You can find instructions on how to resize fat and create ext3 partition directly in OpenRecovery in this very fine guide by pontomedon:
    Full guide from stock Motorola Android to CyanogenMod 7 for Milestone

    CM9 for Milestone is using 2ndboot to run custom kernel despite the bootloader kernel lock.

    Android 4.x requires at least 340MB RAM available to kernel and userspace
    As we have only 225MB, don't expect any miracles - the hardware constrains count.

    HW acceleration increases application's RAM demands. You can use the included HWA Settings app to disable it per app.

    Known issues:
    You tell me ;) .

    9.1.0d (4.0.4) 07.01.2013
    - fix: keep keyboard backlight off while keyboard is hidden
    - fix crash on launch of certain apps (e.g. Aldiko) - use workaround for occasional mysteriously zeroed bitmap scale parameter
    - Apollo music player fixes - jellybean backports; reworked image fetching and caching (by iwo)

    9.1.0c (4.0.4) 30.12.2012
    - call recording: fix recording for calls with asterisk in the phone number
    - fix the per app HW acceleration disable code to work according to application package name as specified by HWA Settings app (the original implementation [which pre-dated HWA app usage] used process name, not package name)
    - re-implement the 'Disable Dock Observer' option - for users of phone cases with magnetic closures (to prevent the screen turning on in reaction to a magnet appearing near the phone)

    9.1.0b (4.0.4) 26.12.2012
    - fix VoiceSearch, VoiceTyping and Talk (voice) - please use the updated gapps package http://d-h.st/xd0
    - fix adb toggle
    - fix possible crash when recording videos and re-enable limited preview frame rate for better Camera app responsiveness
    - fix backup of system files (mostly gapps) during ROM updates
    - add built-in call recording option; no beeps every 10s during call recording any more
    - updated CMFileManager
    - wifi: disable 802.11n support by default (HT_Enable in tiwlan.ini) to prevent stale data connections when using certain N routers
    - kernel: reverted doubling of the DAC fifo size to 16384 (to prevent audio drop-outs) as it caused broken audio playback in certain games

    in case you're wondering why the new build is not uploaded to github as before, see https://github.com/blog/1302-goodbye-uploads


    9.1.0a (4.0.4) 11.12.2012
    - fix relaunch of some activities on keyboard slide out/in (e.g. YouTube playback, Root Explorer...)
    - CMFileManager included (backport from JB)
    - fix unwanted lcd-backlight activation by camera button while the screen is off (was related to the light sensor workaround that allows to use camera button to provoke sending of light sensor data without waiting for ALS interrupt)
    - better handling of Basband Processor panic (by maniac103) - instead of immediate reboot like in stock firmware, user is notified and can choose to postpone the reboot (e.g. when he's got some work to finish first). Note about the reason of reboot is displayed after restart.
    - workarounds for some motorola RIL issues that cause occasional data connectivity problems (by maniac103)
    - optional swap activation on boot via /system/etc/init.d/12swap
    -- requires swap partition present as third partition on sdcard
    -- swap size (in kB) is determined by persist.sys.swapsize property
    -- no persist.sys.swapsize property defined or set to 0 means no swap activation

    example how to set persist.sys.swapsize property in terminal:
    su
    setprop persist.sys.swapsize 16384

    9.1.0 (4.0.4) 05.12.2012
    notable recent fixes and features:
    - support for connecting to adhoc wifi
    - fixed wifi networking when using UPnP/DLNA apps
    - note that this build is done from the branch with removed theme engine,
    as the theme support seems to be too heavy, hurting performance of our device

    07.03.2012
    update-cm-9-20120307-SNAPSHOT-umts_sholes-signed.zip
    - video recording (not exactly smooth yet, but working nevertheless)
    - added missing sysctl to prevent RAM fragmentation (cause of gmaps freezes)
    - etc.

    03.03.2012:
    - camera is working (only taking pictures, not video recording; panorama mode is not working)
    - switched back to Calendar and LatinIME built from source (use the updated gapps-ics-4.0.3-20120302)
    - bootanimation is enabled by default, it can be disabled under performance settings
    - baseband selection is under device>advanced settings
    - usb and native wifi tethering is not working yet (but should be fixed soon, probably in the next build)

    14.01.2012:
    notes:
    - until the open source solution will be ready, Google builds of Calendar and CalendarProvider are installed via gapps to provide Google Calendar sync. Google build of LatinIME is included to provide access to downloadable dictionaries.
    - most of the gapps are installed to /data/vendor. if you are updating from earlier CM9 build, use "rm -r /system/*" in recovery console before installation to make sure you don't run out of space in /system because of previously installed gapps
    - bootanimation is disabled (debug.sf.nobootanimation=1 in build.prop), because the default bootanim takes more than 80MB of RAM while running, which may cause issues - from very long boot time to bootloops.
    33
    To let you know what's going on:
    CM10 (Jelly Bean) boots fine here. A lot has been already done and achieved, though there's also a lot of minor issues that will need more work.
    What's important - there doesn't seem to be any show stopper at this point.

    CM9/ICS is more or less dead from the moment of JB release, therefore I fully focus on bringing CM10 to omap3 / Milestone now.

    (Indeed, CM7 for Milestone will also get a significant update, hopefully sometime soon, when JB frenzy will cease a bit).
    30
    thanks for your explainations. i didnt know that we did not have full hw acceleration on our cm9 but its good to know. but may this new driver also fix the video encoding issue? if we would have full hw acceleration and could watch videos without any lags, that really would be awesome.

    Accelerated video encoding already works fine.
    It's the hw accelerated video decoding, and that is still a problem (on every omap3 device running ics). But I dare to say that it's really the last hard bit remaining to be solved.

    Anyway, the ICS for Milestone has reached a point I wouldn't dream about at all in the beginning.
    16
    Just to let you know: I plan to upload new build + new gapps package in a few days, stay tuned.
    And... thanks to those providing the intermediate builds for other users. I'm rather busy, so I appreciate your help.