O2 Joggler Forum

Initially looking hopeful, but getting boot loop and double image on bootanim so thrashing Google for debug infos, but no reason why it shouldn't work just fine!

In a word no :$ give us a clue, looks interesting....

Jellybean?

JimbobVFR400 wrote:Jellybean?

Androidx86 Jelly Bean 4.2 to be precise! As the previous Miiju et al Android releases seemed to have stopped coming, I thought I'd have a pop at the latest http://www.android-x86.org release, as after all, our Joggler is simply an x86 computer with touchscreen and internal flash storage, so it should just work!

Well, almost!

Where I'm at now:

Boots to bootanim "android" screen. albeit in 16bit and split screen of two l/h r/h screens and boot loop!:


OK, so a way to go yet, the split screen has been encountered before and is due to poor/no support of our Intel GMA500 'Poulsbo' graphics chip, but there is hope, as there is an Xorg modeset driver recently surfaced that can hopefully find it's way into newer Androidx86 builds, even so, it should be possible to get usable screen with Vesa for now, but I will have to trawl through the logcats and Google to find out why I have a boot loop...

To get where I am now, I downloaded the latest Androidx86 'live' .iso image, booted it on VirtualBox, 'installed' it to my pre-partitioned SD card (4gig: sda1=2gig Ext3, sda2=1gig Ext3, sda3=1gig whatever), then took the Efi files from previous releases and stuffed them in, edited the 'Android-x86...' folder to be just 'android' and that was about it.

Anyone with some ideas to how to jump the next hurdle, I'm all ears!

anyone got jellybean working on this yet ??

I think that until someone at the Androidx86 project sorts out the EGL graphics issue, it's a non-runner for now.

I have tried everything I can think of to get past the boot loop to no avail so far, not much interest or suggestions over at the Androidx86 forums either:

https://groups.google.com/d/msg/android ... rTk0NICFQJ

There is a modesetting driver out there for the GMA500 (Poulsbo) graphics, but I don't think it has arrived in Androidx86 yet...

Any more interest on this?

I would love jellybean on this device it would be great to use with tomtom in my car

There's been no new releases since end of Feb https://code.google.com/p/android-x86/downloads/list and no help on the 'support forum' https://groups.google.com/forum/?fromgr ... ndroid-x86 (or here for that matter) so we are pretty much stuck until either a newer release appears (which may include some mentioned Intel graphics improvements) or someone suggests a fix. I suspect that is it something that will require compiling and adding to the boot image, so this is over my head I'm afraid.
If anyone has any other ideas or clues as to how to get past the 'slit Android' boot animation screen, I'm all ears!

My post to the Androidx86 list:
https://groups.google.com/forum/?fromgr ... Kb2YvenNi0 please bump it if you want it to be seen, the list gets loads of posts with very few answers..

How come there's so little progress on getting Android working on the Joggler in an easy to use way?

I want to install Android on the internal memory of my Joggler so my USB slot is free but I'm not sure how to do it

deeinlondon wrote:How come there's so little progress on getting Android working on the Joggler in an easy to use way?

I want to install Android on the internal memory of my Joggler so my USB slot is free but I'm not sure how to do it

Progress is slow die to lack of knowledge and poor support for the graphics chip in Linux basically. Unless someone can build an Androidx86 image which includes support for the Poulsbo GPU, we are stuck. Support in the Androidx86 forums https://groups.google.com/forum/?fromgr ... ndroid-x86 is not what it could be, I got no replies when I posted...

There have been some 'new' releases over on Android-x86 recently: https://sites.google.com/a/android-x86.org/web/ but I've not got round to testing them (and my Virtualbox got broken after playing with different kernels...>.<), will have a go soon and see if any improvement...

The options as I see it now are:

• *Use old existing Android images
  *Hack a newer Androidx86 release to disable fancy graphics (poor user experience)
  *Find out how to include support for dodgy GPU (of which there has been some work recently but...)
  *?

By the way, you don't have to use the internal memory, why not use a USB hub, then plug in all your USB devices simultaneously?

Just noticed new test build of Android 4.3 is out for the x86 and it boots in Virtualbox ok, so hopefully will get round to trying it on the Joggler shortly...

Of course, this was the first place I came when I read this article http://liliputing.com/2013/08/android-4 ... uters.html

I think I might have a shot. Virtually no chance of me managing to make it work though