yashsingh1/xdaforums huggingface dataset:
[XPERIA X8 Original Android Development] stelios97:
i get this error when i try to compile kernel!

In file included from include/linux/netfilter_ipv4/ip_tables.h:28:0,
from net/ipv4/netfilter/nf_nat_rule.c:22:
include/linux/netfilter/x_tables.h:206:25: error: duplicate member 'match'
include/linux/netfilter/x_tables.h:207:14: error: duplicate member 'matchinfo'
CC net/ipv6/xfrm6_mode_beet.o
make[3]: *** [net/ipv4/netfilter/nf_nat_rule.o] Error 1
make[2]: *** [net/ipv4/netfilter] Error 2
make[2]: *** Waiting for unfinished jobs....
CC net/ipv6/mip6.o
CC net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.o
make[1]: *** [net/ipv4] Error 2
CC net/ipv6/netfilter/nf_conntrack_proto_icmpv6.o
CC net/ipv6/sit.o
CC net/ipv6/ip6_tunnel.o
In file included from include/net/netfilter/nf_conntrack_tuple.h:13:0,
from include/linux/netfilter/nf_conntrack_dccp.h:28,
from include/net/netfilter/nf_conntrack.h:23,
from net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.c:25:
include/linux/netfilter/x_tables.h:206:25: error: duplicate member 'match'
include/linux/netfilter/x_tables.h:207:14: error: duplicate member 'matchinfo'
In file included from include/net/netfilter/nf_conntrack_tuple.h:13:0,
from net/ipv6/netfilter/nf_conntrack_proto_icmpv6.c:23:
include/linux/netfilter/x_tables.h:206:25: error: duplicate member 'match'
include/linux/netfilter/x_tables.h:207:14: error: duplicate member 'matchinfo'
make[3]: *** [net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.o] Error 1
make[3]: *** Waiting for unfinished jobs....
CC net/ipv6/addrconf_core.o
make[3]: *** [net/ipv6/netfilter/nf_conntrack_proto_icmpv6.o] Error 1
make[2]: *** [net/ipv6/netfilter] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [net/ipv6] Error 2
make: *** [net] Error 2
[XPERIA X8 Original Android Development] Daveee10:
I'm got too with linaro... use GCC... That's working without errors
[XPERIA X8 Original Android Development] przemek4113:
have anyone tried to fix the cypress bug,tested the kernel on leatest MiniCM10 nightly and the touchscreen works very poor.Must use nAa jb 29. kernel:(
[XPERIA X8 Original Android Development] :
I'm sure they're trying, but it's not that easy..
[XPERIA X8 Original Android Development] _JoaoCampos:
Does anyone else have rather low volume on the earphones? Dunno if this is a kernel issue or a rom (latest nightly) issue.
[XPERIA X8 Original Android Development] leonardv128:
Yes i have too, just modify the equalizer values for earphones in DSP manager to max :laugh:
[XPERIA X8 Original Android Development] khestrell:
for me the volume is good, but the music playback is skipping and cracking, and the overall performance seems dropping while playing music. (which is awesome otherwise)
[XPERIA X8 Original Android Development] aminsetan:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

if i have mobile phone company,first man i will hire is you nAa..chief of development sector..and congratulations for new kernel and era..

Sent from my MT25i
[XPERIA X8 Original Android Development] xelyt:
screen flash after CRT-off animation

@nAa

I did some research about the screen flashing after CRT-off animation which is a kernel bug and i have found these two commits (this and this) that maybe could help fixing this bug. Hope this can help.
[XPERIA X8 Original Android Development] Daveee10:
no that's fixes the anomation show... If animation doesn't show on phone this patch make a little wait how animation shown...

But that's not needed because the frameworks base included patch for show animation...

and nAa's .32 kernel not using this patch, so the issue is caused by other thing...

but if he revert this commit in frameworks base: Revert "Revert "Triggering EarlySuspend based on BackLight brightness""[URL="https://github.com/MiniCM/android_frameworks_base/commit/71cdcff6bf6a91bc828ef3dfb4518db060cfee2e"][/URL]

then adding patch to kernel what you posted the issue solved...
[XPERIA X8 Original Android Development] Cancar96:
is this kernel using more battery than .29 or is is just me?
[XPERIA X8 Original Android Development] 2010matej:
I didn't try .29,bt on .32 battery time is very good!
[XPERIA X8 Original Android Development] CtrlAltDelIrl:
I agree.. Battery Life is great, even under very heavy use I'm getting a full day.
[XPERIA X8 Original Android Development] pradhana:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

I feel the same with you :D

Sent from my E15i
[XPERIA X8 Original Android Development] :
When the kernel was made, battery consumption wasn't a priority. They wanted to make everything work. Sure there will be fixes, but this is the first version, which works good. Mostly. But still, there are bugs like, cypress, battery consumption etc.
[XPERIA X8 Original Android Development] sonty:
on a good note ipv6 browsing now works without crashing the kernel somewhere in iptables. thanks a lot.
[XPERIA X8 Original Android Development] MatthewWu:
nAa, please make 2.6.32.60 kernel for Gingerbread.

I'm sure that if you make this kernel for Gingerbread, it will be the fastest and most stable Android ever. (Cause i've seen my dad's Samsung G Mini Phone and it's 2.6.30) :D
[XPERIA X8 Original Android Development] sgt. meow:
Team Fun (the team behind GingerDX) are already on it, and nAa is helping them if I know right.

Don't get too excited though. Stuff may not work, and if that's the case it won't be released.
[XPERIA X8 Original Android Development] pilu1978:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

I'm also working on a gb version. ;) The first look: the performance increased, but the gained extra performance is smaller than what you get with the jb version.

The todo list is long, need to fix the cypress bug (I can't do it, I'm on synaptics ;)), and need some adjustment to work correctly with gb roms. Anyway better than the older .29 gb kernels. ;)
[XPERIA X8 Original Android Development] nobodyAtall:
03 will be bootable on all Android versions >=2.3.

@pilu if you have any gb specific fixes you would like to push, let me know.
[XPERIA X8 Original Android Development] sgt. meow:
Damn man I wanted to achieve that. I was like this close.

Anyways good work nAa.

It was pretty obvious that you were going to beat me by a long shot.
[XPERIA X8 Original Android Development] TAJ_Rocks:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

@nAa happy to hear new v03 will be hit for x8

Because for members like us who use pc rarely mostly on fone so it will be easier to swap between gb, ics, & jb romz without changing kernel.

Cheers:beer:

SORRY FOR OT

Sent from my iXperiA 8s
[XPERIA X8 Original Android Development] pilu1978:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

@nAa: don't worry, if I found some valuable fix, I will inform you. ;) Now just reconfigured it, no real changes in the code. It must be work on gb. ;) The cm9 and cm10 is nice and good, but only the minicm7 good enough for daily usage.

And a question: "the bootable with all android>=2.3" equal with separated .32 kernels for cm7-9-10, or this is a hybrid solution (one kernel for all minicm)? If you talk about the second version, I will share my solution. :) Working on the same thing is only wasted time. ;)
[XPERIA X8 Original Android Development] Daveee10:
For cypress bug:

with .32 cypress files, the ts doesn't recognise the touches. but if the pressure values defined, like 255 and 0 for not touch maybe it will be work...

I make a test, edited the cyttsp_core.c file, but I forgot to change cyttsp_i2c.c file with original cyttsp-i2c file. And maybe that's need to edit because it containing some ABT_PRESSURE values.

The problem, how our touch panel doesn't recognise the pressure, so we need to predefine the minimum and maximum values for it, then it will be workable...
[XPERIA X8 Original Android Development] nobodyAtall:
03 boots on all android versions >=2.3. This means ONE kernel for all - we should really avoid fragmentation whenever we can.

I'm only testing with MiniCM roms but since this is pure CM, it should work for all roms like gingerdx, etc. There are some issues with GB roms though which I'm not gonna spent time fixing.
[XPERIA X8 Original Android Development] pilu1978:
Hey man, you made my work! :) ;) :D

And how to made it? I used this method: start the phone with a clean init.rc -> if any event happened (touch/key) start a boot menu to select the recovery (if more than one exists) or other things (filemanager/multiboot) -> identify the rom type, kill/umount everything and chroot to the correct rootfs (depends on the rom version).

I know, several other method exists, but this is not need anything (mounted images/external ramdisks, etc like other devs making it).
[XPERIA X8 Original Android Development] :
We can get a special kernel integrated multirom?Like this:http://xdaforums.com/showthread.php?t=1304656

Running (gb/ics/jb)init by a modified init would be better than chrooting.
[XPERIA X8 Original Android Development] nobodyAtall:
I don't really like chrooting. It causes more problems later on.

Single init - single ramdisk suitable for the android version you are using. Simple, elegant, effective.
[XPERIA X8 Original Android Development] pilu1978:
Ok, maybe I not understand correctly your previous post. :)

The one kernel for all os is a kernel with a ramdisk for every rom (like the method what I made) OR you want to merge the kernel binaries into one (no more separated repo for gb/ics/jb), and we can use separated kernels for each version with SAME kernel image and DIFFERENT ramdisk?

Now:

- for gb: gb kernel image (from gb branch) + gb ramdisk

- for ics: ics kernel image (from ics branch) + ics ramdisk

- for jb: jb kernel image (from .29 jb branch/.32 repo) + jb ramdisk

The future will be this?

- for all android version: the common kernel image + the rom specific ramdisk?

Sorry if I misunderstand you :)

P.s.: yes, we need to be extreme careful with chroot. :) It can be an easy way to make an unstable system. :D

EDIT: Ok, I read again your last post :) So, the kernels will be different (.32-gb, .32-ics and .32-jb) BUT it will base on same code. You need to compile only one kernel image, and the ramdisk will be compiled from the rom source, not need to compile kernels for each android version. :)

Sorry, sometime I'm read only every 2nd line, like the most members... ;):D
[XPERIA X8 Original Android Development] sgt. meow:
How will a GB ROM boot on a JB ramdisk?

I just wanna know because I can't seem to figure it out (which is expected because I pretty much suck at devving).
[XPERIA X8 Original Android Development] darkfrmr:
something like this? original .29 cyttsp_core.c had the same problem and it was modified based on that commit I think...
[XPERIA X8 Original Android Development] Daveee10:
thats not enough... Need some change on cyttsp-i2c.c and need edit makefile how using cyttsp-i2c.c not cyttsp_i2c.c
[XPERIA X8 Original Android Development] paulebe525:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Some times lag on touch
[XPERIA X8 Original Android Development] ElmirBuljubasic:
R: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Aha, thanks for your spam...you cant read? Its a known bug
[XPERIA X8 Original Android Development] Bunny2rock:
You are awesome dude!!! What eh Question!!! :laugh:
[XPERIA X8 Original Android Development] nobodyAtall:
Don't complicate things that much.

This is how it's done:

- 1 kernel Image,

- 1 recovery

- 1 kernel ramdisk with init, init.rc, etc from each android version >=2.3

- kernel starts and checks which android version is installed

- kernel boots into android using the correct stuff

boot image size is kept minimal and there is no reason to chroot -> win-win !

I hope its clear now :)
[XPERIA X8 Original Android Development] pilu1978:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Yes, everything clear. ;)

It was only a fast solution (what is good for me ;)), but I know lot of more elegant method exists. :) (segmented init files with on:property tags to separate the differences between the different versions, modded init binaries what can load different init files depends on the rom version, etc, etc...).

Usually I making stuff for myself only, not for public release. ;) If I found a 2 minutes long elegant solution, and an 1 minute long hacked solution, I will make the hacked version. :D But I'm only an x8 owner with near zero free time, and you are the leader x8 developer. :D

Last question: you found a solution to the different partitioning? For the jb the standard partitioning is not good, and for gb the 260mb system is only a wasted space.

Ok, no more question, instead of useless talking, trying to find possible bugs and/or optimisations. ;)

Edit: and thanks for your replies to answer my (sometime idiot) questions. ;) My main playground is the ocr/opr/security apps, not android, this is your speciality... :D
[XPERIA X8 Original Android Development] nobodyAtall:
Partitioning is one: the JB one. This cannot be changed after mtd is detected and initialized.

It's not wasted space even for gb, It can easily be used for stuff in /data e.g. via symlinks.

P.S. you should always go with the cleanest method. Even if it needs more work to develop - it will save you tons of bugs later on ;)
[XPERIA X8 Original Android Development] pilu1978:
Yes, the cleanest method is always the best. :) But I use too much clean method in my real work, need to do something "dirty"... ;)

Okay, no more chatting. :D

Small fix to solve the the mddi_on: clk_set_min_rate failed errors with hitachi screen (this is exists in all .29 kernel too). :)

In the board-delta.c under the static void __init msm_mddi_hitachi_hvga_display_device_init(void) change the mddi clocks to:

[COLOR="Sienna"]panel_data->panel_info.clk_rate = 10000000; //153600000 original values, same as than the toshiba mddi clocks;
panel_data->panel_info.clk_min = 9000000; //150000000;
panel_data->panel_info.clk_max = 11000000; //160000000; [/COLOR]

The clock values ripped from a P500 .32 kernel (franciscofranco), the P500 use hitachi and novatek mddi panels.

And little cleanup in the configs:

#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
[COLOR="Red"]CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y[/COLOR]
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
[COLOR="red"]CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_MC44S803=y[/COLOR]
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
# CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set

The red lines is not needed (analog/digital tv tuners), later I will check the other drivers, the two TEA576x is FM tuner maybe needed.

Or you have informations about the fm receiver in these phones?

And about the partitioning: You don't like the chrooting, I not like the symlinks and partitioning... ;) :D You are right, we can place stuffs from /data to /system really easy. :) BUT we can place stuffs in the JB roms from /system to /data too. :) Both direction need a little work in the recovery, if we place stuff from /data to /system with gb roms, we need to extend the format /data function (with remove the folders in /system what we moved from /data), and if we place /system components into /data, we need to use remove all folders from /data (except the linked ones) instead formatting the partition.

Anyway, the JB roms filled with 10 megabytes of trash. :( (near 10 MB 1600x1280 and 1920x1080 sized wallpapers in trebuchet, some big sized picture in framework-res, etc, etc...). And all not important apks moveable to /data/app (themes, wallpapers) to fit the JB into the standard partitions. ;) With a small "dirty work" the gapps package can be smaller too (remove all unnecessary resources (hdpi-xhdpi-etc...)).

Now go back to discover the bugs in the .32 code, and find solutions to make it cleaner, faster... :D
[XPERIA X8 Original Android Development] jimmkind:
Why not compile 2 different kernels with 2 different mtd schemes. One for gb and one for ics/jb. Personally i think you should stop maintain ics completely. Gb is stable and jb is the latest
[XPERIA X8 Original Android Development] pilu1978:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Basically this is not true. The LatinIME.akp is more than 20MB due the built-in dictionaries. If you use another app WITH DICTIONARIES, you can't get more than 5-10MB. :) But this is true, the standard app is a "free space killer monster". ;) But this is a kernel developer thread, better if we share the rom related ideas in the MiniCM10 thread, or better if we open a new thread in the general section: "How to make smaller JB" or something similar... ;):D
[XPERIA X8 Original Android Development] eagleeyetom:
Okay, it's true that we've been playing a bit with .32 kernel.

Here's the proof that kernel boots on Gingerbread.

Overall performance is better than .29 (3100 points w/o sd-card, oc and KSM on GDX v030).

The two bugs tracked so far:

Camera preview - photos are taken but the preview isn't working.

Audio doesn't work.

Probably we need to rewrite the libaudio to force CM7 to work on .32 and about camera preview I'm not quite sure as I'm not a skilled dev like dx or nAa.

Anyway I provided some logs:

Audio when I was trying to run music player

Camera and two photos taken

Both logs were taken on GingerDX with reverted KSM support (gave bootloop) and clean installation.

Any help will be appreciated.
[XPERIA X8 Original Android Development] nobodyAtall:
Hi folks,

Here's the changelog for nAa-03:

Performance is improved, battery life is better. One kernel to rule them all :)

We are checking for regressions - kernel will be released once we are ready to say that all is good.
[XPERIA X8 Original Android Development] androidbpb:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Hi nAa, will you be adding Slide2Wake module to the kernel (for mimmi as well) as discussed in below thread:.

http://xdaforums.com/showthread.php?t=2117349

Thanks for your awsome creation.
[XPERIA X8 Original Android Development] Mockingbird:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

the 03 has cypress issue fixed ? I dont see it listed there
[XPERIA X8 Original Android Development] CKKnot:
Old good X8 with cypress are hard to get now, Or perhaps yours do it's rat lab?;)
[XPERIA X8 Original Android Development] Mockingbird:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

I dont get it
[XPERIA X8 Original Android Development] vuiseng:
this naa can use for GDX ??
[XPERIA X8 Original Android Development] effective:
When 0.3 version of the kernel comes out youll be able to use it with GDX
[XPERIA X8 Original Android Development] vuiseng:
okok :good:...........i will wait for it :laugh:
[XPERIA X8 Original Android Development] przemek4113:
I m too waiting for the new version, but if you have cypress digitizer like me,the touchscreen will work very poor and not recognize all touches.Maybe this problem with cypress will be slowed in next nAa 03,but i m not sure.
[XPERIA X8 Original Android Development] ->Sid:
Re: [KERNEL] 2.6.32.60-nAa-jb-02 [6/2/2013] Custom JB kernel + CWM Recovery

Any inside news regarding cypress bug in 03 version, i really can't wait now for 04th version for that bug to be removed, i want to use these kernel..:( :crying:
[XPERIA X8 Original Android Development] nobodyAtall:
nAa-03 is released. Note that the fact that this kernel version is bootable for other ROMs besides MiniCM10 does not mean that they are supported by this kernel.

There are ROM fixes that need to happen, thus, as usual I strongly suggest using this kernel with MiniCM10.

Cheers,

nAa.
[XPERIA X8 Original Android Development] Cancar96:
Re: [KERNEL] 2.6.32.60-nAa-jb-03 [16/2/2013] Custom JB kernel + CWM Recovery

with great kernel comes great thanks.
[XPERIA X8 Original Android Development] Amrooz:
For those who ask about cypress.. it is not fixed
[XPERIA X8 Original Android Development] Soniakos:
So, Cypress not work - I am not HAPPY :(
[XPERIA X8 Original Android Development] bbalint96:
Have you been able to fix the msm_serial_hs_dma wakelock bug, that drfr has pointed out? (I can't check it for myself, U20 user here :) )
[XPERIA X8 Original Android Development] Vitruvian:
Nothing new about us with cypress, we just desperetly waiting this bug to be fix, i hope will be fixed soon :'(
[XPERIA X8 Original Android Development] eagleeyetom:
Complaining about cypress won't speed up the development. Make logs and post them here.

Sent from my X8 using Forum Runner
[XPERIA X8 Original Android Development] Heronger:
If you want cypress to be working, than try to solve the problem for yourself.

I think nAa isn't working anymore on fixing the cypress issue, because he doesn't have a cypress device.
[XPERIA X8 Original Android Development] matmutant:
hey x8 users, do you have same 2D (little) boost as i had during testing? (on mini)

previously :

now :
[XPERIA X8 Original Android Development] Renegeits:
for me, after flashing latest kernel, when I turn on phone it's showing just a black color
[XPERIA X8 Original Android Development] nobodyAtall:
VDD interface

Hi folks,

For 03 I've ported the vddlevels functionality from msm7x30 so that we can variably change the voltage level of the frequency we want without the need for external modules.

The current voltage information is available at:

E.g. the defaults after flashing the kernel should be:

To change for example the voltage level of the 122880 frequency, you could do:

If you cat this file again, you should see that the voltage level is picked up. The new voltage level is picked up when the CPU will scale to the particular frequency level.

The undervolting tickbox in the 'Performance Settings' of the latest MiniCM10 nightlies already uses the new interface. The values that are set there are the same ones as those passed by the old undervolting module:

Do I need undervolting?

You dont NEED undervolting. It can save though hours of some battery life during the day.

Overvolting?

Even though the interface allows you to overvolt, I don't suggest doing so. It will result to instabilities or crashes and is totally unsupported.

Performance?

Undervolting decreases the performance results - this is to be expected.
[XPERIA X8 Original Android Development] Cancar96:
is triple buffering going to work on roms with lower android version,since it is a kernel feature?
[XPERIA X8 Original Android Development] ElmirBuljubasic:
R: [KERNEL] 2.6.32.60-nAa-jb-03 [16/2/2013] Custom JB kernel + CWM Recovery

Im getting black screen too sometimes
[XPERIA X8 Original Android Development] mile18:
also black screen after boot, nothing hapens, fix anyone?
[XPERIA X8 Original Android Development] tiestobunio:
Dear users of this forum xda developers:)

Please do not ask NobodyAtall and the rest of the project team or theme some patches for cypress digitizer

He has done quite a lot of work one can do fixes for Cypress does not bother him no such questions as you can? enough already done for us ... Let us do it and wait for the results because of what I see is the developer of nAa does for us something we did not expect the kernel of 2011 on our x8 and see how many years have passed and we naa further supports

Congratulations nAa and rest of this project:highfive:
[XPERIA X8 Original Android Development] Lajbymester:
Install the latest MiniCM10 nightly and then the gapps-jb on an older nAa-jb kernel, and then flash this nAa-03 kernel and it will boot.