Develop Bugs

[ROM][29July2013] mROM v4.0 JSS15J - stock 4.3 + GAPPS, MOD(s), etc.

Here is a 4.3 ROM built from AOSP source designed to emulate what a Verizon 4.3 ROM would be like. The changes from AOSP include the addition of GAPPS, addition of Verizon apps, appropriate binaries so everything works, addition of busybox, correct eri.xml, home screen layout to mimic a stock ROM, and the removal of the tethering restriction. The ROM is not pre-rooted, so flash Chainfire's SuperSU if you want root.
As usual, flash at your own risk and post any successes or problems.
Download Link(s) for v4.0: MD5: be4377ab16432112f09d18ae37c91041
DOWNLOAD via Goo.im
Cubby.com MIRROR
SuperSU v1.51 - you may want to check for a more recent version if this link becomes outdated. Flash after you flash the ROM.
Bugs - text-to-speech may not work correctly. Please flash fix attached to this post after flashing the ROM. Thanks AndroJak!
MODS:
Extended Power Menu - CM style
- Ability to reboot, hot reboot, reboot recovery, & reboot bootloader.
- Replaces /system/framework/android.policy.jar
- Thanks to Cyanogenmod and xIC-MACIx
- DOWLOAD
- MIRROR
Thanks to mmuzzy for help building from aosp (fixing t-cdma64 in eri.xml and cell broadcasts menu, plus other stuff I'm probably forgetting), adrynalyne, and djp952 for help building from AOSP.

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
about 5 min or so....
Click to expand...
Click to collapse
first cant wait!!! ^.^

Here we go!!!!!

Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.

Download for 1 server is ready now. I'll get a mirror up as well.
BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
Yes, it's working. I asked it how long a bridge was and it read the answer back to me. I haven't done much more than that though yet.

Downloading. Looking forward to this. Thanks Mwalt for sharing!!!
Quick DL as well. 2 minutes has got to be a new record for a JB rom

BrandT90 said:
Is Google Now working? I know mmuzzy was having issues on his AOSP ROM. Either way, I'll give 'er a test once the download links are available.
Click to expand...
Click to collapse
OP says Google Now is working. I'm downloading now.

excellent. you're a regular johnny on the spot!

downloading now, hope its all good! i'm looking for a "stock jb" style rom of the newest update. ill post my outcome shortly. going to test the basics that are supposed to work.

Is a flash to the JB bootloader recommended? Finally, a build that seems to have all/most components working! No issues with the 4G's or the LTE's?? Lol.
Galaxy Nexus - Slim ICS 4.2

Downloading now. Any thoughts on current JB kernel compatibility?

i wiped data, cache and dalvik cache 2x each, installed and installed trinity kernel on top and hit reboot. (i like trinity for the colors and such, and good battery life ).
first boot took a minute.
updating some apps and gonna test some things.
still getting t-cdma 64 as a carrier

mwalt2 said:
Here is a stock, rooted, busybox, etc. ROM built from the 4.1.1 AOSP source for Verizon. It has GAPPS included from the GSM developer preview and the Verizon apps as well (MyVerizon and the backup one). My attempt was to make a stock rooted ROM for Verizon based off of the 4.1.1 source on AOSP. Some things are still added to this rom from 4.0.4 IMM76K Verizon ROM, but I did include the new binaries for toro. I haven't fully tested everything, but camera, google now, gps, and wifi all work as expected. I'll try to get some add-on's / mods before too long and have them posted as flashable .zips.
As usual, flash at your own risk and post any successes or problems.
Download Link(s):
DOWNLOAD from Dev-Host
MD5: 8383b87cc2f9e5b510807c3034052ffe
Click to expand...
Click to collapse
Any issues in this build? Also, what are the install instructions?

when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?

^System/media/ringtones maybe?
Galaxy Nexus - Slim ICS 4.2

works well so far. thanks!

xweaponx said:
Downloading now. Any thoughts on current JB kernel compatibility?
Click to expand...
Click to collapse
I've always used stock, so I can't really comment. Now that source is out, I'd expect the JB kernels to work better.
imablackhat said:
still getting t-cdma 64 as a carrier
Click to expand...
Click to collapse
No sure what causes this, but I've never seen it with this build or the previous developer preview build. Did it happen on first boot before you installed anything else?
tycoon177 said:
Any issues in this build? Also, what are the install instructions?
Click to expand...
Click to collapse
I'd recommend a full factory reset, but people can try what they feel comfortable with. Personally, I did a factory reset, wiped both caches, and then flashed the ROM (with TWRP).
imablackhat said:
when going to sounds to set ringtones i have a lot of doubles of default ringtones, wonder where i can remove them?
Click to expand...
Click to collapse
Do you have any on your sdcard partition in the Ringtones folder? If not, I'd check \system\media\audio path (subfolders for ringtones, alarms, etc). Delete any duplicates you find in there. I don't have any duplicates and there aren't any in the rom.zip I uploaded.

just overwrote mms.apk in system/apps to get the custom pink mms, and got a quick reboot to my boot screen, this never happened on 4.1 roms that weren't source, don't know if this is normal because i replaced the app and it was a one time thing (i hope). as far as going to system/media/ringtones, i see them but there arent any doubles, however theres doubles when i go to select a ringtone from the menu, for everything system related, ringtones and notifications.

What issues have people had? Any boot issues?

I replaced the "stock" keypress ogg files from ics/jelly bean that sound better with this 4.1.1 release, the new key click sounds are horrible. works fine. i used to have t-cdma 64 with any build from 4.1.1 there is a fix that works that ill just apply. its a xml file or something.

[Guide] GSM To CDMA Rom Conversion

Extract the following files from a compatible CDMA Rom (meaning if your gsm rom is ICS,use files from a version of ICS that does exist on the CDMA side..Jellybean,etc)
Open the gsm rom you wish to convert in winrar and navigate to each folder listed below and drag the file listed into the folder listed. be sure to delete its counterpart example: sensors.primou.so will be deleted,sensors.primoc.so will be dragged into rom. when prompted by winrar for compression method,select store. and let it add the file to the rom.
in system/lib/hw copy:
sensors.primoc.so
in system/etc/permissions copy:
android.hardware.sensor.proximity
android.hardware.sensor.light
android.hardware.sensor.acceletometer
in system/bin copy:
sensorservice
now the above will take care of sensors that use auto rotate,etc..
now to fix mms/sms
sense based roms usually have a file in framwork-res.apk called apns.xml,its in the xml folder within framework-res.apk. Copy the file from any stock rom or cdma rom that has the proper apns.xml you need into the gsm based rom you want mms/sms to work in. I use winrar to open the framework-res and simply navigate to xml and drag the file in and select store as option for compression.
now the mms/sms fix will usually be a little different in slim,cyanogen,asop,aokp type roms..but sometimes it isnt. only way to know is check. if the apns.xml isnt in framework-res or if it is and it does not contain the appropriate settings,check system/etc in rom for a file called apns-conf.xml and replace it with one from any cdma rom that is available that matches your rom..example would be my slim conversion. i used the apns-conf.xml from aokp because slim gsm and aokp are both 4.1.2 roms. just drag it into rom with winrar using the store compression setting. sometimes,but not always you can use some of these files on roms not of the same type like for instance 4.2.2 roms MAY..may..work with some files from 4.1.2,etc..its a trial and error kind of thing. try them out and see how it boots.
edit build.prop and change default network type to 4 instead of 0(there are other changes you can make to build.prop but i cant tell whether or not they have any effect so i will skip those).
you may encounter roaming notifications in some roms you are trying to convert. i tried two miui roms that are 4.1.2 based and encountered the roaming icon in status bar even though i had working connections..couldnt figure out how to get rid of the roaming indicator. also of note,after getting the rom up and running you may see "evdo" listed as your connection in status bar. you are 3G,just that some roms call it evdo..just rename the 3G icons in systemui.apk to the names of the evdo ones and they will show as 3G again.
now for the boot.img. if you are using ics sense roms,jmz's boot.img will work,you can try out sick kernel for roms that use that on the cdma side or any other kernel on the cdma side that will match the rom you are trying to use. for instance..slim gsm to cdma uses the aokp kernel from the cdma side. be sure to add the system/lib/modules files to the rom and if the rom does not even have a modules directory,add it with appropriate files from your kernel. if you plan on sharing the newly converted rom with the public be sure to get proper permissions from all those you used source material from.
i know its not a perfect guide and rough around the edges but should get you running.

Do you think this will work the other way around?

MameTozhio said:
Do you think this will work the other way around?
Click to expand...
Click to collapse
Yes. Change the telephony line from 4 to 0 though.
Curtis, Roaming Indicator is Eri.xml in framework. Use it from a Cyanogenmod rom.

Curiousn00b said:
Yes. Change the telephony line from 4 to 0 though.
Curtis, Roaming Indicator is Eri.xml in framework. Use it from a Cyanogenmod rom.
Click to expand...
Click to collapse
Thanks! I knew about the telephony thing, but I was stuck on some other things aswell.

Curiousn00b said:
Yes. Change the telephony line from 4 to 0 though.
Curtis, Roaming Indicator is Eri.xml in framework. Use it from a Cyanogenmod rom.
Click to expand...
Click to collapse
i knew i was missing something. thanks bro

Curtis1973 said:
i knew i was missing something. thanks bro
Click to expand...
Click to collapse
What wouldn't be working that usually does?

Well,in the case of what new info CuriousNoob gave about the eri.xml it would either be a data disconnected issue with roaming turned on even though all changes for cdma network had been applied (minus the missing eri.xml) or data working but roaming still showing as being active.

Has anyone been able to successfully convert a gsm ROM to CDMA?
If so, I am going to start on the Miui ROM for my RAZR.

nu2droid said:
Has anyone been able to successfully convert a gsm ROM to CDMA?
If so, I am going to start on the Miui ROM for my RAZR.
Click to expand...
Click to collapse
i think so yes
PA2.9 was converted from GSM to CDMA AFAIK

I want to thank you for this guide. I've been noticing development for the cdma version of this phone has dropped off. But I'm noticing allot of roms for the gsm version. Gonna have to give this a try. Just something else phone related to piss the wife off.

lol dont pee her off to much... know where that leads... ye olde dog house!! lol. but back on topic...with some of the newer gsm roms,this guide will get you booted,mms,sms working but may need to consult with rom developer on getting your data service operating correctly even though you have properly set it in build.prop,it doesnt always work right..youll notice it being detected in rom ok but say disconnected. i need to revise this with a work around for those issues because the newer 4.1.2 gsm roms do not have module support..so even if you add the modules it just doesnt use them.

Curtis1973 said:
lol dont pee her off to much... know where that leads... ye olde dog house!! lol. but back on topic...with some of the newer gsm roms,this guide will get you booted,mms,sms working but may need to consult with rom developer on getting your data service operating correctly even though you have properly set it in build.prop,it doesnt always work right..youll notice it being detected in rom ok but say disconnected. i need to revise this with a work around for those issues because the newer 4.1.2 gsm roms do not have module support..so even if you add the modules it just doesnt use them.
Click to expand...
Click to collapse
They're in kernel ramdisk for HELLBOY. It depends on where the kernel looks for them (I think).

Is this porting tutorial specific to the one V or just general gsm to cdma? I want to see ifi can do it on a sprint One rom

In general, if you have two devices that are the same with one on gsm and one on cdma,it should work fine. Its just a matter of adding appropriate changes to the rom to suit your network and use appropriate boot method specific to your device. But as with anything I suspect there might be minor device specific differences that you will have to work out for your particular device.

In porting slim CDMA back to gsm, I noticed that i had no LED fit notifications. After checking in /system/lib/hw i noticed that lights.primoc.so was there. I replaced that file with lights.primou.so from the gsm ROM and, after a reboot, i had my light back.
FYI
sent from a phone that's running a rom

mrcorey said:
In porting slim CDMA back to gsm, I noticed that i had no LED fit notifications. After checking in /system/lib/hw i noticed that lights.primoc.so was there. I replaced that file with lights.primou.so from the gsm ROM and, after a reboot, i had my light back.
FYI
sent from a phone that's running a rom
Click to expand...
Click to collapse
I used to just rename them. I don't think that worked though xD

If you did that for your re-port, then it does work.
sent from a phone that's running a rom

mrcorey said:
If you did that for your re-port, then it does work.
sent from a phone that's running a rom
Click to expand...
Click to collapse
I think I just used the ones from CM but I don't remember.

I know it's not going to be the exact same procedure but is it possible that these steps could be used to port a custom rom from another HTC phone to work on the one v? They would both be cdma roms.

So I have spent some time looking around seeing if it was possible to put a phone from boost (GSM) onto the verizon nerwork (CDMA), and I keep seeing the same thing.
They all say "impossible" or something along those lines.
Yet, if I am understanding this correctly, by following these steps I could in fact do the impossible, and enable a phone to work on a Verizon-like network?
Just asking because I want to do this to either an S3 or an S4.
Sent from my DROID X2 using Tacotalk 2

Wifi Region code Connectivity problems: A Solution

Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk

arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later

atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.

arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.

atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.

arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.

atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of

arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess

atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL

arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone

atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.

Flashable zip added for new Commotio Rom Nightlies

Any chance to apply the patch to a stock rooted rom?
Thanks

Region Code
Hi can someone fix this file for region code?

nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.

Can someone post the patch for latest cm nightlies?

nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based

nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works

arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.

Android L

I was playing with some apps and files from Android L and I finished doing this lol I hope Enjoy it as much i do make this stuff
Thanks to CyanogenMod for the Base
if you want full experience enable On-screen Nav Bar
also for the new keyboard you have to go to Settings>Language & input>Google Keyboard then scroll all that way down till Advanced settings>Color Scheme and select Material
as always do a BACKUP and full format no your Internal Memory but you know that
NOTE: THIS IS NOT ANDROID L IS CM11 THAT LOOK LIKE ANDROID L
Download it from here

Nice. Can you specify in the thread title that this is not Android L?

This is pretty awesome. I love the look. Can I ask a favor? Would you mind doing the same thing to a newer version of CM11? I see the kernel is from June 8, is that the build you used as a base? In the official CM11 thread Shelnutt said that the data issue was fixed in newer nightlies. The issue is that for us 3G users we keep getting a FC for the phone UI. It happens when mobile data is on. It used to be able to be fixed by replacing the apn config file. I am going to try and I will let you know.
Thanks for the time you put into this.

Ill Try to do it as soon as i can =]
dopy25 said:
This is pretty awesome. I love the look. Can I ask a favor? Would you mind doing the same thing to a newer version of CM11? I see the kernel is from June 8, is that the build you used as a base? In the official CM11 thread Shelnutt said that the data issue was fixed in newer nightlies. The issue is that for us 3G users we keep getting a FC for the phone UI. It happens when mobile data is on. It used to be able to be fixed by replacing the apn config file. I am going to try and I will let you know.
Thanks for the time you put into this.
Click to expand...
Click to collapse
sure i can do that i choice this build because is the most stable lol i also just finished another rom called Xperia G which i love it lol but is base in the same build of CM but on that one you can flash the Apps over any Cm11 version i guess ill do the same with this ROM that way the people can use any base and just flash the APPs/UI over =]

Android 6.0 Marshmallow for jflte(Unofficial cm13)

After impatiently waiting for that day to arrive, here it is: Android 6.0 for our dear s4 is there thanks to our great dev @AntaresOne.
He brought us an unofficial cm13 for the unified s4 variants (jflte) which is stable enough to be used as a daily driver. All credits go to him.
Almost all the basic functions work.
FYI, it's a goodbye gift.
Download link: http://forum.xda-developers.com/showpost.php?p=63729768&postcount=312
Please, used the gapps suggested by the dev. Otherwise, you may face bootloop.
Enjoy but remember to thank @AntaresOne for this awesome work!

Reserved

Reserved...

I'm downloading it right now and going to give it a shot. Hopefully everything works out, including using streaming services like Netflix or Hulu Plus. Will report findings soon.

I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It's not implemented yet

Flash failed... Hmmm. Maybe corrupt data?

bbroad4455 said:
Flash failed... Hmmm. Maybe corrupt data?
Click to expand...
Click to collapse
It should work if the signature verification is skipped.
Also be sure that the downloaded file is correct; some of the mirrors do not yield the correct file andd have a different checksum.
The checksums should be:
Code:
cm-13.0-20151108-UNOFFICIAL-jflte.zip
Size: 297,677,777 bytes
CRC32: 919fb9b9
MD5: cfc714dda4be22afabdaa95e98f72bed
SHA-1: 97d993fccce699fdeb15bb1d39ad074220ce4a75
SHA-256: a3eff70e51b3c32f94808f9ade592d9cb9e1da07113773f2aa30d62503429295

Successfully flashed here. However internal and external mic don't work as well as auto time zones. Other than that, I haven't noticed an issue. I guess at first glance it also does not appear to be rooted.

Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.

This thing did not work for me, leaving the phone stuck at the Galaxy S4 screen at boot. Restored using Odin and stock image, my device is the M919V.

CM 13flashed
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.

pointdotslash said:
Everything works fine but microphone. It does not work at all; call, skype, hangout, voice recorder, etc.
Click to expand...
Click to collapse
It's a known issues in all cm13 built. No fix for it yet.

Is this ROM dead? or will it be updated to work with microphone fix?

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
It cannot. Since ICS, T-Mobile's WiFi Calling has depended on TouchWiz to work. Sadly, for the S4, TouchWiz is stuck on 4.4.4 KitKat and likely won't be moving up to Lollipop. As of now, I keep a working KK TW Rom backup up as a Nandroid in case I need it but I've since resigned myself to moving on.

Need something to fix 6.0
I downloaded the Android 6.0 marshmallow for tmobile and the 6.0 gapps i flash them with TWRP recovery on my galaxy s4 I cannot create an APN because it says my device model is unknown and sims card is not inserted what do I need to do to fix this or is it just a CM bug.

Same^ any help

i used these micro gapps http://opengapps.org/

madcow007 said:
I have read that cm13 will support tmobile wifi calling will it work with the s4 builds? Is it implemented in this build?
Click to expand...
Click to collapse
I think that a work around would be to call with hangouts... That's what I use to call over Wi-Fi
Sent from my SGH-M919 using Tapatalk

jfltetmo
vasolini said:
Trying this on my Metro PCS S4 (jfltetmo) since it's not my daily driver and not connected to their network. So far it seems to be stable, but the battery usage is not good at the moment. The top of the list shows "Uncounted" using the battery the most. Not sure what that means. I am willing to help with testing this rom for this model jfltetmo, so if you want any info from this phone, let me know what and how to get it, and I will gladly share.[/QUOTEiwould definatly interested in this that i have s4 with 5.1.1 rooted aicp rom w/twrp.
]
Click to expand...
Click to collapse