[SELFKANG ICS AOSP ROM] CM9/ICS for Droid 3 -- [BETA 2012-03-11]
- Thread starter Hashcode
- Start date
-
- Tags
- development
I missed 5/8, but 5/10 seems to be working pretty well for me so I'd say go for it.
Only things I've noticed not working right at the moment are:
- Camera (rear camera works fine for pictures, but trying to use either front camera, or video not only crashes the camera app, but also cause an inability to use the camera app again until rebooting the phone)
- Dialler app (this one's weird, works fine, but exits immediately after dialling a number, leaves the call running though so you can continue talking, you just have to find the call in the tray to get back in to control it)
- Haven't tried bluetooth at all, so can't comment on it.
EDIT: the dialer problem was in fact due to having the wrong SIM chip, once I upgraded to a V3 SIM the dialler problem was solved.
That said, I did try the bluetooth, and it's hopeless for my use. The phone can see other devices, but they can't see the phone, and enabling it stops your call audio from working (known issue)
Last edited:
That problem with the dialer is not a ROM problem. It is baseband problem. I bet you use a XT860 on TELUS in Canada with V1 or V2 SIM. Go get yourself a V3 (lte) SIM and problem will be gone.
Sent from my Galaxy Nexus using Tapatalk 2
I really like the latest build. Seems better on battery too. I am using XT860 with manual GSM adjustment, slightly less intrusive than Ricks patch which modifies build.prop in a sort of dirty way plus replaces framework.jar for some reason. I manually modified build.prop comparing the original XT860 one and the one from D3's CM9, it is only 5-6 lines that need to be added or changed. Also put libmoto_ril.so from the patch and all is good.
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
I would be interested to know what changes are needed. I tried doing the exact same thing and ended up with it either not working or constantly connecting and disconnecting
Sent from my XT860 using xda premium
There is def an issue with wifi and 4g data, my data will die and it simply will not work, until I turn off wifi, then it kicks right in, its happened exactly like that 3 times on the 4-8 build, nit big deal, but maybe something you can track down.
Sent from my XT894 using Tapatalk 2
Sent from my XT894 using Tapatalk 2
I'll assume this is a joke, and that you do realize this isn't the Themes forum... :screwy:
Sent from my XT862 using xda premium
Here are the changes I did to the 2012-05-10 nighty:
Code:
15,18c15,18
< ro.product.model=XT862
< ro.product.brand=verizon
< ro.product.name=solana_vzw
< ro.product.device=cdma_solana
---
> ro.product.model=XT860
> ro.product.brand=MOTO
> ro.product.name=solana
> ro.product.device=utms_solana
56,57c56,57
< # 7 => Global Phone (4 => CDMA).
< ro.telephony.default_network=7
---
> # 7 => Global Phone (3 => WCDMA).
> ro.telephony.default_network=3
164c164
< ro.telephony.gsm-routes-us-smsc = 1
---
> ro.telephony.gsm-routes-us-smsc = 0
180c180
< ro.mot.FTR.33857=true
---
> ro.mot.FTR.33857=false
192c192
< persist.radio.ap.phonetype=2
---
> persist.radio.ap.phonetype=1
194a195,205
> # BEGIN Motorola, IKCBS-1419 turn on 26911
> ro.mot.FTR.NSUI = true
> # END IKCBS-1419
>
> gsm.sim.mot.simswap=1
> ro.gsm.data_retry_config=default_randomization=2000,0:0,0:0,2000:0,4000:0,5000,60000,120000,180000,540000,960000
> umts.apn_authentication.enable=1
>
> ro.telephony.ignore.linkiperror=true
> ro.telephony.disable.globalnwswitch=true
>
255c266
< persist.ril.features=0x30E
---
> persist.ril.features=0x306
311c322
< ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
---
> ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/motoxt860/Profile/motoxt860.rdf< is what goes out and > is what replaces it. This patch can be followed to update future releases of the file (so versioning and everything else remains intact).
I am attaching the actual build.prop from May 10 build to the post too.
The other change I did is to upload libmoto_ril.so in /system/lib that I took from Rick's patch to /system/lib. Don't forget to set permissions properly for it:
Code:
chmod 644 /system/lib/libmoto_ril.soAside from signal indicator not displaying properly, I haven't seen other ill effects. Phone is running on Rogers Canada.
If you use XT860, yes. But it will be 2G only.
Sent from my DROID2 Global using Tapatalk 2
Yes, but it all depends how you define "4G" a little while back Canadian carriers decided to call anything more than 3G "4G", so what used to be called 3G+ (which is what these phones do) is now called "4G" even though it's not really the old 4G definition.
As for this build, really quite happy with it, though I am curious as to what the roadmap is going forward. What are the priorities as the next step? is it likely we'll see some of the big known issues addressed soon (like camera, codecs, and bluetooth)? or are those still pretty big hurdles to need tackle?
Last edited:
(Please feel free to correct me if I am wrong, I am NOT an expert.)
My understanding is that the reason these hurdles are not being dealt with is that we have gone just about as far as developers can go. These problems more or less exist across all Motorola phones running ICS.
There is a light at the end of the tunnel, if Motorola unlocks the bootloader (I wont really pretend to know what that means, just know its the problem) OR if Motorola releases a stock ICS phone, then we may see significant gains. For now, I dont think there is much hope at all.
That said, Hashcode has done a huge amount! Was not that long ago BT and camera didnt work at all, now we just have BT unreliability, and no camcorder. That is impressive progress when you consider he has a JOB and a FAMILY.
My understanding is that the reason these hurdles are not being dealt with is that we have gone just about as far as developers can go. These problems more or less exist across all Motorola phones running ICS.
There is a light at the end of the tunnel, if Motorola unlocks the bootloader (I wont really pretend to know what that means, just know its the problem) OR if Motorola releases a stock ICS phone, then we may see significant gains. For now, I dont think there is much hope at all.
That said, Hashcode has done a huge amount! Was not that long ago BT and camera didnt work at all, now we just have BT unreliability, and no camcorder. That is impressive progress when you consider he has a JOB and a FAMILY.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
51*** NEW BLOG SITE: http://blog.hash-of-codes.com ***
AUTOMATIC NIGHTLIES ARE HERE
GET GAPPS HERE (Choose "CyanogenMod 9.0.x" Link)
DON'T LET GOOGLE RESTORE YOUR SETTINGS WHEN INSTALLING THIS ROM COMING FROM GINGERBREAD
Changelogs:
Changelog at Blog.Hash-Of-Codes.com
Automatic STS-Dev-Team Development Log
What is NOT working in this build:
Need Better Camera: FFC, ICS features
No Camera Video
HW Video Codecs (in progress)
Bluetooth on but not connected = loss of all audio (in progress)
More Information:
NEW! http://blog.hash-of-codes.com
Or follow me on Twitter:
http://www.twitter.com/hashcode0f
GITHUB sources are now here:
https://github.com/organizations/STS-Dev-Team
Screenshots:
8KNOWN ISSUES (as of 2012-01-12 build):
- 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)
- Backlighting for keyboard and capacitive keys only works with "Auto Brightness" set: see here for custom settings http://xdaforums.com/showpost.php?p=22637417&postcount=957
- [NEEDS TESTING]Leaving Bluetooth on but not paired causes all audio to stop working on the phone. If you turn off Bluetooth then audio comes back.
- [NEEDS TESTING]Bluetooth in general needs an overhaul. It does work to make phone calls, but that's about it.
NICE LINKS TO HAVE
Nova Launcher: http://xdaforums.com/showthread.php?t=1389071
HANDY WORK AROUNDS:
- 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
FOR BACKLIGHT CUSTOM SETTINGS IN CM9: http://xdaforums.com/showpost.php?p=22637417&postcount=957
** AS A RULE, IF YOU'RE EXPERIENCING "ODDNESS" WHICH ISN'T MENTIONED ABOVE PLEASE WIPE DATA/CACHE/DALVIK CACHE AND TRY AGAIN5
In this case, I took the updated files from the official soak test (906) and pushed them up so that they are used in the D3 cm/aokp builds.
Jhiza has the right of it, sometimes you'll see minor improvements here and there. Will need some input as to how much of a difference the new binaries make.
NOTE: CM9 has added back in the theme system, and I merged that into last nights build as well. And updated the CM release tools -- flashing zips now tries to keep your gapps in place. So from the 5/7 build on, if you have gapps installed and don't need to update them, then don't re-flash gapps after flashing the rom.zip. THIS IS ONLY A CHANGE FOR CM9.
Sent from my Droid 3 using Tapatalk 2
