jazzmista wrote:And now I can't reset my repo as it has uncommitted changes which I can't drop. Fantastic! GodAmongDucks, would it be possible to upload your build to another repo (on GoogleCode or the like) that we can both commit to?
git repo? and you want to remove all local changes?
git reset --hard ?
also git clean -f -d
etc
It's not letting me quote you Buzz (for some reason - tech really doesn't like me today!)
~~~~
I've already tried all the git commands, but Git doesn't recognise it as a Git repo (but Repo does!)
jazzmista wrote:And now I can't reset my repo as it has uncommitted changes which I can't drop. Fantastic! GodAmongDucks, would it be possible to upload your build to another repo (on GoogleCode or the like) that we can both commit to?
Hey Jazzmista,
no problem, if you want to set it up, and give me the instructions i'll be happy to do so. I'll be travelling for business next week forward so wont have much time to work on this till Christmas.
swifty wrote:I've been meaning to do some more testing on android for a while but haven't had time.
I got honeycomb booting but without any acceleration at all and didn't have the touchscreen working.
I didn't have any more time to play with it since then but hopefully will do again soon.
my next step was to enable the new gma500 staging driver present in the new 3.x kernel as its not reliant on xserver afaik.
That sounds great swifty...any specific pointers on how you got it up and running? As i'm new to building Android (and I think a few are) would be great if you could share
Would also be very interested in understanding how Mijuu's patches for his Froyo build differs from those on the wiki...does anyone know or have these?
jazzmista wrote:And now I can't reset my repo as it has uncommitted changes which I can't drop. Fantastic! GodAmongDucks, would it be possible to upload your build to another repo (on GoogleCode or the like) that we can both commit to?
Hey Jazzmista,
no problem, if you want to set it up, and give me the instructions i'll be happy to do so. I'll be travelling for business next week forward so wont have much time to work on this till Christmas.
Thank you!
There are some guides on the Google Code site here - http://code.google.com/p/support/wiki/GettingStarted .
It's very similar to repo except it doesn't use the repo command - it uses proper git! I'd recommend doing the source code upload overnight as it will probably take a while :-S
You will need to set up git (and upload to the Google Code project) using the folder you downloaded from Android-x86 - in my case the folder jogglerics.
GodAmongDucks wrote:That sounds great swifty...any specific pointers on how you got it up and running? As i'm new to building Android (and I think a few are) would be great if you could share
Would also be very interested in understanding how Mijuu's patches for his Froyo build differs from those on the wiki...does anyone know or have these?
No real instructions as such at the moment - I've simply been larking around with the source and seeing what happens, I think the most successful boot was using Mijuu's kernel/initrd and then merging the joggler specific bits from his image into the honeycomb filesystem.
That was only for fun though, the real aim is to get a fully compile-able joggler image straight from source using the gma500 staging bits, but I don't know how feasable that is in reality...
Hopefully I'll get some time to tinker a bit over xmas.
The good news is that I got ICS to compile (re-syncing the repo made fixed potential missing file, or maybe the x86 guys have been working on the side.
- it boots (boot screen logo is very slow - definitely no hardware acceleration).
- it shows the main screen
- it boots with a hub + mouse + keyboard
- Mouse can be used to navigate
- keyboard can be used to write commands in shell
Things that dont work (yet):
- Touchscreen
- Graphics acceleration
- No portrait layout
- Reboots after a few minutes without activity
I will make a small video and upload tonight.
Considering this, I think it may make more sense to work on ICS rather than Honeycomb for the Joggler.
Edit:
Forgot to mention, that to get it to work, you have to compile ICS first, and then use the initrd.img and kernel file from Mijuu's build. Also the Grub file needs editing.
GodAmongDucks wrote:Good news people [Dr. Farnsworth voice]
The good news is that I got ICS to compile (re-syncing the repo made fixed potential missing file, or maybe the x86 guys have been working on the side.
- it boots (boot screen logo is very slow - definitely no hardware acceleration).
- it shows the main screen
- it boots with a hub + mouse + keyboard
- Mouse can be used to navigate
- keyboard can be used to write commands in shell
Things that dont work (yet):
- Touchscreen
- Graphics acceleration
- No portrait layout
- Reboots after a few minutes without activity
I will make a small video and upload tonight.
Considering this, I think it may make more sense to work on ICS rather than Honeycomb for the Joggler.
Edit:
Forgot to mention, that to get it to work, you have to compile ICS first, and then use the initrd.img and kernel file from Mijuu's build. Also the Grub file needs editing.
Great news!
Merry Christmas
Last edited by jazzmista on Tue Dec 27, 2011 9:39 pm, edited 1 time in total.
I've created an empty Sourceforge repository at https://sourceforge.net/p/joggler-ics - still haven't downloaded a *working* version of the code so if anyone could upload the current working state of the project it would be very helpful .
If you want Admin rights for the project please PM me.
On a side note, found an interesting thread in the Android-x86 google group: https://groups.google.com/forum/#!searc ... ZOvlejeWUJ (Yes, I know the thread is about GMA600 acceleration but it mentions how to enable the GMA500 drivers).
BuZz wrote:those are the in kernel drivers though. no 3d etc etc.
Ah right OK - thought something was a bit odd as I haven't seen any 3D drivers yet!
GodAmongDucks wrote:Thats great! This was beginning to drive me slightly bonkers! Well that and jailbreaking the playbook to run android apps :S
Recreating my build environment and downloading everything again over terrible WiFi was driving me bonkers! Sorry for the off-topic, but how are you doing with the Playbook? Was going to buy one at £149 but then didn't bother due to limitations with email etc. (don't own a BlackBerry)
GodAmongDucks wrote:Thats great! This was beginning to drive me slightly bonkers! Well that and jailbreaking the playbook to run android apps :S
Recreating my build environment and downloading everything again over terrible WiFi was driving me bonkers! Sorry for the off-topic, but how are you doing with the Playbook? Was going to buy one at £149 but then didn't bother due to limitations with email etc. (don't own a BlackBerry)[/quote]
Sorry for that....my build environment got up to 20gb, and couldnt locate what I could exclude to sync to the repo. Tried both eeepc, brazo and a few other targets to see what the difference was...in the end only eeepc yielded results.
As for the Playbook....at the moment, i'm just happy I got a 64gb for a really good deal....its a good device spec wise but the app availability is terrible. I've been told the next OS update should have full android support (for platform independent apps) which would make it a good little tablet for my dad
