Related
Does anyone know if there are any Foxfi compatibility issues with Foxfi and the new update, software version MMB29M.G930VVRURAPI3?
Foxfi no longer works with the nougat beta.
However the usb/bluetooth seems to work. Just no wifi hotspot anymore.
Thanks for the reply but I wasn't asking about Nougat. I was wondering if the latest update for marshmallow works with Foxfi?
Coneyo said:
Thanks for the reply but I wasn't asking about Nougat. I was wondering if the latest update for marshmallow works with Foxfi?
Click to expand...
Click to collapse
It does. I use it every day.
Sent from my SM-G930V using Tapatalk
I can't seem to replicate it on my clean wiped phone but when I upgraded from Marshmallow to Nougat initially, foxfi worked great (AND no repeated warnings on boot about the VPN cert). After clean wipe on second nougat beta though, I couldn't get it passed the certificate installation check (though it looked like the certs were installed just fine). And now some time later, when I check the box it just says unsupported for my phone :/ Maybe foxfi can figure it out once we are out of beta. I also was somehow able to trick the hotspot feature in Android settings.. When I tapped away from the "you need a subscription" popup somehow the tether actually kicked on. I can't seem to replicate this now though
Hey guys, I'm stock, rooted, s-off with magisk and I'd like to be on Lee Droid or Viper Nougat with working Magisk and Verizon features. The way I'm reading their guides, it seems I would have to be on Nougat firmware for that. Does that mean I can convert to US Unlocked Nougat with updated firmware, then to Lee Droid or Viper Magisk and pass safety net while having nougat and advanced calling and such?
Thanks guys
I'd love to know the answer to this as well. I don't have many friends using Verizon, so I don't use the Verizon features much. I'm just kind of tired of Verizon being slow with their updates. For some reason I keep being stupid and buying Verizon phones despite the long updates for 4 different phones that have been on Verizon. :/
you guys have to flash the US unlocked RUU and then flash the Verizon radio for it to work. From what I've read you'll have the features you want. But since I haven't personally tried I cannot be 100%. there is guides on how to do this.
IMHO, I would wait for Verizon, it is always best to use your carriers firmware. It wont be much longer even though itll feel like a lifetime.
I'd love to get a confirmation on this as well. I can say however from my own experience that running VZW firmware with viper10 4.x.x ROM that everything works great EXCEPT volte (HD calling/ advanced calling features) I'd like to mention to others who are experimenting as well that I can format data, flash 3.5.0 and have volte back up and running no problem. My theory is the issue lies in the VZW firmware being a MM version. My next step is to flash the nougat RUU, flash the VZW radio, and then the viper nougat ROM. I'll share the results once I get the chance to do everything. Again if anyone can chime in on this method that would be greatly appreciated.
ROMs now support Advanced Calling with Magisk.
now just need vzw nougat.
andybones said:
ROMs now support Advanced Calling with Magisk.
now just need vzw nougat.
Click to expand...
Click to collapse
Really? What changed?
Im on viper with 1.85 firmware and advanced calling works for me
jhorn85 said:
Im on viper with 1.85 firmware and advanced calling works for me
Click to expand...
Click to collapse
Did you do anything special when you installed the ROM? Could you tell me what steps you took installing it? Just wondering if I'm missing something. I have the latest VZW firmware installed as well. Are you positive that advanced calling is working? I notice that when you make a call the data signal icon will remain on the status bar (unless you go into venom tweaks and change it to anything other than the stock icon, then it will disappear) but there won't be any traffic and I can confirm it by trying to load a web page.
aer0zer0 said:
Really? What changed?
Click to expand...
Click to collapse
Some team work from lee, captn, nkk, baad, and testers.
on multirom with advanced calling and wifi calling, leedroid N.
https://forum.xda-developers.com/showpost.php?p=70525234&postcount=5074
andybones said:
Some team work from lee, captn, nkk, baad, and testers.
on multirom with advanced calling and wifi calling, leedroid N.
https://forum.xda-developers.com/showpost.php?p=70525234&postcount=5074
Click to expand...
Click to collapse
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
aer0zer0 said:
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
Click to expand...
Click to collapse
That's what it's looking like to me. With some work it is possible to get ROMs working on MM firmware with VoLTE and Wi-Fi calling. Santods rom has had this for a little bit and now with this new information, if one was to say combine both, the outcome is great. But I'll leave that to those more experienced than myself, but it is possible now thanks to all these brilliant minds.
Is the magisk files in the magisk repo?
aer0zer0 said:
Is the magisk files in the magisk repo?
Click to expand...
Click to collapse
That I am not sure of, sorry.
aer0zer0 said:
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
Click to expand...
Click to collapse
Need verizon to update to n, that's the step we need. On mm it's still broken on n based Roms
Other Than that yes
afuller42 said:
Need verizon to update to n, that's the step we need. On mm it's still broken on n based Roms
Other Than that yes
Click to expand...
Click to collapse
on a personal build combined from Santods mostly I am able to be on Leedroid N on latest Verizon MM firmware with multirom with VoLTE and Wi-Fi calling.
andybones said:
on a personal build combined from Santods mostly I am able to be on Leedroid N on latest Verizon MM firmware with multirom with VoLTE and Wi-Fi calling.
Click to expand...
Click to collapse
Works now on latest Viper 4.6.0 also
sdamark said:
Works now on latest Viper 4.6.0 also
Click to expand...
Click to collapse
Still not working for me, ill try a clean install at some point. Volte never broke for me on any update, been lucky on that i guess
@andybones also
sdamark said:
Works now on latest Viper 4.6.0 also
Click to expand...
Click to collapse
Even better. Didn't realize that 4.6.0 was out, so I don't know of the change log.
Wasn't bragging by any means also.. Was just stating that it works, and was sure smarter devs would get it soon.
I can confirm that the viper 4.6.0 upgrade does fix volte for vzw devices running mm firmware. The changelog says only working for non magisk version, I suppose that's due to no nougat firmware/RUU released from Verizon yet. If that's a deal breaker your gonna have to wait, otherwise make sure your running the supersu only version. I upgraded from 4.5.0 and it works perfectly. Something I've noticed over the last few months with all the flashing I have done is that if you go into the hidden network info screen, if it shows 3107 for your carrier, it won't work, if it says Verizon wireless as your carrier, then everything is working as it should. Thanks for the update in the rom guys this is GREATLY appreciated for the hard work.
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
pwnerman said:
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
Click to expand...
Click to collapse
an Android controlled toothbrush? is it april 1st? How does that work?
blue"tooth" LOL
You listen to music via vibration of your teeth.
railfan-eric said:
an Android controlled toothbrush? is it april 1st? How does that work?
Click to expand...
Click to collapse
it syncs with bluetooth and your phone camera to see what stops you are missing and over brushing. even without all that functionality and just as a dumb toothbrush it really is worth it
Same problem with LG G5 with 7.0. Did you find any solution?
Oral-B not starting on rooted devices
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
jbd7 said:
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
Click to expand...
Click to collapse
hi. did you find a solution? rootcloack didnt help me...
Ugo10 said:
hi. did you find a solution? rootcloack didnt help me...
Click to expand...
Click to collapse
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
jbd7 said:
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
Click to expand...
Click to collapse
it's perfect! thx!
I downloaded the Samsung FM radio app from APK Mirror and tried installing it on my unrooted S7 Edge (SM-G935U). It wouldn't install -- phone showed "The package name conflicts with an existing package by the same name." Huh, I am 100% certain no such app is installed. I tried it again with logcat running. The error there is more informative:
Code:
AASATokenParser: Violate security policy of MSTG. Package(com.sec.android.app.fm) is blocked.
Unfortunately, Google seems to know precious little about the above. Searching for "aasatokenparser" returned nothing useful. Hits on "mstg" mostly pointed to something called a "mobile security testing guide."
AASATokenParser might be from AASAservice, which is commonly removed by debloat scripts. I don't want to root this phone though. Any other options for bypassing this security check or whatever it is?
Fixed it. Found this thread about installing S8 packages with reports of the same error I was seeing. Tried the suggestion of togging the secure startup setting followed by a reboot. That worked -- radio app installed and is behaving normally.
Very odd...
woah wacky so it actually works!
is this a snapdragon model? I like nextradio but stock always does it better
I tried cloning samsung radio.apk.... the damn thing would crash every time. even in force keep open/prevent crash mode.it only worked... when I used next radio... couldn't actually use the interface.
how did you get it to work exactly? the "remove lockscreen, add shortcut and install right away" trick didn't work
supertac said:
is this a snapdragon model? I like nextradio but stock always does it better
Click to expand...
Click to collapse
SM-G935U, so Snapdragon model.
supertac said:
I tried cloning samsung radio.apk.... the damn thing would crash every time. even in force keep open/prevent crash mode.it only worked... when I used next radio... couldn't actually use the interface.
Click to expand...
Click to collapse
Cloning seems not to work so well in recent versions of Android. Instead try the downloading the APK from APKMirror.
supertac said:
how did you get it to work exactly? the "remove lockscreen, add shortcut and install right away" trick didn't work
Click to expand...
Click to collapse
The link I posted before points to yet another link that had the actual steps I followed, post #24:
Go to Settings > Lock screen and security > Secure startup. Whatever Secure Startup is set to, toggle it (i.e. turn it on if it's off and turn it off if it's on), then reboot.
Click to expand...
Click to collapse
yeah I did all those things and I wouldn't even think it would work cause the package is locked in the software...
OH MY GOD... IT WORKS, IT ACTUALLY WORKS! I can't believe such a simple work around WITHOUT ROOT does the trick! even on the S7 active with the latest security patch (dec 2017) still works!
the galaxy A series samsung fm radio app... works just fine on the galaxy s series phones!.. its much louder then regular music (like nextradio) but I think that's to do with samsung making it quiet. I like nextradio for what they did but this interface works MUCH better and faster. strange I'm running dark theme on my samsung phone and this is the only stock app not effected by it- likely cause of how its installed.
thank you so much for reposting this... I wonder if it works for every phone... NOW I want to go back to the galaxy A5 2017 (enxyos 7880 has it in) 520W canada version and try this trick to see if it works on that unit... since canada carriers/samsung blocked the fm radio on the canada release.
I wonder if this works for all recent samsung phones?
AASATokenParser might be from AASAservice, which is commonly removed by debloat scripts. I don't want to root this phone though. Any other options for bypassing this security check or whatever it is?
perhaps package disabler pro could remove this out? I just figured out how to work that- you gotta install an extra it to get it running properly it that runs without root.
unrelated...I'm trying eng root method again... it kinda sucks. I love these custom roms but eng boot sucks some battery- its not a real way to root at all, at least it doesn't trip knox and can be reset to stock without major issues
can someone try this with Enxyos S7?
supertac said:
perhaps package disabler pro could remove this out? I just figured out how to work that- you gotta install an extra it to get it running properly it that runs without root.
Click to expand...
Click to collapse
I've been convinced by the arguments /u/neromancr has floated in various Reddit threads (example) to avoid package disablers.
I've tried to install it on my exynos phone and although I have been able to install it, the screen is always white and a few seconds after open it, the app always crash.
Thank you anyway.
Enviado desde mi SM-G935F mediante Tapatalk
chomi7 said:
I've tried to install it on my exynos phone
Click to expand...
Click to collapse
According to many reports across the web, only the SnapDragon vesion of this phone has the FM radio.
SteveRiley said:
According to many reports across the web, only the SnapDragon vesion of this phone has the FM radio.
Click to expand...
Click to collapse
I know it, but I had to tried it
Enviado desde mi SM-G935F mediante Tapatalk
I'm on 930P,
Getting 'parsing error' when installing apk,
I do not have 'secure starup' in settings.
Ideas?
Suggestions?
Created homescreen shortcut to .apk file
and tried 'reboot/quick install after reboot'
same 'parsing error'
??
KaptainRandom said:
I'm on 930P,
Getting 'parsing error' when installing apk,
I do not have 'secure starup' in settings.
Click to expand...
Click to collapse
What Android version?
7.0 here. The option is in Settings | Lock screen and securty | Secure startup.
SteveRiley said:
What Android version?
7.0 here. The option is in Settings | Lock screen and securty | Secure startup.
Click to expand...
Click to collapse
6.0.1
PB5
KaptainRandom said:
6.0.1
PB5
Click to expand...
Click to collapse
Ah. Not sure how to advise you, as I've had only Nougat on this device. Perhaps you'll need to try an older version of the radio app? APKMirror lists several.
SteveRiley said:
I downloaded the Samsung FM radio app from APK Mirror and tried installing it on my unrooted S7 Edge (SM-G935U). It wouldn't install -- phone showed "The package name conflicts with an existing package by the same name." Huh, I am 100% certain no such app is installed. I tried it again with logcat running. The error there is more informative:
Code:
AASATokenParser: Violate security policy of MSTG. Package(com.sec.android.app.fm) is blocked.
Unfortunately, Google seems to know precious little about the above. Searching for "aasatokenparser" returned nothing useful. Hits on "mstg" mostly pointed to something called a "mobile security testing guide."
AASATokenParser might be from AASAservice, which is commonly removed by debloat scripts. I don't want to root this phone though. Any other options for bypassing this security check or whatever it is?
Click to expand...
Click to collapse
I downloaded nextradio apk (am not in the US so it's not available in the play store) and the basic tuner is working very fine with earphones offline! Finally enjoying fm radio on s7 edge!
Works great! S7 Edge, Verizon, 8.0.0!
Gutted no fm radio works with my exynos s7 edge. If i had an fm radio my life would be complete. Is there no work-around for this?
dj.shauny.g said:
Gutted no fm radio works with my exynos s7 edge. If i had an fm radio my life would be complete. Is there no work-around for this?
Click to expand...
Click to collapse
Sorry,
Exynos not have fm hardware on chip.
Hey, I'm on sm-g9350 (Hong Kong snapdragon) and I want to get fm working on custom rom /kernel. What needs to be added? I have tried adding proper dts, radio iris modules, but no luck..
Link for daownload radiofm pls?
I successfully downloaded from APK but when I try to install I get "the package conflicts with an existing package by the same name" and will not allow installation (Samsung Galaxy Note 5).
I have looked at all apps and do not see this app "radio" anyplace.
Thanks
Anybody install this yet?
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
I have been running 10.3 for a while and I am t-mobile locked but converted to International. Everything is smooth other than Gpay is not working and Playstore is not certified. This is because I am t-mobile variant.
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Yes! I've been installed for a few weeks. All perfect.
Enviado desde mi ONEPLUS A6013 mediante Tapatalk
I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance
BoSavageYo said:
I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance
Click to expand...
Click to collapse
Just do a local upgrade. Just follow the guide to save root.
jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Everybody has installed it... It's been out for days
Went for it yesterday. With an "ultimate guide" here on forum. I was 9.0.17 rooted with twrp description problems. So I downloaded update (1.8Gb) from official One+ site. And did local update, and all the steps to keep root. After finally booting up I got message that Magisk Manager stopped working, but everything was fine. So cleared app temp memory, and settings (for Magisk only) and next boot everything was ok.
Nope... 100% stock, 9.0.17 is ROCK solid, g-pay, samsung pay work perfectly & there really isn't anything in 10 I can't live without yet. So, I
see no need to update for now.
I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.
sssarg said:
I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.
Click to expand...
Click to collapse
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.
sssarg said:
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.
Click to expand...
Click to collapse
There is a Magisk module to deal with that (immersive gestural Navigation for Android 10), and an adb command to change the size of the space. It's a deliberate thing from Google so they'll perhaps remove it later or no but staying with Pie just for that.....
Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk
Question of the day. I've been waiting to do the A10 update for the issues it showed on the first days. I'm on a converted 6T from TMo, running 9.0.17. my major concern is the GPay thing I use it a lot. But researching here there's a way to make it work if I root the device. So can I update to 10.3.0 then root to get the GPay issue resolved with the Hide module on magisk? Or should I root on Pie then update?
phillymade said:
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk
Click to expand...
Click to collapse
This is pretty bad ux experience, and with the amount of complaints it seems and accidental keypress possibly when swiping is much better than losing all the text and keyboard closing with an accidental touch. At least give us the option to move it down, without having to go into ADB and setting an offset that then interferes with the way all apps render.