[FIX]AT&T Carrier Billing for 4.3 ROMS - One (M7) General

thought this may help more if i post it in general instead of the ARHD thread. Thanks to Garmig for his original post i found with the additions to the build.prop for 4.1 or 4.2 roms, cant quite remember
Tested this on ARHD (4.3) and Trickdroid (4.3), but i imagine it will work on all 4.3 ROMS
okay so after a little playing around i managed to figure out which build.prop lines to add to enable carrier billing on google play market for AT&T users so that it actually works without breaking mms.
originally i found a post by user Garmig which showed these additions:
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-att-us
after applying those additions to the arhd build.prop it enabled carrier billing for att successfully, but somehow breaks mms? not sure how but it did
so i played with the lines independently and figured out that if you add only these lines:
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-att-us
it will successfully enable att carrier billing without breaking mms. maybe someone more experienced can answer why one of the two last lines woud break mms, but either way, maybe some of the other att users using arhd 20.1 will find this useful, and garmigs original post that i found
Best to use Root Explorer or a similar app to make the changes, be sure to make a nandroid before messing with the build.prop or you may jack your phone up

Related

[MOD] MMS Not working for you? Heres a fix!

Hello!, I've personally seen people struggle on these forums having a MMS Related issues, and i can honestly say more or less its not as much the rom, but more of the Files in it in general for your APN (access point names) and i know some of you already made this method by your experience, but i have still gotten requests for "how the h**l did you fix your MMS!?!?!!!!!! (enter any CDMA carrier name here) hasn't worked for me since android ICS! (Android 4.0.* )!!" Well i can honestly say its not as much as the MMS.apk (default Android SMS/MMS messenger), as much as it is the apns-conf.xml file in the /system/etc directory! i know this post may seem stupid to some higher-up knowledgeable people, but there's too many common-day users who have this issue and i'm getting frustrated as i'm trying to make better roms/apps and being distracted with hangouts messages/emails/PM's and even somehow random Facebook messages, that i'm just going to release my flashable zip that i use for my rom, and implemented to my future rom zips as an overlay, but for those with Constant MMS Related issues the main problem is that Cyanogenmod has the apns-conf.xml in single string notations (all in one line), while on some and or most APNs needed for carriers are needed to be separate lines for data/mms/tethering and so forth, so for the basic ones that i know this device (Samsung Fascinate) is usable with: (Straight talk, Verizon, Metro PCs, even Sprint / T-Mobile / and AT+T if you have you rom spoofed as GSM using a modified Voicemail Notification GSM Spoofing Exploit from the GEEWiz Rom's Github+some of my own ides mixed into it), and integrated the right codes into the rom+build.prop, as the radio still makes it read as w/e as I've tested using ESN/MEID tricks in-rom codes to test carrier signals (unreleased as its unstable, but i used a homemade Debugging method in the build.prop entries for carrier codes, and signal modifiers so ti can be done if you build from-source) but anyways here's a MMS Fix for the common CDMA Carriers this device is known to use in one flash-able zip (No MMS.apk included so it can be used with ANY Android version, but if it is MMS.apk's issues you wont have any MMS so you can test using this zip BEFORE complaining to the rom developer) Should work on ANY CMDA device, but i more focused on this one, but has proven to work on Samsung Galaxy S3 Running Verizon ( friends device on STOCK Rom (with custom recovery tho) having MMS Issues)
***Credits to Slim-Rom Developers At Least as i used their apns-conf.xml as a base with minor modifications***
Download:
http://www.androidfilehost.com/?fid=23329332407589477
(if Error 404 file not found in the future since this posting, it is because it hasn't been downloaded within Android-File-Host's Required since-last-download time restrictions from their Terms-of-Services)

[PLEASE HELP] MMS Issues on JFLTEVZW KK RC-3 dev

This seems to be an issue on any CM-based ROM I use, but I really like PAC and the features it has so this is especially troubling to me.
I am on a VZW Galaxy S4 (SCH-I545, I545VRUAMDK baseband) with TWRP recovery, ktoonsez kernel 3.4.104.
Every time I install a CM-based ROM I cannot ever send or receive MMS messages through Hangouts, or any other messaging app.
When I look at Mobile Network Settings and check Access Point Names from within the system settings menu, I see Verizon APN info. The one I have enabled currently is the default VZWINTERNET one.
However, when I go into Hangouts and check my APN info there, I see APN entries for Sprint and MetroPCS. I cannot change any of them, I cannot add any of my own, I cannot manually input Verizon APN info, because they don't ever save. I can delete them all and render my phone unable to send or receive anything, but recover them by restoring default.
It's because of that fact that I believe that this is due to the ROM itself.
I first noticed this a year ago when I was using CM 10 and 11 release candidates, after CM switched to unified builds instead of carrier-specific ones. Since then I've flashed other ROMs like Dirty Unicorns and the like, and the ones that are based off the CM Unified builds always carry the Sprint/MetroPCS APNs in Hangouts.
This prevents me from ever sending or receiving MMS messages from anyone regardless of carrier of origin.
I've tried apps and tweaks to resolve this, but nothing works. The only thing that ever does is switching to a non-CM core ROM, but I like the feature-rich PAC-ROM the most.
Does anyone know of a definitive way of resolving this issue? A hack? A manual change to the system files?
I tried running a search of XDA, as well as good old fashioned Google, but all I can ever find are blog posts with suggestions and "definite" fixes that never work.
At this point I am a little desperate for help. Every time I've posted a help thread, be it here, the S4 official subforum on XDA, or Reddit, or the PAC forums, I get nothing, not a single reply.
I cannot be the only one who has been experiencing this.
Please advise.
Thank you,
I am experiencing this too, and APN settings dont seem to help.

build.prop optimization

Hey guys,
Between the attached build.prop file & an app titled Memory Locker, my multi-tasking experience has never been smoother.
So I figured I would share & get a larger discussion going. Some of my values are popular Android tweaks. Others are taken from the CM12 ROM in the development section. Others were experimental or hunch-based. Before anyone asks, dalvik.vm.heapminfree=512m was supposed to read dalvik.vm.heapminfree=512k, but 512m works great & a switch back to 512k slowed my boot time.
I am running a rooted KitKat stock rom, but I presume that most of these values would work for Lollipop as well. I would be curious to see the stock build.prop post Lollipop update.
Disclaimer: don't mistake me for being a genius who understands what all this stuff does exactly.
mine says dalvik.vm.heapminfree=2m do you know anymore tips on how to make my Z3TC smoother please share thanks

Rom wth User Profile built in

Is there a ROM for the retail verizon version that has built in Profiles.?I've been away from my S5 for awhile so I haven't been following ROM development for about 6 months.. But now I want to add a 2nd user. I'm currently doing that with the Xposed multiuser module. But I'd like to update my ROM and find one if I can with profiles baked in. I've done some (lots of) searching, but have only found CM11 but as near as I can tell it can't be installed on the Verizon variant because of the locked boot loader. I don't need a lot of info just the name of any ROM's that I can then research myself.
No one is using/tried a rom with multi-user profiles on this device or is there not one?
Thanks for any help with this.
MOAR!!!!
Thanks, I'll check it out.

Will there be a fully functional MM 6.0.1 Rom for the Note 3 with Verizon Sim?

So, I have tried Darkwolf and had problems with it. I couldnt change my APN settings, couldnt get ES File Explorer working, ect. I am feeling really discouraged.
We have had unlocked boot-loaders for a little while now, but is it just too late for this device?
I got darklord 3.3 working. Had to make some edits to the buld prop file and copy over the apps conf file but in the end was mostly worth it. Some small camera issues but think it's hardware.
Sent from my SM-N900V using XDA-Developers mobile app
I'm running Aryamod, with VERY few tweaks! It doesn't come with a kernel, so I nabbed the Darkera kernel from the DarkLord ROM page. It comes with Pico GApps preloaded, so it's easy to add to or strip out the Google Apps with TiBU. (I'm running MicroG, with official Play Store apk, myself.)
If you care to give it a try, choose the Sprint version in the Aroma installer and flash your kernel before rebooting. After you've got it running, use the "ROM Control" app to add your APNs (under Phone Mods>Advanced Function Menu>Phone APN Setup) and tweak your smsc number (under Phone Mods>Advanced Function Menu>Device Network Info and Settings>Device Information).
The only downside is that the stock (Samsung) Messages app doesn't send correctly, so I've substituted GoSMS (with the manual APN settings tweaked). Admittedly, it helps to have another phone handy, to test SMS/MMS sending/receiving. I haven't had any of the problems others have had with the "sent message failed", after these tweaks, so I'm certainly impressed. It's good to have some of the neat features the S7 and Note 5 do, WITHOUT sacrificing a stable ROM! ?
Edit: As previously mentioned, not all camera features work (hardware limitations) and NFC isn't working (nobody can, or is willing to, figure out the VZW NFC hardware). However, Bluetooth is working flawlessly, whereas some have had complaints with call audio, in other ROMs.
Sent from my SM-G935F using Tapatalk

Categories

Resources