Related
hello,
their seems to be a few posts on this being ported to BA recently. ow ive got linux running on my BA fairly well (havent got round to setting up gprs etc yet though but thats a different matter) and id be willing to try and get a port of android working, if someone can extract the 3 img files in the android sdk as ive not managed to do that yet ? anyone want to try and help or am i talking of a lost cause
ok, ill post this incase anyone is watching. i made some progress getting andriod running but i keep getting seg fault tryingto run it, any1 who could provide insight let me know pelase
Unfortunately I can't help you but I'll be keeping a VERY close eye on this thread!
Good luck, I'm sure there are a whole load of people who'd buy you a beer if you succeed.
Steve
glad to see someones watching . ill have another play around over weekend see what i can come up with
it will be interesting to see how android works on BA keep up with the good work
Nice.
I like my BA and I don't wont to change it until an open linux mobile is avaible (an open Iphone could be great).
Maybe a sub-forum called "Blue angel linux" could help.
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
And this seems noise. And I don't want to pay for having linux on my BA!
http://www.a-la-mobile.com/news/press/pr080114.html
aperles said:
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
Click to expand...
Click to collapse
Not the access, but a nice gui/setup.
remember linux is designed primarily for people who know what their doing. yes theirs guis now which help but you stil need command line to use linux properly. except on the iPhone and android from what ive seen
actually there was an earlier thread regarding android. and with 921+ adding 200+ views here, We bet there are people that are REALLY interested porting this.
hope we get it up and running.
anything for our BA.
even alternatives to WM6 are welcome.
well im not having a lot of look, it seems to be segfaulting pretty much constantly. think its down to the busybox shell though so im going to find a newer one and try that later, does anyone know what version of the arm feature set the BA uses. (because from reading http://benno.id.au/blog/2007/11/21/android-neo1973) android only seems to work on devices using ARMv5 featureset. whatever that means)
UPDATE: thats not a problem, the pxa263 in the BA is ARMv5TE so thats ok - gotta love wikipedia (http://en.wikipedia.org/wiki/XScale)
Further update: ok been reading up a bit more and im doing the risky thing of building my own kernel for android see if i can get round these damn segfaults
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
DJ_Steve said:
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
Click to expand...
Click to collapse
I've compiled kernels under Linux before, but not for an embedded system like the angel's.
Where did you get the tarballs for everything? And what distro of Linux did you install?
Really, real machine vs virtual machine, in this case, shouldn't matter. It might, but shouldn't.
not so much the fact im using a virtual machine, its the fact im only on a 2mb connection so downloading linux cd images takes ages and since debian is the only distro ive seen which has arm crosscompile tools that work that means 2 dvds or 9+cd images. most of the tarballs ive had to rip direct from the android sdk emulator. i could host them somewhere if someone wants to try and help me out getting a kernel running - after that i think most of android should fall into place on its own, but getting openbinder support in the kernels proving difficult
EDIT/UPDATE: ok just tried installing the arm crosscompiliers on my development dedicated server and it seems to be compiling a kernel as i type (hopefully) so looks to be some progress happening here
Been following your thread with interest.
I should be getting a new PDA from work, so then I could take the risk of bricking my trusty and battered Blue Angel.
Any chance you could post some links to the various bits you are using? Not a step by step (unless you have the time) but the starting points so others can attempt to duplicate your efforts in parallel?
Good luck - I'm rooting for you!
ok, im just tarballing up the files on my webserver now, didnt have any success with kernel, looks like im going to have to take the blueangel drivers etc from the kernel posted on handhelds.org and manually merge the config files into the android kernel image to get it to compile. unless anyone can suggest a way to do that easily (windows or linux routine i dont mind)
the main sites ive used to help out ive listed below
http://benno.id.au/blog/ << somewhere on their theirs a link to the android root filesystem image. (http://benno.id.au/android/system.tar.gz and http://benno.id.au/android/data.tar.gz)
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/
http://handhelds.org/moin/moin.cgi/BlueAngelKernel
the three above above links help even though their not scriptly related to android on blueangel
the rest of the files are in http://radiodmp.net/android-files/ - the 365mb file contains the 2 arm cross compilers and also both the newest blueangel linux kernel and the android kernel - as said above these need merging (android kernel needs to be the one that is the final kernel as its newer i believe
edit: ive just put the system and data tars linked above into the folder on my server also to save people time.
hope that helps
if anyone wants any help drop me a message and ill try and help out. will of course keep trying to sort it myself too
Any update on this?
Actively watching this thread and just wanted to know. I'd love to be able to play with Android.
good to see ppl interested. ive not had time to try and merge the kernels yet, hopefulyl might get chance this week
DJ_Steve said:
good to see ppl interested.
Click to expand...
Click to collapse
Still watching, still interested!
Keep it up.
Steve
ok managed to hack together the two kernels, compiling it as i type - hopefully it'll workon my BA
Hi everybody , I was on youtube when i saw that video
http://www.youtube.com/watch?v=v1etbtava-g
Any info ???
No info but it looks awesome, it seems to be really smooth, I would love to have something like that on my KS20!
I found this
http://www.limofoundation.org/
Do you think that we can flash our KS20 with this OS ?
My english is not good , so please excuse me if I made some mistakes
someone got more information about this ?! looks very interesting but i cant find much about it via google and co.
greetz
limo its a project, this video its a testdrive demonstaration.
I found our phone (LG KS20) at here
http://www.limofoundation.org/en/limo-handsets.html
LG LiMo phone
^^ I think that's our KS20 with LiMo inside
I hope that we can also have it !!
I'm trying to boot android on my KS20 but i don't find one android release which boot arf =(
If someone can try to compile a new release of android which boot on KS20 , it will be great
Sorry for my bad english :$
Android | LiMo @ LG KS20
YOHA.. would be time to get rid of that WM6.1 from my LG KS20..
But, wait, LiMo is completely another thing than Android..
And besides that, I'm also pretty sure that Linux does work on the LG KS20, there is anyhow no trace of users able to do so in the wild till now..
So this means that either Android than some LiMo adehrent version should be available around: afaik there are no traces of such images or even help to build from sources..
Is this right or do somebody of you have some links/hints?
Maybe the closest relative to this is anyhow the HTC based Android compilations found in this forum (Vougue and Phantom..), maybe starting from them somehow..
But if someone has updates.. please do some postings here!
Cheers,
tent:wq
Hi everyone
After a hole night of compilation , i've obtain 4 files
"Generated: (out/target/product/generic/android-info.txt)
Target system fs image: out/target/product/generic/obj/PACKAGING/systemimage_unopt_intermediates/system.img
Install system fs image: out/target/product/generic/system.img
Target ram disk: out/target/product/generic/ramdisk.img
Target userdata fs image: out/target/product/generic/userdata.img"
A System.img , userdata.img , ramdisk.img and a text file android-info.txt
I don't know what to do with this files ( maybe haret ??? )
if someone would help me , it'll would be really apreciate ^^
Thanks
yuuuhuuu i'll be waitin for next info and release
Any new info on this? Willing to get rid of wm as soon as possible.
Any update ?
I'm sorry if i'm boring but if we can make linux works on our device , i think it wiil be great
as i'm a newbie , i really need help so everyone who want's to work in this project i leave my msn [email protected]
thanks you
News? (Android on LG KS20)
News? (Android on LG KS20)
I searched several times, but no traces of KS20 port of Android for the moment.
If you look at the nearest hardware device in advanced dev, you will see it's not gonna happen soon with full features :
http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
kancrutt said:
yuuuhuuu i'll be waitin for next info and release
Click to expand...
Click to collapse
up..
tent:wq
No Android release for KS20
I'm sorry guys but it will be hard to have Android on KS20.
This LGE phone is based on MSM7200 old Qualcomm chipset at 400MHz.
Qualcomm started developing Android releases on newer MSM7200A which not only has higher clock for the ARM11 application processor, but also different architecture in terms of graphic acceleration. This means there will not be any official release compatible with KS20 in the future.
Although me and other engineers, who have access to Android and Qcom drivers code, would like to port it to this device, we are struggled by the fact that we don't have any drivers from LGE, to make all other things working (primarly camera and display). So, no way we can do it for now...
Anyway, without the benefit of having Qualcomm Adreno 3D graphic accelerator on it, it will be a pain to run Android UI on KS20!
webjoker said:
I'm sorry guys but it will be hard to have Android on KS20.
This LGE phone is based on MSM7200 old Qualcomm chipset at 400MHz.
Qualcomm started developing Android releases on newer MSM7200A which not only has higher clock for the ARM11 application processor, but also different architecture in terms of graphic acceleration. This means there will not be any official release compatible with KS20 in the future.
Although me and other engineers, who have access to Android and Qcom drivers code, would like to port it to this device, we are struggled by the fact that we don't have any drivers from LGE, to make all other things working (primarly camera and display). So, no way we can do it for now...
Anyway, without the benefit of having Qualcomm Adreno 3D graphic accelerator on it, it will be a pain to run Android UI on KS20!
Click to expand...
Click to collapse
This is a video by me ...
http://www.youtube.com/watch?v=l1UB9jLpwmw
gregnapola said:
This is a video by me ...
http://www.youtube.com/watch?v=l1UB9jLpwmw
Click to expand...
Click to collapse
WOW! this gives me hope!
Do you have something to download and compile.. and maybe contribute?
some LGE drivers showed up at last or what? I suppose no touchscreen working atm but anyway worth to try..
tent:wq
tentator said:
WOW! this gives me hope!
Do you have something to download and compile.. and maybe contribute?
some LGE drivers showed up at last or what? I suppose no touchscreen working atm but anyway worth to try..
tent:wq
Click to expand...
Click to collapse
Hi, you can try to load 0.8 linux images and almost all of other initrd like angstrom etc... with earlier Htc Niki's Kernel. Unfortunately I can't login trough ssh and GPIOs detection list from Haret doesn't correspond to the ones listed in the detailed Ks20 service manual...
I'm starting a new thread and I hope to involve some people with more skill than me...
ok, let me know about that new thread and links to the material and instructions, and I'll also try to contribute.
tent:wq
gregnapola said:
Hi, you can try to load 0.8 linux images and almost all of other initrd like angstrom etc... with earlier Htc Niki's Kernel. Unfortunately I can't login trough ssh and GPIOs detection list from Haret doesn't correspond to the ones listed in the detailed Ks20 service manual...
I'm starting a new thread and I hope to involve some people with more skill than me...
Click to expand...
Click to collapse
Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Now our smartphones become a mini computers.
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.
pharatlil said:
Google says android 4.4 kitkat is available for everyone. So is it means we can flash it directly to our galaxy w?
Click to expand...
Click to collapse
No, it needs to be ported.
pharatlil said:
in dekstop computers we can install a new os(linux or windows) directly. The OS recognize the drivers then install them directly or from the web. Maybe some of hardwares drivers cant find but its very rare issue.
So why android doesnt like this. Thats everybody install new version of android and its install the phones drivers directly or from the internet.
The smartphones hardware manufacturers less than dekstop computers hardware manufacturers but dekstop computers OS can do it well and avaliable for every kind of computer.
Why Android OS install like dekstop computers OS.
Click to expand...
Click to collapse
This is just partially true. Windows and Linux for desktop PCs already come with most of the drivers directly on the CD or DVD or at least with hardware IDs for the drivers they can download and install via internet.
Your ROM simply isn´t about the same size like a Linux or Windows DVD It also doesn´t have a 100GB HD, a DVD drive and at least 4GB RAM installed.
So if you want an Android that is about as easy to install on all devices, you would have to make it about that big in size like a Linux or a Windows installation DVD which most of the devices couldn´t handle.
That´s why it needs to be ported with just the drivers for your specific device. And this is also the advantage to keep it as small and slick as possible.
Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.
pharatlil said:
Most of linux os about 1gb.
Windows is about 1-2 gn. Not about 100gb.
İ ha ve a galaxy s3 and stock rom about 900mb.
İf google want to give latest firmwares every device They can make a pc program and it finds devices specs automatically.
Samsung, htc, lg...etc.. maybe dont want to give newest firmwares to older devices for selling new devices.
But why google dont make roms for every device. Android is a linux based os and linuxs difference is its avaliable for everyone. So i think googles s strategy about android isnt true. İt must be same way with linux.
Click to expand...
Click to collapse
A totally fresh installed Windows 7 already is taking about 4GB on your HD and needs a way bigger partition to get installed at all.
Android is not a linux based rom. It´s a Java based ROM. Only the kernel is linux and this needs to be compiled first and match your hardware to make it able for the rom to work at.
Google only offers the basic code for a ROM but the rest must be added by the manufacturers. Beside this linux also wasn´t that userfriendly like it is now. The very first releases even didn´t use an UI. All had to be done on command line. Was meant to be used on servers but not for end users and though it was open source it took about 20 years from this stage to become an userfirendly OS for endusers like Windows.
So this is like comparing apples with pears. Best you ask Google and see what they will answer you.
İm disagree with you. or i couldnt explain well.
There in not more hardware manufacterers than PCs. But dekstop computers OS can handle it. For example i have got a hp compaq nx8220 notebook. its very old pc but i intalled windows 8 and its running very well. There is no drivers for windows 8 but windows have a feature for it. İ install many drivers in compatibility mode. ( Yes HP didnt publish a driver for it but windows's this compatibility feature solve the problem.)
Im not a developer but i know programming dialectic (i wrote programs in q basic and gw basic but i stay away from programming because of my job.) im interested about java and c++ and im learning. im seeing that developers main problem to porting Android to a device is hardware drivers. İf manufacterer give codes they port it easier.
İ want to say my hp compaq nx8220 is very old device but its runs with windows 8 very stable.
But my old phone and and my wifes phone galaxy w isnt a old device but they r saying your device cant runs properly with android's newest OS. It has 512 mb ram and 1,4ghz processor.??? (my notebook worst but runs w8)
Maybe one day some developers agree with my opinion and work with hardware drivers than making alot of custom roms. So maybe one day we enter a web page (for example cyanogenmod web page)and flash newest rom like installing a newest OS to a PC.
You may agree or disagree. No problem with that. It´s just you are comparing apples with pears. An Android Phone isn´t the same like a PC. Doesn´t have a HD or something equial to this in its capacity and so on. Neither Android, Firefox OS or Ubuntu Touch do have such an installer included that will install the Operating System on all devices. They all need to be ported. The same even for Windows Phone. So rather than arguing with me, go out and ask all the big players like Google, Ubuntu, Firefox or Microsoft why this isn´t the same like fo a PC.
Yesterday I bricked my brand new P8000(B) - the new version with Marshmallow 'out of the box' (and the new SIM slots etc...)
I tryed to reflash several stock- and custom ROM's but they don't work because they are made for the 'old' version and there must be major differences in the hardware. At the moment the main problem is that the LCD driver is wrong and the display shows only lines and blurry spots
The Phone was running on ROM "P8000_6.0_20160516" - this ROM is not available at needrom or bbs.elephone.hk even Google doesnt know
It would help a lot if some could supply the ROM "P8000_6.0_20160516" - thank you!
FrauHofrat said:
Yesterday I bricked my brand new P8000(B) - the new version with Marshmallow 'out of the box' (and the new SIM slots etc...)
I tryed to reflash several stock- and custom ROM's but they don't work because they are made for the 'old' version and there must be major differences in the hardware. At the moment the main problem is that the LCD driver is wrong and the display shows only lines and blurry spots
The Phone was running on ROM "P8000_6.0_20160516" - this ROM is not available at needrom or bbs.elephone.hk even Google doesnt know
It would help a lot if some could supply the ROM "P8000_6.0_20160516" - thank you!
Click to expand...
Click to collapse
I can do nothing else than blaming you, I wrote a reply yesterday to the eragon forum that there's someone else who flashed -not even a custom rom- just the root .zip that was for the "old" p8000 and got his phone bricked the same way as you (LCD driver problem). That's why I asked for a dump/backup. It could have been useful for you too (as in this case) and for the other guy too. But nevermind, I hope that you learn from this for later things... anyways, the other guy has contacted elephone on their facebook, so I hope you'll get the rom so you can use your device again. Good luck!
I have this version too, just got it today.
If someone can explain to me how to create the scatter file and the backup, I'll do it.
I have some experience with this stuff, but MTKDroidTools tells me unknown rom structure.
Any help?
I do have the same problem (see here: http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571 ). I just wanted to root the phone because I liked to change the wifi modem file but i didn't even realize that I got another version of the phone at this point, so I bricked it.
I also contacted the support via facebook, but the support guy had to ask the engineers for help.
But maybe someone can help Emileh taking a dump of his phone, that would be really great!
@ardrift
you are sooo right but I have'n expected that two phones of the same type contain conplete different hardware respectively the firmware is not supporting both hardware versions. Even the manufacturer does not metion to check the hardware version before flashing...
@Emileh @flo1k
I do have a second 'untouched' P8000(B) too - and I'm starving to copy the firmware from this working phone to the faulty phone if someone could explain how...
problem solved
flo1k managed to get a stock ROM for this hardware version - the softwarepackage is named K06TE-A.A.vR14.E1.160707 and should be available at the elephone forum soon....
Further information you can get here http://forum.xda-developers.com/elephone-p8000/general/2016-version-fingerprint-scanner-t3436270
Hello all Intel atom owners,
I am the owner of a device destine for the trash heap (e-waste sucks) but I'd like to save it from that fate. My device is a z2560 soc asus Trio TX201LA. Its tablet half is what has been deemed ewaste by asus & id like to save it from that fate. Windows 10 has also ended support for clovertrail now so that also SUCKS..
This thread is being started to talk about development on these devices that intel gave up on. Android is primary focus but I don't want to limit it to that cuz the soc can do more. I'd like to discuss the following:
1. How the device boots? In what order? What files are used? Variations per device? Similarities between asus & Dell and Samsung (3 largest intel atom inside device makers during 2011-2016)?
2. What tools are available to us to save our devices and in save I mean upgrade.5 tools Ive found that are so interesting are the following:
2A. Intel Manufacturing Flash Tool lite (For dual booting devices specifically?)
2B. Intel Platform Flash Tool Lite (For both atom & intels Edison devices): https://software.intel.com/en-us/articles/flash-tool-lite-user-manual
2C. Intel xFSTK Downloader (rescue flasher, seems to be primarily for bay trail but also clovertrail)
2D. ASUS Flash Tool, not sure about this one, I bet its only for zenfone, have to check.
2E.. Flashall for Edison devices only, so useless for atom tablets: /docs/DOC-25154 https://communities.intel.com/docs/DOC-25154
4. I'd also like to look at droidboot ver 2.0 and 2.1, whats the difference? It seems droidboot is intel and is intel own way of getting android to boot. What is also interesting is that some devices running android 5 got an update that changed droidboot a lot. So much so that it has a uefi partition (dell venue 7, asus memo pad 7 & maybe others) & after that update boots android differently using what seems to be a more generic x86 android (like a pc image).
5. Intel DnX (download and execute) mode. This seems to be a product of Device updates beyond droidboot 2.1 and android 5.0. Id like to discuss if its possible to add DnX to devices that don't have it. It runs from an image off the main disk just like droidboot and even android. So the theory is it could be simply added to other images & devices?
6. Alternative OS options (Reference: https://communities.intel.com/thread/120652):
6A. Sailfish OS devices that are atom based such as the Geeksphone Revolution & Jolla Tablet have sailfishOS, but so do dual boot atom devices including CHUWI hiboot, Hi8, a bunch of Lenovo devices, to many to mention here.
6B. Ubuntu this is possible but only if clovertrail can gain either DNX, droidboot 2.1 or uefi (my theory) .
6C. Remix OS see: https://forum.xda-developers.com/remix/remix-os/release-remix-os-pc-32-bit-t3305916 Remix OS can be run on our devices but again only if we can gain droidboot 2.1, uefi & or DNX (again my theory)
6D. MultiROM for intel (unknown) see: https://www.xda-developers.com/install-use-multirom-xdatv/ There is also support for galaxy tab 3 10.1 a fellow z2560 soc device. So getting multirom support could be added for almost all z2560 devices via this support see: https://www.getdroidtips.com/dual-boot-galaxy-tab-3-10-1-dual-boot-patcher/
6E. Others including second stage bootloaders. Google that term and many come up.
Ok so that is about it. I did not include a lot of links here purposefully, almost every term I used here can be googled for the info I found. The x86 android devices are flexable and able to do more but have primarily not been developed for because intel sucked at advertising them, failed to get them into apple devices and killed them off early. So we are where we are but intel is also very open. There are so many tools to develop for this platform if you know and understand x86. I believe I could rebuild my entire tablet image using the Intel Manufacturing Flash Tool include the newer droidboot 2.1, dnx image, and a updated kernel and system image of android with my device specific drivers and be up and running to a point where I could then dual boot other OS's. I theorize that if you tried this and failed you could still use the Intel xFSTK Downloader to rescue the device completely. Yes I'm a noob & its why I want to learn more via this thread. Think this development is a waste of time, see: https://www.asus-zenfone.com/2015/07/asus-zenfone-2-running-windows-7.html
I'd love to see other intel owners join and discuss these ideas, grab your intel device dust it off and join me in experimenting.
Bumpy boompop shazam.. Hello Atoms not DEAD yEt.. https://www.pcworld.com/article/315...m-chip-in-panasonics-2189-android-tablet.html
Yep, I'm still working on trying to get unsigned stuff to work myself.
pcwizzy37 said:
Yep, I'm still working on trying to get unsigned stuff to work myself.
Click to expand...
Click to collapse
Any progress? Its a shame such a great device is meant to die...
UPDATE. I found this topic.. https://groups.google.com/forum/#!topic/android-contrib/t6AEhwaILUs
Interesting..
madhits45 said:
Any progress? Its a shame such a great device is meant to die...
UPDATE. I found this topic.. https://groups.google.com/forum/#!topic/android-contrib/t6AEhwaILUs
Interesting..
Click to expand...
Click to collapse
Nope, no progress, my backlight also got messed up pretty bad by a diode being defective and letting current pass both ways, so now I cannot change brightness, or else the screen turns off. But nope, still stuck.
pcwizzy37 said:
Nope, no progress, my backlight also got messed up pretty bad by a diode being defective and letting current pass both ways, so now I cannot change brightness, or else the screen turns off. But nope, still stuck.
Click to expand...
Click to collapse
Bummer, What tablet do you have? I have a Asus TF201LA its also know as the transformer trio. The tablet half has android 4.2 and its basically useless, the screen of the tablet is shared with windows 10 dock which I am still using daily. The atom z2560 cpu in the tablet is still pretty fast with 2gb of ram, but no updates or i should say no unlock keeps it useless.
madhits45 said:
Bummer, What tablet do you have? I have a Asus TF201LA its also know as the transformer trio. The tablet half has android 4.2 and its basically useless, the screen of the tablet is shared with windows 10 dock which I am still using daily. The atom z2560 cpu in the tablet is still pretty fast with 2gb of ram, but no updates or i should say no unlock keeps it useless.
Click to expand...
Click to collapse
I have an Acer Iconia One 7 (B1-730HD), which has the Z2560 as well, but a pitiful 1GB of RAM.
pcwizzy37 said:
I have an Acer Iconia One 7 (B1-730HD), which has the Z2560 as well, but a pitiful 1GB of RAM.
Click to expand...
Click to collapse
VERY exciting info to come. I am working with a zenfone hacker who hopefully will help me adapt his bootloader unlock to my device. Ill update when I get something and document everything for you.
Keep us updated. I have a Asus VivoTab ME400c.
Any updates? I have an HP Elitepad 900 G1 with a Z2760.
I have ASUS Memo Pad 7 (K017) with atom Z2520, which is no calling edition with FE170CG...
I have found some new information and ideas for this.
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card
http://www.linuxium.com.au/how-tos
I am trying to understand how you boot from droidboot to a SD card or via USB. I'm willing to try some of these because they do not evolve flashing a recovery which does not match mine. I also found a CWM recovery for the memo pad 10 FHD but whats the point without a new rom. If I can boot linux I could boot x86 android.
I have an acer w3-810 with some (fairly buggy) uefi firmware.
Since this is a windows device I've been able to disable secureboot and play around with unsigned uefi programs. If for some reason your device doesn't disabling secureboot, you might be able to change the variable in your firmware file via uefitool (popular in the bios modding / hackintosh community) and then reflash it if there's no signature checking pre-flash.
On the linux side I've basically gotten no where. The graphics module / kernel params should be set up similar to cedar trail (from my basic research clover is just a lowend version of cedar). But unfortunately that doesn't get me anywhere. Disabling uefi via the kernel param noefi or disabling uefi runtime services gets the display to spazz black and white lines. Going to try to compile a custom kernel later though and see if I can get preboot early efiframe buffers working for earlyprintk.
Interestingly the tablet (through some trickery (force it to boot to a non-present device)) will let you switch the graphics mode of operation between pci and agp