Database Users

WP=OFF, Does It Work Though

JakeDHS07 said:
Ok guys. I am gonna throw you all a bone here. Cause I'm nice like that. I haven't been able to figure out the bootloader but I have gained write protection off already.
Heres the process I used
go to play store and download an app called BusyBox Install (No Root) and install it and install BusyBox
If you don't already go and download Android Terminal Emulator from the play store
Now after you install emulator open and enter su
Accept the superuser prompt
now go back to the busybox app and copy the link it gives you and enter in emulator by pasting and hit enter
exit out of emulator
reopen emulator and ensure su is enabled by looking for the $
enter the following command busybox mount -o rw,remount system
Wait a minute or so
Reboot and profit!
Click to expand...
Click to collapse
Found this going through the turbo section, does anyone want to try this?

[email protected]:/ $ su
[email protected]:/ # busybox mount -o rw,remount system
tmp-mksh: busybox: can't execute: Permission denied
126|[email protected]:/ #

JH1108 said:
Found this going through the turbo section, does anyone want to try this?
Click to expand...
Click to collapse
It's not going to be anything as already stated. If it was that easy, it would've been done already.

Disable system write protection
Did anyone try to use this kernel extension to disable Write Protection?

carbonat87 said:
Did anyone try to use this kernel extension to disable Write Protection?
Click to expand...
Click to collapse
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app

kalel420 said:
I doubt it that's for HTC one
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
And what? A didn't ask what for is that extension.

carbonat87 said:
And what? A didn't ask what for is that extension.
Click to expand...
Click to collapse
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app

kalel420 said:
No you asked if anyone had tried it and I said I doubt it it's for HTC one kernel, but feel free to try that should give you a very nice brick I would think.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Seems you don't know anything about bricks. In the worst way it will give a soft brick which is easy to repair. If you can't help with this, what are you doing here?
I'm asking this question because it can be done only on unlocked bootloader.

carbonat87 said:
I'm asking this question because it can be done only on unlocked bootloader.
Click to expand...
Click to collapse
What makes You think it is only for unlocked bootloader? Anyway if You had unlocked bootloader you would not need to turn WP off.
Do we actually have any knowledge on how the write-protection is done in our phones? Is it the same way as in htc? Do we have the kernel code for this to look at? I did see that motorola released some code because of the gpl license, but is it there?

So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.

pizmak said:
So I did try this and no luck.
I took the latest sources from here:
https://github.com/flar2/wp_mod
I took the motorola kernel sources from here:
https://github.com/MotorolaMobilityLLC/kernel-msm
I compiled the module and copied it to the phone, but insmod did not work:
insmod init_module failed (operation not permitted)
I did run su in the console before trying the insmod. I have no idea why I can't insert the module into kernel, maybe it would have to be copied into /lib/modules/ and insmoded at boot, but that would require to burn the module into the system and flash it, but i have no time for that currently.
Click to expand...
Click to collapse
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.

carbonat87 said:
Ok, thanks for great work. I'll try to find someone who would be able to bake into system your compiled module and give us dump.
Click to expand...
Click to collapse
Just be careful with this, because if the module gets insmoded correctly, but does not work with our kernel and cause a reboot it will leave you with a brick and you would have to flash the filesystem once again without this module burnt in.

[HOW TO] Unlock tethering on Marshmallow 6.0

Google made a change from Android 4.1.2 which allows operators to know when users are using tethering and conveniently block tethered devices from accessing internet.
This can be fixed permanently using the following procedure and no root required on all rom types (stock, mod):
1) Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2) Enable USB debugging under Settings -> Developer options
3) Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4) Start an adb shell: adb shell
5) In the adb shell, run this command:
Code:
settings put global tether_dun_required 0
Tested on Nexus 5 & 6 with Marshmallow STOCK ROM

Just tried this on a freshly imaged Verizon Nexus 6 with Marshmallow, and I'm still getting the prompt for subscribing to tethering.

Can you do this with sqlite editor? If so, how?

net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.

Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk

trent999 said:
Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
I'm on Verizon and that's what I did also.
Sent from my Nexus 6 using Tapatalk

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You don't need root to do it, you can make the change via recovery and adb shell commands.

wishkah said:
Can you do this with sqlite editor? If so, how?
Click to expand...
Click to collapse
I'm not sure this can be done with sqlite editor anymore because when I go to the file path data>data>com.android.providers.settings>databases there is no longer a settings.db in that location to edit.
Maybe I'm missing something.... IDK???

didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
Click to expand...
Click to collapse
editing the build.prop worked for me! thanks guys/gals

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is Rooot needed to do this through adb?

That is my question, too.
For right now, I want to wait to unlock and root. I have reasons...
Can I edit and replace build.prop somehow under those conditions ?
I have ADB and fastboot both working and have pulled a copy of the stock Lollipop build.prop onto my laptop. I can edit it, but can I push the revised copy back with the boot loader still locked and no root ?
I read somewhere about achieving temporary root via fastboot booting twrp, instead of flashing, but that fails for me and I cannot find the referencing thread.
Sent from my VS985 4G using Tapatalk

Same boat here. I'd love to enable this, but don't want to do too much as I'm switching to a 6P in two weeks.
Do you need root to mod this? i'm not able to R/W system without it I assume?

So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.

Yes, the above is what I have been looking at, but it is important to realize it requires an unlocked bootloader, which requires a total phone wipe.
Plus I am concerned that this will prevent any future OTA, like to Marshmallow for mine, and also make it impossible to use Android Pay on that device, if those issues matter to you.
Yes, I know it is self-limiting to have a stock, locked N6.
Sent from my Nexus 6 using Tapatalk

pmhesse said:
Note that this does make the scary This device is corrupt... message appear at bootup.
Click to expand...
Click to collapse
Also note that this will also make you unable to apply any future OTAs (neither pushed to you by Google, nor sideloaded via ADB).
18 months ago, before /system validation became a thing, I would have recommended this method to a lot of "casual" modders - booting to TWRP to fix a couple things, and then going on their merry way with an unrooted "stock" (or close enough to it as to not matter) device.
Now that /system validation is a thing (breaks OTA applicability, dm-verity), I wonder if it's actually more advisable that people keep TWRP installed, and take the time to fully educate themselves about what they're doing, so that in the future they can fix things themselves more easily (and manually apply the monthly security patches, etc.).
I'm honestly not sure about the right answer - what do folks think?

pmhesse said:
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Click to expand...
Click to collapse
Ah. I don't have TWRP installed. Thats what I was missing. I went full stock besides my unlocked bootloader with Marshmallow. Not being able to Android Pay also sucks as I do use that. Wonder if I set it up first, then do this if it will let me still use the cards I load.

Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
editing the build.prop worked for me! thanks guys/gals
Click to expand...
Click to collapse
So the command did not work but adding the net..etc to build prop worked anyone in T-Mobile done this yet? Thanks

Correct, the command didn't work, but the line at end of build.prop did. Should work for any carrier.

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
Thank you!

[7.0] Enable google daydream (root needed)

I've managed to get daydream VR up and running on my LG G5.
I'm just gonna jump straight to the point and explain how I've managed to do this.
To set this up, you're gonna have to be on Android 7.0, and have root access.
First of all, enable ADB Debugging in your developer settings and test if it works on your computer, we are gonna need this later on.
Download and install the following apps;
Daydream apk http://www.apkmirror.com/apk/google-inc/daydream/daydream-1-1-161121023-release/daydream-1-1-161121023-android-apk-download/
VR Serviceshttp://www.apkmirror.com/apk/google-inc/google-vr-services/google-vr-services-1-1-141111507-release/
Daydream Keyboardhttp://www.apkmirror.com/apk/google-inc/daydream-keyboard/daydream-keyboard-1-0-release/daydream-keyboard-1-0-android-apk-download/
Any root explorer app, i used https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en
Open up the root explorer and navigate to: /system/etc/permissions
In the permissions folder, look for the following file and open it: "handheld_core_hardware.xml"
BE SURE TO CREATE A COPY THE FILE FIRST SO YOU HAVE A BACK-UP OF THE ORIGINAL HANDHELD_CORE_HARDWARE FILE
Add the following lines between the <permissions> tags
"<feature name="android.software.vr.mode" />"
"<feature name="android.hardware.vr.high_performance" />"
Reboot your phone. A lot of things will crash when it starts up, this happened to me too. This happens because the file we just edited doesn't have the proper permissions set up.
To fix this problem we're gonna open up an ADB Shell on the computer.
Once you have ADB open do the following commands:
SU (and grant superuser permissions on phone)
mount -o rw,remount -t /system
chmod 644 /system/ect/permissions/handheld_core_hardware.xml
mount -o ro,remount -t /system
reboot
Now, if we open the daydream app we can launch daydream by pressing the cardboard button in the corner.
You can also use a secondary android phone as a controller, if you have one. Google has a guide set up for this https://developers.google.com/vr/daydream/controller-emulator
Sources: https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other/
If you have any questions, feel free to leave a comment and i'll get back to you as soon as i can!

Thank you
Successfully tried this on fulmics 1.0. Even didn't have to chmod after reboot, config file already was 644. Thank you a lot for this tutorial, its great to know we can use g5 with daydream, in my opinion the experience with the qhd lcd screen is good enough, amoled is not a (real) must.

tatsujin said:
Successfully tried this on fulmics 1.0. Even didn't have to chmod after reboot, config file already was 644. Thank you a lot for this tutorial, its great to know we can use g5 with daydream, in my opinion the experience with the qhd lcd screen is good enough, amoled is not a (real) must.
Click to expand...
Click to collapse
I'm glad it works for you! i think i had to chmod since i'm on stock v20a. This will probably (don't take my word for it though) work on a lot of newer high-end phones running on 7.0 or higher.

There's a way to use it without NFC ?

Confirmed on Xiaomi Mi5
Works perfectly on a Xiaomi Mi5 with a Moto G controller emulator both running on LineageOS 14.1.
Only a couple of Games wont Run, but almost everyone does and runs smoothly.

did so just without rooting and editing the xml File
Everything Works fine - the g5 says "Hold the Home Button...", my old Samsung galaxy s4 (Controller Emulator) says Bluetooth (Connected)
but if i push the Controller Home Button on the s4 nothing happend on the g5
are you shure it will work with root and editing xml File?
i Don t want to root the g5
thanks

xamax88 said:
did so just without rooting and editing the xml File
Everything Works fine - the g5 says "Hold the Home Button...", my old Samsung galaxy s4 (Controller Emulator) says Bluetooth (Connected)
but if i push the Controller Home Button on the s4 nothing happend on the g5
are you shure it will work with root and editing xml File?
i Don t want to root the g5
thanks
Click to expand...
Click to collapse
I haven't gotten around to figuring out how the controller emulator actually works, you need to initiate the pairing on the G5 (or the phone that's running daydream) as far as i know. I have no idea if it works without root since you're editing a build.prop, i couldn't tell you since i'm always rooted.

night.shadows said:
There's a way to use it without NFC ?
Click to expand...
Click to collapse
How do you mean use it without nfc? If you're talking about the controller emulator, open the link in the OP (original post) to the google page that provides you with the controller emulator. It explains pretty much everything you need to know when it comes down to that.

TFDRA said:
How do you mean use it without nfc? If you're talking about the controller emulator, open the link in the OP (original post) to the google page that provides you with the controller emulator. It explains pretty much everything you need to know when it comes down to that.
Click to expand...
Click to collapse
No I meant use daydream on non-nfc phone, but I've found in the developers options, thanks !

Just keeps crashing
So i go into the daydream app and go into the actual vr mode and it just crashes the app, idk what to do from here. I bought the daydream headset and i have a oneplus 3t so I dont really know what to do and it sucks cause i really wanna use it.

statertot said:
So i go into the daydream app and go into the actual vr mode and it just crashes the app, idk what to do from here. I bought the daydream headset and i have a oneplus 3t so I dont really know what to do and it sucks cause i really wanna use it.
Click to expand...
Click to collapse
Check out this thread on the oneplus forums, someone managed to get it working on the oneplus3.
I think the proccess would be fairly similar for you since you're probably using oxygenOS as well.
https://forums.oneplus.net/threads/major-announcement-daydream-vr-fully-running-on-op3-oxygenos.479505/

TFDRA said:
Check out this thread on the oneplus forums, someone managed to get it working on the oneplus3.
I think the proccess would be fairly similar for you since you're probably using oxygenOS as well.
https://forums.oneplus.net/threads/major-announcement-daydream-vr-fully-running-on-op3-oxygenos.479505/
Click to expand...
Click to collapse
Hi I've tried this method but I'm stuck, when it try to modify the permissions of the file the terminal keeps saying its a read only file system, help please :crying:

matias041198 said:
Hi I've tried this method but I'm stuck, when it try to modify the permissions of the file the terminal keeps saying its a read only file system, help please :crying:
Click to expand...
Click to collapse
If you have root, you can try running these commands in a terminal:
Code:
su
mount -o remount rw /

SkyrisBactera said:
If you have root, you can try running these commands in a terminal:
Code:
su
mount -o remount rw /
Click to expand...
Click to collapse
I've tried with no success
Code:
victara:/ $ su
victara:/ # mount -o rw,remount -t /system
/system/etc/permissions/handheld_core_hardware.xml <
chmod: chmod '/system/etc/permissions/handheld_core_hardware.xml' to 100644: Read-only file system
1|victara:/ # mount -o remount rw /
mount: '/' not in /proc/mounts
I just realised I can't change permissions of any file in my phone :crying:
I've attached my handheld core hardware file, it's from my Moto x 2014 (VICTARA). Can anyone please make it .xml, set permissions and make a flashable .zip? Thanks
EDIT: I was able to mount the /system using root explorer somehow, after that it was straight forward

Hi, i'm planning on buying the lg g5 and the daydream view headset, is it worth it? does it work well? i want to know if daydream games are working with the daydream controller too. Thanks a lot!!!

guideahon said:
Hi, i'm planning on buying the lg g5 and the daydream view headset, is it worth it? does it work well? i want to know if daydream games are working with the daydream controller too. Thanks a lot!!!
Click to expand...
Click to collapse
Maybe you should get a phone with oficial daydream support

Hi, i tried all the steps from here, the daydream app crashes and i cant play any daydream games, do i have to install any specific version?? i'm on stock 20a

Hi, followed the guide on a LG G2 with BOBO-VR Z5 with controller, everythings fine except the pairing of the controller through bluetooth.
"No controller found. Make sure that your controller is charged and next to your phone, then try again."
Any idea?

Install Magisk Module Daydream Enabler
Install Magisk Module Daydream Enabler For solve this issue in a better way.

build.prop missing in OPR1.170623.026.8.1.10 (Android O)?

Hi,
I recently got my M1 A1 from Elisa, in Estonia(packages says Global Version). I've been looking for a guide to enable camera2 API, and since I'm not interested in root or other functionalities, I figured I could only edit build.prop file in /system with the relevant
Code:
persist.camera.HAL3.enabled=1
line.
My steps so far:
1. Unlock the bootloader.
2.Temporarily boot into TWRP:
Code:
PS C:\platform-tools> .\adb reboot bootloader
PS C:\platform-tools> .\fastboot devices
28833e59 fastboot
PS C:\platform-tools> .\fastboot boot recovery-tissot.img
downloading 'boot.img'...
OKAY [ 0.755s]
booting...
OKAY [ 0.592s]
finished. total time: 1.353s
3. Mount /system from TWRP
4. Try to pull out build.prop:
Code:
PS C:\platform-tools> .\adb pull /system/build.prop c:\platform-tools
adb: error: failed to stat remote object '/system/build.prop': No such file or directory
At this point, I was starting to worry: wrong TWRP, /system was not mounted properly, etc.. But then I tried:
Code:
PS C:\platform-tools> .\adb pull /system/default.prop
/system/default.prop: 1 file pulled. 0.0 MB/s (893 bytes in 0.052s)
...and it worked perfectly:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.oem_unlock_supported=true
ro.zygote=zygote64_32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.appimageformat=lz4
pm.dexopt.first-boot=quicken
pm.dexopt.boot=verify
pm.dexopt.install=quicken
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
debug.atrace.tags.enableflags=0
ro.logdumpd.enabled=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Wed Jan 10 14:39:53 WIB 2018
ro.bootimage.build.date.utc=1515569993
ro.bootimage.build.fingerprint=xiaomi/tissot/tissot_sprout:8.0.0/OPR1.170623.026/8.1.10:user/release-keys
persist.sys.usb.config=mtp
So, my question: where does that build.prop live or hides? And can default.prop be used instead for the same purposes as build.prop?
What other steps I've tried so far:
- factory reset(twice);
- full firmware flash with MiFlash(and factory reset after);
- different versions of TWRP(best one from here:https://forum.xda-developers.com/showpost.php?p=75357241&postcount=817 )

Oh, and what I've noticed weird is this message, when invoking adb shell:
Code:
PS C:\platform-tools> .\adb shell
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered

/system/system/build.prop

You should be interested in root in this case, because whenever you mount the system with write privileges which you do, you loose OTAs. Magisk let you to modify the system systemlessly and whenever you receive OTA, you can install it.

sorry but which is the utility of OPR..?

maross said:
You should be interested in root in this case, because whenever you mount the system with write privileges which you do, you loose OTAs. Magisk let you to modify the system systemlessly and whenever you receive OTA, you can install it.
Click to expand...
Click to collapse
I guess I'll just dirty flash new firmwares with MiFlash . Maybe even restore original build.prop, MiFlash, then modify build.prop again. Rooting sometimes affects some apps, i.e. some banking apps won't install, Neflix won't let you download content, and so on.

sidbyron said:
sorry but which is the utility of OPR..?
Click to expand...
Click to collapse
It's just a naming convension for the firmware filename that Xiaomi uses.

quad_bx said:
I guess I'll just dirty flash new firmwares with MiFlash . Maybe even restore original build.prop, MiFlash, then modify build.prop again. Rooting sometimes affects some apps, i.e. some banking apps won't install, Neflix won't let you download content, and so on.
Click to expand...
Click to collapse
Just use Magisk with Magisk hide feature. You will achieve the same with less effort. Btw. direct modification of system will break Safetynet as far as I know, so you won't be able to install Netflix anyway [emoji846]

_mysiak_ said:
Just use Magisk with Magisk hide feature. You will achieve the same with less effort. Btw. direct modification of system will break Safetynet as far as I know, so you won't be able to install Netflix anyway [emoji846]
Click to expand...
Click to collapse
Well, let's take for example TWRP installation.... The official variant does not work on the last Oreo build(internal storage size is seen as 0, can't install). And for Magisk, I could not find a detailed tutorial to follow.
Anyway, let me see if I can find the hidden build.prop and what happens.

quad_bx said:
Anyway, let me see if I can find the hidden build.prop and what happens.
Click to expand...
Click to collapse
So, I've found it. On the plus side, editing it and re-uploading it did not trip SafetyNet. But... camera2 API is not enabled
I've even managed to edit it twice, in system_a and system_b, same result. Rebooting, clearing the app cache for the apps where I wanted to get RAW shooting did not help either.

I confirm build.prop is in /system/system after mounting it with TWRP.
I can pull it, change it, and push it, but nothing actually changes in the phone.
I confirm that going into "adb shell" generates that error.
Issue is: I DON'T WANT to install Magisk, I DON'T WANT to root.
I want auxiliary tele lens exposed to OpenCamera and gCam porting, and I want Whatsapp forced to use HAL1 specifics (as inner Whatsapp camera brakes after enabling Camera2api).
It means to convert this line:
camera.hal1.packagelist=com.skype.raider,com.google.android.talk
To this
camera.hal1.packagelist=com.skype.raider,com.google.android.talk,com.whatsapp
... and nothing more.
To me it sounds stupid to root, installa Magisk and leave the phone unlocked just to tell Whatsapp to use HAL1.
Also for exposing aux camera, it means to turn:
#Expose aux camera for below packages
vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,com.huaqin.factory,com.mi.AutoTest
#add by yaoshaorong for Expose aux camera for D2AO-892 for packagelist can't more than 91 byte
vendor.camera.aux.packagelist2=com.android.systemui
to
#Expose aux camera for below packages
vendor.camera.aux.packagelist=org.codeaurora.snapcam,com.android.camera,com.huaqin.factory,com.mi.AutoTest
#add by yaoshaorong for Expose aux camera for D2AO-892 for packagelist can't more than 91 byte
vendor.camera.aux.packagelist2=com.android.systemui,net.sourceforge.opencamera
But it simply doesn't work.
Is this the right file, or do we need to modify something else?

Dm verity and the related error correction changes your modifications back to the stock build.prop

Android 9 (Pie) for Wileyfox?

Since updating to Oreo battery has not been good.
I'm hoping Wileyfox will be giving us Android Pie which will fix the notification and battery issues.

KraftwerkElectro said:
Since updating to Oreo battery has not been good.
I'm hoping Wileyfox will be giving us Android Pie which will fix the notification and battery issues.
Click to expand...
Click to collapse
You can install an unofficial Project Treble and find the GSI Android Pie.

JavaVOBIS said:
You can install an unofficial Project Treble and find the GSI Android Pie.
Click to expand...
Click to collapse
Have you tried it, and does it fix the above problems?
Do you have a link?

KraftwerkElectro said:
Have you tried it, and does it fix the above problems?
Do you have a link?
Click to expand...
Click to collapse
I tried Project Treble based on Android Oreo and Pie - I didn't really like it.
Firstly, the device certification may fail (you need to install the Magisk module).
Secondly, on some GSI there is such a problem that the phone simply does not see the headphones.
Thirdly, for some GSI Pie it is necessary to install additional patches for the camera or NFC to work. Also it should be taken into account that there are other bugs that, for the time being, cannot be fixed.
But if you find a stable GSI, then you can use it. I recommend AOSP GSI.

KraftwerkElectro said:
Since updating to Oreo battery has not been good.
Click to expand...
Click to collapse
Hi!
Usually there are 6 working cores out of 8. This is the cause of bad energy saving. You could using Kernel Adiutor or editing file /sys/devices/system/cpu/cpu0/core_ctl/min_cpus.
But on version 8.1, the value is restored after the change, so it must be committed.
You must execute this simple script after each reboot. (You can move it in init.d dir) Dont forget give execution rights to script ex. chmod 777
Code:
#!/system/bin/sh
chmod 777 /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
echo 0 >> /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
chmod 555 /sys/devices/system/cpu/cpu0/core_ctl/min_cpus

PHPoenX said:
Hi!
Usually there are 6 working cores out of 8. This is the cause of bad energy saving. You could using Kernel Adiutor or editing file /sys/devices/system/cpu/cpu0/core_ctl/min_cpus.
But on version 8.1, the value is restored after the change, so it must be committed.
You must execute this simple script after each reboot. (You can move it in init.d dir) Dont forget give execution rights to script ex. chmod 777
Code:
#!/system/bin/sh
echo 0 >> /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
chmod 555 /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
Click to expand...
Click to collapse
Thanks for the reply, but I'm no expert and the script you mention, I don't understand how to do this, without step by step instructions.
Once I've done it once it will be easier the next time.

Do you know if this is affecting a lot of mobiles that run Oreo?

I don't understand how to do this, without step by step instructions.
Once I've done it once it will be easier the next time.
Click to expand...
Click to collapse
Do you have superuser? Init.d?

PHPoenX said:
Do you have superuser? Init.d?
Click to expand...
Click to collapse
Sorry, but I don't even know what 'Init.d' means.

Has anyone run this script? Does it work?

I just ran it, anyway to check what its done?

Maz1994 said:
I just ran it, anyway to check what its done?
Click to expand...
Click to collapse
You can see that 4 of 8 cores is working if there isn`t any heavy running processes in Kernel Adiutor. Also battery life will be increased.
You can try disable cores using Kernel Adiutor, but it don`t working on Oreo.
My script commits and prevent from editing this value using chmod

KraftwerkElectro said:
I'm hoping Wileyfox will be giving us Android Pie
Click to expand...
Click to collapse
I have found Android P but it not official Lineage OS. It has a lot of bugs. Camera, fingerprint scanner, nfc, wifi and ringtone dont working. Also SELinux is permissive.
http://4pda.ru/forum/index.php?showtopic=894518&view=findpost&p=80814647