Related
I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!
If you're on another Lollipop device the tricky part in making the V4A driver stick, is to manually edit the audio_effects.conf on the "Vendor" partition. V4A only writes to the system audio_effects.conf.
trackloading said:
I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!
Click to expand...
Click to collapse
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??
Lw00d said:
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??
Click to expand...
Click to collapse
That's the one I'm using, so I don't have to be in permissive mode...
I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?
dom2684 said:
I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?
Click to expand...
Click to collapse
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?
igothacked1 said:
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?
Click to expand...
Click to collapse
Ahh gotcha thanks
this work great for me..
what are some preferred settings??
I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.
igothacked1 said:
I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.
Click to expand...
Click to collapse
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.
cor_mann said:
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.
Click to expand...
Click to collapse
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now
igothacked1 said:
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now
Click to expand...
Click to collapse
Good to hear. I'm not sure why some people have to add the lines and others don't.
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
You're right: I'm running Lollipopalooza ROM. That explains it.
Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9
mrshades812 said:
Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9
Click to expand...
Click to collapse
I haven't gotten mine to work either. I just noticed it. However, my Oneplus One has IRS working on 5.0.1. It could be how the driver is behaving?
trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
Igothacked said he was using my kernel/ramdisk, I'm not sure what ROM, but the kernel in my boot.img is completely stock, the only edits were to the ramdisk, and I'm positive that would not effect anything with this. I'm not sure about what Roms were being used, I guess it could make a difference, maybe permissions are slightly different or there is a difference with some symlinks with different roms and stock.
Thanks, also working on stock Acer A1-810 too.
I'm also running theLollipopalooza ROM and had to edit the file manually before the driver would install. All seems to be working fine now though. Thanks☺
Nevermind I re-read
I removed Album as the default picture launcher like done by venkat kamesh (link to original thread is at the end) for other Xperia models following his nice tutorial , after installing you can choose which app will be used for opening your pictures out of the camera.
Updated 27/03/16
Instructions for MM (use the attached file SemcCameraUI-generic-xhdpi-release.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI-generic-xhdpi-release.apk to "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI-generic-xhdpi-release.apk
delete oat folder
reboot - enjoy!
Instructions for LP (use the attached file SemcCameraUI.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI.apk to "/system/priv-app/SemcCameraUI/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI.apk
reboot - enjoy!
Big thanks to venkat kamesh!!!
Original threads
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/mod-camera-album-default-app-t3139667
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/tut-how-to-remove-album-default-xperia-t3219268
will it work with marshmallow?
No, this version is only working for Lollipop.
I will make a MM version in the following days and post it here.
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
I managed to modify the apk, unfortunately it doesn't start any longer, no idea why ... Any hints what could go wrong after recompiling the apk with apktool and cause the app to crash? I did it the same way as with LP ...
civicsr2cool said:
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
Click to expand...
Click to collapse
This doesn't work on my MM system, I guess its only for LP ...
Thorstenk said:
This doesn't work on my MM system, I guess its only for LP ...
Click to expand...
Click to collapse
Yeah, I haven't made the jump to mm for a lot of reasons, xposed modules being a big one
Should work by now with MM, see first post for instructions!
Happy Easter
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
sheraro said:
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
Click to expand...
Click to collapse
On my device it works without having the oat-folder and as far as I know the oat-folder won't be created again, because the apk is deodexed ...
I just downloaded my file again and did the whole process again and it still works .
Did you do it (copy the file and set the permissions) via adb?
Could you try it again?
md5 is: 43774a75b358b255ca629c0bfd56e289
md5 is correct, I set permissions with total commander, I did it with root explorer too, the permissions are correctly set (rw-,r--,r--) but camera app is nowhere to be found ... I will try with adb and see
The camera is missing after I did this.
Tried it on Marshmallow, can you help bro?
Followed the instructions carefully. Thank you
Tried via adb, doesn't work as well.
Upon checking the file SemcCameraUI-generic-xhdpi-release.apk its still my default apk and not the one i pushed with adb (the one i downloaded here), the oat folder was still there as well. Pretty sure I deleted it via adb as well and no error showed up.
Update: Tried it again via adb, this time SemcCameraUI-generic-xhdpi-release.apk pushed properly with correct permissions and oat folder deleted as well. But the camera is now missing again. Any ideas? Thank you
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Thanks but tried it like 3 times already, no luck still.
Not working for me either on 6.0.1 -.-
Seems like .apk is broken or something (when opening .apk get parsing error )
and when replacing original .apk Camera disappears like the other ones said
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Hello, what about using Xposed to create a module like the one working for Lollipop?
it would be a lot easier for people instead of replacing files, messing with odex files and It could probably support all the MM releases. If i have some time i could try to do it, but i'm not as skilled as you.
Apart from that, thank you a lot for the work! I've been searching this since ever.
modified camera for MM 6.0.1
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
bruno.trudo said:
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
Click to expand...
Click to collapse
can you make a new one with .253 plz ?
Sure, I can. Please send me appropriate SemcCameraUI-generic-xhdpi-release.apk file.
I am still on .224
Thanks! Here it is : https://drive.google.com/file/d/0B9nyD39hGfrkTWxOczkwdXZZcnc/view?usp=drivesdk
Anyone made the Measure app work on their OP3?
I'm also having problems what's brought me here. I was trying different versions and nothing works :/
Yep, works perfectly fine here. Do other AR Core apps work for you?
Actually I have a problem with installing AR Core itself, do you have a link to proper version?
Also can't get it to work. I tried a few different versions of the ARCore apk now, but when opening the measure app all I get is different error messages.
Fobos531 said:
Yep, works perfectly fine here. Do other AR Core apps work for you?
Click to expand...
Click to collapse
Do you have a OnePlus 3 or 3T?
I've had ARC running earlier, but can't get the Measure app to work. I can install both APKs, but I get error when starting the Measure app.
zhuoyang said:
Do you have a OnePlus 3 or 3T?
Click to expand...
Click to collapse
I have the 3.
What I did was the following:
1) Download and install the latest ARCore apk from apkmirror: https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-3-180604066-release/
2) Sideload an ARCore-enabled app like Just a Line or IKEA Place (again, from APK Mirror) and launch it so it crashes the first time.
3) Using a root explorer, go to /data/data/com.google.ar.core/files/device_profile_database/ and find the file for the OnePlus 3T (it will have "OnePlus3T" in its name).
4) Rename/Remove the "T" from "OnePlus3T" in the file name.
5) Launch an ARCore-enabled app again and it should work flawlessly.
Fobos531 said:
I have the 3.
What I did was the following:
1) Download and install the latest ARCore apk from apkmirror: https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-3-180604066-release/
2) Sideload an ARCore-enabled app like Just a Line or IKEA Place (again, from APK Mirror) and launch it so it crashes the first time.
3) Using a root explorer, go to /data/data/com.google.ar.core/files/device_profile_database/ and find the file for the OnePlus 3T (it will have "OnePlus3T" in its name).
4) Rename/Remove the "T" from "OnePlus3T" in the file name.
5) Launch an ARCore-enabled app again and it should work flawlessly.
Click to expand...
Click to collapse
... or it replies to you then with the error: " This device does not support AR" instead of hanging at start ^^
Fobos531´s instructions seem to work well for me. I can use the measure app now. Though I'm not yet sure how exact it is. Haven't had much time yet for testing it.
For reference, I've got OP3 (not T) running NitrogenOS 8.1
Fixed, I completely kicked ARCore APK and reinstalled. Now it works. AR Stickers does not, but I think that I use the wrong APK...
Fobos531 said:
I have the 3.
What I did was the following:
1) Download and install the latest ARCore apk from apkmirror: https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-3-180604066-release/
2) Sideload an ARCore-enabled app like Just a Line or IKEA Place (again, from APK Mirror) and launch it so it crashes the first time.
3) Using a root explorer, go to /data/data/com.google.ar.core/files/device_profile_database/ and find the file for the OnePlus 3T (it will have "OnePlus3T" in its name).
4) Rename/Remove the "T" from "OnePlus3T" in the file name.
5) Launch an ARCore-enabled app again and it should work flawlessly.
Click to expand...
Click to collapse
Hi,
On my op3 I tried this.... I used the app JUST A LINE..... It did FC and then I went into the said path but only 2 folders there CACHE and CODE CACHE.... I Then i tried directly installing the MEASURE apk from apkmirror.... I it installed but same thing FC...
And again no folders in the said path except for the cache and code cache...
Any ideas please.
Regards
gregferns said:
Hi,
On my op3 I tried this.... I used the app JUST A LINE..... It did FC and then I went into the said path but only 2 folders there CACHE and CODE CACHE.... I Then i tried directly installing the MEASURE apk from apkmirror.... I it installed but same thing FC...
And again no folders in the said path except for the cache and code cache...
Any ideas please.
Regards
Click to expand...
Click to collapse
Can you try manually creating the file in that case? Create a "files" folder, inside create a folder named "device_profile_database" and inside that folder create a file named "device_profile_OnePlus3_colon_8.textproto" (make sure .textproto is the extension). Put this in the file: https://gist.github.com/fobos531/64cd45838ffb6a143a83306882d208b6
Also the file should have read+write permissions only for the owner (you can do "chmod 600 /data/data/com.google.ar.core/files/device_profile_database/device_profile_OnePlus3_colon_8.textproto") to achieve this.
gregferns said:
Hi,
On my op3 I tried this.... I used the app JUST A LINE..... It did FC and then I went into the said path but only 2 folders there CACHE and CODE CACHE.... I Then i tried directly installing the MEASURE apk from apkmirror.... I it installed but same thing FC...
And again no folders in the said path except for the cache and code cache...
Any ideas please.
Regards
Click to expand...
Click to collapse
Same happened to me. Problem was a too old apk (didn't use the version from the download link above at first, thought I had the right one)
Sure you used that one?
Fobos531 said:
Can you try manually creating the file in that case? Create a "files" folder, inside create a folder named "device_profile_database" and inside that folder create a file named "device_profile_OnePlus3_colon_8.textproto" (make sure .textproto is the extension). Put this in the file: https://gist.github.com/fobos531/64cd45838ffb6a143a83306882d208b6
Also the file should have read+write permissions only for the owner (you can do "chmod 600 /data/data/com.google.ar.core/files/device_profile_database/device_profile_OnePlus3_colon_8.textproto") to achieve this.
Click to expand...
Click to collapse
Will try this and revert....
Oehrly said:
Same happened to me. Problem was a too old apk (didn't use the version from the download link above at first, thought I had the right one)
Sure you used that one?
Click to expand...
Click to collapse
Yes, i had used the latest one,... in fact there is a newer one than the link too. tried that also... but always FC... i had an old one lying around which was posted by @SKULSHADY and that installed... now will try the above method and see..
will revert.
EDIT :: TRIED IT WITH SKULSHADY'S ARCORE INSTALLED BUT DIDNT WORK.... TRIED UPDATING THE ARCORE BY INSTALLING LATEST OVER SKULSHADY's .... Didnt get installed... WILL TRY TOMORROW BY REMOVING and REINSTALLING THE LATEST ONE AND SEEING...
thanks
Greg
Fobos531 said:
I have the 3.
What I did was the following:
1) Download and install the latest ARCore apk from apkmirror: https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-3-180604066-release/
2) Sideload an ARCore-enabled app like Just a Line or IKEA Place (again, from APK Mirror) and launch it so it crashes the first time.
3) Using a root explorer, go to /data/data/com.google.ar.core/files/device_profile_database/ and find the file for the OnePlus 3T (it will have "OnePlus3T" in its name).
4) Rename/Remove the "T" from "OnePlus3T" in the file name.
5) Launch an ARCore-enabled app again and it should work flawlessly.
Click to expand...
Click to collapse
This works well for me.
I have the Skulshady's ARCore before. I uninstall it and install the latest version from apkmiror, then follow this guide and works fine.
Thanks @Fobos531 , your way works for me like a charm. OOS 5.0.3 with Magisk. Installed ArCore 1.3 from apkmirror, then Ikea app, let it crash one time, edited the filename and everything works now.
i installed the lasr ar core from apk mirror,
and downloaded measures from play store
and i didnt do anything else
and its working fine.
Sent from my ONEPLUS A3003 using Tapatalk
may_moon911 said:
i installed the lasr ar core from apk mirror,
and downloaded measures from play store
and i didnt do anything else
and its working fine.
Click to expand...
Click to collapse
If you are able to download measure app from play store then it means, your phone supports this, you don't need to do anything else
So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?
I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop
bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?
Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?
truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom
Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.
hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions
I think the root is not perfect, I can't change the permissions of the files
carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.
hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet
What are you trying to achieve?
the terminal command to try to mount as RO would you know?
_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files
carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.
I wanted to change the audio files regarding the volume, I wanted it a little higher
carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
i read android 10 problem, would you recommend me to mount with termux, installing vim?
_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls
carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module
Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?