yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ro_explorer:
Ok, here we go again :) ...

What is a filesystem? Is a medium where you store data ... correct?

The word "store" comes from the fact you are writing your data onto that medium.

Here is the fake stuff:

The huge quadrant IO scores are generated by the fact that the writing operation on the filesystem is not done ACTUALLY on the file system but into the RAM. Quadrant seem to miss the fact that the "write OK" signal from the file system is not coming from the file system itself but from a daemon which, with the proper settings, can work with a huge RAM cache => incredible read/write speeds but not real.

Unfortunately this trick is just for scoring purposes and is not helping you in the real life because you are actually loosing the reliability of that data. The process which is initiating the write action will think the data is safe on the storage so it can quit, while that data is still in the ram-disk therefore NOT on the storage media ... so you can loose it if other process, with a higher priority than the respective daemon is reclaiming the ram.

That why the that IO score is fake .. because IT IS FAKE.

I 100% trust CPU/GPU and RAM scores of quadrant advanced .. but it is a big fail in the IO score .. and that is the point everyone is taking advantage of, w/o actually improving much.

It isn't simple phone for me either .. but I NEED to know that aat any time, in any moment and place, I can reach my phone in my pockect and use it as whatever I want .. w/o worrying that it is in a BSOD state ... or frozen ... or whatever it make it unusable. I also need to know that if my life will depend on a phone call or a communication situation, I can rely on that small device I'm carying around with me.

If I feel that this gadget is not up to the speed/cpu power expectations, I'll just buy a more powerful one (and there are plenty to choose from).

Even if there is no real 6500 quadrant score, I was trying to reveal the fact that some guys around here are trying to get drunk by drinking plain water ... ain't gonna happen.

As for the kernel ... I'm 100% with you. I know what this stuff is made from ... :)
[Nexus S Android Development] polobunny:
We are all well aware of how to trick quadrant io scores, but it's not even about this. There's nothing wrong in comparing a "fake io" quadrant score to another "fake io" quadrant score. Stop thinking about the letters IO for a second and imagine the value name would be "points". We're comparing points against points. Big deal. We're not debating whether quadrant io benchmark is a reliable io benchmark, simply comparing the value between different settings on an identical device.

And once again, reliability != performance. I want a reliable phone just as much as you do, doesn't mean I'm not looking for the absolute best performance I can squeeze out of my phone, while still staying stable.
[Nexus S Android Development] ro_explorer:
Have it your way. I promise I'll not say a word from now on referring to the quadrant scores.

And while talking about reliability, here we go with a bug report on nov. 25 kernel: connectivity loss. GSM signal greyed out .. no phone call possible, no data ... no airplane mode access ... I had to reboot.

Giving the fact that I've changed the radio and also from the past experiences .. I'll turn off the deep idle because I suspect this is the problem.

I'll report back with news ... hopefully, good news this time.
[Nexus S Android Development] bdpyo:
Quote so I can set this up!
[Nexus S Android Development] polobunny:
We all have different opinions, but it's pretty pointless to bash on anyone posting Quadrant score, as if it harmed you in any sort of way. :)

That's a weird bug, some people get it all the time and some don't. I've never EVER got a lost signal, with deep idle on or off. I'm starting to wonder if it's not an AOSP bug...
[Nexus S Android Development] simms22:
wonderfull! :D

next goal is to hit 6000 using ICS.

its too bad that the galaxy s 2 is hitting 8000 now.
[Nexus S Android Development] Cybergr:
Talking about a "fake" or not "fake" quadrant score i have to say, that this was the fact made me to include a detailed SETUP of every thing i have done to accomplished it.

If u don`t believe it, u can always try it by your self using my setup and cross fingers your device can handle it..!!

PS : No war here i`m not referring to any of you personally.

I`m well aware of that IO hack that ro_explorer mentioned in one of his previous posts and i can guarantee you that i haven`t used it to achieved what i have posted here. :-)

If anyone want so, i`ll try it and post back with detailed setup + the I/O hack! :-)

+1 for stability and reliability for me too..It`s obvious that my daily setup isn`t what i have posted!!Nothing extreme at all..not even LiveOC..just lazy gov and min set to 200Mhz with max set to 1200, Deep_idle -> Off .

That said..

I am pretty sure that disabling as u mention deep_idle will resolve the problem u had..I am not using deep_idle since from kernel version 23.11 and haven`t run into any of those troubles..No signal drops and radio dumps in combination with Oxygen 2.3.1 and XXKF1 radio and great battery life!
[Nexus S Android Development] polobunny:
I wouldn't expect less from a 1.2GHz dual core phone. :p

I'm wondering though, when you posted your Quadrant 6000+ screens, you had a much better 2D and 3D score than Cybergr got. Any idea why that would be?
[Nexus S Android Development] Cybergr:
Good luck mate!! ;-)

Thank you simms22..And doesn`t matter what the Galaxy S 2 can hit..The fact is that the Nexus S is a single core warrior and the faster i repeat "sigle core" out there!!

When i will leave this little monster i am gonna for the Galaxy Nexus for sure!

Probably wasn`t a 1.2Ghz Dual Core phone but in fact a 1.6Ghz+ phone under a good custom ROM and a good Kernel!This for sure cause my best friend has it stock and can`t hit those numbers!

I was wondering even my self this thing about 2D and 3D scores..but thats maybe cause of the mods CyanogenMOD team use!!Not really sure though!!Different ROMs and different kernels brings to different results i suppose!

(simms22 was under a CyanogenMOD kang ROM at the time and a Thermite15-S22b kernel)
[Nexus S Android Development] franciscofranco:
I've enjoyed reading these past posts, thanks people :)

There is a hack to make Quadrant score more, its mounting it inside a TMPFS partition, dunno if cyber is doing it, but I really doubt it.
[Nexus S Android Development] Cybergr:
Franco read my first post on these page!!I am telling about that hack!!I am well aware of that!! ;)

Maybe i am gonna try it tomorrow just for fun if i have such free time as today and post back!!:D
[Nexus S Android Development] polobunny:
Oh for sure it wasn't stock, but I haven't been overly impressed with the state and performance of dual core mobile CPUs so far. Nothing still making me itch to replace my trusty Nexus S.
[Nexus S Android Development] waterface:
Could you quickly point me to the post/s where you read about that?
[Nexus S Android Development] bdpyo:
I'm still laughing at this. lol
[Nexus S Android Development] derekwilkinson:
hey franco, i love your kernels... is there a way you can make a special version for me? i have different preferences
[Nexus S Android Development] krex:
NOV25 kernel is brutal! :) Thanks franco!

Please, enhance it with 1.4Ghz! Let it go! :)
[Nexus S Android Development] ro_explorer:
To be honest I have no idea where those posts were ... I was just reading over the net and I saw couple of guys mentioning this. I said it will not harm me to test this myself.

I didn't saw any difference from KF1 ... but trying another radio to check the data drop issue seemed like a good idea :).
[Nexus S Android Development] SilverEagle:
Ok, deep idle ON, stock voltage, lazy 200/1000 with max freq PASSED THE NIGHT without hanging. Testing now 110 liveOC (deep idle on) for daily use

EDIT...ok...liveoc is not for daily use on my phone, or at least not with deep idle
[Nexus S Android Development] marjaN_:
Try changing the arm voltage! I changed it to +25 and it's working for me.
[Nexus S Android Development] SilverEagle:
Ye maybe works but its wort it the ratio performance/batterydrain? (im trying btw)

anyway...what's the difference between arm and int voltage?
[Nexus S Android Development] ro_explorer:
I just had one radio drop with Nov 25 kernel, deep_idle off and using KB1 radio.

I've switched back to KF1 radio and kept all the other config.
[Nexus S Android Development] waterface:
Nov 23 was stable for me, and good battery, with deep idle enabled (Oxygen 2.3.1).

Testing Nov 25, but phone froze two times already at the lockscreen, just when I went to unlock it- the lock screen tab hung when I slided it to the right. Had to pull battery. Also I experienced a couple of signal losses, airplane mode on/off fixed it. Kinda want to do a full wipe, but I did wipe cache and dalvik before flashing 25.11 kernel, shouldn't it be enough?..

Just noticed that there is a folder named bugreports into /sdcard/, I wish I could decipher it. There must be valuable information in there!!
[Nexus S Android Development] hachoo:
Freshly flashing the 25/11 ker. Crashed overnight and drained more battery than with the 23/11. Only thing i've done is updated NStools in the mean time. Seems to have less battery at the moment, and I feel is less responsive. I'll keep testing though.
[Nexus S Android Development] suksit:
Exactly the same as mine. I tried 25 Nov build for a day and the battery went from 90% to 30% in ~12 hours. Now reverted back to 23 Nov build and got 60% left from similar usage.
[Nexus S Android Development] franciscofranco:
Thanks for the reports, although I dont see a reason for that, I'll take a look.
[Nexus S Android Development] Cybergr:
I will be fast and clear and i`ll not go through a deep explanation..!!

ARM = CPU

=========

INT = GPU

Hope was clear!:)

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

When updating NSTools is always recommend performing an NSTools reset with the zip provided on this link : http://xdaforums.com/showthread.php?t=1333696

I have run into those troubles with NSTools updates and the only solution was to reset it.
[Nexus S Android Development] polobunny:
Got a straaaange bug this morning. My phone was draining too fast for no apparent reason... Until I checked battery stats:

No idea what happened. Rebooting fixed it. If anyone has an idea, I'm all ears. :confused:
[Nexus S Android Development] franciscofranco:
Maps has been known as a ****ing battery killer if it stays open, keep asking for Location waking the phone up. I've observed this issue in all the phones I've worked on.
[Nexus S Android Development] saranyan:
When i initially got my phone, Maps would kill my battery. Found out that it was due to latitude, sign out of latitude and the battery drain vanishes.
[Nexus S Android Development] Icecoldmeat:
Ive been running this flawlessly so far, but with high-graphic games I got laggs and sometimes my phone freezes and I need to reboot.. am I doing something wrong? Ive tried a lot of frequencies/voltagss but it keeps happening..

Somebody knows a good combination for gaming?

Greets.

Sent from my Nexus S
[Nexus S Android Development] krex:
I think you did google maps update to 6.0 yesterday's evening...
[Nexus S Android Development] polobunny:
But I didn't open maps in forever. :|

Will check that

I might have when I did all my updates. There's a known problem with 6.0?

Edit: Nope, 5.12.0 updated nov 27th.
[Nexus S Android Development] belvedere:
Can't believe I never thought of this. I signed into Latitude recently and felt like my battery had been crappier as of late. Hopefully I notice a substantial difference!
[Nexus S Android Development] caleb1783:
thanks for a great kernel franco...

i've started a systematic way of testing out your kernel for battery drain, since everyone claims differently. Keep everything else same, while changing just 1 thing. And screenshot at the end of the day.

More of the testing at http://caleb1783.tistory.com/258
[Nexus S Android Development] benseoul:
hello,

when the screen turns off it makes a green color ... I'm on Miui and a NS amoled. Anyway thank you for this great kernel.

Envoyé depuis mon Google Nexus S avec Tapatalk
[Nexus S Android Development] polobunny:
Salut, c'est un bug connu lorsque les couleurs sont ajustées. Il y a 2-3 solutions:

-Tu remet les couleurs par défaut avec voodoo control

-dans voodoo control tu bouges le vert dans screen v1 gamma hack un peu. Des fois un de plus ou un de moins fonctionne

-si miui le permet tu met une animation au deverouillage (cyanogenmod le permet, je sais pas pour miui)
[Nexus S Android Development] benseoul:
Merci polobunny ;)

Qu'elle est ta configuration pour des couleurs instances sans ce petit Bug?

Envoyé depuis mon Google Nexus S avec Tapatalk
[Nexus S Android Development] skitapa:
Cool! Is that the dead language from futurama?

The Terminal is warm and inviting.
[Nexus S Android Development] hachoo:
25/11 kernel reset 3x today on stock (lazy, no deepidle) and after 9 hrs is down to 68% in mostly idle and some facebook/msging. I did the NSTool backup reset trick but it hasn't fixed anything that i know of. It did reset my settings, but the results haven't improved.

Might move back to the 23/11 until i can figure out why.
[Nexus S Android Development] SilverEagle:
Battery drain is fine for me (dunno if 23nov kernel was better because lack of testing), but sometimes (like 2/3 a day) i get a spontaneous reboot on stock voltage and everytime when the screen is off, regardless of deep idle or not.

Trying now to disable the manage permission on superuser (i'm on brainmasters miui).
[Nexus S Android Development] benseoul:
Okay sorry,

I will ask my question in English:

What is the best setting for intense colors without bug?
[Nexus S Android Development] phone_user:
Could you try these values?

#Screen v1 gamma offset color hack

red -30 / green -30 / blue -33

#Screen colors multipliers

red 2259970880 / green 2249744960 / blue 2556528160
[Nexus S Android Development] Zorrich:
You can also go into the advanced display control of miui, and change the dim value to 10 from 5. That will get rid of the green, and allow you to keep the punchy settings rather than dropping them down. I personally love the punchy settings, with 321, 321, 429 rbg.
[Nexus S Android Development] benseoul:
Thank you phone_user but the green color persists before the extinction of the screen...
[Nexus S Android Development] :
You could try Alt setting instead of punchy in voodoo

Sent from my SNES
[Nexus S Android Development] ValenteL:
Hi Francisco

I have now a Nexus S and installed the Koush CM9 Alpha 11. It work like a complete ROM. I Love that.:D

Your kernel, I must install the GB or ICS kernel on it?:)

Abraço

Manuel
[Nexus S Android Development] Tzorg:
I've been running it for a few hours and so far so good :)

Looking forward to the new version.
[Nexus S Android Development] coloxim:
I've terrible battery drain..with this kernel..1% every ten minute ..

I don't know why..only with this kernel..

Inviato dal mio Nexus S
[Nexus S Android Development] xXfuzzXx:
Yup, me too. Had 18% when going to bed last night... In the morning it was dead :D Just happens with this kernel :(
[Nexus S Android Development] skinniezinho:
You guys have something wrong.

I went to be with less than 40% and I still have 25% (After some use).

Although I had better battery with TEUV 05/10 (1% 8h in airplane mode everything off) this kernel has good battery too.The performance of this kernel even with undervolting is higher than the 0.88GHz TEUV (I think it may be even faster than the great TUV kernel too).
[Nexus S Android Development] coloxim:
I've tried anything but nothing change..

But i haven't freezer or reboot..

Inviato dal mio Nexus S
[Nexus S Android Development] xXfuzzXx:
Already thought about that, but there is nothing running in the background what hadnt run before.

Well, i'll do a fresh ROM install anyway with latest BM MIUI when he released the multi version, so i'll just c how it works :)
[Nexus S Android Development] ro_explorer:
I have a possible bug report.

I've played with 100-1200 MHz freq. range over past 3 days. Everything is stable and going smooth. The battery is excellent (2-3% over night - 8h).

Today Ive mounted a samba share from my NAS and I've tried to watch a 720p MKV movie using dice player (hardware decoder). The phone froze in 5 secind after starting to render the movie.

I've rebooted the device, set the maximum freq to 1100 MHz and played the same movie. My phone went into frozen mode in about 10-15 seconds.

Rebooted again, set the max, freq. to 1000MHz and repeated the movie play over wi-fi samba share ... everything went smooth.

Question: are you playing with the bus freq. and also with the GPU freq. by directly dividing the main CPU freq?

I'm thinking that my GPU doesn't take too well any overclock, that why my phone will freeze only if I'm in the OC mode and trying to use the HW acceleration.
[Nexus S Android Development] skinniezinho:
Could be your phone that needs more voltage in the 1000MHz+ settings to be "rockstable".

I guess franco didn't overclock nothing apart the cpu in this kernel.

---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------

Don't know...I would give a try for some days on a vanilla MIUI,with all wipes including battery stats.

I may be wrong,but even those "translations" of MIUI sometime behave differently.

I'm using MIUI PT (Portuguese) now and I may be wrong, but I think battery is worse than MIUI EN (same kernel)..but again it could be because of the updat to .21
[Nexus S Android Development] franciscofranco:
I think something is wrong with the 1100 frequency in the released kernel. In the next update all the overclocked frequencies will be gone and the only thing avaliable to overclock the device will be Live OC.
[Nexus S Android Development] as6:
nice

Looking forward for the release.
[Nexus S Android Development] bdpyo:
light to moderate use using oxygen 2.3 :)
[Nexus S Android Development] civicdrivr:
66% left, moderate use, 400/1200 smartassv2. CM7 N230.

Sent by carrier pigeon
[Nexus S Android Development] kecinzer:
Looking forward for next release. Is there any tools for LiveOC control? Or we need to use terminal emulator?
[Nexus S Android Development] franciscofranco:
As far as I know it's only possible via terminal emulator. Best thing to do is creating an init.d file with the shell command! I'll explain everything after I release it probably later in the night.
[Nexus S Android Development] ragnarokx:
Just flashed yesterday on Brainmaster's MIUI. Performance is excellent at 1GHz!

Looking forward to it :)
[Nexus S Android Development] civicdrivr:
Same here.

Sent by carrier pigeon
[Nexus S Android Development] idelgado782:
Installed and trying out now. Phone is working smooth so far.
[Nexus S Android Development] bgdxv:
Anyone else still not getting 100% charge? My i9023 charges to 97-98% and stops :( help. I wiped battery stats, clean install, everything
[Nexus S Android Development] pauldgroot:
Try charging to 100% while the device is off, you can check to see if 100% by pressing vol+ or - while it's off and charging. Then reboot into recovery and wipe stats.
[Nexus S Android Development] as6:
99

Stop at 99%
[Nexus S Android Development] Lalaca:
You should install the ICS kernel. Obviously.
[Nexus S Android Development] Icecoldmeat:
Looks like nobody wants to answer.

Sent from my Nexus S
[Nexus S Android Development] polobunny:
Not bad settings, feel a bit too bright to me though.
[Nexus S Android Development] Zorrich:
yea it is bright, but I like that :)
[Nexus S Android Development] vis80k:
fresh install of oxygen 2.3.1 and franco's kernel from 25th gave me sod on the first charging cycle. then on the next day, it froze up on me when i tried to unlock screen while charging.

Left all settings in nstools as default kernel setting. hm....

I guess it's time I give other kernels a chance;)
[Nexus S Android Development] bdpyo:
I think nstools blows, nothing but problems using that app, I typically run stock settings and never have an issue.
[Nexus S Android Development] Maximilian Mary:
Green screen is caused by a green gamma too low for your minimum brightness. Either raise the green gamma or raise your dim level.
[Nexus S Android Development] polobunny:
I'm using right now, decent setting. :)

NStools isn't the problem in itself as far as I'm aware, but I don't like the design at all. There's no fine granularity, it's either it starts up at boots and overrides everything or it doesn't start up at boot.

I prefer SetCPU way of woking, where you can set the voltage at boot, frequency at boot and so on. There's also no advanced options for governors (except option for lazy) in NStools, which isn't practical for those who use another governor but still want Ezekeel mods to be enabled or want a Live OC.

You have to use SetCPU + NStools, and that's just looking for conflicts. Or go the manual way.
[Nexus S Android Development] phone_user:
There is a possibility of your changing rom ;)
[Nexus S Android Development] franciscofranco:
I haven't had a single problem with this last update, and so did not a lot of users. I'll review some things by the weekend, until then I have no time.
[Nexus S Android Development] krex:
Oh-o .. I can't change between front- and backside camera without reboot with nov25 kernel. No liveoc, no deep idle. :(

Edit: after some reboots I can't reproduce it, works normally
[Nexus S Android Development] phone_user:
NSCollab_1.0.60 has "rm /dev/log/main" script (/system/etc/init.d/99nscollab)
[Nexus S Android Development] majorgoose:
just figured it out 2 hours ago... you beat me up to it ... :-)

Thanks !
[Nexus S Android Development] skitapa:
Hmm, I still cannot get my logs working. Flashed the zip, fixed the typo in 61logcat to modules, removed the line from 99nscollab that deletes dev log main. But when rebooting and checking I noticed that the logger module isn't loaded. I tried to load it with modprobe at 02,and 04 in init.d. Do I have to use insmod with full path instead, and at what stage in the init?

What am I missing?

The Terminal is warm and inviting.
[Nexus S Android Development] skitapa:
I am used to linux/unix and there you can restart services via the commandline, however, when trying to find documentation on how this works in android, I can only get info of how to do this through the java api. Can anyone point me to some good information about android internals?

The Terminal is warm and inviting.
[Nexus S Android Development] polobunny:
Read

http://wiki.cyanogenmod.com/wiki/ADB
[Nexus S Android Development] CommanderDuplex:
Hi, i would tell you my experienze with your Kernel

at first, it works very well and fast ! i use a CM7.1 Nightly Rom and your Kernel.

but what i note is , the Graphics performance are lower than the "Original CM" Kernel. could you test this ?
[Nexus S Android Development] polobunny:
How did you see this?
[Nexus S Android Development] SilverEagle:
Cant keep the deep idle stable...sometimes it self-reboots when the screen is off.

Voltages are stock
[Nexus S Android Development] frenccw:
Has anyone got this before? After SOD the phone charges itself via magic. My battery was at 57 and climbed up to 67 after reboot
[Nexus S Android Development] Ezekeel:
Stop that at once or I report you to a mod for breaking the laws of thermodynamics.
[Nexus S Android Development] SilverEagle:
LOL, did that to me too btw, but only because i reset battery stats
[Nexus S Android Development] stojshic:
At some point, there was ezekeel's cleanup script added to this kernel, right? Now, I want to know if it was removed in the meantime or something? I wanted to give another try to MIUI after a month of oxygen. KelLMSKing Rom has matrix as default kernel, and with it I got radom reboot while doing nothing, so I installed this kernel, but there's still a lot of init.d scripts, and I'm pretty sure some of them are not needed with this kernel, but have no idea which ones...