Database Develop

[Q] kernel 2.6.32 ??

look im a n00b(still learning android stuff),
so this question is just out of curosity
why cant we have kernel 2.6.32 ??
well google said froyo needs atleast 2.6.32 to run
but we here are running gingerbread smoothly on 2.6.29(thnaks to all the awsoms devs )
can someone knowledgble reply
thank you ;p

Simply because the kernel drivers needed for the X8 only exist in Linux 2.6.29 as published by Sony Ericsson.
If you would want to use a newer Kernel release (i.e. the ones Google is using for their Android builds) you need to port the drivers to that kernel version - read: make them fit the kernel.
That's a very tedious process, so it's easier for the ROM and Kernel developers to base their work upon the original SEMC Linux 2.6.29 sources.

on short: its easier to port drivers from 2.6.32 or 35 or 38 than make the base 2.6.32.... working on our phone

as b.jay said, porting kernels takes a long time, and if you recive only a couple of errors in the middle of it, BOOM, you gotta go back to the sart and track what wrong command you typed or what code is wrong etc. thats why no one has ported 2.6.32 kernel.
to many drivers to cope with, to much errors that you will recive. porting roms is easyer

thanks guyz for the answers....in short it is possible to have kernel 2.6.32....maybe nAa can port it....he has already backported some stuff.

It is possibe given someone wants to spend an insane amount of time (edit: we're talking several weeks to several months here) in forward-porting the Shakira specific drivers and additions to the ARM Linux code base.
I don't see it happen as it's a enormous undertaking for a single developer to port the whole stuff - that would require a medium-sized team of coders a) knowing what to port / b) well versed in Linux Kernel hacking / c) knowing how to code for ARM (edit: as the existing sources most likely need to be adapted to the Kernel ABI (in this case 2.6.3.x), which is not exactly stable in Linux and changes erratically as Linus' maintainers see fit. Also, don't forget that the changes need to be tested to see if the kernel boots and works flawlessly).
Don't hang your hopes too high.

need to much time to update linux version of kernel

But for instance lg optimus p350 has almost same specs but runs .32 kernel.it has same qualcomm 600 mhz cpu,ardeno 200,and 140 mb ram.so x8 has even better specs.so i dont se why this wouldnt be possible.
Sent from my GT-I5800 using xda premium

Budding dev needs some help

Hello all. I've recently been trying to get into Android development, more specifically Kernel development. I've played around with some kitchens and looked at the GB kernel sources from Samsung and tweaked it around.
Previously I previously learned Java to a point where I can put basic lines down and also more advanced stuff but with a bit of help here and there.
I have one question though, what would be the recommended path for creating an ICS Kernel. My plan is to start of with something "stock" and build up but I'm not quite sure what to consider stock seeing as the S1 never got ICS officially. Would I have to use CM9's Kernel sources and if so where do I acquire them.
I also have a good understanding of Ubuntu and its terminal and have a functional idea of what I'm doing there.

[Kernel] Shield Portable Kernel Development [Incl. Guide]

Welcome to the first custom kernel for the KitKat Shield.​
This thread is for the development and building of the Shield Portable kernel.
This is not intended to download a build, post issues, and return when fixed.
Kernel Source:
https://github.com/StarKissed/starkissed-kernel-roth
Kernel Downloads:
https://goo.im/devs/playground/shieldroth
The kernel can be built using the commands below or the included script.
Code:
make tegra11_android_defconfig -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make tegra114-roth.dtb -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).

[Kernel] Shield Kernel Development
The included ramdisk is for update 98. If you are on 72, this will most likely result in a bootloop. Using the 72 ramdisk will not work with this kernel, as the source is specific to "OTA 5" according to the Nvidia gitweb.

I recently updated the source and changed a few commands that may explain why current source resulted in non-working builds. I will be testing builds soon and then begin modifying the kernel once the core build is verified working.

Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.

rylen said:
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
Click to expand...
Click to collapse
All the code is there, it just loops. I'm not sure what's going on with it. The shield tablet version works.

Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!

bakageta said:
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
Click to expand...
Click to collapse
Won't do much good until it boots

True enough, just thought I'd bring it up since it's a fairly easy fix. In the meantime, I threw together a stock kernel with an updated driver to get by. I had one problem after another with the latest official driver, but the good folks at LKML had already put some work in on v4.1.0 several years ago. Using drivers/net/usb/asix.c and usbnet.c from the 3.4.106 source built without problems.

Beginning to think I may have to settle for building against the full source on this one. It boots fine when doing that, but not built alone. The shield tablet builds fine alone, so there's no explanation for it.

you are going to make a new build of your kernel? if you need help with the tests i can help.

YamazakiRobert said:
you are going to make a new build of your kernel? if you need help with the tests i can help.
Click to expand...
Click to collapse
Things are a bit crazy, but once I can get all of the changes fixed up and it'll build clean, I'm going to try to run it over night.

Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.

bakageta said:
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
Click to expand...
Click to collapse
It shouldn't be related. You may need to check the proprietary drivers. I believe HDMI is one.

Didn't bother to find out what the problem was, it just stuck around because I was doing dirty builds as I tested. Once I got a few other tweaks and had some time, I did a clean build and it resolved itself. Did you manage to get your kernel booting when building it by itself? I'm sure I'm doing something wrong there too, but I've been grudgingly building the entire device, since that at least works reliably.

What is so special about this kernel compared to stock ? goodjob already btw, you're one of the few who actually have a kernel
It's really sad how not much development is going on, it's such a good device there is only like 1 release at the original section :/

[DEV][KERNEL] TRIM for Galaxy Tab 10.1

Obsolete. This has been merged into the most recent releases of my ROMs.
TRIM for Galaxy Tab 10.1
These are kernels with TRIM enabled.
Backstory:
In 2011/2012 the eMMC DISCARD operation (aka TRIM) resulted in the SuperBrick bug on this device and many other Samsung devices. Samsung released a fix[1] back then but the Android community was not happy with the way Samsung had treated the them. So it seems that many ROM maintainers did not trust that the issue was fixed. The SuperBrick bug patch was never merged for most devices despite it being merged into the mainline Linux kernel. Instead the indie developers opted to disable the DISCARD operation all together. Since then every major ROM/kernel/recovery for this device has had DISCARD disabled.
Fast forward to the past year and a half or so some developers began to release kernels with the Samsung brickbug patches and renabling the DISCARD operation. The buggy operation that resulted in bricking eMMC cards is the secure DISCARD operation. The plain DISCARD operation is safe. The patch from Samsung simply disables the buggy secure DISCARD.
I have been testing TRIM for this device on my own since shortly after[2] I first released the Lollipop ROM in November 2014. I have not run into any problems since then.
Developer @Lanchon has been publicly testing[3] it on the Galaxy S2 i9100 for a long time. Recently the DISCARD functionality was officially merged into the CM-13.0 kernel for that device. He also pointed out in a recent post that the lifespan of eMMC cards are adversely affected by write amplification[4] if TRIM is not being used.
So all things considered I think we are overdue for re-enabling the DISCARD operation and having TRIM working for this device.
Additional note:
Wiping in recovery is still safe. Some devices use the same kernel for the ROM and recovery. This device does not. This device has a seperate kernel for the ROM and recovery. So there is zero risk with using this kernel and any recovery that is also itself safe to use.
That was a major concern for devices that use a single kernel for the ROM and recovery but that does not apply to this device. Every recovery I have released to date still has DISCARD completely disabled.
You can find plenty of documentation/articles/threads about the SuperBrick bug saga so I won't write anymore than needs to be said.
[1] https://wiki.cyanogenmod.org/w/EMMC_Bugs
[2] https://github.com/Decatf/android_kernel_samsung_p4/commit/15ca63c60b63a9e6796b9554694c1a2c9aed2a53
[3] http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-brickbug-aftermath-speeding-t2843238
[4] https://en.wikipedia.org/wiki/Write_amplification
Downloads:
I'm posting these as a separate project because I won't be re-enabling DISCARD in the kernel of my ROM releases until these kernels have been tested publicly for some time.
Standard disclaimer applies. Use this at your own risk!
p4wifi_kernel-aosp-5.1-20150305-TRIM.zip
p4_kernel-aosp-5.1-20150305-TRIM.zip
p4tmo_kernel-aosp-5.1-20150305-TRIM.zip
Only compatible with aosp-6.0.1-20160428 and older. ROMs newer than 20160428 have TRIM included by default.
p4wifi_kernel-aosp-6.0-20160414-TRIM.zip
p4_kernel-aosp-6.0-20160414-TRIM.zip
p4tmo_kernel-aosp-6.0-20160414-TRIM.zip
Using TRIM:
Android runs TRIM automatically (since Lollipop) so you don't need to install any app to do it. You might want to run it manually once after you've installed this kernel since most of your devices probably have never been TRIMed before.
There is a command to do it manually from the terminal. It must be run as root.
Code:
$ fstrim -v /data
$ fstrim -v /system
$ fstrim -v /cache
XDA:DevDB Information
TRIM for Galaxy Tab 10.1, Kernel for the Samsung Galaxy Tab 10.1
Contributors
decatf
Kernel Special Features:
Version Information
Status: Testing
Created 2016-03-07
Last Updated 2016-08-23

Thanks bro. Will surely try it

Hello
There is problem. I cant install p4 trimm kernel because of error message " your unit isn't p4tmo" My unit is really p4 the message is failed. Please correct the error. Best regards joe ps your rom is fantastic
decatf said:
TRIM for Galaxy Tab 10.1
These are kernels with TRIM enabled.
Backstory:
In 2011/2012 the eMMC DISCARD operation (aka TRIM) resulted in the SuperBrick bug on this device and many other Samsung devices. Samsung released a fix[1] back then but the Android community was not happy with the way Samsung had treated the them. So it seems that many ROM maintainers did not trust that the issue was fixed. The SuperBrick bug patch was never merged for most devices despite it being merged into the mainline Linux kernel. Instead the indie developers opted to disable the DISCARD operation all together. Since then every major ROM/kernel/recovery for this device has had DISCARD disabled.
Fast forward to the past year and a half or so some developers began to release kernels with the Samsung brickbug patches and renabling the DISCARD operation. The buggy operation that resulted in bricking eMMC cards is the secure DISCARD operation. The plain DISCARD operation is safe. The patch from Samsung simply disables the buggy secure DISCARD.
I have been testing TRIM for this device on my own since shortly after[2] I first released the Lollipop ROM in November 2014. I have not run into any problems since then.
Developer @Lanchon has been publicly testing[3] it on the Galaxy S2 i9100 for a long time. Recently the DISCARD functionality was officially merged into the CM-13.0 kernel for that device. He also pointed out in a recent post that the lifespan of eMMC cards are adversely affected by write amplification[4] if TRIM is not being used.
So all things considered I think we are overdue for re-enabling the DISCARD operation and having TRIM working for this device.
Additional note:
Wiping in recovery is still safe. Some devices use the same kernel for the ROM and recovery. This device does not. This device has a seperate kernel for the ROM and recovery. So there is zero risk with using this kernel and any recovery that is also itself safe to use.
That was a major concern for devices that use a single kernel for the ROM and recovery but that does not apply to this device. Every recovery I have released to date still has DISCARD completely disabled.
You can find plenty of documentation/articles/threads about the SuperBrick bug saga so I won't write anymore than needs to be said.
[1] https://wiki.cyanogenmod.org/w/EMMC_Bugs
[2] https://github.com/Decatf/android_kernel_samsung_p4/commit/15ca63c60b63a9e6796b9554694c1a2c9aed2a53
[3] http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-brickbug-aftermath-speeding-t2843238
[4] https://en.wikipedia.org/wiki/Write_amplification
Downloads:
I'm posting these as a separate project because I won't be re-enabling DISCARD in the kernel of my ROM releases until these kernels have been tested publicly for some time.
Standard disclaimer applies. Use this at your own risk!
p4wifi_kernel-aosp-5.1-20150305-TRIM.zip
p4_kernel-aosp-5.1-20150305-TRIM.zip
p4tmo_kernel-aosp-5.1-20150305-TRIM.zip
p4wifi_kernel-aosp-6.0-20160305-TRIM.zip
p4_kernel-aosp-6.0-20160305-TRIM.zip
p4tmo_kernel-aosp-6.0-20160305-TRIM.zip
Using TRIM:
Android runs TRIM automatically (since Lollipop) so you don't need to install any app to do it. You might want to run it manually once after you've installed this kernel since most of your devices probably have never been TRIMed before.
There is a command to do it manually from the terminal. It must be run as root.
Code:
$ fstrim -v /data
$ fstrim -v /system
$ fstrim -v /cache
XDA:DevDB Information
TRIM for Galaxy Tab 10.1, Kernel for the Samsung Galaxy Tab 10.1
Contributors
decatf
Kernel Special Features:
Version Information
Status: Testing
Created 2016-03-07
Last Updated 2016-03-07
Click to expand...
Click to collapse

decatf said:
TRIM for Galaxy Tab 10.1
I tried this on my P4 Wifi running [AOSP] Android 6.0.1 Marshmallow this evening and the tab rebooted while trying to run the first command. However second attempt seemed to work and trim successfully. :good:
Click to expand...
Click to collapse

Sagij0619 said:
There is problem. I cant install p4 trimm kernel because of error message " your unit isn't p4tmo" My unit is really p4 the message is failed. Please correct the error. Best regards joe ps your rom is fantastic
Click to expand...
Click to collapse
Install the p4 TRWP.

Wow, thank you for that!
My P4wifi was dying (many lags).
I will test your kernel when I have time.

This is awesome! My tablet is running better than ever! I've used it for a week without any issues. It trimmed almost 1.5 GB in data partition when I ran it manually, as advised it the post. Since then, no more lag.
Thank you very much, @Decaft
Enviado de meu GT-P7510 usando Tapatalk

Running this on my p4wifi and boy does this seem to make a huge difference! I installed the kernel then ran the commands as outlined above then rebooted and this thing just flies now. can't believe this is running marshmallow before my note5 awesome work @decatf

It is done. I've installed your Trim kernel on my p4wifi with Lollipop ROM.
I'm not comfortable with terminal so I used Trimmer store app to trim partitions. All went well. No brick. :good:

New toy? Nice! One question though: How does this kernel (release date of March 5 when I wrote this) compare to the one included in your March 14th AOSP 6.0 ROM? I noticed that the kernel build date in the ROM version is also March 14 while this one is earlier (as of this posting). Were the wifi issues that were fixed in the March 14 ROM userspace issues or kernel issues? And a dumb question: If using F2FS, is running fstrim manually once installed still worthwhile, or is that more for ext4 systems?

rtiangha said:
New toy? Nice! One question though: How does this kernel (release date of March 5 when I wrote this) compare to the one included in your March 14th AOSP 6.0 ROM? I noticed that the kernel build date in the ROM version is also March 14 while this one is earlier (as of this posting). Were the wifi issues that were fixed in the March 14 ROM userspace issues or kernel issues? And a dumb question: If using F2FS, is running fstrim manually once installed still worthwhile, or is that more for ext4 systems?
Click to expand...
Click to collapse
It was kernel issues.
Use TRIM regardless of what filesystem it is. Pay no attention to posts elsewhere saying that TRIM doesn't work on F2FS or that it's not worthwhile. Those issues apply to old versions of F2FS. Some maintainers enable an F2FS option that runs DISCARD internally but Android runs TRIM periodically so there's no need to enable that.

Worked great on P7510. No issues at all. Were able to TRIM right after reboot and installation of a terminal .
Just great to get this old relich taken out of deep storage and brought to life again with updated kernel and android 6.0.1 ROM :good:

I'd suggest the app eMMC Brickbug Check for probing the hardware in your tab10.1 flash disk and a little reading online. The first trim after all these years use gives the greatest improvement, removing a monster clog in the hardware. Further trims depend on how much writing/deleting one does.
Working great on my P7510 with decatf rom and pico apps.
---------- Post added at 11:55 AM ---------- Previous post was at 11:23 AM ----------
My eMMC hardware says:
Type: SEM16G
Date: 05/2011
CID: blah long number blah
FwRev: 0x90
YMMV

App rotate soft reboot
@decatf, as if you need more logs to indict rotate sensors, here's another.
I once again ran eMMC Brickbug Check to add the output to my previous post to share with the thread and, like many phone-centric apps, it only runs in portrait mode even though I keep my tab locked in landscape (which nearly eliminated soft reboots), but when the app started in portrait mode, instant soft reboot. Good luck and thanks again.

DrGirlfriend said:
I'd suggest the app eMMC Brickbug Check for probing the hardware in your tab10.1 flash disk and a little reading online. The first trim after all these years use gives the greatest improvement, removing a monster clog in the hardware. Further trims depend on how much writing/deleting one does.
Click to expand...
Click to collapse
Tried the eMMC check.
Result is:
eMMc chip
Type: MAG4FA
Date: 09/2011
CID: 1501004d414734464112f813e2fe9e00
FwRev: 0x12
Brick Bug?
YES. Insane chip
Is the "Brick Bug YES" significant when the path have been put into the kernel ? I gues it is'nt

PowerDK said:
Tried the eMMC check.
Result is:
eMMc chip
Type: MAG4FA
Date: 09/2011
CID: 1501004d414734464112f813e2fe9e00
FwRev: 0x12
Brick Bug?
YES. Insane chip
Is the "Brick Bug YES" significant when the path have been put into the kernel ? I gues it is'nt
Click to expand...
Click to collapse
This fixes the brick bug so it should be safe to use.

TRIM Kernel
The TRIM kernel is working great for me so far on p4wifi.

The aosp-6.0 TRIM kernel been updated with changes from the 20160326 ROM merged in.

could you please tell me how to do it manually? Thanks a lot

dihoc said:
could you please tell me how to do it manually? Thanks a lot
Click to expand...
Click to collapse
If you mean "how to trim manually" the easiest way is to follow LeBourrin's suggestion earlier in the thread and download the Trimmer app from the Play Store. It worked for me.
LeBourrin said:
It is done. I've installed your Trim kernel on my p4wifi with Lollipop ROM.
I'm not comfortable with terminal so I used Trimmer store app to trim partitions. All went well. No brick. :good:
Click to expand...
Click to collapse

Mainline Kernels

Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!

PieGuy128 said:
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
Click to expand...
Click to collapse
I am not an expert, but have learned a lot by tweaking the kernel for the Hp Touchpad. To my basic understating none of the native driver codes were release as they are not "open source". How the developers got it working is by tweaking the hardware from what is "based on". If the drivers where open source, it could possible be more helpful on getting a lot more done. All I can do is provide some links from others that had tried:
The LuneOS is using the same kernel branch as Android, but there is no development for the kernel:
https://www.webos-ports.org/wiki/Main_Page
https://www.webos-ports.org/wiki/Main_Page
It will be great to have a kernel to run Linux natively.
Here are some work around that others had used:
https://github.com/mikestaszel/ArchLinuxARM-TouchPad
https://github.com/CalcProgrammer1/kernel_tenderloin_debian
https://forum.xda-developers.com/showthread.php?t=2761381
I did the following videos running Ubuntu (arm) as Chroot and is very fast !
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
Good luck learning!

@PieGuy128
Take a look at this post from @elginsk8r about a possible 5.0 Kernel:
There is a 5.0 kernel floating around that looks promising (uses mesa rather than proprietary blobs for display) albeit missing some key hardware support in it's current state. If anyone would like to take a look at the kernel sources and see what can be done it can be found here https://github.com/flto/linux/tree/msm8660. Building and booting instructions are here https://github.com/flto/linux/wiki
original post:
https://forum.xda-developers.com/showpost.php?p=83040029&postcount=273