yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Original Android Development] DJNoXD:
Please test about the cpufreq issue.

I think that is the most important.

Camera flicker should also be gone (please test).

As I told if cpufreq is stable, I will create version as normal.

And yes, vsync is on. (will also create the off version later)

Did anybody here now if it is a problem to use touchscreendriver as module?
[Optimus One, P500 Original Android Development] dnle71:
What i am really concern about is the SDCARD read/write speed bro, don't something bull****.. .i am really offended of what you said to me..:(

And i tested roq's kernel at the same day,same rom.etc..tested it also about 5 times using conservative and smartassv2
[Optimus One, P500 Original Android Development] dnle71:
Delete
[Optimus One, P500 Original Android Development] DJNoXD:
Be patient. New kernel is coming. :)

I know that v2.0 (keep in mind its still for testing) is not on the level of 1.4.

All the patches / fixes / improovment must be implemented again (if they don't cause any problem).

That why I started new.

I also understand that some "problems" are important to some of you and its hard for you to wait. But nobody wants a fast kernel that drains the battery.

For the moment:

If you can't wait, please use the old kernel.

If you live (at the moment) without all patches, ... and you want to help, take the testing v2.0.1
[Optimus One, P500 Original Android Development] DJNoXD:
I can create a version which has lots of improvements in it again.

If you tell me cpufreq is realy working fine again I could upload it for you.

about vsync:

The v2.0.x versions are compiled with vsync on.

Programs can override that (you know that from windows games). Neocore did that. With vsyncOn I got 71fps.

There is also something inside the code, which I understand like you can toggle.

Can anyone confirm that?

If thats true and I don't fail about that, my opinion is that vsync should be on and apps has to decide to override it with fault.
[Optimus One, P500 Original Android Development] dnle71:
It seems like "/sys/devices/virtual/bdi/*/read_ahead_kb" set to 1024 comparing to the default 128..maybe you could try to go back to default value..and i guess this is not vsync-on, it still stutters. And lulzactive is still always on the max freq..:)

Btw: white noise is always present, when waking up the phone..
[Optimus One, P500 Original Android Development] DJNoXD:
You mean a lower value (default 128) will solve that problem?

How can I reproduce that problem to test?

Other governors are working fine?

I am still testing lulzactive.

Will try if I can do something about, but if I can't it will be removed.

white noise:

There are two things which I can try.

I will also take a look at the changes (no many left) since minimal testing version.

Edit: My v2.0.2 testing version feels realy fast. :D

Will now test including TS driver as module.
[Optimus One, P500 Original Android Development] dnle71:
Testing sdcard speed? And i guess it's only lulzactive, lionheart is working well:D using it right now..

Edit: just flash back to roq kernel, and "/sys/devices/virtual/bdi/*/read_ahead_kb" are much higher! 4096 and some are 4?..:confused::confused:
[Optimus One, P500 Original Android Development] deniso177:
its just sd card speed cache, it doesnt seem to do that much of a difference, but 4096 is too high 1024 is best for our phone, dont earlier from tests and using scripts.

So really its last priority lol.

Will test the cpu freqs, and overall stability

---------- Post added at 10:20 AM ---------- Previous post was at 09:50 AM ----------

Just tested the cpufreq, performance governor works, the max freq is set, but conservative, lionheart do not work, its always doesnt go higher then one slot below the max frequency.

Maybe something in 3.0 is simply incompatible, as remember with a kernel update come driver updates, and some code you cant backport =(
[Optimus One, P500 Original Android Development] Cresqo:
Not problem for me here, cpufreq is working fine with every godrnor, tested with cool tool
[Optimus One, P500 Original Android Development] deniso177:
test with setcpu or rom toolbox. Change the frequecncy and governor withing CM setttings and then go to either of the programs and touch the screen a lot and scroll around that normally makes it go to 100% cpu, for me it always gets stuck on slot underneath, no matter what frequency i choose.
[Optimus One, P500 Original Android Development] Cresqo:
ROM toolbox i know it always uses one step lower when OCing
[Optimus One, P500 Original Android Development] thenenea:
Gtr 2.0 , kernel 2.01 no frills conservative , sio 122-729 freezes when browsing. I'm trying minimal 200 to see if it's more stable.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for your help.

I tried to reproduce this way:

I have selected conservative / lionheart / ... inside CM setting.

After that I srolled, ... a lot.

Then I called setCPU. Shows me 480MHz.

Now I have touch the screen for ~5sec. -> Max freq

After release freq got back to my min freq (480Mhz).

Then I touched the screen and mooved my finger. -> Max freq

After release freq got back to my min freq (480Mhz).

I used SetCpu 2.2.4. Also tested with Christian Göllners Bemark & Tuning.

For me the only governor that is always at max freq is lulzactive.

I have found an update for that governor, which I hope will solve that.
[Optimus One, P500 Original Android Development] DJNoXD:
In the past there where lot of discussions about the min freq.

The result:

Use 480Mhz as min freq, without loosing batterylife. (320Mhz should also work)

Lower min freq will make the system less responsive.

Which rom did you use?
[Optimus One, P500 Original Android Development] dnle71:
Have you fix the sdcard issue now? Hope so!! Btw Im really loving this kernel's graphics driver, it's so clear..:D

Waiting for it!!:D
[Optimus One, P500 Original Android Development] DJNoXD:
lulzative v2 tested:

Now we can use the app, but is not working correctly.

Stucks at min (if you came from screenoff) or max (if you came from other governor and max freq).

I will remove until I found a solution.

sdcard:

Lots of patches from 1.4 are back again (in my test version).

Havn't tried if its fine.
[Optimus One, P500 Original Android Development] dnle71:
I you want i have time to test!..:pand btw there's somethings wrong with your script.. and also the system/etc/file(i forgot what it is) is not related from your kernel..
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks

I will suspend the work on lulzactive for the moment. (lowest prio)

File is removed.
[Optimus One, P500 Original Android Development] DJNoXD:
v2.0.2

v2.0.2 is up for testing (for those who want).

For download, take a look at the first post.

v2.0.2 (complete list of

all

included changes)

- default governor set to lionheart
- lulzactive governor removed (does not work)
- clean up: governors and schedulers
- axis inverse workaround (waleedq)
- VM tweaks
- Claim more free ram (lupohirp)
- grants system server access to oom_adj for applications (lupohirp)
- remount with noatime and nodiratime (cresqo)
- cgroup: fix cpuset permission check (thachtunganh)
- msm: cpufreq: Do not call a cpu transition if selecting the same speed (LorDClockaN)
- cgroup: speed up access to cgroupfs mounted entries in /proc/mounts (franciscofranco)
- Fix memory leaks from the wifi drivers (franciscofranco)
- staging: android: lowmemorykiller: minfree values added
- msm cpufreq Improve initial frequency selection - CodeAurora
- fs: simple fsync race fix ()
- ashmem: fix deadlock when system is low on memory
- Wifi set to FAST (roqu3)
- Set correct divx codec type (francisofranco)
- Fast Sleep, wake lock timer change. (wistilt2)
- lionheart (implementation from roqu3) done to 3.0.8 conservative governor
- file system cache enabled
- Lower radio/event log for more ram (wingrime)
- Increase readahead to some more reasonable values (franciscofranco)
- New battery driver courtesy of thachtunganh
- net: wireless: bcm4325: Convert kmalloc() + bzero() to kzalloc() (franciscofranco)
- Fix camera flicker (Turducken)
- Set axi freq to max possible (clk_get_max_axi_khz())
- CPUFREQ_ondemand code from 3.0.8 kernel
- CPUFREQ code from 3.0.8 kernel
- Using OC settings from franciscofranco (higher OC?)
- Update: Linux upstream 2.6.35.10 > 2.6.35.13
- vm_swappiness = 1 (performance is a little bit better than 0)
- Erase memory pages as soon as they are freed to prevent new processes getting old information (franciscofranco)
- writes_starved = 1
- added tun.ko
- added cifs.ko
- lzo kernel compression (larger file, but faster boot time)
[Optimus One, P500 Original Android Development] scout1089:
ok downloading now..thank you brother, is the white noise reduced?
[Optimus One, P500 Original Android Development] DJNoXD:
No, I have not found the reason.

But since it is in all my version, there must be a difference. (still searching for it)
[Optimus One, P500 Original Android Development] scout1089:
ok..when i was using franco kernel v4 there is no white noise during turning the phone on, maybe you could look on it(franco's build)..
[Optimus One, P500 Original Android Development] dnle71:
Problems i found from 2.0.1 are still there..:(
[Optimus One, P500 Original Android Development] DJNoXD:
Did you have the problems with the v1.x version too?

There are still some changes from v1.x that are not included.
[Optimus One, P500 Original Android Development] dnle71:
Have'nt tried it..

Will try it later..

Edit: tried 1.4 vsyn-on dercaveman touch

-lulzactivev2, still always at max freq.

-white noise upon waking up the phone.

- slow sdcard speed..

I only tried the known bugs from v2.

.:)
[Optimus One, P500 Original Android Development] thenenea:
GTR v 2.0 as stated above. 320 seems stable so far.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks

lulzactive seems to have a bug. Its removed till I found about.

white noise: still searching

slow sdcard speed: will try to find out
[Optimus One, P500 Original Android Development] deniso177:
Ye I overclock with CM settings, i just use Rom toolbox to see the current cpu. Will wait for next realease and test again =) By the way defiantely include the new GPU drivers from ta kernel, it makes a huge difference in screen quality =)

Other then that great kernel, glad to help with testing =)
[Optimus One, P500 Original Android Development] DJNoXD:
GPU drivers will be included. ;)
[Optimus One, P500 Original Android Development] deniso177:
OK retested the new kernel, With CPU Spy , I can now see my max being used, ROM toolbox is the one not seeing max, maybe because the app itself has problems with the 3.0 (Im using an older version). So will use cpy spy to test from now on, as it shows which slots have been used, and its handy to just reset the timer and test other governors.

I am going bed now so will leave my phone idle to see the battery situation on standby, which is a good way to catch battery drain if any =)
[Optimus One, P500 Original Android Development] edinrh:
I must say that your kernel is awesome friend .. I am using now with my rom and is excellent .. good job, keep it up
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks :)

Now working on v2.1, with CPU driver from kernel 3.0.
[Optimus One, P500 Original Android Development] dnle71:
just a suggestion bro! maybe you could try paolov6 2.6.35.14 as base:D:D
[Optimus One, P500 Original Android Development] pradipsoman:
How is the battery life? What are the bugs ? And is there a link?
[Optimus One, P500 Original Android Development] DJNoXD:
v2.1

v2.1 is online (first post)

Only default TS driver with vsync off.

Other versions will follow tomorrow evening.

- try to fix "white noise" (still there, but only very short time)
- some patches about speed
- more debugs disabled
- fix cpu load 100%
- backported binder from 3.0 kernel (lupohirp)
- BUS freq OC
- GPU freq OC
- GPU drivers from 3.0 kernel
- genlock enabled
- axi OC
- bcm4325: MAX_STATIC_PKT_NUM patch (HepHappy)
- LZMA compression (best compression -> testing about speed)
- ARM: decompressor: use better output sections
[Optimus One, P500 Original Android Development] deniso177:
Downloading now, will test all feautres =)

Your doing a great job by the way, you picked up kernel development preety quickly =)
[Optimus One, P500 Original Android Development] corwin42:
Hello DJNoXD,

I'm currently using your 2.0.2 Kernel and it has some problems with GPS.

Every 5 minutes the GPS fix is dropped for a short time (some seconds). I have tried different governers with and without overclocking but the problem remains always the same.

In the attached image (captured from Run.GPS) you can see in the DOP (GPS Dilution) graph that there is a peak every five minutes.

Even with Google Maps you can see this problem. Every five minutes the position jumps around for a few seconds and then returns to normal.

The 2.0.0 version has this problem, too. I'm not shure about 2.0.1. Haven't tried 2.1 so far.

CM7 stock kernel does not have this problem.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks for telling me.

Will try to find out whats happen.

Did you know if this happen with 1.x versions?
[Optimus One, P500 Original Android Development] corwin42:
GPS Problem

Will try it this evening with 1.x version.
[Optimus One, P500 Original Android Development] DJNoXD:
Thanks.

The version with less modifications is 1.2 (link). (So I think it should work with this version)

If problem is also in this version, it should be easier to find for me.

You have only gps actived or also positioning by data (inside location settings)?

Can you post a logcat of that?

Edit: Warum schreibe ich dir eigentlich nicht in deutsch? ;-)
[Optimus One, P500 Original Android Development] cupliz:
Your new kernel is superb!! Waiting for vsycn on version...

-better battery live than v1.4

-faster reboot

Dont know about:

-Gps

-sleep/wake when wifi on

What is different between v2.1 and 2.0.2?

Sent from my LG-P500
[Optimus One, P500 Original Android Development] DJNoXD:
These are the changes compared to v2.0.2.

In first post you will now find all changes for a main release line (e.g. v2.x).

A marker line ("----") shows the beginnen of the changes of a new version.

Main difference in v2.1 are the gpu driver from 3.0 and the smaller kernel (LZMA compression)
[Optimus One, P500 Original Android Development] dnle71:
so i've tested you're kernel 2.6.35.10 1.3.1 and the sdcard read is okay..will stick to this for now..

edit: nvm! tested 4th to 5th times smartassv2 and conservative still sdcard is inverted again..:mad:
[Optimus One, P500 Original Android Development] DJNoXD:
I have searched and found that it is a problem of the main kernel source, that seems to be fixed in kernel newer than 2.6.38.

So I will take a look if I find out what has to be patched.

Don't ask when it will be patched. It takes time to get through all that changes. ;)
[Optimus One, P500 Original Android Development] deniso177:
I got an interesting "bug" once in a while when i get a text message that wakes the screen, after the phone has been asleep for a while, i see 2 of the screen, the screen is divided into two parts, and both top and bottom are my unlock screen, touch works fine tho, swiping were the lockscreen normally is shows the phone being unlcoked and its unlocked. turning the screen of and on fixes the bug straight away, so its really not a big deal, but may freak out some people.

---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------

Try downloading FasterGPS from the market and setting your country in the settings, this helped me a lot, and my gps is as stable as ever

P.s FASTERGPS is better then FASTERFIX, its newer and is more accurate with more advanced tweaks

---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------

my sd card speed seem fine, but i have an ordinary sd card, maybe people with class 10 cards notice something more
[Optimus One, P500 Original Android Development] DJNoXD:
Have not seen this on my phone.

But I guess its something about the white noise thing I tried (maybe delay is to short).

I can create a version without that if you want to test.

I also did not feel its slow. But I never tested my card with a benchmark tool. :D

Anyway, I will try find out if there is a fix (maybe backporting new driver from 3.0 kernel)
[Optimus One, P500 Original Android Development] deniso177:
Ye its probably the white noise, as you didnt do anything else that has to do with the screen waking up. The white noise never bothered me, it actually looked cool lol, better then a double screen =)
[Optimus One, P500 Original Android Development] landeiro:
I have same problem. Your kernel is very good but there is a delay, white screen and screen divide in two parts.
[Optimus One, P500 Original Android Development] deniso177:
yey im not crazy and seeing things lol =) Best way to reproduce it is get go sms, set it to vibrate and wake up screen when recieving texts, then leave the phone for like 10 mins and send urself a txt
[Optimus One, P500 Original Android Development] corwin42:
I have a class 10 16GB SD in my Optimus One and have tested speed with SD-Tools with 2.0.2 kernel. Write speed was about 9MB/s and read around 39MB/s.

Stock CM7 Kernel has 7MB/s write and 19MB/s read with my card.
[Optimus One, P500 Original Android Development] deniso177:
well thats class 10 speeds approximately anyway, It tells me i have 7 MB/s on antutu but i doubt my card is anything higher then a class 4

---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------

I just use sd tools and i have 6.7 MB/s Writing Speed, 22.9 MB/s Reading speed.

So unless i magically got a 2gb class10 SD card with my previous nokia e63, your card is either Not a Class 10, or the speeds of the SD card are being throttled (held back) by the kernel
[Optimus One, P500 Original Android Development] DJNoXD:
I have write speed of ~13Mb/s / read speed of ~10Mb/s with antutu and

write speed of ~8Mb/s / read speed ~32Mb/s with sd-tools.

Can't tell you what class my card should be.

So I would guess SD-Tool testing is more about sequencial reads (always faster) and antutu is more random (slower).

Nevertheless I will try the 3.0 drivers.
[Optimus One, P500 Original Android Development] DjFreeze1984:
gps looses stelite with this kernel :S
[Optimus One, P500 Original Android Development] GonDr:
Use Gps Aids or Faster Gps from Market. ;)
[Optimus One, P500 Original Android Development] DJNoXD:
Is there an error about that in your logcat?

If yes, please send that logcat part to me or post it here
[Optimus One, P500 Original Android Development] DJNoXD:
Before I create the other versions (cyveman, vsync) I will revert the changes I have done about white noise.
[Optimus One, P500 Original Android Development] DJNoXD:
v2.1.1 all four versions are online (see first post)

v2.1 -> v2.1.1 reverted possible "white noise" fix
[Optimus One, P500 Original Android Development] deniso177:
Great update so far, and the "white noise" is really not an issue, lots of phones do that, when Ram is filled up or the phone slept a long time. My friends stock HTC phone does it some times too.

I like to pretend im turning on an old fashioned tv if i ever see the white noise =)
[Optimus One, P500 Original Android Development] corwin42:
GPS Problem

It's not so easy to test GPS problem. It seems that it doesn't occur directly after flashing/reboot. Tried some Kernel versions yesterday (1.2, 1.4, 2.1 and even 2.0.2 again). Can't reproduce the problem directly after flashing (used GPS for half an hour every time). Then left 2.1 version on the phone over night. This morning GPS problems again (every 5 minutes GPS fix loss).

Here is a complete logcat

I think relevant part is only this (this is the time where GPS fix was lost. In the complete log you can see that a short time later TTS service speaks "Tschie Pie Ess-Signal zu schwach", thats Run.GPS warning about lost GPS signal):

D/libloc ( 208):
D/libloc ( 208): Event RPC_LOC_EVENT_LOCATION_SERVER_REQUEST (client 0)
D/libloc ( 208): loc_eng_deferred_action_thread signalled
D/libloc ( 208): loc_eng_deferred_action_thread event 64
D/libloc ( 208): loc_eng_process_loc_event: 40
D/libloc ( 208): loc_event_cb: get loc event location server request, event = 2
D/libloc ( 208): loc_eng_process_atl_action, AGpsStatusValue = 2,data on = 1, APN = [internet.eplus.de]
D/libloc ( 208): loc_eng_report_agps_status, type = 0, status = 2
D/libloc ( 208): loc_eng_data_conn_closed
D/libloc ( 208): loc_eng_ioctl called: client = 0, ioctl_type = RPC_LOC_IOCTL_INFORM_SERVER_CLOSE_STATUS
D/libloc ( 208): loc_eng_ioctl result: client = 0, ioctl_type = RPC_LOC_IOCTL_INFORM_SERVER_CLOSE_STATUS, RPC_LOC_API_SUCCESS
D/libloc ( 208): loc_eng_ioctl for ATL close. rc = 1
D/libloc ( 208): loc_eng_deferred_action_thread. waiting for events

I will make more tests with other kernel versions again (even stock kernel to confirm that stock kernel really does not have this problem).
[Optimus One, P500 Original Android Development] DJNoXD:
Great

Thanks for your help.
[Optimus One, P500 Original Android Development] neko95:
> gonna test 2.1.1 caveman+von

> feedback later on.. there are lot of OC you had made so probably will loose stability and OC features
[Optimus One, P500 Original Android Development] GonDr:
v 2.1.1 is not stability and i have many FC and many auto reboot and freezing and kernel panic

v 2.1.1 vsync on dercav + Official CM7 latest

oc 480-729
[Optimus One, P500 Original Android Development] DJNoXD:
This kernel uses more aggressive CPU OC settings. (Which work fine for me)

I can only reccomend to lower OC for the moment and try again.

If everthing is fine again than it is a problem with the aggresive OC settings, which can only be changed by compiling kernel with changed values.

Tell if everthing works fine with lower / no OC.

If that solves the problem I will switch bakc to "normal" OC settings to be compatible with more devices.
[Optimus One, P500 Original Android Development] neko95:
> everything is ok on 768 for me.. 787.. I cant open camera, It reboots.. so thats how far I can go for it.
[Optimus One, P500 Original Android Development] thachtunganh:
My kernel are using aggressive Overclocking too, and because of it i got kernel panic....

And, did you fix the Slow USB read and write speed???
[Optimus One, P500 Original Android Development] deniso177:
Lower your OC, you get more performance with less oc, Im on 729 and my phone is as stable as a new chair
[Optimus One, P500 Original Android Development] DJNoXD:
For me 787Mhz ist the last stable freq I can use. But for me 729Mhz is also enough OC. I don't play much with my phone and AngryBirds for example can be played at that freq.

Even for benchmarks higher freq want increase result that much.

Now, I didn't work on that. Its one of the next things to work on the read / write speeds.

If have one strange thing with my touchscreen (with every kernel I used till now and I can remeber) which is the most important reason why I started working on kernel.

Sometimes it just stops working. Then I have to press power twice and everything is fine again. Yesterday I tried to find out whats the reasone. But it seems not to happen if my phone is conncted to PC by usb-cable. :confused:

Did this happen someone else here?
[Optimus One, P500 Original Android Development] deniso177:
Cm already went over the dangerous overclocking

https://github.com/CyanogenMod/lge-kernel-msm7x27/commit/373843806be03badd4fe523e974eb83a35f4f8f8

---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------

And nope my touchscreen doesnt have that bug, but each phone is unique, just as the over clocking show, one phone can handle 806MHZ easy, when some cant go past 729