Hi
can somebody recommend best way to enable multiwindow work at X98 Air 3G with Android 5.0 from Mirek190?
I have not tried so far any solutions for multiwindow and would like to try best one from the beginning.
Using bluetooth keyboard and mice, need to work in excel mobile + gmail inbox at the same time if possible.
Happy New Year!
Nicodem
Wysłane z mojego X98 Air 3G przy użyciu Tapatalka
I would boot into Windows. Android doesn't do multiple windows well.
Just root your device and install xposed framework from sikke1 debloated rom thread and then this app https://www.androidfilehost.com/?fid=24269982087020392. You will be able to put gmail and excel in the whitelist and open them in movable/resizeable windowed mode.
0czko said:
Just root your device and install xposed framework from sikke1 debloated rom thread and then this app https://www.androidfilehost.com/?fid=24269982087020392. You will be able to put gmail and excel in the whitelist and open them in movable/resizeable windowed mode.
Click to expand...
Click to collapse
Tried this. It made a lot of problems with reboot of Android. Hangs during boot and even when it finally launched I could not have any bubble with apps. So I gave up. Got revert.
Seems my configuration is not working properly with this framework.
Anyway thanks for idea.
Wysłane z mojego X98 Air 3G przy użyciu Tapatalka
Since I'm unable to post in Developer section I started this thread as I can't find an answer to my problem.
I have a Candy5 rom latest release with it's kernel. When I click on Tap&Pay under NFC I receive message that 'Unfortunately, Settings has stopped'. Does the Tap & Pay works on CM12.1 based roms? If yes what might be causing such behaviour?
Taking advantage of this thread I would also like to ask second noob question. Kernel adiutor is installed with Candy5 rom. It's not visible in Play store under my apps but when I search for it it shows me that update is available. Is it safe to update it or it's better to stay with the version which was installed with the rom?
lol
candy5 is based on cm .... and that option you mentioned NOT working on CM....
Thanks. That clarifies NFC usage for me
Wysłane z mojego SM-T800 przy użyciu Tapatalka
"Hello everyone,
This update gives you OnePlus Community App update and bug fixes.
Release notes for this Open Beta build:
Updated OnePlus Community App to V 1.9
Bug Fixes
Fixed occasional duplicate notifications
Fixed expanded screenshot duplicate stitches
Fixed app locker
Fixed inaccurate battery percentage
Fixed certain display issues with OnePlus Font
Fixed certain display issues in the weather app
Fixed camera occasionally unable to open
Fixed sending files with 3rd party apps via hotspot
Fixed inaccurate displayed network speed when activating hotspot
Please make sure you take a bit of time to fill out our survey on UX & UI here: https://goo.gl/forms/OvHAFhSItm7idDhB3.
And please remember to tell us about any bugs you may find using the bug report forums, found here. https://forums.oneplus.net/feedback/
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta) you will receive this new build as an OTA.
If you ARE NOT running open beta software and would like to, please refer to the flashing instructions and the full ROM found in the downloads page here: http://downloads.oneplus.net/
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will NO LONGER receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (FULL WIPE of all data and cache)
Please let us know how you feel about the beta builds here, we are watching."
GDrive Link - https://drive.google.com/file/d/0B9UeupRxu1D_VEkta1Z2WEFSazQ/view Thanks to @abhi0502
Google drive link please?
Hello folks, I'm so happy of OOS Open Betas that I'd take the plunge and return back to full stock (now I have unlocked bootloader and TWRP).
So, after having made a full backup on USB OTG, I'd go through these steps:
1) boot into fastboot mode and flash stock recovery via adb flash recovery recovery_op3.img
2) flash Open Beta 18 with adb sideload OnePlus3Oxygen_16
3) lock bootloader with fastboot oem lock
Is it correct? Is it enough?
Thanks!
Edit: nevermind, found a nice step-by-step guide.
TWRP does not want to install after update on beta18. Magisk does not pass SafatyNet
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
djmarco83 said:
TWRP does not want to install after update on beta18. Magisk does not pass SafatyNet
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Click to expand...
Click to collapse
Enable Core Mode in Magisk to pass SafetyNet Google patched it
liam_davenport said:
Enable Core Mode in Magisk to pass SafetyNet Google patched it
Click to expand...
Click to collapse
It does not work on beta 18
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
which files working for twrp and root?
Blu_Spark TWRP and Magisk beta v13.0 (96f8efc)
those are the files that gives you recovery and root.
Can not run normally ViperFX on beta 18
Worth Magisk Beta 13
On version ViperFX 2.5.0.5 everything is fine but does not handle the sound
Other versions of the same thing, or writes that the driver is not installed, or simply in the driver statistics writes problems
Advise how to get ViperFX to work, but at the same time that would work in the magic of SafetiNet
need OTA GUYS
When do you expect Android 7.1.2? Maybe next beta? Actually Idk if there's much difference between 7.1.1 and 7.1.2?
Is safety net passing for anyone with the latest magisk beta? It isn't for me. I've tried pretty much everything.
Twrp blu-spark 3.1.1.37 by eng syk.
Full wipe, clean flash. Everything works for me. Magisk v.12 works fine. I don't use safety net.
After flashing the rom, i reboot to recovery. Recovery, OK. After seting the rom, apps, i flash Magisk v.12 in recovery. OnePlus recovery shows up. I reflash 3.1.1.37 & it's ok.
Thank You.
kalpik said:
Is safety net passing for anyone with the latest magisk beta? It isn't for me. I've tried pretty much everything.
Click to expand...
Click to collapse
yes , on latest beta 13 safetynet passes ok
djmarco83 said:
It does not work on beta 18
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Click to expand...
Click to collapse
Works fine over here. You do have to sacrifice the use of modules though.
theduke7 said:
yes , on latest beta 13 safetynet passes ok
Click to expand...
Click to collapse
EVR_PR said:
Works fine over here. You do have to sacrifice the use of modules though.
Click to expand...
Click to collapse
I wonder what I'm doing wrong. I don't even have any modules. Let me try and flash everything again.
Edit: flashing everything again fixed it. Thanks for your help guys
how to change kernel to permissive from enforcing,,,
Which sound mod are you using guys? Could you please provide link? I tried some, but they didn't work as expected
SpartaKurd said:
Which sound mod are you using guys? Could you please provide link? I tried some, but they didn't work as expected
Click to expand...
Click to collapse
Arise.
Search it.
Sent from my ONEPLUS A3003 using Tapatalk
Hi community,
Since some time I'm trying to solve strange problem that I have on Samsung S5 and Nexus 7 2013 both with LineageOS and Magisk. It's almost not possible to pair two BT devices because pairing dialog disappears in fraction of second. One needs to have very good reflexes to touch "PAIR" button before dialog vanishes. If entering PIN code is required then it's not possible. Been thinking that something is wrong with LOS, but two days ago disabled Magisk just to be sure. And gues what? Everything worked as it should. Paired all devices and reinstalled Magisk. All paired devices are working perfectly well, but can't pair any new as problem still persists. Disabled all Magisk modules just to check if they are not a source of the problem, but it didn't helped. It looks like it's Magisk by itself. Of course I'm ready to debug it but need to know what to do... PLS suggest some solution...
Wysłane z mojego Nexus 7 przy użyciu Tapatalka
P.S. It's Android 7.1.2; LineageOS 14.1 in latest versions on both devices. Magisk 16 on Nexus and 16.4 on SGS5.
Wysłane z mojego Nexus 7 przy użyciu Tapatalka
Grabbing a logcat while trying to pair might be the best way to see what's going on.
And how should I do it? Should I grab a logcat just after unsuccessfull pairing?
P.S. Just found it. Below is my logcat.
https://drive.google.com/file/d/1bSLtvToN9wNP0PEwk1QJVqktwFXYnmrL/view?usp=drivesdk
darzur said:
And how should I do it? Should I grab a logcat just after unsuccessfull pairing?
P.S. Just found it. Below is my logcat.
https://drive.google.com/file/d/1bSLtvToN9wNP0PEwk1QJVqktwFXYnmrL/view?usp=drivesdk
Click to expand...
Click to collapse
There are a whole bunch of Bluetooth related errors in that log, but I can't see how they're related to Magisk.
Hopefully someone more knowledgeable on the subject can take a look at your log...
That it happens on two different devices, both with the same ROM, does suggest that it is somehow ROM related. Maybe also ask for advice in the ROM threads...
Reported it on LOS bugtracker but there are little chances for solution. Removing Magisk cures the symptoms so I think you understand why... Will try to grab a logcat without Magisk but for now I'm not even sure it's possible to do it without root.
Wysłane z mojego SM-G900F przy użyciu Tapatalka
darzur said:
I'm not even sure it's possible to do it without root.
Click to expand...
Click to collapse
Go back to the link I posted earlier and you'll find a link with instructions on how to do it with ADB.
OK, thanks. Will do that and report back.
Wysłane z mojego SM-G900F przy użyciu Tapatalka
I'm running a LineageOS powered Xperia F5121 phone with root and all was well until... Sky decided to updated their Skygo App and wouldn't allow it to run on rooted devices any longer.
I have therefore installed Magisk and Magisk Manager and added Skygo as well as a homebanking app in Magisk hide. However, Skygo is still complaining about a rooted device while the homebanking app is not complaining any longer but keeps crashing. Something utterly went wrong, obviously. I installed the "props" addon but changing hide parameters doesn't appear to have any effect.
Any advice would be highly welcome.
Thanks in advance!
Did you clear cache of the apps with issues?
Wysłane z mojego SM-N910F przy użyciu Tapatalka
There are a few more things you can try:
https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot