Yotaphone 2 Lollipop Rom EU1.1.60 - YotaPhone

Hi all,
Finally I was able to update my yota from 4.4.3 to 5.0 via YOTAFLASHER.
now i see that on the e-ink panel when i try to read a book it's impossible to go back to library index. It's like there is no button to move back.
it happens also to you?

You have to tap on the screen and then will appear all keys

Related

[ROM][KRT16S] AOSP 4.4 - Reporting some bugs

Hey everyone, I use the Beta 3 of KRT16S ROM AOSP 4.4 KitKat and I experience some bugs that need to be fixed.
Post of the project : http://forum.xda-developers.com/showthread.php?t=2397511
When you lock the phone, the clock does not refresh correctly so when you unlock, the clock is frozen and you need to update the clock settings to unfroze it.
The sleep screen does not working.
When you are in the application menu, try to push the left button of your phone, the settings menu appears in the background so it's impossible to use it.
Look at the pictures I share to correctly understand what I say, sorry for the english... I'm french.
Need a fix please

[5.0][CM12] How to Activate On Screen Buttons and turn of Capacitive Buttons

Hey guys,
There have been a ton of people asking how to activate onscreen buttons and disable the capacitive buttons since CM12 builds have started rolling out. Obviously, at some point, these features will be rolled into the ROM, but until then, I figured it would be a good idea to simply present a step-by-step thread on the issue. There have been answers all over the place button nothing dedicated and centralized, so I figured I would help some guys out.
Things needed:
CM12 Build on any variety (currently K900 and bpear have "nightlies" available in development. Check em out.
Root access. Just flash SuperSU 2.16 (http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip) if you don't have it. Root is necessary.
Zip to turn of the backlights: http://www.mediafire.com/download/p385se5ia28cqab/noSoftkeyBacklight.zip (thanks @Moody for this)
1.) Activate On-Screen buttons
- Use a program such as BuildProp Editor (look it up on the Play Store) to create a new build.prop entry. Call it qemu.hw.mainkeys, and set it's value to 0. If you are doing this manually, just add the line "qemu.hw.mainkeys=0"
- Reboot.
2.) Deactivate Capacitive buttons
- Download Root Explorer or some other program that allows editing of system level files.
- Mount your system as R/W. In root explorer at least, when you get into the system, there is a button up top to do so.
- Navigate to /system/usr/keylayout. Open Generic.kl in with a text editor.
- Comment out the follow lines by inserting a pound sign (#) in front of the line:
key 158 BACK
key 172 HOME
key 139 MENU
After this, they will read:
# key 158 BACK
# key 172 HOME
# key 139 MENU
Therse are numerically ordered, shouldn't be hard to find within the document.
- Remount your system as R/O.
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Anyone know how to enable hardware home long press to get to Google now?
TjPhysicist said:
Anyone know how to enable hardware home long press to get to Google now?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Hi there, first of all, thanks. I am having a problem where after I disabled the capacitive buttons (Step 2) the power and volume buttons are not working. Thanks in advance.
You know how to enable menu key also?
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Yes any chance of getting home button long press as search? Default is the menu button doing this.
Its not working bro
Tried and followed your steps , disabling capacitive keys works but enabling on screen keys not working even after changing build.prop , also i read in some post that enabling on screen key mod will not work in cm roms is that true can any one confirm me?
i am using following rom its CM12
http://forum.xda-developers.com/oneplus-one/development/devrom-cm12-scheduled-builds-t2938372
its very stable didnt experience any glitch till now , multi user and guest account works , all the other features are working too, try it out friends.
Pure awesomeness, many thanks for this guide. I'm back to my comfort zone, onscreen for me is just more intuitive.?
BTW, how to bring back the capacitive lights? I tried to remove the script at /etc/init.d and it only bootloops after reboot.
Edit: Nvm, found it, re-flashing the ROM brings back all to the default behavior including the capacitive backlights.
kmakiki said:
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Click to expand...
Click to collapse
For some reason this step isn't working for me. I tried wiping cache/dalvik and it didn't fix anything
Can anyone give a screenshot of the on-screen buttons?
Is this possible to do in hydrogen OS? I love that rom, but i switch back since there is no option to turn off hardwer keys and enable software key in system?
Sent from my A0001 using Tapatalk
How to add volume button onscreen by editing buid.prop

Weloop Tommy Smartwatch (FAQ/Updates/Hacks)

The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!

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 ?

Back & menu keys problem [TEMPORARY FIX]

Hello K3 Note users!
So, about 5 months ago I discovered that my back and menu keys were not working. I tried rebooting the device, pulling the battery out, changing the ROM and I even opened the phone up, to see, if every wire was connected properly....but the problem wasn't to be found. I also tried to get some support from the Lenovo's website, but I ended up getting none.
Eventually I found a workaround, that does not fix the problem itself, but it makes the phone usable again.
The solution is easy and it has already been written before:
1) Flash a custom ROM.
2) Make sure that you have ROOT.
3) Download a file manager, that can make use of the root rights.
4) Go to /system/build.prop
5) Add the line: "qemu.hw.mainkeys=0" to the very end of the file.
6) Reboot and voila!
However, I found that some apps refused to work with the nav bar and some vital content of those apps got hidden by the buttons.
I managed to found a fix for this problem. It can be solved with a wonderful Xposed module titled "Hideable Nav Bar".
The plugin will create a little down arrow on the left of the nav bar. This will let you to hide the bar whenever you want/need to. When the bar is hidden, then bringing it back is as easy as swiping up a bit from the bottom of the screen.
(I won't give you the steps on how to install Xposed, because it has already been described in the general thread.)
Anyway if you have installed Xposed, then you want to go to "Download" and search for this module. After that you should install the module, activate it and then reboot your phone. :good:
I hope this post was helpful to some K3 Note users and if it did help you, then don't forget to press the "Thanks" button too!

Categories

Resources