[CDMA/LTE][WIP][4.1.2] CDMA builds of Skrilax_CZ's CM10 - Motorola Photon Q 4G LTE

Well guys, it's been fun. It's been a real pleasure developing for you all. I know my build was never very good, but i hope that those who used my builds were able to enjoy a peek at Cyanogenmod for CDMA. Now that arrrghhh, Skrilax, and the rest of the Razrqcom dev team have gotten the camcorder in 10.1 working, it looks like my build had become redundant. Thanks so much to everybody who used or tested my builds. Special thanks goes to Arrrghhh for being such a big help to me when i was struggling with things, and to Skrilax for letting me use his code as a base!
CDMA builds of CM10
I'll continue maintaining and improving this build, as CM10.1 still does not have a working camcorder.
These builds are based on the work of Skrilax_CZ with modifications to enable CDMA, eHRPD, and LTE on Sprint's network.
Buglist in Second post, Changelog in Third
Additional thanks to arrrghhh and cmattern, who are helping to improve these builds beyond my limited skills.
I am no dev, i'm just a tinkerer, i'm just hoping my tinkering can benefit others who are itching for a taste of CM on these great phones of ours.
ROM
Builds from source: (These builds are based on source from the razrqcom team)
5/28 build with changes to proprietaries
Just set subscription type to NV and toggle airplane mode
Old builds have been moved to third post.
Source
https://github.com/solitarywarrior1
Got my build environment up and running, future builds will be built from source.
Anyone is welcome to suggest changes to my github, i'm still just learning this stuff so any tips are appreciated!
Instructions:
TWRP is recommended when flashing this ROM. I've had reports of it not flashing properly in OpenRecovery.
Wipe cache/data (recommended)
Flash ROM
Flash GAPPS from Skrilax_CZ's Thread located here:Skrilax_CZ's GSM CM10 Build
open phone and enter *#*#4636#*#* and ensure that mode is set to CDMA/LTE auto (prl)
go to settings>wireless and networks>more>mobile networks and set network mode to LTE/CDMA/EvDo and set CDMA Subscription to NV.
you may need to toggle radio or mobile data on/off after the above step
Enjoy!
NOTE: This is still a work in progress and may cause damage to your phone, damage to your relationship, or global thermoneuclear war. None of which am I responsible for. You have been warned!!!!
Thanks to:
HUGE credit goes to Skrilax_CZ, nadlabak (kabaldan on XDA), and the razrqcom-dev-team for the GSM port of CM10 and getting CM10 working on our phones.
Epinter for the CM10 port upon which Skrillax's is based.
Arrrghhh and interloper for the work they've done with Skrilax to get CDMA working up to this point.
Nwo122383 for his original modded build.prop that got CDMA calls working, it inspired me to start blundering about with the config files and gave me a place to start from.
Credit also has to go to the awesome CyanogenMod team for their awesome roms. As well as the teams responsible for the CM10 roms on the Samsung Galaxy S3 (d2spr) and HTC EVO 4G LTE (jewel) from who's roms my modifications come.
Additionally, we should all take a moment to recognize how awesome all of the developers are who build software for all of these phones and make the android community what it is.

What Works
CDMA calls work fine
CDMA 1xRTT, EvDo, and eHRPD data work
LTE works (toggle airplane mode if it doesn't connect)
4G signal bars
GPS Locks within 1 minute of turning GPS on
What Doesn't
Needing to toggle the subscription and mode settings to get data to connect
Data doesn't seem to want to stay connected (may be fixed, additional testing required) as of 4/15 source build
Earpiece whines during calls
My phone number, MIN, and PRL version show "unknown" most of the time | this doesn't appear to effect the ability to make/receive calls or use data or SMS
MMS
SMS longer than the single message limit don't appear to send. (May be fixed as of 4/17, can someone please confirm?)

Changelog
5/2 New build, Phantom VM fix (Thanks Arrrghhh!), New ERI from Toroplus, build.prop tidying
4/22 Moved links to all but the latest build to third post, cleaned up OP to make it more readable
4/17 Added tweaks to hopefully improve GPS and MultiPart SMS
4/15 Additional tweaks to build.prop
4/14: Added source-built unofficial CM10 built from Skrilax_CZ's source with modifications to make it play nice with Sprint's CDMA network
Mods are as follows:
/system/framework/framework-res.apk/res/xml/apns.xml
and
/system/framework/framework-res.apk/res/xml/eri.xml
replaced with the Galaxy S3 CM10 stable versions
Build.prop modded with bits and peices from the Galaxy S3 CM10 and Stock ASA-14 ones Ver. 2 adds lines from HTC Jewel (EVO LTE) CM10 as well.
/system/etc/apns-conf.xml replaced with the S3 CM10 one
/system/app/stk.apk removed
Old Builds
Modified GSM builds: (These builds are based on the nightlies from Skrilax_CZ, with some modifications to enable CDMA/LTE)
CDMA Modded CM10 4.12 Nightly Ver. 2
Builds from source: (These builds are built from Skrilax's source with the CDMA mods baked in)
My first source-built version
*Note* GPS seems to work, though not well. This build also has no LTE or eHRPD, but EvDo seems to work more reliably than the modded builds. Next build should have working eHRPD/LTE
Source-built CM10 with eHRPD and LTE 4/15
*Added Bonus: 4G signal bars appear to display correctly as of 4/15 build as well*
4/17 build with SMS tweaks
5/2 build with phantom VM fix

GPS works, only needs some time to booted, also don't forget that nadlabak (kabaldan on XDA) is also author of the CM10 port.

Skrilax_CZ said:
GPS works, only needs some time to booted, also don't forget that nadlabak (kabaldan on XDA) is also author of the CM10 port.
Click to expand...
Click to collapse
Ahhh ok.
And thanks, I don't want to miss anyone who deserves credit for this!

No, you didn't get it. nadlabak is also porting the CM10 to Photon Q with me, only he joined later ( = got his Photon Q later). CM10 port for Photon Q is based on epinter's CM10 port for RAZR HD.

Skrilax_CZ said:
No, you didn't get it. nadlabak is also porting the CM10 to Photon Q with me, only he joined later ( = got his Photon Q later). CM10 port for Photon Q is based on epinter's CM10 port for RAZR HD.
Click to expand...
Click to collapse
Oy my bad. Sorry! I'll fix it presently.
Fixed

GPS doesn't work for me no matter how long I wait after boot. I also have the high pitched whine in the earpiece during phone calls which may be considered a bug. Do the GSM guys have that too?
Sent from my XT897 using Tapatalk 2

No, GSM works fine.

Skrilax_CZ said:
No, GSM works fine.
Click to expand...
Click to collapse
another issue for my to-do list i suppose,then.

For NV at boot,you need to edit using sqlite editor. Open data/data/com.android.providers.settings/databases/ using root explorer. Copy settings.db and paste it at the same dir and it will be renamed to settings.copy.db automatically. Open the copy and click secure. Notice number 13 which is preffered_cdma_subscription. Open it and change the value to 1. Remove settings.db and rename settings.copy.db to settings.db. Reboot your phone. I need someone who are using CM10 to try this method first. I'm on stock ASA14 now. This method used to work on my Droid 4 to enable CDMA ruim.

For NV at boot,you need to edit using sqlite editor. Open data/data/com.android.providers.settings/databases/ using root explorer. Copy settings.db and paste it at the same dir and it will be renamed to settings.copy.db automatically. Open the copy and click secure. Notice number 13 which is preffered_cdma_subscription. Open it and change the value to 1. Remove settings.db and rename settings.copy.db to settings.db. Reboot your phone. I need someone who are using CM10 to try this method first. I'm on stock ASA14 now. This method used to work on my Droid 4 to enable CDMA ruim.
Click to expand...
Click to collapse
Hmm. Thanks for the tip!
I'll see if I can't figure out how to include it in the next build.
Sent from my Photon Q

Still can't run from/install apps to the SD card? Is this a limitation in the moto design or something?

matt2k12 said:
Still can't run from/install apps to the SD card? Is this a limitation in the moto design or something?
Click to expand...
Click to collapse
Is this bug unique to my builds or is it present in stock and/or the othe CM10 builds?

solitarywarrior1 said:
matt2k12 said:
Still can't run from/install apps to the SD card? Is this a limitation in the moto design or something?
Click to expand...
Click to collapse
Is this bug unique to my builds or is it present in stock and/or the othe CM10 builds?
Click to expand...
Click to collapse
This "bug" is present in CM10 from Skrilax_CZ and nadlabak, so not referred to this modded build.
Don't know of the RAZR HD (from which CM10 is coming from), but I think that this should be easily be done.
On the other side, some (me too) have problems with corrupted SD-Cards (I need to mount my card a few times),
this could be a problem if this feature is used. But everyone should know that, so not a stop for this feature.

Loader009 said:
This "bug" is present in CM10 from Skrilax_CZ and nadlabak, so not referred to this modded build.
Don't know of the RAZR HD (from which CM10 is coming from), but I think that this should be easily be done.
On the other side, some (me too) have problems with corrupted SD-Cards (I need to mount my card a few times),
this could be a problem if this feature is used. But everyone should know that, so not a stop for this feature.
Click to expand...
Click to collapse
Thanks for the clarification.
I'm a total n00b at this point, so i won't be doing much of adding features. Mostly i'm trying to figure out a config that gets CDMA/LTE working properly.
Any requests for new features or fixes related to bugs that are common to both CM10 builds should probably be directed to Skrilax_CZ in the GSM thread, as everything I do is based on his builds currently, and he has the skills to fix them.

Firstly, nice work. I've been running this for about 24 hours without any major issues. Runs really smooth and I'm happy we have a CDMA version.
I have two quick questions though. Has anyone seen 4G or is this an issue yet? Normally at work I have 4G and I haven't picked it up yet today. Secondly, my fiance sent me an mms and it will not download on 3G. Is this a known issue. I didn't see either as "not working." Do my APNs need adjusted?

Thanks!
I can confirm 4G working in the latest source-built build. 3G is much more stable as well. Same as before some toggling is required, but less than originally.
toggle subscription and radio on/off or mobile data on/off until system>about phone>status shows your phone number correctly and you should be good to go. I'll upload some screenshots when i get out of class today.
I have yet to test MMS though
Sent from my TF300T on CM10.1

solitarywarrior1 said:
Thanks!
I can confirm 4G working in the latest source-built build. 3G is much more stable as well. Same as before some toggling is required, but less than originally.
toggle subscription and radio on/off or mobile data on/off until system>about phone>status shows your phone number correctly and you should be good to go. I'll upload some screenshots when i get out of class today.
I have yet to test MMS though
Sent from my TF300T on CM10.1
Click to expand...
Click to collapse
I will check out your new source build! Thanks for the quick reply. I will let you know what i find.
Edit: I am running your source build. I can confirm that 4G is working on it. Though my phone number is saying unknown. Regardless of the number of times I toggle it. I'm still able to place calls so I'm assuming all is good haha

Any updates on GPS on this ROM? Non-functional GPS is a deal breaker for me, even on CM.
Sent from my XT897 using xda app-developers app

Related

[ROM][12.23.10] Jiminy V (for Cricket) - 100% EVO 3.70.651.1 **OBSOLETE**

****THIS ROM IS NOW OBSOLETE*****
****THIS ROM IS NOW OBSOLETE*****
****THIS ROM IS NOW OBSOLETE*****
Install your favorite Sense based rom (I still haven't gotten MMS working in AOSP despite all my attempts) on your EVO flashed for Cricket
Use the dialer to edit EPST settings and configure the MMS server information:
mmsc: http://mmsmycricket.com/servlets/mms
mms proxy: wap.mycricket.com
Remember to set your MMS size limit in the msging app to 500k (higher settings don't seem to go through)
Enjoy.
****THIS ROM IS NOW OBSOLETE*****
****THIS ROM IS NOW OBSOLETE*****
****THIS ROM IS NOW OBSOLETE*****
I proudly present Jiminy, it is an EVO rom meant for Cricket subscribers. I now consider it a 100% working solution for Cricket subscribers that have MMS issues with Sprint based roms. This is targeted more towards people with the $55 Android plan that has the Android data features activated on it. If you are on the $45 or less plan you likely need to use token419's solution (http://forum.xda-developers.com/showthread.php?t=730289) in addition to this rom to route data traffic through the cricket wap proxy.
The HTC MMS app is fully functional and already set to the 500k send size to work with Cricket. It can view all conversations properly. There is no need for a 3rd party MMS client.
Flashing this rom does NOT program your phone for Cricket, it is simply a rom optimized for full functionality on Cricket with none of the sprint crap you won't use. Your phone still must be reprogrammed either by a Cricket store with the Houdini software or by yourself (or someone who knows how) via QPST and CDMA workshop to have all the proper settings for putting the phone on the Cricket network. If your phone has not been reprogrammed for Cricket yet I would suggest using these instructions: http://www.howardforums.com/showthr...o-Flash-to-Cricket-with-Talk-Text-Wap-and-MMS
It might be a good idea to use a newer PRL than the one suggested in that guide (since it's old). I am attaching the most recent PRL I have to this post.
Rom is:
rooted
deodexed
busybox installed
data/app enabled
No Sprint bloatware
***************************************
Flash rom to device (a wipe is suggested) and then restore/import a working APN for Cricket (or maybe even MetroPCS).
Here are the contents of an APN.xml file that is known to work. Remember you MUST edit it with you own phone number, don't simply copy and paste it....
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="1">
<apn name="CDMA-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="your10digit#[email protected]" server="NA" password="cricket" proxy="wap.mycricket.com" port="8080" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://mms.mycricket.com/mycricket/mms.php" type="mms" />
</apns>
***********changelog***********
Jiminy v1 - like v2 but with too many bugs lol -no longer hosted
Jiminy v2 - deodexed OTA 3.28.651.1 rom for EVO and the 3.21.651.1 OTA for the Incredible. g3a8614e kernel. Removed all market available apps (facebook, google maps, etc) so that they can be installed from market and updated in the future.
http://www.massmirror.com/2b70dfedce096c317481f922e8fa350b.html
Jiminy v3 - I never distributed it but ran it for almost 2 months (3.29 base with 3.21 Inc bits) with the kingxklick BFS #9 kernel - had a grand ol' time.
Jiminy IV - 100% 3.30.651.3 EVO base. No more hybrid with Incredible. MMS.apk is modified to work properly now. Everything works 100%. HDMI and 4G control are full restored. All stock apps restored minus Sprint bloatware. Hopefully this does not cause a problem with voicemail notifications now? I use Google Voice for mine so it won't matter, but if you use the Cricket voicemail then you might want to keep an eye on this lol. But more importantly, why aren't you using google voice for your voicemail anyway? It's free and infinitely awesome.
*added keyboards
http://massmirror.com/4566f745375e8dd9beb7bfd6d9834a9d.html
Jiminy V - 100% 3.70.651.1 Evo based off of aamikam's reengineered stock rom that has all the apks rebuilt to be smaller and faster. I think I forgot to add the multitouch keyboard back in, but go snag yourself a Gingerbread one instead anyway (and of course the oem supplied Swype is in there as well). As always it is de-Sprinted as well.
If some apps stop working over 3g (youtube and pandora) then your proxy settings might have been returned to Sprint. Follow these instructions to set them back to working settings for Cricket:
Dial ##3282#
edit mode
enter 000000 ok
goto advanced
scroll to RTSP proxy address and HTTP PD proxy address and change them to 0.0.0.0
hit back twice and now try youtube it should work!
http://www.massmirror.com/5c47fa4e19c30e4a949242989b17acb9.html
******************************
I would like to thank snq- for the extra options in reboot power menu that I have added to this rom. http://forum.xda-developers.com/showthread.php?t=776495
A big thank you to token419 as well for getting my internet working before I moved over to the android plan with his great solution. http://forum.xda-developers.com/showthread.php?t=730289
major props to tritron777 who got the Sprint MMS.apk working properly with Cricket. http://forum.xda-developers.com/showthread.php?t=793588
Another big thanks to aamikam for thinking outside the box and pioneering the reengineered/optimized rom idea by trimming out all the fat! http://forum.xda-developers.com/showthread.php?t=878670&highlight=ReEngineered
Comments, suggestions, bug reports, and criticism welcome!
I am also adding a donate button here since it has been requested
-deathsled
Can you provide the settings manipulated to get internet/mms/gps working?
well i was gonna wait for you to grab post #2 before i posted but anyways no big deal. im gonna go and try this out right now
also wanna give us the run down as to what exactly was done with this rom?
akarol said:
Can you provide the settings manipulated to get internet/mms/gps working?
Click to expand...
Click to collapse
Internet and GPS simply work, no settings
MMS is set by importing an APN xml file as I already stated. Use APN Backup and Restore from the market to do this.
This rom assumes you have the Android cricket plan. If you are on the $45 plan you probably still need to use Token419's cricket flash for that u2nl tunneling through the wap stuff.
xTONEx said:
also wanna give us the run down as to what exactly was done with this rom?
Click to expand...
Click to collapse
Surprisingly little.
It turns out MMS.apk has a couple buddy apks in the /system/app folder. I haven't pinpointed exactly which ones are required and aren't. However, using pretty much the entire /system/app folder from the right Incredible rom in the right EVO rom seems to work pretty well.
Another key component to pulling it all together was to start the combination process using deodexed roms for the EVO and the Incredible as the source material. I tried with some odexed roms with no success. Deodexing removes some sort of device/framework related dependencies from what I understand.
It really wasn't too hard in the end, I can recreate the rom in just a few moments and will probably be able to do future ports in little time, but it took a LOT of trial and error to get to this point.
is it normal for it to kick back to 1x and auto make a slideshow?
ok was able to send myself a mms, but sent one to my girl and she hasnt gotten it yet. and ive been on 1x now for a few mins
xTONEx said:
is it normal for it to kick back to 1x and auto make a slideshow?
ok was able to send myself a mms, but sent one to my girl and she hasnt gotten it yet. and ive been on 1x now for a few mins
Click to expand...
Click to collapse
Slideshow is what you get for now, lol. When I send the "slideshow" to my other phone (iphone) it just shows up as 1 picture. So unless it bothers you to see "slideshows" on your end I really don't see what the issue is. A very minor quirk and may just be how the Incredible mms app works.
No idea about the 1x stuff. Doesn't happen to me. Have you updated your phone to the latest radios?
Also, make sure anyone you send to does not have a 1 in front of their 10 digit number. It (or Cricket) doesn't appear to like that.
deathsled said:
Slideshow is what you get for now, lol. When I send the "slideshow" to my other phone (iphone) it just shows up as 1 picture. So unless it bothers you to see "slideshows" on your end I really don't see what the issue is. A very minor quirk and may just be how the Incredible mms app works.
No idea about the 1x stuff. Doesn't happen to me. Have you updated your phone to the latest radios?
Also, make sure anyone you send to does not have a 1 in front of their 10 digit number. It (or Cricket) doesn't appear to like that.
Click to expand...
Click to collapse
i rebooted and 3g came back and doesnt kick back into 1x now when i send a mms. all seems well at this point!!! Congrats man hopefully the cricket mafia dont come knocking on your door lmao! u need a donation button too!!!
Nice. I'll pop this on my wife's EVO and post results. I spent a good half day till I got the MMS working properly on it, with the handcent/chompsms assist of course. I grabbed a Droid Incredible MMS.apk that's floating around somewhere here in the forums.
deathsled this rom rocks. I flashed it this morning here in Phoenix and it works great on Cricket. I can even get voice mail notifications without having to install voice mail notifier. I'm getting awesome 3g service, calls come through great and so far, no issues. Please get yourself setup for donations.
*** Update: found that Google Maps and Superuser won't update. Uninstalled both and re-installed with newer versions.
sillyputty said:
deathsled this rom rocks. I flashed it this morning here in Phoenix and it works great on Cricket. I can even get voice mail notifications without having to install voice mail notifier. I'm getting awesome 3g service, calls come through great and so far, no issues. Please get yourself setup for donations.
*** Update: found that Google Maps and Superuser won't update. Uninstalled both and re-installed with newer versions.
Click to expand...
Click to collapse
alot wont update...
That aside the rom runs great for me so far. havnt been able to really gauge its uptime but i will after a few days.
I noticed a couple things weren't updating on my phone as well.
It's not a huge deal, but I'd like to sort that out, so I'll hammer out this updating issue and pop out a V2 before long lol
deathsled said:
I noticed a couple things weren't updating on my phone as well.
It's not a huge deal, but I'd like to sort that out, so I'll hammer out this updating issue and pop out a V2 before long lol
Click to expand...
Click to collapse
i think its just because where they are getting installed to. other roms ive seen have had same issues
**ok it wasn't Apps2SD***
Ok so it looks like any preinstalld apps don't like to update. I'll make another revision with a couple more tweaks but also strip out any apps available in the market. That way they can all be installed manually and should be able to update properly in the future.
In the mean time if you just pull the stuff off the device manually that won't update and then reinstall from the market I think you're good to go.
updated original post with new v2 information and links
also, I no longer consider the no MMS while wifi is on the last 1% I'm missing. It turns out that Android disables the mobile data connection when wifi is turned on (at least for CDMA devices). This can obviously be defeated as seen by the wifi tethering apps, but basically would require some recoding of the MMS app. I'm sure future updates to Android will probably iron this little annoyance out.
good job man
i have been working on this myself but you beat me to it i am working on a port myself for cricket that will have the proxy settings built into it for the peeps that don't want the android plan. but congrats and appreciate the hard work
Thank You So Very Much
Thank you very much for all of your hard work!
I appreciate the Cricket love for the Evo.
Thanks to your ROM (which works FLAWLESSLY and FAST AS ALL GET OUT) I'm able to enjoy my EVO 1000x's more than I have before.
I see a PayPal donation coming your way in the near future..... ;-)
Whoa, you know it's legit kudos when you're getting it from these two. ^
add the fact that you can add the kingklick #9 kernel to this and unlock FPS AND overclock and this rom is great. again thanks for your contribution.
I wouldn't run King's BFS #9 kernel. I experience 100% CPU usage lag that was associated with that kernel. I'd stick with #8.

CM6 V6.1.0-RC2 2.6.32 Test Kernel

This is a test release with a new kernel 2.6.32 based from legend kernel source modified by cyanogen and attn1 to work on cm6. I am looking for reports on wifi and bluetooth mostly. Since this just replaces the kernel in 6.1.0 RC2. I don't want bug reports of issues already mentioned in the main 6.1.0 RC2. Please contain them to wifi and bluetooth. Overclock is included. I basically want to make sure your wifi runs good and the bluetooth works with your headsets/a2dp devices.
Thanks for testing
http://www.mediafire.com/?fbdrs3n6jv6d3d0
jznomoney said:
This is a test release with a new kernel 2.6.32 based from legend kernel source modified by cyanogen and attn1 to work on cm6. I am looking for reports on wifi and bluetooth mostly. Since this just replaces the kernel in 6.1.0 RC2. I don't want bug reports of issues already mentioned in the main 6.1.0 RC2. Please contain them to wifi and bluetooth. Overclock is included. I basically want to make sure your wifi runs good and the bluetooth works with your headsets/a2dp devices.
Thanks for testing
http://www.mediafire.com/?fbdrs3n6jv6d3d0
Click to expand...
Click to collapse
Changelog?
Is the included overclock already clocked higher or is it set at stock?
It would be great to have more info on this please! I may test it out once you can include more information.
The os itself is the same it's just a kernel change. Going from 2.6.29 in the other release to 2.6.32 in this test release. It's basically a subsystem change. You won't see any cosmetic change. I just want to make sure it doesn't cause any issues before attn1 and I add it to the next cm release. The only reason I mention OC is because this kernel still has it in it. So you will have the same OC features as the 2.6.29 kernel. Hope this helps explain what has changed.
Just curious if this .32 kernel will pave the way for FM radio support?
Wifi is working fine for me so far. I don't use any bluetooth devices, so haven't tested that.
Sent from my Liberty using XDA App
downloaded, haven't flashed it yet. There's still no nls_utf8.ko in /system/lib/modules. I know how to compile one, but I'll appreciate if you guys could make a small change in the config.
Code:
CONFIG_NLS_UTF8=m
That would save my trouble.
Wifi is working fine; tested both Wifi data connection and Wifi tethering (actually posting this using Wifi tethering). BT paired with Plantronics 520 headset is working and BT Voice Dialer was launched when I selected the headset button.
Do you just flash this?
Sent from my Liberty using XDA App
You install it the same way you install the cm6-rc2.
ladios said:
downloaded, haven't flashed it yet. There's still no nls_utf8.ko in /system/lib/modules. I know how to compile one, but I'll appreciate if you guys could make a small change in the config.
Code:
CONFIG_NLS_UTF8=m
That would save my trouble.
Click to expand...
Click to collapse
I made a kernel with your change. You'll still need to install the first package on this page before you install this kernel update. What is is for nls_utf8 used for anyways? Does this kernel update do what you need it to?
http://www.mediafire.com/?8c9pqhckurh7rlg
jznomoney said:
I made a kernel with your change. You'll still need to install the first package on this page before you install this kernel update. What is is for nls_utf8 used for anyways? Does this kernel update do what you need it to?
http://www.mediafire.com/?8c9pqhckurh7rlg
Click to expand...
Click to collapse
Thank you so much!!
nls_utf8 should always comes with cifs. With this module, we can mount cifs with "iocharset=utf8" option to access files that have special characters in their names. This is quite important for non-english users who use cifs.
WiFi seems be fine here. Bluetooth connects and working fine with Blue Eagle ll headset.
Sent from my Liberty using XDA App
Thanks for your input guys, if I could get some more it would be great. CM6.1 final will be out in the next couple of days so I'd like to get as much feedback as possible before then.
Bluetooth is connecting fine with my Nokia headset (BH-503). Wifi is working no different for me (aka, it works).
Tether working great for me don't know about Bluetooth don't ever use it but everything else is great!
Sent from my Liberty using XDA App
Wifi's fine. Cifs's working and it's good to have utf8 support.
Don't have any BT device to test on.
Wifi working for me. Just the kernel flashed over the latest nightly.
Downloaded this, ran it through it's paces as best I could. Connected two bluetooth devices (jabra and jawbone) worked without any glitches or weirdness. I also moved between several wifi spots WEP, WPA, and unsecured without issue.
Need any other info let me know.
I can also verify wifi working perfectly.
(no bluetooth devices to test that)
Only ROM in the CM series that works with my WIFI router (WPA-PSK). Had tired the most recent CM version and really liked the expanded dock along the bottom that allowed up to 5 icons to be placed there, but again, no wireless. Guess I'll stay with this one till Gingerbread comes out, Right...

Tanzanite is finally out!!! 2.0.2

Tanzanite is finally out!!!!!!!!!!
You can get it here
http://wiki.ccroms.net/tanzanite/releases/2.0.2
No 3g , no thanks
Sent from my DROID2 using Tapatalk
do we have to install gapps also?
Wow! No 3G, that's a deal breaker. It shouldn't even have been released.
Wow, as others have said, no data is a complete dealbreaker although I don't think this is meant to be used outside of an environment with a wifi connection anyway. Might flash it and give it a whirl.
Wow no data, camera, gps, or video. Sounds more like an alpha than a beta, still glad to see more apps released for the Droid 2 though so its a win lose situation
tried to download 1 app and it said there was not enough room
ok back to liberty
It still shocks me that people release these in this shape in non-beta format. (This one didn't say, but still).
Kinda like UD's limping "RC" release.
I know we all want new stuff for the D2, and fast, but it needs to work. What's the point of not data/3G on a smartphone?
Agreed,
I haven't released my swag squad rom for the droid2 because there is one more big feature I need and a few more bugs to sort out. Peope should release a rom unless it is practically finished already.
Tanzite will be good in another few weeks once they fix all the monster bugs.
Sent from my DROID2 using XDA App
There won't be any updates unless team phoenix gets it working, cvpcs has quit working on his gem roms and is now working on cyangogen
FYI...
"Important Notes
Because I know some of you young hipsters just want to get right to flashing and not read through all of the KNOWN BUGS (though you REALLY SHOULD), I've consolidated some important things to remember.
ON INSTALL YOU DO NOT NEED TO MOUNT SYSTEM MANUALLY - although it won't hurt, my install script automagickally does everything for you
FULL FACTORY RESET IS REQUIRED - blur-related data mixing with aosp is a no-no, so wipe data before you restart
THIS IS IN BETA - remember that. there WILL be bugs and i cannot guarantee that this will be ready for daily use yet. just keep your wits about you and enjoy.
USES KOUSH'S RECOVERY - this now uses koush's recovery, so bootstrapper and ROM Manager should work
DATA DOESN'T WORK - 3G/Data connections don't appear to be working yet, so you'll have to use Wifi if you use this. I will be releasing a partial update “fix” for this as soon as I can
I will keep this updated with any other questions people have.
License Agreement
The core of Android is released from AOSP under a combination of the Apache and GPLv2 licenses. Emerald is released under the GPLv2 license, which can be found below:
Tanzanite ROM - A custom Android OS built from AOSP
Copyright (C) 2010 Austen Dicken (CVPCS)
Known Issues
Video doesn't work
Video “sorta” works, but only on low-res and youtube videos, and even then it's choppy. progress has been made but more work needs to be done.
Pin-point GPS doesn't work
Network-based GPS works (fuzzy-gps) and is accurate to approximately 20 meters. However, pin-point gps or true gps is not currently functioning. It is being looked into.
Camera/Camcorder do not work
The Camera freezes and ultimately crashes if you attempt to take a photo with it. The camcorder will crash as soon as you turn it on. These are being looked into as well.
3G/Data do not work
For whatever reason the phone refuses to connect to the 3G/Data network. Phone calls appear to work, but not data. I will be looking into this and releasing a partial update fix in the future."
from the link the previous post....
there's no market.apk on there so you have to
have your droid 2 backed up from CW recovery
and have the droid2-bootstrap.apk on your phone
or else you're screwed and you have to SBF
Guys, Cobalt has this, with data working. It has the exact same stuff.
jaypatel32795 said:
there's no market.apk on there so you have to
have your droid 2 backed up from CW recovery
and have the droid2-bootstrap.apk on your phone
or else you're screwed and you have to SBF
Click to expand...
Click to collapse
Incorrect. You hold down power>reboot>reboot recovery.
Matt4542 said:
Incorrect. You hold down power>reboot>reboot recovery.
Click to expand...
Click to collapse
Thanks preciate it
No Joke no 3G = No dice.

[Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012)

DO NOT POST IN THIS THREAD UNTIL YOU HAVE COMPLETELY READ THIS POST AND THE FAQ.
Since jt1134 is no longer supporting his CM9 releases here on XDA and asking people to go elsewhere for support, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working. Even more goes to LinuxBozo - without his CM7 work we would be nowhere.
http://d-h.st/vN1 - 06/20/2012 build
http://d-h.st/ahW - 06/27/2012 build
http://d-h.st/Pfr - 07/28/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
Coming from any AOSP-based firmware with "blue CWM":
Flash this, flash gapps, wipe. That should be all you need.
What is working:
Calls
GPS
Sound
Video playback
What is partially working:
Camera (minor flakiness, but mostly working)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Wifi - It frequently loses connection when the device is asleep. Most likely needs some SDHCI driver tweaks to match the N7000 wifi driver.
Wifi Direct - A little glitchy but mostly working with I777/N7000. Won't talk to a P7510 (Tab 10.1) though.
Bluetooth - A2DP (music) and SCO (call audio) now works. However BT power management (LPM) is currently disabled, so BT may eat your battery when on.
Not working:
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Known issues:
SetCPU seems to be unable to set the minimum frequency to 100 MHz. This is one of the main reasons for holding off on OC - even stock clock code isn't working quite right
Facebook contact sync has been blocked by Google in ICS - this is universal to ICS on all devices I'm aware of. Facebook got what they deserved here.
Building - Use the Source, Luke
Kernel source is at: https://github.com/teamhacksung/android_kernel_samsung_dempsey
Device repo at: https://github.com/teamhacksung/android_device_samsung_infuse4g
To build, first prep your system for a Cyanogenmod build by following the instructions at:
http://wiki.cyanogenmod.com/wiki/Building_from_source
Once you have done the first "repo sync", at the two following lines to .repo/local_manifest.xml
Code:
<project path="device/samsung/infuse4g" name="teamhacksung/android_device_samsung_infuse4g" remote="github"/>
<project path="kernel/samsung/dempsey" name="teamhacksung/android_kernel_samsung_dempsey" remote="github" />
Run "repo sync" again
Sync https://github.com/TheMuppets/proprietary_vendor_samsung/ into vendor/samsung
Drop the contents of the attached tarball into vendor/samsung
(I really need to clean that process up...)
Run:
Code:
. build/envsetup.sh && brunch infuse4g
FAQ
Q: I get weird rainbows in recovery and when my device boots? What gives?
A: This is what happens when a Gingerbread or ICS kernel is booted on a device with Froyo bootloaders. You will need to either live with the rainbows (recovery is at least partially usable with the rainbows now) or flash Gingerbread bootloaders. Stay tuned for more info on bootloader flashing.
Unfortunately, the classic "rainbow fix" we used for Gingerbread is not compatible with how video acceleration is set up in ICS. The rainbowfix will just cause the device to crash immediately on boot. (I think this is why jt was not successful with LinuxBozo's CM7 source.)
Q: I'm getting rainbows, how do I flash Gingerbread bootloaders?
Flash the bootloaders from the file attached to this post using Heimdall as follows:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
DO NOT do this unless you are experiencing rainbows, and DO NOT do this until you have confirmed you can flash less dangerous stuff (like kernels) with Heimdall. If the flash fails you will hardbrick!
Thanks to LinuxBozo for confirming, way back in the days of UCKJ2, that Heimdall can safely flash bootloaders from leaks. http://forum.xda-developers.com/showthread.php?p=18539754#post18539754 - Be warned, once you do this step there is no going back. For whatever reason the Infuse won't flash dumped bootloaders, so there is no known way to return to Froyo and Rogers Gingerbread bootloaders.
Change Log
7/28/2012:
Removed 1000 MHz cpufreq step - the extra frequency step was causing all sorts of weird derpage.
Fixed 1200 MHz step (it was using the wrong PLL settings)
Moved to open source sensor HAL
7/22/2012:
Major improvements to camera flash functionality - torch is still broken but most other flash functions work
EXIF info (including rotation) is now saved. However I had to disable JPEG thumbnail generation, which slows down viewing of images in gallery
Structural changes to the repos to make things cleaner - Once two patches get merged by CM I plan on submitting Infuse for official nightlies
CPU clock handling for GPU bus frequency was changed from a policy change (min freq bumped to 200 MHz in policy, which would cause some apps to "stick" the min at 200) to a DVFS lock. Min no longer bumps up to 200 - however any time the GPU is active it'll still lock to 200 MHz.
6/27/2012:
Discovered our device has a Broadcom BT chipset - the CG2900 is NOT used for Bluetooth. BT is now fully functional other than possible power management issues
6/20/2012:
Various upstream stuff
Wifi Direct support added - partially glitchy (see OP)
Bluetooth support brought up to CM7 levels (Audio stuff is still broken)
5/27/2012:
New wifi driver from GT-N7000 Update3 source drop: Hopefully will improve wifi for those with issues
New LPM (charging while off) code from I9100
All upstream changes since last build, including lockscreen weather
5/19/2012:
Lots of upstream CM9 changes, including theme engine and customizable lockscreen
Settings->Advanced now works. mDNIE settings (tested) and HSPA+ control (untested)
A small patch that might help wifi driver loading issues, but not guaranteed (gokhanmoral reverted it within a day in his case...)
5/2/2012:
Pulled in a few wifi fixes from gokhanmoral's I9100 SiyahKernel tree. May help those who are having wifi issues.
4/23:
Fixed wifi MAC address getting set randomly on every boot
4/22:
Misc stuff from CM9 upstream
New wifi driver backported from the I9100 update4 sources and pershoot's Tab 10.1 kernel - Fixes wifi tethering!
USB tethering removed until I can make the RNDIS driver play with the new net/wireless code - not even sure if it was working to begin with.
4/19:
No more banding in recovery (thank codeworkx for this one, exact same fix as for I9100)
FFC is no longer cropped to one corner of the sensor. Full resolution support for FFC still not implemented
Various upstream changes
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Thanks for taking this on for all of us here in the xda community.
Sent from my MB865 using xda premium
The_Zodiac said:
Very nice any idea on how to get mtd to work? Also would that improve speed ? Thx
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I believe that was primarily used to eliminate the need for Samsung's proprietary RFS/FSR modules.
It doesn't carry a speed benefit, but it's beneficial in the long run for kernel developers.
Current differences between my build and jt's last:
1) I haven't put AriesParts in yet - half of the features don't work
2) Overclock is not in yet - The overclock code from netarchy/LB is ancient and needs to be reworked. Voltage control is in there though
3) Car dock audio redirection is working, using a built-in CM9 approach instead of a separate dock audio redirector app. I had to make some changes in libaudio of aries-common to fix this. Probably some more work needs to be done here - ringtones when docked are iffy.
Great work... blindly flashing now based on developer name.
Sounds great.. I just got jt1134's build 2 installed and working..
Looking forward to seeing what you put together for us. Always great stuff coming from you!!
Entropy512 said:
Since jt1134 is no longer supporting his CM9 releases here, I have decided to start building CM9 for the Infuse.
Much of the credit goes to him for doing the initial ICS bringup for Infuse, I'm working on fixing some of the things that are not yet working.
http://d-h.st/x53 - 4/15/2012 build
Installation instructions-from a Gingerbread firmware with "red CWM":
Place this release and an ICS gapps release on your SD card.
Flash this ZIP in CWM
Reboot - you will get stuck at the Samsung screen
Reboot to recovery again using the three-finger salute - hold down VolUp+VolDn+Power until the device reboots, release Power after the reboot, continue holding VolUp+VolDn
Go to Mounts and Storage and format: system, data, cache
Flash this ZIP a second time, then flash gapps
Reboot and enjoy
What is working:
Calls
GPS
Wifi
Sound
Camera
Video playback
What is partially working:
Camera (front camera is zoomed in excessively)
Car dock audio (possibly desk dock too, untested) - Some issues with ringtone playback when docked - This is native dock audio, not using the Car Dock Redirector app workaround. Thanks go to StevenHarperUK of the GT-I9100 community for reworking CM9's dock audio code to permit this to work.
Not working:
Wifi tethering - We need far more than the HIDDEN_SSID fix CM7 required unfortunately
Bluetooth - Not working at all, not even to CM7 levels
TV Output - No one has gotten MHL fully working on any Samsung device yet to my knowledge. There's some promising results from the I9100 community but it's not there yet.
Click to expand...
Click to collapse
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Frooty said:
Thanks for this! Did you fix/attempt to fix the problem with music coming out of the speaker when you get a notification with headphones plugged in? That's the only thing keeping me from loving ICS, since it's preventing me from listening to music at work.
Click to expand...
Click to collapse
Not yet... I'm just starting to mess with libaudio.
Awesome finally in the Dev section thanks Entropy!
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
Are you saying that he's not building any more releases, or that he just won't be releasing them here on XDA, but on rootzwiki instead. I'm confused.
Click to expand...
Click to collapse
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Entropy512 said:
I don't know what he's doing... All I know is he released his first build here but refuses to post any subsequent builds here, even though this is where all other Infuse development occurs. It's unreasonable to ask users to go to another forum just for ONE firmware, especially a forum with broken CSS stylesheets and a horrifically immature/irresponsible userbase. jt1134, imnuts, and Ezekeel are the only RW fans I've met that weren't complete douchebags and had technical skills to back up their bravado. Others think it's "kewl" to tell users to flash bootloaders all the time and then laugh at them if they hardbrick.
Not yet... I'm just starting to mess with libaudio.
Click to expand...
Click to collapse
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
bigjoe2675 said:
1st must you quote the entire op?
Yes and no...yes jt is still building...no he is not posting on XDA...jt prefer the rootzwiki site that's where he is posting....
Check or Hold??
Click to expand...
Click to collapse
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
He and I clearly also have differing opinions on how to go forward. My opinion - fix what's broke until you hit something insurmountable (like fully working Bluetooth on CM7).
Then add shiny destabilizing features like overclocking...
kirin0ichiban said:
Alright, well thanks for the quick reply. I didn't/don't know whats going on either. I'll just continue to monitor both threads and eventually things will become clearer on what he's doing. Great work on the ROM by the way! Keep it up.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
No need to be rude to mister Joe he was only trying to help!
I'm glad its finally on XDA makes it easier to know when an update is since I only check this site
Sent from my SGH-I997 using xda premium
kirin0ichiban said:
obviously I needed to quote the first OP, because that where my question originated from. And thanks for giving me the information that I was basing my question on, I know he's posting his builds on Rootzwiki, and has several threads opened up for his builds where everyone is saying something different about what he'll be doing with his releases.
Click to expand...
Click to collapse
Actually you didn't but YW for clearing up your confusions....
Runs beautifully as advertised!
I spoke with Entropy.. I would like everyone to take note:
Your phone is lying to you when it says you are on H+ all the time. That would kill your battery. It will jump to H and 3G all the time. CM9 does not display H+, only H.
I found Alarm Free (HD) does the same thing as Touchwiz Clock (Alarm, Stopwatch, and Countdown). I rely on Touchwiz clock at work for testing devices times and at home for timing punishments and waking up in the morning... I felt this was important to mention.

[CM11][Virgin Mobile US] MMS fix

Back in the CM7 days, a developer named Blarf (Blarfiejandro) started a repo called Inferior Human Organs for the optimus S/V (LG LS670 and VM670) when no-one could figure out how to get Virgin Mobile MMS working in CM.
His MMS patch to decode Virgin's weird system for MMS was eventually absorbed by CM even though they refused (and still refuse) to support the chipset these phones were based on. Without it, MMS comes in as one or more sms from a 9999999999 number full of gibberish.
I took the CM10.2 patch for this fix
https://github.com/CyanogenMod/andr...mmit/417458b50576a2438b0ed5771a2015b08659a32d
and updated it enough to work in CM11
CdmaInboundSmsHandler.java
I also had issues with CM11 not registering a default APN on boot until after the APNs editor was used to open/save the valid APN.
I tried all kinds of variations on the APN, and almost any of them would send and recieve MMS with the above patch, but only after the APN was triggered with the APNs editor.
I made another patch to trigger the default APN on boot, based on a combination of: the DcTracker fix to set homeOperator to ro.cdma.home.operator.numeric that was eventually absorbed by CM, and most of createAllApnList(), which runs the first time DcTracker executes. it's not pretty, but it works.
DcTracker.java This commit (and its parent. I goobered the push while my patch was missing a piece and didn't compress the commits together afterwards.)
I don't use Gerrit and just started ROM building this year, so these patches are floating around my github but not being pulled upstream.
Anyone who wants may fix and/or submit them upstream to get things working better for everyone. Maybe let me know if you do for politeness.
My contributions are totally FOSS code, though.
//edit: this has moved upstream into Team-Hydra android_frameworks_opt_telephony easy to add their repo to a build rather than use my patch.
mms fix for the 9999999999 error virgin mobile
bigsupersquid said:
Back in the CM7 days, a developer named Blarf (Blarfiejandro) started a repo called Inferior Human Organs for the optimus S/V (LG LS670 and VM670) when no-one could figure out how to get Virgin Mobile MMS working in CM.
His MMS patch to decode Virgin's weird system for MMS was eventually absorbed by CM even though they refused (and still refuse) to support the chipset these phones were based on. Without it, MMS comes in as one or more sms from a 9999999999 number full of gibberish.
I took the CM10.2 patch for this fix
https://github.com/CyanogenMod/andr...mmit/417458b50576a2438b0ed5771a2015b08659a32d
and updated it enough to work in CM11
CdmaInboundSmsHandler.java
I also had issues with CM11 not registering a default APN on boot until after the APNs editor was used to open/save the valid APN.
I tried all kinds of variations on the APN, and almost any of them would send and recieve MMS with the above patch, but only after the APN was triggered with the APNs editor.
I made another patch to trigger the default APN on boot, based on a combination of: the DcTracker fix to set homeOperator to ro.cdma.home.operator.numeric that was eventually absorbed by CM, and most of createAllApnList(), which runs the first time DcTracker executes. it's not pretty, but it works.
DcTracker.java This commit (and its parent. I goobered the push while my patch was missing a piece and didn't compress the commits together afterwards.)
I don't use Gerrit and just started ROM building this year, so these patches are floating around my github but not being pulled upstream.
Anyone who wants may fix and/or submit them upstream to get things working better for everyone. Maybe let me know if you do for politeness.
My contributions are totally FOSS code, though.
//edit: this has moved upstream into Team-Hydra android_frameworks_opt_telephony easy to add their repo to a build rather than use my patch.
Click to expand...
Click to collapse
sorry if this is a noob question but i've been getting this error on my galaxy s4 ever since i flashed it to virgin mobile. I can send mms picture texts but i can't receive. sending and receiving sms messages are no problem.
my question is how can i apply your patch to the S4's version of the cm11 nightly flashable zip? I have no idea how to compile java files. is there a guide you can point me to? I would really appreciate it.
bigsupersquid said:
Back in the CM7 days, a developer named Blarf (Blarfiejandro) started a repo called Inferior Human Organs for the optimus S/V (LG LS670 and VM670) when no-one could figure out how to get Virgin Mobile MMS working in CM.
His MMS patch to decode Virgin's weird system for MMS was eventually absorbed by CM even though they refused (and still refuse) to support the chipset these phones were based on. Without it, MMS comes in as one or more sms from a 9999999999 number full of gibberish.
I took the CM10.2 patch for this fix
https://github.com/CyanogenMod/andr...mmit/417458b50576a2438b0ed5771a2015b08659a32d
and updated it enough to work in CM11
CdmaInboundSmsHandler.java
I also had issues with CM11 not registering a default APN on boot until after the APNs editor was used to open/save the valid APN.
I tried all kinds of variations on the APN, and almost any of them would send and recieve MMS with the above patch, but only after the APN was triggered with the APNs editor.
I made another patch to trigger the default APN on boot, based on a combination of: the DcTracker fix to set homeOperator to ro.cdma.home.operator.numeric that was eventually absorbed by CM, and most of createAllApnList(), which runs the first time DcTracker executes. it's not pretty, but it works.
DcTracker.java This commit (and its parent. I goobered the push while my patch was missing a piece and didn't compress the commits together afterwards.)
I don't use Gerrit and just started ROM building this year, so these patches are floating around my github but not being pulled upstream.
Anyone who wants may fix and/or submit them upstream to get things working better for everyone. Maybe let me know if you do for politeness.
My contributions are totally FOSS code, though.
//edit: this has moved upstream into Team-Hydra android_frameworks_opt_telephony easy to add their repo to a build rather than use my patch.
Click to expand...
Click to collapse
Please comment on this patch by Dorian Snyder so that the MMS fix can be integrated: http://review.cyanogenmod.org/#/c/67788/
Merudo said:
Please comment on this patch by Dorian Snyder so that the MMS fix can be integrated: http://review.cyanogenmod.org/#/c/67788/
Click to expand...
Click to collapse
well, that's interesting. thanks for pointing that out!
they don't need my comments to move forward, though. I might leave one anyway.
Could someone test if the 999-999-9999 issue got resolved on the latest CM11 nightly?
I know a fix got merged but it's not clear if it works.
Merudo said:
Could someone test if the 999-999-9999 issue got resolved on the latest CM11 nightly?
I know a fix got merged but it's not clear if it works.
Click to expand...
Click to collapse
I can't tell.
The new fix looks good, but I can't use cm frameworks_opt_telephony because it breaks my mobile data (no mms without data.)

Categories

Resources