GSM users have reported phone still FCs quite a bit. I have a solution for this but it's a work in progress and takes a long time to do (porting Motorola World Phone code to ICS from Gingerbread). I am sorry for the hassle, but usually a wipe cache/dalvik cache will reset your connection.
Mute button on calls doesn't work
Camera doesn't work
Codecs which reference the /dev/ion driver don't work (including audio only for Netflix)
For users experiencing high battery drain: goto "Settings" -> "Sounds" and uncheck "Touch sounds" and "Screen lock sound".
For GSM/WCDMA users who have lost 3G: enter *#*#4636#*#* into the dialer. Then goto "Phone Information". Near the bottom of that screen there's a drop down of network preference. For GSM-ONLY use GSM (PRL). Exit that screen and reboot the phone. Wipe cache/dalvik cache if you still don't get 3G back or have many phone FCs.
For GSM/WCDMA users who seem to boot up into an phone FC loop. Try removing "GlobalNWSwitch.apk" from /system/app folder. Is probably only useful for DualRadio models.
For a Gallery replacement use "QuickPic" from the market
QUICK REFERENCE "/system/build.prop" ITEMS OF NOTE FOR NON-VZW USERS
CHANGE THIS TO 3 for GSM(PRI), 4 for CDMA and 7 for GLOBAL PHONE
# Default network type.
# 7 => Global Phone (4 => CDMA).
ro.telephony.default_network=7
CHANGE THIS TO FALSE TO DISABLE THE DUAL MODE RADIO
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
ro.mot.FTR.33857=true
# END IKDROIDPRO-430
CHANGE THIS TO FALSE TO FORCE A SIM SETUP ON THE LOCKSCREEN
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim = true
# End Moto
Few days ago, I completely stripped out the dev/ion references from the camera code and was starting to work through a rewrite using our version of the memory tiler built into the kernel (read as TI memmgr1.0) Basically, that caused a little instability in the system which you can see in Alpha #4. Also, it hung the media_audio service out on the boot up which is why it's taking so long to boot currently.
Today, I reverted all of those changes, and instead built a ion_driver kernel module. The /dev/ion device is the new ICS interface for Android to work with the memory tiler at the kernel level. The module included an update to the tiler / dmm driver source as well (i named them tiler2 and tiler2_dmm) and all of the ion driver calls are directed to tiler2 instead of the original.
If loaded on system boot, tiler2_dmm.ko, and tiler2.ko modules load fine.
But, I'm working through some missing references on the ion_driver.ko module.
I'll know more in a day or so as I debug it, as to whether this technique will work.
Worst case is, I'll have to re-write the tiler2 portion as a wrapper of our existing tiler instead of a whole new device as it is now.
TL;DR: Camera needs the /dev/ion device (as does a few codecs) I'm working on a kernel module solution at the moment which has some bugs.
I am in Canada using Bell and I can't seem to add APNs as they won't save. I am currently using a verizon Droid 3 and I have tried switched the network to both WCDMA mode only as well as auto GSM. Any tips on what might be causing the problem?
ICS/CM9 users
i posted a video in my thread [first post] that shows Alpha3 running smoothly. I made the video because lots of users were saying many things didnt work in the ROM that did. It shows that paid&free apps, google music, gallery, quickpic, wifi,usb charging and everything but camera works. It seemed like some users needed a little proof to how it should be running. Well anyone is free to check it out =] Follow hashcodes instructions exactly and this is what youll get. Happy ROMing
I'm also GSM user and on ALPHA#2 GSM work great but in ALPHA 3 and 4 i dont have any possiblility to make a ph. call ( 3g and sms working) but when i try to call always got com.andoird.phone was stop
- i try to wipe all / format / edit build.prop / i changing many time in *#*#4636#*#*
You mean even when you set it to NOT unlock from slide in settings?
Because else I find this not an issue at all. In fact I bought widgetlocker just to have my phone unlock when I slide
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
[SELFKANG ICS AOSP ROM] CM9/ICS for Droid 3 -- [BETA 2012-03-11]
Print
Email
[SELFKANG ICS AOSP ROM] CM9/ICS for Droid 3 -- [BETA 2012-03-11]
View Profile
View Forum Posts
Follow on Twitter
View Facebook page
Linear Mode
