Related
EDIT: It seems the sqlite solution does not work at all. I am trying other ways.
See this thread: http://forum.xda-developers.com/showthread.php?t=593739
[DEL]
I've been searching for the way to get my Hero access the Internet through a proxy when connected to a WiFi network. And the only information I found useful was a HOWTO on setting up the emulator to use a proxy.
According to that HOWTO, inserting a record into table 'system' in database 'settings.db' (/data/data/com.android.providers.settings/databases/settings.db) tells the emulator the proxy information:
Code:
sqlite> insert into system values(99,'http_proxy','<ip-of-proxy>:<port-of-proxy>');
So I wonder if this works on a Hero product.
I am using a HTC Generic 2.73.405.38 ROM and I couldn't find sqlite in my phone. Following is what I have tried under android sdk in windows:
Code:
android-sdk-windows\tools> adb pull /data/data/com.android.providers.settings/databases/settings.db .
android-sdk-windows\tools> sqlite3.exe settings.db
sqlite> insert into system values(99,'http_proxy','<ip-of-proxy>:<port-of-proxy>');
sqlite> ^C
android-sdk-windows\tools> adb push settings.db /data/data/com.android.providers.settings/databases/
But after rebooting my Hero, the proxy still does not seem to work.
Can anyone help me with some clues on this? Does the settings.db not work as it did in emulator? If not, then how?
[/DEL]
Hi,
i had problems with some Modder Tools using windows 8. And after i didn't find solutions i decidet to post my one here.
So i had problems with some signing tools and the ddms from adb to take screenshots.
When starting i get some errors like install java but i still installed it. To solve try this:
edit the bat causing the error. I take for example ddms.bat.
search for Java and you'll find this part:
rem Check we have a valid Java.exe in the path.
set java_exe=
call lib\find_java.bat | < here you see that the bat is searching with find_java.bat in the lib folder for java. So we will edit this file.
if not defined java_exe goto :EOF
So if you now looking in this folder and search for java you'll find this part:
set java_exe=
for /D %%a in ( "%ProgramW6432%\Java\*" ) do call :TestJavaDir "%%a"
if defined java_exe goto :EOF
rem Check for the "default" 32-bit version
:Check32
echo Checking if it's installed in %ProgramFiles%\Java instead.
set java_exe=
for /D %%a in ( "%ProgramFiles%\Java\*" ) do call :TestJavaDir "%%a"
if defined java_exe goto :EOF
So here is the problem the folders where it looks for Java doesn't exist for Windows 8.
For me java is installed in Program Files (x86).
So add this part:
set java_exe=
for /D %%a in ( "C:\Program Files (x86)\Java\*" ) do call :TestJavaDir "%%a"
if defined java_exe goto :EOF
and save. You can now open cmd, browse to adb folder and type in "ddms.bat" you'll now get the same error, but you can ignore it. Additionaly you'll get an other error. to fix this open System control, System, System, advanced system settings,
enviroment Variable.
At the User Variables select new and type for name java and value C:\Program Files (x86)\Java\jre7\bin\java.exe.
Please notice that the value can change if you have a newer Version. The cmd should get you the right value. Save it and repeat the command "ddms.bat" it will give you the same errors but after a while the ddms will open and you can use it. I haven't try it for the signing tool but i'm sure this will work for these, too.
I'm sorry for bad english, maybe someone can "translate" this in better english.
EDIT: Skip to the bottom EDIT for the short version..
Preamble: I searched for a fix to this recently and over the past 10 months and haven't seen any real solutions to this. Most people have probably experienced this issue at some time flashing roms, especially those people running gapps-free Android :highfive: such as myself. A band-aid for fixing this is running gapps' SetupWizard and/or CM's CMAccounts, I started adding CMAccounts.apk to /system/app some months ago to fix this. I was never satisfied with this workaround though since it doesn't narrow down the actual problem, and I really like sticking to the AOSP experience, open-source, no Stasi-esque permissions, and without the need to taint my installation just to set it up (setupwizard does a lot more than you might think).
Using some additional skills I didn't have 6 months ago, I finally isolated the issue to the SQL database /data/data/com.android.providers.settings/databases/settings.db, table global, value name device_provisioned. It is set to "0" by default which leads to all these ridiculous problems, and setting it to "1" + a reboot fixes all of these problems for me. Setting it back to "0" + reboot breaks everything again, back to "1" fixes, provision.apk present or removed.. I searched for (sqlite3 dump | grep) lots of other provision and setup value differences... tested this a lot.
!!!BACKUP /data/data/com.android.providers.settings/databases/settings.db before attempting this. Use 'busybox cp -p /data/data/com.android.providers.settings/databases/settings.db Your_Backup_Location' to copy and keep correct permissions on it. I would do a nandroid backup maybe anyway. This should be harmless or very helpful, but it's a su'd command in depths of /data so ya never know.
A couple simple ways to get this set right since you can't reliably grep'n'sed here: Get a nice free sql-frontend app off fdroid or xda -very handy- and go to the settings.db file, 'global' table, and then find or add "device_provisioned" in the name column and "1" in the value column. Root Explorer has this built in I think. The better way though is to pull up the 'adb shell' terminal remotely or use a terminal emulator from the phone with free && adfree Jack Palevich's Terminal Emulator, Spartacus Rex' Terminal IDE (recommended ...for everything!), anything using a jni_exec java execute emulation command. Also Ghisler's Total commander file manager has a built-in command line for convenient executions (or cool shell-script shortcuts you can make --it was actually the first tasker).
# Enter each command line by line (after '>'):
Code:
>su
>$(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db
>update global set value="1" where name="device_provisioned";
>.quit
>exit 0
# One-liner
Code:
su && $(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db 'update global set value="1" where name="device_provisioned";'; exit 0
Then just reboot, enjoy that home softkey that takes you to your launcher home.. your notification bar that displays your notifications. lol such basic s***.
Hope this can help someone else out as much as it did me. You don't have to use gapps/setupwizard to fix it! I also want to make sure there isn't another rogue SQL.db value. (btw if you happen to read this and have a broken back softkey/button, your problem is likely the lib file /system/lib/jni_latinime.so. Thought I'd throw that out there.)
EDIT: Heres an update short version. I added another sqlite value that needs correcting in ROMs without gapps setup bla installed. Run these commands in terminal emulator or via adb. Just copy and paste, they need to be exact.
Check that the values on the right are "1" when you fire off:
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''select * from global where name="device_provisioned"; select * from secure where name="user_setup_complete";'\'
Otherwise or just to be safe, fire off this wicked one liner(Warning: reboots when finished):
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''update global set value="1" where name="device_provisioned"; update secure set value="1" where name="user_setup_complete";'\'' && sync && fsync /data; sleep 3; svc power reboot'
Done, 1-2 steps.
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
namtombout said:
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
Click to expand...
Click to collapse
Yeah man, glad it worked. Cheers to your cojones for trying it!
What I usually do for a no gapp solution is:
-grab the libjni_latinime lib from microgapps cause its needed for the aosp keyboard swipe usually
-use "gapps browser" for Google related stuff like gmaps.
-or use rmaps (this and gapps browser need the maps api, so you gotta pull the google maps framework jar or use the "no-gapps project" hack api /system/framework/*google*jar. Make sure to add the corresponding /etc/permissions/*google*xml files too)
-instead of gmail I use the standard email client of k9
-instead of play I use fdroid, aptoide sometimes, nextwap.net, or mobilism forums, or a lucky patcher cracked Google play. (careful with the non-fdroid ones)
Sorry bout this 6 month late reply, Jesus I gotta watch my posts more closely.
So far, it looks like some folks have dabbled in pursuit of stock native tethering without the nagware, but it seems undocumented. I hope this is a bit more thorough!
I successfully modified /system/customize/ACC/default.xml to enable the native tethering tools without interference from the TetheringGuark apk.
Here's the catch. It's not working with 4G. Previous HTC phones have had this issue too; it could be because of an RF interference countermeasure installed by HTC or it could just be silly drivers. Or maybe it's an ipv6 setting! I didn't get that far today, but if I get to the bottom of it I'll update. I think my next step will be to break open a stock-based rom and see what others have done.
For reference, I have a Sprint HTC10, unlocked via HTCDev, S-ON, TWRP 3.0.2.4, and the HTC10 modified SuperSU. I made the edits on a linux host, so I had no concerns about dos2unix conversion. YMMV.
reboot into recovery, and mount /system from the "Mount" menu.
adb pull /system/customize/ACC/default.xml . #this is the file we'll edit
adb push default.xml /sdcard/default.xml.orig #make a backup
Make the following edits to the local copy of default.xml using a text editor of your choice:
Set tethering_guard_support to false
Set use_default_profile_for_tethering to true
adb push default.xml /system/customize/ACC/default.xml
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard).
Reboot. If it won't boot, DON'T PANIC, go back to recovery (by holding voldn+power for 10 seconds), and replace default.xml with your backup at /sdcard. Don't forget to fix permissions with chmod again.
Enable hotspot or USB tethering and connect clients (bluetooth untested)
If you're on 4G, clients won't have any internets. Go to Settings -> Mobile Data -> Network mode CDMA Only (or GSM/UMTS only, I suppose. Untested.)
That's it. No scripts or separate apks required. Please someone let me know if I just reinvented the wheel, or if you know how to make 4G do 4G things!
Reserved for if/when I figure out 4G.
Is this for sprint? I have it working for T-Mobile US, USB nor Bluetooth tether tested as I don't tether using that method.
Sent from my HTC 10 using Tapatalk
fmedrano1977 said:
Is this for sprint? I have it working for T-Mobile US, USB nor Bluetooth tether tested as I don't tether using that method.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
fmedrano1977 - Yes, I'm on Sprint. I suspect the process for Sprint and Verizon will be identical, since they're both CDMA providers. T-Mobile is a GSM carrier, so there may be a few small changes to the process above.
Are you able to tell me what you did differently?
roleohibachi said:
So far, it looks like some folks have dabbled in pursuit of stock native tethering without the nagware, but it seems undocumented. I hope this is a bit more thorough!
I successfully modified /system/customize/ACC/default.xml to enable the native tethering tools without interference from the TetheringGuark apk.
Here's the catch. It's not working with 4G. Previous HTC phones have had this issue too; it could be because of an RF interference countermeasure installed by HTC or it could just be silly drivers. Or maybe it's an ipv6 setting! I didn't get that far today, but if I get to the bottom of it I'll update. I think my next step will be to break open a stock-based rom and see what others have done.
For reference, I have a Sprint HTC10, unlocked via HTCDev, S-ON, TWRP 3.0.2.4, and the HTC10 modified SuperSU. I made the edits on a linux host, so I had no concerns about dos2unix conversion. YMMV.
reboot into recovery, and mount /system from the "Mount" menu.
adb pull /system/customize/ACC/default.xml . #this is the file we'll edit
adb push default.xml /sdcard/default.xml.orig #make a backup
Make the following edits to the local copy of default.xml using a text editor of your choice:
Set tethering_guard_support to false
Set use_default_profile_for_tethering to true
adb push default.xml /system/customize/ACC/default.xml
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard).
Reboot. If it won't boot, DON'T PANIC, go back to recovery (by holding voldn+power for 10 seconds), and replace default.xml with your backup at /sdcard. Don't forget to fix permissions with chmod again.
Enable hotspot or USB tethering and connect clients (bluetooth untested)
If you're on 4G, clients won't have any internets. Go to Settings -> Mobile Data -> Network mode CDMA Only (or GSM/UMTS only, I suppose. Untested.)
That's it. No scripts or separate apks required. Please someone let me know if I just reinvented the wheel, or if you know how to make 4G do 4G things!
Click to expand...
Click to collapse
/system/customize/ACC/default.xml
<item type="boolean" name="tethering_guard_support">True</item> ---> <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> ---> <item type="string" name="fixed_apn_for_dun">fast.t-mobile.com</item>
Added this line to /sysyem/build.prop
net.tethering.noprovisioning=true
Opened up Terminal Emulator for Android App
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
fmedrano1977 said:
/system/customize/ACC/default.xml
<item type="boolean" name="tethering_guard_support">True</item> ---> <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> ---> <item type="string" name="fixed_apn_for_dun">fast.t-mobile.com</item>
Added this line to /sysyem/build.prop
net.tethering.noprovisioning=true
Opened up Terminal Emulator for Android App
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
Click to expand...
Click to collapse
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
dmchssc said:
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
Click to expand...
Click to collapse
Would you mind doing a step-by-step for us newbs? I, for one, would highly appreciate it. Tried to follow the instructions,, but no go.
Use a custom ROM viper 10 has hotspot working on 3g-lte simple no extra work needed
roleohibachi said:
fmedrano1977 - Yes, I'm on Sprint. I suspect the process for Sprint and Verizon will be identical, since they're both CDMA providers. T-Mobile is a GSM carrier, so there may be a few small changes to the process above.
Are you able to tell me what you did differently?
Click to expand...
Click to collapse
Hey bro thanks for that! Is it possible to get a step by step for this? I am still fairly new and I have found it very difficult to do. Thanks!
Help! I didn't do a backup!
I've got a Sprint htc 10, rooted, s-on stock rom.
I opened the system/customize/acc/default.xml file with a text editor to change the tethering guard. When I hit save, it said changes could not be saved. Backed out and changed permissions, now when when I try to open it with any text editor, it either won't open or it's blank.
It hasn't caused any problems that I can see after a reboot, but now I need to replace the file!
Anybody know where I can find a copy of that exact file?!
Any help would be greatly appreciated!
jtaylormartin said:
I've got a Sprint htc 10, rooted, s-on stock rom.
I opened the system/customize/acc/default.xml file with a text editor to change the tethering guard. When I hit save, it said changes could not be saved. Backed out and changed permissions, now when when I try to open it with any text editor, it either won't open or it's blank.
It hasn't caused any problems that I can see after a reboot, but now I need to replace the file!
Anybody know where I can find a copy of that exact file?!
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I would try a custom ROM compatible with Sprint.
Sent from my HTC 10 using Tapatalk
bibbin said:
Would you mind doing a step-by-step for us newbs? I, for one, would highly appreciate it. Tried to follow the instructions,, but no go.
Click to expand...
Click to collapse
were you able to figure it out? If not, let me know and I'll gladly guide you through
Oh, goodness no. I've been waiting for a reply. Thank you. What do I need to do?
bibbin said:
Oh, goodness no. I've been waiting for a reply. Thank you. What do I need to do?
Click to expand...
Click to collapse
Alright...
I take it you already know how to boot into recovery: reboot into recovery, and mount /system from the "Mount" menu in TWRP - uncheque mount partition read-only
when you first rooted your HTC 10, you had to install the ADB fastboot files on your PC.(unzipped)
In the unzipped Fastboot folder: shift right click, Open command Window Here...
From there: adb pull /system/customize/ACC/default.xml . #this is the file we'll edit - located in the same folder where you opened the command line.
adb push default.xml /sdcard/default.xml.orig #make a backup - copy that default.xml in adb folder and save and rename copy to desktop and/or external sd.
Make the following edits to the local copy of default.xml using a text editor of your choice: (local copy meaning the Default.xml in the unzipped ADB fastboot folder where you opened the command line prompt, I used notepad)
Ctrl F the following: ** always be on the top line of notepad when Ctrl F. if not it won't located the search in question***
Set tethering_guard_support to false (ctrl F for: "tethering_guard_support") ...
Set use_default_profile_for_tethering to true (ctrl F for: "use_default_profile_for_tethering)
<item type="boolean" name="tethering_guard_support">True</item> change to <item type="boolean" name="tethering_guard_support">false</item>
<item type="string" name="fixed_apn_for_dun"></item> change to <item type="string" name="fixed_apn_for_dun">cinet.spcs</item> I'm on sprint.
Save the File...
adb push default.xml /system/customize/ACC/default.xml (the command line window should still be open)
adb shell
chmod 664 /system/customize/ACC/default.xml #yes, it's supposed to be 664, that's no typo. Reboot.
Backup and uninstall (by whatever means you please, I just rm'd it) TetheringGuard (com.htc.tetheringguard). - I did this with Titanium Backup
Use a file explore of your choice from the play store (I use Root Explore) and navigate to: system/build.prop. mount r/w open with text editor and add the following line all the way to the bottom of the build.prop:
net.tethering.noprovisioning=true
Save.
Download and Open "Terminal Emulator for Android" from play store.
typed "su" ENTER should change $ --> #
typed "settings put global tether_dun_required 0"
typed "reboot"
once phone reboots, pull down your notification, long press mobile hotspot, set it up and test on pc. BAMN!!!!
Hope this works for you, mate. Let us know
Of course, cheers to OP hence all other contributors for putting this together. I by no means take credit for any of this awesome work, of which, I only wish to have had half the talent and patient to develop such skills. Only thought to put it all together for those who may need it. Cheers.
Let's go Steelers.
where is the bloody thanks button?!...
Can't seem to locate it...
THANKS
dmchssc said:
I used this to get native LTE tethering working with Sprint. Do everything fmedrano mentions, except instead of setting the fixed_apn_for_dun to fast.t-mobile.com, set it to cinet.spcs.
Click to expand...
Click to collapse
Thanks for the help, these added instructions for Sprint worked for me.
Can sprint detect when your using hotspot or USB tethering if you don't have it on your plan?
Sent from my 2PS64 using XDA-Developers Legacy app
Thanks guys. I had an Internet outage this morning, so I tried this using stock rooted N. Worked like a charm!
For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
bruceas said:
If i try this command
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
this is the output. How i can solve it?
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
P.S. Now it works. The solution is to use this command:
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
" to '
Thanks.
Click to expand...
Click to collapse
Thanks for the update, it seems to be related to the Windows regional settings on a PC (?). On my personal PC it works with double quotes ", on my work PC with single '. I've update the instructions.
Edit: if you split command into two, it works with double quotes as well
1. adb shell
2. settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
_mysiak_ said:
For those wanting to have the back button on the right side (where it naturally belongs ), it's simple with ADB:
Like stock spacing:
Code:
adb shell settings put secure sysui_nav_bar "space[0.25WC],contextual;home;back,space[0.25WC]"
or
adb shell settings put secure sysui_nav_bar 'space[0.25WC],contextual;home;back,space[0.25WC]'
More comfy:
Code:
adb shell settings put secure sysui_nav_bar "space,contextual;home;back,space"
or
adb shell settings put secure sysui_nav_bar 'space,contextual;home;back,space'
To return back to stock:
Code:
adb shell settings delete secure sysui_nav_bar
Click to expand...
Click to collapse
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
arjo656 said:
hello, sorry for this "stupid question" but, how to use ADB? where can i find it to enter those commands?
i've installed the usb driver, unlocked oem, and activated usb debug on the phone. but i don't know what to do after...
Click to expand...
Click to collapse
https://www.xda-developers.com/quickly-install-adb/
https://www.xda-developers.com/what-is-adb/
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
arjo656 said:
i followed the tuto, but when i enter "adb devices" it says " the term adb is not know as a .exe ......."
Click to expand...
Click to collapse
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
_mysiak_ said:
Either put adb.exe to Windows PATH, or you must change directory before running adb (for example "cd c:/platform-tools").
Click to expand...
Click to collapse
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
arjo656 said:
ok thanks, now it works with the .exe in win path, i've got the pop-up asking to allow usb debug, but when i enter any command , i've got this
/system/bin/sh: home: not found
/system/bin/sh: back,space: not found
i've tried the 4 differents lines normal and confy
Click to expand...
Click to collapse
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
WORKS!!!!!! :good:
thanks!!
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
Dont kill app, they will use more power when relaunching them, they use almost no power when in background.
arjo656 said:
just by curiosity, is it possible to move the task killer/cleaner button from the left to the right when i open the recent app list?
to avoid having to scroll left through the whole list, and have direct access to clean
Click to expand...
Click to collapse
No idea, I wasn't even aware of this button. As antoine62 said, it's totally useless. If you need to kill an app, just swipe it away from recent menu (or click on details and "force stop" if the app works with background service).
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
arjo656 said:
Sorry, my translation may not have been clear, in french we have the "effacer tout" (clear all) button on the left of the recently used apps, i took a screenshot.
And as a right hand writer, i find it useless to swipe all the list to the left before accessing this button, i would like to put it directly on the right of the list so when i swipe up from the bottom, i Can clear the list immediatly.
Click to expand...
Click to collapse
That button should not be really used at all, it just kills all cached apps. Stock Android is pretty good at memory management. There is really no point in force killing all the apps manually.
_mysiak_ said:
You have probably some unusual language/regional settings on your PC. Try it this way:
Code:
1. adb shell
2. settings put secure sysui_nav_bar "space,contextual;home;back,space"
..
3. exit
Click to expand...
Click to collapse
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
arjo656 said:
hello mysiak, i updated to android 10 yesterday against my will (see other post), i tried to do the same procedure, but it doesn't work anymore, any idea?
i did
./adb shell
settings put secure sysui_nav_bar "space,contextual;home;back,space"
exit
Click to expand...
Click to collapse
I don't have Android 10 yet and it seems that Google killed this feature (why oh why). I found this app which might help, give it a try and let us know. https://play.google.com/store/apps/details?id=nu.nav.bar
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
lowmanager said:
Hi,
Today i updated my phone to android 10 and I have same problem as arjo656. I tried app that you posted here, but now I have app's buttons and aslo original android's buttons. It looks weird. Didn't you find any way how to change it by adb again?
Click to expand...
Click to collapse
Nope, Google removed the interface for navbar customization in Android 10. I just keep stock 2 buttons navbar and use "Edge gestures" app for one hand operation (it's even on sale right now, grab it while you can).
Phil_gloves said:
Hi, I followed this guide https://forum.xda-developers.com/mi-a3/how-to/button-nav-hack-t3997527 to get back the three buttons (as in the previous versions of Android), and wanted to combine the two "hacks" to get back the 3 nav bar buttons but with the back button on the right, and the contextual on the left, but when I use your command via adb, the contextual button disappears, even tho in the command it's still there, I attach two pics to understand better
Click to expand...
Click to collapse
For 3 buttons navbar replace "contextual" with "recent". For example:
Code:
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
Edit: if you want to keep "contextual" button as well, this might work (can't test it as I'm on Android 10 already):
Code:
adb shell settings put secure sysui_nav_bar "contextual;space,recent;home;back,space"