Related
I am using:
1. Adaway after enabling systemless in magisk settings
2. Greenify4magisk - helpful in hibernating notification hungry and backgroung running application
Both safetynetcheck are green.
Cant find SELinux permissive module. Can someone help? Also what other modules are you using?
Aj.GaLaxY aCE said:
I am using:
1. Adaway after enabling systemless in magisk settings
2. Greenify4magisk - helpful in hibernating notification hungry and backgroung running application
Both safetynetcheck are green.
Cant find SELinux permissive module. Can someone help? Also what other modules are you using?
Click to expand...
Click to collapse
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Gcam freezes
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Could you share that module, please? I added persist.camera.HAL3,enabled=1 to the build prop but the GCAM take a long time to open and even my stock camera. I don´t know what I am making wrong.
paqr28 said:
Could you share that module, please? I added persist.camera.HAL3,enabled=1 to the build prop but the GCAM take a long time to open and even my stock camera. I don´t know what I am making wrong.
Click to expand...
Click to collapse
You're doing it right, but there is a bug in Oreo, at the moment there is only one known workaround - set SELinux to permissive mode (for example with this or any other app/method). Gcam and stock camera will start fast in permissive mode.
Slow motion GCAM
_mysiak_ said:
You're doing it right, but there is a bug in Oreo, at the moment there is only one known workaround - set SELinux to permissive mode (for example with this or any other app/method). Gcam and stock camera will start fast in permissive mode.
Click to expand...
Click to collapse
Thank you, It finally works with SELinux to permissive, Did the Slow motion in gcam works for you? That is the only thing that doesn´t work for me.
paqr28 said:
Thank you, It finally works with SELinux to permissive, Did the Slow motion in gcam works for you? That is the only thing that doesn´t work for me.
Click to expand...
Click to collapse
Slow motion requires different media profile files, but when you replace them, stock camera will crash with slow mo mode.. As I never use this mode and I prefer fully working stock camera, I just let it be..
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Couldyou please share your module? It works on oreo?
IronJacob said:
Couldyou please share your module? It works on oreo?
Click to expand...
Click to collapse
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Code:
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
audio.safemedia.bypass=true
_mysiak_ said:
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Click to expand...
Click to collapse
Thank you very much
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Fix video recording sounds? Is it bad?
_mysiak_ said:
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Code:
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
audio.safemedia.bypass=true
Click to expand...
Click to collapse
thank you man! to add or edit stuff in your module i can simply edit the system.prop file in your mod?
Also , i see you use "ro.qc.sdk.audio.fluencetype=fluencepro" while oher mod use "ro.vendor.audio.sdk.fluencetype=fluencepro", both valua are correct or other mod mistake this value?
riccetto80 said:
thank you man! to add or edit stuff in your module i can simply edit the system.prop file in your mod?
Also , i see you use "ro.qc.sdk.audio.fluencetype=fluencepro" while oher mod use "ro.vendor.audio.sdk.fluencetype=fluencepro", both valua are correct or other mod mistake this value?
Click to expand...
Click to collapse
Yes, you can edit system.prop to modify the values and reinstall the module to apply them. I used to be able to modify system.prop of already installed module in /magisk/module_name/system.prop file directly, but it stopped working for me - file doesn't get saved (not sure if related to Oreo).
"ro.qc.sdk.audio.fluencetype=fluencepro" was required in Nougat. In Oreo, the default value is indeed "ro.vendor.audio.sdk.fluencetype=none". However audio recording is fine as far as I can tell, so it either has been fixed by Xiaomi or "ro.qc.sdk.audio.fluencetype=fluencepro" is still working. Will check when I have more time for testing
Edit:I can't hear any difference between stock "ro.vendor.audio.sdk.fluencetype=none"; "ro.vendor.audio.sdk.fluencetype=fluencepro" and "ro.qc.sdk.audio.fluencetype=fluencepro". My guess would be that it has been fixed by Xiaomi in the January(?) Oreo update. Can anyone else confirm?
A question - if I have the EIS and HAL3 already activated as I have the Gcam previously installed I don't need to deactivate them in your module? Just install the module? What I want is the voice recorder. Or, shall I put to zero ("0") these values: persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
laotzy said:
A question - if I have the EIS and HAL3 already activated as I have the Gcam previously installed I don't need to deactivate them in your module? Just install the module? What I want is the voice recorder. Or, shall I put to zero ("0") these values: persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
Click to expand...
Click to collapse
You can keep them (Magisk merges build.prop changes from all modules), remove repeating lines or add comment sign "#" at the beginning of the line which you want to skip. The easiest way is to use module as it is, it should work without any issues..
Hello guys, anyone tried the Systemless Xposed for Oreo?
spithash said:
Hello guys, anyone tried the Systemless Xposed for Oreo?
Click to expand...
Click to collapse
Yes, many of us. It's working fine, but will break Safetynet.
These modules help me a lot everyday.
joeyhuab said:
These modules help me a lot everyday.
Click to expand...
Click to collapse
Pls Give link of Andromeda Enabler and all modules related with nav bar
sauru.660 said:
Pls Give link of Andromeda Enabler and all modules related with nav bar
Click to expand...
Click to collapse
Andromeda enabler: https://drive.google.com/open?id=1SwIza1UYLQrn0c6b0gS9zEV7p48YefKh
Soft keys only: https://drive.google.com/open?id=1kOrqcZRki8ZhEeGy8_AC515uXq6qjBkr
Navbar: https://drive.google.com/open?id=1mv1XkT_ElubR-hBUpXC2cmF7mYbplEXs
Enjoy.
joeyhuab said:
These modules help me a lot everyday.
Click to expand...
Click to collapse
Are you on Oreo or Nougat? If on Oreo, have you installed the latest update?
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed
byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either
dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way
I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now
byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)
i need a rom which is having camera2api pre-enabled in it ??
Aosp extended AEX Rom
Masik Miui Rom
Pixel Experience and Lineage os
Manav10799 said:
Pixel Experience and Lineage os
Click to expand...
Click to collapse
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)
MSM Extended
https://forum.xda-developers.com/redmi-note-5-pro/development/stable-msm-xtended-x9-t3819822
v0id_walker said:
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)
Click to expand...
Click to collapse
Or simply editing the build.prop in the system/ folder: "persist.camera.HAL3.enabled=1"
Sure you need to root the device but who doesn't in case you have already flashed a custom rom: hiding root from certain apps is not the problem (except Pokemon GO fair enough)
A R said:
i need a rom which is having camera2api pre-enabled in it ??
Click to expand...
Click to collapse
Masik
v0id_walker said:
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)
Click to expand...
Click to collapse
yes i agree i also manually enabled camera2api on Los15.1 but it broke my front camera video calling feature in all the apps. So if anybody have any solution to this please do share here.
Surik4t4 said:
MSM Extended
https://forum.xda-developers.com/redmi-note-5-pro/development/stable-msm-xtended-x9-t3819822
Click to expand...
Click to collapse
they have just provided the option to enable or disable it from settings but what about the video calling feature which gets broken after enabling it ?? did anybody tested on any rom with enabling camera2api ???
A R said:
yes i agree i also manually enabled camera2api on Los15.1 but it broke my front camera video calling feature in all the apps. So if anybody have any solution to this please do share here.
Click to expand...
Click to collapse
There's magisk module called camera2_api+WhatsApp.zip that enable camera 2 api without conflict with any other app (in this case video calling on WhatsApp), i get it somewhere on di xda but not test it yet, i'll report back tomorrow
Bad english, sorry
Some advice: do not choose ROM just because camera2 API enabled. Enabling camera2 API is very easy. Choose ROM according to your needs and preferences first, then worry about camera2 API.
A R said:
they have just provided the option to enable or disable it from settings but what about the video calling feature which gets broken after enabling it ?? did anybody tested on any rom with enabling camera2api ???
Click to expand...
Click to collapse
Whatsapp video calling works perfectly well on Msm Xtented no issues here and in the latest build also comes with A2 ported cam
Nokia Extensions!Telegram Group
This thread is discontinued. Future posts will be made here.
Module description
Why should the Chinese have all the fun? This module aims at porting features from the Chinese variants of Nokia phones to Global variants (Android One).
Features
1. AI Floating Ball
The phone will recommend relevant application shortcut settings according to your usage. You can also:
Use the custom shortcuts to customize the shortcut menu.
Use gestures to enrich your interaction with the phone.
2. Data speed indicator
Tested and working on Nokia 6, Nokia 8 and Nokia 7 plus on Oreo. After installation, go to Settings - Network & Internet - Data Usage and toggle Show data speed. Now you should be able to see your internet speed on your status bar.
3. Screenshot Plus
Take long screenshots, edit them on the go.
4. Screen Recorder
Supports FHD, HD and SD at 30 and 60 FPS, records audio too.
5. Junk Cleaner
Clears cache and junk files.
6. Task Manager
View and end a running task.
7. Smart Boost
Enjoy gaming without frame drops and hiccups!
8.. Virus scanner
Scan for virus and keep your phone secure.
9. NokiaPure fonts
Change your system font to NokiaPure
How to's
To install the module, flash the zip using Magisk manager or TWRP and reboot.
To uninstall the module, flash the same zip again and reboot.
To get the internet speed on the status bar, go to Settings - Network & Internet - Data Usage and toggle Show data speed.
To use Screenshot plus and Screen Recorder, add them to Quick Settings.
To open AI Floating Touch, Smart boost, Task manager, Junk Cleaner and Virus scan use NEX Launcher.
Compatibility
Nokia Phones
Magisk 17+
Android 8.1.0 and above
Download from Magisk Manager.
Source code: Github[/SIZE]
Credits
@topjohnwu for Magisk
@ahrion & @Zackptg5 for Unity template and Volume Key Selector
FIH/Evenwell/HMD Global (whoever it is) for making these apps
Changelog
v1
Initial release
v1.1
Added more features - Screenshot plus, Screen Recorder, System dashboard
Added NokiaPure fonts
v1.2
Added smart boost
fixed some FCs
v1.3
Merged Pie and Oreo files into a single package
Users can now select only the files they want to install using volume keys
How to use these apps? I am unable to use the apks after downloading.
yagyanshskumar said:
How to use these apps? I am unable to use the apks after downloading.
Click to expand...
Click to collapse
The Title shows that it's a Magisk Module. Means that you need to be rooted using Magisk
Akilesh T said:
Nokia Extensions!
Module description
Why should the Chinese have all the fun?
Click to expand...
Click to collapse
Haha, great!
maybe is not working on nokia 6 with magisk root which have locked bootloader
frnsl3 said:
maybe is not working on nokia 6 with magisk root which have locked bootloader
Click to expand...
Click to collapse
I guess you are using Magisk 16.1
This module requires Magisk 17+
ZeroPointMax said:
Haha, great!
Click to expand...
Click to collapse
These features could have been added by Nokia mobile itself if they wanted to. But they decided to keep it only for China, going with "Pure stock" Android for the rest of the markets. You can say that it might reduce the speed of the updates, but China variants have been getting updates at almost the same speed as the global variants. It would have been great if they had gone with something like OOS.
Akilesh T said:
I guess you are using Magisk 16.1
This module requires Magisk 17+
Click to expand...
Click to collapse
yep so sad, able rooting but not maximum potential and soft brick too often if we modify the system
frnsl3 said:
yep so sad, able rooting but not maximum potential and soft brick too often if we modify the system
Click to expand...
Click to collapse
Magisk is systemless
Akilesh T said:
Magisk is systemless
Click to expand...
Click to collapse
not talking about magisk there, i tell you about rooting
Unable to install
I have nokia 8. When i try to install this module, it says that my decvice is pixel Xl and refuses to install. I think this is because i have installed daydream enabler module. Is there a way to bypass the device check and proceed with installing this module?
audiophile55 said:
I have nokia 8. When i try to install this module, it says that my decvice is pixel Xl and refuses to install. I think this is because i have installed daydream enabler module. Is there a way to bypass the device check and proceed with installing this module?
Click to expand...
Click to collapse
Looks like that module edited your build.prop
You can bypass it. Extract the zip. Remove the device check part in install_module function inside the config.sh file. Rezip it and flash again
Akilesh T said:
Looks like that module edited your build.prop
You can bypass it. Extract the zip. Remove the device check part in install_module function inside the config.sh file. Rezip it and flash again
Click to expand...
Click to collapse
Can you tell me exactly which lines to remove? I try removing few lines but getting the same error. I am a noob at this. BTW, i also tried deleting the entire config.sh file and still I get the same error.
EDIT: My bad. I kept flashing the original zip and not extracted zip. All good now.
audiophile55 said:
Can you tell me exactly which lines to remove? I try removing few lines but getting the same error. I am a noob at this. BTW, i also tried deleting the entire config.sh file and still I get the same error.
EDIT: My bad. I kept flashing the original zip and not extracted zip. All good now.
Click to expand...
Click to collapse
You mustn't delete config.sh file
:good:
does this module work with other android one phones? im using xiaomi a2 lite @ oreo 8.1
How can i use ai floating? . I cant find where to activate it
cbkottege said:
How can i use ai floating? . I cant find where to activate it
Click to expand...
Click to collapse
Search for "touch" in settings. There'll be a result like "Hide in do not disturb apps". That'll take you to the AI floating button' settings
Hi. I am using nokia 8. After installation module and restart, i get smart tuner and data speed indicator force close, how to fix it sir?
(Sorry for my bad english)
zeronatdo said:
Hi. I am using nokia 8. After installation module and restart, i get smart tuner and data speed indicator force close, how to fix it sir?
(Sorry for my bad english)
Click to expand...
Click to collapse
Are you using the latest version (v1.3)?
Hi everyone, as our mi pad has the OV13855 sensor like some Mido (RN4) versions I simply installed the suggested apk from mido thread and I managed to have hdr+ working using Pixel 2 XL settings in the apk. You are free to try other combination anyway.
Here's the link from 'official' page: Download
I have it working on 25/12 Mokee, don't know if it works in Miui or other Pie roms.
sacca25 said:
Hi everyone, as our mi pad has the OV13855 sensor like some Mido (RN4) versions I simply installed the suggested apk from mido thread and I managed to have hdr+ working using Pixel 2 XL settings in the apk. You are free to try other combination anyway.
Here's the link from 'official' page: Download
I have it working on 25/12 Mokee, don't know if it works in Miui or other Pie roms.
Click to expand...
Click to collapse
I'm on Xiaomi.eu's MIUI10 8.12.13 Rom, and app crashes on launch. My suspicions is because MIUI10 does not support/enable Camera2 api. I should be rooted, so I'm gonna try tinkering with the build.prop to get it enabled and report back.
Havoc Os 2.0 build 28-12-2018 crashes
Works on my los 16.
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Andro_Nicus said:
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Click to expand...
Click to collapse
I flashed official build of Havoc Os 2.0 31-12-2018, enable camera2 api and camera work normal.
Andro_Nicus said:
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Click to expand...
Click to collapse
Thanks!
Confirming this also works on xiaomi.EU 9.1.3 weekly.
Enabling camera2api via build. Prop does break the stock miui cam though, it'll crash when launched.
Not that that's a big loss...
Hello,
I have the latest version of xiaomi.eu installed on my mipad 4, is this compatible with it?
Yes
on latest xiaomi.eu I can't get it to work. With magisk 19.2, I can't directly edit the /vendor build.prop (although I give root permission), so I tried systemless with MagiskHide props config module. I supposedly add persist.camera.HAL3.enabled=1 but nothing happens... gcam doesn't work and stock cam continues to work ok. does anyone know what am I doing wrong?
vogiasf said:
on latest xiaomi.eu I can't get it to work. With magisk 19.2, I can't directly edit the /vendor build.prop (although I give root permission), so I tried systemless with MagiskHide props config module. I supposedly add persist.camera.HAL3.enabled=1 but nothing happens... gcam doesn't work and stock cam continues to work ok. does anyone know what am I doing wrong?
Click to expand...
Click to collapse
1. You can edit system build.prop or vendor build.prop, not both.
1a. Copy build.prop to any folder, edit, save.
2. Reboot to twrp, mount system or vendor.
2a. Twrp, advanced, file manager. Rename original build.prop to build.prop.bak, copy edited into system or vendor.
3. Reboot.
dzidexx said:
1. You can edit system build.prop or vendor build.prop, not both.
1a. Copy build.prop to any folder, edit, save.
2. Reboot to twrp, mount system or vendor.
2a. Twrp, advanced, file manager. Rename original build.prop to build.prop.bak, copy edited into system or vendor.
3. Reboot.
Click to expand...
Click to collapse
Thanks! I tried with vendor and it worked! if anyone else tries dont forget to chmod 644 otherwise stuck on boot
its working on my Mi Pad 4 Plus Lte with SuperiorOS. no build.prop editing is required. Thank you.
There is a much simpler method without involving editing any build.prop. Requires magisk. Connect the pad to PC with usb debugging enabled. Type:
adb shell
su
setprop persist.camera.HAL3.enabled 1
setprop persist.camera.eis.enabled 1
by order on PC. Check your tab and accept anything pop up. Reboot and it's good to go.
Works great on the latest Havoc Rom, rooted with Magisk. It also has video stabilization at 1080p! this is awesome! thank you!
I'm in pixel experience rom, and didn't work, I don't know what to do. I am not an expert.
Jagoflo said:
I'm in pixel experience rom, and didn't work, I don't know what to do. I am not an expert.
Click to expand...
Click to collapse
Works fine here, Pixel Experience Plus with Mi Pad 4 no build.prop editing required.
FYI, Urnyx's Gcam 7.3, including night mode, works out-of-the-box on Carbon ROM Pax (Android 10).