Database Develop

3.0 Kernel for AOSP JB?

I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least

TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....

There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app

I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app

TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?

Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app

CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.

ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?

The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s

CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.

ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?

markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.

Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?

The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.

The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.

TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:

zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!

markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed

[Dev] [JB/ICS] OC Engine for 2.6.39 Kernel

I got time today a little while to observe OC possibility, and attempted. I was in hurry and these days I dont much have time these days so I've not tested what I've writtten, but theoretically it should work without issues:
OC Engine For LG Optimus 2x For 2.6.39.x Kernel
*It's written for 1.2Ghz but it's easy to ramp up to 1.4/1.5 by observing codes.
Devs feel free to use ,
and rippers dont rip codes to represent it as yours.
Download
*See attached patch file

Wow thank you so much.....will have a look at it right away......

spica1234 said:
I got time today a little while to observe OC possibility, and attempted. I was in hurry and these days I dont much have time these days so I've not tested what I've writtten, but theoretically it should work without issues:
OC Engine For LG Optimus 2x For 2.6.39.x Kernel
*It's written for 1.2Ghz but it's easy to ramp up to 1.4/1.5 by observing codes.
Devs feel free to use ,
and rippers dont rip codes to represent it as yours.
Download
*See attached patch file
Click to expand...
Click to collapse
this is another OC/UV patch
http://forum.xda-developers.com/showthread.php?t=1971350 (Please see attachments)
based on the "Overclocking the Toshiba AC100" work by gordan
- http://www.altechnative.net/2011/12/31/overclocking-the-toshiba-ac100/
and the TF101 OC by ibladesi
- https://github.com/ibladesi/TF101-HighOC-3P1
it works nicely with my SU660
harsh already applied simplified version of this OC/UV patch on his kernel
https://github.com/bhanvadia/lge-kernel-star/commit/ed65546739d458454f0c4d14902d970626046e06
https://github.com/bhanvadia/lge-kernel-star/commit/31cd7ea99b962386ba12e36fc99e3ac9dc858def
it needs two fixes
- https://github.com/bhanvadia/lge-kernel-star/commit/604d675b84aaa905a675109e52b4becebded9cff
- https://github.com/bhanvadia/lge-kernel-star/commit/4ade8a95ed07aa5ac08d1923f48192f91ced8d68

Thanks wkpark for all these references. I logged in xda after many days, I wasnt aware about yours and harsh's attempt about oc. Anyways but I am happy, about your references and yours and harsh's work . Actually your 2 refrences posted last are useful that's neccessory for oc, I made a long route instead as I din't get much time to observe other files.
Thank you anyways
Sent from my LG-P990 using xda app-developers app

Welcome back buddy.....
Old is gold.....have seen the two old buddies come back when there sadness with one good one gone....
But life is like that......good and bad
O2X with Magical ROM and supersonic kernels from my buddies

whank u spica any one compile a OC kernel all ready?

Take your time, but those can't wait, all of us in fact, must try Topogigis rom
Sent from the new smoothly LGP990

Thanks Spica
Subscribed :laugh:

CarloIT said:
Thanks Spica
Subscribed :laugh:
Click to expand...
Click to collapse
I logged in after many days and found wkpark has already made oc available in easy more effective ways and more robustly it has been written
Users are usually don't aware about the real heroes and those such persons are wkpark, harsh etc who has given very much contributions for lg optimus 2x.
So thanks deserving persons are wkpark and harsh as well that users must know
"Share, learn and enjoy" that's the key to OpenSource
Sent from my LG-P990 using xda app-developers app

wkpark said:
this is another OC/UV patch
http://forum.xda-developers.com/showthread.php?t=1971350 (Please see attachments)
based on the "Overclocking the Toshiba AC100" work by gordan
- http://www.altechnative.net/2011/12/31/overclocking-the-toshiba-ac100/
and the TF101 OC by ibladesi
- https://github.com/ibladesi/TF101-HighOC-3P1
it works nicely with my SU660
harsh already applied simplified version of this OC/UV patch on his kernel
https://github.com/bhanvadia/lge-kernel-star/commit/ed65546739d458454f0c4d14902d970626046e06
https://github.com/bhanvadia/lge-kernel-star/commit/31cd7ea99b962386ba12e36fc99e3ac9dc858def
it needs two fixes
- https://github.com/bhanvadia/lge-kernel-star/commit/604d675b84aaa905a675109e52b4becebded9cff
- https://github.com/bhanvadia/lge-kernel-star/commit/4ade8a95ed07aa5ac08d1923f48192f91ced8d68
Click to expand...
Click to collapse
can u build one version for p990!

anjo88 said:
can u build one version for p990!
Click to expand...
Click to collapse
commit in my github is for P990 itself.
But as Topo said, OC is flaky currently. Anything more than 1.2 GHz make phone hang. Need to find where did NVIDIA implemented code for making CPU stuck as half frequency if its OCed.

Harsh said:
commit in my github is for P990 itself.
But as Topo said, OC is flaky currently. Anything more than 1.2 GHz make phone hang. Need to find where did NVIDIA implemented code for making CPU stuck as half frequency if its OCed.
Click to expand...
Click to collapse
great can u share it so that people can test! i have all msot shure that audio bug is boatloader related so if some on can compile a cm10 from RC and apply the new bootloader for testing will be great!
Anda I'm saying that because 28e/g cm10 old bootloader call problems v228/e/g new bootloader at 10 not a sigle call problem!

anjo88 said:
great can u share it so that people can test! i have all msot shure that audio bug is boatloader related so if some on can compile a cm10 from RC and apply the new bootloader for testing will be great!
Anda I'm saying that because 28e/g cm10 old bootloader call problems v228/e/g new bootloader at 10 not a sigle call problem!
Click to expand...
Click to collapse
bootloadr is not related with audio bug... and that will never be.
official leaked ics roms doesn't have audio bugs just because they are official p990 roms with the official p990 kernel from lg, i remind you that cm10 is using su660 kernel source, a not completely but strongly enough different phone.

pidocchio said:
official leaked ics roms doesn't have audio bugs just because they are official p990 roms with the official p990 kernel from lg, i remind you that cm10 is using su660 kernel source, a not completely but strongly enough different phone.
Click to expand...
Click to collapse
If you read a bit more, you'll find out that the original P990 ICS leak with untouched kernel is also suffering from the same bug. Nothing to do with CM10 or SU660...
Sent from my LG-P990 using xda app-developers app

pidocchio said:
bootloadr is not related with audio bug... and that will never be.
official leaked ics roms doesn't have audio bugs just because they are official p990 roms with the official p990 kernel from lg, i remind you that cm10 is using su660 kernel source, a not completely but strongly enough different phone.
Click to expand...
Click to collapse
If you read a bit more, you'll find out that the original P990 ICS leak with untouched kernel is also suffering from the same bug. Nothing to do with CM10 or SU660...
Click to expand...
Click to collapse
I think that the new bootloader and related thing have better compatibility with ics then the old gb bootloader, for sure..
I'm using the leaked ics from the beginning and i don't have a single call bug

Buccio said:
I think that the new bootloader and related thing have better compatibility with ics then the old gb bootloader, for sure..
I'm using the leaked ics from the beginning and i don't have a single call bug
Click to expand...
Click to collapse
why dont adapt cm10 with new bootloader and then we know wheter the in call audio bug is still present or not....sorry for oot

godh3ll said:
why dont adapt cm10 with new bootloader and then we know wheter the in call audio bug is still present or not....sorry for oot
Click to expand...
Click to collapse
Agree, someone with kind heart and capable should build cm10 with new bootloader/layout partition.

aldyu said:
Agree, someone with kind heart and capable should build cm10 with new bootloader/layout partition.
Click to expand...
Click to collapse
+11111

godh3ll said:
why dont adapt cm10 with new bootloader and then we know wheter the in call audio bug is still present or not....sorry for oot
Click to expand...
Click to collapse
I know audio bug is really an annoying bug.
I don't know whether audio bug is related to boot loader or not.
And about boot loader, I won't say its impossible w/o sources but we don't have boot loader sources, neither sources of old nor new:/
Sent from my LG-P990 using xda app-developers app

don't care about OC on JB, need ramhack...CM10 have tiny free ram

JB4.3 for p970

This topic is for other developers, not for users who are eagerly waiting for something that may never come
I know that upstream p970 development has stopped. However, I still find it a challenge to get JB4.3 running on the p970. Main reasons is that on the Samsung Galaxy Tab 10.1 (which has also been discontinued by CM-team due to the outdated tegra2 chipset) CM10.2 actually seems to run smoother than CM10.1 (possibly due to the code cleaning from JB4.2 -> JB4.3).
I have started by adding some missing variable to BoardConfig.mk and enabling SELinux in kernel, but already bumped into some compiling issues. Are there any others working on this, or interested in helping?!

Not going into technical part but I have heard and strongly believe that new version means not really a high-end hardware only. According to my knowledge KLP will run smoothly on a device having 512mb of RAM.

and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable

recl said:
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
Click to expand...
Click to collapse
????
JB is build based on pure android code from google. So that is the source code necessary...

Honestly,if I could choose from android 4.3 and android 5.0, I'll prefer to wait for android 5.0! Android 5.0 is designed to ensure the performance on old and low-end devices !
I am looking forward for developers to port android 5.0 into our device!!!

I'm willing to help in testing so ring me up anytime!
Sent from my LG-P970 using Tapatalk 4

kasper_h said:
This topic is for other developers, not for users who are eagerly waiting for something that may never come
Click to expand...
Click to collapse
What this mean for you guys?

It is booting already!
only running into some stagefright issues so the display isnt turning on, but i already get access to the logcat to debug.
our target is getting closer and closer

Nice job

Discussion Tread for Cyanogenmod 11 (Android 4.4.x KitKat)/ Cyanogenmod 10.2(jb)

Hello everyone, Like everyones know Galaxy mini (s5570) received kitkat/Jelly Bean(cyanogenmod 11/10.2[unofficial]) , since samsung stopped supporting this device devs've started a hard work to update this device.
All AndroidArmv6 Team specially @erikcas , @yajnab , @psyke83 (remember if i forget you and sorry)
and at the moment we're getting stable rom of kitkat and already stable jellybean
Kitkat 4.4.x:
Whats Working ??
everything
what is wrong on this rom ?
batery drains too faster this problems contains in many others kk ROMs including devices . ask google to fix .. xd
Jelly Bean 4.3.x:
Whats working ??
everything
Whats wrong on this rom ?
only small things
the rom was in alpha stage, but already is stable, some people using it daily.
At the moment Jelly beam 4.3 was a amazing rom for daily, lastest's releases from jenkins are incredible.
where i can find more info ?
- you can search for yajnab Tread in Original development section.
Where i can download the rom ?
- look for Jenkins.androidarmv6.org/view/Android/Builds (download only "TASS" builds)
you can look too for Review.androidarmv6.org (see it for reviews of fixed etc)
Where can i find Gapps ?
- i think no was a full package for Gapps (no much space left in the system)
Whats never going to be fixed ?
- google now voice search (dont wait for it, never going to be fixed, why ? device its armv6 google now voice search works only in armv7 .) and others few things
batery- KitKat really takes so much batery!
do thanks for devs of armv6 Team.
if possible donate or pay a drink for their
if you have anything that can help with the development post here. (fixes solutions etc)
i stopped testing with this Device since i buyed a Lg optimus L5(E612)
but i'm here you can use my PM to help (question possible solutions littles things too)
and sorry for my slower updates, its why i'm not at home theses days and i have only 5% of free time to check the forum.
Hot News!!! :
all changes are going to be merged so if any build have a old bug dont worry . only report .
psyke83 said:
Please folks, always take the time to upload logs. You appear to have no active developer who owns a Mini at this moment, so we (other androidarmv6 developers) rely exclusively on users to assist in fixing bugs specific to your device.
Click to expand...
Click to collapse

Link to CyanogenMod 11 for Galaxy Mini thead

AntiBillOS said:
Yes
Click to expand...
Click to collapse
So any progress? Just interested.

ast00 said:
So any progress? Just interested.
Click to expand...
Click to collapse
Working hard on get it builded.

AntiBillOS said:
Working hard on get it builded.
Click to expand...
Click to collapse
so any possible fix for android 4.3 cm 10.2 camera ? i think people forget it

AfonsoADR said:
so any possible fix for android 4.3 cm 10.2 camera ? i think people forget it
Click to expand...
Click to collapse
I even don't want to look at Android 4.3 coz it mutch laggy than 4.2*. Also I have no mutch free time, so I focused at Android 4.4.

AntiBillOS said:
I even don't want to look at Android 4.3 coz it mutch laggy than 4.2*. Also I have no mutch free time, so I focused at Android 4.4.
Click to expand...
Click to collapse
so contiue so. really no bigger diference of android 4.2 to 3 .
looks better work in 4.4 . ur correct . really looks lost time work in cm 10.2 i see this now

I've been looking at the Jenkins build bot from androidarmv6 team. It seems that they haven't managed any successful builds either.

programmargorp said:
I've been looking at the Jenkins build bot from androidarmv6 team. It seems that they haven't managed any successful builds either.
Click to expand...
Click to collapse
I don't it for boot.

on general kitkat just need minimum 512MB RAM right?? for JB need 1GB ram ??
sorry for my english

Guys,I dont want to destroy your hope but, I have 4.4 on my XT and RAM manager is still pretty same as it was on CM10.2 ..still 300mb +- RAM in use.
Maybe is minimum requirement 512MB but mini have only 279MB.

Villeness said:
Guys,I dont want to destroy your hope but, I have 4.4 on my XT and RAM manager is still pretty same as it was on CM10.2 ..still 300mb +- RAM in use.
Maybe is minimum requirement 512MB but mini have only 279MB.
Click to expand...
Click to collapse
384MB* About 105MB of it is system reserved, which is not accounted by the requirements.

Why are we worried? JB needs 1gb and it ran on Mini. KK needs half of it, it should run just fine.

android 4.4 was made by google optimized to take less ram memory.
will work better than cm10-10.1-10.2 .
galaxy mini no have a totally hardware support but no have problem try right ?

As my Gio just died, I'm back to reading these forums for the sake of keeping my brother's Mini decent now, haha.
Speaking of which, yeah, I'm curious how CM11 will run, seeing how anything up to CM10 runs smoothly (CM10.1 not so much, CM10.2 horribly).
We'll get a surprise. Two possibilities is that it's either going to run so horribly that we'll not even consider using it, or it'll be as nice and smooth as CM9 is if not better (Although I wouldn't count on that).

Harakhti said:
As my Gio just died, I'm back to reading these forums for the sake of keeping my brother's Mini decent now, haha.
Speaking of which, yeah, I'm curious how CM11 will run, seeing how anything up to CM10 runs smoothly (CM10.1 not so much, CM10.2 horribly).
We'll get a surprise. Two possibilities is that it's either going to run so horribly that we'll not even consider using it, or it'll be as nice and smooth as CM9 is if not better (Although I wouldn't count on that).
Click to expand...
Click to collapse
cyanogenmod 11 promisses , why kitkat was optimized low memory and more other optimizations.
lastest release of cm 10.1 was better than cyanogenmod 10 .
kitkat will run great on mini. i'm 100% of this

Cheer up, Jenkins seems to be able to build again.

For those who are interested in knowing about our progress.
http://jenkins.androidarmv6.org/view/Android/builds
I hope soon we will see a tass cm11 there :laugh:

cyanogenmod 11 on LG P500
1st release of armv6 device P500 (LG optimus one) was received a first cyanogenmod 11 : submission-test .
check'out here : http://jenkins.androidarmv6.org/job/submission-test/755/

now cooper(Galaxy ACE) receive submission test : http://jenkins.androidarmv6.org/view/Android/job/submission-test/757/
Sucess
Galaxy 5 received Cyanogenmod 11 : http://jenkins.androidarmv6.org/view/Android/job/android-experimental/340/

Why no 3.4.x based kernel?

Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk

saurav112214 said:
Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
Have you seen kholks kernel? its 3.4
Its a big undertaking with little benefit compared to the amount of work put in, It can be great if everything is stable and working but it normally requires a team of developers hired by LG to pull it off.

JoinTheRealms said:
Have you seen kholks kernel? its 3.4
Its a big undertaking with little benefit compared to the amount of work put in, It can be great if everything is stable and working but it normally requires a team of developers hired by LG to pull it off.
Click to expand...
Click to collapse
Yes I have seen Kholks kernel, it is 3.4 but apart from that (with all due respect) its not working as it should (RIL, Mobile data, otg, battery drain etc). Moreover it looks like he has abandoned the project and no other projects are 3.4 based.
I did not know that it requires a team of developers hired by LG to pull it off. I thought it was just do able by developers here because they brought us all the amazing android goodies. Sorry for being noob. Since we know that LG is crap in providing support to devices, is it safe to assume that we will never be getting 3.4 version of kernel?

saurav112214 said:
Yes I have seen Kholks kernel, it is 3.4 but apart from that (with all due respect) its not working as it should (RIL, Mobile data, otg, battery drain etc). Moreover it looks like he has abandoned the project and no other projects are 3.4 based.
I did not know that it requires a team of developers hired by LG to pull it off. I thought it was just do able by developers here because they brought us all the amazing android goodies. Sorry for being nobb. Since we know that LG is crap in providing support to devices, is it safe to assume that we will never be getting 3.4 version of kernel?
Click to expand...
Click to collapse
It doesnt require LG but to get it completely polished to OEM standard a team of that size is very handy. We may see another independently developed 3.4 kernel, nvidia has dropped their 3.4 kernel source for tegra which would make it easier, id personally rather backport some of its improvements and features than port it to our device

JoinTheRealms said:
It doesnt require LG but to get it completely polished to OEM standard a team of that size is very handy. We may see another independently developed 3.4 kernel, nvidia has dropped their 3.4 kernel source for tegra which would make it easier, id personally rather backport some of its improvements and features than port it to our device
Click to expand...
Click to collapse
Would be great to get the 3.4 kernel from nvidia used as base for our P880. Great idea !

saurav112214 said:
Dear forum members. I would like to ask why we cant have 3.4 based kernels? Htc one x with almost identical hardware has it..and many other devices using the same processor and other hardware have it too. What is the requirements for 3.4 kernel? I see a lot of developers have put amazing effort for bringing new kernels to us that has greatly improved the performance of our device but we dont have 3.4 based kernels. I would love to know if i would ever get usb otg on my device. Now that nvidia has released a new source for supporting kitkat, is there a chance that we could get 3.4 based kernel anytime soon? Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
HTC One X doesn't have a 3.4.x kernel on Tegra 3. "Android 4.2.2 Sense 5 - kernel 3.1.x