Enable on-screen NavBar on Stock ROOTed Nougat? A2017U - ZTE Axon 7 Questions & Answers

Any way to enable the onscreen navbar on Nougat?
I used Root Browser to edit the build.prop to change the 0 at the end of this to 1 and back again
qemu.hw.mainkeys=1
Click to expand...
Click to collapse
But had no luck after reboot either way.
Any way to enable them?

It didn't work in MM because ZTE took the on screen buttons out of the framework, rather than just from the build.prop line.
I'm guessing they did the same thing in N.

needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop

That's odd cause when I went from lineage back to stock the nav bar followed. Full wipe, full stock zip.

I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?

t2jbird said:
I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?
Click to expand...
Click to collapse
Button mapper.

My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?

iNaruX said:
My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?
Click to expand...
Click to collapse
That's really weird, mine didn't have that? Only thing I had under "Navigation Keys" was the ability to swap them but not display them on screen?
I did, however, flash the vR26 Permissive kernel, and that automatically enabled the onscreen buttons......It also made Nougat much smoother

I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg

DrakenFX said:
needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop
Click to expand...
Click to collapse
you keep promise that... I'm still waiting on your ROM

iNaruX said:
I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg
Click to expand...
Click to collapse
Been meaning to reply to this with a screenshot from "stock rooted".. There is no option to "Always show navigation bar" in stock. Not sure if DrakenFX added that, or what?
I do know the Beast Mode Permissive kernel will enable them, and I used it for a couple weeks, but while that kernel is really smooth and I had my on-screen navbar.... My battery took a fairly huge hit, and my stock camera didn't work. So I reverted back to pure, rooted, stock.

Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.

p4ch1nk0 said:
Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.
Click to expand...
Click to collapse
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.

raystef66 said:
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.
Click to expand...
Click to collapse
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar

nmk_123 said:
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar
Click to expand...
Click to collapse
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:

raystef66 said:
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:
Click to expand...
Click to collapse
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing

nmk_123 said:
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing
Click to expand...
Click to collapse
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.

raystef66 said:
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.
Click to expand...
Click to collapse
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this

nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm attempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
No problem. We're here to help each other out :good:
I'll give a look at your build.prop later on.
But do try the Mifavor 5.0. As I'm not mistaken, the option is built in too. So nothing to change there. And this rom is quite smooth, fast and without force closes. Perhaps try it and let me know.
Tomorrow I'll take a look at your file.

nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
Looked into your build.prop and all should be ok. And since you installed the SLIM³ all files such as framework-res.apk and systemui.apk are overwritten in case the U models files could have been different. But as said, with all these files and your build.prop the nav bar should show up....
So for the moment i do not see an immediate solution for that matter.
As said and afaik , the Mifavor 5.0 from my rom has this nav bar build in

Related

[ ROM Release ] the latest 2.3.9MIUI perfect port

ROM contents
1, using the latest development version of the the MIUI transplant system perfectly stable, change the model for the HTC, modify the boot animation
2, the kernel G major MIUI repair kernel, do not break the sound
3, individuals joined enhance the script and add a few features: turned on by default 80M of Zram default unlock the FPS, you can turn off to enhanced.conf
4, all normal functions, to in addition to FM, the TV-OUT .
5, by adding the RE Manager, Google PLAY, goggles, the Huawei document management, animation acceleration, replace the input method Sogou
Integrated titanium backup and MIUI control center, you can customize the status bar
8, modify the boot theme is self produced IPHONEV1 optimize the camera and power-saving mechanism. Interface fluency can be used to adjust other settings
9 , add ice4.0, window effects, if you feel slow with other settings to modify the animation speed
10, to modify the system wallpaper, system sounds, calls music and other more personalized
11, the boot since the launch of the EQ manager, automatically adjust the sound of music. Listen to music the effect of greatly optimized.
PS: MIUI2.3 now break the sound problem solved, reaches the perfect state, there are some minor issues such as: volume shock and screenshots screenshots screenshots repair will lead to gravity sensing, I have limited skills do not specify a screenshot button . After miui no major updates, and I are working on to release a small update patch package. Can be updated to the OTA, as removed from Brush Shuangqing troubled.
Think the effect is not convenient students can turn off the animation displayed inside.
Install the ROM:
1 will download the zip Brush package do not extract directly into the SDcard
Hold the volume up + power button is turned on, do not release until well into the recovery mode
Recovery, the volume up and down keys / menu Home key to move up and down the power button / Search button to confirm the back key to return to the previous menu level.
Select "Clear all data recovery factory
Select from the SD card, select the Brush package "
6 re-election to select the ZIP file from the SD card "
7 to find just download the zip Brush package confirmed
8 confirmed, Brush, wait about 1 minute to complete.
After brushing, back to the first menu, select "immediately reboot the system restart the phone
10 and then patiently wait for a while, you first start will be relatively slow.
http://www.mediafire.com/?108h4zeap2dcx31
pikachukaki said:
ROM contents
1, using the latest development version of the the MIUI transplant system perfectly stable, change the model for the HTC, modify the boot animation
2, the kernel G major MIUI repair kernel, do not break the sound
3, individuals joined enhance the script and add a few features: turned on by default 80M of Zram default unlock the FPS, you can turn off to enhanced.conf
4, all normal functions, to in addition to FM, the TV-OUT .
5, by adding the RE Manager, Google PLAY, goggles, the Huawei document management, animation acceleration, replace the input method Sogou
Integrated titanium backup and MIUI control center, you can customize the status bar
8, modify the boot theme is self produced IPHONEV1 optimize the camera and power-saving mechanism. Interface fluency can be used to adjust other settings
9 , add ice4.0, window effects, if you feel slow with other settings to modify the animation speed
10, to modify the system wallpaper, system sounds, calls music and other more personalized
11, the boot since the launch of the EQ manager, automatically adjust the sound of music. Listen to music the effect of greatly optimized.
PS: MIUI2.3 now break the sound problem solved, reaches the perfect state, there are some minor issues such as: volume shock and screenshots screenshots screenshots repair will lead to gravity sensing, I have limited skills do not specify a screenshot button . After miui no major updates, and I are working on to release a small update patch package. Can be updated to the OTA, as removed from Brush Shuangqing troubled.
Think the effect is not convenient students can turn off the animation displayed inside.
Install the ROM:
1 will download the zip Brush package do not extract directly into the SDcard
Hold the volume up + power button is turned on, do not release until well into the recovery mode
Recovery, the volume up and down keys / menu Home key to move up and down the power button / Search button to confirm the back key to return to the previous menu level.
Select "Clear all data recovery factory
Select from the SD card, select the Brush package "
6 re-election to select the ZIP file from the SD card "
7 to find just download the zip Brush package confirmed
8 confirmed, Brush, wait about 1 minute to complete.
After brushing, back to the first menu, select "immediately reboot the system restart the phone
10 and then patiently wait for a while, you first start will be relatively slow.
http://www.mediafire.com/?108h4zeap2dcx31
Click to expand...
Click to collapse
Thank you for sharing this rom, but i have some questions: have you tried it? If yes, which are the bugs? Does it work perfect and fast?
MyNameIsKappa said:
Thank you for sharing this rom, but i have some questions: have you tried it? If yes, which are the bugs? Does it work perfect and fast?
Click to expand...
Click to collapse
Im using it right now its very fast and stable with tweaksv5 and kickasskernelizer i get 2500+ on quadrant but i only want to change the long press search key to open the mini menu with send sms and take screenshot option than open camera..anyone knows how i can change it?
Ok i fix it! ^_^ now the only one not working is the screenshot but there an app for that!
so no bugs on this rom?
matteof93 said:
so no bugs on this rom?
Click to expand...
Click to collapse
ss don't work i don't found other bug everything works fine
is this me or its to iOs looking?, and whats about with more statistic? does someones some numbers , on why this is perfect?
blksina said:
is this me or its to iOs looking?, and whats about with more statistic? does someones some numbers , on why this is perfect?
Click to expand...
Click to collapse
You can also change the theme if you like, some people prefer the look of iOS but not the way it performs.
It has only English and Chinese?
sewa2k said:
It has only English and Chinese?
Click to expand...
Click to collapse
Yes, I'm using it right now as we speak. It has both English (which I use) and Chinese.
The only issue is that I can't seem to sync my account.
KayxGee1 said:
Yes, I'm using it right now as we speak. It has both English (which I use) and Chinese.
The only issue is that I can't seem to sync my account.
Click to expand...
Click to collapse
It needs gapps!
pikachukaki said:
It needs gapps!
Click to expand...
Click to collapse
My gapps were bad, thanks!
is there a Russian language in this firmware?
Can I update to this ROM with only wiping cache and dalvik from MIUI 2.3.2?
EDIT: Nevermind, I've tried it and I can confirm that you can't update from MIUI 2.3.2 with only wiping cache and dalvik
borisstone said:
is there a Russian language in this firmware?
Click to expand...
Click to collapse
No, sorry. There are only a few versions of English based on the region, and Chinese.
pikachukaki said:
Im using it right now its very fast and stable with tweaksv5 and kickasskernelizer i get 2500+ on quadrant but i only want to change the long press search key to open the mini menu with send sms and take screenshot option than open camera..anyone knows how i can change it?
Ok i fix it! ^_^ now the only one not working is the screenshot but there an app for that!
Click to expand...
Click to collapse
Thank you! I upgraded to this ROM and i can confirm that is perfect!
Could you tell me please how did you change the long press search key to open another application?
MyNameIsKappa said:
Thank you! I upgraded to this ROM and i can confirm that is perfect!
Could you tell me please how did you change the long press search key to open another application?
Click to expand...
Click to collapse
/system/usr/keylayout/qwerty.kl
change
#key 127 SEARCH WAKE_DROPPED
#key 217 CAMERA WAKE_DROPPED
to
#key 127 SEARCH WAKE_DROPPED
#key 217 SEARCH WAKE_DROPPED
pikachukaki said:
/system/usr/keylayout/qwerty.kl
change
#key 127 SEARCH WAKE_DROPPED
#key 217 CAMERA WAKE_DROPPED
to
#key 127 SEARCH WAKE_DROPPED
#key 217 SEARCH WAKE_DROPPED
Click to expand...
Click to collapse
Thank you, it works !
MyNameIsKappa said:
Thank you, it works !
Click to expand...
Click to collapse
np!!i want it to have the mini menu so i can took screenshots...how is your battery drain??this is my only concern with this rom!
I do not understand a thing, is based on ics?
Kautuak said:
I do not understand a thing, is based on ics?
Click to expand...
Click to collapse
No its based on 2.3.9 miui but has ics animations...its translated from chinese but you can get the picture of what about this rom is!

LOS 14.1 - Swap hardware (capacitive) buttons without Xposed+Gravity Box?

Hello there,
As of now, Xposed is still not supported in LOS 14.1 as stated by the person maintaining it in this recent post. Is there a way to make the hardware buttons operate inverted? Right now the left button is "BACK" and the right button is "RECENTS" without any way to change it directly from the settings menu.
I have tried editing the file
Code:
/system/usr/keylayout/Generic.kl
directly from the TWRP terminal using VI, in the following entries:
Code:
key 139 MENU --> key 139 BACK
key 158 BACK --> key 158 MENU
But even after rebooting, the changes didn't happen. I checked the Generic.kl file and the changes persisted but no change whatsoever. Has anyone tried ButtonMapper ?? The pro version allows changing the button mapping but it seems like a temporal solution rather than a permanent, more elegant one.
Thanks for any help provided!
Flogisto said:
Hello there,
As of now, Xposed is still not supported in LOS 14.1 as stated by the person maintaining it in this recent post. Is there a way to make the hardware buttons operate inverted? Right now the left button is "BACK" and the right button is "RECENTS" without any way to change it directly from the settings menu.
I have tried editing the file
Code:
/system/usr/keylayout/Generic.kl
directly from the TWRP terminal using VI, in the following entries:
Code:
key 139 MENU --> key 139 BACK
key 158 BACK --> key 158 MENU
But even after rebooting, the changes didn't happen. I checked the Generic.kl file and the changes persisted but no change whatsoever. Has anyone tried ButtonMapper ?? The pro version allows changing the button mapping but it seems like a temporal solution rather than a permanent, more elegant one.
Thanks for any help provided!
Click to expand...
Click to collapse
The free version allows swapping back and recents. It doesn't require root and is less intrusive than using xposed.
flar2 said:
The free version allows swapping back and recents. It doesn't require root and is less intrusive than using xposed.
Click to expand...
Click to collapse
The free version doesn't allow it. Just wanted to confirm if anyone tried it and does it work properly?
Thanks for the reply!
Flogisto said:
The free version doesn't allow it. Just wanted to confirm if anyone tried it and does it work properly?
Thanks for the reply!
Click to expand...
Click to collapse
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
DrakenFX said:
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
Click to expand...
Click to collapse
You are COMPLETELY right, my bad! Thanks for the tip and to @flar2 as well. I completely missed that option. Thanks for your work with LOS 14.1!
DrakenFX said:
You are COMPLETELY wrong, Free version Does allow Swap of the hardware keys
Just toggle when it say " Swap Back and Recents " ,will stick at boot ,but will needs to be reenable when dirty flash a new build. Been using since the first LineageOS build.
Click to expand...
Click to collapse
Just in case, this has been posted, I can confirm it works just fine. POST. The difference is that @XblackdemonX edited the Synpatics.kl file instead of Generic.kl.

Asus Z300M Nougat update?

Has anyone installed the Nougat update for the Asus Zenpad 10 Z300M?
Yes I do, what do you need to know?
I didn't know there was an update to Android 7 - I'm still hoping (probably in vain) for this tablet to be rooted.
fabfor said:
Yes I do, what do you need to know?
Click to expand...
Click to collapse
I was just wondering if there were any noticeable changes or any issues with it as of yet.
Thanks for the reply.
Is the update OTA or from a website?
odyseus said:
Is the update OTA or from a website?
Click to expand...
Click to collapse
OTA
---------- Post added at 14:19 ---------- Previous post was at 14:13 ----------
PeteSeiler2010 said:
I was just wondering if there were any noticeable changes or any issues with it as of yet.
Thanks for the reply.
Click to expand...
Click to collapse
Changes are those in the changelog. I haven't noticed any issues so far but multi user support isnt't there and I was hoping yes.
ASUS ZenPad 10 Android Nougat Changelog:
Update Google security patch
Remove redundant app shortcuts “Audio Wizard” “Splendid” “System update” and “Flashlight” from all apps menu
Remove ”PC Suite” (CD ROM)
Remove “Tap and hold to show menu” form Settings > ASUS customized settings > Touch key setting. Add “Tap and hold to activate Multi-window ” in Touch key setting
Quick Settings supports multiple pages , user can swipe left to right to see more quick settings if using more than 12. User can enter edit screen by tap the edit button on top right corner to determine which settings enabling or disabling
Default Tap and hold Recent apps key to activate Multi-window
Add “Game Genie”
ZenUI Keyboard added New Unicode code 9.0 emoji and skin tone.
The preloaded Holo Spiral, Bubbles, Black Hole, and Phase Beam live wallpapers are not compatible with Android N and will be removed after system update
Add bundled notifications switch. (Settings > Notification > Configure notifications.) When multiple notifications for a single app are received, they can be bundled together into a single group. This group can be expanded to see the individual messages
Add Lock screen wallpaper slideshow
Change wallpaper every time you wake up your device. And users can go to “Settings” -> “Lock screen” -> “Wallpaper slideshow settings” for setting
Update SMMI tool to SMMI_TEST_V5.1.74_CSC_L1L2
Support Unlock tool
Click to expand...
Click to collapse
Must be US update then as still running Android 6.x here in the UK
Odd .. haven't gotten it .. and I check every couple of days ..
It could be me, but it seems like my battery dies faster after having the update for a few days.
odyseus said:
Must be US update then as still running Android 6.x here in the UK
Click to expand...
Click to collapse
No, it's worldwide.
The official website have the link of the update, and you can apply it manually.
http://dlcdnet.asus.com/pub/ASUS/Ee...62.438207375.1494693050-1331990512.1494693046
Hello, pls can anybody help? I bough z300m from second hand, turn on it (not try log in to google) and on startup screen (language select) system ask me for update to nougat, i click OK, system updated, tablet restarted and i cant log into tablet (FRP).
I search for bypass z300m on nougat, but cant find it.
This procedure dont work for me (android 7.0)
So i need flash from fastboot, but i cant find flashtool for z300m (p00c), firmware i downloaded from official page.
Any solutions?
Thanks.
Edit. I cant turn on usb debugging in developer settings (system want log in for view all options in developer settings...)
Nougat
PeteSeiler2010 said:
Has anyone installed the Nougat update for the Asus Zenpad 10 Z300M?
Click to expand...
Click to collapse
I did the nougat OTA update yesterday,it took a few minutes to download,but it is working great !
macikcz said:
Hello, pls can anybody help? I bough z300m from second hand, turn on it (not try log in to google) and on startup screen (language select) system ask me for update to nougat, i click OK, system updated, tablet restarted and i cant log into tablet (FRP).
I search for bypass z300m on nougat, but cant find it.
This procedure dont work for me (android 7.0)
So i need flash from fastboot, but i cant find flashtool for z300m (p00c), firmware i downloaded from official page.
Any solutions?
Thanks.
Edit. I cant turn on usb debugging in developer settings (system want log in for view all options in developer settings...)
Click to expand...
Click to collapse
Bad news I'm afraid. You need the original login details used to setup the device when it was originally purchased other than that it's a long winded battle with ASUS to prove you didn't steal the device.
Good luck
After update the system reboots all the time when WiFi is ON.
If I turn OFF wifi - it works fine. No other solution...
root / multi-user
fabfor said:
OTA
---------- Post added at 14:19 ---------- Previous post was at 14:13 ----------
Changes are those in the changelog. I haven't noticed any issues so far but multi user support isnt't there and I was hoping yes.
Click to expand...
Click to collapse
There is a thread right after this listing when search for Z300M on XDA that claims TWRP and asus bootloader unlock tool (not necessary 2 get twrp) and was the reason I purchased this tablet. So far errors in everything in the OP with no responses and I hate to be paranoid but once I know, if not twice I have actuall run into "FAKE" threads on XDA in the 2-3 years being on here claiming root/twrp for a device with a small amount of chit chat, responses.... that was pure BS!
Anyhow, if you ever get root here is the fix for your multi-user issue, with es file explorer, or root explorer and editing the boot. file:
Enable Multi Window and Multi User Modes
If you have a rooted Marshmallow ROM (or Nougat), you can enable the 2 features above by editing the build.prop file found in /system/
For multi-window mode, change this entry in build.prop
ro.build.type=user
to -
ro.build.type=userdebug
To enable multi-user mode, add these 2 lines to the build.prop (anywhere, it doesn't matter)
fw.max_users=3
fw.show_multiuserui=1
Once you've made these changes, reboot the tablet.
To use multi-window mode, go to Settings, Developer options, and there will be a new menu item to switch this on or off.
To use multi-user, there will be a new option under Settings called Users.
If anyone seeing this has accomplished root on the Z300M 16GB wi-fi tablet, please let me know.....
thanks,
zach
ps of course, make sure you make a copy of the boot file to ext sd card or somewhere b4 just in case.... in the 15 times I have used this on 6.0, 7.0 lenovo & LG devices & 1 HTC... never had an issue BUT...
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
odyseus said:
Must be US update then as still running Android 6.x here in the UK
Click to expand...
Click to collapse
Actually all of the updates for the Z300M taking it to 7.0 are for the WW SKU (world wide) tablets, as well one for Japan and 1 other.........
any sign of root?
Asking around since purchasing this tablet due to thread on here claiming twrp but its falling on its face and no response as of yet.....
zach
?????
coolbeans2016 said:
Anyhow, if you ever get root here is the fix for your multi-user issue, with es file explorer, or root explorer and editing the boot. file:
Click to expand...
Click to collapse
Thank you coolbeans2016, that's right the reason I am too desperately looking for a way to root: to apply that fix.
Btw, I really do not see the reason for Asus to disable a native function (multi-user) that is - to me - obvious for a tablet. (Maybe it eats resources? i.e. storage space)
problem is
fabfor said:
Thank you coolbeans2016, that's right the reason I am too desperately looking for a way to root: to apply that fix.
Btw, I really do not see the reason for Asus to disable a native function (multi-user) that is - to me - obvious for a tablet. (Maybe it eats resources? i.e. storage space)
Click to expand...
Click to collapse
Problem is the instructions for getting TWRP flashed or even just booted up on TWRP threaded for installation of SuperSU or Magisk is failing. I've been told I'm wrong and am just not reading or following the instructions correctly but on a VERY popular device there is NO ONE claiming $$PROFIT$$ on the thread! Even the ones claiming understanding of the thread are having complications but only have an average of 6 posts as jr users with no thanks feedback.... yet they have no questions regarding using the SP Flash Tool?!!!!! Strange to me!
I'm contacting the dev on the thread AGAIN to see if I can get a detailed set of instructions in JUST getting TWRP onto this tablet, or its useless to me......
He really thought I was calling his thread a false listing but straightened it out with him about the fact he references another such thread along the same lines for the Verizon Asus A380M, which EVERYONE knows has never been, probably never will be able to get a custome recovery, let alone root of any kind!!!!!!!!
Any info you come across, or if you have tried the thread I'm mentioning please let me know your errors encountered, any ideas how WE may be not taking the instructions correctly.
zach
Hi,
I couldn'tt find any update for Z300CL.
Does anyone know if such an update is available?
Could you post the link here?
Thanks a lot
I used usb ethernet dongle on android 6 and it worked , it showed ethernet icon instead wifi. But when on android 7 the dongle does not work, seems usb host function is disabled, I dont want to root my tabled is there any way to enable usb host support ?

Enable DCI-P3 for OP3T with S6E3FA5 display panel

Update: Thanks to @MishaalRahman for the great summary article. More discussion there.
Update: Thanks to @GR0S for the app solution, available in this post
Update: Thanks to @doubleaykay for the magisk module, available in this post
I am no developer but I was researching the OP5 DCI-P3 calibration, saw that some international users were able to activate the calibration on their OP3T, and thought I would share what I have found so far. Long story short, this probably works if your device is a OP3T with the S6E3FA5 display panel, but not if your device is a OP3T with the S6E3FA3 display panel.
Note: I believe this changes the actual calibration for the "Default" selection in the display settings, but you will not see the name "Default" change to "DCI-P3"
Sources:
Credit to @rquandt on Twitter for getting the ball rolling: Tweet
Proposed command-line solution from ITHome: Link
Proposed modified apk solution from OnePlusBBS: Link
More discussion from OnePlusBBS: Link
Even longer thread (86 pages) from OnePlusBBS: Link
Even longer thread (583 pages) from OnePlusBBS: Link
This post to Weibo discusses S6E3FA5 vs S6E3FA3 compatibility: Post
Procedure:
Find out if your display panel is compatible (looking for S6E3FA5)
Install AIDA64 and check Display > "Panel ID"
(optional) I also checked to see if the profiles were available on my OP3T running Oxygen OS Open Beta 9 using a file explorer.
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 1 > sys/devices/virtual/graphics/fb0/DCI_P3
The changes will revert to previous configuration on reboot, so this must be re-applied after reboot.
To revert changes
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 0 > sys/devices/virtual/graphics/fb0/DCI_P3
I'm on VertexOS and DCI-P3 profile is not available in said location. Will flash OB9 and report back.
---------- Post added at 03:53 PM ---------- Previous post was at 03:20 PM ----------
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
twoxa said:
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
Click to expand...
Click to collapse
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled. DCI-P3 is a lot more colorful, but not quite as the default calibration, which is borderline psychodelic. The selected calibration will still read "sRGB" though, as this new standard isn't officialy included in OP3T software. And yes, after a reboot, calibration will return either to standard values, or sRGB.
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
twoxa said:
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
Click to expand...
Click to collapse
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
redsmith said:
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled.
Click to expand...
Click to collapse
Cool, sounds like it works even if you don't select "Default" before running the commands. Thanks!
redsmith said:
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
Click to expand...
Click to collapse
twoxa said:
Phone switches back to sRGB after reboot...
Click to expand...
Click to collapse
redsmith said:
after a reboot, calibration will return either to standard values, or sRGB.
Click to expand...
Click to collapse
I'll update the instructions accordingly. Thanks!
redsmith said:
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
Click to expand...
Click to collapse
So i think it's useless for now!
Let's hope for a magisk module,maybe...
Still trying to see if there's a way to enable a setting to allow this to work on S6E3FA3 display panels.
Found this mention of a "OPScreenColorMode.java" configuration file on the OP3T but I can't find where that would be on the device.
I decompiled the Settings.apk and couldn't find the file, but I did see a mention of that synonym (as well as OPNightMode and OPReadingMode) inside "display_settings.xml":
Code:
<PreferenceScreen android:title="@string/oneplus_night_mode_enabled_op" android:key="oneplus_night_mode" android:fragment="com.oneplus.settings.better.OPNightMode" />
<PreferenceScreen android:title="@string/oneplus_reading_mode" android:key="oneplus_reading_mode" android:fragment="com.oneplus.settings.better.OPReadingMode" />
<PreferenceScreen android:title="@string/oneplus_screen_color_mode_title" android:key="screen_color_mode" android:fragment="com.oneplus.settings.better.OPScreenColorMode" />
Not sure where to go from here, though.
soccerwuedo5 said:
Not sure where to go from here, though.
Click to expand...
Click to collapse
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Hi all,
I packaged this into a Magisk module for everyone to enjoy. It simply runs the provided command as part of the Magisk late_start service.
Here is a link to the GitHub repo: https://github.com/doubleaykay/DCI-P3_Enabler_OP3T. I have submitted it to the repo.
In the meantime, I have attached a zip you can install in Magisk.
I have tested it on my own device and it works perfectly!
Enjoy!
Edit: Yes, this allows it to persist through reboots!
nicesoni_ash said:
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Click to expand...
Click to collapse
Thanks for taking a look! It seems the guys on OnePlusBBS have overridden that removal for compatible devices to add the menu items back in on the OP3T. It's over my head but maybe someone can replicate their efforts here.
Root required
Will add srgb button tomorrow
GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
I have an A3 display and I still see a change when using DCI-P3!
vampire36 said:
I have an A3 display and I still see a change when using DCI-P3!
Click to expand...
Click to collapse
That's awesome! I tried the app and saw no change but maybe there's some other variable involved.
Magisk module isn't working for me, but the command is
Navi44 said:
Magisk module isn't working for me, but the command is
Click to expand...
Click to collapse
You could at least be more specific and include OxygenOS version and Magisk version for him/her to compare. . .
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
tzbigworm said:
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
Click to expand...
Click to collapse
That is bizzare, maybe it's an issue with Magisk v13. Could you post your Magisk log?
I am using Magisk v12, the stable release, and it works perfectly fine for me.... odd.
Could we have more people test the Magisk module to make sure it works?
GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
This works like a charm! The colours take a bit of getting used to though.

Guide For customize U-touch On OREO based rom And enable Soft Nav Bars

Hello everyone ...First of all I want to write that these trick are for all version of android(6.0, 7.0, 8.0)
Lets go straight to the point.
Don't forget to check the screenshots below
I'm going to cover two topics
1. Customize U- touch
2. Enable nav bars
1. Customize U- touch
Step 1- Download any root browser (recommend Root browser classic by JRummy apps)
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic&hl=en
All u can get in screenshots below
Step 2- Open system
Step3- Open usr
Step 4- Open Keylayout
Step 5- Open fpc1020tp.kl file as text file via RB text editor
Step 6- YOU will get this
Key 158 BACK VIRTUAL
Key 249 MENU
Key 254 APP_SWITCH
Key 183 HOME VIRTUAL
Step 7- Now remember this
Space between back virtual and home virtual is 10 space(press space 10 times before writing virtual)
Key 158 is single tap
Key 249 is swipe right
Key 254 is swipe left
Key 183 is long tap
For google assistant just type
ASSIST VIRTUAL
Add any command after any key you want
Step 8- Edit, save and reboot
Now its your decision how you want to customise it..... I'll attach some screenshots of users below so you get an idea ...
2. Enable soft navbars
Just go to system--open build.prop as text file via RB editor-- add these lines to the end and save and reboot
qemu.hw.mainkeys=0
Bro thanks for the awesome post.. Whats the command for screen lock and Screenshot? I will edit it accordingly
Here is the magisk module which modifies u-touch activities..
https://forum.xda-developers.com/lenovo-zuk-z2/themes/module-t3695560
ashiskar said:
Bro thanks for the awesome post.. Whats the command for screen lock and Screenshot? I will edit it accordingly
Click to expand...
Click to collapse
Dont know about that command...but u can just try and write like screenshot and screen lock ...may they work...if not edit it back...this method is safe..or u can try any app from play store which give options for fingerprint customisation
Shubhi singhal said:
Dont know about that command...but u can just try and write like screenshot and screen lock ...may they work...if not edit it back...this method is safe..or u can try any app from play store which give options for fingerprint customisation
Click to expand...
Click to collapse
But its read only.. I cant find the permissions to change..using file explorer root add on
Edit: got the read and write
ashiskar said:
But its read only.. I cant find the permissions to change..using file explorer root add on
Click to expand...
Click to collapse
Is ur rom rooted?
Can someone assist to configure the button long press for Google assistant instead of long tap?
Shubhi singhal said:
Dont know about that command...but u can just try and write like screenshot and screen lock ...may they work...if not edit it back...this method is safe..or u can try any app from play store which give options for fingerprint customisation
Click to expand...
Click to collapse
For screen lock type SLEEP.
Kiranbhand1 said:
Can someone assist to configure the button long press for Google assistant instead of long tap?
Click to expand...
Click to collapse
I think for pressing the button there is another file to edit not fpc file i think generic.kl
Kiranbhand1 said:
Can someone assist to configure the button long press for Google assistant instead of long tap?
Click to expand...
Click to collapse
Ok so I try this really cool app button remaper...works absolutely good....now u can customise home button press not tap....Enjoy
Shubhi singhal said:
Ok so I try this really cool app button remaper...works absolutely good....now u can customise home button press not tap....Enjoy
Click to expand...
Click to collapse
Requires pro to do anything. Useless.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Fails to save build.prop
Chadlinje said:
Requires pro to do anything. Useless.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Fails to save build.prop
Click to expand...
Click to collapse
M still using button mapper without pro version working flawless for me....
For build prop: use the browser suggested in the first post..and u must have root access for this
TanajiKC said:
For screen lock type SLEEP.
Click to expand...
Click to collapse
Is there also a command for pulling down the notification window like it was with ZUI?
Cydas said:
Is there also a command for pulling down the notification window like it was with ZUI?
Click to expand...
Click to collapse
If it's working on zui then definitely there'll be a command ....if u can.... then flash zui and then open the same fpc1020kl file and copy the command
Shubhi singhal said:
M still using button mapper without pro version working flawless for me....
For build prop: use the browser suggested in the first post..and u must have root access for this
Click to expand...
Click to collapse
I am using the browser recommended in the first post and have given it root access too. Still fail to save build.prop
thepranavjain said:
I am using the browser recommended in the first post and have given it root access too. Still fail to save build.prop
Click to expand...
Click to collapse
You can use any build prop editor from the play store
And which "Key" is responsible for a long press and press on the u-touch?
mega_bodry said:
And which "Key" is responsible for a long press and press on the u-touch?
Click to expand...
Click to collapse
For press not tap....download button mapper from play store works very well...
Because fpc file is only for tap
Not for press
how to call "status bar"???
---------- Post added at 05:20 PM ---------- Previous post was at 04:23 PM ----------
juniofdm said:
how to call "status bar"???
Click to expand...
Click to collapse
iam read Google DOCs, but dont find...
https://source.android.com/devices/input/key-layout-files
does anyone know the command to go back to prev app?

Categories

Resources