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 just received my Oreo update for my Unlocked S8+. Has anyone else received it yet? I'm thinking since we have Safestrap and now custom rom support that I'll cancel the update and wait for an AOSP rom.
ajsmsg78 said:
I just received my Oreo update for my Unlocked S8+. Has anyone else received it yet? I'm thinking since we have Safestrap and now custom rom support that I'll cancel the update and wait for an AOSP rom.
Click to expand...
Click to collapse
What carrier are you with? Did you have beta?
I just got it also. I'm on cricket
xmckinzie said:
What carrier are you with? Did you have beta?
Click to expand...
Click to collapse
I was on T-Mobile but switched to MetroPCS two days ago. (Same network)
It's true... I am on Sprint with G995U1 and I am currently downloading a 1354.14MB update.
I had to check for it, but it found it and downloaded it. My phone is unlocked. Update applied without issues.
Loving finally having the auto fill API.
Just checked my software updates for the first time in weeks and there it was! Unfortunately they're working on our electrical system, so I won't be able to download it until WiFi is back up, but it'll give me time to back things up.
Factory unlocked running on T-Mobile
Can anyone confirm if Hotspot remains functional after the update without carrier involvement.
Thanks
Aridon said:
Can anyone confirm if Hotspot remains functional after the update without carrier involvement.
Thanks
Click to expand...
Click to collapse
I used the hotspot yesterday at a clients and I also just switched carriers a few days ago and the hotspot worked fine. I did end up taking the OTA to Oreo.
I live in albania and no update, I have the unlocked firmware running in vodafone network. Currently im on BRB1? Any ideas why I dont have an update yet? Thanks
Can someone please confirm which bootloader is bundled with this update?
hazard666 said:
Can someone please confirm which bootloader is bundled with this update?
Click to expand...
Click to collapse
Bootloader 2
clownin72 said:
Bootloader 2
Click to expand...
Click to collapse
Awesome. Thanks!
I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
bigmikey307 said:
I have the T-Mobile variant which I converted to the International ROM using the method that does not require the bootloader to be unlocked. I am running the open beta of 9.0.17. I went to check if I have Chat features yet and it worked for like a second! I turned the toggle on, went back, clicked chat features again and now it says it's not available for my device. Maybe it was just a glitch, but look at the screenshot I attached! My hopes were so high and now I'm just upset again. Will I ever get Chat features? Who am I waiting on? Google? OnePlus? T-Mobile?
Click to expand...
Click to collapse
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Yes, I was running the international software and had this same issue. Flashed back to stock T-Mobile software due to horror stories of the update to Android 10 bricking converted devices. Tried to turn these on again, and same story... Stock messaging app worked, Google's didn't.
I have converted to International and upgraded to 10.0 using Oxygen Updater then downloaded Google Messenger app and it works great. I do have a unlocked bootloader however.
qbanlinxx said:
On the T-Mobile firmware it only works with the stock messaging app, probably the same on the OB.
Click to expand...
Click to collapse
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
pyrorob said:
Wrong, just update to the latest beta of messages and make sure carrier services is updated and it can be fully activated. Am currently on stock T-mobile firmware.
Click to expand...
Click to collapse
RCS on the stock TMobile firmware isn't the issue. Latest beta message installed, carrier services updated, still no RCS on my device.