yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Original Android Development] pradipsoman:
Cant just flash it. 6.6.1 is for old BB. So you will have to flash old BB to try that and then again reflash the new BB to come back to 7.2...There is a BB fix but then it will rob you of some functionalities...
[Optimus One, P500 Original Android Development] vlt96:
He was talking about kernel, that guy has old baseband already, he wondered if the kernel works on the ROM
[Optimus One, P500 Original Android Development] ravidahiya74:
any bug with stock gb rom??
[Optimus One, P500 Original Android Development] DJNoXD:
Make a backup and try it, then we will know. ;)

As I wrote in the first post, I haven't tried.

I guess it should work.
[Optimus One, P500 Original Android Development] DeuxEx:
I tried some of your kernel version 2.2.2(caveman+vsync, caveman+vsyncOFF, vsyncOff) on Oxygen Rom (latest), but I experienced a few bugs: misplaced screen, crashing apps, problem with finding market apps (a don't know if is related...), and yes, problem with GPS. I tried this kernel only on Oxygen ROM.
[Optimus One, P500 Original Android Development] Cresqo:
The only problem with I had with this kernel with oxygen ROM that it makes the ui not fluid or smooth...on cm7 its better
[Optimus One, P500 Original Android Development] carrthee89:
Anybody tried this kernel with omfgb rom?
[Optimus One, P500 Original Android Development] DJNoXD:
No more touchscreen lockups happen, since I have changed the workqueue and have recalibrated TS twice (used "Nook Screen Calibration").
[Optimus One, P500 Original Android Development] GonDr:
Any update soon ?
[Optimus One, P500 Original Android Development] DeuxEx:
Not only the UI is not fluid/smooth, but also some games and apps: Androizip, Pirates - Master of the Sea, Angry Birds Space. But, I repeat myself, only on Oxygen Rom.
[Optimus One, P500 Original Android Development] k2n3:
hey randolf i'm use your kernel on oficial cm last nightly and works great!!!! congrats and keep going good work:D
[Optimus One, P500 Original Android Development] DJNoXD:
Maybe you you like to try if my personal 2.3 fixes not fluid/smooth things on oxygen. This version has higher axi frequence.

@k2nr

Thanks, I'm happy to hear that. :)

v3 kernel:

At this evening I will continue the work on my new kernel (kernel source 3.0.31).

Sometimes its realy annoying. Very much time is needed to get minor results. :(

I have started min 4 times from the beginning :(, but learned much (main thing was how to start) ;).

So this evening I will start to add the first parts realy needed for our phone.

Hope it wont take so long to get a first (only booting) version.
[Optimus One, P500 Original Android Development] DJNoXD:
Could someone tell me how to remove the poll from this thread?
[Optimus One, P500 Original Android Development] neko95:
> hi dj.. just flashed 2.2.2, I did not find un 2.2.2 changelog.. scheduler is deadline by default? or its just me?
[Optimus One, P500 Original Android Development] DJNoXD:
Changelog can be found in second post.

Default scheduler is not changed.

These are the changes in v2.2.2:

- Advanced Routing enabled

- tun and cifs build into kernel (no longer provided as module)
[Optimus One, P500 Original Android Development] GonDr:
hi DJNoXD i like ur kernel but i have question, is it only me, i always feel ur kernel not very smooth like franco kernel, but i can say ur kernel is most kernel good for battery life i had ever, thank you

CM7 RC2 latest
[Optimus One, P500 Original Android Development] DJNoXD:
There a two modifications which could cause.

- axi frequ (default value in 2.2.2 because of max stability. Before I used a higher value.)

- cahnged workqueue setting in touchscreen driver

You could test my personal v2.3 testing version (@github or @googledrive). In this version again a raised axi freq is used . I you try please tell me if it feels smoother.
[Optimus One, P500 Original Android Development] russian392:
Thanks I love you for this kernel it's just what I needed.

I was begonias work on my own kernel and I find this infamous genius, +1.

Than.

Tested on mini for optimistic one, oxygen, cm9
[Optimus One, P500 Original Android Development] scout1089:
hi dj can you bring back NOOP i/o scheduler? :D IMHO, its saves power..
[Optimus One, P500 Original Android Development] GonDr:
i don't know how to download v 2.3 from ur google drive ! :(

Edit : i dowloaded it, never mind thanks will test it
[Optimus One, P500 Original Android Development] DJNoXD:
It will be enabled again. I will tell you if I have build a new version.
[Optimus One, P500 Original Android Development] DJNoXD:
@scout1089

New v2.3 with noop enabled is up.

Please try if you can select.
[Optimus One, P500 Original Android Development] DJNoXD:
I have created a website for my kernel. link

The complete changelog of all versions can now be found at that website.

Therefore changelogs are / will be removed from all other places.
[Optimus One, P500 Original Android Development] scout1089:
you are the next francisco franco...

thank you :)
[Optimus One, P500 Original Android Development] am486:
I am now testing v2.3 with RC2, no bugs so far, your kernel is good.
[Optimus One, P500 Original Android Development] Cresqo:
I tried it on stock LG gingerbread ROM and it's works fine, except for sometimes screen is unresponsive(usually after a reboot or a flash)
[Optimus One, P500 Original Android Development] Kvidli:
Same thing here... Flashed it with stock and it's kinda laggy and unresponsive, tried 2.3 and 2.2.2 :/
[Optimus One, P500 Original Android Development] Lycan:
Its a modded CM kernel, therein its in this section.
[Optimus One, P500 Original Android Development] deniso177:
This might help

http://book.git-scm.com/3_basic_branching_and_merging.html
[Optimus One, P500 Original Android Development] Lycan:
So will this :

http://gitready.com/

:D
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for the links. :)

The touchscreendriver from derCaveman or the default can be easy selected in the build config.

So I have decided to do the same with vsync.

Than it should easyly be possible to build that version without changing the brances.

With that it would be easy for me to build version with camandriver vsync on/off / default touchscreendriver vsync on/off (if needed).

included in next kernel (v1.3) if tests are ok for me:

v1.3:

- included touchscreendriver from DerCaveman

- mcs6000_ts: fix cpu load 100% (mik_os)

- vSync disabled (added compile switch)

- some backport from 3.3 kernel (if it works)

- Lower radio/event log for more ram (wingrime)

- Fast Sleep, wake lock timer change. (wistilt2)

- Set correct divx codec type (francisofranco)

- Wifi set to FAST (roqu3)

- ashmem: fix deadlock when system is low on memory

- fs: simple fsync race fix

- msm cpufreq Improve initial frequency selection - CodeAurora

- staging: android: lowmemorykiller: additional minfree values added

- faster writeback

- cgroup: speed up access to cgroupfs mounted entries in /proc/mounts (…

- Fix memory leaks from the wifi drivers (franciscofranco)

- Increase readahead to some more reasonable values (franciscofranco)

- some code optimisations

Should I make these two kernel version next?

1. Caveman touchscreendriver + vsync off

2. default touchscreendriver + vsync on
[Optimus One, P500 Original Android Development] GonDr:
what about Caveman touchscreendriver + vsync on ?
[Optimus One, P500 Original Android Development] deniso177:
With v-sync having it of really doesnt do anything but raise benchmarking scores, but with it on, majority experience smoother performance and no screen tearing. But as for der_caveman I really cant judge, but I know Roqu3 reverted back to stock touch screen driver, and make the caveman available as an extra
[Optimus One, P500 Original Android Development] DJNoXD:
Ok, than I will make four versions and we will see which will be best.

Caveman + vsync on

Caveman + vsync off

default + vsync on

default + vsync off

After we have tried, we can skip some of them.

@deniso177

One reason to start with the kernel was that sometimes my touchscreen does not response. After pressing power two times it is fine again for some time. Thats why I try the caveman driver. Till now (with caeman driver) it does not happen again to me.

But I will take a look at the touchscreen drivers, to find out what happend.
[Optimus One, P500 Original Android Development] GonDr:
Thank you, waiting. :o
[Optimus One, P500 Original Android Development] DJNoXD:
v1.3 with cavman driver and vsync off is up.

Other versions will follow later.

kernel reverts will be in a later versions.

It takes longer than I tought.
[Optimus One, P500 Original Android Development] DJNoXD:
- all four version are up

- add kernel version to thread title
[Optimus One, P500 Original Android Development] neko95:
> i'll try ur v-off with dercaveman touch fix.. :)
[Optimus One, P500 Original Android Development] mDroidd:
Now this is a nice changelog :)

Keep going !
[Optimus One, P500 Original Android Development] neko95:
> dude i flashed v1.3 touch fix+voff.. but its not vsyncoff.. i can only attain 63.4 fps at neocore.. it should be atleast about 74 if it is vsync off
[Optimus One, P500 Original Android Development] DJNoXD:
I will check that.

Have you tested the vsync on version?

Maybe there is an error in code with the compile switch.

Edit: Found it.

Will compile and upload the fixed version this evening.
[Optimus One, P500 Original Android Development] thachtunganh:
Haha, you are a funny people... how can you update from. 35 kernel to. 37 kernel with a patch.....
[Optimus One, P500 Original Android Development] DJNoXD:
"Update" is maybe the wrong word.

But I think you know what I mean.
[Optimus One, P500 Original Android Development] neko95:
> have you updated the touchfix w/ voff? I'll test it
[Optimus One, P500 Original Android Development] DJNoXD:
Only source is updated.

Kernels are the old one.

This evening I will compile the new ones.

The new ones will get v1.3.1 as version tag (to avoid confusions).

Thanks for testing. :)
[Optimus One, P500 Original Android Development] neko95:
> ok.. I'll wait for it :)

> i had tried you v1.3 w/touch fix.. everything goes smooth .. so far so good, i had no complains..
[Optimus One, P500 Original Android Development] DJNoXD:
v1.3.1 is online
[Optimus One, P500 Original Android Development] DJNoXD:
Everyone who is trying to help me.

Thank you for your help.

About problems with other roms than cyanogen:
[Optimus One, P500 Original Android Development] scout1089:
hey dj where is the kernel with cfs version 2.3 in your Google drive? :o
[Optimus One, P500 Original Android Development] DJNoXD:
Its included, but sio has been set as default.

So you have to change it yourself (for example by using nofrills).
[Optimus One, P500 Original Android Development] storm11:
You are talking about the I/O Schedular , he's asking about cfs task schedular :) correct me if I'm wrong
[Optimus One, P500 Original Android Development] DJNoXD:
I tought he was talking about i/o sched.

But I think your understanding is the correct one.

about cfs task schedular

There was never a special version for that (only the TS driver and vsync version).

As far as I remember I havent changed anything since the first v2 version about that, so it was never there.

I will check this evening. If its disabled and it can be enabled
[Optimus One, P500 Original Android Development] DJNoXD:
Cfs task schedular is now enabled.

v2.3 is updated (uploaded).

Please test it.

Edit:

CM feels faster now
[Optimus One, P500 Original Android Development] scout1089:
thank you..can we also have a vsync on version? :D

agree...cm7 is snappy...:eek:
[Optimus One, P500 Original Android Development] seriousia:
2.1.1 vsync off is more responsive than 2.2.2 vsync off

And don't know why in 2.2.2 screen misses my touch and its not responsive as compared to 2.1.1

But it feels very smooth.

Great work btw

Thanx :D
[Optimus One, P500 Original Android Development] Cresqo:
Oops, i mean sometimes touch doesn't work on the lockscreen (usually after a reboot or a flash), pls edit your changelog website:)
[Optimus One, P500 Original Android Development] ZonbekaUnlimited:
@DJNoXD: are you gonna build "non caveman" or vsyng on versions??, I get hell alot of lag while scrolling touching screen with your 2.3 :(
[Optimus One, P500 Original Android Development] am486:
I got some random reboots with the v2.3 kernel on the RC2 so i decided to go back to v2.2.2, now is all fine.
[Optimus One, P500 Original Android Development] GonDr:
+1 sometimes i miss touch screen too and not very responsive in 2.2.2 and 2.3 don't know why!
[Optimus One, P500 Original Android Development] DJNoXD:
For the moment v2.3 is not release. That's the reason why I only made one version (its my testing version).
[Optimus One, P500 Original Android Development] DJNoXD:
Its changed.
[Optimus One, P500 Original Android Development] DJNoXD:
I guess its because of that what I have changed in v2.2 to fix the rare problem with Touchscreen driver that I and some people have (ts driver stops working).

(using high priority (non-delayed) workqueue for TS driver)
[Optimus One, P500 Original Android Development] DJNoXD:
Uploading all four versions of v2.3 is finished.

Changes:

Enabled SCHED_DEBUG for better control of CPU scheduler

CFQ Group Scheduling support and hierarchical scheduling support in BFQ enabled

max_axi_khz set to 422400

vfs_cache_pressure = 100

cfs task (block) schedular enabled

noop scheduler enabled

tried something to about "white noise if display is enabled"

some more debugging disabled
[Optimus One, P500 Original Android Development] allenwalker1998:
What does max_axi_khz do?
[Optimus One, P500 Original Android Development] DJNoXD:
AXI = AMBA

A

dvanced e

X

tensible

I

nterface

7x27 doesn't allow graphics clocks to be run asynchronously to the AXI bus.

So AXI bus frequency also sets the frequency used for graphics clock.

The default value is 160000 for power savings.
[Optimus One, P500 Original Android Development] thachtunganh:
Randolf, Have you see any improve when you enable block IO control???
[Optimus One, P500 Original Android Development] DJNoXD:
I can't tell you any facts about improvments. (For me system feels a bit better)

What I can say is, that I havn't seen any disadvantages after I enabled it.
[Optimus One, P500 Original Android Development] thachtunganh:
I enabled for CFQ cgroup support once, and it slowed down my phone...
[Optimus One, P500 Original Android Development] DJNoXD:
How did you recognize the slowdown?
[Optimus One, P500 Original Android Development] ZonbekaUnlimited:
@DJNoXD: I've tried all your 2.3 kernel flavours, but they all give me lag while scrolling touching screen
[Optimus One, P500 Original Android Development] seriousia:
+1
[Optimus One, P500 Original Android Development] thachtunganh:
Enabled it , test a game, it slowed down.

Then i disbale Block IO control, compile, test a game, it isn't slowed down....

Then i try to turn of the cgroup control, compile, test the game and some apps, it's better!
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks :)

I will test it (if I have a free time) and tell you.
[Optimus One, P500 Original Android Development] DJNoXD:
Is it first time in v2.3 that you recognized?
[Optimus One, P500 Original Android Development] DJNoXD:
kernel 3.031 update

Lots of compile errors are fixed (and even more will follow).

Now I have to add drivers to fix some more compile errors.

WLAN drivers are included.

Now I am adding kgsl drivers.
[Optimus One, P500 Original Android Development] neko95:
> Hi DJnoXD, I guess its time for you to ask our assigned moderators to move this thread at Original development section. I personally believe it belongs there.
[Optimus One, P500 Original Android Development] dnle71:
+1
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks to all for your support. :)

I have asked about.
[Optimus One, P500 Original Android Development] GonDr:
+1

---------- Post added at 02:36 PM ---------- Previous post was at 02:31 PM ----------

its nice new, btw what about touchscreen ?
[Optimus One, P500 Original Android Development] DJNoXD:
For 3.0.31 there's still a long way and lots of drivers needs to be included. (and TS driver is included ;))

But its useless until I can compile the kernel without errors.

About v2.3 TS response:

I forgot to ask you and seriousia if you want to try a version without that change which I think is the reason of your TS response problem.
[Optimus One, P500 Original Android Development] seriousia:
yea I'm ready to test some testing kernels. :D

Btw I'm using 2.3 default vsync off

now and its touch response is better than 2.2.2 vsync off

:)
[Optimus One, P500 Original Android Development] GonDr:
+1 i'm ready too
[Optimus One, P500 Original Android Development] DJNoXD:
@seriousia and GonDr

Caveman or default TS driver as testversion?
[Optimus One, P500 Original Android Development] FitAmp:
Caveman first
[Optimus One, P500 Original Android Development] seriousia:
Well I'll prefer default TS driver with vsync off first. :)
[Optimus One, P500 Original Android Development] GonDr:
we can test both
[Optimus One, P500 Original Android Development] DJNoXD:
I know. ;)

But I hoped that I only have to build one. :)

Ok, I will make both, but only vsync off.

You can test tomorrow evening.
[Optimus One, P500 Original Android Development] DJNoXD:
Its not evening in germany, but I have created the testversions. ;)

v2.4-caveman-vsyncOff

v2.4-default-vsyncOff
[Optimus One, P500 Original Android Development] seriousia:
Ok i have flashed new 2.4 default vsync off

I don't feel much difference :p but yes touch is now more responsive. :D

And it is better now :cool:

Thanks for testing kernel.

:) :)
[Optimus One, P500 Original Android Development] DJNoXD:
Thank you for testing. :)

The changes in v2.4 testing are:

- OC 806+ MHz

- TS testing
[Optimus One, P500 Original Android Development] seriousia:
One thing i wanted to ask you that before i was using hephappys cm9 the ui was not smooth as gb but the touch response was just awesome.

100% ics touch response = like 80% or 85% of gb

Both kernels are cm based then why ?

EDIT:

sorry i meant 80% of ics = 100% of gb :D

p
[Optimus One, P500 Original Android Development] DJNoXD:
Good question.

I think there are two possible reasons.

- ICS is more efficient and therefor TS also works better

- hephappy has something changed in his kernel

Have you tested the GB CM kernel with cm9? (I know lots of things wont work with it)

If GB kernel has the same touch response on ICS like on GB than its something about kernel.
[Optimus One, P500 Original Android Development] seriousia:
Its not booting up with testing kernel.
[Optimus One, P500 Original Android Development] DJNoXD:
I will take a look at haphappies TS source. Maybe I find something changed.
[Optimus One, P500 Original Android Development] vlt96:
WTF??? GB has no smoothness for me, I can say 100% that my nokia 2330 is much much smoother than GB on P500... ICS has HW/A, which brings us smoothness
[Optimus One, P500 Original Android Development] seriousia:
GB is buttery smooth for me in apps as well as in system UI :cool: but in ics except app drawer, setting menu, browser everything else lags like hell like opera, xda, uc browser, es filemanager, root explorer etc. etc. :p

Or i can say they are not smooth in ICS as compared to GB.

but really i love ics :D
[Optimus One, P500 Original Android Development] GonDr:
testing v2.4-caveman-vsyncOff

Damn time boot now is very fast, in v 2.3 and 2.2.2 time boot was take +2 minute, in 2.4 time boot now is 1:15 minute and apps loading faster than before, very nice

touch is more responsive now and ui is smooth but has cpu spike, cpu is 100% when touching the screen (tested via system tuner pro app)

i see IO scheduler is sio, i guess noop is better for speed and battery but i'm not sure.

will report more when i find more info

Thanks DJNoXD for your great kernel

Rom : CM7 Official latest nightly 20-5-2012
[Optimus One, P500 Original Android Development] seriousia:
Booting time is same as 2.3 for me.

And yes that cpu spike bug is still present.
[Optimus One, P500 Original Android Development] DJNoXD:
For caveman I think I forget to implement it.

For default it is possible that I deleted it while creating this version.

I will check and tell you the result.
[Optimus One, P500 Original Android Development] DJNoXD:
Caveman driver is updated. Please test.

v2.4-caveman-vsyncOff

v2.4-default-vsyncOff

[SIZE=4][B]Changelog v2.4 testing 2012-05-24[/B][/SIZE]
- TS: caveman: fix cpu 100%
- governor added: minmax
- giving the kernel a name :-)
- Revert "touchscreen: using realtime (non-delayed) workqueue"
- Higher OC values enabled
[Optimus One, P500 Original Android Development] DavisNT:
I also have slow SDcard read speed with this kernel.

AnTuTu shows: 1.8 MB/s read; 3.8 MB/s write

With CM 7.2 optimized stock kernel AnTuTu shows: 6.1 MS/s read; 3.6 MB/s write
[Optimus One, P500 Original Android Development] DJNoXD:
I have written to yuripg1 if he could tell me if he has changed something.
[Optimus One, P500 Original Android Development] DJNoXD:
Can someone help me with this error?

Below its the complete compile error log.

CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: »include/generated/mach-types.h« ist bereits aktualisiert.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC arch/arm/mach-msm/socinfo.o
/tmp/ccuUhKjM.s: Assembler messages:
/tmp/ccuUhKjM.s:701: Error: constant expression required -- `mrc p15,0,r3,c0,c0,CPUID_MPIDR'
make[1]: *** [arch/arm/mach-msm/socinfo.o] Fehler 1
make: *** [arch/arm/mach-msm] Fehler 2
[Optimus One, P500 Original Android Development] GadgetCheck:
Thread Moved
[Optimus One, P500 Original Android Development] DJNoXD:
Thank you :)
[Optimus One, P500 Original Android Development] DavisNT:
With CM 7.2 RC1/RC2 stock kernel results are very much like with yuripg1 optimized: 5.5 MB/s read; 3.4 MB/s write
[Optimus One, P500 Original Android Development] GonDr:
there is a big problem in caveman+vsyncOff

touch is take a very long time to responsive, i must long press !! there is a very big delay in touch !!
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for testing.

Will check it again this evening.
[Optimus One, P500 Original Android Development] DavisNT:
Also setting /sys/devices/virtual/bdi/179:0/read_ahead_kb to 128 (as it is in CM7.2 stock kernel) in this kernel doesn't help.
[Optimus One, P500 Original Android Development] DJNoXD:
My results a very close to yours.

Later I will a look at my changes.
[Optimus One, P500 Original Android Development] thachtunganh:
Hey DJ :D

Can i ask you 1 question?

Do you know in the kernel, where the VM Heapsize values is?
[Optimus One, P500 Original Android Development] DJNoXD:
I guess the default used, if not defined in build prop, is here:

arch\arm\mach-msm\smd_private.h

#define SMD_HEAP_SIZE 512

But I don't feel 100% safe about that
[Optimus One, P500 Original Android Development] FitAmp:
V2.4 caveman vsyncoff. Screen was very unresponsive, wasn't even able to unlock phone or reboot
[Optimus One, P500 Original Android Development] DJNoXD:
I know. Will check it later.
[Optimus One, P500 Original Android Development] DavisNT:
Want to report 2 more problems:

1. WiFi is slower than with CM 7.2 stock kernel - only about 15 Mbps down; 8 Mbps up (about 19 Mbps down; 22 Mbps up with stock kernel)

2. I noticed touchscreen bug (2.3. default+vsync) - when I tried to longpress phone reacted like I would pressed and released several times (several times tried to get context menu for an item in Astro, but always opened it)
[Optimus One, P500 Original Android Development] DJNoXD:
1. How did you test?

2. I have changed the samplerate back to 10 (default cm value)

please test 2.4 testversion
[Optimus One, P500 Original Android Development] DJNoXD:
Updated version is uploaded.

Everthing is reverted now (=unmodified caveman driver)