[ROM] CyanogenMod 9.1.0d (Android 4.0.4) [20130107]
- Thread starter kabaldan
- Start date
Love how smooth 9.1.0d is. It is now my daily driver.
One small issue if you have time Kabaldan. Beautiful widgets is unable to update weather on this build (says updating weather information and nothing ever loads). Also, on Lightning launcher, the clock for this widget just stops after deep sleep. Had to switch back to trebuchet.
One small issue if you have time Kabaldan. Beautiful widgets is unable to update weather on this build (says updating weather information and nothing ever loads). Also, on Lightning launcher, the clock for this widget just stops after deep sleep. Had to switch back to trebuchet.
Did the card test give back any sector errors/filesystem errors? If not, the other thing I would do is try with another card. It seems your card is damaged somehow. It can´t be system error, or sdcard filesystem error since you said you already re- flashed the rom to test it out (using hopefully both dalvik and cache wipes) and re-formated the card... Find another card to test (or buy one) and check it out. Also, does the problem appear on other CM versions? Does it appear on "official" android versions? Test that out also:good:
Last edited:
Thanks again but if it was damaged then it couldnt have been read through 2ndboot right? my pc can read the card when i go to storage mode form 2ndboot.
i will try with other card
My experience with 9.1.0d was rather pathetic.Although it was pretty fast it suffered with frequent Auto Reboots.Also the Phone apk crashed very often there by call issuing & attending and also using contacts were a problem.I tried several times wiping dalvik,cache & data and reinstalling the ROM including redownloading it afresh.But no success.The plus point of this ROM was a smooth camera and video recording. It was due to this good quality I came to this ROM and tried to hold on with this.But other parameters made me to go again to CM10 and there I deleted stock gallery apk and installed MIUI Camera and QuickPic.Now the video recording is flawless(even smoother than UCam) in 4.1.2.Also cm10-4.1.2 is more userfriendly and customizable than 9.1.0d in my experience.
pnsdhrn
Yep, in part it should indeed work... but it may be that 2ndboot uses sectors not used when fully booted into system. There is only enough you can do inside 2ndboot. If you have tried all tests I mencioned it should at least spit back some errors in testing. If not, it should be recognized in other roms for it not to be damaged. Did you uninstall/reinstall the phone drivers on the pc for a second time? It may also be drivers are flacky and work for the hardware detection part needed for the phone to be recognized in recovery mode but not in full "online" system/removable device mode. Just an idea though, not shure if it makes that diference. It might.
For all its worth, do test with another card (if you can) and report back, as I´m also curious for what is happening with it :good:
---------- Post added at 02:17 AM ---------- Previous post was at 02:04 AM ----------
Agree with scoutme. With the current kernel the rom is super stable (no random reboots since I can remember (probably since installing the latest CM9). There must be something on your phone contributing to the misbehaviour. You should try re-flashing cm9 after 10. Also, if I was having all those issues I would reflash stock android and then go back to cm9 to have a go at it... :good:
"also using contacts were a problem" Just out of curiosity, what problems did you experience relating contacts?
Last edited:
I try cm9 yesterday and found out that i can answer incoming call but all All the outgoing calls are terminate immediately.
sound familiar ?
sound familiar ?
Nobody tried that http://xdaforums.com/showthread.php?t=1987032.
For me is the best way to eliminate the lag on my Milestone, it's a wonderful app. Is there any contraindications?
Even with 600 Mhz my phone is fluid without any lag.:good:
For me is the best way to eliminate the lag on my Milestone, it's a wonderful app. Is there any contraindications?
Even with 600 Mhz my phone is fluid without any lag.:good:
This app removes lag because it forces the CPU to run at its highest clock all the time - so have fun draining your batteries even faster 
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
Hi, i had some time outside the forums, right now i'm running cm7.2.4b, with 12mb swap on /data, now i wonder whats the state of cm9/cm10, i also see more updates to cm9, how are they running right now? how do they compare to cm7 as daily driver?, i tried cm10 a couple of months ago and it was just unusable for daily use, i know i should try them and judge on my own, but since this is the only phone i own and my daily driver, because of my work i can't afford to be several hours without it... thanks in advance!
Thank you Ricfil.When I try to open People to select a contact for calling the People will not open and a message will appear instead saying "Contacts could not be opened".This occurs immediately after the crashing of phone program. However with CM10 I am quite happy now as it is supersmooth without any major problems and it is also more userfriendly and customizable than CM9 which I was using previously(of course the Nightlies prior to CM9.1.d).
pnsdhrn
CM9 works great for me, smooth and fluid with swap partition and another launcher (Lancher Pro in my case). Give it a shot.
Also, you do not need to take that long to transition from CM7. Just make a backup of your apps, flash CM9 and install the one´s you want on it.
It is that easy :good:
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
Glad CM10 works for you :good: Still, you had a problem not many have had as it seems. I don´t know if you did so, but it would be helpfull if you could post the logs of those crashes available to kabaldan (when those kind of problems appear), so he could have a go at it. Helps troubleshooting things, and increases the roms fluidity/stability in the longer run :good:
---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------
Kind of feeling the same at the moment. Still, some users report that using third party cameras and galery apps, the camera fluidity on CM10 improves a lot, and mencion overall performance is still on par with CM9 (fluidity wise)
Last edited:
Maybe CM10 is quite fluid but If you want it you have to make ext partition because of its size, camera app needs good procesor and RAM performance (familiar to Google Now). JB just doesn't fit for our old device, it is higher profile
.ICS is good compromise between GB and JB, and I really like it. I don't need Google Now and other gimmicks.
It doesnt mean that I don't want to see JB 4.2 on MM
, just for fun.Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
176Yes, 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 .143Main 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.33To 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
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.
