Related
It seems I'm having an issue where TB is crashing a few seconds after it launches successfully. This issue started when I upgraded to 81 and was fixed when I downgraded to 80. It seems its conflicting with some modules such as Gravitybox and XHangouts. Is anyone else having this issue?
I'm running stock Moto X Pure Android 6.0
Xposed & TBPro are OK, but Xposed & FDroid seem to be conflicting.
raddacle said:
It seems I'm having an issue where TB is crashing a few seconds after it launches successfully. This issue started when I upgraded to 81 and was fixed when I downgraded to 80. It seems its conflicting with some modules such as Gravitybox and XHangouts. Is anyone else having this issue?
I'm running stock Moto X Pure Android 6.0
Click to expand...
Click to collapse
I'm running v81 on rooted~stock 5.1.1~XZDualRecovery~Locked Bootloader~Xperia Z2(D6503), and haven't have any issues with either scheduled or manual operations in TBPro.
However, since updating to v81, I've been experiencing issues with either FDroid apps or Xposed modules FC'ing on start or just not running at all. Also...and this is where my NOOBness shows itself...I find references to the FDroid framework in the Xposed log near entries with "issues". I haven't been able to do a proper root cause analysis (sorry) and since I'll be flashing the new MM ROM tonight, I probably won't be able to shed any further light on this topic unless this happens in MM (I plan to do a clean install, I'll be using these 3 appps - so we'll see.)[/I][/I]
Cheers!
Running 83 on my HTC One M9 rooted/S-OFF with Andybones 4.0.0 Rom of 6.0 MM... both TiBU and FDroid working for me.
redhawk
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.
This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287
Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289
NOTE: You are, I believe using the @tdhite kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.
The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.
The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
Sent from my iPad using Tapatalk
@koop1955 Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel
@tdhite Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?
Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol.
Chuck
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
koop1955 said:
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
Click to expand...
Click to collapse
No doubt! Version 13 gives me something to look forward to for sure
Chuck
digitalchaos1980 said:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
Click to expand...
Click to collapse
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed
Saafir said:
Place a copy of audio effects.conf in vendor/etc. Should get you working. Be sure to set permissions as well.
Click to expand...
Click to collapse
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.
Sent from my iPad using Tapatalk
Official Xposed Framework for Android Nougat is Here – Download your Favorite Modules Now!
Announcement by rovo89 in XDA thread
Anyone tried it yet? Please give your feedback here.
He also says Xposed for Oreo won't be a long wait!
Tried it on a stock build, rooted, BL unlocked, etc. Installs great. The Youtube adaway works well, greenify doesnt work yet. the others I use arnt supporting N yet. only a matter of time
either way, its safe to install, make sure you install the correct version, and wipe cache on boot, or else stuff breaks
I mainly used (on my Moto X Pure running MM): GravityBox (which is supposed to be ready), Youtube adaway, and Youtube background play. Greenify and Amplify too but not nearly as important on this phone. OG Youtube has given me pretty much the same capability using custom ROMs, though, along with some of the customization you get in Gravitybox. I do wonder about a potential performance hit running the Xposed framework, but it'd sure be nice having the full stock camera functionality again.
Karlinski said:
Tried it on a stock build, rooted, BL unlocked, etc. Installs great. The Youtube adaway works well, greenify doesnt work yet. the others I use arnt supporting N yet. only a matter of time
either way, its safe to install, make sure you install the correct version, and wipe cache on boot, or else stuff breaks
Click to expand...
Click to collapse
Can you please share the direct download link of what needs to be flashed/installed first? It would be great if you can mention the order of flash/install as well? This is for users like me who would be requiring some help.
Also, I have magisk 14 installed on my rooted g5 Plus and am seeing Xposed Installer in the Downloads section? Can you please confirm if this is the official one?
Dahenjo said:
I mainly used (on my Moto X Pure running MM): GravityBox (which is supposed to be ready), Youtube adaway, and Youtube background play. Greenify and Amplify too but not nearly as important on this phone. OG Youtube has given me pretty much the same capability using custom ROMs, though, along with some of the customization you get in Gravitybox. I do wonder about a potential performance hit running the Xposed framework, but it'd sure be nice having the full stock camera functionality again.
Click to expand...
Click to collapse
I'm using the GB beta. It's working well for me. No need to flash AOSP anymore :laugh:
GB has all the things I like to flash LOS for and I don't have to deal with any bugs :good:
I've got it running too, thanks to the favorable feedback getting me to take the plunge after not being on stock for several months. Am using the Youtube Adaway that appears under Installer/Download, then found a Youtube Background Playback module apk that seems to work fine, and the GravityBox/Nougat also as an apk (says it's alpha, not beta). No errors or problems so far and settings are holding after reboots.
I'm really not a big camera user but the stock camera is noticeably brighter and just works way better than those on the custom roms. Viper4Arise (flashed as a zip in TWRP) works on everything but SoundCloud, which I think is a nougat thing because it works on all the oreo roms I tried, but also didn't on most nougat roms.
I'd say it's definitely a go for those wanting to try it, just do some research to see if your preferred modules are working or not, and don't expect it to be perfect yet since it just came out.
Dahenjo said:
I've got it running too, thanks to the favorable feedback getting me to take the plunge after not being on stock for several months. Am using the Youtube Adaway that appears under Installer/Download, then found a Youtube Background Playback module apk that seems to work fine, and the GravityBox/Nougat also as an apk (says it's alpha, not beta). No errors or problems so far and settings are holding after reboots.
I'm really not a big camera user but the stock camera is noticeably brighter and just works way better than those on the custom roms. Viper4Arise (flashed as a zip in TWRP) works on everything but SoundCloud, which I think is a nougat thing because it works on all the oreo roms I tried, but also didn't on most nougat roms.
I'd say it's definitely a go for those wanting to try it, just do some research to see if your preferred modules are working or not, and don't expect it to be perfect yet since it just came out.
Click to expand...
Click to collapse
Does not work on moto g5plus for me . get architecture error
update :after reinstalling apk it stated framework was active
Hi all, after I flash any rom (ressurection remix or lineage os 14.1) video lags in YouTube and there is no audio when it does play. Also Spotify has no audio and same with Facebook videos etc.
This is obviously a system wide thing so if someone could help me I'd greatly appreciate it as I can't use my phone for what id normally use it for. Many thanks in advance.
Hi, I have the same problem, only I am using stock rom 9.2.3.0 can't find any reason why this happened. All videos stutter with no audio. Before I updated to newest release it was all working.
magin1 said:
Hi, I have the same problem, only I am using stock rom 9.2.3.0 can't find any reason why this happened.
Click to expand...
Click to collapse
Sorry for the late response but I have the solution worked perfect for me. Follow this and then reboot.
https://forum.xda-developers.com/mi-5s/help/media-lags-phone-browser-t3685290
He means build prop editor too.
I have the same problem with LOS 16.
Unfortunately buildprop cannot find an attribute called audio.deep_buffer.media.
What else can I do?
Same problem happened to me yesterday (didn't hear the alarm clock cause there was no sound ). I'm on the same version of unofficial rr16 from 4 months and this issue began yesterday. If i reboot the phone the problem disappear for some time, then comes back again.
P.S. i don't have audio.deep_buffer.media in my build prop too
Lol you saved me. I am using a miui gsi right now, I also didn't have the prop. Simply download a root explorer like mixplorer, go to /system/build.prop and open it with text editor. Then add: audio.deep_buffer.media=false
It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Raven.95 said:
It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Click to expand...
Click to collapse
Shadow 00 said:
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Click to expand...
Click to collapse
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
EdoNINJA93 said:
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
Click to expand...
Click to collapse
Yep, extended kernel do the job too, thanks. So it's really a kernel problem...