I've just flashed the stock 3.2.0 ROM and for the first time rooted using the systemless method and have installed the systemless version of xposed. How do I change the DPI on the OP3 with this setup? Thanks in advance!!
No need for xposed, use Le DPI changer on plays store and select 'Use Shell WM' to apply, it works perfectly.
Striatum_bdr said:
No need for xposed, use Le DPI changer on plays store and select 'Use Shell WM' to apply, it works perfectly.
Click to expand...
Click to collapse
Lame, it's not working... supersu is working, and so is xposed, adaway, YouTube adaway etc... I selected Shell WM as you said.
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
Lame, it's not working... supersu is working, and so is xposed, adaway, YouTube adaway etc... I selected Shell WM as you said.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Turn off Shell WM, and press edit build.prop then reboot. It worked for me. Hope i helped
@_MartyMan_ Are you using systemless root? I heard that you shouldn't mess with the system if you are.
Sent from my ONEPLUS A3000 using Tapatalk
Edit: Hahaha, it worked, thanks!
rickyx32 said:
@_MartyMan_ Are you using systemless root? I heard that you shouldn't mess with the system if you are.
Sent from my ONEPLUS A3000 using Tapatalk
Edit: Hahaha, it worked, thanks!
Click to expand...
Click to collapse
Amm yes, i'm using systemless root.
Your welcome
Do you have a link to the systemless root? I don't seem to find it or I am looking wrong.
superiscch said:
Do you have a link to the systemless root? I don't seem to find it or I am looking wrong.
Click to expand...
Click to collapse
Here you go man, this is the latest systemless root SuperSU made specifically for our OP3 that can be flashed with TWRP. Came out this morning.
https://www.androidfilehost.com/?fid=24591000424944601
Sent from my ONEPLUS A3000 using Tapatalk
In my case, I changed DPI by adb commands.
But I have some problem on some apps. Is there any difference between adb method and chaning build.prop?
I've not rooted my device but I would consider if there's differences with 2 methods.
jerrygo2 said:
In my case, I changed DPI by adb commands.
But I have some problem on some apps. Is there any difference between adb method and chaning build.prop?
I've not rooted my device but I would consider if there's differences with 2 methods.
Click to expand...
Click to collapse
What kind of issues are you having and at what DPI?
Sent from my A0001 using Tapatalk
rickyx32 said:
I've just flashed the stock 3.2.0 ROM and for the first time rooted using the systemless method and have installed the systemless version of xposed. How do I change the DPI on the OP3 with this setup? Thanks in advance!!
Click to expand...
Click to collapse
It is the same method, whether you are systemless or not. You just need root access to mount system in r/w so you can edit the build.prop file. Obtaining the root access is determined by the app itself, not the root method. Some file explorers may not like systemless though...ES file explorer for example. However, you can change the build.prop via terminal or adb mode as well. There are many ways to change the DPI. In regards to your root method, that does not really matter.
Changing DPI is a little bit different for OnePlus phones. I did it by adding a line to my build.prop file. In other phones the line is already there and you just have to change the value.
Steps:
1. Use file explorer with root access. I use root explorer pro, but there are free apps as well.
2. Go to /system/ and locate build.prop file
3. Long press the file and select 'open in text editor'
4. Add the line 'ro.sf.lcd_density=xxx' where xxx is your desired DPI.
5. Save and close
6. Reboot
7. Profit
rickyx32 said:
What kind of issues are you having and at what DPI?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Adm method always giving problem not croping correctly play store icons get big so your rooted and you can use le dpi changer or build.prop
Sent from my ONEPLUS3
how is systemless different from normal (noob) and why do it that way?
I've developed a systemless changer. This will modify the boot.img (init.supersu.rc) while the installation of supersu to add an additional entry which changes the DPI to the wanted value. It was necessary this way as the init scripts located in /su/su.d are loading too late to be able to change the DPI anymore.
1. Simply drop a file into /data/custom_ramdisk_patch.sh with the following content, it will change the DPI to 401:
Code:
#!/sbin/sh
COM=/tmp/supersu/common
echo "custom boot patcher"
echo "COM: $COM" > /tmp/hi
cp $COM/init.supersu.rc /tmp/init.supersu.rc
MFILE=/tmp/init.supersu.rc
echo "" >> $MFILE
echo "on init" >> $MFILE
echo " setprop ro.sf.lcd_density 401" >> $MFILE
/su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 750 init.supersu.rc $MFILE >> /tmp/hi
if [ $? -ne 0 ]; then
echo "patch failed" >> /tmp/hi
exit 1
fi
exit 0
2. install systemless supersu.zip (at least 2.76) again
3. profit
This could be improved in such a way, that a script file is executed on init to allow any build.prop changes or third party execution as well, but currently I'm only interested in the DPI change
Related
I'm on Bugless Beast Jellybean (8-7 build) running Franco's kernel. None of my kernel settings, minfree settings, or VM cache settings will "stick" after a boot. I noticed I did not have a /etc/init.d folder or a syscntl.cfg file anywhere on my system. I tried manually adding these files, adding scripts, and totally opening permissions (0777) on the folders and files, then rebooting into recovery, wiping cache/dalvik, and rebooting. Nothing still sticks. Is there a way to get this to work without unpacking / repacking my boot image, preferably a way to add the init.d folder (manual or flash a .zip), or secondly using some sort of auto-script tool? I have my build.prop set up how I want, and that sticks. Thanks for any suggestions, and sorry if this has been answered elsewhere - I'm a noob to the site, but I did search first!
You should install supersu from the market, open it and it will update binary and be the default su application. All settings will stick than
Sent from my Galaxy Nexus using Tapatalk 2
Different than Superuser?
dascjb said:
You should install supersu from the market, open it and it will update binary and be the default su application. All settings will stick than
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You're thinking of a different app than the Superuser (by chainsdd) app? If so, I'll give it a shot. Thanks!
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Trying it out!
dascjb said:
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll give it a shot. Thanks again.
Partial Fix
dascjb said:
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So, supersu fixed one of my issues - the Franco kernel settings now stick (thanks!). However, I still can't get minfree settings to stick after a boot. It seems that any scripts I write in /etc/init.d/* are not being read. Suggestions on how to get minfree and VM cache settings to stick?
pkgnex said:
So, supersu fixed one of my issues - the Franco kernel settings now stick (thanks!). However, I still can't get minfree settings to stick after a boot. It seems that any scripts I write in /etc/init.d/* are not being read. Suggestions on how to get minfree and VM cache settings to stick?
Click to expand...
Click to collapse
Do you have busybox installed?
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
Also did you add sysctl.conf in system? and not syscntl.cfg?
sysctl
dascjb said:
Do you have busybox installed?
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
Also did you add sysctl.conf in system? and not syscntl.cfg?
Click to expand...
Click to collapse
I do have the latest busybox installed.
As of right now, I actually am re-trying one step at a time... at the moment I have no sysctl.conf, trying to get /etc/init.d/tweaks file to work, still no luck.
Not sure if it is required but all files in my init.d all started with a number ie. 98tweaks
Sent from my Galaxy Nexus using Tapatalk 2
Yeah
dascjb said:
Not sure if it is required but all files in my init.d all started with a number ie. 98tweaks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've actually been doing that just in case!
Did your rom come with an init.d folder, or did you flash something to get it or create it "by hand" like I'm trying to do?
pkgnex said:
Yeah, I've actually been doing that just in case!
Did your rom come with an init.d folder, or did you flash something to get it or create it "by hand" like I'm trying to do?
Click to expand...
Click to collapse
The ROM I am using now came with the init.d support. Not sure if it matters but it looks like there is a symlink from /etc to /system/etc
symlink?
dascjb said:
The ROM I am using now came with the init.d support. Not sure if it matters but it looks like there is a symlink from /etc to /system/etc
Click to expand...
Click to collapse
Which means? How do I handle this?
pkgnex said:
Which means? How do I handle this?
Click to expand...
Click to collapse
you would need to use terminal emulator app or, easier, adb. If you connect your phone and type in 'adb shell' you will get a terminal on phone. You should be able to just type
su
ln -s /system/etc etc
this will make the symbolic link from the root of the device to /system/etc
alternate method
pkgnex said:
Which means? How do I handle this?
Click to expand...
Click to collapse
Looking into work-around's, found "smanager" app to run scripts. It successfully executed my minfree script, so if the "set at boot" option works, it will be what I need (albeit through and app and not purely at the system level). It's progress!
dascjb said:
you would need to use terminal emulator app or, easier, adb. If you connect your phone and type in 'adb shell' you will get a terminal on phone. You should be able to just type
su
ln -s /system/etc etc
this will make the symbolic link from the root of the device to /system/etc
Click to expand...
Click to collapse
Just symlinking /system/etc to /etc won't magically make init.d scripts work if the init.d service isn't being invoked in init.rc.
You need a ROM/kernel that will support init.d scripts. If the ROM/kernel don't support init.d, then you can't get them to auto-run on boot, except for work-arounds like using Script Manager to run them on boot.
Also, your link command is only correct if you're in the root directory of your phone. Executed from anywhere else, you don't end up with /etc. It should be:
ln -s /system/etc /etc
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
AdAway works without problems here, with simple press activate button.
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yup
Sent from my HTC 10 using Tapatalk
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yes, but it modifies the /system partition unless you do the trick in OP. If I'm correct, you will have problems with OTA updates and Google Pay if you let AdAway directly modify the hosts file on /system.
Now that TWRP can access /data, can we just flash the zip?
goodtimes50 said:
Now that TWRP can access /data, can we just flash the zip?
Click to expand...
Click to collapse
Yes, you can. I downloaded that zip and apk from the Unofficial AdAway thread linked above. Booted into TWRP, flashed the newest betaSuperSU2.74-2-forceencrypt (not related to this, just so I'd be on the latest version), then the AdAway_systemless_hosts_v2.zip, rebooted and installed the apk and let it run. Rebooted. Showing hosts location as /system32/etc/hosts as the OP says is a good thing, and both files mentioned are in their correct places per Root Browser. [emoji106]
Sent from my HTC 10 using XDA-Developers mobile app
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
bmwbasti said:
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
Click to expand...
Click to collapse
I believe that is correct. There hasn't been a new OTA for my phone yet so I can't verify. However, when I do the check for new software it tells me no new updates (as opposed to the message about the files system being corrupt). I believe Android Pay should also work. I have it installed and added a new card, but I haven't tested making a purchase yet.
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Fix for AdAway.
matif525 said:
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Click to expand...
Click to collapse
Your device may use su, & still not have an su folder (at all) that is used for hosts file (ie systemless root). Just do this..
Download... Terminal emulator.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Open terminal
Then enter these commands.. "Quote"
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -orw,remount /system
Now open AdAway go to preferences and select option to " Target hosts file"
Select /data/data/hosts
Enjoy..
If you still have ads in apps do this!!!
githyanki said:
Open the 3 dot menu in adaway, chose log DNS request. Enable TCP dump.
Open the app with ads, when ad loads, go back to adaway, and open log.
Long press any entries and chose black list.
Profit
Click to expand...
Click to collapse
All credit where credit is due. I just shared what I read else where.
Read here for more details..
https://github.com/AdAway/AdAway/issues/770
&
http://forum.xda-developers.com/showthread.php?t=2190753&page=143#post68988079
There is a known issue in HTC devices involves S-off. If the above doesn't solve this for you message here I'll follow. Or pm me. I work wierd hours be patient.
Rom Maximus 3.0.0 ( Android 7 ).Any instruction don't works,adaway no blocked ads.
regarding su folder to move files to
FreydNot said:
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
Click to expand...
Click to collapse
Hi there, ive got a mate 8, not sure if this adblocker will work on it but i want to try it out anyway. Ive unzipped the file but which folder in su do i move the files to? screenshot of the folders i have in su
did anybody find away to push adblock to system via rooted.. thx @Chainfire
like terminal emulator? or anyway. thx In advance
Sent From Pixel XL/Rooted
Team Blackout
Try AdAway
http://forum.xda-developers.com/showpost.php?p=69466682&postcount=217
freddienuxx said:
did anybody find away to push adblock to system via rooted.. thx @Chainfire
like terminal emulator? or anyway. thx In advance
Sent From Pixel XL/Rooted
Team Blackout
Click to expand...
Click to collapse
Here you go install go to settings and enable systemless mode https://drive.google.com/file/d/0B6bczptEI-1LNHphSUQxRDg1RWM/view?usp=drivesdk
Here are the instructions for install Adblock without Recovery (e.g. TWRP):
1. Download Adaway from here: https://www.androidfilehost.com/?fid=24588232905720420
2. Download a Terminal emulator from Playstore
3. Give him root (just type in the emulator "su" and allow root
4. Copy/write this in the Emulator and press enter:
mkdir /su/etc; cp /system/etc/hosts /su/etc/hosts; echo "#!/su/bin/sush\nmount -o bind /su/etc/hosts /system/etc/hosts" > /su/su.d/50adaway; chmod 0700 /su/su.d/50adaway
5. Restart your Phone
6. Install Adaway
7. Allow Root
8. Press install and follow the instruction
I hope this helps
Way too complicated. For AdAway there is a check box in pref for systemless now. Just install AdAway and check that box. Don't need to do anything in terminal.
thx brother much appreciated
mrRobinson said:
Way too complicated. For AdAway there is a check box in pref for systemless now. Just install AdAway and check that box. Don't need to do anything in terminal.
Click to expand...
Click to collapse
do you have that adblock apk?
thx
not working for me... downloaded adaway from above link and no systemless box to check in pref that I see. Also tried running the command in terminal emulator but I get an 'event not found' error
update: I had to use the official 'Terminal Emulator for Android', which I wasn't wanting to use at first and used a different one because it would not let me copy and paste the above command line into the emulator, I had to physically type that whole thing out. But it said that the su folder exists which was the only confirmation I received in the emulator. Then I rebooted and installed, all good now!
freddienuxx said:
do you have that adblock apk?
thx
Click to expand...
Click to collapse
in_dmand said:
not working for me... downloaded adaway from above link and no systemless box to check in pref that I see. Also tried running the command in terminal emulator but I get an 'event not found' error
update: I had to use the official 'Terminal Emulator for Android', which I wasn't wanting to use at first and used a different one because it would not let me copy and paste the above command line into the emulator, I had to physically type that whole thing out. But it said that the su folder exists which was the only confirmation I received in the emulator. Then I rebooted and installed, all good now!
Click to expand...
Click to collapse
As Mr. Robinson said too complicated... Just got to the official link below. Download 3.2 and install, open app go to setting and select systemless... Done
http://forum.xda-developers.com/showthread.php?t=2190753
Give Adguard a go, best one I've used yet. Doesn't need root either.
Sent from my Pixel XL using Tapatalk
Adclear from seven is free is just like adguard
But all those non root adblock apps use up battery.
Personally I use Firefox with adblock plus addon
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Also any app that can set rotation on a per app basis
teostar said:
Also any app that can set rotation on a per app basis
Click to expand...
Click to collapse
Tasker
Sent from my OnePlus3 using XDA Labs
teostar said:
Also any app that can set rotation on a per app basis
Click to expand...
Click to collapse
I use Ultimate Rotation Control for this. Works well.
https://play.google.com/store/apps/details?id=nl.fameit.rotate&hl=en
Prattham said:
Tasker
Click to expand...
Click to collapse
I tried Tasker. But had an issue with it saying I don't have root.
teostar said:
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Click to expand...
Click to collapse
Any suggestions on these?
Can you elaborate a bit? I may be able to help you. What were you trying to do that needed root?
Some Tasker tasks require root if you need to run them through Secure Settings, which is kind of a companion app for Tasker for changing certain system settings. You may be able to set up a profile without requiring root for what you want to do.
Redjax said:
Can you elaborate a bit? I may be able to help you. What were you trying to do that needed root?
Some Tasker tasks require root if you need to run them through Secure Settings, which is kind of a companion app for Tasker for changing certain system settings. You may be able to set up a profile without requiring root for what you want to do.
Click to expand...
Click to collapse
I was attempting to setup a scheduled airplane mode. Which needed secure settings, but it's was saying I needed root( which I already have).
teostar said:
I was attempting to setup a scheduled airplane mode. Which needed secure settings, but it's was saying I needed root( which I already have).
Click to expand...
Click to collapse
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Squabl said:
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Click to expand...
Click to collapse
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
teostar said:
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
Click to expand...
Click to collapse
It's systemless.
Squabl said:
Do you have systemless root installed? Secure settings doesn't work with systemless root. If you have systemless root, then by doing this in terminal will make secure settings recognize root:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
If you don't have systemless root then I would test remounting system partition with read/write permissions and then re-setting Secure settings again.
Edit: you can use any terminal application from Google Play
Click to expand...
Click to collapse
Gr8 it worked. Thanks again :good:
teostar said:
Thanx I'll try this a lil later. To be honest I have no idea if I have systemless root or not I just flash the superuser 2.78 s5 whether it's systemless or not I don't know.
Click to expand...
Click to collapse
Hey, check out phhSuperuser, and Magisk. It's easy systemless root, no ADB commands or anything
Redjax said:
Hey, check out phhSuperuser, and Magisk. It's easy systemless root, no ADB commands or anything
Click to expand...
Click to collapse
I took a look at that thread and its out of my league for now. #babysteps I just got this, my 1st android device in October.
teostar said:
I took a look at that thread and its out of my league for now. #babysteps I just got this, my 1st android device in October.
Click to expand...
Click to collapse
I'm sorry, just saw this post. Magisk is very easy to install. The thread has a lot of information, but it's as easy as downloading the zip for Magisk and phh superuser, flashing them, and installing the apk files. Then you open the Magisk manager app and follow the steps in the thread! I installed it on my first try, and I agree, it seems complicated...But it works great and isn't hard at all to install if you've flashed things like SuperSU before! It's basically the same process when I'm not on mobile, I may reply with a short guide that follows the steps I took to get it working.
teostar said:
Hi, I always ran xposed since getting my op3. But since taking the plunge for 7.1 are there any apps that has these features without xposed.
1- download progress bar,
2- hide ongoing notifications in status bar
Click to expand...
Click to collapse
1. There's a module called Flat Style Bar Indicators that might help with download progress but it shows just the percentage not a bar.
http://repo.xposed.info/module/com.bocharov.xposed.fsbi
2. For notifications there's a great module called Notify Clean, it can do what you wan an much much more.
http://repo.xposed.info/module/de.defim.apk.notifyclean
I also advise to use a module called UnbelovedHosts, it's an ad blocker for xposed that's much more effective than any other because it just loads it on boot and doesn't need to run in the background.
http://repo.xposed.info/module/de.defim.apk.unbelovedhosts
Sent from my SM-G903F using XDA Labs
MegaArthur said:
1. There's a module called Flat Style Bar Indicators that might help with download progress but it shows just the percentage not a bar.
http://repo.xposed.info/module/com.bocharov.xposed.fsbi
2. For notifications there's a great module called Notify Clean, it can do what you wan an much much more.
http://repo.xposed.info/module/de.defim.apk.notifyclean
I also advise to use a module called UnbelovedHosts, it's an ad blocker for xposed that's much more effective than any other because it just loads it on boot and doesn't need to run in the background.
http://repo.xposed.info/module/de.defim.apk.unbelovedhosts
Click to expand...
Click to collapse
Thanks for the suggestions. But I was looking for regular apps not xposed since xposed doesn't work for nougat just yet.
An app or a module that disables vibration on successful fingerprint authentication? I have nougat and I can't have xposed...
teostar said:
Thanks for the suggestions. But I was looking for regular apps not xposed since xposed doesn't work for nougat just yet.
Click to expand...
Click to collapse
Checkout Download Progress++ in Play Store. It is by the same Dev as GB. It doesn't even need root leave alone Xposed. Checkout this post also: https://forum.xda-developers.com/showpost.php?p=71480102&postcount=293
I am using it and works wonderfully.
tnsmani said:
Checkout Download Progress++ in Play Store. It is by the same Dev as GB. It doesn't even need root leave alone Xposed. Checkout this post also: https://forum.xda-developers.com/showpost.php?p=71480102&postcount=293
I am using it and works wonderfully.
Click to expand...
Click to collapse
Seems it's not available in my country. Thanks. I'll try a VPN tomorrow.
Made a new thread as seems this is demanded option. Some people already checked this and looks like this works. I can't check right now but if you want, please check and post if it works for you.
Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. To do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'.
Connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app (eg. MagiskHide Props Config)
You need root to do this.
Also there is Xposed Module in xposed manager to do this automatically called "EnableSoliOnPixel4", here's thread about it https://forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Monazite said:
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, without root you can’t edit system props
Eugnis said:
Yes, without root you can’t edit system props
Click to expand...
Click to collapse
getting failed to set property reply. any idea what i'm doing wrong?
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
omar5099 said:
getting failed to set property reply. any idea what i'm doing wrong?
Click to expand...
Click to collapse
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Kris Chen said:
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
Click to expand...
Click to collapse
Yes, this setting just disable country check at all. So Soli will work worldwide
Eugnis said:
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Click to expand...
Click to collapse
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Now I gotta root my phone and lose automatic updates just to be able to use it normally. Thanks a lot, Google!! _l_
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Bogega said:
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Click to expand...
Click to collapse
yes same here, any1 got this to work ? thanks
Pixeling said:
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Click to expand...
Click to collapse
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
That's what I suspect since the property lives in /data which is not changed/erased after OTA. I've not tried it myself however that's probably what I will do when I get the phone.
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
Performing some more reading on the subject, there is a possibility that unlocking the bootloader by itself trips safetynet which in turn prevents OTA. I can't know whether this is true for sure, but in this case keeping Magisk root shall hide that and let you download the OTA.
Before applying the OTA you should use magisk to restore the boot.img, let the OTA install, and then let Magisk install itself to the other inactive flash slot where the OTA is. That will make sure that root is kept intact post update and keep hiding that the bootloader is unlocked. Can anyone confirm?
WORKED
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
sta3b said:
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
Click to expand...
Click to collapse
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Bogega said:
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Click to expand...
Click to collapse
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
chris111111 said:
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
Click to expand...
Click to collapse
Soli doesn't survive reboots if you're using this method.
There's a magisk module (non Xposed) which solves this though (https://forum.xda-developers.com/pixel-4-xl/themes/enable-soli-contries-magisk-module-t3997035)
wolfgangam31 said:
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
Click to expand...
Click to collapse
correct, rebooting the phone will cause SOLI to get disabled, you need to re-enter the commands in the terminal to get it to work again