Hey guys
I've been watching out the work of psyke83 by porting kernel 3.0.31 to msm7x27 devices in madteam forum and him next release of CM10.1 for Galaxy 5 (no ETAs) will already be using this new kernel, how you
can see in changelog maded by himself (http://madteam.co/forum/development-8/(dev)-cyanogenmod-10-1-galaxy5-port-(androidarmv6)/).
Considering the good things he comented in changelog by bringing kernel 3.0.31 to Galaxy 5, i'm wondering if developers here are already knowing that and if the same will occur to our Ace.
Will we have kernel 3.0.xx working on futures 4.2 based ROMs? Here is the link to the kernel development itself http://madteam.co/forum/development...el-3-0-8-porting-for-samsung-msm7x27-devices/.
Would be awesome if devs would implement latest 3.x kernel
Sent from my GT-S5830 using xda app-developers app
We have already 3.0.31.1 kernel xD )) Its working awesome. Big battery life and big performance
P_A said:
We have already 3.0.31.1 kernel xD )) Its working awesome. Big battery life and big performance
Click to expand...
Click to collapse
who is "we"?
Gesendet von meinem Nexus 7 mit Tapatalk 2
..
links for download?
Look at this: http://forum.xda-developers.com/showpost.php?p=39970645&postcount=263
Psyke83 checked the kernel and found out that this is just
the older androidarmv6 2.6.37 kernel with the version number faked in the kernel Makefile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39972798#post39972798
nikwen said:
Psyke83 checked the kernel and found out that this is just
http://forum.xda-developers.com/showthread.php?p=39972798#post39972798
Click to expand...
Click to collapse
Yea, this one was a fake, but i was talking about the real development that is being made by psyke and the others. I really expect to see our legacy devices (Ace, G5, Mini, Gio, etc) running this kernel with android 4.2.1
Could anybody please post the link to his kernel 3.xx sources here as I am not a member of the madteam forum and can't view links there for that reason?
EDIT: Found it: https://github.com/psyke83/android_kernel_samsung_msm
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
And does anybody know why they can not get it booting on our Ace?
Related
According to the nightly builds site, it looks that starting today the SGM is integrated into the main path of Cyanogen build. The next build is going to include the SGM string.
review.cyanogenmod.com/#change,8469
yep it's true cyanogen team has added galaxy mini to their devices list...
Yeah...yeah..hope we will get a study rom..but this (7.1) is also not that bad..thanks to tj...
Sent from my GT-S5570 using XDA App
Wow That's amazing!!!!! When I saw this thread i thinked it's only prediction, but now... I'am feeling very very happy!!!!!
I see here http://cm-nightlies.appspot.com/ that our mini vendor is add to ace nightly build #235 so this last build for ace is also for us?
denzel09 said:
I see here http://cm-nightlies.appspot.com/ that our mini vendor is add to ace nightly build #235 so this last build for ace is also for us?
Click to expand...
Click to collapse
No, maybe will use tass name not ace, now just waiting, hope release soon
Ok buddy, understand now
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
squadzone said:
No, maybe will use tass name not ace, now just waiting, hope release soon
Click to expand...
Click to collapse
I will wait your amazing mod kernel and other ;-D
Wait a few days. It should have it's codename tass... Check tomorrow or even later
new release!
the link shared here, umm those guys posted a new link today... still not sure if it is compatible to our mini? any clues!
Galaxy mini has codename tass, it is for ace.
TheWhisp said:
Galaxy mini has codename tass, it is for ace.
Click to expand...
Click to collapse
Afaik, ace and mini are different. Or what its the difference from rom point of view?
genieass said:
Afaik, ace and mini are different. Or what its the difference from rom point of view?
Click to expand...
Click to collapse
Yes, they are different...
any update
freaking awesome
edenscully said:
any update
Click to expand...
Click to collapse
No nothing for now..
Hi folks!!
Take a look to this I found
http://developer.sonymobile.com/wp/...ical-differences-between-gingerbread-and-ics/
It clearly explains why 1/3 of I9100G total RAM is not seen by us.
request
please do not start new tread for small topics like this
It's a theme of great interest, I think
scontin said:
Hi folks!!
Take a look to this I found
http://developer.sonymobile.com/wp/...ical-differences-between-gingerbread-and-ics/
It clearly explains why 1/3 of I9100G total RAM is not seen by us.
Click to expand...
Click to collapse
THANKS
And why it isnt on the normal SG2 too?
Sent from my GT-I9100G mit Tapatalk 2
I don't think it's a problem, with the new ICS formware finally my i9100g is going great! Solved many bugs of GB, good interface and performances.
But why it isn't on the normal SG2 version and only on the G version?
Maybe it can depend by the fact ICS was developed on OMAP architetecture?
Galaxy Nexus have the same amount of RAM.................
Thank you for your information.
---------- Post added at 12:15 AM ---------- Previous post was at 12:08 AM ----------
scontin said:
Maybe it can depend by the fact ICS was developed on OMAP architetecture?
Galaxy Nexus have the same amount of RAM.................
Click to expand...
Click to collapse
The Galaxy Nexus was the first to run ICS, So it's fully compatible with it, but I9100G received the 4.0 after a long time, that means there were so many problems to solve. And I think this is one of them, I think it has relation with the boot or hardware resources.
According to me it's not totally correct.
Maybe Samsung engineers were occupied by S3 launch, so I9100G was put into the second floor
atomo37 said:
I don't think it's a problem, with the new ICS formware finally my i9100g is going great! Solved many bugs of GB, good interface and performances.
Click to expand...
Click to collapse
Which ICS do you have?
Sent from my GT-I9100G using XDA
neshro said:
Which ICS do you have?
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
basically all ics released is the same but some say malaysia version is better than india...its matter of personal opinion but CM9 is far better than all stock ics
dante10 said:
basically all ics released is the same but some say malaysia version is better than india...its matter of personal opinion but CM9 is far better than all stock ics
Click to expand...
Click to collapse
cm9 is best
only one thing suckz
i cant play some videoz on my phone
Sent from my GT-I9100G using xda premium
I finally ported Xperia JB (4.1.2) to our device. link coming soon...
get the complete xperia feel. about bugs, you guys need to tell me.
Credits : DooMLoRD for his xperia rom
CM team for CM10 and
rishabh.raj37 for his porting technique
Aingaran said:
I finally ported Xperia JB (4.1.2) to our device. link coming soon...
get the complete xperia feel. about bugs, you guys need to tell me.
Credits : DooMLoRD for his xperia rom
CM team for CM10 and
rishabh.raj37 for his porting technique
Click to expand...
Click to collapse
Sooo this is going to be CM based or are you just thanking those guys cause they're awesome?
It's most likely ported over a cm10 base.... Which I gotta wonder how stable that will be since there isn't a decent cm 10 for ahd...
Sent from my MB886 using Tapatalk 4 Beta
---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------
Aingaran said:
I finally ported Xperia JB (4.1.2) to our device. link coming soon...
get the complete xperia feel. about bugs, you guys need to tell me.
Credits : DooMLoRD for his xperia rom
CM team for CM10 and
rishabh.raj37 for his porting technique
Click to expand...
Click to collapse
You need to get the link posted up. If it's not ready to post please DONT make a thread. No place holders.
Sent from my MB886 using Tapatalk 4 Beta
You are not allowed to create "place-holder" threads on XDA
Please send me a PM or report this thread when you have a link ready to post.
Until then, thread closed.
Hello everybody,
First of all this is not yet an announcement for a project.
I'd like to know if there are people already working on this task or not.
If not I hope some people are interested in teaming up to port over the msm-3.10 kernel to ariesve just like arco, ivendor and the AriesVE_Dev_Connection team has done for kernel 3.0 and the 3.4 kernels.
At the moment there isn't a android version which uses the 3.10 kernel as far as I know, but because the source is already available on the AOSP repository and also in the CodeAurora github this hints a version which ships with kernel 3.10 will land in the near future.
Of course I can't exactly tell what the changes between the 3.4 and 3.10 kernel exactly are because this is a very big list.
You have to think in terms of bug fixing, power enhancements, updated drivers and code for filesystems etc.
So if you have some knowledge with the linux kernel, programming, patching, and with git please leave a message in this post.
Greetings PsychoGame
PsychoGame said:
Hello everybody,
First of all this is not yet an announcement for a project.
I'd like to know if there are people already working on this task or not.
If not I hope some people are interested in teaming up to port over the msm-3.10 kernel to ariesve just like arco, ivendor and the AriesVE_Dev_Connection team has done for kernel 3.0 and the 3.4 kernels.
At the moment there isn't a android version which uses the 3.10 kernel as far as I know, but because the source is already available on the AOSP repository and also in the CodeAurora github this hints a version which ships with kernel 3.10 will land in the near future.
Of course I can't exactly tell what the changes between the 3.4 and 3.10 kernel exactly are because this is a very big list.
You have to think in terms of bug fixing, power enhancements, updated drivers and code for filesystems etc.
So if you have some knowledge with the linux kernel, programming, patching, and with git please leave a message in this post.
Greetings PsychoGame
Click to expand...
Click to collapse
The current msm kernel 3.10 from Google is experimental !! it needs much more effort to compile successfully !
Its better to start from LKA 3.12 branch . as Dorimanx has changed his branch to 3.12 successfully I am sure its possible to boot LKA 3.12 on ariesve too .
Do not forget its too much more difficult than what have been done for 3.0/3.4 ! Kernel 3.10/3.12 has huge changes in memory management , timer , processes and may be net (?) . our drivers are too old !
KitKat is based on 3.4, no need for a new Kernel version.
Sent from my Nexus 4 using Tapatalk 4
XeLLaR* said:
KitKat is based on 3.4, no need for a new Kernel version.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hello XeLLaR,
I partially disagree with you on the need for a new kernel.
First of all the kernel is loosely related with the android version, but in fact every kernel theoretically could work with most android versions.
An example is of course ICS which used the 2.6 kernel at first and JB which used 3.0 at first before 3.4 was ported.
If it was possible AOSP would follow the mainline kernel release schedule, because this way you are always assured of the latest optimizations and bug fixes.
Unfortunately this still isn't a possibility as some android code still isn't merged in the mainline by Linus Torvalds because of potential problems with existing code.
Luckily this problem is getting smaller and smaller each kernel release as more and more android patches get sent upstream in the Linux mainline sources.
Alireza7991 gave an example of Dorimanx which ported the LKA 3.12 kernel over to his android devices.
So I think it's certainly useful to port over the msm-3.10 and maybe even 3.12 kernel, the question which only remains is, are there people interested in this project?
Greetings PsychoGame
But is it usefull to use an LKA kernel?
We must use CAF Sources to create a proper kernel.
Sent from my Nexus 4 using Tapatalk 4
Currently there are more importan projects, this is waste of time...
My 2 cents
XeLLaR* said:
But is it usefull to use an LKA kernel?
We must use CAF Sources to create a proper kernel.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yes it is useful .
Android is a software which runs on linux kernel so there won't be any problem for booting ariesve using LKA !. just some patches are needed to be merged for adding the support of features Android needs
Is'nt it better to keep our kernel with a new and stable base instead of using an ancient kernel for just being in CAF branch ?
However we can even start from Dorimanx's 3.12 branch !
alireza7991 said:
Yes it is useful .
Android is a software which runs on linux kernel so there won't be any problem for booting ariesve using LKA !. just some patches are needed to be merged for adding the support of features Android needs
Is'nt it better to keep our kernel with a new and stable base instead of using an ancient kernel for just being in CAF branch ?
However we can even start from Dorimanx's 3.12 branch !
Click to expand...
Click to collapse
I think dorimanx is an exynos kernel
Inviato dal mio GT-I9505 usando Tapatalk 4
davidteri91 said:
I think dorimanx is an exynos kernel
Inviato dal mio GT-I9505 usando Tapatalk 4
Click to expand...
Click to collapse
My knowledge in that case is very poor, but this is a guy, who try to port 3.12 to galaxy spica i5700 (ARM v6) https://twitter.com/tom3q/status/364896808327065601
So I dont knwow it is necessary, but is possible In my opinion there are more important things
davidteri91 said:
I think dorimanx is an exynos kernel
Inviato dal mio GT-I9505 usando Tapatalk 4
Click to expand...
Click to collapse
Exynos = MSM = APQ = OMAP = ... = ARM based platform
we just need to merge msm-7x30 specific codes in kernel + drivers .nothing else is needed ;
I just said Dorimanx 3.12 kernel since it boots android so there is no need to add Android support to kernel , also it has been booted on a device which is very similar to ariesve, we only need to add msm-7x30 support !
alireza7991 said:
Exynos = MSM = APQ = OMAP = ... = ARM based platform
we just need to merge msm-7x30 specific codes in kernel + drivers .nothing else is needed ;
I just said Dorimanx 3.12 kernel since it boots android so there is no need to add Android support to kernel , also it has been booted on a device which is very similar to ariesve, we only need to add msm-7x30 support !
Click to expand...
Click to collapse
Hello Alireza7991,
Currently I'm experimenting with the msm-3.10 source which is available over at https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/
I use this source as base because it has the android patches along with many of the Qcom patches for hardware support.
It's just an experiment at the moment, and I don't know how far I will be able to get.
Currently I'm patching in the AriesVE specific support and from there will try to fix the building process.
PsychoGame said:
Hello Alireza7991,
Currently I'm experimenting with the msm-3.10 source which is available over at https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/
I use this source as base because it has the android patches along with many of the Qcom patches for hardware support.
It's just an experiment at the moment, and I don't know how far I will be able to get.
Currently I'm patching in the AriesVE specific support and from there will try to fix the building process.
Click to expand...
Click to collapse
Hi, any progress on this?
alireza7991 said:
The current msm kernel 3.10 from Google is experimental !! it needs much more effort to compile successfully !
Its better to start from LKA 3.12 branch . as Dorimanx has changed his branch to 3.12 successfully I am sure its possible to boot LKA 3.12 on ariesve too .
Do not forget its too much more difficult than what have been done for 3.0/3.4 ! Kernel 3.10/3.12 has huge changes in memory management , timer , processes and may be net (?) . our drivers are too old !
Click to expand...
Click to collapse
Hello my friend.
kernel 3.10 is booting on huawei u8800 (msm7x30 device)work done by Blefish from xda.
that will be uploaded when all is fine.
desalesouche said:
Hello my friend.
kernel 3.10 is booting on huawei u8800 (msm7x30 device)work done by Blefish from xda.
that will be uploaded when all is fine.
Click to expand...
Click to collapse
Hey,
That souds great! But booting is only step one. Being stable is a different story.
Gesendet von meinem Nexus 5 mit Tapatalk 2
XeLLaR* said:
Hey,
That souds great! But booting is only step one. Being stable is a different story.
Gesendet von meinem Nexus 5 mit Tapatalk 2
Click to expand...
Click to collapse
Let the work be finish , it is still wip.
desalesouche said:
Let the work be finish , it is still wip.
Click to expand...
Click to collapse
We'll See.
Gesendet von meinem Nexus 5 mit Tapatalk 2
XeLLaR* said:
We'll See.
Gesendet von meinem Nexus 5 mit Tapatalk 2
Click to expand...
Click to collapse
hope you have a huawei honor (u8860) device cos for now 3.10 msm7x30 kernel is done for that device...
if you don't you will see nothing.
you might port it to arieves if you want.
desalesouche said:
hope you have a huawei honor (u8860) device cos for now 3.10 msm7x30 kernel is done for that device...
if you don't you will see nothing.
you might port it to arieves if you want.
Click to expand...
Click to collapse
I think i could buy one but im not into this stuff anymore (since i have a Nexus5 and a Nexus6 over here)
Porting a booting kernel shouldnt be that hard. Ramdisk and a few drivers are the only things that need changes i think. But im not a developer by any means, so that could be wrong as hell. You could send a link of the repo to christopher, but i guess he's busy with other things.
P.S: Blefish is an awesome developer, i saw much stuff from him in github when we (DevCon) developed the 3.4 kernel for the AriesVe. I think he even contributed to our repos but im not a 100% sure.
Gz
X
Gesendet von meinem Nexus 5 mit Tapatalk 2
XeLLaR* said:
I think i could buy one but im not into this stuff anymore (since i have a Nexus5 and a Nexus6 over here)
Porting a booting kernel shouldnt be that hard. Ramdisk and a few drivers are the only things that need changes i think. But im not a developer by any means, so that could be wrong as hell. You could send a link of the repo to christopher, but i guess he's busy with other things.
P.S: Blefish is an awesome developer, i saw much stuff from him in github when we (DevCon) developed the 3.4 kernel for the AriesVe. I think he even contributed to our repos but im not a 100% sure.
Gz
X
Gesendet von meinem Nexus 5 mit Tapatalk 2
Click to expand...
Click to collapse
no need for you to buy that device, xD.
and i agree with you that @Blefish is awesome dev. i wish i have his knowledge.
Brickbug Aftermath: Speeding up the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000
UPDATE: CM 12.1 kernels are now available!!! (for CM 12.1-supported platforms only: i9100 and i777.) new kernels are rom-independent: they are no longer tailored to specific official CM builds (they might work with other roms too) and their names no longer reference a specific CM build.
UPDATE: this project now supports all roms and kernels!
if you are not running CyanogenMod M snapshots, please see this post.
this project restores TRIM capability to CyanogenMod kernels for the Galaxy S2 family of 4210-based devices: i9100, i777, d710 and n7000. TRIM is needed to avoid "aging" of the state of the eMMC, the internal flash storage, that eventually slows the device to a crawl. TRIM functionality is built into android 4.3 and later. however, due to historical and safety concerns, TRIM capability was removed from the CM kernels for these devices (and from most if not all other AOSP-based kernels).
STOP!!! DRAGONS AHEAD!!!
in theory there could be risk of hard-bricking your device forever.
1) READ THIS POST IN FULL.
2) answer this poll (view results).
3) discuss your n7000 experience below in this thread.
Downloads
for the supported devices, you will find IsoRec-compatible CyanogenMod-based kernels here. (old kernels without IsoRec support can be found here. yet older retired kernels without FPBug fix are still available here.) note that for some supported devices, no releases or M snapshots are currently being produced. for those devices i can produce kernels based on known 'stable' nightlies if users ask.
XDA:DevDB Information
BrickbugAftermath-n7000, Kernel for the Samsung Galaxy Note GT-N7000
Contributors
Lanchon
Source Code: https://github.com/Lanchon/BrickbugAftermath-SGS2
Kernel Special Features: CyanogenMod kernel with TRIM support
Version Information
Status: Beta
Created 2014-09-13
Last Updated 2016-01-12
(reserved)
Can this kernel be used on Slimkat and Slimkat based ROMs ?
AFAIK they are based on CM kernels !?
der_Kief said:
Can this kernel be used on Slimkat and Slimkat based ROMs ?
AFAIK they are based on CM kernels !?
Click to expand...
Click to collapse
no way for me to know! these are CM kernels
Hi, could you perhaps make a kernel with these implementations but based on CM11/Omni? Any of the latest nightlies are "stable".
XxPixX said:
Hi, could you perhaps make a kernel with these implementations but based on CM11/Omni? Any of the latest nightlies are "stable".
Click to expand...
Click to collapse
i sure can. M10 should be out tomorrow maybe. lets wait for that, and if no M10 for the n7000, then ill make a nightly. any nightly that ud recommend?
Where is the kernel? I checked the link and couldnt find it
Sent from my GT-N7000 using XDA Premium 4 mobile app
NoteboyTech said:
Where is the kernel? I checked the link and couldnt find it
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
please read again!
OHkay.. then i guess you should proceed and create a kernel.. its time we test them.. but will it improve speed by a huge margin or it is just a placebo?
Sent from my GT-N7000 using XDA Premium 4 mobile app
NoteboyTech said:
will it improve speed by a huge margin or it is just a placebo?
Click to expand...
Click to collapse
It will vary from user to user, but if you have high I/O lags then yes, there will be a big improvement.
if u used CM and its kernel for long in your phone or ever used up most of the phone's storage since installing CM, it should make q big difference.
how to test if device needs to be trimmed ?
der_Kief said:
how to test if device needs to be trimmed ?
Click to expand...
Click to collapse
all do regularly
don't understand you right....
Do you mean if everthing is working without problems/slowdowns than no need to trimm ?
der_Kief said:
don't understand you right....
Do you mean if everthing is working without problems/slowdowns than no need to trimm ?
Click to expand...
Click to collapse
if you dont trim it will slow down, or it has slowed down already
where is the CM11 kernel for the N7000 ?
In CM-11-M9 folder there is only a kernel for the I9100 !
der_Kief said:
where is the CM11 kernel for the N7000 ?
In CM-11-M9 folder there is only a kernel for the I9100 !
Click to expand...
Click to collapse
please read the OP! and thread
ok, than i may ask you if you are so kind and build a kernel for the N7000 ?
der_Kief said:
ok, than i may ask you if you are so kind and build a kernel for the N7000 ?
Click to expand...
Click to collapse
sure. the M10 was promised for this weekend that just ended. it should be released very soon, please wait till that happens. if they don't release an M10 for the n7000 then i'll do a nightly.
crap, this is the latest the CM has ever been on a CM11 nightly!!!
http://download.cyanogenmod.org/?device=hammerhead&type=snapshot
and by a whole week!