yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] LKNim:
What I mean is

I use NOOP SmartmassV2 1300 102%

No freeze, no auto reboot

After manual reboot then open NSTools, the settings changed itself, it becomes VR SmartassV2 1000 100%

Which means some settings doesn't stick, I never experience this in the other kernels

Sorry to my poor English:(
[Nexus S Android Development] y3mita:
I mean i9020 device like mine so I can use your kernel
[Nexus S Android Development] novic_dev:
Can anybody test Beta 6 on i9020?

Is it booting up correctly?..

I have only i9023 device and can't test kernel on i9020 :(

Great thanks for all!!! ;)
[Nexus S Android Development] y3mita:
Just read op will flash soon
[Nexus S Android Development] y3mita:
Bad news!! It doesn't work :(
[Nexus S Android Development] mamba720027:
Same here,dosent work,but willing to test next
[Nexus S Android Development] daniel3ric:
Tried 45Hz over CM9. Does not boot.
[Nexus S Android Development] teckx:
i9020a aosp 4.0.3, does no boot
[Nexus S Android Development] navillos:
Isn't the stock refresh 60hz? Why no stock one?
[Nexus S Android Development] novic_dev:
Hi for all!!!

Please try THIS kernel on your i9020 devices! Thanks! ;)
[Nexus S Android Development] novic_dev:
All's OK with M1 on i9020 on 4PDA Russian discussion forum..

Any proves?.. :)

If so - I will correct i9020 support in Beta 7.
[Nexus S Android Development] mamba720027:
So far booted and running great.Did some bench and notice performance improvements an looks like although Hz is capped still performs fantastic. Also voodoo colors does not work but its a working kernel :)
[Nexus S Android Development] novic_dev:
Thanks for testing!

Voodoo colors patch is used and colors are now statically corrected to -24 -30 -33

Do you mean the ability to tune colors via voodoo app?
[Nexus S Android Development] mamba720027:
Ok I see.Yea meant the ability to tune colors by voodoo app.The static colors works good with my themed ics plus no green flicker when turning on or off the screen.
[Nexus S Android Development] novic_dev:
Before Beta 7 today I'll release Milestone 2 of Anidroid-Hardened Kernel to finally debug Beta5-Beta6 display driver issues on i9020 (AMOLED) devices..
[Nexus S Android Development] morfic:
we have a few scenarios, you only focus on that one corner case

1) it is very simple to render and will run at 56fps or 65fps, no problem. (here you would feel 65fps helps)

2) it is moderately hard to render but can keep at 56fps, but phone can't reach 65fps and thus hits nasty 33fps spots due to vsync (here you might feel 65fps hurts)

3) it is very demanding and you can not reach 56fps, could reach 40fps but, you render at 28fps due to vsync, on a 65fps kernel again you render at 33fps (here you would feel 65fps helps)

If it's worth it or not will be a very personal choice. To say it is categorically pointless is not the best choice of words.

Side note, a sentence started with "No offense" is acknowledging that it does just that and thus should be time to reflect if one wants to go forth and finish the sentence one intends to add after those words.

Side note #2, quoting you would be easier if those links wouldn't part of your message, why not stick them in your signature?
[Nexus S Android Development] :
I'll reply to that in your thread :)
[Nexus S Android Development] :
This works. Max fps reads as 44?

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] mamba720027:
Make sure to put a check on "set on boot" in nstools settings tab.
[Nexus S Android Development] novic_dev:
M1 provides STOCK 60 FPS Framerate. Fps2D app shows me an 56 average FPS.

M2 will provide only 45 FPS limit.

These today's Milestone builds will help me to debug display driver issues on i9020 ;)
[Nexus S Android Development] :
Oh... I had it in my head that it was 40 limit.

So the link you posted was for M2 correct? The .zip has M1 in the name: .../AniDroid_Hardened_M1.zip/download
[Nexus S Android Development] daniel3ric:
It works for me. Gamma hack in Voodoo control does not work, but default colors are ok.
[Nexus S Android Development] novic_dev:
No, the link provided was to M1.. M2 will be released some time later today
[Nexus S Android Development] :
Sorry I'm confused. You said M1 has 60fps? I'm seeing 45.

Anyway, the benchmark is done!
[Nexus S Android Development] novic_dev:
What tools are you using to benchrark?

fps2D shows me 56 FPS
[Nexus S Android Development] :
I'm using AnTuTu 3D test....

Hang on, just downloaded fps2d and it also shows 42 with stddev 2.66

(nice app btw)

So... what's happened? Wrong zip uploaded?
[Nexus S Android Development] novic_dev:
No.. no.. ZIP uploaded is correct..

I'm using 1000 MHz max CPU freq, and what freq you are using?
[Nexus S Android Development] :
This is what I'm seeing. 1000mhz locked

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] LKNim:
I know how to use NSTools

Both BLN,BLX,TW,CPU governor are stick.

It's strange that IO scheduler, CPU freq, Live OC will become default after every reboot, which is VR 1000 100%
[Nexus S Android Development] novic_dev:
It can be an AMODED display issue or ROM issues... :confused:

The kernel provides FPS unlock up to 60 Hz and you system cannot render this value due to some reasons..
[Nexus S Android Development] novic_dev:
Try to uncheck and check "Apply on boot" in NSTOOLS after changing the settings.

If it doesn't work for you - try to reproduce this situation on M1 build and tell us the results.
[Nexus S Android Development] y3mita:
I think it's an NSTOOLS bug. It doesn't remember settings, once you boot.
[Nexus S Android Development] :
I've tried it on another ROM now, same result, 45fps.

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] novic_dev:
I haven't this bug on NSTools 1.15
[Nexus S Android Development] novic_dev:
On my SCLCD display and CM9 Nightly it has 56 fps..

So, it's likely an AMOLED issue.. Need to review video driver code..
[Nexus S Android Development] LKNim:
I tried this, doesn't help

M1 have the same result

I even reflash the ROM, reinstall NSTools

Still got the same result:(

Will try to full wipe tomorrow:o
[Nexus S Android Development] novic_dev:
Sorry, but it's not a kernel problem :(
[Nexus S Android Development] y3mita:
Like I said before it's an NSTOOL bug... it happens to me too I have to manually set the settings after boot up.
[Nexus S Android Development] Gazoo222:
for what it is worth, I had the same bug running CNA rom, with NSTools, I would find my phone set at 1000 min and max, I would reset to 200/1400, and shortly after it was back to 1000/1000. I would set it to 200/1400, check set at boot and then boot, only to find the settings back at 1000/1000.

Got rid of NSTools and everything worked fine using the roms settings for cpu Mhz, all though now I have no control of the cfg/noop settings or live O/C
[Nexus S Android Development] y3mita:
http://xdaforums.com/showpost.php?p=22918136&postcount=683

http://xdaforums.com/showpost.php?p=22980323&postcount=692

http://xdaforums.com/showpost.php?p=23239844&postcount=709
[Nexus S Android Development] LKNim:
After wipe data/factory reset, same result

I won't say that is single bug from ROM/kernel/tools

Below is some of my previous combinations with NSTools 1.15

Pixel Lite Touch + Air = OK

CyberGR + Air = OK

CyberGR + Trinity = OK

AOKP + Trinity = OK

AOKP + Air = OK

AOKP + AniDroid = Partially OK

(IO Scheduler, CPU freq, Live OC settings will go back to default value after reboot)

It seems that AOKP don't like AniDroid on NSTools, how I solve it is just simply flash Air over AniDroid

Will be back in future version to see if it works for me:o
[Nexus S Android Development] teckx:
now starts, but runs slow :(

sorry for my English
[Nexus S Android Development] novic_dev:
It cannot be a kernel problem because NSTools is an app that runs in rom environment, reads saved settings and apply these settings by writing them to kernel management interface (ex: /proc ).

So, here NSTools cannot read the correct settings, but can transfer them to kernel..
[Nexus S Android Development] stremax:
usb issue

does anybody got issue with usb mounting?

connected to my pc but recognized as well... running CNA v1.5.5 and anidroid b6 on a 9023

solved: enabled and disabled root permission for adb and apps, selected only apps, reboot and now works fine, really don't know if a kernel or rom issue
[Nexus S Android Development] novic_dev:
All i9020 users!!! :)

You are welcome to try Milestone 2 (M2) build of AniDroid-Hardened :)

It provides only up to 45 FPS display refresh rate support, it helps me to test the display driver for your devices.
[Nexus S Android Development] y3mita:
Flashed M2 and phone boots fine now... will test for issues!

Thanks
[Nexus S Android Development] warrenbey:
not workin for me :(

my phone stuck off after google logo !!

any suggestions ??
[Nexus S Android Development] navillos:
Yup milestone 1 definitely has the 45fps cap. I'm using cybergr v9 and have tried with multiple kernels. All get around 56fps and m1 gets 44fps.
[Nexus S Android Development] novic_dev:
Just found a BUG in the display driver.. So, that was the problem with i9020.

Will correct and release Beta 7.
[Nexus S Android Development] Dorilife:
I must say this kernel seems pretty good, just flashed a rom which brings your kernel by default and it seems solid, thanks for the work put into this.:cool:
[Nexus S Android Development] navillos:
why no stock fps b7?
[Nexus S Android Development] y3mita:
Is beta 7 the same as M2?
[Nexus S Android Development] ljordan2:
OC up to 2.0 GHz? Have anybody tried 2.0 Ghz?
[Nexus S Android Development] qtwrk:
I have been up to 1.68G for minute with matr1x kernel.

But doesn't anyone ever worry about that speed may damage hardware?

Sent from Google Nexus S using xda premium while eating Ice Cream Sandwich
[Nexus S Android Development] ClericDade:
Beta 7 is working on 9020, thx. The only little problem no is that voodoo colours works just like in Air Kernel - changing values of Screen v1 gamma hack below 0 just doesn't make any effect. I know that it's all because the green flicking fix, but now colours are not great, IMHO.
[Nexus S Android Development] novic_dev:
No, M2 (as M1) has many code changes and optimizations reverted and was used to understand what was the problem with i9020 devices.
[Nexus S Android Development] novic_dev:
Kernel with stock FPS will be available till Beta 8.
[Nexus S Android Development] :
Seems like pretty decent battery life to me. 45fps minimum brightness. Also accidentally locked the frequency to 1440mhz for a couple of hours.

Total drop: 80%

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] y3mita:
B7 running fine
[Nexus S Android Development] mamba720027:
B7 45hz working great.
[Nexus S Android Development] glennkaonang:
Will 45 fps refresh rate have any effects on i9023 with SLCD?

Or does this only apply to SAMOLED?

Thanks.
[Nexus S Android Development] lolokman:
working perfectly on i9023
[Nexus S Android Development] novic_dev:
Refresh Rate affects both i9020 and i9023 devices.
[Nexus S Android Development] lolokman:
I decide to switch to your kernel from now on.

45Hz saves more battery than I have expected. Just great.

It is the first time I can have 5.5 hours screen on time.
[Nexus S Android Development] novic_dev:
Just for the information:

As I've tested already - 43 Hz for display seems to be the lowest value to provide stability for SCLCD and AMOLED displays on Nexus S devices..

So, I've used 45 Hz to provide guaranteed stability for my kernel ;)
[Nexus S Android Development] ClericDade:
Running B7 for a 24 hours. 65Hz, liveOC 110, 100-1000 (100-1100 with liveOC), SIO/smartassV2, default voltages. Had 2 reboots. Just for a statistic.
[Nexus S Android Development] Oodie:
Tried B7 45 .. its really laggy . Gonna try 65 version.
[Nexus S Android Development] novic_dev:
Please try to use without LiveOC. Every system supports different OC values due to for example it's CPU production properties (revision, silicon material properties and so on).. If you wish to use OC - you have to find out the stable values for your device by using different OC and Voltage settings!
[Nexus S Android Development] novic_dev:
And what kind of lags do you have? :confused:
[Nexus S Android Development] Oodie:
Rom feels laggy . Launcher , app launching .. etc . Tried the 65 version . Still the same . I'm running cybergrmod on my 9030 . Back to t11 , all is good . Wonder what the issue is . Also tried deleting your init tweak , still the same .
[Nexus S Android Development] zadnica:
+1, Beta 7 is laggy. I use 45Hz.
[Nexus S Android Development] DaXmax:
I would +1 to that too. Tried both version, lags on i9023. Which i assume, B7 will only works better on SAMOLED models. Going back to Speedy Kernel...
[Nexus S Android Development] y3mita:
Feels good here!!
[Nexus S Android Development] novic_dev:
I haven't any lags on my i9023 SCLCD.

So, can you give me more detailed information about the lags?

Do you using OC/LiveOC? Do you using custom or kernel stock voltages?

Thanks for the information! ;)
[Nexus S Android Development] ClericDade:
I know it. I've tried a lot of combinations and the one i\I posted before is stable for my device.
[Nexus S Android Development] zipredictive:
+1 laggy ill try b6
[Nexus S Android Development] novic_dev:
OK, thanks a lot!!!

And if Beta 6 will work for you I'll understand the reason of this issue and fix it as soon as possible
[Nexus S Android Development] DaXmax:
I guess one of your fixes or testing screw the gpu rendering... Anyway, was running on 1200/400 SavagedZen... Both 45/65hz has lags. :/

P.S Beta 6 works fine! ^^
[Nexus S Android Development] y3mita:
I'm running vr-ondemandx loc 110% and it's buttery smooth!
[Nexus S Android Development] y3mita:
I still can't make Airdroid work?? It only happens with this kernel... if I use Air_Kernel by r_data everything works fine.
[Nexus S Android Development] Oodie:
Sorry for the less detailed report . I used stock settings .. NO live oc , No oc . Stock voltages .

After 2-3 reboots I tried with different governors , but its also the same .

So after another reboot , I deleted your init.d script & checked again ( I thought it conflicts with other tweaks ) . But its also the same .

Hope this will help you & Looking forward to B8 :)
[Nexus S Android Development] noobiekins:
I definitely feel lag on the 45hz version, I came from a air kernel 65hz and it feels more painful than it should be, even games like unblockme feel sluggish
[Nexus S Android Development] morfic:
Even 49Hz makes the UI too painful for my taste, fwiw.
[Nexus S Android Development] y3mita:
It's not laggy here
[Nexus S Android Development] mamba720027:
Strange cause i run the B7 45hz on codename android rom ver 1.3 with scheduler deadline an lulzactive governor at 1.3mhz clock with everything else default and run stable with no lags .Have the superamoled screen here.
[Nexus S Android Development] deetailed:
I tried beta 7 on AOKP M4 and had problems with 2 apps that pulls external data:

- FBReader couldn't use fonts from sdcard, only shows Android's original fonts

- Smurf Village loses the saved game

I rebooted a couple of times and reflashed once, but the problem remains.

Not sure about other apps, because I have to admit not testing everything extensively before flashing a new kernel (Air 3.6).
[Nexus S Android Development] novic_dev:
All App lags in current version of kernel are now GRsecurity related.

I'm working on fixing this kind of issues now.
[Nexus S Android Development] Shadow-Nexus:
Nice kernel man I really like that it has voodoo colors and no green screen bug

And all the customization is wonderful thanks
[Nexus S Android Development] y3mita:
Would you please install airdroid app on your device and see why it doesn't work?

Unless you already know why
[Nexus S Android Development] PIKO1982:
I have tried all kernel, but this is the worst. This kernel (65) is full of lag, in any combination (governor / scheduler) that can be done.

I return to use the fantastic ICUP Speedy 7 (with PixelRom)
[Nexus S Android Development] roshga:
comments like that one are driving me mad.

Please tell me mr. piko, have you ever did something for the community? did you ever tried sharing your development with others? nah, lemme guess, It's just so much easier to complain and offend things that you got for FREE.

That's a really mature comment for a 30 years old man (considering that the 1982 means your birth year).

Let me advise you on how to make a helping and not a craping comment:

Hi,

Im getting lags with every governor/scheduler that I try to use.

Using beta7 (65fps version) with PixelRom

I tried to do blablablabla and the phone did blublublublu.

And this is an example of how to treat a human being who's trying to be nice and help you. With that said - @novic_dev, Thanks a lot for your hard time developing this kernel and listening to us whining about it, your work is much appreciated! :D
[Nexus S Android Development] PIKO1982:
I'm not disregarding your work but I'm just giving an evaluation of the kernel. For a long time I have been developer for nokia symbian. I am aware of the work that a developer should be. Try to understand the motivations of the criticisms that people make in order to improve your kernel
[Nexus S Android Development] DaXmax:
Really? I only went back to M1 cuz it works better.

Seriously, stop the **** before you do.

@roshga, its up to him to comment in a good or bad way, anyway, novic will ignore it (cuz devs doesnt have time to view comments unless its necessary)

@PIKO1982 I've been there before for Sony Ericsson Satio, but please... Do some testing and sastified yourself. M1 axed it. Novic and the others has tried their best to made this kernel fast, smooth like a Quad-Core phone.

Morfic's, Novic's, r_data's, steve.garon's and Mathkid's kernel are monster. But, the others, tried, but they not improving it as they are busy themselves...
[Nexus S Android Development] roshga:
Dude... I'm not the kernel's dev... read the names man..

Just saying - There's a way to give a criticism. saying "this is crap" is not a good way of doing so.

anyways, not gonna spoil this thread with an argument, that's my last comment on this topic and as an answer to you and what I see as user's rudeness.
[Nexus S Android Development] y3mita:
I had to go back to air kernel, once wifi apps work I'll be back to try
[Nexus S Android Development] DaXmax:
Played Hot Pursuit for an hour+

Battery from 97% to 55%
[Nexus S Android Development] mamba720027:
B7 45hz after a full day and night drain
[Nexus S Android Development] WarByte:
Tried to stay quiet but I just can't. Criticism? Okay, it is the worst? How come? Is it slow? Is it unstable? under what scenarios? What rom? Overclocked or underclocked? Multitasking? That along with some personal ideas or thoughts could be called criticism.

You are free to say whatever the heck you want but I find it hard to believe you are a developer when you say things like that. Okay, developer mind: Good base, "hardened", GRSecurity, wow, 8 new features I never heard of. Do we really need them? maybe not. Will they cause overhead? Of course. It is only one guy, will it be buggy and/ or unstable or will he run into trouble? Of course. Is there a precedence to what he is doing? Nope, I see a storm ahead.

Checked the history? Alphas and betas with some some heavy changes among what is enabled and what not. Would you as a developer expect out of this kernel the much awaited next speedy? twice as fast? Of course not! It will be slower and even then I tried myself and it is not that much slower. Due to the nature of the security features that this guy is trying to implement there are gonna be unforseen issues but heck, let's flash and try.

Come on man, even when it was a long time ago I remember those days when we were taught in college that the best value a developer could have is to be humble. Listen and learn. I'd love to see how this guy does all this stuff and even if I already knew all that I am sure I am gonna learn something anyways.

OP, thanks for the kernel. When I look back at stuff I coded in the past I realize how bad I did it, but I was proud back then. It is an undescriptible joy to see stuff executing and I will never forget all those times I ran into issues I thought I could never solve, I will also never forget all those who offered me moral support :) keep on going man, have fun, there are bunches here who appreciate what you do.
[Nexus S Android Development] mamba720027:
Complaining to a dev about problems is fine for improvement sake but people don't need to be critical towards a project a dev is pushing esp in beta stage of development. Theres alot of working kernel around if anyone feel they are not content with the free time and effort a dev steps forward and put into there work for free but remember every kernel available for the nexus s had a phase it had to go threw to get where it is today and no thanx for many who do not test and report a problem if there is one but step forward to only reap. So being critical and steam out like the above non mentioned name (s) does not make things improve.
[Nexus S Android Development] enik_fox:
I saw 2.0 ghz and now I'm excited!
[Nexus S Android Development] aLNG:
Hope dev can fix the path of smartassv2 params so that I can start using this awesome kernel.
[Nexus S Android Development] novic_dev:
Thanks to all for the useful comments! ;)

After my primary work time I'm hard working on porting AniDroid-Hardened to Linux 3.3 to bring you completele new stable kernel based on 3.3!

All improvements to 3.1.10 are also scheduled, but now (temporarely I'm sick) I haven't so much time to complete all these stages in a short time.

So, I'll try to apply all my stability improvements and release Beta 8 (the last Beta before Stable) version of AniDroid-Hardened during this or the next week!

Thanks for Your patience! ;)
[Nexus S Android Development] att1cus:
You should quit smoking...
[Nexus S Android Development] hideto000:
with cyanogenmod 9 nightly this kernel doesnt work ... why?

It loading forever on boot screen with google logo.
[Nexus S Android Development] fleischbanane:
It works fine for me with CM9 nightlys and eurokangs.

Gesendet von meinem Nexus S mit Tapatalk 2
[Nexus S Android Development] hideto000:
I have this ROM :

update-cm-9-20120324-NIGHTLY-crespo-signed.zip

but the two kernel fails ...

for now I use trinity kernel for cm9

help me please :/
[Nexus S Android Development] fleischbanane:
I am using this one: update-cm-9.0.0-RC0-crespo-KANG-signed.03232012-0800.zip

Look here: http://fitsnugly.euroskank.com/skankwich/?id=crespo

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] hideto000:
thank you now it works!

but unfortunately I gained only 2500 score on quadrant with 1440 mhz and performance :(

its much more with trinity kernel
[Nexus S Android Development] morfic:
compare a trinity score of yours with his, is it I/O that is much higher than the rest?

then you could try remounting /data with a ext4 mount option that has been in use since curio first built his voodoo lagfix ramdisks.

compare the results side by side, this will help him know which area to focus on.

the average does not help him improve/change things.

on the linux terminal do this:

you should see 1 or more lines containing noauto_da_alloc, if not ask him to test this for his kernel

If it already uses this on /data i would like to know which individual score is so much lower (99% sure it's going to be I/O though)

hope this helps
[Nexus S Android Development] morfic:
Since i probably won't be around when you are, i am referring to this:

This can be run out of a script in init.d, but i strongly suggest to try the second line by itself in terminal before adding any scripts you don't know who pasted to your init.d
[Nexus S Android Development] simms22:
to add to what morfic said, try this script in a terminal emulator, it might help you enjoy this AniDroid-Hardened kernel, as it is, a little more. in a terminal emulator type..

su(press enter)

mount -o remount,noauto_da_alloc /data /data(press enter)