yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Original Android Development] Garuxa:
With stock rom 2.3.3 + SmartassV2 748/480 + I/O deadline

I try this with a init.d script

Vsync on Neocore wo/s: 48.5FPS

Vsync off Neocore wo/s: 49.0FPS

As I probe typing the command in the Terminal Emulator and I do not received any message or error thrown, so I assume that the command is running

Later I will try with CM7 6.6.1 to see if there is any variation

I hope this serves franco :)
[Optimus One, P500 Original Android Development] eigokyoukan:
Flashed and tested vsync switch.

Command eched proper but didn't seem to do anything.

With Neocore sound off:

Vsync off - 63.1 fps

Vsync on - 63.1 fps

Will go ahead and focus on conservative governor testing.
[Optimus One, P500 Original Android Development] vlt96:
Does conservative save some battery does anything good?
[Optimus One, P500 Original Android Development] sweetnsour:
at 480/600 smartassv2 (neocore sound off):

vsync off - 58.9, 60.0, 59.7

vsync on - 59.1, 60.2, 59.8
[Optimus One, P500 Original Android Development] DaXmax:
Franco, i think u need test another is it?
[Optimus One, P500 Original Android Development] yuripg1:
I don't know if this is relevant info, but I ran neocore after setting cpu to 122/122 as min/max frequencies and didn't notice any tearing.

(It's always good to be clear that I flashed the latest kernel, wiped cache and dalvik cache and executed the command on terminal emulator - no errors because it went through Google Chrome to Phone)
[Optimus One, P500 Original Android Development] vlt96:
You can't even launch any app at 122MHz, I don't think it stayed there, it got higher, I thinl
[Optimus One, P500 Original Android Development] franciscofranco:
Tomorrow ;)
[Optimus One, P500 Original Android Development] Lawful123:
Good on you

Just wanted to say that i apreciate your work and donated a coffee to your cause. Look forward to the release tomorrow. Just wondering if you plan on having this kernel work with official and cm or are you just going to support cm? What does the future hold?

Even thow that "other guy" wants you to retire please dont. :D
[Optimus One, P500 Original Android Development] sucka:
Hell no, do not retire, who are this device gods? i say respect to all devs and to mik and franco that they are like the father gods :D best fastest most stable and greatest stuff :) just keep up the good work to make this working better than ever so you will remain in history and all people just keep supporting them :D
[Optimus One, P500 Original Android Development] kly91:
i can't wait for another great kernel!..:D thanx
[Optimus One, P500 Original Android Development] aaronbutton:
After flashing v1 with official gingerbread. wifi would cause boot loop and root explorer FC's. No split screen for me though. 825Mhz would again be nice. Great work
[Optimus One, P500 Original Android Development] DaXmax:
Wad time will u release? I cant wait...
[Optimus One, P500 Original Android Development] andy572:
every day and every 4th post the same requests "it woud be nice to have...", "when you release" and "what about ETA?"

some people should sometimes think before writing such questions... most professional developers

have a known (alleady posted) github address - why not look at it and look for that

answers there? than u can see the state of kernel/software/rom - we can't post every day a update with 2000 new features and 3000 bugs fixed ...
[Optimus One, P500 Original Android Development] franciscofranco:
I don't know about you andy, but I can release everyday with 2001 new features and 3001 bugs fixed, I just pwned you ;) (for users that don't understand, I'm joking)
[Optimus One, P500 Original Android Development] eigokyoukan:
Dev power over 9000!!!!! Lol old jokes aside, really appreciate all the work poured into this. Your kernel makes my friends witb droid x phones jealous! Thanks again for the work man.
[Optimus One, P500 Original Android Development] franciscofranco:
Update released.
[Optimus One, P500 Original Android Development] fernando1sg:
Thank you man i've been waiting for it now i'm going to flash it right away :D
[Optimus One, P500 Original Android Development] Freedomalfa:
hey franko ,can you tell me what black screen mean and when i receive this ?
[Optimus One, P500 Original Android Development] fernando1sg:
just test the kernel and when you see the black screen bug i mean by logic it must be a black screen not going away for a moment or something then you'll understand what he meant... just saying!
[Optimus One, P500 Original Android Development] fernando1sg:
Hey bud that black screen bug is real problem here thought.

but after a couple minutes fighting with the black screen bug i was finally able to unlock the phone at least hahah

PD: Thanks for adding smoothass governor i'll investigate about those 2 governors you added.

Good luck and thank you again.
[Optimus One, P500 Original Android Development] franciscofranco:
Andy maybe just found the bug! Big congrats to him, we're testing all the scenarios now to make sure this **** gets fixed.
[Optimus One, P500 Original Android Development] fernando1sg:
Great! keep it real you all devs!
[Optimus One, P500 Original Android Development] andy572:
Thanks franco, but without your ideas i'm nothing :)
[Optimus One, P500 Original Android Development] onlymeipse:
Awesome dudes! I hope we'll have a .35 full working kernel in a couple of days :)
[Optimus One, P500 Original Android Development] theb3s7:
Hi!

The misaligned bug is indeed gone, but I'm having some problems with WI-FI.. When I try to turn it on it just says "Error" in Settings and it doesn't turn on.

Anyone else experienced this?

I wiped dalvik cache before flashing the Kernel

Thanks!

LE: Rebooted and the Wi-Fi worked. Dunno what was the case earlier..
[Optimus One, P500 Original Android Development] fernando1sg:
Yes i've got that Error Wifi problem too.

and i wiped dalvik and battery stats
[Optimus One, P500 Original Android Development] yuripg1:
It's a patience exercise, but it does run.

Just to confirm, I did it again and, this time, I reseted cpu spy right after setting the frequency to 122. It confirmed that I was running at 122MHz all that time (it was showing 3min09sec at 122MHz after exiting neocore and opening cpu spy).
[Optimus One, P500 Original Android Development] franciscofranco:
Ok my implementation didn't work, I will try something different later. Anyway this latest release will be stabler, much less reboots.
[Optimus One, P500 Original Android Development] metalboy94:
Well it's not about CPU usage here, it's about WiFi usage, that drains quite a bit of battery.

Well, dunno if that question was sarcastic or not, but Tasker deals with profiles AND tasks, and you can have tasks outside of profiles. I preferred using a script and a profile to disable it so that it would be rather smart and disable quickly (and to circumvent some Tasker limitations).

Also, Franco is indeed Jesus, I had 2 crashes last night while playing FMX IV but I figured they were because of the (very buggy) game. :D I will flash the latest kernel tonight and try conservative and all the new changes.
[Optimus One, P500 Original Android Development] fancccc:
also tested conservative on 480/768 30 minutes in neocore interactive, no panics
[Optimus One, P500 Original Android Development] voyager20021:
In my case it only crushes at 710 max (wich was my stable freq in .32 kernel) including with conservative gov, but the performance is greater using 691 on this kernel than .32 tree (691 is also stable on smartass2 as the 2 govs are both stable-never had panic because of the gov). So downclocking one step is not an issue at this point. If reducing FSB/BUS speed will result in decreasing perf then i preffer this release. Also i think it's a good idea to make vsync optional. I dunno if it does anything else than on pc, but if it doesnt, i cant find it useful on such a small screen as O1's. And using it causes a perf loss of about 10 fps in Neocore.
[Optimus One, P500 Original Android Development] voyager20021:
So true! Wifi is the big batt consumer on this device, and i guess on any other. But i also think its just as much as the devs can do about that.

Regarding the testing, another fast way to test kernel panic i found is setting gov to performance presuming this gov has no bugs like franco said about smartass2. In all the cases i got panic using that gov, and that came almost immeditely after setting it if there was a problem with the kernel, i also got panic sooner or later on normal use with any other gov. So it was pretty relevant for me.
[Optimus One, P500 Original Android Development] Hanny:
hey voyager have u tried stress tesy for about 3 hours? that is effective to produce panic(reboot) on my phone with one step down than .32 (for me 729->710)

i kept stress testing my phone from day to night and

justnow 2h50m smartass2 710 rebooted! and now gonna do another long stress test on 710conservative

please help confirming! because here i can confirm long stress test.is quite accurate n i recommend u to try it on ur 691 too, especially both conservative n smartass2 :)

im starting conservative 3 hrs stress test and please refer to my signitures link for more details and results on 12112011!!

gonna reply and give more detailed and clearer results/comparisons of my phone later! :)
[Optimus One, P500 Original Android Development] voyager20021:
Try using performance gov on 710 normal use and see if you get KP after a while.

I noticed that i also get KP on 710 after some more using time than on 02.10 kernel so i thought at first its stable. But stil KP after some time.

On the other hand, stil having continuous bootloops after pushing too many apps to sd, although i could move more apps and get stable this time.

Vsync on/off not effective, but already known.

A couple of frames down caused by FSB/BUS tweak.

Conservative gov looking good so far, even if i couldnt figure out its improvements yet.

Cant wait to have back the 7x fps wich made Micks rom so loved by so many.

Good job Franco! Keep it up! We keep on testing your ”****” cause this ”****” is getting better on each release!:)
[Optimus One, P500 Original Android Development] franciscofranco:
Thank you for a so detailed report. At this moment I can't give you much more information as I'm still brainstorming, but what I can assure you is that your phone can't handle anything higher than 691mhz with this kernel, I think that's already obvious, and there's nothing I can do to change that.

Conservative governor will save more battery life than smartass2, and because I tweaked it there shouldn't be any performance loss in the long run. There is enough information about conservative in the web, a little Google search will do it.
[Optimus One, P500 Original Android Development] metalboy94:
^ Truth is, I get just one kernel panic per day @ 729 mhz smartassV2. I will start using InteractiveX though to observe any performance/battery differences.
[Optimus One, P500 Original Android Development] franciscofranco:
Decrease your frenquency and it will be fine.
[Optimus One, P500 Original Android Development] Hanny:
your welcome and thanks franco, will start trying on 691!! :) and see what results do i get later ;)
[Optimus One, P500 Original Android Development] voyager20021:
I bet you will be stable on 691!;)

How are you on random reboots? Stil happening?
[Optimus One, P500 Original Android Development] metalboy94:
Running 320/729 conservative since last night, great performance and no crashes it.
[Optimus One, P500 Original Android Development] ciolnadu:
I must be lucky since my phone is running great at 748/480 conservative.
[Optimus One, P500 Original Android Development] Hanny:
yea until now, they are still happening on 710 and 729, see my signitures link ↓ ;)

and im quite certain that they are almost equal to kernel panics :) as they happen aftet some hours of stress test

am using 691 normally for about 10 hours w/out errors, not going to stress it though, and gonna see what happen :):) hope it will be stable for me!

@the two above this post

wow man u guys are lucky, have u tried setcpu stress test?? wanna compare myself to yours! ;)
[Optimus One, P500 Original Android Development] voyager20021:
Mine is longer.:D

Nope, i dont use setcpu anymore. I dont like the idea of testing something for hours. But i can say that now i`m on 710 conservative normal use for a few hours. Only if i move to performance gov or i play some games i get KP. So, as i said before, this kernel is more stable than 02.10 as on that one i got KP almost immediately at 710 any gov.
[Optimus One, P500 Original Android Development] RevengeFNF:
Hey people.

In the first post i read this:

But, where can i see what are all the changes of the latest testing version?
[Optimus One, P500 Original Android Development] terratrix:
few pages back
[Optimus One, P500 Original Android Development] metalboy94:
Conservative is indeed a godlike governor in this kernel OwO no crashes on 320/729 conservative in ~8 hours of normal usage. Once I plug the phone to charge I will report about crashes on 480/748 minmax.

Also Franco, I haven't even gotten the OpenGL freezing I talked to you about (graphics still froze before kernel panics but that doesn't count :D ) since flashing your kernel!
[Optimus One, P500 Original Android Development] voyager20021:
Yap, i also noticed some lag just before kernel panic. But on stable freq, no problems at all with conservative gov. Also great on battery consumption indeed.
[Optimus One, P500 Original Android Development] franciscofranco:
That's what I want, stability comes before anything else.
[Optimus One, P500 Original Android Development] metalboy94:
I've had one kernel panic on 480/748 minmax but meh, I'm just pushing it now :p
[Optimus One, P500 Original Android Development] terratrix:
Since you have tweaked conservative governor, i'm currently having a dilemma choosing InteractiveX or conservative:p What are your opinions:confused:
[Optimus One, P500 Original Android Development] TakamineSubasa:
conservative +1

1 vote for conservative, at least for me the performance of conservative is more constant and i find it smoother than interactiveX with practically the same battery!
[Optimus One, P500 Original Android Development] voyager20021:
+1 conservative
[Optimus One, P500 Original Android Development] franciscofranco:
Conservative.
[Optimus One, P500 Original Android Development] DaXmax:
Actually i was thinking, what is ur tweaked conservative??
[Optimus One, P500 Original Android Development] rpankaj:
Hey guys.. what to do foe gud battry bckup... getting lesser bckup.. tweaks any??
[Optimus One, P500 Original Android Development] vlt96:
Any english please?
[Optimus One, P500 Original Android Development] fserve:
Just for testing purposes.

Someone could set 122MHz and check if mp3 is playable with this .35 franco.Kernel? :-)
[Optimus One, P500 Original Android Development] mihir287:
Max/Min frequencies: 122 MHz

Governor: conservative

Scheduler: deadline

Played a 192 kbps mp3 file, no stutters. :)
[Optimus One, P500 Original Android Development] fserve:
Try enable wifi, browse to google.com, then disable wifi and listen an entire music. (on any clock)

Please :-)
[Optimus One, P500 Original Android Development] mihir287:
Enabled wifi, did a random google search, disabled wifi, then played the same track. (Clock 729/480)

No problems. :)
[Optimus One, P500 Original Android Development] vlt96:
Maybe different settings in dsp manager, another music app, try music on speaker etc...

Sent from my LG-P500
[Optimus One, P500 Original Android Development] Bec de Xorbin:
I find the new test release virtually bugless (except the notorious blackscreen bug) and clearly superior than any .32 kernel version.

---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------

If I translated this correctly from Gibberish to English, you don't need any tweaks. Just set the minimum frequency to 480 and maximum to not more than 691. Also use conservative governor.
[Optimus One, P500 Original Android Development] fserve:
Hmmm

ok

Thank you for testing :-)
[Optimus One, P500 Original Android Development] franciscofranco:
What are you sniffing?
[Optimus One, P500 Original Android Development] fserve:
i've got a bug when i was using miks 6.6.1.

after wifi was disabled, music got little stops, the only solution was reboot the phone.

the same happened to me with andy phoenix rom...

Sent from my ASUS Transformer TF101
[Optimus One, P500 Original Android Development] franciscofranco:
Did you my latest testing version?
[Optimus One, P500 Original Android Development] rpankaj:
Kk.. here is shot.. no bug at 122 mhz..

Music smooth,wifi off
[Optimus One, P500 Original Android Development] fserve:
nops.

will test again later.

phoenix rom gave me another problem (viber wasnt at market), so i'm back to miks 6.5.8

Sent from my ASUS Transformer TF101
[Optimus One, P500 Original Android Development] voyager20021:
For bootloops on Miks CM7 fist post he says

If you get bootloop or stuck at LG logo do next:

Sometimes Recovery can't format /system so you need to clear /system manually. You can do it with this zip (flash as always in recovery), or in mounts menu (clockworkmod recovery only), or with adb:

1. Mount /system in recovery.

2. adb shell rm -rf /system/*

You get 1 error. This is ok.

Will update if I found this bug.

Anyone tried that zip or adb fix? I am not so familiar with adb shell. The zip i think is incompatible or smth.

Franco, do you know if this has something to do with random reboots caused by moving too many apps to sd?
[Optimus One, P500 Original Android Development] Hanny:
me.

that successfully wiped system partition and 2 months ago i did full wipe (including /system) and reinstall everything then do the same thing, and i got the same results - bootloop

please go to darktremor's main thread (nexus one dev forum) and scroll a few pages back, ive been yelling there for help and they did a lot to help me especially temasek(u know who? a famous n1 developer)....

but finally we got no conclusions trying everything, even switching to s2e had ****ed up my phone.

what solution i can tell is that

fk kernel + mik + dt a2sd script 2.7.5.2-1

+ apps staying on /EXT (shown "on phone")

= no problems

fk kernel + mik + dt a2sd script 2.7.5.2-1

+ apps staying partly on /EXT and partly on /android.secure (shown "on SD card")

= after booting (seen lockscreen) for about 3mins, the phone goes back to bootanimation and boot again

[im sure voyager is asking about this]

p.s. fk kernel + mik + dt 2.7.5.3 beta4

will result in LG logo stuck every 2 reboots. wipe /system no help.

hope my info is useful and yeah, take alook at the dt thread ;)

until now the only solution is not to move apps partly to /android.secure :):)
[Optimus One, P500 Original Android Development] franciscofranco:
Why move apps to sd card instead of /ext? doesn't make any sense............. No wonder **** happens...
[Optimus One, P500 Original Android Development] socialdistortion:
Haha! Exactly my thoughts.

Never had any problems with dt a2sd.
[Optimus One, P500 Original Android Development] Hanny:
Yea I agree with your point, moving the app only to /ext is apparently a safer method than dividing it into /ext and /android.secure :)

But however this method (using darktremor together with froyos a2sd feature) can save even more internal storage on our phones because darktremor doesn't move 100% of the "app" to /ext. Except "app data" , a small portion of "app" is also occupying the internal storage when using dartremor.

Say angry birds, despite its ~500kb /data size, when using darktremor, 18mb its "app" is moved to /ext while 2mb of it is staying in the internal storage. When using froyos a2sd feature, this 2mb is moved to /android.secure therefore even more internal space is free-ed.

According to the main darktremor thread, a user named bassmadrigal and even temasek himself, has stated that integrating darktremor "move to EXT" and froyos "move to FAT" does not produce any problems (at least on their nexus one) and can save even more space.

Well its not a problem for me as I only move 4 of my biggest apps to FAT and not having issues now.

I think voyagers attempting to move a lot of his apps (partly as they still partly stay at /ext) to /android.secure (as I tried before) and he got ****ed up like me before.

Hmmph I am not quite sure, voyager have you tried the same procedure (restore titanium and move them to FAT) without flashing Franco.kernel and only with the ROM (ans default kernel) and darktremor script installed? In that way we can see whether the "issue"(not at all but just an disadvantage of not supporting a feature) is about Franco's kernel or about our phones. :);) cheers!!
[Optimus One, P500 Original Android Development] franciscofranco:
Just don't mess with the part that stays in the phone, if you do you're on your own, it's just too damn obvious to waste my time with it, sorry :/
[Optimus One, P500 Original Android Development] Hanny:
yea, i definitely dont think it is of any priorities to request you to dig on this stuff :D and please dont, lol

was just telling my experiences to others and esp. voyager ;)
[Optimus One, P500 Original Android Development] franciscofranco:
Yes but this is nothing for me to dig, isn't kernel related.
[Optimus One, P500 Original Android Development] voyager20021:
Thanks guys, that`s what i needed to hear. Moving remaining bits of apps to sd causses reboots. But then again, this is a feature included in stock rom also? Except on stock internal memory is only 200Mb. So i only thought it would work on CM7 as well. I guess i was wrong. And i get it, it`s not kernel related. I pushed too many apps entirely to sd indeed as i have over 150. After reflashing kernel the system is stable, and also stable after moving a lot of aps to sd. It goes rebooting only at some point and i don`t understand why. Is there a limit? But this is off topic, so i`ll try to find answers elsewere.
[Optimus One, P500 Original Android Development] metalboy94:
Minmax seems a little bugged, as I get kernel panics even on frequencies which are stable on conservative et al.
[Optimus One, P500 Original Android Development] voyager20021:
So conservative rulls!
[Optimus One, P500 Original Android Development] metalboy94:
But I wanted something a bit faster for when it's charging, but not performance (that may produce unneeded heat). :(
[Optimus One, P500 Original Android Development] terratrix:
interactiveX maybe? Or just downclock one step lower when u use minmax
[Optimus One, P500 Original Android Development] metalboy94:
Well I downclocked to 729, which is stable on conservative. Gonna see how stable it is today, if not guess I'm going the InteractiveX way.
[Optimus One, P500 Original Android Development] voyager20021:
Use the outlet charging instead of USB. Is much faster. Or maybe a 2 USB data cable.
[Optimus One, P500 Original Android Development] Hanny:
:p haha he meant he wants *faster performance* when he is charging and *relatively slower performance* and savw battery when the charger is not with him :p

and metalboy i recommend you do a stress test for 2 hours at 729 conservative because i dont think there is bug in minmax, just it uses max freq more so u get panic faster. conservative uses max not much but u may also get panic at 729 somedays later though :) so yeah stress test can shorten the time for testing for u

so i would suggest you to try minmax 710 at charging and conservative 710 when not charging to get maximum stable;) (ofc as i said try stress 729conservativ first and see what u got :))
[Optimus One, P500 Original Android Development] Bec de Xorbin:
Just noticed that my phone was shutted down by itself. 12112011 kernel, CM7 6.6.1, 691/480 conservative. Oh well, maybe I still have to downclock it a bit. Otherwise no problems.
[Optimus One, P500 Original Android Development] Hanny:
yea it will solve the problem, sadly ur even more unlucky than me

but if u get strange stuffs like panic at 600, maybe thats because u didnt reboot between flashing rom and kernel, reflash kernel.will fix it :) goodluck on ur 672mhz!!