Related
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.
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
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
I've tried a lot of the available ROMs (including the new JB ones), but this combination is just awesome:
Firmware MediaPad ICS 4.0.3 HWMOD C232B005
[KERNEL][AOSP][ICS 4.0.3][09/12/12] Mediapad EX (Don't flash modules)
New Qualcomm JellyBean Driver / Libraries
lagfree Governor
Overclock to 1,67 GHz
I'm pretty sure that the new Qualcomm Drivers tip the scales. Overall this combination gives you a fully working and outstanding smooth mediapad.
Have fun and press the thanks button if this helped you.
h25p said:
I've tried a lot of the available ROMs (including the new JB ones), but this combination is just awesome:
Firmware MediaPad ICS 4.0.3 HWMOD C232B005
[KERNEL][AOSP][ICS 4.0.3][09/12/12] Mediapad EX (Don't flash modules)
New Qualcomm JellyBean Driver / Libraries
lagfree Governor
Overclock to 1,67 GHz
I'm pretty sure that the new Qualcomm Drivers tip the scales. Overall this combination gives you a fully working and outstanding smooth mediapad.
Have fun and press the thanks button if this helped you.
Click to expand...
Click to collapse
Amazing testing, I am now on after_silence's CM10. Would the JB drivers with the same adb commands work with his CM10? Only thing not really working is the wifi MAC thing on that rom.
I'm pretty sure that the cm10 Rom already contains the new drivers. I believe I've read that flashing these files won't work with cm based Roms (maybe look at thread where the driver download is located).
Gesendet von meinem LT18i mit Tapatalk 2
Normally I have no problem with ADB, but for some reason I am unable to push the system files for the JB Adreno Drivers. I've attached a screenshot of my command window, but basically it's saying the file doesn't exist or I don't have permissions. I tried moving the file to a drive that wasn't hosting my Win8 OS, and ran the command with the new local file location but I got the same error.
I also tried to use Root Explorer and ES File Explorer to simply copy the files, but Root Explorer causes a hot reboot, and ES FIle Explorer freezes the tablet completely.
I've rooted a ton of devices in my day including that P.O.S. Notion Ink Adam, but this Huawei tablet is turning out to be a whole different beast in and of itself.
Any ideas on what to do now?
EDIT/UPDATE: took out the " / " after local system folder in adb command and all is golden.
I highly advice against flashing the Jellybean Adreno libraries on a ICS flavored ROM!
I've tried it and now the screen remains black. ADB works fine still though, so I can restore things to the way they were.
Still... stay away from mixing Jellybean flavored stuff into ICS!
MrColdbird said:
I highly advice against flashing the Jellybean Adreno libraries on a ICS flavored ROM!
I've tried it and now the screen remains black. ADB works fine still though, so I can restore things to the way they were.
Still... stay away from mixing Jellybean flavored stuff into ICS!
Click to expand...
Click to collapse
Do you have flashed exactly the files contained in the linked zip using adb push? Don't push the complete set from the qualcomm site.
MrColdbird said:
I highly advice against flashing the Jellybean Adreno libraries on a ICS flavored ROM!
I've tried it and now the screen remains black. ADB works fine still though, so I can restore things to the way they were.
Still... stay away from mixing Jellybean flavored stuff into ICS!
Click to expand...
Click to collapse
No problems here. I'm getting butter smooth interactions, and a whopping 3062 in Quadrant. Also the lag over HDMI has gone away for me. I can now play games on my television with my sixaxis!
isolated_epidemic said:
No problems here. I'm getting butter smooth interactions, and a whopping 3062 in Quadrant. Also the lag over HDMI has gone away for me. I can now play games on my television with my sixaxis!
Click to expand...
Click to collapse
Which ROM are you using?
I'm using CM10 ,I flashed whole of them then reboot,after that it couldn't display anythings,so I must restored system back.
chok_thewa said:
Which ROM are you using?
I'm using CM10 ,I flashed whole of them then reboot,after that it couldn't display anythings,so I must restored system back.
Click to expand...
Click to collapse
h25p did say that very likely CM10 would already have the JB fixes, so perhaps the adb pushed driver is borking the one in CM10? If you are successful again I will try.
h25p said:
Do you have flashed exactly the files contained in the linked zip using adb push? Don't push the complete set from the qualcomm site.
Click to expand...
Click to collapse
Can i just flash this zip file directly from twrp? Currently im on HWMOD b005 rom with latest Bart kernel (r08) now. Thanks
Sent from my HUAWEI MediaPad using Tapatalk 2
joy_van_hallen said:
Can i just flash this zip file directly from twrp? Currently im on HWMOD b005 rom with latest Bart kernel (r08) now. Thanks
Click to expand...
Click to collapse
It didn't work for me, but you can try.
athanaso77 said:
It didn't work for me, but you can try.
Click to expand...
Click to collapse
is it possible to just copy the system folder using root explorer and change the permission?
Sent from my HUAWEI MediaPad using Tapatalk 2
zelduy said:
is it possible to just copy the system folder using root explorer and change the permission?
Sent from my HUAWEI MediaPad using Tapatalk 2
Click to expand...
Click to collapse
When I tried to do that with Root Explorer, it froze my tablet completely. And ES File Explorer (with root activated) caused my tablet to hot reboot every time I tried. ADB is going to be your only route I believe.
isolated_epidemic said:
ADB is going to be your only route I believe.
Click to expand...
Click to collapse
That's correct.
Ok.. but I'm quiet new in this adb thingie.. do I need driver for this? cause when I type adb devices / adb remount it said no devices found..
and yes.. I'm already in debug mode...
thanks
zelduy said:
Ok.. but I'm quiet new in this adb thingie.. do I need driver for this? cause when I type adb devices / adb remount it said no devices found..
and yes.. I'm already in debug mode...
thanks
Click to expand...
Click to collapse
Install HiSuite for the proper ADB drivers. It's one of the programs on the "Disc" drive that mounts when you plug the tablet into the computer.
the combination is awesome
but after i use this combination, I have no front camera. The problem is that image need it for Skype video chat.
can somebody tell me what's wrong?
thank you
you need to push the EX's modules
Sent from my HUAWEI MediaPad using Tapatalk 2
danisukses said:
you need to push the EX's modules
Sent from my HUAWEI MediaPad using Tapatalk 2
Click to expand...
Click to collapse
so for bootR08 we need the modules?
---------- Post added at 06:10 PM ---------- Previous post was at 05:33 PM ----------
Just flashed. will test out the combi. thanks
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