yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Original Android Development] DJNoXD:
Kernels are updated

v2.4-caveman-vsyncOff

v2.4-default-vsyncOff

Changes:

- TS problems should be solved

- tried something about sdcard speed (but still working on it)
[Optimus One, P500 Original Android Development] DavisNT:
You are working fast! :):cool:

I tested WiFi speed with Speedtest.net Android app (WiFi connected to Wireless N router and 100 Mbps internet link). Tested, reverted kernel and tested again.
[Optimus One, P500 Original Android Development] scout1089:
hey dj can you add interactiveX governor again? i used that governor for daily use(1.5 days is enough) without any problems, smartass seems to drain power a bit faster than it. Since i dont play games, IMHO, interactiveX + NOOP = good for everyday use(well balance, saves power, smooth and good performance). 672max, 480min. Your kernel is getting better and better, thank you.. :)
[Optimus One, P500 Original Android Development] DJNoXD:
I haven't removed it.

But I have added minmax governor, so maybe you have to scroll down to see interactivex

Which tool do you use to select governor, cyanogen?
[Optimus One, P500 Original Android Development] scout1089:
okey thank you, downloading your latest kernel.. :)

am using no frills. :D
[Optimus One, P500 Original Android Development] seriousia:
New testing kernel default is same as before.

EDIT: my sd card speed

(8gb class 4)

Antutu results

With previous testing kernel

Write speed 3.6 MB/s

Read speed 6.8 MB/s

With new testing kernel

Write speed 3.3 MB/s

Read speed 7.3 MB/s
[Optimus One, P500 Original Android Development] DJNoXD:
I wrote to yuripg1 and he told me the followin interesting thing:

The latest test version uses the defaults of both TS drivers (no changes).

Please test again with v2.4 testing kernel.
[Optimus One, P500 Original Android Development] DJNoXD:
Does this mean you can select interactivex? :confused:
[Optimus One, P500 Original Android Development] seriousia:
Yes and I'm using interactivex only.
[Optimus One, P500 Original Android Development] DavisNT:
I flashed v2.4-default-vsyncOff and got the following speeds in AnTuTu: 1.8 MB/s read; 4.7 MB/s write

My SD card is 32 GB class 4.
[Optimus One, P500 Original Android Development] DJNoXD:
I am not sure if how antutu tests speed. It shows me everytime a higher write than read speed. I don't believe that. Maybe the results have to be exchanged (read = write, write = read)

Anyway, here my speedtest results with latest v2.4 testing (2012-05-25 8:15):

sd-card used: Lexar 16GB class 6

SD Tools:

write: 6,6 MB/s

read: 33,9 MB/s

AnTuTu v2.8:

write: 11,5 MB/s

read: 3,0 MB/s
[Optimus One, P500 Original Android Development] seriousia:
LoL my

SD tool results

Write speed 6.7 MB/s

Read speed 40.6 MB/s :eek:

(I tested thrice and then took the mean.)
[Optimus One, P500 Original Android Development] DJNoXD:
The problem with every benchmark tool is, you don't know whats exactly tested and how its tested.

So its nice to check if changes are better or not, but for nothing else (just my opinion about).

Benchmarking file transfer speed highly depends on file size, as far as I know.
[Optimus One, P500 Original Android Development] DavisNT:
I agree that comparing test scores of different tools is not a bright idea...

May be speed difference in AnTuTu comparing CM stock kernel and this kernel is related to some kind of caching?

Are there any sdcard related changes from CM sources?
[Optimus One, P500 Original Android Development] vlt96:
The ultimate proof that benchmarks are stupid
[Optimus One, P500 Original Android Development] Cresqo:
Why not just try copying a large file (a ROM zip for example) to the sdcard?
[Optimus One, P500 Original Android Development] am486:
+1
[Optimus One, P500 Original Android Development] DJNoXD:
Have you tried 2.4 testing version?
[Optimus One, P500 Original Android Development] neko95:
> good to see. its on the right section now.. gonna test your 2.4
[Optimus One, P500 Original Android Development] DavisNT:
I had - with default touchscreen driver bug is fixed :)

But! I have a new bug to report (I don't know in which version this bug started) - button on handsfree (the one that came with phone) is not able to wake phone from deep sleep. Testcase:

play music in MP3 player (I use MixZing)

press button on handsfree to pause (music pauses)

wait some (about 10) seconds

press button on handsfree (nothing happens)

press any button on the phone (music resumes)
[Optimus One, P500 Original Android Development] cornelha:
I get taps repeating with both the normal and caveman kernels. On they keyboard for example, tap "a" i get "aa". Scrolling in a list would select on touch etc.
[Optimus One, P500 Original Android Development] DavisNT:
Are you using 2.3 or 2.4 test version?
[Optimus One, P500 Original Android Development] cornelha:
2.3 version, will test 2.4 when I get home
[Optimus One, P500 Original Android Development] DavisNT:
About SD card speed.

Issuing

time cp /mnt/sdcard/update-cm-7.2.0-RC2-p500-signed.zip /dev/null

with stock kernel showed more than 8 seconds of time and with this kernel (2.4 test caveman) it showed 6.5 seconds :)

So probably SD card speed is ok :)

So what about WiFi - actually I think that 10 Mbps is enaugh for phone,

but

I think

may be

stock kernel uses less CPU for WiFi or WiFi is more sensitive with stock kernel...

Also I had a strange issue today - after turning on, WiFi didn't connect to previously saved access point, turning WiFi off and on didn't help, bur phone reboot did.
[Optimus One, P500 Original Android Development] DJNoXD:
Will test it. Does it also happen to official cm kernel?

I will official release V2.4 next time, because of ts issue confusion (if you dont read most of this thread) and the bluetooth fix from official cm kernel.

After that it will take some time before I create a new version, because I want to try out some ideas for this kernel.
[Optimus One, P500 Original Android Development] DeuxEx:
Can u make your kernel to have a smoother scroll? When I scroll my app list, it moves strangely. And this bug i find it also in a few games (try Pirates of the Carraiben or Angry Birds Space). Can you talk to popdog, dev of Oxygen Rom, to get some ideas from his stock kernel?
[Optimus One, P500 Original Android Development] GonDr:
Try v2.4 its smoother than v2.3
[Optimus One, P500 Original Android Development] DJNoXD:
All v2.4 version are online.

- bluesleep: Disable the forceful usage of H4_LPM
- disabled: file system cache
- debuging completely disabled
- giving the kernel a name :-)
- touchscreen drivers: problems should be fixed
- governor added: minmax
- higher OC values enabled
[Optimus One, P500 Original Android Development] DavisNT:
Can you, please, explain why? :)

---------- Post added at 02:15 AM ---------- Previous post was at 01:34 AM ----------

Yesterday I made experiment:

Flashed CM default kernel and went to the borderline of WiFi reception area (WiFi access point has reduced transmit power). At point where WiFi still worked without packetsloss WiFi signal was -85 dbm (18 Mbps mode) and GSM signal was -75 dbm. Five minutes later with this kernel (v2.4 test version) WiFi signal was -83 dbm (11 Mbps mode) and GSM was -73 dbm. Also I was able to use WiFi without packetsloss in plase were packetsloss was detected while using CM stock kernel.

Good job DJNoXD! And thank you! :) Have you made some WiFi and 2G/3G optimizations?

Notes: I didn't wipe /cache and Dalvik cache after flashing CM stock kernel. This experiment was conducted only once, so it is also possible that some interfering/jamming transmitters were turned off during those 5 minutes.

---------- Post added at 02:25 AM ---------- Previous post was at 02:15 AM ----------

About problem that button on handsfree doesn't wake up from deep sleep:

Strange results - looks like it's even worse with default kernel, although I think I was pausing and resuming with handsfree all the time. Will do a clean install of CM and test.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for testing and for your feedback. :)

Because of the sdcard discussion.

If noone will tell me that system is slower because of that, I won't enable it again. Advantage: more free RAM

Some fixes, ... mainly about increasing stabilty are implemented.

Wiping is not realy needed for kernels.
[Optimus One, P500 Original Android Development] seriousia:
More ram free, well i don't see any advantage in having more free ram (using my phone at fullest but still 200MB free). :D

But may be on battery side it will be good. ;)
[Optimus One, P500 Original Android Development] D_Viper:
sorry guys: is this bug fixed in this kernel?:

If you enable GPS, then after that moment, your phone won't go to deep sleep

It is present whit many kernel (cm stock, thundervn, roq...)
[Optimus One, P500 Original Android Development] Roqu3:
That's a ROM problem in cm7 (the service keeps running) the best solution (at least for me) was to never disable gps, that thing don't drains battery if it's not in use.
[Optimus One, P500 Original Android Development] Bec de Xorbin:
A very juddery/laggy/jerky kernel. Still waiting for a kernel to beat franco's 11112011 version. Haven't seen one, not even from franco himself.
[Optimus One, P500 Original Android Development] DJNoXD:
Feedback is always welcome and if I am able to improve something I will do.

But instead of waiting for something (you maybe will never get) why not start working on your own kernel?

For example you could take francos kernel as your base.
[Optimus One, P500 Original Android Development] cupliz:
You are mad? Your post not give any valuable feedback.

No need to flaming...

Sorry for OoT

Sent from my LG-P500
[Optimus One, P500 Original Android Development] manast:
Bec, have you used 2.4?

I am using 2.4 Caveman and find it to be good enough. :)
[Optimus One, P500 Original Android Development] seriousia:
:facepalm:

Even NOOBS are better than you. :mad:

:p
[Optimus One, P500 Original Android Development] FitAmp:
v2.4-caveman+vsync-signed.zip tested on stock 2.3.3. Quite smooth for me with no oc
[Optimus One, P500 Original Android Development] DJNoXD:
I am searching what causes the "white noise".

I created a new repository and began from the start. All changes which I thought could be the reason are added and till now there's no "wite noise".

Than I compared the kernel code I didn't see anything. :confused:

Can anyone confirm that "white noise" first time appears in v1.4?

Kernel 3.x

Still fixing compile errors.

I hope that if all problems are fixed and I can compile it will boot.
[Optimus One, P500 Original Android Development] ZonbekaUnlimited:
@DJNoXD: Can you compile a kernel with franco's ts driver??? it gives me the smoothest scroll of all drivers

ty
[Optimus One, P500 Original Android Development] nldxda:
The kernel included rc3 cm7 didn't have the white noise, I noticed (or at least it doesn't always show)... but I didn't use it for long before I switched to your latest kernel... the cm kernel lags when I wake up my phone. This one is snappy when I wake up the phone
[Optimus One, P500 Original Android Development] DJNoXD:
Generally yes.

But I don't want to compile more and more kernel versions.

But maybe its something that can be done for default TS driver.

In which franco kernel is the driver you talk about included?
[Optimus One, P500 Original Android Development] thachtunganh:
Excuse me, but what is the white noise?

And can i see the 3.0 kernel compiling errors, maybe i can help you?
[Optimus One, P500 Original Android Development] thachtunganh:
Use my touchscreen driver... it's based on Franco one, with multitouch fixes, cpu spike fix... but you have to add one things to the mach-lge header.
[Optimus One, P500 Original Android Development] DJNoXD:
In stock kernel it doesn't appear.

Thats why I am searching which change I have done is the reason.

I can live with this and don't think its a big problem, but I want to know the reason and if possible I like to fix it. ;)
[Optimus One, P500 Original Android Development] DJNoXD:
If you wake up your phone you can see a white screen for less than one second.

Thanks, I will send you this evening.

Its already included :), but for the moment I don't compile a version with it.

And if yours will be part of the release kernels one of the other will be removed. (Compiling four kernels every release is the max I will do)
[Optimus One, P500 Original Android Development] thachtunganh:
I mean that use my touchscreen driver as the default... and who need Vsync off???? Vsync off just help people to show off their benmark...
[Optimus One, P500 Original Android Development] FitAmp:
+1
[Optimus One, P500 Original Android Development] DJNoXD:
For those who only play games vsyncOff can be helpfull.

And about the TS driver I havn't finaly decided the way to go.

But anyway I wanted to try your TS driver again, as I told last time I liked it.
[Optimus One, P500 Original Android Development] GonDr:
+1 and i use always vsync on if available.
[Optimus One, P500 Original Android Development] thachtunganh:
Vsync off really doesn't help much.
[Optimus One, P500 Original Android Development] seriousia:
I use vsync off cause i want maximum available fps. :D
[Optimus One, P500 Original Android Development] storm11:
hey , i just flashed the 2.4vsyncon caveman version , after reboot , touchscreen stopped working , again rebooted , worked for sometime then went off again :/

is it a kernel or rom problem ?
[Optimus One, P500 Original Android Development] nldxda:
Had this problem too.. I just reflashed the same kernel and its been working so far
[Optimus One, P500 Original Android Development] thachtunganh:
So if you get maximum available FPS , what it can help you with? Show off your phone performance with a high end device like Nexus S ? Forget it... it's useless
[Optimus One, P500 Original Android Development] seriousia:
My thoughts on vsync n fps are different.

end of discussion. ;)
[Optimus One, P500 Original Android Development] vlt96:
But what does vsync do? I have never seen a difference, not even on my PC... and WoW lags like hell when vsync is on...
[Optimus One, P500 Original Android Development] DJNoXD:
vsync = vertical syncronisation

In easy words:

If vsync is enabled the max fps you can get is the refreshrate of your display.

Nearly all TFT displays use 60Hz (= max 60fps).

So there are never mor fps produced than your display can show.

Problem with vsync on:

If your graphics card can't produce this framerate (e.g. 60fps), the framerate will be only half and so on (= lags).

Example 60->30->15

With vsync off everytime the max fps are shown. (e.g. 31, 29, 100)

Disadvantage: tearing

Shown picture could be torn appart because of no syncronisation (e.g. first half of the shown picture is new, second half is old). Normaly this happens if you turn around.
[Optimus One, P500 Original Android Development] Roqu3:
screen tearing is the main problem with a vsync off kernel, the ui cracks when you scroll or drag something and it's very crappy, tbh if you use the stock ROM or a custom stock ROM only a vsync off kernel will give you a smooth ui, but in cm7 is not really necessary because ui is smooth and fast with vsync on in that case using a vsync off kernel is just for benchmarks.

On cm9 (in its current status) i think it's better a vsync off because ui it lags a lot after some use
[Optimus One, P500 Original Android Development] Bec de Xorbin:
Yeah, I'm about to do so, yes. Unfortunately franco's github is quite messy. But good luck with your kernel, I'm sure you'll find a way to improve it further.

Ad hominem. How classy.

Yeah, xda is always so full of valuable feedback. Like the one you gave me.
[Optimus One, P500 Original Android Development] DJNoXD:
This is the compile error I'm about to fix at the moment:

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
CHK kernel/config_data.h
CC drivers/gpio/gpiolib.o
CC drivers/gpio/devres.o
LD drivers/gpio/built-in.o
CC drivers/i2c/busses/i2c-gpio.o
CC drivers/i2c/busses/i2c-msm.o
CC drivers/i2c/busses/i2c-msm.o
drivers/i2c/busses/i2c-msm.c:89:29: error: field 'pm_qos_req' has incomplete type
drivers/i2c/busses/i2c-msm.c: In function 'msm_i2c_recover_bus_busy':
drivers/i2c/busses/i2c-msm.c:261:12: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:264:24: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:265:24: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:267:24: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:268:24: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:299:12: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c: In function 'msm_i2c_xfer':
drivers/i2c/busses/i2c-msm.c:334:52: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:335:16: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:469:16: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c: In function 'msm_i2c_probe':
drivers/i2c/busses/i2c-msm.c:524:12: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:530:11: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:530:35: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:549:37: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:553:11: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:555:29: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:556:33: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:558:9: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:564:28: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:606:7: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c:607:7: error: dereferencing pointer to incomplete type
drivers/i2c/busses/i2c-msm.c: At top level:
drivers/i2c/busses/i2c-msm.c:672:12: error: 'THIS_MODULE' undeclared here (not in a function)
make[3]: *** [drivers/i2c/busses/i2c-msm.o] Fehler 1
make[2]: *** [drivers/i2c/busses] Fehler 2
make[1]: *** [drivers/i2c] Fehler 2
make: *** [drivers] Fehler 2

To get the source take a look at v2.6 at candied-kernel repository.
[Optimus One, P500 Original Android Development] PattPatel:
Hi,

no tun.ko for the latest release?
[Optimus One, P500 Original Android Development] allenwalker1998:
If u want why not just compile one for urself
[Optimus One, P500 Original Android Development] DJNoXD:
Its now compiled directly into kernel code (no module).

If this wont work and a tun.ko module is needed because its expected by some apps, I will set back to be compiled as module.
[Optimus One, P500 Original Android Development] PattPatel:
I asked it because it is specified in the title and i couldnt find it :)

Ok thanks, will try and report if it works :)

--------

Edit: it's not working. Getting

Cannot open TUN/TAP dev /dev/tun: No such file or directory (errno=2)

In OpenVPN. Am I missing something?
[Optimus One, P500 Original Android Development] DJNoXD:
Will change back to modules.

It was worth a try. ;)

Tomorrow you can download the updated version with modules.
[Optimus One, P500 Original Android Development] DJNoXD:
fixed
[Optimus One, P500 Original Android Development] thachtunganh:
Wow, you're fast :thumbup:
[Optimus One, P500 Original Android Development] DJNoXD:
Sometimes ideas just come over / in night. :)
[Optimus One, P500 Original Android Development] DJNoXD:
Will take a bit longer.
[Optimus One, P500 Original Android Development] Negi9:
Hey DJ!

The "white noise" bug is fixed in the latest CyanogenMod nightly! :D
[Optimus One, P500 Original Android Development] PattPatel:
Don't worry, take your time :)
[Optimus One, P500 Original Android Development] DJNoXD:
v2.4.1 released

- bluesleep: Fix wakeup
- tun and cifs build build as modules

default ts driver is replaced by thachtunganh's.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for telling me.

I saw that but I didn't find out the difference (till now).
[Optimus One, P500 Original Android Development] GonDr:
i question please, is ca TS and ta TS with fixed cpu spike ?

i feel ta TS has battery drain, maybe i'm wrong coz i flashed a new rom

CM7 Latest 03-06-2012
[Optimus One, P500 Original Android Development] thachtunganh:
Why do you know that my Touchscreen driver caused battery drain :rolleyes:?
[Optimus One, P500 Original Android Development] Cresqo:
Yeah I cant see why too...I compiled my own kernel with your driver and I feel it's very good, smooth and nice for gaming, battery life is unchanged though.
[Optimus One, P500 Original Android Development] DJNoXD:
I often read that after flashing a new rom the battry drain is higher and after a few days its normal again. Maybe this is because some data is created first time.

But I understand why gondr asked because beside the new rom the ts driver is the only change.

So my advice is to wait one or two days while using the new rom. After that battery drain should normalize.
[Optimus One, P500 Original Android Development] GonDr:
+1 thats what i said, will wait 2 days and see, thanks DJ and Ta
[Optimus One, P500 Original Android Development] williamcharles:
yes..ppl should wait for a complete battery drain..only then the battery will stablize...;)
[Optimus One, P500 Original Android Development] DJNoXD:
If changes are tested successfully, I will release a kernel update on weekend (v2.4.2)

* merge of latest cm kernel sources
* USB write performance: f_mass_storage: Disable write cache support
* Recent LCD Patch
[Optimus One, P500 Original Android Development] kyerie030:
Just a question, lcd patch is for the noise when opening the screen? I ask because Im experiencing loss of responsiveness of the screen. Its as if im not touching the screen.

Info:

Cyanogenmod 7.2 RC2

2.4 kernel 480-710
[Optimus One, P500 Original Android Development] yuripg1:
The LCD patch is a change seen on the latest sources that LG released for the Optimus One.

I think no one is 100% sure about what it's supposed to fix. To me, it seemed related to the behaviour of the phone when the screen turns off (which could change the behaviour when it turns on too - Who knows?).

But it comes from LG, so it earns some trust automatically.
[Optimus One, P500 Original Android Development] williamcharles:
yeah the LCD changes were released in the gb version for P500H..so probably something we can count for...
[Optimus One, P500 Original Android Development] DJNoXD:
I have tested my v2.4.2.

The "white noise" is now gone.
[Optimus One, P500 Original Android Development] DJNoXD:
v2.4.2 released
[Optimus One, P500 Original Android Development] GonDr:
Kernel become better and better

DJNoXD i really love ur work

Thank you very much
[Optimus One, P500 Original Android Development] FitAmp:
Tested on latest nightly nothing out of the ordinary yet... :thumbup:
[Optimus One, P500 Original Android Development] neko95:
> DJ.. your latest kernel had the white screen noise fix? or latest cynogenmod kernel had it?
[Optimus One, P500 Original Android Development] DavisNT:
Latest candied kernel by DJNoXD has screen white noise fixed :)
[Optimus One, P500 Original Android Development] Kanad:
@DJ: 2.4.2 kernel works on MIUI GB 2.3.7 by fundooz :) Excellent kernel!

Edit:

Governor: No Lionhart! surprising

DJ why u removed it any reasons?
[Optimus One, P500 Original Android Development] omidreza:
I tested the 2.4.2 ta-vsync kernel on the gtr and i should say it's better than thundervn but the sd card read speed is too low...if you improve this , it becomes better
[Optimus One, P500 Original Android Development] DJNoXD:
I removed some time ago.

The reason is, that the implemented version of lionheart isn't better than the original conservative.

I updated the governour sources to the latetest version (kernel source 3.0). So please use conservative.