Passwords and scripts - Chromebooks

I have a multi-boot touch screen enabled machine running Android as one of the partitions. I like the idea of transitioning from Android to ChromeOS, but I have to have use of Android apps. The Brunch project has given me a way to install ChromeOS and seems to work extremely well for what I need. But there are a few ChromeOS quirks that keep me from making the swap. Search seems to indicate they are not solvable at present, but maybe this community can help.
1. The biggest issue with ChromeOS is its insistence that I login using my full Google password every time. The Android (or ChromeOS) partition would not be my main driver, so simply sleeping is not a feasible option for me.
a. Is there a way to mod chromebook to login from cold boot using a PIN? And if so, would such a mod survive updates? Sorry, I'm pretty sure that's a hard no, but it's worth asking.​
b. Alternatively, I think I could get this to work if I could hibernate (suspend to disk) to work. I know suspend to disk is not part of the nominal use case of chromebooks, so maybe it's not even supported? Either way, I'm struggling to fine resources for it. If that worked, then I think that I could simply login with a PIN most of the time.​
2. Brunch includes a great mod to allow tablet mode to be turned on/off by way of terminal. What would be better is to have a link to a script that could toggle with a tap (or maybe two). But I don't see a way to run a script for android terminal without going into terminal. Is there a way to run scripts without having to switch to the terminal? Bonus points if I can give that way an icon and stick it in the dock.

Related

Overlay in 6.0 breaks Android, why is no one else complaining?

Lets say I want to enable disk access to "drives" (a great software product to display dive space utilization), I can not do so there is no way to do so as I get a message "Screen Overlay detected", of course it is detected I have over 10 apps that require it, if I disable it they do not work PERIOD. so I need to have it enabled, nut then I have many apps that simply do not support Marshmallow (6.0) at all as a result. I can not understand why there are not more complaints and fixes for this as I'm basically stuck I have apps that require overlay including my dialer and I have apps I need that I can not use if overlay is enabled!
One work around I heard of was to boot into safe mode and run the apps there, but in safe mode I can not run any third party apps (so I can not execute those that I need to overlay disabled to set a permission.
I need help, either to fix the overlay prompt (simply put at this point security be damned I'll live without it I need the software to function), but searching and searching I've yet to see any solution or even suggestion beyond safe mode, which does not let me execute the software I need to fix, other than down grading (which does not help since at some point I'll need to move to 6.X), how does one fix the very annoying and Android breaking issue of overlay?
I just do not understand how Overlay a very necessary feature is also able to break many apps, including a few that require overlay themselves. I'm completely confused and sick of wasting time (hours at this point trying to figure out how to get around this).
Thanks,
ERIC

Can't change location or screen orientation

Hi all,
Hope I'm posting this in the right place. If not, please move.
I have Remix_OS_for_PC_Android_M_64bit_B2016072603 installed as a virtual guest in Virtualbox 5.0.24_Ubuntu r1083 with Xubuntu-core 16.04 as the host machine. Using a Toshiba Satellite Pro L510. Took me four days to nut out how to get to this point, but installed and booting and stable now.
My issues:
1/ Location: When I try to run an app from Play Store it thinks I'm outside of Australia/New Zealand (the app I'm trying to run is specific to those regions). I'm in Australia, the app works fine on my phone (am logging in exactly the same way).
(* Update: I installed GPS Status and it tells me GPS is not switched on. Was hoping to then change the location with Fake GPS, which I also installed. It won't do anything with same message: GPS not enabled or similar.)
2/ Resolution: The screen defaults to portrait, as expected I suppose, but I have a 1366x768 monitor and it doesn't fit in the screen. Consequently, I have a scroll bar because as Virtualbox Guest Additions is not compatible with Remix OS at this point there is no mouse integration (I need to hit Right Control to use mouse in host and same to use in guest again). I need to press a bunch of keys to just scroll the screen up and get back to where I was going. :|
Other than that, all working great, Remix OS is great, thanks to the team that created it. The main reason I was wanting to use it is to use this one app on my computer (AFL Live) and plug my computer into the TV. I don't use my phone for anything other than that one app, SMS and the occasional call so I am by no means an Android junky. In fact, before this, I knew very little about it (but a lot about Linux/Ubuntu).
This install has been a quest, a learning curve, and these are my last two hurdles so I'm calling for help if it's out there. Trawled the net, tried some things, but have hit a brick wall with these two problems.
My first post so not sure of the protocol. If these two issues should be the subject of two separate threads, mods please advise and I will edit accordingly and create a new thread.
Tnx in advance.
(* Further update: Just having a read of this: http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
Wondering if rooting the device would allow me to change any of these, in particularly, the location to Australia where it should be, or switch on GPS so my app can see where I actually am. I'm presuming it thinks I am in the Cocos Islands or somewhere else!)
(* And further update: The screen resolution was as easy as typing Alt+F1 to launch a terminal then 'wm size 1366x768'. That looked terrible, though, so changed it to 1048x768 (from memory) and it is good enough, though not perfect. I may be able to get closer with further tweaking. Now the last, and most important, hurdle to leap: How do I get Remix OS, and more specifically my AFL app, to know I'm in Australia. Frustration. It's taken about ten days, on and off, to get here and still not quite where I want to be, but hopefully my travails can help someone else along the way ...)
Gave up on it. If anyone comes up with a way of running Remix OS in Virtualbox and setting the location, please post. Guestadditions would probably fix it and maybe one day ROS will be compatible with it.
On the other hand, I did learn a lot more about Android than I cared to know, but am now thinking about buying my first ever Android tablet to do the job with a USB/HDMI adapter.

[02/05/17][HUB] Megathread

Hello, everyone!
If you aren't an expert - that's okay. Everyone is welcome and you're free to ask questions.
Make sure to check the date this post was updated (I may forget to update the date in the title) which is located at the bottom of this post. If this post hasn't been updated in more than a month, contact me and I'll refresh everything.​
Quick Introduction:
I'm new to the Yoga Book squad, and I've noticed one major downside.... the forums are a total mess. So what I'm hoping to do, is to keep this thread as up-to-date as possible, with links to guides, development progress and anything else.
I figure to make this more... tidy, I will enforce a colour-coding system for each sub-thread-guide-thingy, so you can instantly tell whether a guide or method to do something to your Yoga Book is risky, and most likely experimental, or is well tested. These will probably be done via experiments on my own Book (the wifi-only version), but of course I will hope via this community thread I will be able to provide more detailed statistics and such as everyone does their own thing to their device.
If you have anything to add to this thread, or would like to help out with anything; please feel free to contact me or just tell me what you're thinking - I'll do my best to read everyone's replies.
General Yoga Book Information
To my knowledge, there are two versions of the Yoga Book, each with two sub-versions for the OS:
1.) YB1-X9aF - this is the Wi-Fi version
2.) YB1-X9aL - this is the LTE/4G version
Where the "a" between the 9 and the F/L is either a zero or a one, depending on the installed OS (Android: 0, Windows 10: 1)
The SIM card is a Nano-SIM with 3G capability.
Other than that, all Yoga Book devices share the following specifications:
- 10.1 inch IPS display, of resolution 1920x1200
- Intel Atom x5-Z8550 processor, which:
----+ Has an architecture of x86_64
----+ Core base clock of 1.44 gigahertz
----+ Core boost clock of 2.4 gigahertz
----+ 4 cores and 4 threads
- Battery capacity of 8500 milliampere hours
- On-board storage of 64 gigabytes of solid-state storage (SSD)
- 4 gigabytes of random-access memory (RAM)
- A microSD card slot capable of up to 128 gigabytes of storage
- Two camera's, one above the display and one on the keyboard
- Wi-Fi (802.11 ac) and Bluetooth (v4)
- 3.5 millimetre headphone jack
- Micro-USB 2.0 OTG port
- Micro-HDMI port
Colour (or color) Codes and Tags:
For those who like using grey-scale display filters or whom are colour blind, I've added a "level" to each of them, where level 3 is like... crazy meltdown experimentation mode, and 1 is stable-ish (probably as stable as it'll get unless a REAL developer takes on the challenge).
[X] - Means that you will have to delete some or all of your data for it to work
[R] - Means that it requires a Rooted device
[Level 3] VERY EXPERIMENTAL - Use with caution, and with the knowledge that you may boot-loop, brick your device or lose your data!!! OR ALL OF THOSE THINGS!! Make sure to backup everything you hold dear, and just for good measure you'll have something to fallback on.
[Level 2] NOT WELL-TESTED - This will probably work for most people, but things may be unstable at the best of times. Again, make sure you have a backup before trying level 2 items.
[Level 1] 99% FINE - If there's an issue, it's probably your own fault... but again, I can't guarantee that everything I or anyone else does is perfect and will work for everyone! You should probably still have a backup, but if you're lazy like myself it's okay, I forgive you.
Android M/6.0
Rooting, backups, and more!​
[1][X] Unlocking the Bootloader
earthCallingAngela wrote a really nice guide for unlocking the bootloader. The original thread is here, but for those who are too lazy to open the link in a new tab I've quoted the information.
IF YOU APPRECIATE THEIR EFFORTS GO AND THANK THEIR ORIGINAL POST!!!
Remember, unlocking your devices bootloader will format your storage (meaning you'll lose all of your data), so backup anything important before proceeding.
earthCallingAngela's OP: https://forum.xda-developers.com/yoga-book/how-to/how-to-unlock-bootloader-t3502216
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Click to expand...
Click to collapse
[3] TWRP Custom Recovery
danjac has written a post about his attempt at getting a modified version of TWRP running on his Yoga Book. From what I can tell it was a success, besides a few bugs (which are avoidable... I think).
WARNING! MAKE SURE YOU READ THESE!!
Before you go ahead and just flash his version, make sure you know the consequences that could arise if something goes wrong. If the recovery of your device screws up, you don't really have much to bring it back to life with. Even though there shouldn't be many things to worry about, it's still very risky.
In fact, it is recommended you ONLY temporarily boot into TWRP, instead of just flashing it like you would on another device. danjac's OP gives more information for you to use.
If you think you are willing to take the risk and know what you're doing, I highly suggest you make a complete backup of your device if possible. So far there isn't really a way to get your stock recovery back (since we don't have a custom ROM or a way to download Lenovo's modified version online).
danjac's OP: https://forum.xda-developers.com/yoga-book/development/recovery-twrp-t3533980
[2] Rooting (via Magisk)
danjac wrote the first guide to rooting the Yoga Book, and you should, again, go and thank his original post. However, his OP is now a bit outdated, Magisk (currently v12.0) now includes a root module (MagiskSU) based on phh's SuperUser.
Please note: If you are already rooted via a different method (and maybe you want to change because it didn't work... or something like that) you have to go into your super-user manager and uninstall it. If you have a previous version of Magisk installed, there is an uninstall ZIP that you can flash, which will remove any Magisk version, including MagiskSU. Again, more details on the main Magisk thread.
Do I NEED to unlock my bootloader to Root my device?
The short answer is yes, and the long answer is sort-of. You only need to unlock your bootloader if your ROM doesn't support Rooting out-of-the-box (which in Lenovo's case, it isn't supported). However, you can lock your bootloader afterwards if it's such a concern to you. Yeah, you probably will stop receiving over-the-air updates from Lenovo, but they're probably not going to push out another update for a long while, so in my opinion it's nothing to worry about.
Follow the instructions on the main Magisk page to install it if you're new to Magisk, but if you know a thing or two then I'll paraphrase:
- Flash the latest Magisk ZIP file via the TWRP Recovery (if you have it) or just flash it over ADB
- You should also download the Magisk Manager from the Play Store to make sure you're always up-to-date
danjac's OT: https://forum.xda-developers.com/yoga-book/how-to/root-yb1-x90l-how-to-t3534268
Magisk's main thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[2] Dual-booting Android and Windows 10
Since there isn't a place to get the Android side of things, I won't put too much info here.
Although if you're already running the Android version and want to know how to put Windows 10 on your device too, look at this thread.
Dual-booting OT: https://forum.xda-developers.com/yoga-book/help/android-to-windows-hack-dual-boot-option-t3475733
[3][X] Custom ROM
Currently there is no custom ROM which supports the Yoga Book, mainly for the simple fact not many people own the device. However, if we make enough noise in the community I'm sure someone will crack under the pressure ;P
Although, I'm doing my best efforts to merge the device drivers and such into the Android Source code, but you shouldn't get your hopes up. If I ever get it working, it will probably be unstable and not that great (I don't have much experience with the details of the Android OS), I'm running off my knowledge of the Linux OS.
If you're using the Windows 10 version of the Yoga Book (I'm sorry you paid the extra $50!!), hopefully Lenovo will at least release a version of their own ROM soon (or put it back from what I've heard). I've also heard that they're upgrading to Nougat in October (of 2017)... so we've got plenty of time to find another solution to our sorrows.
Information for Developers:
Someone has also posted a backup of their working Lenovo-customised Android OS, but I won't post a link here because:
- It's only a backup
- May draw un-wanted attention to the link
But if you're a developer and you think that will help you, you can easily find it somewhere in these forums.
EDIT: The link has now been removed (I can't find it)
If you're trying to
Code:
repo sync
the AOSP and you're getting stuck syncing the work tree, try doing this (from the folder you're trying to sync to):
Code:
rm -rf frameworks/compile/slang/
mkdir /home/<user>/slang_helper
sudo ln -s /home/<user>/slang_helper frameworks/compile/slang
Please be careful when typing commands into your terminal, especially from the internet, and especially when you don't understand what the commands are doing.
Lenovo's source code download: http://pcsupport.lenovo.com/au/en/products/tablets/yoga-series/yoga-book/za0v/downloads
[2] Linux without removing Android
Thanks to @Tiggi2017 for making the first guide. His OT here is a good one to read through if you're interested in this.
Via a few apps and some commands, you're able to have a "Linux" OS running on your Android device with the Halo Keyboard and such still working perfectly.
His original method doesn't need Root access apparently. However, there are other methods that may be easier for some people if they have a Rooted device. Look through the comments in that thread for more information.
OT: https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
Apps, tips and tricks!​
[1] Apps That Support Multi-Window
Thanks to sashlon1138 for doing most of the hard work by putting this list together (may not be complete, if you know of more apps that work let me know so I can add them!).
Thanks to uuang for getting the ball rolling.
Thanks to Csilla4 for finding the first calculator app that works.
Thanks to docoli for also finding a huge list of compatible apps.
Csilla4:
- iDo Calculator
uuang:
- RAR
- Google Photos
sashlon1138:
- Chrome (but not beta)
- Facebook
- Messenger (Facebook)
- Gmail
- Outlook
- Youtube
- VLC
- Google Search
- Home
- Instagram
- Pinterest
- Dolphin Browser
- Ebay
- Paypal
- Flow Free
- Google Maps
- Google Earth
- OneNote
- Wikipedia
- ES File Manager
- Twitter
- Evernote
- Reddit
- Skype
- Candy Crush Saga
- Candy Crush Soda
- Candy Crush Jelly
- Spotify
- Soundcloud
- Opera
- Opera Mini
- Yahoo Mail
- Viber Messenger
- MX Player
- Google Translate
- Shazam
- AliExpress
- Tumblr
- Twitch
- Mega
docoli:
- Microsoft Word, Excel and Powerpoint
- Softmaker Textmaker HD, Planmaker HD and Presentations HD
- RealCalc
- Adobe Acrobat
- CamScanner
- MindjetMaps
- LinkedIn
- ezPDF Reader
- Detexify
- HERE WeGo
- Google Street View
- Öffi (German Public Transportation Schedule app)
- DB Navigator (German Railroad Schedule app)
- Kindle
- Amazon Prime Video
- Maxdome
- Barnes & Noble Nook
- Audible
- TuneIn Radio
- TED
- Babbel
- dict.cc. plus
- Amazon
- Nine (you can even have any number of items in parallel on the screen, e.g., inbox, calender, contacts, notes)
- OneDrive
Link to OT: https://forum.xda-developers.com/yoga-book/help/multi-window-apps-t3565253/post71494066#post71494066
[2] Changing the DPI
WARNING! Do not change your DPI to extreme values! You may render your device useless (unless you already have set up ADB and know how to revert the changes)!
Thanks to melando for bringing up the actual default DPI values.
Just so you are aware, if you're running Android 7 (Nougat) or later, you can adjust the "DPI" to some preset values from the settings app.
Using this site, I calculated that the Yoga Book has a technical DPI of 224 pixels per inch, with a resolution of 1920 by 1200 pixels, over a 10.1" screen (diagonal). However, the default Lenovo has set it to may be actually 280. They suggest that you may find it better if the DPI is set to 240.
This is a trivial modification if your device is Rooted. All you have to do is open the Play Store, and search for something along the lines of "DPI changer", and find an app that has good reviews.
An example app would be "Easy DPI Changer [Root]"
If your device does not have Root, then you will have to have a computer with ADB installed.
To install ADB, do a quick Google. There's bound to be a guide there somewhere (I'll put one here soon).
Once you have ADB installed, you can follow this easy guide to change your DPI to whatever you like.
DPI Calculator: http://dpi.lv/
Non-Root Method: http://www.androidbeat.com/2015/07/how-to-change-dpi-of-android-device-without-root/
[1] Recommended Apps...?
There isn't anything here as of yet, because I haven't gotten far enough to look for any good apps that work well with the Yoga Book. So right now I'm going to rely on everyone else for that. I'll get there eventually.
However, you should at least download Magisk Manager from the Play Store, to manage your Root and other neato Magisk features.
If you're a developer, and need guinea pigs to test your stuff on, I am happy to help anyway I can (and I'm sure much of the community is too).
If anyone needs help, I'll do my best to assist, but if it's anything too tedious (such as teaching you how TWRP works or something along those lines), you should probably have a look on the internet for tutorials and guides for that stuff. There are plenty of people out there who can explain concepts better than myself.
Windows 10
Simple customisations!​
[1] Touch-pad Customiser
This program was first put into the spotlight by dinosauria123, so go to their original post and thank them for finding this.
This small program lets you modify some simple variables associated with your touch pad, only requiring a reboot after you change something.
Features:
- Setting extended right click area
- Setting unlock area
- Setting mouse pointer acceleration
- Setting scroll direction
- Disable Touchpad clicking (added in version 1.4)
Click to expand...
Click to collapse
OT: https://forum.xda-developers.com/yoga-book/themes/yoga-book-touch-pad-setting-application-t3569836
[1] Minor Halo KB Customisations
If you were wondering if there was a simple and easy way to lower the brightness of the Halo Keyboard, or just get rid of those pesky battery-draining touch vibrations for every key press, there is a way!!
Best of all, you don't have to download it! It's already installed!!
To find this not-so-well-hidden app, you have to either go to your Program Files, or open the good-old Control Panel (thanks to urayandro for pointing out that it's in the Control Panel!).
Control Panel method: Once you're in the Control Panel, just click on "Appearance and Personalisation", and you will find the "Halo Keyboard" program right at the bottom.
Program Files method: For 99.9% of people this is on your Local Drive (C: ). It may be located in your normal Program Files or it may be in your x86 Program Files, I'm assuming it depends on whether you're using the Windows 10 your device originally came with, or you have re-installed it (thanks to sawyerbenjamin for informing me that for them, it was in the normal Program Files folder). Assuming it's in your normal program files; go to Program Files/Lenovo/ and there it is. The application name is "ControlApp.exe". You can also make a shortcut to this application - I put a shortcut on my Desktop.
It allows you to:
- Toggle the touch tone/sound
- Toggle the vibration on keypress
- Adjust the time it takes for the keyboard lights to turn off
- Adjust the backlight (or whatever that is called) brightness for the whole keyboard
Risky or experimental customisations!​
[2] Using AMIDuOS (Android Emu)
Update: I've spent a bit of time trying to use this, and in my opinion it's not worth the time. But if you need a development environment for something, it's pretty good at that. :/
In my attempt at replacing my Windows 10 installation with any version of Android I could find, I ran across this program called AMIDuOS. It's similar to emulating an Android system while you're in Windows, but instead of running it in a virtual environment, it runs directly on your x86 hardware (which is what the Yoga Book uses).
If you're cool with having a Windows 10 version of the Yoga Book, but still want to use some Android applications (possibly for drawing, or maybe just because the Android ecosystem is miles better compared to the Windows one) this may be a good solution for you.
Currently, they support Lollipop and Jellybean (not Marshmallow). However, this program is not free. You can trial it for free though. I'm fairly certain the full price is $10 USD.
It's not a difficult thing to set up (apparently), so if you wanna try something out and know how to deal with possible emulation problems (although unlikely) it may be worth it.
AMIDuOS Website: http://www.amiduos.com/
[2] Process Lasso
Huh? Process what-now? Yep, Process Lasso is a very complex program filled to the brim with algorithms tailored mainly towards getting the best performance and responsiveness, and to control those pesky rogue background processes that slow down your device when you don't need them to.
This program is completely free (but it does have a Pro version if you want a few extra customisation's and want to support the developers) and I've found it works pretty well, especially with a low-power device like the Yoga Book.
Since the Yoga Book is meant to be a very portable device, I'm not using Process Lasso to get maximum performance (as that would obviously drain the battery life quickly), I'm using it to make sure that if there's a program that needs to use power and deplete my battery life, then it's something I want - not some dodgy Windows background processes or other stuff like that.
It's pretty easy to set up. I've got a few of the main features enabled, and I recommend that you use similar settings.
I've enabled:
- ProBalance; this will keep the background processes in check, and allow the foreground processes to take the reigns of your CPU, insuring you experience minimal stutters.
- SmartTrim; this is an optional one, since I'm constantly micro-managing the applications I've got installed on my 64GB internal drive, this should help to prolong the performance of my drive, making sure it's well pruned (that's a pretty good analogy actually)
I've turned off the tray-icon showing me the CPU utilisation, so that doesn't need to waste any of my precious battery life (I'm usually a battery-life extremest), but you don't need to do that.
So if you're experiencing major delays when just doing simple things like moving around the Windows 10 user interface due to rogue background processes, I highly recommend you give this program a try.
Also, if you're a pro-ish-user like myself, feel free to dive deeper into the program. It's filled with toggles and adjustable's for you to play with and tailor the program to your needs, and almost everything you can change is accompanied with a tool-tip explaining what it does. Enjoy! But of course, as always, be careful of what you change - there are some things that could make your system really slow and or unstable.
P.S. The Yoga Book uses the 64-bit system, so choose that version of the program.
Website: https://bitsum.com/
Reserved
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Con_Sole said:
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Click to expand...
Click to collapse
I'm not entirely sure, however flashing something to your device (via TWRP at least) does require an unlocked bootloader. So without an unlocked bootloader, I don't think there's a way to install MagiskSU. Sorry about that... :/
I will have a look around and see what I can find, though.
Con_Sole said:
Does anybody know, whether bootloader unlocking is necessary for magisk root?
Click to expand...
Click to collapse
So I've done more looking around and here is your answer: Yyyyeeeeaaaahhhhhh......?
Magisk itself does not require an unlocked bootloader, however, it does require root access. Usually to get root access you need to unlock your bootloader, unless it comes already rooted in a custom ROM (but in our case, it doesn't). Unlocking the bootloader is a relatively safe procedure to perform, so [in my opinion] you shouldn't have anything to worry about!
nan0s7 said:
[1] Minor Halo KB Customisations
If you were wondering if there was a simple and easy way to lower the brightness of the Halo Keyboard, or just get rid of those pesky battery-draining touch vibrations for every key press, there is a way!!
Best of all, you don't have to download it! It's already installed!!
To find this not-so-well-hidden app, you have to go to your Program Files. For 99.9% of people this is on your Local Drive (C. So to get to it, go to Program Files (x86)/Lenovo/ and there it is. Its very helpful and informative name is ControlApp.exe.
It allows you to:
- Toggle the touch tone/sound
- Toggle the vibration on keypress
- Adjust the time it takes for the keyboard lights to turn off
- Adjust the backlight (or whatever that is called) brightness for the whole keyboard
Click to expand...
Click to collapse
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
urayandro said:
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
Click to expand...
Click to collapse
Indeed it is! Consider that noted ;P
urayandro said:
it's not not-so-well-hidden app.... it's not hidden at all. you can found it under "appearance and personalization" section of retro control panel.
Click to expand...
Click to collapse
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
sawyerbenjamin said:
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
Click to expand...
Click to collapse
Huh, well it must depend on whether you kept the original installation of Windows that came on the device, or whether you reinstalled it (or came from Android). I'll add that information. Thanks!
sawyerbenjamin said:
I found it in my normal Program Files folder. (x86) only contained a folder for LenovoPaper.
Click to expand...
Click to collapse
Same here. In my device is also only contain LenovoPaper under \Program Files (x86)\LenovoPaper
What i mean with retro control panel is old window's control panel. not the win10 setting. You can access it by:
1. Click start and type "control panel" then press enter.
2. You should see control panel window that similar to older version of windows.
3. Go to "Appearance and Personalization
4. Under there you should see "HaloKeyboard" shortcut.
You can also create another shortcut of this app by right-clicking it then choose create shortcut. Windows will make another shortcut on the desktop. I did this to get easier access when need to adjust keyboard brightness.
Hey there,
i think there is a way to flash the win 10 image on my yb1-x90f. just don't wont to brick it and so i have a few questions to all of you experts. in other words, i need your help
there is a quide i found in internet, which i think could work. But there are words i've never read before like "RUSB". is this an important word? i attached as low quality pdf...
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
maybe we can put together, 50/50 so its 25$ for me and you?
i think you know which page is meant. if not pm me
like descriped in the guide, (part 3) we have to select "Boot Menu" and after that "EFI USB Device"
But my bootloader looks different (android version).
is there a way to flash the image via original android bootloader/recovery or do we need to find a way to get into the other bootloader?
in this post: https://forum.xda-developers.com/yoga-book/help/bricked-yoga-book-yb1-x90l-t3537048
 @mmusaad managed to get into this kind of "mode" but i think its a dangerous way and he had a big luck to "unbrick" his device. maybe onyone find an easy way to go into this "windows bootloader" or whatever?
so maybe we can work togehter
woodirk said:
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
Click to expand...
Click to collapse
Probably wrong translation from Chinese... Should read USB-R. There are USB Ports which don't support remote drives
woodirk said:
there is also the win 10 image online. but we have to pay for it because it's "exclusive" stuff. 50$
Click to expand...
Click to collapse
Windows was never free, that's why the Windows Yoga Book is $50 more expensive. A Win-Image will not help you either, as Lenovo brands the Product Key into the Bios.
jamespmi said:
Windows was never free, that's why the Windows Yoga Book is $50 more expensive. A Win-Image will not help you either, as Lenovo brands the Product Key into the Bios.
Click to expand...
Click to collapse
OMG sometimes i think "together" :highfive: is a heavy word... :crying:
what about this ? (see attachement)
and stop letting me look like an idiot...
I'm on the YB1-X91F, which is the Windows version. Unfortunately for us, the Android and Windows versions of the Yoga Book have totally different BIOS's. This is the main thing stopping us from being able to dual-boot.
Easy-firmware has both the Android and Windows' ROM's, but they only provide instructions on how to overwrite the current operating system, not the opposite ones. I have downloaded everything they have on the Android side of things, and everything except the Windows ROM on the Windows side.
While I was messing around with my device, I did brick it. But I was able to get an SD-card with a Windows bootable "USB" install on it, and went through the installation process on my external keyboard. Then from there was able to install the drivers and restore the Windows version with everything working after a bit of time. I don't know how different this would be if you don't mind getting rid of the Android bootloader totally, but that's not really recommended.
What we'd need for getting Android alongside the Windows version is a way to get a working Fastboot/ADB connection.
For the Android version getting Windows alongside it, you need a way to get the Android bootloader to point to and recognise the Windows installation. However, this is almost impossible unless you have a custom ROM, which we do not have that supports the Yoga Book. You could probably delete Android totally, and then install Windows from there, but I'm not 100% sure because I haven't messed around with the Android version of the tablet.
We'd need a way to get the Android BIOS and Fastboot off of it so we can then use it to our advantage.
nan0s7 said:
I have downloaded everything they have on the Android side of things, and everything except the Windows ROM on the Windows side.
Click to expand...
Click to collapse
that's good to know...
nan0s7 said:
You could probably delete Android totally, and then install Windows from there, but I'm not 100% sure because I haven't messed around with the Android version of the tablet.
Click to expand...
Click to collapse
this is exactly what i want to do and where i need your help
imo this will help us https://forum.xda-developers.com/showpost.php?p=70540959&postcount=7
woodirk said:
what about this ? (see attachement)
Click to expand...
Click to collapse
That probably flashes a valid Serial Number into the Bios...
DPI settings
I believe default DPI may actually be 280 - there's a Lenovo forum thread recommending setting it to 240 which I have found reduces the size of icons etc. so 224 does not seem right
melando said:
I believe default DPI may actually be 280 - there's a Lenovo forum thread recommending setting it to 240 which I have found reduces the size of icons etc. so 224 does not seem right
Click to expand...
Click to collapse
Thanks for the information! I've added a bit to the DPI section about the other values.
nan0s7 said:
Thanks for the information! I've added a bit to the DPI section about the other values.
Click to expand...
Click to collapse
However now that the Nougat update is out some adjustments can be made in Display Settings...
melando said:
However now that the Nougat update is out some adjustments can be made in Display Settings...
Click to expand...
Click to collapse
Oh yeah forgot that happened (I'm on the Windows version). Fixed it now!

Commercial grade Android tablet issues accessing adb or developer mode

So I came into possession of a commercial grade advertising kiosk (Nintendo Amiibo Display) that runs an Android OS 4.1.1. The device is setup to auto load the "AmiiboFrameWork.apk" package installed. The model of the system is DucoTech D185-ACA-720. I can access basic Android settings menus through a special key combination. Mainly system information, network setup, and volume controls. There is a menu that says App Install and gives the option of installing APKs from SD card or USB with a file structure of USB:\APKFiles\ or SD Card:\ApkFiles\. However no matter how I layout my file structure or name my APKs following that structure nothing appears in this menu to install. However There is a media tab for photos with a similar structure and photos I put on the card do show up. What I'm trying to figure out is how either install APKs, or access the base android system so I can customize the system to run custom apps I plan on making for it. However I want to retain the original AmiiboFrameWork APK or the whole OS so I can restore the system later if I want.
Now what I have tried is plugging it into my PC via the USB-OTG port while on, putting APKs in various file structures and naming conventions, booting it with my PC connected via OTG port, tried to trick my way into other menus through keyboard and settings menu tricks (similar to how people use to bypass lock screen security through menus).
Results:
1. OTG to PC while on: Device shows up as 2 USB 2.0 Flash drives in device manager. The drives appear in my computer but aren't accessible. ADB doesn't see it as an android device.
2. APKs on usb: Nothing shows up in the menu regardless of my naming convention or file structure.
3. Boot device while attached to PC via OTG port: My computer detects it as an NES Classic (previously installed the driver to mod my classic). This leads me to think its an Allwinner device or similar since that is what the driver was made for I believe? ADB still doesn't see it. This might be my best bet to get in.
4. Menus: Options are very limited and I wasn't able to access anything valuable aside from Install APK, Transfer Media, and Set startup APK.
5. Tapping build number: Tapping the build number in settings any number of times doesn't activate the developer mode options. The prompt doesn't even appear for it.
If anyone can assist in trying to gain access to this system, or even figure out the file structure so I can just install my own APKs like I want that would be great. Any ideas on where to look, what to try, and so on is greatly appreciated.
Here are some photos of the main board just in case
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
hedburnr said:
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
Click to expand...
Click to collapse
IDK what to say man other than what in God's name made u think framework.res needed to be pulled. It's gone man barring the original firmware and itself install method
hedburnr said:
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
Click to expand...
Click to collapse
I work with Ducos! In fact there's an Amiibo kiosk a few feet from me here in our offices
mojoswagger1980 said:
IDK what to say man other than what in God's name made u think framework.res needed to be pulled. It's gone man barring the original firmware and itself install method
Click to expand...
Click to collapse
AmiiboFramework doesn't have anything to do with the "framework.res", Nintendo just called the app the "AmiiboFramework"
They only install APKs with a specific package name in a specific folder on your USB device / SD Card (com.general.mediaplayer.player). Unfortunately Nintendo used a different folder than us, and I don't recall what it was. You can go into a "normal" Android screen using a special procedure if the AmiiboFramework app is installed, but it should work without it too:
- Wait for the Loading screen to appear
- Begin to press the CSR and Setup buttons together, quickly alternating between them. Repeat until the CSR appears
- After the CSR appears, leaving the screen open for an extended period of time will cause the Amiibo Display Framework to re-appear
- If Alt+Tab is used, be sure to return to the CSR before returning to any other app, or the CSR will reboot the player
Alt+Tab refers to using a USB keyboard, after you have the CSR up you can exit with it.
They're really not great hardware for general usage.
selaliadobor said:
I work with Ducos! In fact there's an Amiibo kiosk a few feet from me here in our offices
AmiiboFramework doesn't have anything to do with the "framework.res", Nintendo just called the app the "AmiiboFramework"
They only install APKs with a specific package name in a specific folder on your USB device / SD Card (com.general.mediaplayer.player). Unfortunately Nintendo used a different folder than us, and I don't recall what it was. You can go into a "normal" Android screen using a special procedure if the AmiiboFramework app is installed, but it should work without it too:
- Wait for the Loading screen to appear
- Begin to press the CSR and Setup buttons together, quickly alternating between them. Repeat until the CSR appears
- After the CSR appears, leaving the screen open for an extended period of time will cause the Amiibo Display Framework to re-appear
- If Alt+Tab is used, be sure to return to the CSR before returning to any other app, or the CSR will reboot the player
Alt+Tab refers to using a USB keyboard, after you have the CSR up you can exit with it.
They're really not great hardware for general usage.
Click to expand...
Click to collapse
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Enmity said:
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Click to expand...
Click to collapse
There isn't much more documentation than what I mentioned unfortunately. The people who you'd get in a call definitely don't know anything about them (I don't think Nintendo made the AmiiboFramework app in-house either). If you want to repurpose it, you can try getting into the CSR and going into the normal Android Launcher. Try connecting over ADB and force-stopping any process with the letters "csr" in it's name
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Enmity said:
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Click to expand...
Click to collapse
There isn't much more documentation than what I mentioned unfortunately. The people who you'd get in a call definitely don't know anything about them (I don't think Nintendo made the AmiiboFramework app in-house either). If you want to repurpose it, you can try getting into the CSR and going into the normal Android Launcher. Try connecting over ADB and force-stopping any process with the letters "csr" in it's name
To connect to ADB use a USB mini cable on the "USB OTG" port and ClockworkMod's Universal ADB Driver
I have a few devices similar to this. They are duco DT156-AS4-1080. I was wanting to repurpose them as video players. The devices are wiped of content and load into a main menu. There is an option to exit to administrator, though it asks for a password. I dumped the partitions and tried to look through the binaries, but am unable to come up with anything. I can get into superSU and then exit to playstore, but then some type of watchdog kicks me back to the duco menu. Any help appreciated.
er0ck said:
I have a few devices similar to this. They are duco DT156-AS4-1080. I was wanting to repurpose them as video players. The devices are wiped of content and load into a main menu. There is an option to exit to administrator, though it asks for a password. I dumped the partitions and tried to look through the binaries, but am unable to come up with anything. I can get into superSU and then exit to playstore, but then some type of watchdog kicks me back to the duco menu. Any help appreciated.
Click to expand...
Click to collapse
Just uninstall com.general.mediaplayer.* (anything that starts with that package name) and you should have a normal device
I DID IT! Working tablet
So the story is yesterday I found an Amiibo display at my apartment dumpster where people put stuff they don't want that still works, I nabbed it with the intention of salvaging the "monitor." Judging by the hammer-marks on the acrylic enclosure, and pry marks on the metal cage that held the power supplies for the led strips and the tablet I assume somebody took it home, got frustrated by the locks and screws after some prying, and just busted in the acrylic window to get to the floor model Amiibos.
I cracked it open, and after some fun with a butane torch to melt the acrylic around the screws open (damn security hex) was surprised to find that the "monitor" had a usb dongle plugged into it. I plugged it into my station and found it was a 2.4/5 GHZ wifi dongle.
All code here is from Windows power shell since I don't like to dual boot my main gaming rig. Usually I just use the Bash on Ubuntu on Windows developer option for stuff like this, but I didn't know if the fact I was using Windows usb drivers to connect to this would cause problems and I wanted one fewer step to troubleshoot if I had issues. Forgive me penguin for I have sinned.
I found the item number on the back of it and after some googling found it was an android device. Score!
I plugged the tablet in and it went into an Amiibo advertisement kiosk mode.
After about 8 hours I now have a limited (but functional!) giant Android tablet.
To any future adventurers I am making a guide to get you up and running quickly.
I followed selaliadobor's instructions:
To connect to ADB use a USB mini cable on the "USB OTG" port and ClockworkMod's Universal ADB Driver
Click to expand...
Click to collapse
As well as pressing CSR and Setup to get into the settings screen. This was interesting, but ultimately didn't do much. However using
Code:
./adb shell logcat >> log.txt
and waiting for it to reboot from the csr menu led me to find (with some help from my engineer father) that /system/app/CSR_A003_20160304_BT.apk was the culprit of the restarts.
This was solved with
Code:
./adb shell rm /system/app/CSR_A003_20160304_BT.apk
From there I was stuck. But then I discovered: THE CSR SETTINGS MENU IS NOT THE REAL ANDROID SETTINGS MENU. To get to the real android settings menu use this:
Code:
./adb shell am start -a android.settings.SETTINGS
This allows you to do a factory reset!
However when it reboots the default launcher is stripped of important features like back/home/running apps, keyboard, a launcher etc. I sideloaded the following apps:
Chrome Browser
Microsoft Arrow Launcher (I originally used Nova but it was too much a ram hog to be useful)
Multiling Keyboard (I originally used Swiftkey, but it too was taking up too much ram)
WebTube (stripped down youTube frontend)
Soft Keys (so I had a home and back button, the running apps button still doesn't work :'( )
First post so no links ;(
imgur .com/dGAOmoM
This is what it looks like after boot. I may also have an affinity for Amiibos.
imgur .com/uQ8u7js
Classic.
Quick note: This device doesn't support google play services, so no hulu, official youtube, netflix unfortunately. Try as I might I haven't found a solution.
i bought a box of these units a while back from the carboot and wanted to use them in our coffee shop were opening, i too didnt have much luck with them then i saw this thread, i know abit about computers but never messed with android, we basically wanted to use them for what they are used for now for displaying changing menus and advertising etc, i downloaded the clockworkmods adb, now how to enter the "./adb shell logcat >> log.txt" etc, presumably i just connect the otg port to the pc (win10) run the clockworkmod program then i use commandpromt? i did try it but i couldnt get it to work, do i have to put the android device into a mode like csr? any help would be appreciated?
N/A
Additional help needed
i got to the settings menu but it is only temporary i am wanting it to be like a regular tablet where can i get a rom to do that? to flash it so it will function like a galaxy tab 3 or so, as i would love to use my DT101-ASA-800 like a normal tablet with a keyboard and mouse. any help would be welcomed. as the factory reset doesn't let it work any different it keeps going straight to CSR settings.
so stuck... my head hurts
so i can not get my Model DT185-ACA-720 to connect to my pc..... ok it connects and a K: and F: drive appear but I cant access them. I managed to get .apk files to show up and transfer to the 12gb storage on the tablet but i cant access the storage on the tablet... im so lost... I downloaded the universal driver and ADB but both changed nothing... If anyone has any advice or updates im all ears since I basically destroyed the Kiosk to get this tablet free
jaybanc said:
i bought a box of these units a while back from the carboot and wanted to use them in our coffee shop were opening, i too didnt have much luck with them then i saw this thread, i know abit about computers but never messed with android, we basically wanted to use them for what they are used for now for displaying changing menus and advertising etc, i downloaded the clockworkmods adb, now how to enter the "./adb shell logcat >> log.txt" etc, presumably i just connect the otg port to the pc (win10) run the clockworkmod program then i use commandpromt? i did try it but i couldnt get it to work, do i have to put the android device into a mode like csr? any help would be appreciated?
Click to expand...
Click to collapse
Same issue here with the DT133-AC4-900 that I managed to pull out of a trashed google nest display from where I work. I managed to get the device to always load to the DUCO app by uninstalling the mediaplayer throught the DUCO app. However that is as far as I can get as the device will not communicate with ADB at all. Not sure if it's a win10 thing or if it's the device itself.
TheArcticGentoo said:
I DID IT! Working tablet
So the story is yesterday I found an Amiibo display at my apartment dumpster where people put stuff they don't want that still works, I nabbed it with the intention of salvaging the "monitor." Judging by the hammer-marks on the acrylic enclosure, and pry marks on the metal cage that held the power supplies for the led strips and the tablet I assume somebody took it home, got frustrated by the locks and screws after some prying, and just busted in the acrylic window to get to the floor model Amiibos.
I cracked it open, and after some fun with a butane torch to melt the acrylic around the screws open (damn security hex) was surprised to find that the "monitor" had a usb dongle plugged into it. I plugged it into my station and found it was a 2.4/5 GHZ wifi dongle.
All code here is from Windows power shell since I don't like to dual boot my main gaming rig. Usually I just use the Bash on Ubuntu on Windows developer option for stuff like this, but I didn't know if the fact I was using Windows usb drivers to connect to this would cause problems and I wanted one fewer step to troubleshoot if I had issues. Forgive me penguin for I have sinned.
I found the item number on the back of it and after some googling found it was an android device. Score!
I plugged the tablet in and it went into an Amiibo advertisement kiosk mode.
After about 8 hours I now have a limited (but functional!) giant Android tablet.
To any future adventurers I am making a guide to get you up and running quickly.
I followed selaliadobor's instructions:
As well as pressing CSR and Setup to get into the settings screen. This was interesting, but ultimately didn't do much. However using
Code:
./adb shell logcat >> log.txt
and waiting for it to reboot from the csr menu led me to find (with some help from my engineer father) that /system/app/CSR_A003_20160304_BT.apk was the culprit of the restarts.
This was solved with
Code:
./adb shell rm /system/app/CSR_A003_20160304_BT.apk
From there I was stuck. But then I discovered: THE CSR SETTINGS MENU IS NOT THE REAL ANDROID SETTINGS MENU. To get to the real android settings menu use this:
Code:
./adb shell am start -a android.settings.SETTINGS
This allows you to do a factory reset!
However when it reboots the default launcher is stripped of important features like back/home/running apps, keyboard, a launcher etc. I sideloaded the following apps:
Chrome Browser
Microsoft Arrow Launcher (I originally used Nova but it was too much a ram hog to be useful)
Multiling Keyboard (I originally used Swiftkey, but it too was taking up too much ram)
WebTube (stripped down youTube frontend)
Soft Keys (so I had a home and back button, the running apps button still doesn't work :'( )
First post so no links ;(
imgur .com/dGAOmoM
This is what it looks like after boot. I may also have an affinity for Amiibos.
imgur .com/uQ8u7js
Classic.
Quick note: This device doesn't support google play services, so no hulu, official youtube, netflix unfortunately. Try as I might I haven't found a solution.
Click to expand...
Click to collapse
This worked, but I couldn't get ADB to work in Windows, I had to go grab my laptop running Deepin Linux and set up ADB on that, but no USB drivers are needed in Linux, so once I set up ADB, it just worked. So I'm hoping that might be the solution for others who are having trouble, just use Linux, it just works. ADB works on the CSR level, so no need for security key. Got CPU-Z on there for any curious about the hardware specs, my model is a DT101-ASA-800

Kernel watchdog reseting unbranded commercial android tablet/not graceful.

Sorry if this is in the wrong location, if it is please let me know where to move it.
So the story goes I found an Amiibo Kiosk at my apartment dumpster. It was originally designed to run a single app meant to be interacted with by customers and a settings app meant to be accessed by a technician and nothing more. Using adb I managed to get into the /actual/ android settings menu instead of the custom "CSR" one that you can access by pushing some buttons on the back and perform a factory reset. If you need more information I documented everything I did here: https://forum.xda-developers.com/android/help/commercial-grade-android-tablet-issues-t3594279 the post is at the very bottom.
It's a giant 18.5 inch 720p commercial tablet from DUCO meant to be mounted in customer-service kiosks: (product page) http://www.ducotech.com/product/18-5-android-based-720p-hi-def-lcd-media-player/
I sideloaded arrow launcher, aosp keyboard, google chrome, and a stripped-down youtube front-end so it can be used as an actual tablet. Unfortunately Google Play services in not supported on this device (although I could probably spoof it as an officially supported device to make it work, but I want to fix my biggest problem first.)
My problem is that after a pretty consistent amount of time it unceremoniously black-screens with a pop from the speakers, then starts back up. I logcatted it and it shows nothing but wlan polls and ram cleanup before it shuts down, however I'll include it anyway since I'm sure that'll be the first thing anybody asks for.
My best guess is that there is some kernel watchdog resetting it since it's not being tickled by DUCO's CSR app that is normally installed when the system is sitting on a salesfloor.
Is there any way to check for this and/or disable it?
Additional info:
Running Android 4.1.1
Sun4i architecture
I attempted to install Busybox, but the tablet resets itself before Busybox can finish installation.
Logcat is here since the logcat.txt is a few kb too big to upload.
How did you get PowerShell to accept the line code. It errors everytime I type the codes you are recommending

Categories

Resources