Would it be possible to emulate android on an android phone? As in, you could supply an app with an android version (or have the app build it for you) an emulate or run it. Any time it asks for something device specific, it would simply run the request back to the stock OS. Said app would kill all but the essential android processes to improve performance. And to return, it could add a shortcut to the app drawer that would close everything and return to the stock. Using this, could we create universal, or at least wider, distributions of android?
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Darkcon said:
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Click to expand...
Click to collapse
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
The Original Leppa said:
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
Click to expand...
Click to collapse
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Darkcon said:
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Click to expand...
Click to collapse
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
The Original Leppa said:
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
Click to expand...
Click to collapse
Hmm you've got a point there, this could be used to root a phone thats unrootable effectively, like the android emulated inside an Iphone that some people did in the Iphone 4 days
all depends on implimentation, you'd have to set up the emulator to trigger normal events, like power saving cpu states etc in response to the emulated android os's requirements
I've been thinking.
Let's say you decide to emulate AOSP Nougat. You then installed the official Pixel Launcher. While emulating, it would act as it should, as it would be entirely identical to if you were running Nougat.
Then you close the emulation. You then try to open Pixel Launcher; it's already installed. Would it crash?
Ok then...
Would I just look for adb? Or does adb simply ask something else to emulate?
Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
Sorry Guys,
As there doesn't seem to be a whole lot of interest in this project and as no one stepped forward to assist, I'm afraid I'm going to have to abandon this project.
Thanks for following.
___________________________________
OK Guys,
I've run into a bit of a brick wall and need some input from other developers. One of the required APKs from the Q needs a class not included along with my CM9 or Samsung stock roms. The class appears to be called "android.os.UpdateLock". So how do I go about ripping the class out of the Nexus Q rom and injecting it into CM9? Any help would be very appreciated!$!
--------------------------------------------------------------------
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
You can already do that on most android devices. The Q just takes it to the big screen conveniently.
The function of being able to control the Google queue of device A from device B, C, D etc does not exist. Or at least I'm not aware of an app that does that.
I believe that I've tracked down the apk that does it on the nexus but I need to deodex the apps and can't seem to find a tool that works. Anyone out there deodex this rom yet?
JoeJonnyBoy75 said:
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
Click to expand...
Click to collapse
This is a pretty nice project and there is nothing like this happening in Android now, besides the nexus Q. I'd like to see a future port of it to Google TV devices
auad said:
I'd like to see a future port of it to Google TV devices
Click to expand...
Click to collapse
Would love to have this functionality in an APK for me Google TV. Don't see why it wouldn't work, well other then no bluetooth on the Revue....
Still very interested in this thread regardless of GTV. I will be following your progress. Thanks!
.
I'm looking for this as well.
I have 3 spare HTC EVO's, and they all have HDMI out. I would like to be able to just plug them into the TV and use my other phones to control them / play music / etc. Maybe even throw XBMC on them with the ability to control from another phone..
They're slower, and less memory..but it may be doable.
Did anyone dig into this? I'd like this for the latest port of Android for a Raspberry Pi and willing to do some of the (noob)stuff myself.
That would be awesome to use any HDMI equipped phone along with the Nexus Q functionalities. I'm really interested.
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Vettekult said:
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Click to expand...
Click to collapse
Not true, Q runs ICS...
Let me know...
what I can do to help. If you give me a run down on what you would like me to try as far as pulling files from the q or my connected devices just shoot me a PM and i'll give it a shot. I too would love to add this functionality to my spare devices laying around.
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
joeavery2 said:
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
Click to expand...
Click to collapse
Ok so here is some more detailed info for those of you still following the project.
HubBroker.apk is the app that is for all intents and purposes the "launcher" for the nexus Q. It will install on the Galaxy Tab and Nexus 7. It takes over your "home" and replaces it with a picture of the Nexus Q and a welcome sign. This app looks to be only the launcher as it doesn't do anything if you tap on it. Also having the app running doesn't allow the Nexus Q app (from your phone) to find the device.
So I assume that that the Q is controlled via bluetooth to get it setup and running. Including configuring the Wifi, network settings, etc. Oddly enough the app does send a request to android system to turn on the bluetooth and changes the bluetooth device name to Nexus Q.... The ... part is a odd string of characters that I assume is used in case you happen to have multiple Nexus Q's.
Now as just having the app doesn't seem to work (Phone finding the Q). I've replaced all the bluetooth libs with the ones from the Q. Still nothing. I've migrated all the other APK files and then I get FCs all over, and still no connection. I haven't tried replacing the whole system yet, but I assume the hardware differences would be to great. The only other piece of the puzzle I have yet to attempt it merging the kernels or at least the init parts of the kernel relating to bluetooth.
If you have any questions though let me know. I've been up and down this thing.
Why don't we just flash the img on an old phone and see if that works?
zAo_ said:
Why don't we just flash the img on an old phone and see if that works?
Click to expand...
Click to collapse
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Cool, Thanks.
Sent from my Galaxy Nexus using xda premium
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Galaxy nexus has very similar hardware. Someone should try porting it.
Sent from my Nexus 7 using xda premium
If someone still interested in the project, i'm very interested in it, i have a galaxy nexus (almost same hardware) so we can give it a try, im also a android developer, so if it need to build some apk for it to work, i could give a shot.
Anyway, if there is someone interested just post here and we do all we can to make that work.
edit: Only one problem, as I'm out of USA, i need the q apk to test if it will connect or not. I cant download from play store.
I'm sure there will be so many people interested in it. I just think that not to many of them enter this category on forum
I also need the nexus q image so I can flash it. I tried searching it but didnt find
First things first, I'm NOT talking abot canonical's project "Ubuntu for Android"which dual-boots your phone.
I'm talking about this: http://sourceforge.net/projects/linuxonandroid/?source=navbar
Also, this project requires that the device supports a loop device (configured in the kernel). I know that there are some ROMs that support it, but I want a ROM that is really light (so no graphics tweaks or TouchWiz UI) and that I can use to run that.
Also I have a bit experience to build my own ROMs (although I've never shared them), so tips to build one myself are appreciated as well.
I hope that is enough to answer my question,
thanks in advance
shivam89 said:
First things first, I'm NOT talking abot canonical's project "Ubuntu for Android"which dual-boots your phone.
I'm talking about this: http://sourceforge.net/projects/linuxonandroid/?source=navbar
Also, this project requires that the device supports a loop device (configured in the kernel). I know that there are some ROMs that support it, but I want a ROM that is really light (so no graphics tweaks or TouchWiz UI) and that I can use to run that.
Also I have a bit experience to build my own ROMs (although I've never shared them), so tips to build one myself are appreciated as well.
I hope that is enough to answer my question,
thanks in advance
Click to expand...
Click to collapse
Assuming you have a 5.0 player...
That method of running linux on android is known as the "chroot" method which allows you to run linux alongside android, and use vnc to use the gui.
I believe that loop device support has been enabled since the initial development of the 3.0 kernel for the 5.0 and I sure that it's enabled on all the ROMs that I've built. This line in the defconfig confirms it:
https://github.com/Meticulus/nutell...rm/configs/cyanogenmod_venturi_defconfig#L975
I personally have done this before but it was on the stock ROM (long time ago). It should work on any ROM. There are even apps in the play store that will help automate the process for you...
https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid
For me, it was novel. I had alot of fun doing it but it wasn't practical to use as a daily driver. Keyboard usage in vnc apps is a bit of a pain and because of the small screen, it was difficult to use the mouse to hit buttons. Minimize, maximize and close; on windows was especially difficult to use..
Anyways... Good luck...
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!
Hi. I'm wondering which brands make a product like this but also though, the user should be able to install and run android apps if wanted/needed.
Is
Also, if you know if an older one that you can do this on, still let me know
LimeRibbon said:
Hi. I'm wondering which brands make a product like this but also though, the user should be able to install and run android apps if wanted/needed.
Is
Also, if you know if an older one that you can do this on, still let me know
Click to expand...
Click to collapse
Buy an old android tablet and use the kindle app.
Pretty much all tablets can do this