Related
Hi all,
I've learned that the StarTrek is able to boot the current kernel from the Linwizard project without any modifications. I've posted a video of this at http://vimeo.com/2114567. Before you get too excited, however, there's a few things to keep in mind:
The buttons aren't mapped correctly by default.
You need a networked computer to log in and do anything fun, for now.
If you're wondering about Android, the answer is "not yet".
I will do my best to address the important things here; what works, what needs tweaks to work, and (most of all) what needs attention. I will also, over the next day or two, try to post my findings regarding the button GPIOs collected from HaRET, kernel modifications necessary to fix a few things. etc.
Consider this post a call for help. I'm hoping this will encourage others to contribute toward more complete linux support on the phone. I personally am driven by the opportunity to dual-boot Android on the device, but I have much to learn and can't do this alone. So, if you have kernel experience and a StarTrek, here's your motivation to get hacking! (If you'd like to help, but don't have a device to test kernels on, I'm often in #xda-devs.)
Status (Let me know if there's anything missing here.)
Internal LCD - YES - Seems to work great.
External LCD - ? - Shows the device's default image. Not sure how to control this in linux.
Backlight - ? - Unsure. As far as I can tell, Linux will retain the brightness level being used when HaRET finished loading the kernel.
USB Networking - YES - Works like a charm.
Audio - ? - No idea. I don't know how to test this.
Cellular - ? - No idea, but I don't think it will necessarily come easily.
Buttons/Keypad - SOME - By default, the keys and buttons are mapped either incorrectly or not at all. The phone keypad and some of the special buttons type random keystrokes, since we are using the mappings for the Wizard. I have a modified board-htcwizard.c with correct mappings for the StarTrek I'll post really soon, as well as a list of the GPIO readings for many of the buttons. Unfortunately, the Up/Down/Left/Right/Select/End buttons function differently than the other, matrix-based keys. I have yet to discover how to configure them.
Camera - ? - No idea, but they don't even have this working on the Wizard (Linwizard's primary target device).
Light Sensor - ? - I wouldn't know where to begin. It barely works in WM, anyway.
MicroSD - YES - I can mount the MicroSD with no issues, full read/write. Even managed to open my photos in the GPE photo gallery on the device (launched over telnet).
X[\B] - YES - I am able to start X, by calling startx over the telnet connection. However, X will try to run a touch screen calibration before doing anything else, and this is a bit of a problem for us! Fortunately, on newer Linwizard versions, you can disable this by passing tslib=0 to the kernel (in the defaults.txt file you give to HaRET). GPE also seems to be running perfectly after X starts.
Problems - After a few idle minutes in linux, the screen likes to black itself out automatically, as per the design of Linwizard. Unfortunately, on the Star Trek, there seems to be no way to make the screen wake up. Telnet still works in this situation.
I promise to keep this post updated, and get my data together and uploaded soon. Please share your own results and tricks as they come along, and join me (and some talented people) in #xda-xevs and #htc-linux on irc.freenode.net. Happy hacking!
Attached:
arch/arm/mach-omap1/board-htcwizard.c - Contains key matrix mappings modified for StarTrek. Be sure to remove the ".txt" from the file extension before using.
default.txt - Used with HaRET to make Linux boot. The only thing unusual in here is the TSLIB=0 option that's passed to the kernel, telling linux to skip touchscreen-related tasks.
great work! but you need some advanced startrek owners to test linux - that's a big problem
Fantastic news! I' would really try it out. Unfortunatly my startrek's connector is damaged. I can charge the device, but I cannot connect with the pc. If I can use the micro sd card to install it(I think is possible) I will try it.
Thanks for the great job.
dancer_69 said:
Fantastic news! I' would really try it out. Unfortunatly my startrek's connector is damaged. I can charge the device, but I cannot connect with the pc. If I can use the micro sd card to install it(I think is possible) I will try it.
Thanks for the great job.
Click to expand...
Click to collapse
You can, by dropping Haret+default.txt+zImage+initrd onto the SD card. Unfortunately, without a USB connection, you won't be able to telnet into the device and run commands.
very interesting! Ive been waiting to hear this kind of news Unfortunately, I still use my StarTrek as my primary phone, so I can't test it out until it moves along a little further. I'll be sure to keep an eye on this thread, as this is good news!
gigawatts said:
very interesting! Ive been waiting to hear this kind of news Unfortunately, I still use my StarTrek as my primary phone, so I can't test it out until it moves along a little further. I'll be sure to keep an eye on this thread, as this is good news!
Click to expand...
Click to collapse
Linux actually boots directly from a Windows Mobile program called HaRET; When you're done playing with Linux, you can just reset the phone and you're back to normal. No permanent changes.
awesome! I'll give it a go right now, thanks!
BHSPitMonkey said:
You can, by dropping Haret+default.txt+zImage+initrd onto the SD card. Unfortunately, without a USB connection, you won't be able to telnet into the device and run commands.
Click to expand...
Click to collapse
I already did it, and works. Thanks anyway.
Why not combine the effort to get Android on it?
Kwen said:
Why not combine the effort to get Android on it?
Click to expand...
Click to collapse
Are you volunteering your expertise on the subject?
The point of this post was to accomplish just that: to attract the interest of more people who can contribute. I'm in the process of setting up a repository of changes right now, so the patches I've made so far are kind of scattered about my hard drive for the moment. If you're interested, you can try catch me in #htc-linux or #xda-devs on irc.freenode.com. Otherwise, I'm trying to keep the post at the top of this thread up-to-date.
Unfortunatly Android cant work, it needs 128 ram.
http://source.android.com/release-features
BHSPitMonkey said:
Cellular - ? - No idea, but I don't think it will necessarily come easily.
Click to expand...
Click to collapse
from linwizard wiki page :
What we need
Right now we need people with experience with GSM and WiFI to help get linwizard connectivity up!
Click to expand...
Click to collapse
about two years ago , another linux project ran that called Xanadux. why you don't use from Xanadux ?
sorry for my english !
I have linux booting
it up booting to the point correctly then sit conclusion cannot one yet start?
sorry for my bad english my german are better
Oh.......I think HTC Phone can do that ADIDAS ' AD "impossible is nothing"
Been a few months since ive been on the scene, any news here? My Cingular 3125 is nearing the end of its life, and I figured I can play a bit more with it
P.S. Whats new BHSP?
autologin on linwizard
hi
http://wlcrck.wl.funpic.org/wlcrck-elf-linux/autologin
to solve the problem i develop a simple aplication to automatic login but dont have any security autologin in root mode
to use this have to make a couple of things
you need decompress the inirtd and add this app to /bin and set suid and modify
/etc/inittab file and compress the initrd again.
change this line
tty1::respawn:/sbin/getty 38400 tty1
for
tty1::respawn:/sbin/getty -l /bin/autlogin 38400 tty1
sorry for my english
thanks for the code of htc board
Hi Developers
I thought I would share an idea I had with the developers on this forum in regards to the issue with the x10 camera not functioning on 2.2 or 2.3 roms. I am an experienced developer, but honestly am not very familiar with the android platform to be able to attempt this idea. Don't shoot me down, this is just an idea but it may be worth investigating.
I understand that there are issues in porting items such as the camera over from a 2.1 rom over to 2.2 or 2.3 due to the change in the android camera api. Instead of rewriting drivers, etc, it may worth investigating or attempting the method I am about to mention.
I have noticed that there have been alot of emulators written to play games on the android, which emulate neogeo, psx, etc. Why dont we emulate aspects of the 2.1 run which can be run in 2.2 or 2.3?
For example, create an app which will emulate the camera from 2.1 rom by emulating the camera api's from 2.1. When you load up your phone and run the 'camera' app, it would actually emulate the camera app from 2.1 within the 2.2/2.3 rom by using the required 2.1 camera api's? I believe this would be the best way of resolving the issue. Plus, this app which emulates the camera from 2.1 would actually just be an app which can be easily installed to work on 2.2, 2.3, or any other future rom releases....
Developers, let me know what your thoughts are on this. If this works, we may be able to always use native features from the x10 already written and developed for the 2.1 rom.
neomira
Thats a very good idea mate,make an 2.1 emulator for 2.3 and up. But mate thats not the problem,its not the camera app itself thats not working,its the inside libs(drivers so to say) that were written in 2.1 (Lets say Windows 98) language and now to switch them to 2.2/2.3 (Windows 7 so to say) is a problem cause those libs(drivers) arent compatible in the operating system,as Android changed ALOT from 2.1 to 2.2 and specially 2.3. You see,Z got the camera ongoing but with software decoding not hardware decoding,thats why you can make a photo but not a video,making a video is too much job for Software emulation (Try it with illusion pro,you'll result in a laggy 15fps 640x480 vid). What they are trying atm is to rewrite the camera driver in a way that it could cope with the hardware decoder . Cause the election is eigher camcorder or video-watching,and 90% want Video decoding rather than the Camcorder.
The camera itself is recognized and stuff but because the camera driver is very old already,it wont work on the new OS's.
Emulation is a good idea but still wont work alright afaik,its like trying to emulate a old windows 95 printer to your windows 7,yes you can emulate windows 95 but you wont be able to use the printer cause windows 7 doesnt know what it is or what to do with it,because the OS that handles the Hardware is the base one,not the emulated one.PSX and so on emulates the remote control cause Android base system knows the hardware that the software translates and makes you be able to use it and can interact with it (touch screen),but that happens because the base OS has and recognizes it,imagine if the base OS wouldn't know the touch screen.Having the buttons displayed on your display would be pointless cause you cant use them as they dont even exist for the base OS which is the important one.
EDIT : Thats why its called Emulation,cause it just Emulates the hardware,doesnt actually use it,has it or recognizes it ,its all software that translates from a unknown hardware to known software for the Base OS,but in our case if the base OS doesnt know the camera,its pointless that the Emulated OS does cause an emulation first needs an input to work,if that input isnt there it just wont work.
EDIT 2 : So its not the camera app,its the camera driver(libs),and there is no way you can use windows 95 drivers on windows 7 unless you rewrite them. (Heck,i remember i couldnt even use W95 drivers on WMillenium,and they had the same base kernel 9x so imagine).
But thats my thought,maybe there is something else i dont know and it could work.
Respect
xtrmshadow said:
Thats a very good idea mate,make an 2.1 emulator for 2.3 and up. But mate thats not the problem,its not the camera app itself thats not working,its the inside libs(drivers so to say) that were written in 2.1 (Lets say Windows 98) language and now to switch them to 2.2/2.3 (Windows 7 so to say) is a problem cause those libs(drivers) arent compatible in the operating system,as Android changed ALOT from 2.1 to 2.2 and specially 2.3. You see,Z got the camera ongoing but with software decoding not hardware decoding,thats why you can make a photo but not a video,making a video is too much job for Software emulation (Try it with illusion pro,you'll result in a laggy 15fps 640x480 vid). What they are trying atm is to rewrite the camera driver in a way that it could cope with the hardware decoder . Cause the election is eigher camcorder or video-watching,and 90% want Video decoding rather than the Camcorder.
The camera itself is recognized and stuff but because the camera driver is very old already,it wont work on the new OS's.
Emulation is a good idea but still wont work alright afaik,its like trying to emulate a old windows 95 printer to your windows 7,yes you can emulate windows 95 but you wont be able to use the printer cause windows 7 doesnt know what it is or what to do with it,because the OS that handles the Hardware is the base one,not the emulated one.PSX and so on emulates the remote control cause Android base system knows the hardware and can interact with it (touch screen).
But thats my thought,maybe there is something else i dont know and it could work.
Respect
Click to expand...
Click to collapse
Thanx for your feedback. I think you may have misunderstood me though. I understand that the drivers, classes, etc have changed since 2.1. My idea is to emulate the old kernel , api's and camera app from 2.1 onto 2.2 or 2.3. Basically writing an x10 2.1 rom emulator, which will only emulate 2.1 camera. It wouldnt emulate the entire 2.1 system.
Think of a neogeo emulator...you load in the neogeo bios and you load in the game rom. Hey presto, u have a neogeo on your mobile...well not really...just emulated..
In the idea i have of emulating the camera from 2.1:
Your bios rom = 2.1 kernel, camera api and x10 camera driver..
Your game rom = camera app from 2.1.....
However, when u would run the app everything would be built into it and u wouldnt have to specify anything. It would load up looking just like the camera app....
Kinda like Wine on linux but only intended for the camera....to save on resources.
Just an idea....
I dont know what would be easier or quicker - to emulate the camera from 2.1 or to rewrite the drive on 2.2/2.3....however, you may need to rewrite it 2.4, 2.5, etc....as api's are always changing. An emulated camera wouldnt need to be rewritten with each new android release. We will always have to wait for someone to rewrite drivers if not emulated.
What do you think? Just an idea....
Sent from my X10i using XDA App
I Understand your idea mate,and im not saying its impossible, it might aswell be very possible and really apreciate your intention ,who knows ^^
But it doesnt sound like it would work for me,cause if its a hardware the base OS doesnt recognize,i doubt the emulated camera would work,cause when the emulation requests to contact the hardware to the base OS,it would just recieve a "unknown/incorrect request".Cause remember,emulations cannot direct-access the hardware,it first has to pass through the base OS.And thats why to emulate a machine as simple as the 33MHz PS1/PSX , you need at least 500MHz CPU to even try to run it,cause it cannot go to the CPU and simply do the chores.
Thats my point of view tho.
Respect
Ah now that you mentioned Wine on Linux.
What happens when you try to play a 3D accelerated game on Wine that tries to access the Graphics Card and you havent installed the graphics card drivers on Linux?It would just fail cause the base OS , Linux doesnt understand what the Emulator is telling it.
EDIT: Also dont know if you know Compiz-fusion for linux (or Beryl),its a Window Manager that gives you alot of effects and stuff on windows and many things(search beryl on youtube) but if you dont have a graphics driver installed ,it would just say "Hardware Graphics Card not detected,it cannot continue" so obviously you cant use VMWare to create a virtual machine and emulate the drivers on that VM cause for it,it wouldnt even exist as "Unknown" ,it wouldnt even exist at all.
Hope that helps you understand it more.
Respect
xtrmshadow said:
Ah now that you mentioned Wine on Linux.
What happens when you try to play a 3D accelerated game on Wine that tries to access the Graphics Card and you havent installed the graphics card drivers on Linux?It would just fail cause the base OS , Linux doesnt understand what the Emulator is telling it.
Hope that helps you understand it more.
Respect
Click to expand...
Click to collapse
hmmm you may be right. what about virtual pc though? that is probably a better example. you can actually use hardware....for example, i could get a soundcard working properly on windows xp so i installed windows 98 via virtual pc....bingo, it worked....i could keep making music without buying another $1800 soundcard for ages.
therefore, have an app called "x10cam" which is emulates the 2.1 rom just like virtual pc....when you click on it, it would load emulate 2.1, but a completely cut down version with no apps, just the camera app and maybe even go straight into the camera app. on exit of the camera app, it quits the emulation and goes back to your 2.2/2.3 rom or home screen.
i dont know....sounds like it may work but might take some time...however, it may benefit in the long run though as the cam driver wont have to be rewritten each time of a new android release.
thanks for your replies too. i do appreciate it. someone may read this posts and come up with an alternate idea which would work
xtrmshadow said:
EDIT: Also dont know if you know Compiz-fusion for linux (or Beryl),its a Window Manager that gives you alot of effects and stuff on windows and many things(search beryl on youtube) but if you dont have a graphics driver installed ,it would just say "Hardware Graphics Card not detected,it cannot continue" so obviously you cant use VMWare to create a virtual machine and emulate the drivers on that VM cause for it,it wouldnt even exist as "Unknown" ,it wouldnt even exist at all.
Hope that helps you understand it more.
Respect
Click to expand...
Click to collapse
Thanks for mentioning Beryl, i actually wasnt aware of Beryl until you mentioned it. Much appreciated.
neomira said:
hmmm you may be right. what about virtual pc though? that is probably a better example. you can actually use hardware....for example, i could get a soundcard working properly on windows xp so i installed windows 98 via virtual pc....bingo, it worked....i could keep making music without buying another $1800 soundcard for ages.
therefore, have an app called "x10cam" which is emulates the 2.1 rom just like virtual pc....when you click on it, it would load emulate 2.1, but a completely cut down version with no apps, just the camera app and maybe even go straight into the camera app. on exit of the camera app, it quits the emulation and goes back to your 2.2/2.3 rom or home screen.
i dont know....sounds like it may work but might take some time...however, it may benefit in the long run though as the cam driver wont have to be rewritten each time of a new android release.
thanks for your replies too. i do appreciate it. someone may read this posts and come up with an alternate idea which would work
Click to expand...
Click to collapse
Well,creating a VM (Virtual Machine = Virtual PC) might be able to make it work if the developer of the base ROM can at least make the OS Recognize the camera and access it (eventhought no image cause of the 2.1+ incompability),yes that might be possible . But still gotta write at least some basic drivers for the Cam.Lets say for exemple Z's 2.2 might perfectly be able to do what you've said cause the OS has 100% access to the camera,but cannot camcord cause of the base OS but the emulated one might aswell.
Yes that is a good idea as long as at least basic drivers are written.
And about you beeing able to Virtual PC that sound card,means that the base OS could already access it but it just didnt know how (Its like when you go on "Device Manager" and you see your device in "other" and it says the name it just cannot correctly interact with it cause of limitations)
Eventhought a Virtual Machine on our 280Mb of RAM wouldnt go too smooth but yes its a very good possibility.
Respect mate
sounds like a good idea and it will work in HD with the nice SE user interface .... it may take a long time to boot into camera app.... but still better than switching between roms for camera....
xtrmshadow said:
Well,creating a VM (Virtual Machine = Virtual PC) might be able to make it work if the developer of the base ROM can at least make the OS Recognize the camera and access it (eventhought no image cause of the 2.1+ incompability),yes that might be possible . But still gotta write at least some basic drivers for the Cam.Lets say for exemple Z's 2.2 might perfectly be able to do what you've said cause the OS has 100% access to the camera,but cannot camcord cause of the base OS but the emulated one might aswell.
Yes that is a good idea as long as at least basic drivers are written.
And about you beeing able to Virtual PC that sound card,means that the base OS could already access it but it just didnt know how (Its like when you go on "Device Manager" and you see your device in "other" and it says the name it just cannot correctly interact with it cause of limitations)
Eventhought a Virtual Machine on our 280Mb of RAM wouldnt go too smooth but yes its a very good possibility.
Respect mate
Click to expand...
Click to collapse
Yes, you are right. The only issue I can see is that a VM for just the camera functions would have to be a VERY VERY cut down version of 2.1 due to the 280mb of RAM. Otherwise it would be so slow.
Thanks xtrmshadow for the positive feedback. Maybe somebody might use this thread as an idea for something.
hemo1001 said:
sounds like a good idea and it will work in HD with the nice SE user interface .... it may take a long time to boot into camera app.... but still better than switching between roms for camera....
Click to expand...
Click to collapse
thanks hemo1001. much appreciated feedback.
that is my thought exactly, to prevent having to switch roms entirely just for the cam. also, if you think about a completely cutdown VM of 2.1 to access the cam, i dont think it would be cut down to only run what is necessary for the camera to function. I think it would be a better alternative than switching roms.
neomira said:
Yes, you are right. The only issue I can see is that a VM for just the camera functions would have to be a VERY VERY cut down version of 2.1 due to the 280mb of RAM. Otherwise it would be so slow.
Thanks xtrmshadow for the positive feedback. Maybe somebody might use this thread as an idea for something.
Click to expand...
Click to collapse
Agreed ^^ , Making a VM program for Android would be fairly easy as there are loads for Linux (VMWare,VirtualBox + more) and a very core version of 2.1 with only the necesary things for the task(No launcher,drivers for anything but camera,no apps etc).
Also i agree hemo1001 ,well said mate haha.
Hopefully someone that is very experienced with Android (Im only experienced on C++ and Hardware ><) takes a look into this and thinks about it ^^
Respect.
xtrmshadow said:
Agreed ^^ , Making a VM program for Android would be fairly easy as there are loads for Linux (VMWare,VirtualBox + more) and a very core version of 2.1 with only the necesary things for the task(No launcher,drivers for anything but camera,no apps etc).
Also i agree hemo1001 ,well said mate haha.
Hopefully someone that is very experienced with Android (Im only experienced on C++ and Hardware ><) takes a look into this and thinks about it ^^
Respect.
Click to expand...
Click to collapse
I hope so too mate. It would be great.
Sent from my X10i using XDA App
the client on a vm depends on the hardware and drivers from the host. you can't emulate hardware on a client that doesn't work on a host.
At least we can emulate it in 2.2 freex10
Sent from my X10i using XDA App
Using New Drivers
The cameras for the new sony models are different. But maybe there is a chance that
we can modify their libraries and use them on our phones.
I am not familiar with the camera libraries so I don't know how hard it is to modify the new libs in the xperia arc to match our hardware but it should be possible right?
i have read the complete discussion..phew...amazing amazing u guyz are u ll gave me a triggering pulse which straight away took me o my Embedded System Lectures from College..!!! Jokes apart i think the logic of Emulator is a better option as of now..atleast get a working camera..lets hope..all our experts are actually working hard hope for teh break through very soon..m not good with programming and stuff..so unfortunately i cannot even think but the whole logic behind Emulators was actually cleared after 2 yrs since i finished my Engineering in IT..lol..great stuff guyz..Proud to be on XDA since 5 yrs now sorry for going off topic..
camera - email.apk
hello,
i think since two month ago, if i write this or not ...
now, it's looking good for this information, but i dont know,
if this could help the camera-problem.
i'm working as an admin in a firma with some developers.
during android V1.6 - V2.1 we could sync exchange-server with no "device-limitation" by given all 5 minutes a device-code in.
since android V2.2 the email.apk changed very hard ... now we have to give all 5 minutes a device-code in. but the devices are not devices from the firma, so we dont sync anymore. but the info-lost is sometimes very critical.
one of our developers making an email.apk or find an email.apk with no exchange-securitas. the result was that barcodescanner and all other aps with camera inside dosnt work. although the camera.apk
now there is an email.apk outside with NO-EXCHANGE-Securitas and NO-Camera-PROBLEM.
i am glad to use the email.apk since 2 ore 3 weeks without any problems and securitas.
i dont belive that is only a driver/lib-problem because i used a htc leo and have the probs (and solution) that i above describes.
what i mean is, that could not only a driver-problem ... that could be a securitas-problem like ... "if you manipulate email than your cam doesnt work!"
i hope this is not for 1000% to trash and my bad english will automaticly changed to good-english by a developer with bad-english too (bad + bad = good
okokur
okokur, i didn't understand a thing you wrote but it was a very interesting read! i hope someone woth more knowledge picks it up.
this is a great thread guys, love your outside of the box thinking, brilliant!
sorry for going OT, best of luck, peace
Cool! The app works on Froyo & Gingerbread.. problem is in the drivers for the camera and kernel, which are being prioritized in jerpelea's gb build..
Imagine if something similar to virtualization took place at boot time?
So, basically, I got the smart dock and, it's pretty damn awesome. But OMFGTHATFREAKINGMOUSECURSORTHATWON'TGOAWAY.
Anyway, I did some searching and found that there's no way to get it to disappear under stock. Grr. But some custom ROMs allow it. Unfortuantely, none of them seem to say whether they do or not, so I need your advice! BUT! There's other things I need too, which are even more important than being able to make the cursor disappear. So... I need:
1) NTFS support, read AND write. If the ROM isn't Android 4.2+, Paragon NTFS & exFAT can take care of that. So; I need a ROM that's either 4.1 based or has built-in NTFS support. (I don't need exFAT.)
2) Works with the smart dock. The one that has the audio out, HDMI, and 3 USB ports, and isn't officially compatible with the S3 but works anyway.
3) Can make the freaking mouse cursor disappear. Even better if this can be set on an app-by-app basis or toggled with a key shortcut on an external keyboard.
4) Decent battery life. Doesn't need to be better than stock, just not one of those ROMs that runs the thing flat in half an hour.
5) Being based on Samsung's rather than AOSP would be a bonus, but I'm not *overly* fussed on this.
(I heard some custom ROMs result in the FM Radio not working. I really couldn't care less about this, I never use it, so it's fine if that doesn't work.)
I don't need to be walked through how to install it etc, I've done all that several times before. Just need a reccomendation on which one to use, to save me trying every one of the millions out there. Even if you can only confirm some of those features and aren't sure about others, that'll at least narrow down the selection to try. Thanks in advance guys. =)
Recommend a ROM threads aren't allowed. You have to read the features in the rom thread.
That said:
1) This is KERNEL related
2) Only Touchwiz support video out
3) The mouse cursor you turn on in developer options? Or you mean when you're using the mouse? Can't imagine using a mouse without a cursor
4) Again, mainly kernel related. But since you narrowed it down to only touchwiz roms in point 2, it's not really relevant anymore.
5) Not really got a choice.
^^^^This^^^^
Thread Closed
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?
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
Most Promising Leads for Installing Android (1/12/17)
I have tried to install Bliss OS, but with not much luck. Once you get passed the GRUB screen it says there was an emergency error of some kind and reboots the device.
https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657
I found that his updated installer (v25.0004) doesn't work at all, but the latest version from the original developer worked fine, linked below:
https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483
I followed the following methods, all which resulted in a failed attempt, but the one with the most success was the first one:
- Easy install for Bliss-x86 UEFI/ESP
- For Bliss-x86 USB based installs
- Custom install for Bliss-x86 UEFI/ESP
My next attempt will be with Phoenix OS.
OLD INFO (as of 1/12/17)
Edit: I managed to replicate my situation twice. So I now have a method. Will post more info soon.
Okay... so if you want to get into Remix OS (knowing it's only temporary), here's how to replicate what I did. But make sure you have the following tools:
- USB keyboard & microUSB to USB adaptor (for the keyboard)
- Remix OS (I'm using the 64-bit version)
- A bit of time
What I did:
- Install Remix OS (doesn't matter what size you choose; 8, 16 or 32) on your C: Drive (main Local Disk) with the bundled installer
- Reboot when it finishes (via the dialog box, don't reboot any other way... it won't work properly)
- Give it about 10-15 minutes on the first boot. It'll be "stuck" at this Android-looking thing (mine's all glitched up and stuff)
- When it's done it'll show a black screen, and the Pencil icon to switch the Halo Keyboard on/off will stop turning on&off, it'll instead just stay on 100% of the time
- Reboot again, again choosing to boot into Remix OS
- As soon as you choose Remix OS, you NEED to hold the escape (ESC) key!!! If you don't do this, you'll have to start from scratch
- If you did it right, it'll come up with a couple lines of code, and then after a couple second it'll say "ANDROID" underneath the code, and everything will load up
- Everything should be in portrait-mode, but you should have no graphical glitches now, and should see the setup screen
- The touch-screen still shouldn't work here, you need to use the keyboard to navigate through the setup. If the Wi-Fi bit isn't connecting properly, do that later (just skip that step, up the top right). I left Google Play Services enabled, it doesn't matter, it won't ask for your information unless you open a Google App.
- When you finish the installation, everything should work (except the Halo Keyboard of course)
- To make Remix OS take up the whole screen instead of just the middle... go to the Settings App -> Remix OS Settings (whatever the top one is) -> Always show landscape thingo, toggling this off will make it use the whole screen instead of that little square in the middle.
This is far as I've gotten. I've tried getting USB Debugging to work, but it doesn't want to work. Bluetooth doesn't work for me, nor does changing the brightness. I wouldn't lock the tablet either, sometimes that doesn't work. Also don't try use the Google Play Store, because when you finish entering your information, it'll likely crash and you'll have to start over again. Rebooting will reset everything.
OLD INFO (as of 30/03/17)
I've had some random luck (as told in my recent post, I'll quote it here) with Remix OS.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
Click to expand...
Click to collapse
Somehow I managed to get it working, but only temporarily.
If I'm able to replicate this situation again, I may be able to install the Stock ROM alongside Windows 10. However, I don't have all the time in the world, so this may take a long while.
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 (ie. 64-bit)
----+ 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
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
- Windows 10 with AMIDuOS on-top (honestly wasn't that great)
Currently testing:
- Windows 10 with BlueStacks on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting BlueStacks on-top of Windows 10, which is a player that allows you to run Android apps. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
Ehh... BlueStacks isn't that great after all. Personally I'd stick with Windows apps if you need something like that.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
AmiDuOS works for me but the keyboard language cannot be changed somehow.
nan0s7 said:
Hello, everyone!
So as we all know, any developments to do with the Yoga Book seem to be very slow.
Considering a decent number of us have experimented with the Yoga Book, I thought it'd be a good idea to make a centralised place for methods that have worked for people, so we can all have a go and hopefully obtain similar results.
So the idea would hopefully end up being something along the lines of my Megathread (which is now in General).
I guess this is where I get the ball rolling...
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)
Any information I put about my experience will be with the YB1-X91F version (aka Windows 10 Wi-Fi)
Dual OS or Switching the pre-installed one:
I have attempted getting Android on my Yoga Book, and completely deleting everything Windows. This has obviously not gone very well for me.
Version's I've tried:
- Android x86 6.0-r1
- Android x86_64 6.0-r1
- Android x86 6.0 20160129
- Android Nougat x86 20160902
- Android 4.2.2-r1 "ia3-core mesa-userdebug"
- Remix OS (32 & 64-bit)
The one I personally have had the most success with (by that I mean I've gotten it to display the Android set-up screen with no touch-input) is the 32-bit version of 6.0-r1 (so the first one on my list above).
Other OS's that I've tried/succeeded in running:
- GParted Live 0.28.1-2 i686 (although, the whole screen is in portrait mode)
- Ubuntu 16.10 Desktop (amd64 - so it obviously didn't work)
Currently testing:
- Windows 10 with AMIDuOS on-top
TLDR:
If you're on the Windows 10 version of the Yoga Book, I cannot recommend attempting to install Android on it (even with a dual-boot) at this current time. This will probably change if x86 Android update their ROM/Image, though.
I'm currently testing the practicality of putting AMIDuOS on-top of Windows 10, which will be like having an app that just runs Android. The only thing I'm keeping an eye on is battery life (since it'll be doing background tasks for Windows AND Android). However, you will at least have full functionality - especially with the Halo Keyboard.
I will add more info and links later on, I just wanted to get this out before hitting the hay. Australia's time difference sucks.
Click to expand...
Click to collapse
deepsync said:
AmiDuOS works for me but the keyboard language cannot be changed somehow.
Click to expand...
Click to collapse
Have you tried different keyboard apps?
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
deepsync said:
Well on screen keyboard works fine. I just can't change the key mappings of the Halo keyboard to my German keyboard. English may work as that seems to be the default.
Click to expand...
Click to collapse
Hmm you're right. I've tried switching to a Polish keyboard in AMIDuOS, and it doesn't work at all. Although I didn't try switching the keyboard language in Windows, and then using AMIDuOS. I'm kind of optimistic that that method may work, so possibly give that a try if you haven't yet?
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
sawyerbenjamin said:
Are you gonna try again if you can get your hands on Lenovo's stock Yoga Book ROM?
Click to expand...
Click to collapse
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
I had a minor breakthrough last night. I don't know how I managed it though.
So Remix OS has an installer application you can run from within Windows. I used that, then rebooted into Remix OS. The first boot was met with just lots of graphical errors, but when I rebooted again into Remix OS, it booted perfectly. Android was running smoothly, everything worked (the touch screen, Wi-Fi, etc. - but not the Halo Keyboard). However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
I'll continue to mess with it, but if anyone has Windows and wants to attempt getting Android on it, this may be a viable method they can try. But of course, it's not perfect so don't do anything you don't know how to do just yet.
nan0s7 said:
However, when I rebooted again, it stopped working. I was not able to successfully replicate that again - even with many re-installations of Remix OS.
Click to expand...
Click to collapse
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
jamespmi said:
Why so much headache? If you are having the Windows Version how often do you really miss Android? What Apps are not present under Windows? I am absolutely not a gamer, that's probably why I don't really have the need for Android... Anyhow, why installing Remix OS and risking to mess up with the Bootloader? I tried NOX Player and KO Player. The last one works very smooth on an Atom Processor. KO Player even let you go Fullscreen. Everything works out off the box as it's just a layer, Halo Keyboard, Pen, just all works and pretty decent. Many low equipped Android Tablets perform slower...
Click to expand...
Click to collapse
I've got Windows machines all around me. Which is... tolerable. But it's more that I just enjoy having Android on my device, and I do really enjoy messing with tech. I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
nan0s7 said:
I've gotten so close to getting Android on my tablet, it's just a project to really satisfy my time with. Plus, with Android I have more control over everything
Click to expand...
Click to collapse
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
jamespmi said:
As a techie achievement I totally understand. But I doubt you will get all the drivers working properly. Halo Keyboard, Wacom & AnyPen for example. But good luck... On the other hand I have to insist: Windows gives you more control over everything... lol...
Click to expand...
Click to collapse
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
nan0s7 said:
Once I get some sort of Android on it, that will allow me to flash a ROM that has all the drivers in it. And it depends what you define control as...
Click to expand...
Click to collapse
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Melliejoy said:
Hey dude,
It looks like this thread hasn't had a great deal of attention lately, which is kinda sad. I figured it would be a really tricky endeavour anyway.
Anywho, just letting you know that if you do ever figure this out, there's one chick in Australia whom will owe you her eternal thanks.
Seriously, I tried to Remix, I tried to x86, but all it got me was a trip to Harvey Norman and a 2-5 week waiting period to get my book back. If you get a flashable Android ROM for this thing you will be my favourite person in the whole world ever. :laugh:
Click to expand...
Click to collapse
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
nan0s7 said:
Haha damn sounds like a.... fun time
But yeah, there hasn't been much progress. I mean you could always run an emulator on-top of Windows if you NEED an Android tablet.
Click to expand...
Click to collapse
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Melliejoy said:
I didn't NEED Android until I discovered Freeview FV, so I could watch Highway Patrol without taking the TV from my hubby. Between that and the few apps I use for D&D, I'm sort of regretting going with the Windows version.
I can't really do anything until I get it back, anyway. The furthest I got was successfully installing Remix, but it wouldn't accept any external input when trying to select it from the boot menu. I guess I could use an emu, but it's not as good as the real thing.
Click to expand...
Click to collapse
Yeah I wish I had gotten the Android version, but I got mine for a reduced price... so I can't complain too much ;P
Yeah... none of the emus are perfect anyway. I'm hoping that a new version of x86 Android or Remix OS will allow me to get ADB to work, so I can then flash Android. But I'm not holding my breath for that.
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
sawyerbenjamin said:
Any recent experimenting with Remix? Im about to download it and see what I can gather. Too bad there's about zero android devs on this thing. Im sure a custom Kernel under RemixOS would be fix most of its problems.
Click to expand...
Click to collapse
Nah I haven't done anything recently. But if you're having trouble getting things booted use my method (assuming it still works now) and I guess see what you can do
nan0s7 said:
I do actually have a copy of the stock ROM, but not in a format I can put on the Yoga Book without the Android bootloader installed. The versions of Android I tested were ones that include the files for the bootloader and such, but they didn't want to work properly.
If something new comes up, or I get another idea, I will for sure try again. I prefer to use Android over Windows, any day.
Click to expand...
Click to collapse
Is your stock ROM for YB1-X90F or YB1-X90L?
ljbha007 said:
Is your stock ROM for YB1-X90F or YB1-X90L?
Click to expand...
Click to collapse
I have both. Got them from easy-firmware (had to pay for the X90F version).
They're not "ROMS" so much as they are just a way to replace Android with this particular version. So it comes with all the .img files for each partition you'd normally see (system, boot, etc.) and some scripts to use with the Intel flasher program thingo.