[Dev] ICS Kernel Source code is out! - Gen9 Android Development

Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release

so this is where the fun begins

letama said:
Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release
Click to expand...
Click to collapse
its ok
and i agree: let the fun (and headaches) begin

hi letama do you remember me? I'm a mobile programmer I don't know what's usually modded in a kernel used for custom firmwares, but if you need help or testing or need to check code, I can do that
let's rock!

does this mean proper custom roms are now possible as opposed to stock roms with busybox and superuser

letama said:
Hi All,
Devs, kernel and buildroot for ics is up on gitorious!
Let's the fun begin!
Cheers,
LeTama
*** edit ***
Oups, missed previous thread on the topic, sorry djnilse, my damn browser didn't refresh properly. Mods, you can remove the thread or I can keep if for any custom kernel release
Click to expand...
Click to collapse
HI!
Thank you very much Master !
Almost certainly will need your help....for release custom kernel ! Good luck professor !!!

philmein said:
does this mean proper custom roms are now possible as opposed to stock roms with busybox and superuser
Click to expand...
Click to collapse
No, it's not related. Custom roms were already possible without kernel source, I tried cm9 for instance.
The problem with Archos is that it's not really worth it. Custom to do what? Archos firmware is quite "stock", no bloat to remove, so aosp is quite similar and doesn't bring much.
CM9 is in major work, it's going to be interesting soon but it will require lot's of work to adapt it and make it as stable as stock firmware. It's not too difficult to get basic stuff when mixed with proprietary binaries.
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).

great letama !
many works now !

Great news! Now waiting for Ubuntu with the new kernel, WiFi and video hw fully employed. I'm a poor programmer myself but if there is a bug in the software I always run straight into it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(And they are always there, of course.) So I think there will be a lot of them to be found.

letama said:
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).
Click to expand...
Click to collapse
-develop a way to copy new modules to .ext4 system image (and make a backup
of this file to /mnt/storage)

letama said:
No, it's not related. Custom roms were already possible without kernel source, I tried cm9 for instance.
The problem with Archos is that it's not really worth it. Custom to do what? Archos firmware is quite "stock", no bloat to remove, so aosp is quite similar and doesn't bring much.
CM9 is in major work, it's going to be interesting soon but it will require lot's of work to adapt it and make it as stable as stock firmware. It's not too difficult to get basic stuff when mixed with proprietary binaries.
Kernel sources are interesting to:
- learn kernel stuff
- overclock / add governors
- add missing drivers (dvb cards, etc...)
- port to gen8 devices
- debug problems like wifi for instance (bad example, this one will be tough).
Click to expand...
Click to collapse
Archos' fw is quite "stock" but it's slower than other ICS firmwares...
I have a Transformer with ICS here, and it's definitely smoother (less lag) than my G9 101..
And it's not a CPU/GPU difference

faenil said:
Archos' fw is quite "stock" but it's slower than other ICS firmwares...
I have a Transformer with ICS here, and it's definitely smoother (less lag) than my G9 101..
And it's not a CPU/GPU difference
Click to expand...
Click to collapse
Agreed, but don't forget memory difference... I'm convinced that it kills omap4 perfs. I guess we'll see with the new turbo 1G.
Anyway, some news back on the subject, overclocking is very easy on this kernel to go from 1G -> 1.2 "standard way" with governors that can be handled by setcpu or other. It seems stable, didn't run extensive tests though.

letama said:
Agreed, but don't forget memory difference... I'm convinced that it kills omap4 perfs. I guess we'll see with the new turbo 1G.
Anyway, some news back on the subject, overclocking is very easy on this kernel to go from 1G -> 1.2 "standard way" with governors that can be handled by setcpu or other. It seems stable, didn't run extensive tests though.
Click to expand...
Click to collapse
yeah, the RAM...
good news about the overclock anyway

Related

[ROM][Gingerbread] 2.3.2 | Clean Android | AOSP | Joestone

ALL CREDITS GO TO JOESTONE
This is the AOSP of Joestone
He made a version of Gingerbread for our phone.
This version is clean, so no cyanogenmod, just Android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a topic where joestone writes daily updates about his project:
http://logout.hu/bejegyzes/joestone/joestone_gt540_2_3/friss.html
This on other forums:
Android Forum PL
4pda.ru Forum
If you have other links from forums, please post it!
What is working:
Wifi,
Audio
GSM , mms send and receive, automatic apn setup, mobilinternet
Bluetooth
Sensors
Camera
SD card
USB connection
Google market , gmail
GPS, aGPS
Root
APP2SD
FMradio
What is not working:
PCSUITE
Screen calibiration
Fixes in newest verison
DSP Manager is working
iptables and tuneling enabled in the kernel
the default cpu clock was changed to 600 MHz
the cardiotrainer app (and hopefully all others which gave maps error) works
Hopefully increased speed for wifi , hsdpa, umts
the kernel was updated by the lg's source released on 2011.04.12.
Click to expand...
Click to collapse
Some more screenshots of this version:
Download Link
Posted 05-22-11 so 22 May
For fastboot -> ginger....zip
For recovery -> recovery....zip
Video of first version: http://www.youtube.com/watch?v=cQNOJqLyuT0
_________________
For fastboot installation
Code:
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
This is a video of a earlier version so it is just for the impression. In the version in this topic is much more working http://www.youtube.com/watch?v=9z5u8d_Db6o
According to the benchmark results this ones a lot faster right?
Sent from my GT540 using XDA App
I haven't try a benchmark yet but I can tell you because it is still in development it's not totaly smooth.
Joost
Ok
Sent from my GT540 using XDA App
What kernel is this based on? My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel. If so, I'd hope we can port that kernel over to CM7.
themono said:
What kernel is this based on? My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel. If so, I'd hope we can port that kernel over to CM7.
Click to expand...
Click to collapse
As you can see on one of the screenshots, this is still kenrel 2.6.29. A few russian are making kernel 2.6.35 http://4pda.ru/forum/index.php?showtopic=215440
Joost
Cool, I'll try it when it has more functions working.
joostvhoek said:
As you can see on one of the screenshots, this is still kenrel 2.6.29. A few russian are making kernel 2.6.35 http://4pda.ru/forum/index.php?showtopic=215440
Joost
Click to expand...
Click to collapse
Thanks Joost. Looking forward to seeing the results of that Russian work.
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...
great job, just don't give up
fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...
Click to expand...
Click to collapse
We have got the east european guys!! WHahahahah (evil laughing)
Joost
I have added a youtube video in the startpost.
Joost
As soon as this is into the Beta stages I will use it, still in alpha stages at the moment am I correct? I want off of CM7 if I'm honest, I just love stock things.
keewanchoapsss said:
As soon as this is into the Beta stages I will use it, still in alpha stages at the moment am I correct? I want off of CM7 if I'm honest, I just love stock things.
Click to expand...
Click to collapse
I don't know in wich stage it is. I call it pre-beta... It is no more alpha because pretty much is working.
Joost
I will get this version as soon as more things are improved.I liked the CM7 version but the battery problem caused too much problems for me.I hope this version will get improved as soon as possible.
Keep up the good work!
I'll try it
Glad to know that enybody else try tot do something with our phone.
But I dont undrstand what is benefit of original android. But as alternative that cool to see a difference between stuf. Would be cool if someone third try to make a CAF version. I think it has a more perfomanse responsibilities and many impruvements.
Keep up the work, good luck.
fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540... I bought mine mid December 2010 with 1.6 installed and look at us now...
Click to expand...
Click to collapse
I think I got mine at about the same time too. Kudos to the developers of both versions of gingerbread.
fishears said:
How lucky are we?! Seriously, to have two projects working to bring Gingerbread to the GT540
Click to expand...
Click to collapse
Agree. Amazing really, especially considering how old the hardware is, not supporting flash, etc. At least with 2.3 we have some hope of using some of the newer apps.
themono said:
My hope is he's recompiling the (I think 2.6.35?) kernel native to Gingerbread, rather than the other ROM's which have been using a variation on the original LG 2.6.29 kernel
Click to expand...
Click to collapse
Good if its easy but just like compiling kernels on linux, newer kernels cause some big headaches with drivers. I'd rather have the older kernel and have it working correctly then wait for the newer kernel to function properly.
Anything in the newer kernel that we need/want?
First of all yes this is an advantage of having 2.3.1 aswell but its hard to put in words.
second can i ask when would it be updated to the latest 2.3.3 from aosp?
third i got the phone on 28 sept 2010 and on that day was my birthday and also on that day joestone released the rootgt540!
look at the progress of openetna and you will realise that we will get new kernels, just that we need to establish a fully working rom first.
what is CAF?

[MOD]viperMOD for AOSP Kernels - v3 beta RC2.4 |Updated 6.14.11|

Hey everyone, welcome to viperMOD for the EVO, Incredible, Nexus One, Desire GSM, Thunderbolt, Nexus S, Nexus S 4G, Desire HD, and Inspire 4G. Many people are having great success with this mod and I hope you enjoy my work
I would like to turn this into an app! If someone would like to help out that has Java knowledge, please contact me!
What does this do?
Kernel developers make their kernels to be "universal". By universal, they want the kernel to work on as many phones as possible so they may only mildly undervolt. However, some phones can handle a more aggressive undervolt. Some can't. viperMOD allows you to undervolt to your choosing for better battery life or allow you to overvolt to make your phone more stable.
How do I run this?
Once you flash the .zip go into your Terminal app (I use Android Terminal Emulator set to 10pt font) and type:
su
vipermod
I really only use Terminal for my mod and there is something really cool you can do with Android Terminal Emulator (and maybe others). Menu > Preferences > Initial Command > Press Enter and type su > Press Enter again and type vipermod
Every time you start Terminal now, it will open right into viperMOD. You can quickly exit by pressing Enter if you need to use Terminal for something else
UPDATE 6/14
viperMOD v3 beta RC2.4 is live!
Fixed some coding that was giving errors on certain ROMs and phones. Everyone please update to this!
Please see the updated FAQ and changelog for more information!
UPDATE 5/31
viperMOD v3 beta RC2.3 is live!
MUCH better support for NS/NS4G Netarchy kernels and other enhancements!
Please see the updated FAQ and changelog for more information!
UPDATE 5/29
viperMOD v3 beta RC2.2 is live!
Initial support for Desire HD/Inspire 4G and more!
Please see the updated FAQ and changelog for more information!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please see viperboy.tiamat-dev.com for downloads, more information, changelog, and FAQ!
You can find the answers to all of your questions there!​
Feel free to support this mod with a userbar in your sig
Credit to:
- snq_ for the VDD support
- Cayniarb for his awesome Tiamat kernel, hosting, and website!
- Netarchy for his amazing guidance and patience!
- My IRC friends ekarelis, bigrushdog, and morph3k for all their help!
- Ziggy for the adjustable sysfs interface
- Anyone who has done testing for me or helped me at all
- Everyone who contributes to Android development
- Let me know if I left anyone out!
FAQ
[Q] Will this work on Sense kernels?
[A] Technically, yes. None of the current Sense kernels support the sysfs interface but a few of ziggy's old kernels do. I don't know if anyone still runs his kernels but if you do and you want to see it supported, please contact me. You can also compile your own 2.6.32 Sense kernel and build in the sysfs interface. To do so, please read here (thanks chad0989!)
Reserved...
What kind of battery life are we looking at here? There's so many variables as to what affects life. I can chew through my 1500 in 24 hrs or 10, it depends.
I'll try it out, what kernel is this based off of?
shoman24v said:
What kind of battery life are we looking at here? There's so many variables as to what affects life. I can chew through my 1500 in 24 hrs or 10, it depends.
I'll try it out, what kernel is this based off of?
Click to expand...
Click to collapse
It's hard to say because, as you said, it depends what you do with your phone. I have noticed that I get a full day out of my phone when I never used to before. Just to give you an idea though, here is what ffolkes found out after some testing...
ffolkes said:
I spent hours (well, days, no, a week actually) methodically doing stability tests and tweaking voltages for all 24 frequencies. I then went back to a fresh install of CM7, installed Tiamat 3.3.7 and used my Evo for about 30 minutes - doing whatever I normally do, few texts, lots of RSS reading, browser, it isn't important since this is a relative and not absolute test. I then took 10 samples from that time in Battery Monitor Widget and averaged them, resulting in 485mA. Then I installed my customized voltages, and repeated the experiment, and the average was 374mA. That equates to about a 23% decrease in power consumption.
Click to expand...
Click to collapse
In my eyes, anything I can do to get a little bit more battery life is great and this mod will help with that
Is this.something that you would flash over the kernel or for devs to add in while they are creating them?
bradm23 said:
Is this.something that you would flash over the kernel or for devs to add in while they are creating them?
Click to expand...
Click to collapse
Flash over a kernel. Basically, it adds a script to /system/etc/init.d that loads these undervolt values everytime your phone starts up.
Interesting. I think I will keep an eye on this one!
Sent from my ADR6300 using XDA Premium App
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
dscribe said:
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
Click to expand...
Click to collapse
You just need a kernel with the HAVS sysfs interface is all. Would take about 5 minutes to put into a sense kernel. It will be in a future 2.6.37 sense kernel I put out if I ever figure out the funky artifacting issue.
dscribe said:
So, is it not possible to do make this mod available to sense ROM kernels, or just involves doing things no one has done yet?
Click to expand...
Click to collapse
chad0989 said:
You just need a kernel with the HAVS sysfs interface is all. Would take about 5 minutes to put into a sense kernel. It will be in a future 2.6.37 sense kernel I put out if I ever figure out the funky artifacting issue.
Click to expand...
Click to collapse
It could work with a Sense kernel, actually. I just didn't make one for the EVO because Calkulin already did that in his own thread. But I will get it working on Sense for the Incredible for you guys.
Looks like I need 5 Sense testers now!
-viperboy- said:
Looks like I need 5 Sense testers now!
Click to expand...
Click to collapse
I'll be happy to test it for ya.
dscribe said:
I'll be happy to test it for ya.
Click to expand...
Click to collapse
Sent you a PM. Still need a few more testers!
I was able to drop it 50mV going past that would booted but would hot-boot instead of booting all the way.
Still happy. Now to test how much more time I have on my battery
Thanks again viperboy.
cuban11182 said:
I was able to drop it 50mV going past that would booted but would hot-boot instead of booting all the way.
Still happy. Now to test how much more time I have on my battery
Thanks again viperboy.
Click to expand...
Click to collapse
No problem like I said, every phone will handle this mod differently. I don't know if this has happened to anyone in the Incredible forum but some people in the EVO forum have a problem that they can't flash any custom kernel because the kernel is too undervolted so I made an overvolt script that I will post over here as well.
Confused
Is this mod only involving the making of flashable scripts that lower voltage values?
Does it involve anything like modifying kernels, basically making them HAVS kernels, if they are not currently?
Who else wants to help me test?! I need people that are running a Sense-based ROM!
dccoh said:
Is this mod only involving the making of flashable scripts that lower voltage values?
Does it involve anything like modifying kernels, basically making them HAVS kernels, if they are not currently?
Click to expand...
Click to collapse
No, the kernel you are using needs to have on-the-fly HAVS editing built in.
-viperboy- said:
It could work with a Sense kernel, actually. I just didn't make one for the EVO because Calkulin already did that in his own thread. But I will get it working on Sense for the Incredible for you guys.
Looks like I need 5 Sense testers now!
Click to expand...
Click to collapse
-viperboy- said:
No, the kernel you are using needs to have on-the-fly HAVS editing built in.
Click to expand...
Click to collapse
Which no sense kernels do, with the exception of some of the ziggy ones floating around somewhere. I've long since abandoned my 2.6.32 source in favor of 2.6.37 (I only have time for one at a time), but there is an odd artifacting issue that has prevented me from releasing a sense version.
If someone wants to put out a 2.6.32 sense kernel with the sysfs interface here's everything you need:
My 2.6.32 source:
https://github.com/Chad0989/incredikernel
Sysfs interface commit:
https://github.com/Chad0989/android_kernel_common/commit/15d469a1aabc76d549c94bc7150678fe808a51d8
Note that 2.6.32 its acpuclock-scorpion.c instead of acpuclock-qsd8x50.c
I can test sense for you if you would like

[ROM] CM7.1-final, Deodexed, 2.6.35 kernel

Putting this up for those who've been inquiring...I simply integrated bits & pieces for the legend to improve what is already an awesome rom. I take no credit for this. Doesn't hurt to hit the thanks button though if this helps .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How's this different from CM7?
2.6.35 kernel (boots by default to 768/256-interactive; max=806, min=120)
smartass & smartass2 governors
compache/swap
deodexed & zip-aligned
tweaks for deodexed rom and sd read-ahead (3072 by default)
removed rom manager & some default themes/wallpapers
moved file manager to /data/app
modified lock screen icons
flying-in menu animations
TGF's notification bar (notbar) patch integrated
What doesn't work/untested?
wifi tethering - activating them produces an error & breaks wife, in which case, a reboot is required
gps
Is this faster than CM?
can't claim that as i don't see a big jump in quad/linpack scores, though there are improvements & it does feel snappier (I may be biased though). you decide...
full rom here: DOWNLOAD
flash attached:
drowningkernel-8-9-1_mod1.zip
kernel w/ the last three items above included for flashing unto cm7
drowningkernel-8-9-1_mod.zip
just the kernel
CAUTION
do backup before doing anything
see alex' comments, post #9
if you encounter reboots/freeze (not getting this myself though) & wanna revert to your original/stock kernel, simply advance restore boot only
usual liability disclaimer applies
feedback is/are most welcome! if you have questions on TGF's notbar patch, please post on that thread instead.
CREDITS
cyanogen/cm team
alex
drowningchild (kernel)
tosha15 (compatible modules)
TGF
Serris (animations)
ZduneX25 (lockscreen icons)
Thx maxq1, I'll download but will test it only after I get my Legend repaired
Rapier said:
Thx maxq1, I'll download but will test it only after I get my Legend repaired
Click to expand...
Click to collapse
I think this time you took the big hammer and hit it hard
good work man, going to check this out........
smartsreenath said:
I think this time you took the big hammer and hit it hard ..
Click to expand...
Click to collapse
Yeah digitizer is defective...it seems like it happens this after a while (1 year or so). I saw alot of people complaining about this also movies on YouTube showing the issue. I'l send it in service next week I hope
The drowningkernel-8-9-1_mod.zip works fine with CM7.1.0 for me. THX a lot!
I like your lockscreen-icons and the statusbar-patch, but not the flying-in-animation, so I flashed the non-modified one.
What governors do you prefer? I'm using interactive, but never had a smartass/smartass2 kernel on my phone. Does one of these two give me advantages over interactive?
Or can you give me some details about smartass/smartass2 Min-Max-values for the legend?
I have constant cpu usage of 50-75% with this rom :-(
What governors do you prefer? I'm using interactive, but never had a smartass/smartass2 kernel on my phone. Does one of these two give me advantages over interactive?
Or can you give me some details about smartass/smartass2 Min-Max-values for the legend?
Click to expand...
Click to collapse
you could learn more about it here. i'm using 806/122-smartass2. if you try to underclock below stock 245, it seems only the smartass governors give a quick response from sleep.
Suppe123 said:
I have constant cpu usage of 50-75% with this rom :-(
Click to expand...
Click to collapse
which governor are you using?
Just a small comment regarding kernel 2.6.35:
In my tests 2.6.35 was not significantly (or at all) faster than .32, neither could I observe improved battery life.
What actually held us back implementing .35 were the crappy WLAN and missing access point drivers. The sources HTC released are significantly broken - even for their original target "Espresso", and this is still a clear violation of the GPL (the sources they used to compile tiwlan_drv for Espresso/Legend are not at all equivalent to what they released).
That being said, if you don't care about WLAN at all you can use 2.6.35. I seriously wouldn't recommend that kernel though and would request you to add a warning to your post to make sure people don't start to complain about random reboots in CyanogenMod.
Thanks man,looks great will test it soon.
Sent from my HTC Legend using XDA App
File does not exist!
Sent from my HTC Legend using XDA App
if you deodex rom ... take data space after install ... cm 7 179mb free data ... your rom ... ... less
Bad bad bad...
^ i couldn't quite get what you're saying, man. did it drop down to <100mb?!? i'm no expert or dev but is that an effect of deodexing? if any, i just moved file mananger (a couple of kb, i guess). in any case, most of you will be using some sort of apps/data..2..sd/ext anyway. kindly enlighten...
File does not exist!
Click to expand...
Click to collapse
hmm..link works just fine from where i'm at..try again, bro
Sesme said:
if you deodex rom ... take data space after install ... cm 7 179mb free data ... your rom ... ... less
Bad bad bad...
Click to expand...
Click to collapse
Hey E.T, you drunk bro' ?
Okay,now it's working I think Megaupload was just down....Okay I test it now
Sent from my HTC Legend using XDA App
So bad that Wifi is crashing all the time
stevenstrike said:
So bad that Wifi is crashing all the time
Click to expand...
Click to collapse
update your radio!!!
maxq1 said:
^ i couldn't quite get what you're saying, man. did it drop down to <100mb?!? i'm no expert or dev but is that an effect of deodexing? if any, i just moved file mananger (a couple of kb, i guess). in any case, most of you will be using some sort of apps/data..2..sd/ext anyway. kindly enlighten...
Click to expand...
Click to collapse
What he wants to say is that, if you deodex rom, there is more space used in system since instead of having apk+odex as separate files you put the odex inside the apk thus ocuppying more space. So for a deodexed ROM you have less space remaining.
Of course since most of us are using some sort of data2ext this is no big deal, I just wanted to "translate"
Sesme said:
update your radio!!!
Click to expand...
Click to collapse
Huh ? This is a known issue caused by crappy Wifi drivers given by htc for Kernel .35 :
Just a small comment regarding kernel 2.6.35:
In my tests 2.6.35 was not significantly (or at all) faster than .32, neither could I observe improved battery life.
What actually held us back implementing .35 were the crappy WLAN and missing access point drivers. The sources HTC released are significantly broken - even for their original target "Espresso", and this is still a clear violation of the GPL (the sources they used to compile tiwlan_drv for Espresso/Legend are not at all equivalent to what they released).
That being said, if you don't care about WLAN at all you can use 2.6.35. I seriously wouldn't recommend that kernel though and would request you to add a warning to your post to make sure people don't start to complain about random reboots in CyanogenMod.
Click to expand...
Click to collapse
BTW Radio has nothing to do with wifi.
Edit : Plus my radio is up to date !
Edit Plus : I tried this rom (K.35) and official 7.1 Rom (K.32) and i found that the both kernels have the same issue, being on K32 or K35 is the same thing for me, i got the same random crashes, which was not the same thing on the old RC1 (which just sometimes crashes when you just power on wifi with sync enabled).
Too bad, Cyanogen 7.1 passed "stable" with this bug.
^ have you tried this, bro?

[ROM] Plasma Active for SDE enabled Gen9

Hello Guys,
Here is a plasma active build:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't expect much support on this, for me it seems unusable as it is, too slow and not finished. I just wanted to take a look at the way they boot from sdcard.
Installation:
1) You need SDE activated.
2) Unzip files to a directory
3) Copy plasma_rootfs.img to root of storage
4) Flash kernel+initramfs.gz in recovery (details with pictures there).
5) Boot sde
6) Wait, wait, wait! First boot is very slow, I didn't even try a second boot
Download is there (big file, 447 MB)
Thanks to cajl for pointing this and pushing me working on it.
Looks great !
Thank you for your excellent work ! I will try your ROM later....
Yet Another Stupid Question
Does this work also on hdd models?
tapatalked from Desire
BTW, someone promised a KDE-based buid as the usual SDE 'firmware' for gen9. Probably on behalf of Archos itself... Two months ago. Still there are no more signs of progress...
Not allowed to post links here yet, look at dot.kde.org
PLEASE READ:
I talked to a developer working for Archos, the Plasma Active based firmware is going to be the official SDE firmware!
But they're not working on it at the moment, they're trying to get ICS firmware out asap!
ALSO NOTE THAT:
the current plasma active image has no wifi (this is what I was told, haven't tried it yet) and that XORG is not HW Accelerated! The developer who made the Plasma Active based image is waiting for the kernel v3 to be released together with ICS firmware, hoping that a new kernel will fix the issues with WiFi and Hw acceleration.
Thank you, faenil - any piece of information is useful... but why so many capital letters?
faenil said:
I talked to a developer working for Archos, the Plasma Active based firmware is going to be the official SDE firmware!
But they're not working on it at the moment, they're trying to get ICS firmware out asap!
Click to expand...
Click to collapse
Quite reasonable approach for a vendor. No more questions. At least, it is a very good sign that the vendor does not go blindly within the entire Google-driven mainstream but has a broader insight and does try the alternatives. A bad thing IMHO is that the heaviest desktop environment is selected, the least appropriate for XDAs. Yet some people really like it...
the current plasma active image has no wifi (this is what I was told, haven't tried it yet) and that XORG is not HW Accelerated! The developer who made the Plasma Active based image is waiting for the kernel v3 to be released together with ICS firmware, hoping that a new kernel will fix the issues with WiFi and Hw acceleration.
Click to expand...
Click to collapse
well, without wifi it it a pretty useless toy... hw acceleration is less critical for me (but not for others, I think).
On the other hand, once Archos is officially involved into this project, why couldn't they use the existing 2.6.x kernel? It does work within the Android, hence, there are all necessary modules and kernel options being known, written and placed properly. Excuse my ignorance, what is the problem in building the kernel with all the hw features for a particular device yet without Android-specific sw components? Or what is the problem in running a generic Linux userspace on top of it?
Hi gen_scheisskopf,
gen_scheisskopf said:
Yet Another Stupid Question
Does this work also on hdd models?
Click to expand...
Click to collapse
No, still the same issue, I didn't make any progress on this. Sorry :-(
See this information from Basyscom
« Hi Jean-Luc ,
unfortunately we’ll have to wait a bit as the developer edition is required to install plasma edition. Archos wants to publish the developer edition after icecream sandwich being released.
Regards,
Eva »
But letama is faster .....
iourine said:
On the other hand, once Archos is officially involved into this project, why couldn't they use the existing 2.6.x kernel? It does work within the Android, hence, there are all necessary modules and kernel options being known, written and placed properly. Excuse my ignorance, what is the problem in building the kernel with all the hw features for a particular device yet without Android-specific sw components? Or what is the problem in running a generic Linux userspace on top of it?
Click to expand...
Click to collapse
The problem is the guy who's currently building PlasmaActive images is not from Archos the guy from Basyscom http://basyskom.com/news/78-plasma-active-on-archos.html
I don't know if there's any agreement, but I think they'll probably use his work and add the missing features at Archos
Hello letama, nice work here!
Do you have WiFi working in this image?
a1Pha said:
Hello letama, nice work here!
Do you have WiFi working in this image?
Click to expand...
Click to collapse
Thanks, but didn't do much... No, I don't think this build has wifi support yet. They are working on it though.
News?
Hello @ all...
i will test the rom from the first post later today on my Archos G9 101!
The last post was on 8th february, what´s up... is there a developing or not? Because i´m very interessted in this rom for my Archos!
Do anybody knows something about a ubuntu-rom for our Archos G9???
Thank you!
Echse27
Well, I didn't check their progress on it. I'm not really following it, I just did it more as a proof of concept and to get a taste of it. I saw that few builds have been compiled after this one, but I'm out of time to repackage it.
Echse27 said:
Hello @ all...
i will test the rom from the first post later today on my Archos G9 101!
The last post was on 8th february, what´s up... is there a developing or not? Because i´m very interessted in this rom for my Archos!
Do anybody knows something about a ubuntu-rom for our Archos G9???
Thank you!
Echse27
Click to expand...
Click to collapse
as I said earlier, this firmware is actively developed by Basyskom and should become the official firmware for SDE, but they're waiting for Archos to release ICS (with the new v3 linux kernel) hoping that the new kernel will fix the problems with WiFi and hw acceleration
o.k. thank you both!
I hope the offical ICS Build will be released soon.
I think the Archos G9 tab will be more potential with an full useable unix-system.
I´m looking forward to that! ;-)
Echse27 said:
o.k. thank you both!
I hope the offical ICS Build will be released soon.
I think the Archos G9 tab will be more potential with an full useable unix-system.
Click to expand...
Click to collapse
Well, quite logical and reasonable roadmap. But I do not expect much from KDE-based software. Out of all existing desktop environments, they selected the heaviest one, the least suitable for portables. Surely this is just to have fun and see if it can reallу fly (better to say, crawl) on a tablet. It is very unikely to be a viable product for everyday use.
Ubuntu version looks more promising, at least from performance viewpoint... if only it were not its destructive "innovations" like Unity and Ubuntu One...
Anyways, both have the same problems with hardware support, and both are waiting for the new kernel, first... Second, both will prove their inconsistence in the real life... Third, both will serve only as generic Linux booting platform, waiting for someone to compile a more realistic version. Probably it might be a Gentoo-based compilation with LXDE or XFCE - am I the only person in the world to whom this idea comes? 8-(( Sabayon team is now doing some moves in this direction, but their product is very heavy even for desktops...
iourine said:
Ubuntu version looks more promising, at least from performance viewpoint... if only it were not its destructive "innovations" like Unity and Ubuntu One...
Click to expand...
Click to collapse
Personally I'd love to see Xubuntu (or Lubuntu) running
iourine said:
Well, quite logical and reasonable roadmap. But I do not expect much from KDE-based software. Out of all existing desktop environments, they selected the heaviest one, the least suitable for portables. Surely this is just to have fun and see if it can reallу fly (better to say, crawl) on a tablet. It is very unikely to be a viable product for everyday use.
Click to expand...
Click to collapse
I have used Plasma Active on my Nokia N950 (developer phone, which has a 1ghz single core CortexA8 cpu + SGX530!!) and it was really fluid, I mean 60fps...
don't see your point about performance, given what I've seen on my n950
I tested this ROM yesterday evening...
I think you are right, when you say that there ist a lot of development need before it runs smooth on our devices!
It was very very slow but it looks very goog, i think.
No WLAN or 3G
some funktions are without any funktion! ;-)
realy slow... Booting tooks 15 min.
At this time, this rom isn´t allday useable.
Do anybody know something about a ubuntu-release for tabs like our.... like the old netbook-remix?
Any news about new Plasma-based firmware from Archos? A lot of time has passed since release of kernel v3.x...

[KERNEL]HydraCoreNirvana n16[ENDED]

Although this kernel is ended. I think I should put the downloads here:
http://sourceforge.net/projects/maxfuacm/files/Kernel/HydraNirvana/GT-N7000/
Critical Remind:
Flashing this kernel will make your phone Lose Warranty. So please Fully Get Understand of what you are doing. I have no responsibility of any of your lose by flashing this.
Before you download and flash, to farthest avoid bootloop or bricking your phone, please make sure you have read and understand sections from 4 to end.
Please be wisely use the "search this thread" at the top right corner, if you can not see it, click
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there. And be sure you have already read the OP. New-asked-but-already-answered questions will be ignored and maybe disliked or even scoffed by other members.
I will never talk about ETAs (Estimated Time of Arrival). So please save your keyboard or touchscreen.
Please forgive me if I did not answer your question, even you asked before some one I answered. Please informe with message if you need me to answer it. Although I can not guarantee I will answer questions promptly, the carefulness of the answers is guaranteed. If the answer is important to you, please bookmark it cause I may edit the answer post with update instead of posting another one.
And if anyone don't like any part of my word. Please send me a message instead of posting here. All words above are my begging for the nattiness of this thread. I won't open another thread of discussion, cause I saw the discussion theads were mostly useless. Holding one thread is easier.
Thanks to:
@g.lewarne, @hardcore, @chandler929, @Formhault, @androidindian, @noteandfound, @chasmodo, @TeamHacksung, @samsung, @CyanogenMod team, ......,
and a lot of names to add.
Brief:
First, I would like to thank the people I mentioned and not mentioned in section 2. Notably g.lewarne, you are always the owner of HydraCore. Thank you for your great work. Galaxy Note now became a legend with your masterpiece.
Secondly, I would like to thank all people who gave me support, encourage and advise. Under your help, HydraCore has became a really universal and almost perfect kernel.
In this new thread, the legendary Universal Kernel has a new name -- HydraCoreNirvana. I think the word Nirvana can tell the story of HydraCore. With the new name, the kernel steped onto a new stage -- bootable on JB leaks. It is not fully functional, but it is a good beginning.
I have to say that I am not a dev. And I am another Child's Slave who use lavatory time as off hours. I really don’t know how far I can go on this. So please, forgive me if someday I got stuck and be absent like Gavin.
......long after n6......
For a long time I kept absent. I really found it hard to go on especially after the CM team upgraded the Mali driver. I am not the right guy to do the library job. So I switched to Samsung Opensource codes.
The first thing I did was building the Speedmod. I succussed. Meanwhile I made a build with Speedmod kernel image and PhilZ touch recovery initramfs. These builds worked fine with new released TouchWiz Jelly Beans. However, the CM code is going away with the Samsung Opensource codes. There are too many differences between them. The HOME button key issue was one result of this. It is harder and harder to combine CM and TouchWiz in one kernel. It is not just an universal initramfs, the kernel image itself needs to be universalized.
So I have to make a lamentable decision that from now on, I will stick with Samsung Opensource codes. So TouchWiz Jelly Beans will be supported prior to CM and other AOSP roms which have good enough kernels. Legacy features of HydraCore will be transplanted to the new builds one by one with careful test. CM and other AOSP roms maybe bootable with the new builds, but the functionality will not be guaranteed.
At last, thank you all for your long time support. I will keep on building this kernel and try my best to keep it Hydra for everyone. But for now, I can only step on one side, and I choose TouchWiz.
......more to add......
Technical Description:
Safety: mem_cap_erase disabled, so this is a safe kernel.
ROM Support:
ICS (4.0.X):
TouchWiz Based: TouchWiz ICS fully supported. Official MIUI still can not boot to system, adb works.
AOSP Based: CM9 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.1.X):
TouchWiz Based: TouchWiz JB, MIUI made by TWJB + Patchrom from http://www.miui.com/extra.php?mod=download/rom&fid=133 fully supported.
AOSP Based: CM10 fully supported, AOKP and some PA......, and maybe other untested roms.
JB (4.2.X):
TouchWiz Based: Not out even leaked yet
AOSP Based: CM10.1 has bootloop with display.
Recovery: CWM 6 non touch recovery from @Phil3759: http://forum.xda-developers.com/showthread.php?t=1927097.
Root privilege: ADB and LBE superuser.
Usage:
Place the ZIP in the TF card.
Root the phone: If you and if you are sure that you have a safe kernel with CWM jume to next. If you phone is unrooted, Flash the TAR version in Odin to get Root and CWM.
Now you may meet bootloop, Press UP + HOME + POWER until you see the CWM interface. (the phone will never boot to the system with a stock rom flashed a TAR version)
Flash the ZIP in CWM.
Enjoy
Please don't ask me how to use CWM. If you don't know, don't flash any kernel.
Download with Changelog:
Instructions:
These are SourceForge folders, so open in a browser. The corresponding source is included in the same folder.
Not all releases will be kept in this post, find the old ones in the repository. I will keep all files as long as possible. (It seems SourceForge don't delete old files.)
Little trick: maybe you can try middle-click the links, a new tab maybe opened.
Notice: If you met black screen or bootloop after flashing the tar file. Try the zip package (The recovery should be working). The standalong Mali libraries might fix the problem.
n16:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n16/
Changelog:
Kernel: Pushed kernel version to 3.0.83.
Defconfig: Reverted pmem settings to fix video overlap. The bug is reported fixed.
Defconfig: Reenabled Samsung MTP. The hang of the MTP software on my MIUI v5 TouchWiz Patchrom fixed.
Makefile: Brought more legacy HydraCore tweaks including cpu and fpu tweaks.
n15:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n15/
Changelog:
Kernel: Pushed kernel version to 3.0.82.
Network: Fixed wifi tethering.
Audio: Fixed mic in software like talking animals, recoders, etc.
Mali: Tweaked thresholds to reduce lag on some heavy interface like MIUI desktop. Further tweaks may be needed.
Tweaks: Some small tweaks.
Platform: Switched to coLinux. Now it is ideal for me. It is a real linux like vmware, it uses less resource like cygwin, and it is fast like a directly installed linux.
Toolchain: Switched back to Linaro 4.7 with LTO.
n14:
Download: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n14/
Changelog:
Kernel: Pushed kernel version to 3.0.81 with cma port.
Superuser: Switched to LBE superuser with some simple permission management.
Defconfig: Brought more legacy HydraCore options which may be not noticeable.
HydraFS: Some workaround to MIUI. Now official MIUI v4 can boot to adb, positive. But the system is still not usable.
Platform: Switched to cygwin.
Toolchain: Switched to cygwin 4.6.3.
Filename: Yes, X.Y.Fu is still me, it is my name in short.
test builds:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Testbuild/
These builds are test builds. They usually contains new features or fixes. These changes need test. Read the README file in folders for more information.
build environment:
Link: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Platform/
Just follow the readme file.
TODO and TOFIX:
Add Multi-ROM-on-SdCard support.
Investigate the reason of the CM10 and CM10.1 failure boot.
Make MIUI v4 bootable. Fix CM boot problems.
AOSP MIUI JB support.
Bring back more HydraCore features.
Bring ability to set GPU frequency. This is extremely hard to me.
Bring ability to set CPU voltages. Found the location of the settings. Working on it.
Bring more ability to alter the kernel without reflash.
Tweak all the script included.
Study on offcial source code of JB.
64GB cards. I am not sure. 64GB exceeds Fat32 limitation. and exfat is not supported correctly.
Vibration Strength not alterable on AOSP roms. I am still working on this, maybe compile two different modules will solve the problem.
Q&A Collection:
How to flash: like I said if you don't know how to flash, then don't flash. Or you can read section 4.
Can I flash on ...?: Please get to know you rom type, AOSP or TouchWiz based, then please read section 4.
Bootloop/Freeze/..., help!: please be concrete, I can not answer questions simple like this.
Possible reasons of Black Screen: From n9, standalong Mali libraries are located in the zip. Try to use the zip package. It might fix the problem.
Possible reasons of Bootloop:
Please check your rom type see whether your rom is supported.
Another reason is the unsuppored modules. Look in to /system/lib/modules if it exist. And delete dhd.ko, j4fs.ko, scsi_wait_scan.ko and Si4709_driver.ko if they exist. Deleting dhd.ko may also fix WIFI problem.
Possible reasons of Lag: Check the governor and IO settings. Or maybe just clean the RAM. At last, reboot.
Possible reasons of Freeze: Usually happens after a heavy load work. Try to reboot. Reboot usually works.
...adding...and...collecting...
Old Versions:
n13: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n13/
n12: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n12/
n11: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n11/
n10: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n10/
n9: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n9/
n8: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n8/
n7.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n7.JBT/
n6.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n6.JBT/
n5.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n5.JBT/
n4.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n4.JBT/
n3.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/n3.JBT/
n2.JBT: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/6th_v7.6.JBT/
n1: https://sourceforge.net/projects/maxfuacm/files/GT-N7000/HydraNirvana/Release/5th_v7.6.2/
Great maxfu. You have a lot to say and we'd love to listen
Sent from my GT-N7000 using Tapatalk 2
Finally...
ANG.MAHAL.NG.NOTE.KO
maxfu said:
My sixth compilation with experimental TWJB leak support:
https://sourceforge.net/projects/maxfuacm/files/Galaxy Note/MaxFu_HydraCore/v7.6.JBT.1/
Click to expand...
Click to collapse
Seriously? We can finally OC the jb leaks? AWESOME!!!
I guess cm10.1 kernel is next?
ANG.MAHAL.NG.NOTE.KO
It's fantastic, thanks man.
Thanks man a new life for our great Hydracore..............
Another awesome release from Maxfu
thanks man.
Will it really work on JB Leaks ???
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Immortal Nerd said:
M waiting for ur reply ..... ill it really work on JB leaks ??? ( especially latest Ultimate Rom )
Click to expand...
Click to collapse
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Haints said:
Seriously? We can finally OC the jb leaks? AWESOME!!!
Click to expand...
Click to collapse
Yes, you will have OC. But camera maybe gone.
maxfu said:
I build this JB support with Ultimate XXLSA, should be OK with XXLSC. But please be in mind that it is experimental. AFAIK the camera service has problem.
Click to expand...
Click to collapse
Is there any critical problems in the sixth compilation for leaked jb? If not, I well flash this right away
Edit : so the camera is break in the latest kernel? Hmm alright I think I will wait for the next compilation really great work maxfu, thank you for make the hydra core can run in leaked JB :good:
XXLSC Wait,.,
Sent from my GT-N7000 using xda premium
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Should be. But not on CM 10.1
cuba462 said:
Is video camera, 1080 works for with cm10 rom?
Escaped from cuban Asylum. Cell 462
Click to expand...
Click to collapse
Hi maxfu. The original HydraCore 7 is unsupported by the awesome jellybam. This would be?
Sent from my GT-N7000 using xda premium
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
download it again ?
capu81 said:
MaxFu_HydraCore_v7.6.2_OC.zip is corrupted
Click to expand...
Click to collapse
Have you already checked md5?
ANG.MAHAL.NG.NOTE.KO
noteandfound said:
Have you already checked md5?
Click to expand...
Click to collapse
Oh, yeah, sure, no doubt...

Categories

Resources