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

Search This thread

Protector1981

Member
Feb 7, 2011
31
1
Gives no Changelog. Its a Nightly-Build, means build every Day. And Nightly-Builds dont have not ever Changelog. You can look at github to look at the "changelog" ;)
 

kabaldan

Inactive Recognized Developer
Dec 15, 2009
1,640
3,926
Prague
android.doshaska.net
There is the source:
https://github.com/nadlabak (Milestone specific repos)
https://github.com/cyanogenmod (CM repos)
https://android.googlesource.com (AOSP repos)
(only the main three parts are listed, some repos may be pulled from custom forks, mainly tpruvot's for the wifi stuf)
If you're interested which part is pulled from where, check the project manifest: https://github.com/nadlabak/android/blob/ics/default.xml

There are the build instructions:
http://android.doshaska.net/cm9build

There are the builds resulting from the above:
No matter if it's built by Mrvek, me, someone else or the nightly buildbot setup by Skrilax_CZ (and powered by xvilka's server) [thanks!], the resulting build reflects the changes made to the source and is ready to be flashed.
Though beware that the nightly builds are automated and not human tested, so (in the worse case) the build may eventually not boot or be otherwise broken.

So to see what's changed, check the activity feed at https://github.com/nadlabak and the merged commits at http://review.cyanogenmod.com/#/q/status:merged,n,z
 
Last edited:

Abu3792

Senior Member
Dec 26, 2011
65
1
Three questions
1.I want to format my SD card and my phone is rooted, so after I format my SD card should I place that open recovery and update file again? And as I am formatting my sdcard I want to the best open recovery and update file ( if am not wrong I know there is another open recovery)


2. My power isn't working so how do I go to open recovery and switch on my phone?


3 . Would you recommend me to start from the scratch ie flashing sbf file and al those stuff?

Correct me if am wrong guys

Sent from my Milestone using Tapatalk
 
Last edited:

adistf

Senior Member
Jun 9, 2011
326
92
32
Craiova
www.facebook.com

adome5

Senior Member
Oct 22, 2011
275
7
sorry for offtopic,but i found this: "The name of the tagged release is android-4.1.1_r1 and the name of the development branch is jb-dev. The binaries are currently being released for the Nexus 7 and the Galaxy Nexus but will be released for the Nexus S and the Motorola Xoom shortly."

http://www.gsmarena.com/google_releases_android_41_source_code_to_aosp-news-4496.php

now,its realased!
i hope that kabdlan will be working on it.
wish for it and i wait for updates from him.
its possible you thinks?
thank of all ,you the best!
 

GreenRaccoon

Senior Member
Apr 20, 2011
63
18
Austin, TX
3 . Would you recommend me to start from the scratch ie flashing sbf file and al those stuff?

Yes. I always sbf and re-root before I flash a new ROM. People have reported that, for some reason, this seems to fix and/or prevent some weird bugs. I used to have a couple bugs that persisted across different ROM's, but now that I always sbf before flashing a new ROM, I don't get them anymore. Also, I heard that if you DON'T choose "Backup my data with my Google account," that seems to prevent some bugs too.

I'm not sure why these work; :confused: I just know they work for me.

By the way, if you ever have a problem sbf-ing, try moving the .sbf file to "C:\". That seems to fix a lot of sbf-ing problems. I don't know why that works either, but I'm guessing it might have something to do with putting the file under administrator privileges.
 

Abu3792

Senior Member
Dec 26, 2011
65
1
Yes. I always sbf and re-root before I flash a new ROM. People have reported that, for some reason, this seems to fix and/or prevent some weird bugs. I used to have a couple bugs that persisted across different ROM's, but now that I always sbf before flashing a new ROM, I don't get them anymore. Also, I heard that if you DON'T choose "Backup my data with my Google account," that seems to prevent some bugs too.

I'm not sure why these work; :confused: I just know they work for me.

By the way, if you ever have a problem sbf-ing, try moving the .sbf file to "C:\". That seems to fix a lot of sbf-ing problems. I don't know why that works either, but I'm guessing it might have something to do with putting the file under administrator privileges.

Thanks man! What about the first question as am formatting the sdcard? And my power button isn't working so how do I get to the boot loader and recovery mode without the use of power button ... guys help

Sent from my Milestone using Tapatalk
 

scoutme

Senior Member
Jul 3, 2010
171
25
Thanks man! What about the first question as am formatting the sdcard? And my power button isn't working so how do I get to the boot loader and recovery mode without the use of power button ... guys help

Sent from my Milestone using Tapatalk

Are you talking about CAMERA button, aren't you?

Sent from my Milestone using xda app-developers app
 

Eiertschik

Senior Member
Mar 28, 2011
399
67
Google Nexus 4
Google Nexus 5
[...]
its possible you thinks?
[...]

images
 

Abu3792

Senior Member
Dec 26, 2011
65
1
Please help me guys with the power button issue that I've had for months now I want flash a new Tom from the scratch but I don't know how to get to boot loader and open recovery

Sent from my Milestone using Tapatalk
 

shalom06

Senior Member
Feb 25, 2011
477
140
Mumbai
Please help me guys with the power button issue that I've had for months now I want flash a new Tom from the scratch but I don't know how to get to boot loader and open recovery

Sent from my Milestone using Tapatalk
Go to Terminal Type su. Then Reboot .Then while rebooting Press x


Sent from my Milestone using xda premium
 

pnsdhrn

Senior Member
Nov 19, 2010
2,777
373
Samsung Galaxy Z Fold2
Last edited:

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.