Related
Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
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
Welcome One X+ users, this is the SickKernel. What you can expect over time is more and more features.
Changelog:
Code:
11-20-12
Removed userspace govenor
set ondemand govenor default
used newer toolchain
Directions to flash
Code:
Go to fastboot, from android type adb reboot bootloader
download the image
cd to your downloads folder
issue the following command
fastboot flash boot sickkernel-0_0_1.img
Source ->
Bugreports go
Note,
If WiFi doesn't work let me know about it. I am trying a new method of kernel packaging which may backfire. If this happens, there is an easy fix. Enjoy! Also I don't own the device. I have some testers, but if a kernel doesn't boot I have no way of knowing sometimes. Don't be afraid to tell me issues
MOD Edit: Removed DL-Links as OP isn't xda-member anymore
I'd recommend you saying that this is for the Int'l model and not the AT&T model.
Well, it won't cause bricks to flash it wrongly. Besides no one knows if the devices have a definitive difference that prevents it from booting. On a side note, this currently uploaded boot.img has the ramdisk of a cm10 ROM. There for it will bootloop sense
Sent from my PK7630000 using Tapatalk 2
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
n3ocort3x said:
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
Click to expand...
Click to collapse
a totally different base yes not phone, lots of bricks trying to flash international HOX+ software
Look up my kernel release, I think I pretty much nailed down module embedding. There's a total filesize limit it seems on the boot.img but it works.
I can release the framework I'm using, all scripted out to 2 simple commands if you want.
Hi sir could you add call recorder feature into your kernel in such a way we can record calls with the Bluetooth audio ear phone connected....hopefully this can help you
http://forum.xda-developers.com/showthread.php?t=1971302
Just a hope sir
Rgrds
I think you should specify on the top of the OP that this is not for ATT. Hopefully they will split forums for the HOX+ development and add a seperate ATT forum, but until then there will be plenty of havoc over all of these dev threads that are not specific on which device they are for.
Dont mean to bust balls, but Noobs are noobs.
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
simonsimons34 said:
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
Click to expand...
Click to collapse
Simple edit to help solve a simple misunderstanding. Your thread, your rules, though.
Hi, how about sweep 2 Wake?
Sent from my GT-N8000 using Tapatalk 2
Thread closed
As the OP had a wrong assumption about the consequences of breaking xda rules, and preferred to withdraw from xda subsequently, I closed this thread.
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
This is only to be used if you know what you are doing. This enables Unsigned Kernel Modules on the SCH-i545 (NC5/NK1), and the i337 (NC1).
Flash downloaded zip in Recovery.
https://www.androidfilehost.com/?fid=95916177934548235
Package of Modules built by @Surge1223:
https://www.dropbox.com/s/mpyeju0082c6f9m/modules.zip?dl=0
NOTE: Many of these are useful, but don't just load them for fun, they can be dangerous. Also, some do not function as expected, i.e. fastchg.ko has no effect, this is known, but I use that module in specific to test if modload is functioning.
Usage:
-- ALL of these commands must be run as root ("SU' in terminal/ADB Shell)
-- Run "Modload" to enable unsigned modules
-- Run "insmod /path/to/module.ko" to load a specific module
-- Run "rmmod modulename.ko"
-- Run "lsmod" to view a list of currently loaded kernel modules
-- Run "Modload -r" to re-enable kernel module signature checks
Credits:
This is completely based off of @jeboo's original BypassLKM exploit on MK2.
The whole script is kanged from @Surge1223 's update of the BypassKLM exploit to NC5.
@tulth found the memory address to overwrite to re-enable this exploit on NK1.
I just packaged it into Surge's ModLoad script.
Screenshot of usage:
http://imgur.com/Yk9uq6e
This allows kernel to be setup on non unlocked bootloader correct? If so that's pretty neat. I have mdk just was wondering.
And so it begins!
bryantjopplin said:
This allows kernel to be setup on non unlocked bootloader correct? If so that's pretty neat. I have mdk just was wondering.
Click to expand...
Click to collapse
Only kernel modules.
Sent from my SCH-I545 using XDA Free mobile app
Great to see the fight still rages on!!
jeboo said:
Great to see the fight still rages on!!
Click to expand...
Click to collapse
Haha. Good to see you around [emoji14] If you want to join the telegram group chat we have going about Kexec/the boot loader, just let me know, you are more than welcome.
I've been doing some research on this as of late (basically by tweaking the stock kernel and testing different gov's, turning off MP-Decison, etc) Now I want to learn more of what these unsigned modules are about. I have 2 questions. First is can we use other modules outside of the ones Surge compiled? (Like load in the smartassv2 gov or insert and overclock and voltage crtl) Second is for basic understanding can we get a description for each of the modules included in the package?
Thank you @npjohnson and @Surge1223 for your continued work on the VZW s4. I like so many are eagerly checking the thread for updates on the bootloader unlock!
wavedashdoc said:
I've been doing some research on this as of late (basically by tweaking the stock kernel and testing different gov's, turning off MP-Decison, etc) Now I want to learn more of what these unsigned modules are about. I have 2 questions. First is can we use other modules outside of the ones Surge compiled? (Like load in the smartassv2 gov or insert and overclock and voltage crtl) Second is for basic understanding can we get a description for each of the modules included in the package?
Thank you @npjohnson and @Surge1223 for your continued work on the VZW s4. I like so many are eagerly checking the thread for updates on the bootloader unlock!
Click to expand...
Click to collapse
A kernel module can execute code at the kernel level. I.e. make SMC Calls, and device hardware calls, and a lot more.
Any valid (signed or not) kernel module will attempt to load, but obviously fail if it isn't written correctly.
As for the modules in the zip, several are test modules, and some do not work correct, I haven't tested them all. The QuickCHG.KO one does not work for example. Feel free to test and report which ones work.
About 5 pages back in the boot loader thread, surge released over/under clocking modules (don't use if you aren't sure of what you are doing!). I would not recommend including these in a ROM (the over clocking ones), as the basic user will likely wayyy over clock and bad things will ensue.
Building a basic Linux kernel module is a complex process, as in most cases, you have to compile the module along with a kernel meant for your device. (Use NC5 source). If you need any help, I can put you i n touch with some helpful sources on building Kernel Modules.
I doubt a governor would come in the form of a module... But you could probably find a way to set the governor using a governor module and a ROM to enable governors. Also, don't load modules made for other devices/other kernels, as we mist remember, this is still the TW kernel.
npjohnson said:
A kernel module can execute code at the kernel level. I.e. make SMC Calls, and device hardware calls, and a lot more.
Any valid (signed or not) kernel module will attempt to load, but obviously fail if it isn't written correctly.
As for the modules in the zip, several are test modules, and some do not work correct, I haven't tested them all. The QuickCHG.KO one does not work for example. Feel free to test and report which ones work.
About 5 pages back in the boot loader thread, surge released over/under clocking modules (don't use if you aren't sure of what you are doing!). I would not recommend including these in a ROM (the over clocking ones), as the basic user will likely wayyy over clock and bad things will ensue.
Building a basic Linux kernel module is a complex process, as in most cases, you have to compile the module along with a kernel meant for your device. (Use NC5 source). If you need any help, I can put you i n touch with some helpful sources on building Kernel Modules.
I doubt a governor would come in the form of a module... But you could probably find a way to set the governor using a governor module and a ROM to enable governors. Also, don't load modules made for other devices/other kernels, as we mist remember, this is still the TW kernel.
Click to expand...
Click to collapse
I've had the conservative governor working for quite some time.
Has increased my battery life slightly but noticeable.
Do the modules that surge released also support u/v and o/v as well? or do you know?
I have tried building the kernel modules with nc5 source but haven't been able to get past a few errors but I do plan to get back to it sometime.
Do you mind pm'ing the sources you are speaking of? or post them here whichever you prefer
Thanks.
klabit87 said:
I've had the conservative governor working for quite some time.
Has increased my battery life slightly but noticeable.
Do the modules that surge released also support u/v and o/v as well? or do you know?
I have tried building the kernel modules with nc5 source but haven't been able to get past a few errors but I do plan to get back to it sometime.
Do you mind pm'ing the sources you are speaking of? or post them here whichever you prefer
Thanks.
Click to expand...
Click to collapse
Which source? The NC5 kernel is what I was talking about. Then you can kang Linux modules for just about everything else. Other than the governors, this have to be specific to our device.
npjohnson said:
Which source? The NC5 kernel is what I was talking about. Then you can kang Linux modules for just about everything else. Other than the governors, this have to be specific to our device.
Click to expand...
Click to collapse
I mean the sources for building kernels.
I know where to get nc5 from.
I want to try to import other governors eventually once I get past my errors.
klabit87 said:
I mean the sources for building kernels.
I know where to get nc5 from.
I want to try to import other governors eventually once I get past my errors.
Click to expand...
Click to collapse
Well, I could describe it to you, but I'd butcher how to setup a kernel build env. @tulth could describe it much better.
To build a kernel module, you have to build them with the kernel. Honestly though the readme for the NC5 kernel describes the process fairly well.
I can walk you through general kernel building, but each one requires different tools/toolchains.
npjohnson said:
Well, I could describe it to you, but I'd butcher how to setup a kernel build env. @tulth could describe it much better.
To build a kernel module, you have to build them with the kernel. Honestly though the readme for the NC5 kernel describes the process fairly well.
I can walk you through general kernel building, but each one requires different tools/toolchains.
Click to expand...
Click to collapse
Oh ok. I thought you might have a few reliable threads/guides that I may not have seen yet.
I have the environment and toolchains setup I just have some errors that keep getting in the way so it never compiles.
I may take some time this weekend to setup my system as a dualboot again.
Been quite a while since I've done it.
Any particular problems with building anything android on the latest ubuntu?
I would like to use the latest LTS 64 bit
klabit87 said:
Oh ok. I thought you might have a few reliable threads/guides that I may not have seen yet.
I have the environment and toolchains setup I just have some errors that keep getting in the way so it never compiles.
I may take some time this weekend to setup my system as a dualboot again.
Been quite a while since I've done it.
Any particular problems with building anything android on the latest ubuntu?
I would like to use the latest LTS 64 bit
Click to expand...
Click to collapse
Stick with 14.04, and a quick note, dont go installing the newest java, because you have to have jdk 7, and at least on my end, it kept resetting default to jdk 8.
Tl:dr: don't deal with 14.10. God its a pain.
If you want to PM me the errors, I might be able to help.
npjohnson said:
Stick with 14.04, and a quick note, dont go installing the newest java, because you have to have jdk 7, and at least on my end, it kept resetting default to jdk 8.
Tl:dr: don't deal with 14.10. God its a pain.
If you want to PM me the errors, I might be able to help.
Click to expand...
Click to collapse
Thanks for the tip.
I have everything setup in a vmachine but I recall you saying a while back that you never had any luck building with a vmachine
so I'm gonna dual boot for now.
I saved a screenshot of the errors so I will find it and pm you when I can.
thanks.
Sorry if this is off topic, but with loading custom modules couldn't you in a way make NC5/NK1 compatible with AOSP Roms? Just build what they need?
uplusion23 said:
Sorry if this is off topic, but with loading custom modules couldn't you in a way make NC5/NK1 compatible with AOSP Roms? Just build what they need?
Click to expand...
Click to collapse
Its called KitPop (its in the Dev section) [emoji14] MTP and WiFi softboot are the only bugs. Got WiFi AP to work.