Related
I remember there was an app in the CM 4.2 for transferring file via Bluetooth but I don't see that app in CM 5.0.7 anymore so my question is how to receive files via bluetooth because I can sent them just fine but I'm not able to receive anything
What happens when you try to receive a file? I did not take a plunge into Eclair yet but AFAIK bluetooth file sharing is built into settings and should work. Otherwise, you can (most likely) rip that apk from older CM and install on your current rom.
when I try to send a file to my phone nothing happens ,I don't get notification or anything and I don't see an option so I can't set on receive file,
As I said.. I did not take a plunge yet so I can't quite test it out but here's the APK from an older rom. See if that helps you.
For those interested I have flashed Omega v3.1 for i9505 on my Sprint SPH-L720
By no means am I recommending flashing this on Sprint.
I am just relaying my experience YMMV
The latest version of Omega for i9505 GS4 can be found here
http://forum.xda-developers.com/showthread.php?t=2253528
Before I flashed Omega I was already on MDL update and I replaced the following files in the Omega zip:
boot.img in "indie\" with a boot.img from one of the custom MDL kernels available for SPH-L720.
"system\lib\modules" with Stock MDL "system\lib\modules" then copied over "system\lib\modules" from the chosen custom MDL SPH-L720 kernel. (This was to first replace with stock modules then replace with custom kernel modules to account for overlap)
"system\build.prop" and "system\kern_sec_info" with those files from your chosen MDL ROM or stock MDL ROM.
I am not sure exactly what any of these modifications did to make Omega boot on a SPH-L720. It just seemed like the logical thing to do.
If you look in the updater-script the install also backs up the efs partition fyi. Remove from updater-script if desired.
Some of the aforementioned modifications may not be necessary.
Initially after booting, Mobile data did not seem to work, but after a reboot and about 10mins 3G started working.
Still no 4G yet. I will update if I get 4G active.
Please Assist if you can
In "Settings->Connections->More Networks->Mobile Networks" there is an option for "Connections optimizer"
This is not available in stock settings.
There is also no longer the "Smart Mode" in Wifi settings.
I have blindly tried replacing the settings.jar in "system/framework" with stock then booted into recovery and wiped cache and dalvik then rebooted and settings are still the same.
If anyone wants to check this out or provide any feedback it would be greatly appreciated.
Edit: 6/1/2013
I have been messing around with this all day replacing various files with ones from stock MDL and still can only get 3G data working.
Initially after flashing if you look in "About Device -> Status" the phone is connected to the LTE band but data will not connect. After about 10 mins 3G connects and 4G will not reconnect.
If anyone can get 4G working on this please share what you did to get it working.
There is an easier way...
http://forum.xda-developers.com/showthread.php?t=2295557
if you are connected to LTE but status bar shows 3g look at the systemui and see if you have the lte pngs.
I was able to flash v19 omega rom i9505 version without any need of a kernel. Phone numbers work if I push 1 before I dial area code, recieving calls is no problem.
Data/MMS don't work. I have noticed that I don't have the option of changing APN's, but there are 3rd party apps on play store that do allow you to input APN's. I'm about to reflash cm10.2, and backup the APN's to sdcard, then flash v20 on (after it's done downloading), and see if I can restore the APN's that way.
Interested in the result
Sent from my SPH-L720 using XDA Premium 4 mobile app
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This is the latest KitKat 4.4.2 Rom from T-mobile. I ported it to ATT and tried to apply just enough modification to keep all the functionality and remove all the limitations. Nothing has been removed from the rom. The disabled apps are kept to a very minimum so this is NOT a de-bloated ROM. This is as close to stock as it gets. If you need a debloated version go here: http://forum.xda-developers.com/att-galaxy-s5/development/rom-debloated-bnh5-ported-tmobile-t2901620
1- Pre-rooted and deodexed.
2- Knox, security apps, and updater disabled (your phone will no longer update itself without your knowledge)
3- Call recording enabled.
4- SDcard write restrictions removed.
5- Tethering restrictions removed.
6- Download Bosoter functional on AT&T network.
7- Lookout security and T-mobile apps that don't work on ATT are disabled.
If a certain features like WiFi calling doesn't work it's because AT&T doesn't support the feature.
Requirements:
1- Safestrap or custom recovery.
2- To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3
Download link:
Download the latest version since I post an update immediately after discovering a bug.
Mega https://mega.co.nz/#!gpUAxBqI!ukloBoz5KRzixo8a2cEXxsmJ_K0z-8LAYDfKerkWG4U (version 5)
Instructions:
This is a flashable zip. Boot to recovery to flash it. I strongly recommend a clean wipe before flashing a new Rom.
After reboot, go through the initial setup and then leave the phone alone for 10 minutes before you use it. After the first reboot the data connection takes a while to be recognized. If it does not connect after 10 min, enable and disable airplane mode and it should be fine after that.
Credits:
JustArchi for creating ArchiKitchen
Screenshots
Download booster, home screen, call recording.
Change log:
V1: Disabled knox and updaters and security apps except for Lookout.
V2: Same as V1 with Lookout and T-mobile apps disabled.
V3: Essentially the same as V2. A small type was corrected.
V4: Disabled IQ lib and corrected a potentially fatal typo in the update script.
V5: Disabled two more annoying Samsung auto-update apps that somehow slipped through.
Amazing thanks
Enviado desde mi SM-G900F mediante Tapatalk
Any benefits of features to this to make it worth while over say, Goldeneye (MI2) or an International based ROM?
joe3681 said:
Any benefits of features to this to make it worth while over say, Goldeneye (MI2) or an International based ROM?
Click to expand...
Click to collapse
This is closer to pure stock, which may offer benefits in stability. As an example, when I flash this on my system the status remains official (no padlock on boot up).
Tried it. Still full of TMobile bloat and couldn't even do anything with it because "Context Service has stopped". Couldn't type anything anywhere like web browser, couldn't edit the notification toggles, anything. Generally has WAY too many TMobile remnants left in it. Once that's all fixed it might be stable. Not entirely sure this was even tested out.
Also, idk what "Security Apps" were removed but Lookout is most annoyingly still there.
Before it's asked yes, It was a CLEAN freshly wiped install.
joe3681 said:
Tried it. Still full of TMobile bloat and couldn't even do anything with it because "Context Service has stopped". Couldn't type anything anywhere like web browser, couldn't edit the notification toggles, anything. Generally has WAY too many TMobile remnants left in it. Once that's all fixed it might be stable. Not entirely sure this was even tested out.
Also, idk what "Security Apps" were removed but Lookout is most annoyingly still there.
Before it's asked yes, It was a CLEAN freshly wiped install.
Click to expand...
Click to collapse
I flashed this using safestrap on a phone that had G900AUCU1ANCE installed. Since safestrap does not allow boot.img to be written, the result was that after the flash AP and CSC changed to BNH5 but the kernel remained at ANCE1. With this configuration I didn't see any problems. Also, this rom doesn't come with a modem, so it relies that the phone comes with unaltered ATT modem, in my case ANCE1. So, do you have a different kernel or modem?
BTW, disabled security apps are Carrier IQ, and security manager service/provider.
PS: I agree with you on Lookout being a nuisance. I will disable it and re-upload.
I flashed from stock NG3
joe3681 said:
I flashed from stock NG3
Click to expand...
Click to collapse
I see. Perhaps T-mobile NH5 rom is not compatible with ATT NG3 boot.img or modem. I will put a note in the OP. Thanks for checking this out.
OP, can you do something similar with a stock G900F firmware that will be able to be flashed on a G900A?
I have a smg900az - on tmobile
I have a smg900az on Tmo- I want this rom for this purpose. Does this include tmobile AND att modems, or just att? I am downgrading from lollipop..
Because I am sure there are others with ATT based phones who may be on TMO- would you mind if I kang your rom, debloat it, or include a debloat option, add features, etc? All credit would be given to your base.. and it would be a minute before I can get it done anyways..
P.S. PLEASE PLEASE post the md5 checksum for each version! Many of us dont want to spend the time wiping, flashing, finding out it is corrupt, then having to restore, etc!
Attached is the md5 file for version 5 that es-file explore pushed out
md5: a40d7d1ee9903bbec056cd29d52c0277 <--- flashed without a hitch
also- downgraded from a lollipop rom(Liquidsmooth 5.0 revision 2 from the unified dev section) without anything special.. so now sure what is meant by-"To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3" - but perhaps you should link to anything that explains why you believe this..
I am inviting you to a document here where I hope to get developers/contributors for all galaxy variants sharing their knowledge openly- http://forum.xda-developers.com/gal...mplified-to-connect-developers-share-t2997834
KnowledgeBroker said:
I have a smg900az on Tmo- I want this rom for this purpose. Does this include tmobile AND att modems, or just att? I am downgrading from lollipop..
Because I am sure there are others with ATT based phones who may be on TMO- would you mind if I kang your rom, debloat it, or include a debloat option, add features, etc? All credit would be given to your base.. and it would be a minute before I can get it done anyways..
P.S. PLEASE PLEASE post the md5 checksum for each version! Many of us dont want to spend the time wiping, flashing, finding out it is corrupt, then having to restore, etc!
Attached is the md5 file for version 5 that es-file explore pushed out
md5: a40d7d1ee9903bbec056cd29d52c0277 <--- flashed without a hitch
also- downgraded from a lollipop rom(Liquidsmooth 5.0 revision 2 from the unified dev section) without anything special.. so now sure what is meant by-"To begin with, you should be on ATT NCE4 rom or a variant of that. It has been reported that this is incompatible with NG3" - but perhaps you should link to anything that explains why you believe this..
I am inviting you to a document here where I hope to get developers/contributors for all galaxy variants sharing their knowledge openly- http://forum.xda-developers.com/gal...mplified-to-connect-developers-share-t2997834
Click to expand...
Click to collapse
1- This doesn't have any modem in it. Please only use version 5. The older ones are buggy.
2- You can use this ROM for your purpose. Thanks for giving credits.
3- I think I am getting the same MD5: a40d7d1ee9903bbec056cd29d52c0277.
najoor said:
1- This doesn't have any modem in it. Please only use version 5. The older ones are buggy.
2- You can use this ROM for your purpose. Thanks for giving credits.
3- I think I am getting the same MD5: a40d7d1ee9903bbec056cd29d52c0277.
Click to expand...
Click to collapse
Maybe you can clarify- the big modem thread on the tmo S5 section said not to flash their modems on another device.
My phone is back on tmo, so I imagine that running a tmo modem could increase reception..
And if you're willing to add flashable scripts that debloat and some others that make some good changes to the build prop- you have a good base, I wouldn't change it.. then people can just add/remove specific features in your own thread.
Join that Google doc in the last post, and create a section about what you've learned porting over the tmo rom.. more devs need to take it seriously.
Sent from my SM-G900T using XDA Free mobile app
Ignore this... I'm using the debloat version.
Sent from my SM-G900T using XDA Free mobile app
Did you happen to disable any of the Samsung account apps? I'm trying to sign in on gear manager to work with my gear s, but when I go to sign in to my Samsung account it crashes the gear app
LukeLeBron said:
Did you happen to disable any of the Samsung account apps? I'm trying to sign in on gear manager to work with my gear s, but when I go to sign in to my Samsung account it crashes the gear app
Click to expand...
Click to collapse
Yes. Samsung account apps are disabled. You can go to /system/app or /system/priv-app, find the app that you want to enable, and renaming it from wuteverthenameiz.apk.bac to wuteverthenameiz.apk and reboot.
Since I'm on ANG3 rooted, no recovery, I'm happy with my current setup, I just need the stock T-Mobile apps. Can you help?
After updating from KitKat to Lollipop I got one annoyance back. Since I am on Telfort, a MVNO (Mobile Virtual Network Operator) on the KPN network here in the Netherlands, I need to switch roaming on to be able to use data and next to it I constantly see an small R next to my signal bars. The small R is there instead of the 3G, H or other symbol defining the type connection you have on the network so you don't have that information anymore.
This issue popped up since the KitKat 4.4.3 update but was easily fixed with xposed framework and the national data roaming option in gravitybox on KitKat versions. But with Lollipop there is no xposed framework (yet) so I couldn't find a solution.
Finally I looked into editing the framework-res.apk of my stock Lollipop rom and managed to add the values that are needed for my provider and created an update.zip which can be flashed in a custom recovery. I have posted that solution on the open AOSP issue for this but I thought it would be good to post it here as well. As a result of some requests I have also included fixes for two other MVNO's than Telfort only. If you also have this issue and would like to get this fixed for your provider please let me know which MVNO provider you have and what the host network is. I can then add the file for your country to the update.zip
If you would like to create an update.zip yourself just follow the instructions I gave in this post and in this post.
The attached update.zip files now contain fixes for:
Telfort, the Netherlands
Tele2, the Netherlands (not in 5.0 update.zip)
Noverca, Italy
Yesss, Austria
3AT on T-mobile, Austria (not in 5.0 update.zip)
T-mobile on 3AT, Austria (not in 5.0 update.zip)
Play on T-mobile, Poland (in 5.1 update.zip and newer)
Prerequisites:
Stock Android Lollipop 5.0 build LRX210 on Nexus 5: download the update.zip
Stock Android Lollipop 5.0.1 build LRX22C on Nexus 5: download update-5.0.1.zip
Stock Android Lollipop 5.1 build LMY47D on Nexus 5: download update-5.1.zip
Stock Android Lollipop 5.1 build LMY47I on Nexus 5: download update-5.1-lmy47i.zip
Stock Android Lollipop 5.1.1 build LMY48B on Nexus 5: download update-5.1.1.zip
Stock Android Marshmallow 6.0 build MRA58K on Nexus 5: download update-6.0.zip
Custom recovery installed TWRP or CWMOD, latest zip was tested with TWRP 2.8.7.1.
Don't use this when you are on other roms than listed above like CM for example, you need to do the edits to the specific framework of that rom
How to install:
Boot into your custom recovery
Make a nandroid backup
install the update.zip
Reboot
Feel free to use the "Thanks" button
Thanks so much ! works well with Noverca operator
Hi could you create one for tele2 the host network is tmobile nl.
Thanks.
Sure will look into that later today, for which version of Lollipop do you need it? So I will make Tele2.nl (MNC02) to consider T-Mobile.nl (MNC16 & MNC20) as an non roaming operator.
Edit: One check your signature states you have a Nexus 4 these files are for Nexus 5 and will not work for the Nexus 4. If you need a nexus 4 fix I need to have your framework-res.apk so I can edit that one.
Edit 2: I have updated the 5.0.1 update.zip with the Tele2 settings for NL, please let me know if it works
Thanks a lot!
Was wondering if it is possible to make an update.zip that I could run everytime I play around with some custom roms (eager waiting for PA to be released)?
This is soo annoying with Telfort all the time, glad someone with Telfort and the knowledge was able to create a workaround!
teqnl said:
Thanks a lot!
Was wondering if it is possible to make an update.zip that I could run everytime I play around with some custom roms (eager waiting for PA to be released)?
Click to expand...
Click to collapse
Unfortunately that is not possible, since the framework-res.apk is one of the core items of a rom and therefore it differs from rom to rom. So the only solution is to edit the framework-res.apk every time when you are on a new rom. Easiest is to ask the rom-chef to include the edits in his rom. It is only one small xml file he needs to add to his rom so it is not a big deal for him/her I guess.
Hi,
Thanks for posting this update. Last week I have installed update.zip on my Nexus 5 with stock Android 5.0.0 (I have rooted with CF-Root and flashed update.zip with Flashify). It works great. The roaming issue is solved.
Yesterday I received a notification of the OTA 5.0.1. update. I can't install this update. Is this normal? How can I update to 5.0.1 and do I have to run the update5.0.1.zip as well after the 5.0.1 update?
Thanks in advance for your help!
Regards,
Jeroen
jeroencusters said:
Hi,
Thanks for posting this update. Last week I have installed update.zip on my Nexus 5 with stock Android 5.0.0 (I have rooted with CF-Root and flashed update.zip with Flashify). It works great. The roaming issue is solved.
Yesterday I received a notification of the OTA 5.0.1. update. I can't install this update. Is this normal? How can I update to 5.0.1 and do I have to run the update5.0.1.zip as well after the 5.0.1 update?
Thanks in advance for your help!
Regards,
Jeroen
Click to expand...
Click to collapse
Hi I was not aware that you could also do this with Flashify but it looks like a nice tool. Your 5.0.1 update not being able to get installed can be due to having a custom recovery installed or that the update does a check on your system files and that sees that your framework is not original anymore. So if you have a custom recovery replace that with the stock recovery and if you can restore the original framework-res.apk do that first.
I did my update to 5.0.1 using fastboot (install instructions). In short what I did was:
Download all necessary files to update, root and install custom recovery:
Factory image 5.0.1: https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz.
TWRP recovery: http://teamw.in/project/twrp2/205 (version 2.8.1.0 as 2.8.2.0 does not work on my phone)
SuperSU: http://download.chainfire.eu/supersu (put this on your phone's internal memory)
Unzip everything from the factory image into one folder with 7-zip (and move everything into one folder so you can see the recovery, system and boot)
Boot into the bootloader by pushing power and volume-down button at the same time.
Connect to your computer and check whether your device is found by typing in a command prompt: fastboot devices
If it finds a device connected cd to the folder where you have extracted the files and type the following commands on by one:
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.22.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
You have now updated to the full 5.0.1 while keeping your data.
Reboot the device and wait for android to optimize the apps.
Boot into bootloader again and type: fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
You have now installed the custom recovery.
Go into the custom recovery and make a nandroid backup.
In TWRP choose install, here you can install the update.zip for 5.0.1 to get rid of the roaming R and also the supersu.zip to be rooted again.
Good luck!
Thanks! I will try it this weekend.
could you please include T-Mobile Austria to not being roaming for 3AT (Three - Hutchison)? 3AT has an agreement with T-Mobile Austria to use their network, but currently it is shown as roaming...
Thanks in advance.
Sure, but to get it clear 3AT is your provider and it should be not roaming for T-Mobile Austria. Do you need the update for Lollipop 5.0 or 5.0.1?
Edit: Ok just did it for both, so 3AT can roam on T-mobile and vice versa, will upload it in the first post now.
wmn79 said:
I did my update to 5.0.1 using fastboot (install instructions). In short what I did was:
...
Click to expand...
Click to collapse
Your instruction is perfect. I had the same issue with TWRP 1.8.0.2.
I'm on 5.0.1 without roaming R now!
Thanks!!
Good to hear that it has worked.
Great to see this, I had the very same problem. I also have Telfort, haha I even work for Telfort
I asked the dev of the rom I'm using to implement national data roaming in it (he did it also in the kitkat version for me) so that's how I got rid of the stupid annoying 'r'. But good job on this! @wmn79
wmn79 said:
After updating from KitKat to Lollipop I got one annoyance back. Since I am on Telfort, a MVNO (Mobile Virtual Network Operator) on the KPN network here in the Netherlands, I need to switch roaming on to be able to use data and next to it I constantly see an small R next to my signal bars. The small R is there instead of the 3G, H or other symbol defining the type connection you have on the network so you don't have that information anymore.
This issue popped up since the KitKat 4.4.3 update but was easily fixed with xposed framework and the national data roaming option in gravitybox on KitKat versions. But with Lollipop there is no xposed framework (yet) so I couldn't find a solution.
Finally I looked into editing the framework-res.apk of my stock Lollipop rom and managed to add the values that are needed for my provider and created an update.zip which can be flashed in a custom recovery. I have posted that solution on the open AOSP issue for this but I thought it would be good to post it here as well. As a result of some requests I have also included fixes for two other MVNO's than Telfort only. If you also have this issue and would like to get this fixed for your provider please let me know which MVNO provider you have and what the host network is. I can then add the file for your country to the update.zip
The update.zip now contains fixes for:
Telfort, the Netherlands
Tele2, the Netherlands (only 5.0.1 update.zip)
Noverca, Italy
Yesss, Austria
3AT on T-mobile, Austria (only 5.0.1 update.zip)
T-mobile on 3AT, Austria (only 5.0.1 update.zip)
Prerequisites:
Stock Android Lollipop 5.0. build LRX210 on Nexus 5: download the update.zip
Stock Android Lollipop 5.0.1 build LRX22C on Nexus 5: download update-5.0.1.zip
Custom recovery installed TWRP or CWMOD, I tested this with TWRP 2.8.1.0, installing newest TWRP version 2.8.2.0 did not work on my phone.
Don't use this when you are on other roms than listed above like CM for example, you need to do the edits to the specific framework of that rom
How to install:
Boot into your custom recovery
Make a nandroid backup
install the update.zip
Reboot
Feel free to use the "Thanks" button
Click to expand...
Click to collapse
Can you please share how to do this? I wanted to modify the framework-res from cataclysm rom, so i've looked into the framework-res you provided to see where the folder you talked about is located, and what's into the xml file but, as stupid as it sounds, i'm unable to find them
EDIT: i was simply decompressing the apk as if it was a normal archive, using apktools showed the folders
To edit the framework-res.apk yourself and create a flashable update.zip for Android 5.1 you basically need to follow the following steps:
Install the framework apk: apktool if framework-res.apk
Decompile the framework: apktool d framework-res.apk
Edit the files in the framework-res folder that is created
Recompile the framework: apktool b -c framework-res
Use framework-res.apk from the dist folder for your update.zip with FrameworkFlasher 1.1.4a
Put the apk file generated in the previous step in the "place-framework-res-here" folder of FrameworkFlasher 1.1.4a and rename it to unsignedframework-res.apk. After than run RunMe.bat and choose option 4.
For Android 5.0 and 5.01 the last steps are slightly different:
Recompile the framework: apktool b framework-res
Copy the resources.arc file from the new compiled framework-res.apk in the dist folder to the original framework-res.apk
Use framework-res.apk to create your update.zip with FrameworkFlasher 1.1.4a
I have this issue in the US with Verizon network on Liquid Rom with my Nexus 6. What are the chances you could help me with getting it right? The dev is busy and hasnt had the chance to.
Which network are you/is Verizon using when you see the roaming r? Fixing can be done with the steps I wrote above your post. Sure I can help you with it.
has anyone tested this mod on cataclysm rom for nexus 5?
thanks!
GiacintoB said:
has anyone tested this mod on cataclysm rom for nexus 5?
thanks!
Click to expand...
Click to collapse
The files wont work on any other rom than the stock ones listed in the OP. The method should work on any custom rom if you edit the framework of that specific rom. So the files wont work on cataclysm rom the method should work.
Recently, I discovered that the Sprint LG G4 has an FM radio chip. I was actually quite surprised that this feature wasn't advertised or included in normal spec sheets. But go figure, apparently carriers are disabling FM radio chips because they're greedy data-sucking bastards: http://www.npr.org/sections/alltechconsidered/2015/04/16/400178385/the-hidden-fm-radio-inside-your-pocket-and-why-you-cant-use-it
After some research, I found that Sprint is the only U.S. carrier to not disable the FM radio chip on the LG G4 (at least on the software side). This means - much to my delight - that the international variant's radio app for Android 6.0 Marshmallow also works with the Sprint G4 running Marshmallow. The Sprint G4 comes with NextRadio, which is okay but otherwise includes annoying banner ads and seems subpar to LG's stock application. The stock radio application works flawlessly without any special privileges on the Sprint G4 and even allows output through the speaker with a headset plugged in! Just thought I would make it easier to find the application for anyone who's interested. Since I can't figure out how to attach files to a post (I don't see any option for it, how do people attach files to posts here? Sorry I'm a new user ) I'll just provide the link to the specific XDA post where I found it (you'll need to extract the .rar archive but the apk works perfectly!) http://forum.xda-developers.com/showpost.php?p=64610279&postcount=291
I tried to install the apk, and it says that it cannot parse package. So, I'm assuming that it does not work on the Sprint variant, or I'm just unlucky.
ironbesterer said:
I tried to install the apk, and it says that it cannot parse package. So, I'm assuming that it does not work on the Sprint variant, or I'm just unlucky.
Click to expand...
Click to collapse
No, I literally installed it today on my Sprint LG G4, it works perfectly. Make sure to extract the .apk file to your downloads folder on your internal storage before you try installing. Also, make sure to allow installation of apks from unkown sources in the security settings of the G4. I noticed that parsing error happens if you try to install apps from external storage or without extracting the .zip or .rar archive beforehand. Also, are you running the Android 6.0 OTA update? Because it only works on Android 6.0.
I use radio for about 6 months on zv5,zv6,zv9
For all firmwares.
Thanks a lot