Hi All,
First, please refrain to post if not related to development, don't clutter this thread.
Divx118, as I promised, here is my current source status.
You'll find attached the repo diff of aosp 4.0.3 where I stand up to today. It contains mostly traces, few hacks for sgx and touchscreen.
On top of this, I'm using a device definition that I uploaded there:
https://gitorious.org/archos-ics
It's a work in progress, it doesn't have half of what's needed. The init.rc is not valid, I'll attach my current one later on.
You'll find there also the 2.6.35 kernel ported from gen9, only for a70s currently. It's not finished either, I'm having crashes in backlight and touchscreen is not recognized. It requires proprietaries from LG P970 for sgx.
Currently, I'm working with this kernel so BoardConfig.mk should be modified with ARCH_ARM_HAVE_TLS_REGISTER := false to work with 2.6.29
Last, to make the build start, you'll have to grab libaudio.so and libaudiopolicy.so from regular Archos build. Sound won't work but zygote will start.
I'll update post later on, but if I wait for something finished I'm afraid it would take forever
Update 01/07 :
As many asked and I didn't make lots of progress, here is my current build. This one is using 2.6.29 kernel. sgx, touchscreen, wifi works. You *have* to edit initramfs.cpio.gz as you probably don't have the same partition layout as I do. It's for developers only, I won't explain how to make it run.
Cheers,
LeTama
*reserved*
I can't help at all in terms of development, but I will test every single release of this you guys come up with. This is a true milestone for our little seemingly abandoned tablet. I wish you guys the best, and can't wait to see what happens
Thanks Letama sorry I missed you at irc. (still have to work these holidays )
divx118
No problem divx118, same here, work and family, busy days and no time for interesting stuff
Sorry for the messy post and the code state, I wanted to push something out at least before getting caught on something else...
I added the init.rc on first post. This one is again for my .35 kernel, you'll need few adjustments for .29 (mknodes for adb and maybe few things), and it misses probably some mkdir/chmod on /data for initial boot.
Good work now i try it
I can't develop but I will also follow and do whatever I can to help.
Sent from my PG86100 using XDA App
I can develop, but I just know a delphi, basic and a little c#, java
I've been developing games for a several years now and I know how to use ADB
But I don't know anything about kernels and roms
I'll see where I can help
Little update:
I pushed my last changes for the .35 kernel, it has working touchscreen now and feels globally faster than .29. I tried few builds of wifi module for it without success, I couldn't find proper source/firmware for now. Maybe we'll get them when Honeycomb for 70IT2 goes out.
So I went back to .29 and made wifi work, unfortunately browser doesn't. Webkit is using accelerated graphics with an OpenGL extension our driver doesn't have. Does anyone know how to disable it ?
Only the Stuck Browser don´t Work
or any like Dolphin HD
when its Any try to edit webkit false fix
USE_OPENGL_RENDERER := false
And one other thing i have test to build it ... It worked but than i havnt a single .img i have many like system.img .... How can i get only one ?
AlphaTime said:
USE_OPENGL_RENDERER := false
Click to expand...
Click to collapse
USE_OPENGL_RENDERER is for framework, not webkit right ?
Framework is OK and I'd like to keep opengl there.
ENABLE_WTF_USE_ACCELERATED_COMPOSITING seems to be the key for webkit, but it doesn't seem to build properly. Oh well, I'll check that later on.
AlphaTime said:
And one other thing i have test to build it ... It worked but than i havnt a single .img i have many like system.img .... How can i get only one ?
Click to expand...
Click to collapse
These images are useless, they're coming from panda device configuration. You have to build your own img file, mix the Archos root with the files you'll find in out/target/product/g8/system directory.
Don't forget to replace archos init.rc with the one I attached. You need to push few stock archos firmware files on top of that, libaudio.so, libaudiopolicy.so and sgx files if they were not pulled from the device when you did the build.
egl.cfg needs to be replaced too.
Hi letama!
letama said:
You'll find there also the 2.6.35 kernel ported from gen9, only for a70s currently. It's not finished either, I'm having crashes in backlight and touchscreen is not recognized. It requires proprietaries from LG P970 for sgx.
Click to expand...
Click to collapse
I pulled the kernel from your repo and compared it with latest Archos gen9 2.6.35, to get an idea of the changes you made to get it work for A70s.
Seems that you used an early release from the archos git tree.
So looking at the diff generated against latest published sources from Archos,
i realized that some of latest patches are missing.
Maybe these udates would bring us into a better situation in general.
If you got some patches of the work you made for A70s please let me know...
I'm little old fashioned and like to fiddle around with diffs and patch files
You also spoke about wifi now working with ICS in another thread...
Was this related to 2.6.29 or 2.6.35 kernel ?
Refering to the config for gen8 on 2.6.35, it seems that the you used the internal kernel wifi driver, is this correct?
So the external ti module is not working for 2.6.35... also correct?
I guess i'll try another kernel build for A101it this weekend.
Thanks a lot for your work!!!
Regards,
scholbert
Hi Scholbert,
scholbert said:
I pulled the kernel from your repo and compared it with latest Archos gen9 2.6.35, to get an idea of the changes you made to get it work for A70s.
Seems that you used an early release from the archos git tree.
Click to expand...
Click to collapse
Yes, I started quite early, but I merged up to 3.2.61 afaik. So not that far from last release, 3.2.69.
scholbert said:
Maybe these udates would bring us into a better situation in general.
Click to expand...
Click to collapse
I'm a bit better already, I made the touchscreen work. I didn't pay much attention to the change of backlight as I "workarounded" the problem by removing archos dll that controls power. I reached my initial goal, boot ICS and see if sgx drivers are better.
I believe it is, it felt quicker all around, but it didn't solve my crashes that I now believe are not really sgx related. I always see the driver as PC,LR in control panel app, but there are multiple threads and crash is probably elsewhere.
So globally kernel is nice, misses apparently only hdmi and wifi. Wifi may be difficult, we'll see. As I never compiled tiwlan, I'm back on gen9 to understand the process first.
scholbert said:
If you got some patches of the work you made for A70s please let me know...
I'm little old fashioned and like to fiddle around with diffs and patch files
Click to expand...
Click to collapse
git allergic ? Can understand, took me time to get used to it and I probably use 30% but that's enough for me and I won't go back to diff / cvs.
You can get diff from git, just do a "git log" to get commit id then "git diff commit_id"
scholbert said:
You also spoke about wifi now working with ICS in another thread...
Was this related to 2.6.29 or 2.6.35 kernel ?
Click to expand...
Click to collapse
2.6.29... few patches and config to ICS, and it works.
Refering to the config for gen8 on 2.6.35, it seems that the you used the internal kernel wifi driver, is this correct?
So the external ti module is not working for 2.6.35... also correct?
Click to expand...
Click to collapse
Wifi is not working yet, need to first get a grasp on TI way, I always worked on broadcom. TI way is a bit weird for me, I have troubles understanding what version should I get in their tree. Well, we'll see. I need first to make it work for gen9...
I managed to build apparently good tiwlan.ko but while I was trying it I destroyed my gen9 config for other reason, ending up in needing a full format . And I'm good for another as I did update my firmware and forgot to put back my patched recovery, it resized my system partition to a too small size. Grrr. I think I'll work on an initrd to resize partition finally, at least it would have a benefit for the community .
I guess i'll try another kernel build for A101it this weekend.
Click to expand...
Click to collapse
Finally, after updating the git to .61, most changes needed were in a70 board file and back to almost the same file as A10it. So you could have good surprise there. The only delicate part is the sgx driver that I grabbed from p970, but you don't need that at first. Let me know if you get somewhere!
Cheers,
LeTama
As many asked, I added my current build. See first post for it and few details.
Hey letama,
thanks a lot for publishing your build.
It is little irritating, if useful information a is placed in seperate threads...
Maybe we should focus on this thread in the development section.
So i'd like to refer to your answer in the general section (and possibly mix things up):
http://forum.xda-developers.com/showpost.php?p=21191729&postcount=36
I'm not working on Android level because i'm missing the build evironment.
I simply got no adequate machine at hand to set everything up
Back to your post:
letama said:
Ah, market, not very surprising... I just added the ICS google apps quickly just to have a look,
Click to expand...
Click to collapse
Which GAPPS did you integrate?
There'd been similar reports that properly working ICS GAPPS are very hard to find...
letama said:
Screen rotation is normal too, no sensors yet.
Click to expand...
Click to collapse
Agreed, this is a know fact on the A101... fix could done in ICS itself i guess.
letama said:
The only things that work is accelerated graphics/touchscreen on A70/wifi, that's all. The to-do list is huge. On top of my head:
- Web browser (crashes because of missing OpenGL extension)
- Audio (don't know yet what's missing)
- Audio/Video Codecs (dsp support won't be easy)
- Sensors
- Power management
- Memory tuning
Click to expand...
Click to collapse
Some things mentioned here, might rely on kernel i guess and as you said wifi is working... i guess this again refers to 2.6.29 sources, correct?
As this source code is not part of your repo i'd like to concentrate on implementing A101it support for 2.6.35.
It seems there'd been some additions in audio framework in one of the last patches provided by archos
Maybe these patches could be integrated in your ICS 2.6.35 kernel branch as well. Still need to fiddle around with the original sources and git, to get more information about the state of this project in general.
I'm sorry if i mix things up myself, but in fact i'd like to find some "central theme" for ICS development on Gen8.
Should we stick with the 2.6.29 kernel first?
If so it would be very nice to get some information about your patches/canges you made in 2.6.29.
Regards,
scholbert
scholbert said:
Agreed, this is a know fact on the A101... fix could done in ICS itself i guess.
Click to expand...
Click to collapse
Yes, I done it on gingerbread CM7 in frameworks/base/surfaceflinger/SurfaceFlinger.cpp
https://www.gitorious.org/openaos-c...frameworks/base/surfaceflinger_rotation.patch
I don't know how much different it will be in ics, didn't look at any ics code yet.
divx118
scholbert said:
Hey letama,
thanks a lot for publishing your build.
It is little irritating, if useful information a is placed in seperate threads...
Maybe we should focus on this thread in the development section.
So i'd like to refer to your answer in the general section (and possibly mix things up):
http://forum.xda-developers.com/showpost.php?p=21191729&postcount=36
Click to expand...
Click to collapse
Yes, sorry about that. I wanted to keep dev on one side and general question/comments on the other one. I guess that's not such a good idea.
scholbert said:
Which GAPPS did you integrate?
There'd been similar reports that properly working ICS GAPPS are very hard to find...
Click to expand...
Click to collapse
It was just a quick experiment to validate wifi as browser doesn't work. I grabbed them from Cyanogen repositories if I remember well.
scholbert said:
Agreed, this is a know fact on the A101... fix could done in ICS itself i guess.
Click to expand...
Click to collapse
Well, it's worse than that, I don't have sensors dll in the build, so no rotation.
scholbert said:
Some things mentioned here, might rely on kernel i guess and as you said wifi is working... i guess this again refers to 2.6.29 sources, correct?
Click to expand...
Click to collapse
Yes, untouched from Archos 2.6.29. Nothing changed on .29 kernel, just grabbed the right wpa_supplicant and fixed some permissions/directories issues. I didn't touch anything on the .29 kernel, only added the touchscreen patch that you also have on .35.
scholbert said:
It seems there'd been some additions in audio framework in one of the last patches provided by archos
Click to expand...
Click to collapse
Well, raw ICS build doesn't bring audio support, we have to write or grab proper dll to supports it. I believe both kernels are probably equally good. It may be also codec issue as they're probably not working with what I did, I don't know yet.
scholbert said:
Maybe these patches could be integrated in your ICS 2.6.35 kernel branch as well. Still need to fiddle around with the original sources and git, to get more information about the state of this project in general.
Click to expand...
Click to collapse
Yes, maybe, I'll try a merge someday.
scholbert said:
I'm sorry if i mix things up myself, but in fact i'd like to find some "central theme" for ICS development on Gen8.
Should we stick with the 2.6.29 kernel first?
Click to expand...
Click to collapse
Currently I'm not decided, I try to play with both as we may get updated drivers from Archos with the new it2 honeycomb, and they'll integrate easily with .35. However wifi is an issue with .35, not sure proper firmware+source code are available.
Cheers,
LeTama
letama said:
Yes, sorry about that. I wanted to keep dev on one side and general question/comments on the other one. I guess that's not such a good ide.
Click to expand...
Click to collapse
No problem with this intent, but i just tried to sort things out.
Hopefully this thread will gain more intense discussion
letama said:
It was just a quick experiment to validate wifi as browser doesn't work. I grabbed them from Cyanogen repositories if I remember well.
Click to expand...
Click to collapse
So did you check internet connection with it?
letama said:
Well, it's worse than that, I don't have sensors dll in the build, so no rotation.
Click to expand...
Click to collapse
Do we need sensor at first
I'm not that familiar with surfaceflinger, but it seems that the patch from divx118 looks like a default setup for rotation.
So this piece of code might suit into ICS sources as well.
letama said:
Yes, untouched from Archos 2.6.29. Nothing changed on .29 kernel, just grabbed the right wpa_supplicant and fixed some permissions/directories issues. I didn't touch anything on the .29 kernel, only added the touchscreen patch that you also have on .35.
Click to expand...
Click to collapse
O.K. i see.
BTW how does the wifi firmware get loaded on the Gen9 devices?
I realized some wireless framework for the Ti chipset in the 2.6.35 kernel and i wonder if this could be used for gen8 as well.
Anyway, i'll try to find some matching Ti sources for wifi.
letama said:
Well, raw ICS build doesn't bring audio support, we have to write or grab proper dll to supports it. I believe both kernels are probably equally good. It may be also codec issue as they're probably not working with what I did, I don't know yet.
Click to expand...
Click to collapse
Time will bring it to us i guess, there are only a few OMAP3 devices running on ICS right now.
There's also some stuff for beagleboard XM, but i guess there's not much useful stuff in there.
EDIT:
Concerning sound issue... maybe this is worth a try...
https://github.com/kfazz/android_hardware_alsa_sound
EDIT2:
For sound related libs...
http://code.google.com/p/cm-milestone2/downloads/list
I know the codec used on the milestones is different, but AFAIK the higher level libs use the DSP inside OMAP and might fit.
Milestone 2 uses OMAP3630 as well, have to check the kernel versions though.
letama said:
Yes, maybe, I'll try a merge someday.
Click to expand...
Click to collapse
I will do as well... need some days to get a proper overview though.
Maybe i'll prepare some patches to be ready for git merge.
Time is always lacking for such things
letama said:
Currently I'm not decided, I try to play with both as we may get updated drivers from Archos with the new it2 honeycomb, and they'll integrate easily with .35. However wifi is an issue with .35, not sure proper firmware+source code are available.
Click to expand...
Click to collapse
Yeah, maybe we should simply wait until the sources are on repo.
Does Archos already sell those devices?
I know there are more questions, than answers again, but maybe someday i may give more useful contribution.
Have a nice day!
scholbert
scholbert said:
So did you check internet connection with it?
Click to expand...
Click to collapse
Yes, it seems working fine.
scholbert said:
Do we need sensor at first
I'm not that familiar with surfaceflinger, but it seems that the patch from divx118 looks like a default setup for rotation.
So this piece of code might suit into ICS sources as well.
Click to expand...
Click to collapse
I thought he was referring to the fact that the screen didn't switch from portrait to landscape, that's why I mentionned sensors. Reading from divx118 patch, it seems that A101 "default" orientation has to be offset ?
scholbert said:
BTW how does the wifi firmware get loaded on the Gen9 devices?
I realized some wireless framework for the Ti chipset in the 2.6.35 kernel and i wonder if this could be used for gen8 as well.
Anyway, i'll try to find some matching Ti sources for wifi.
Click to expand...
Click to collapse
It's similar to gen8, wlan_loader then specific wpa_supplicant. There is a good chance that Gingerbread driver works, it should against a .35 kernel too. I'll try today if work let me a bit of free time.
scholbert said:
Time will bring it to us i guess, there are only a few OMAP3 devices running on ICS right now.
Click to expand...
Click to collapse
Yes... We'll see. It would be nice to have a manufacturer officially releasing it, we will be able to grab sgx drivers with hw composer. Afaik, there is none so far.
Thanks for the audio pointers, I'll take a look!
scholbert said:
Does Archos already sell those devices?
Click to expand...
Click to collapse
Situation is not clear yet. They are selling a70it2 already, but with froyo. It's not 100% confirmed that these devices are the same than the ones that will be honeycomb, but I'd bet they are.
Hi letama,
thanks for your reply.
Just in short...
I really recommend to look at the latest Gen9 kernel sources.
After stepping through the "huge" diff between these sources and your git kernel tree, i'm pretty sure that most things got included within this release.
Seems that they worked hard to integrate the OMAP3 as well.
Maybe this is because they plan to release the A70S V2 soon.
So what i did is only this...
- copy the board-archos-a70s.c (the original was still lacking quite everything)
- copy the hid-hanvon.c (ICS tweaks for touch)
AFAIK Archos did also a lot of changes in the SGX driver code.
I think it would just require some tiny tweaks to make it work with P970 libs.
Maybe there're only a few defines missing in the SGX part to get it working, but i guess that's really it.
EDIT:
Some header files are still missing in latest source as well.
So i've added them too...
- mnemedefs.h
- sgx531defs.h
- sgx535defs.h
- sgx543_v1.164defs.h
- sgx543defs.h
I'll try your archos_gen8_defconfig to compile with these latest sources.
If it does fine maybe would worth a try on your A70S.
So in fact i believe we will get a useful 2.6.35 kernel for the Gen8 soon.
The kernel already seems to be in a good shape...
Maybe we just have to sit and drink a few beers
Please tell me what you think, if you'll find soem time!
Best regards,
scholbert
Related
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
ddewbofh said:
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
Click to expand...
Click to collapse
Indeed agree, but to try we need to have it!
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
alx5962 said:
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
Click to expand...
Click to collapse
Your thread is excellent but I'd guess that this thread would be more oriented towards "hand-holding", really basic guides. Your topic was very broad requiring going to the android developers site and reading their docs on cross-compilation. Gathering that info into easier guides could be beneficial, if not to demystify the process.
As it stands right now just compiling modules seems almost insurmountable. But if the information needed could be condensed into simple guides it could show that while it takes considerable time and effort it's not an impossible task even for developers not familiar with cross-compiling kernels.
And information information on setting up cross-compilers for Win, Mac and popular Linux distros is nice to have available in an easy to find topic anyway.
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
maxrfon said:
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Click to expand...
Click to collapse
Sources are here :
http://developer.sonyericsson.com/cws/download/1/823/877/1278570405/X10_mini_Donut_100630.tar.gz
Rest can be done in same way as for "big" X10.
alx5962 said:
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
Click to expand...
Click to collapse
Do you have such virtual box image or whatever it is?
maxrfon said:
Do you have such virtual box image or whatever it is?
Click to expand...
Click to collapse
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
alx5962 said:
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
Click to expand...
Click to collapse
Yes, french for me is a bit difficult
Ok i managed to make Ubuntu on my Parallels, just finished with the gcc. Let's see how it works.
Maybe i will share it.
kernel config is included in the /etc folder if I remember well, hope it's the same for the mini X10
It's actually in /proc
zdzihu said:
It's actually in /proc
Click to expand...
Click to collapse
Hi zdzihu,
I managed somehow install arm gcc on my Ubuntu. Now it's time for the tools.
So i would like to ask what config should i use arm v4? V5?
I am so tired with this linux things, but finally at least the demo busybox compiled well
So i tried to compile with arm-v5te config but for flash read (which is normaly working) it says
Code:
# ./dump_image system /sdcard/tt.bin
error reading system: Inappropriate ioctl for device
My task it not to run flash tools available, but my own, to compile all myself, to try to do the trick with the CPU to accept kernel, that i compiled.
Thanks.
The Snapdragon is armv7 compliant, so that should be your target.
ddewbofh said:
The Snapdragon is armv7 compliant, so that should be your target.
Click to expand...
Click to collapse
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
maxrfon said:
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
Click to expand...
Click to collapse
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
ddewbofh said:
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
Click to expand...
Click to collapse
Looks like there is no other tut to build the toolchain. I searched days and nights to find something working.
I even compiled bysybox with it and it works on my x10!
But i found some sources of flash backup, called nandtools, compiled them well, no errors but the exec files are 4x bigger than the precompiled ones... And it makes the IOControl error..
the NDK won't compile, it requires Makefile or Android.mk and those are real headache to learn.
The Makefile from the archive is not compatible with NDK's make system and so on...
And so 2 weeks..
Pufff.. I am so tired if just linux things
Any hand?
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
zdzihu said:
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
Click to expand...
Click to collapse
You see, i need to compile mine, i have enough tools here already working, but my task is to compile my own and that's why i need a toolchain.
NDK is ok for the kernel, i compiled it already. But the native applications are not supported fully. Like write is deprecated and you can't use this function, and lot other limitations. So independent toolchain would help.
That's the point.
maxrfon said:
So independent toolchain would help.
Click to expand...
Click to collapse
PM sent =)
It has been released on June the 26th!
It can be found at this url.
That information seems to be quite good.
From what I understand, binaries from NVidia contain 2.6.38 kernel with Tegra 2 drivers.
Does anyone here knows if this has any chance of working on Folio 100 ?
Could this kernel be usefull for HC releases ?
Thanks !
It cannot be used as is. Btw I'll give it a try just to experiment.
I downloaded also all the source code from nvidia and'ill try to compile it adding some drivers to handle the touchscreen.
Hey thanks roglio, that's a good source of information. I will give it a try as well, but probably not in these few weeks
Im very interested in using this. I dont have any experiance with making my own rom tho, so i have to go and try to find some recources on that first. If you guy's has a link for me ill be very gratefull
Sent from my Folio 100 using XDA Premium App
Moved to proper forum.
shidima_101 said:
If you guy's has a link for me ill be very gratefull
Click to expand...
Click to collapse
Nvm, after some proper reading on my part, it seems that there is a document there that will help you get it up and running...
After a quick read of the supplied doc's, it seems to me that this is more or less the same way to get linux working as was posted previously. They make an ubuntu disk image and flash a kernel and boot files to load the image from a sdcard. The only diffrence here is that you have "official" drivers for the board.
Yes, you're right and consider that is nvidia in person to release this material.
Maybe we will get ubuntu before honeycomb in the meantime that google release ice cream (with source code).
shidima_101 said:
After a quick read of the supplied doc's, it seems to me that this is more or less the same way to get linux working as was posted previously. They make an ubuntu disk image and flash a kernel and boot files to load the image from a sdcard. The only diffrence here is that you have "official" drivers for the board.
Click to expand...
Click to collapse
Atm I'm very busy at the damn work and I can't get the time to try. But be sure I'll spend each minute of the upcoming weekend to work on it!!!!
roglio said:
Yes, you're right and consider that is nvidia in person to release this material.
Maybe we will get ubuntu before honeycomb in the meantime that google release ice cream (with source code).
Click to expand...
Click to collapse
I'm more interested in getting arch up and running than ubuntu
xitrumch said:
I'm more interested in getting arch up and running than ubuntu
Click to expand...
Click to collapse
To get arch running you need to get a file system image similar to the Ubuntu one that nVidia is suggesting. You also need a Arch arm kernel. If I don't forget ill try to look into it
[edit]
Ok, after a quick search I found an Arch arm site and on the forum they have a guide on installing on an ac100, that as far as i know is the folio 100 with a keyboard. (Right?)
http://archlinuxarm.org/forum/viewtopic.php?f=27&t=1626&sid=72ac121c87b9c825454207acde727e67
[/edit]
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
arent they located in /system/bin?
Need root first though
(I would help out with this, but dont really know how to do it, and i dont have the player yet)
zaclimon said:
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
Click to expand...
Click to collapse
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Dyskmaster said:
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Click to expand...
Click to collapse
Well maybe because people don't know how to do it. And as for the current rom the major problem is the hardware acceleration and the camera. Maybe We can find it (The binairies) at opensource.samsung.com
It should be easier than phones because you don't have to worry about not screwing with voice, data, and stuff like that. Just get it on and get all the apps working correctly. Radios are always the hardest.
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
sodomywar said:
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
Click to expand...
Click to collapse
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that? I found the gpu drivers from the opensource. Check in the kernel folder. If I can give you the gpu file if you want. Well tell me what files you are missing i'll find to give it to you. (Well I don't know how to program so I try do to my best.)
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
http://forum.cyanogenmod.com/topic/38960-build-your-own-cm9ics-preview-on-ubuntu-and-perhaps-debian/
Galaxy S Phone
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
zaclimon said:
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that?
Click to expand...
Click to collapse
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
zaclimon said:
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
Click to expand...
Click to collapse
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
sodomywar said:
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
Click to expand...
Click to collapse
how many MB or GB the source has because I can't exceed my download's limitations?
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
EDIT2: nevermind I'll be using ubuntu
alltellmobile said:
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
Click to expand...
Click to collapse
I don't know if we can (we should ask permissions) but it's definitly possible.
zaclimon said:
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
Click to expand...
Click to collapse
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
alltellmobile said:
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
Click to expand...
Click to collapse
You can help I follow the tutorials there:
http://www.freeyourandroid.com/guide/compile-ics
http://marakana.com/forums/android/general/269.html
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
alltellmobile said:
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
Click to expand...
Click to collapse
Oh that's true well you can try to port a custom recovery?
zaclimon said:
Oh that's true well you can try to port a custom recovery?
Click to expand...
Click to collapse
HaHa I'm not that good. that sounds way more complicated
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
jdale38 said:
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
Click to expand...
Click to collapse
Yes they are supposed to be there. But I have download all the source code of the firmware from opensource.samsung.com
Me and sodomywar are working with the internationnal version of the SGP4. If you want to join you're welcome.
EDIT: No problem for the tutorials.
alltellmobile said:
HaHa I'm not that good. that sounds way more complicated
Click to expand...
Click to collapse
Google is your friend
So this is where i'm at currently. I'm trying to compile and I got this error:
Code:
build/core/base_rules.mk:166: *** system/extras/ext4_utils: MODULE.TARGET.EXECUTABLES.setup_fs already defined by device/samsung/galaxyplayer. Stop.
Does anyone know how to remove that error?
EDIT: nvm I managed to remove this error.
Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m
Hi,
Just wondering if/when MadCatz will release the kernel?
I know linux being GPL, it has to be shared, but not sure about Nvidia's sources?
I'm new to android but not java(my day job) and linux.
I've compiled and installed my own kernels on desktop and on my mobile phone (Nokia N900).
I want to try and add a few things.. ie filesystem/DVB/webcam support etc.
Following this how to.
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Sweet! many thanks :victory:
:highfive:
:good:
omg.... does this mean we can finally have a cifs module!? AWESOME!
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
RollingRoman said:
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
Click to expand...
Click to collapse
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
PHYSC-1 said:
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
Click to expand...
Click to collapse
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
gwaldo said:
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
Click to expand...
Click to collapse
I would do that but i only have a panasonic 50" plasma it's a 600hz 1080p it p50x50b model,there are 2 variants of it a hd ready and a 1080p model,i know it's the 1080p model as i used blu ray and xbox 360 and a wiiu etc in 1080p modes so it's definately not 720p only on my model.
I still think it is possible to reinstate that hdmi resolution slider though? I would love for someone to find a fix for that to bring back the slider though.
It also has nothing to do with the overscan as that's off,and the guy said it's an argument between the console's os and the tv,but maybe if i had an option to change resolution within the console when in operation it would ammend this,resolution changer pro works then looses usability eventually and it's awkward and time consuming to get that to work,only for it to stop after a time?
There is no forced hdmi resolution setting in the tv menu unless of course there is in engineer mode but all that seems to do when entered is show test and it's results coming up as ok,after testing it factory resets the tv as well so sick of trying that now.
Someone needs to get a custom rom made up with kitkat and 1080p natively set.
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Unable to untar the tar.gz file. It says "tar: kernel/drivers/net/wireless/bcm43341/src/include/proto/p2p.h: Cannot open: Not a directory" and there are many lines like this. Tried everything from sudo, sudo -s, chmod, chown....
Also it says cannot mkdir: is not a directory
Its a .h and .c files ofcourse they aren't directories! Its not letting me execute make without errors since my source is like crap crawling with this "NOT A DIRECTORY"
Nothing is working. Command used was tar xvfz mojo-jb-kernel.tar.gz with many combinations and OS is Ubuntu 12.04 LTS 64 bit...
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Kingshoo said:
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Click to expand...
Click to collapse
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
It doesn't time out but it says some .c and .h cannot open: Not a directory when I use tar to extract it. Then I thought that I should install something else to extract and tried ARC. It extracted and then the same message box as appeared in windows 7 OS "file already exists cancel or overwrite"
I then said overwrite and then I get the extracted package. I just want to ask you that when you extracted it did you got any errors? What procedure you used to extract it? I downloaded twice with same results...
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
OK as per your suggestion I used wget c and the address. That gave me again the same file and upon extracting it I am getting same errors.
May be that the file isn't corrupted as you can extract it and its possible that I am doing something wrong in extraction..
I tried to create the kernel from sources and got a make error, to remove that I must delete a line in the make file (Line no 603) and after that I can successfully compile the zimage. But the issue is that after completing the procedure for boot.img file the original and compiled one has a difference of 0.1 MB and device don't boot with the newly compiled boot.img
Please if you can provide me with the steps on how you exctracted it and which OS you are using?then it will be really helpful. Also can you please upload the makefile of kernel and config.gz file you are using to make the kernel...
One useful information that can prove that there is an issue in extraction:
Extracted content on windows OS with Administrator priviledges: 42889 items , 487.8 MB
Extracted content on Ubuntu with Tar and other utilities: 42692 items, 482.5 MB
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Kingshoo said:
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Click to expand...
Click to collapse
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
gwaldo said:
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
Click to expand...
Click to collapse
I have gone through with the links you provided already and I understand every bit of conversation. Yes I am new to kernel compiling but its reasonably understandable.
I respect your valuable answer no matter when you reply since you have a minute for me and don't worry about TimeZone differences as I am not in a great hurry, I just don't wish to waste time on errors for which I ain't responsible
OK I tried compiling modules for which I had to compile the kernel to get the module.symvar file and "THE MODULES WORK!" that too with the Default kernel Makefile and ofcourse my own module Makefile.
"You dont use their makefile you recreate it" this line you wrote.. What do you mean by that??
I mean were you talking about the kernel Makefile or our own module Makefile, Please clear me here? As far as I know the Kernel Makefile should be the same when only compiling the stock kernel as that is my purpose "JUST TO COMPILE THE STOCK KERNEL"...
My compiled kernel boots but just shows a black screen! I don't want to spoil your holidays sincerely but if some help I can get from you then I will be able to relieve me from this burden
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Kingshoo said:
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Click to expand...
Click to collapse
Glad you got it working.
Re the makefile, I think you have to run config first to check your systems compilers/linkers/etc which then creates the makefile.
:highfive:
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
is there any reason this is done via some random ftp server and not some place like github/bitbucket with better management? or heck even sourceforge would be an improvement.
is that account for developer outreach? are there any datasheets on the components used in the device? sony does a beta program for updates on their flagship devices have you considered doing something similar where people can grab images and help test updates? ever think about tossing the device trees up for aosp to help encourage a porting of 3rd party roms and spread the community?
the nook color and touchpad being hack and having Cyanogenmod and the like being ported to it drove sales up, i would imagine having a hackable android console that isnt some no name chinese brand would probably do decent. unfortunately now with android tv you guys have some serious competition on the horizon, its a matter of how you go from here and try to make the most of it so everyone already has your product and doesnt need another.
edit: i also see there is several updates yet only one kernel source... any chance of updated source?
@Mad Catz Rich
The new update (205-TS) has a new kernel build of May 2nd.
Any chance that can be put on the server?
from http://madcatz.com/mojo/en-ca/
Ready to Root
As any Android power-user knows, the best way to get the most out of your device is to root it. Root access opens up all sorts of options including adding custom keymapping capabilities and installing custom ROMs. Mad Catz provides a short step-by-step guide to rooting, and our tech support team is ready to help.
The best part – rooting won’t void your warranty.
Click to expand...
Click to collapse
Please help, tech support team!
We need custom ROMs!
make kernelversion
3.4.35