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

Search This thread

igna.worn

Senior Member
Dec 3, 2011
117
15
ApexLauncher Pro can't work as a "fix" for lost sms? It has an unread count on Calls, SMS and Gmail.

Well, you would have to pay it
 

mrvek

Senior Member
Feb 10, 2011
579
460
/home
ApexLauncher Pro can't work as a "fix" for lost sms? It has an unread count on Calls, SMS and Gmail.

Well, you would have to pay it

I guess if messaging app (and/or it's related service, if any, I don't know the inner workings of this process) does not receive a message properly I doubt some third party app (more of a widget feature?) will do the same. Perhaps some memory light replacement messaging app (if such exists)?
 

xd_1771

Senior Member
Feb 12, 2012
99
9
Is there anyone else here with wi-fi connection problems?
i.e skipping "obtaining IP address", going to "connecting", but doing nothing to connect

Only on some connections for me
 

vishalmullur

Senior Member
Feb 6, 2011
130
0
Is there anyone else here with wi-fi connection problems?
i.e skipping "obtaining IP address", going to "connecting", but doing nothing to connect

Only on some connections for me

It usually happens if you are entering wrong password. Check again. I had same issue and then came to know that it was because wrong password.
 

mrvek

Senior Member
Feb 10, 2011
579
460
/home
You are mistaken. The Nexus S is almost identical to the Galaxy S and has 512mb of ram.

Yes. Total. But he was referring to available ram. Milestone has 256mb physical ram but only 226mb available to kernel for "common" use.
Galaxy nexus has 1gb but ~700mb (don't remember correctly) is avail. to kernel.
 

adome5

Senior Member
Oct 22, 2011
275
7
hi
i have a problem
my friends say to me that they send to me a s.m.s messages and i dont see them on my device but on they device that see it...
how i can fix it?
 

n3n00

Senior Member
Dec 7, 2010
1,561
258
Split
hi
i have a problem
my friends say to me that they send to me a s.m.s messages and i dont see them on my device but on they device that see it...
how i can fix it?

Go back to CM7 and you will see messages. I told you five times already and you're not listening.

This device is too low on memory to run CM9 so it closes everything in background, do you understand?
 

_crAss_

Senior Member
Sep 19, 2009
336
52
Go back to CM7 and you will see messages. I told you five times already and you're not listening.

This device is too low on memory to run CM9 so it closes everything in background, do you understand?

Maybe it is not ram as kabaldan said, since it occurs to devices with larger ram as well. We have to wait and see.
 

dstruct2k

Senior Member
Jan 31, 2008
1,253
938
Winnipeg
Google Pixel 4
It's an over-aggressive Android memory management routine that's killing the SMS/MMS service (which then, eventually, restarts itself) and any messages that are delivered to the radio while the service isn't running are lost, as the radio has no "cache" to hold the messages until the service is available again to insert them into the database.

SMS/MMS delivery process:
Tower -> Radio chip -> Radio driver -> SMS service -> SMS database -> SMS app

The radio driver dumps any received SMS to the SMS service, but if the service isn't running at the time, the message gets lost. You can easily reproduce this issue on ANY ROM by loading an app that attempts to consume all device RAM. Android will keep killing background processes until it starts killing some services. I can cause the same issue to occur on the stock Telus ROM by trying to launch Draw Something (which runs) or another memory-hungry app.

It's not a bug in this (or any other) specific ROM, it's an issue with the Android memory management system that can be reproduced on any device (although it's much harder to reproduce on devices with more RAM) and any Android version.

/rant :)
 
  • Like
Reactions: mcpterra

mcdevtingz

Senior Member
Jan 19, 2011
800
66
Oxford, UK
I told my parents that my phone is not receiving messages and I need a new phone
Can't wait for my s3!

Sent from my Milestone using Tapatalk 2
 

igna.worn

Senior Member
Dec 3, 2011
117
15
It's an over-aggressive Android memory management routine that's killing the SMS/MMS service (which then, eventually, restarts itself) and any messages that are delivered to the radio while the service isn't running are lost, as the radio has no "cache" to hold the messages until the service is available again to insert them into the database.

SMS/MMS delivery process:
Tower -> Radio chip -> Radio driver -> SMS service -> SMS database -> SMS app

The radio driver dumps any received SMS to the SMS service, but if the service isn't running at the time, the message gets lost. You can easily reproduce this issue on ANY ROM by loading an app that attempts to consume all device RAM. Android will keep killing background processes until it starts killing some services. I can cause the same issue to occur on the stock Telus ROM by trying to launch Draw Something (which runs) or another memory-hungry app.

It's not a bug in this (or any other) specific ROM, it's an issue with the Android memory management system that can be reproduced on any device (although it's much harder to reproduce on devices with more RAM) and any Android version.

/rant :)

Soy we have to lock in memory SMS messages and that is it ?
Zeppelinrox supercharger script could work ?
 

zeppelinrox

Senior Member
Dec 21, 2010
9,374
21,590
IN THE FREAKIN' OP
The "BulletProof Apps" feature may work... it wouldn't hurt anyway :p
It will apply renice and apply ADJ priority of -17 every 30 seconds.

Haven't had reports of increased battery usage as it still goes to deep sleep without issue.
 
  • Like
Reactions: mcpterra

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.