yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson Xperia Neo, Pro] BYTeXperience:
paul678 on testing-kgsl battery draining seems to be incredible (using INTERACTIVE 364-1401, SIO, KSM, 16bit transparency). Over the night i lost 60% using testing-kgsl kernel and Super Jelly Bean 2.5 on Neo V, in the morning my phone was off. Schedulers doesn't work even on this release for me. I think i will go back on test18, also in this testing kernel i saw that the toggle buttons react with delay, it is easy to see that trying to activate Torch using the toggle, need a lot of seconds to activate the camera led, with other kernels this is ok.

This are the things observed over one night of using, i will continue to use test18 due to battery draining problem.
[Sony Ericsson Xperia Neo, Pro] demolatorul:
Re: [Experimental-23FEB][Neo/V][JB]Only testers

I'm using the same Rom with same kernel with no problems at all, did you wiped cache and dalvik cache after installation?
[Sony Ericsson Xperia Neo, Pro] BYTeXperience:
YES, i have do that. I never had this problem, SJB was installed on test18 kernel. Maybe was a process who remained open, but the phone was off in the morning so i can't see what really happens over the night.
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Experimental-23FEB][Neo/V][JB]Only testers

Everything seems normal here. Battery drain is OK and so far no reboots.
[Sony Ericsson Xperia Neo, Pro] paul678:
At the moment I haven't finished with the kgsl patches and changes. We have fb_num=3 and Vsync is ON on the novatek-fwvga panel (also remember to delete flag line from build.prop) FPS stabilization seems pretty good from my point of view, there are some hiccups when cpu is changing frequency.

About the vmalloc usage I'll take a look myself to see how it is in cm10.

I have attached some tests down below, note that Facebook and Google+ are tested after they loaded the feed.

------------------

And now:

-for battery drain something remained in the background...I have no unusual drain

-yes seems scheduler thing is not fixed...maybe I forgot something

-toggle buttons react with delay: I have no problems with this so I can't figure out the cause. Try a fresh install.

I'm still testing the changes, it's possible I'll revert something regarding page memory allocation in kgsl but the rest seem to do ok.

OFFTOPIC: why are facebook mobile programmers so bad...If facebook process dies because something needs that memory, the process launches a restart signal and then floods the log with hundreds of messages, just to be closed again after 30 seconds and so on. This also calls for a patch in LMK to not kill the same task multiple times, will test it later this week. In the meantime Facebook mobile app ->uninstall!
[Sony Ericsson Xperia Neo, Pro] demolatorul:
Re: [Experimental-23FEB][Neo/V][JB]Only testers

Ok, i had a reboot using maps, kernel seems snappy but I kinda feel reacting strange, testing another kernel now to see the differences
[Sony Ericsson Xperia Neo, Pro] paul678:
Yes indeed, the changes were not complete.

Yesterday I finished everything I proposed for kgsl how ever some things don't cope well, device sometimes feels smoother other times it gives some hiccups don't know..will test further and then see what is wrong. I also should do a clean rom install but first I need to backup many things...

Major changes until now are like this

KGSL-change:
-add tracepoints
-cleaned power states
-Create a separate pool for mapping kgsl allocations
-Store process mem entries in a rbtree
-Allocate physical pages instead of using vmalloc
-disable early suspend and late resume for 2d cores.
-moved some gpu registers
-and many many more...to much code!

If someone can make a clean install -wipe everything- of the latest official CM10 weekly and provide feedback I'll be very grateful.

Meanwhile here is the compile after finishing changes:

http://www.mediafire.com/?tmm914lgzrekim6
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Experimental-24FEB][Neo/V][JB]Only testers

Yesterday the hw video rendering crashed or something suddenly i couldn't play any videos with the hw decoder, even videos that played fine. A reboot solved it and everything went back to normal. I was using PA. Today I'm flashing FXP 208 clean.
[Sony Ericsson Xperia Neo, Pro] paul678:
Yes that could happen yesterday because changes weren't finished. Can you please provide feedback after the clean install with the kernel from today, thank you very much! :good:
[Sony Ericsson Xperia Neo, Pro] mikegapinski:
Hi Paul!

Do you have sources of your kernel uploaded somewhere? I would like to try it with my AOSP platform ;)

Mike
[Sony Ericsson Xperia Neo, Pro] paul678:
Re: [Experimental-24FEB][Neo/V][JB]Only testers

Hello Mike,

Well no I have all the sources on my pc, will upload them but after I finish all my exams (2to go). And I'll have to learn git so I can upload them correctly.
[Sony Ericsson Xperia Neo, Pro] mikegapinski:
Screw the git if you don't have a git log of all your changes. just make clean and compress them in tgz
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Experimental-24FEB][Neo/V][JB]Only testers

So far performance is great on FXP208 and I haven't encountered any problems so far, will update this post if I find any! :thumbup: Keep up the great work!
[Sony Ericsson Xperia Neo, Pro] bambotcha:
but what is KGSL ??
[Sony Ericsson Xperia Neo, Pro] paul678:
That's great, however I really have some annoying hiccups and also some bugs that I'm investigating on kmsg. For example gallery went nuts today it didn't load the pictures, nothing showed on kmsg but on logcat there were some errors about video decoding and not finding some libs, however those shouldn't be related to kgsl...

It is the video driver behind our gpu do a quick search and you'll find what you look for. So please next time don't post this here :)
[Sony Ericsson Xperia Neo, Pro] paul678:
New version is up experimental#1 check first post for changelog and as usual please provide feedback.

EDIT: source is up on gDrive now link, I'll try to upload it on github next week or so but I don't promise.
[Sony Ericsson Xperia Neo, Pro] bambotcha:
Thanks for the great work ,, testing

And sorry if my question did upset you ,, :)
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
Why not continue the version number from test18 or 19?
[Sony Ericsson Xperia Neo, Pro] paul678:
I jumped to many build nr. example from test9 to test 16 or so...And that's why I thought to start fresh with a new numbering system. There will be more frequent updates now because tomorrow I have my last exam on this semester so I'll have more time to work on this :D
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
Anything you'd want us to test btw?
[Sony Ericsson Xperia Neo, Pro] paul678:
User experience:

-general day to day activities

-stability

-performance in heavy apps&games (btw check the new Real Racing3 it works flawlessly :) though it has some effects disabled but it's nice)

-battery

-any bugs?

Also if you can compare wi-fi signal, done a quick patch for signal but I'm not sure if it works as every wi-fi near me is 2bars min.
[Sony Ericsson Xperia Neo, Pro] venoma333:
Hey Paul, which ROM are you using to play Real Racing 3? It kinda lags on Slim Bean, but I think it's just the ROM...

Anyways, the new experimental version is holding up very well. So far no reboots, no noticeable glitches or other big problems.

Battery life is pretty good. I mean, it could be better, but it's sufficient for me so no complaints there.

I'm going back to FXP208 and I'll give you more info, because performance on Slim Bean has not been up to par with FXP so far. I really don't know why. I was definitely expecting more from that ROM.

EDIT: Also, Wi-Fi is slightly better maybe, but it could just be me...
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
Wifi seems to be improved, but could be placebo. Having wifi at my university, it's kind of a big space with several routers and usually it is buggy between two routers, but it seems to be a bit more stable. Not sure if the signal is really better, maybe 1 bar.

Battery is decent, I don't notice any difference, it's very much dependant on usage and CPU speed.

I've found your kernel in general to be very stable, also under heavy load (Minecraft PE with large view distance). But if I put the CPU on 1,6 GHz, it does reboot or freeze for a while about every 15 minutes while gaming (this was the same on previous kernels, maybe even on lupus).

General performance is very good, smooth experience, I'm using Smartassv2 governor, interactive & interactiveX & ondemand can get very laggy sometimes.

I will try Real Racing, but I can't believe what you say :eek:

I remember playing Real Racing 2 on Gingerbread last year and it was a bit laggy, but worse: the input lagged, so I missed every corner, making the game unplayable... Edit: reading some reviews, and seeing several people noticing it doesn't even run smooth on a Galaxy S4 Exynos quad! Edit2: other say it runs fine a Galaxy S1 and Galaxy S Wifi 5.0 (Hummingbird 1 GHz)

Good luck with your exams and have a nice weekend. Keep up the good work!
[Sony Ericsson Xperia Neo, Pro] paul678:
@venoma333: I'm using slimmed official CM10. Thanks for feedback, let me know how it is under FXp

@sdk16420: Hmm maybe interactive is a bit less smooth because it ramps down faster then smartassV2, anyway I really hope in 2 days we'll have the interactive governor from 3.4 with all the candy, I'm curious how it behaves.

About reboots and not stable at 1.6ghz it's because the cpu needs more voltage at that freq for it to be stable, we now have 1.3v@1.6ghz and the same @1.5ghz. If I up the voltage by .05 it will be stable but I have to look at the max operating voltage of the soc, and also if I can find something about the max Tcase temp, we have to remember this is mobile cpu architecture and it's more sensible.

just for the info voltage at 1.4ghz should be 1.225v lower then this I don't think it will be stable for everyone
[Sony Ericsson Xperia Neo, Pro] paul678:
Plans for this night:

- new Interactive, test smartassV3, changes to ondemand.

-changes to LMK including the code to not kill the same id

-Fsync controll maybe

-try to make crt animation work

-lets see that cpu voltage for higher freq

-hope I'll have more to come.

ETA late this night or tomorrow. Anything you would like me to look into?
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
Nice work, very disappointing though that you don't use an SCM so none of us can help.
[Sony Ericsson Xperia Neo, Pro] paul678:
Quick try to learn how to use github, however I didn't have time to commit all the changes separately so here is the link

https://github.com/paul678/semc-kernel-msm7x30/commit/39dc689407e131d3862c50e0a14a1180b85115e7

I'll work this week to set up the git properly. Now back to testing the changes as I wasn't home the other night so the release will be postponed just a little bit
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
Cool. I personally just use standard git package, but with heavy use of the "git gui" command. Very handy. But if you've already got all your current work in one big chunk, it can of course be painful to make seperate commits for each change.

You probably realized this already, but making those commits one by one for each feature is a very good idea so you can revert specific commits that may be causing issues, or otherwise not ideal.

Feel free to PM me if you want any more tips or help with git.
[Sony Ericsson Xperia Neo, Pro] muzik_demon:
Re: [Experimental-28FEB][Neo/V][JB]Only testers

Does this kernel support android 4.2.2?

Sent from my Xperia Neo V
[Sony Ericsson Xperia Neo, Pro] siankatabg:
No,its based on lupus and lupus don't have 4.2.2 kernel.

Bad English,sorry for that.
[Sony Ericsson Xperia Neo, Pro] paul678:
Ok...update will be late, messed up some things in kgsl and now memory is not allocated properly..have to backport more functions from 3.4 I think, if it doesn't work then I'll just revert
[Sony Ericsson Xperia Neo, Pro] paul678:
Ok Experimental#2 is up changes are:

Experimental#2

-Finishing touch on KGSL

-Patch LMK to not kill the same pid over and over

-We got touch boost on Interactive governor

-Add frandom

-Try to fix CRT animation but failed..

-Change some voltages, 1.6ghz may be stable now(use it carefully!)

-Changes from CM10 latest nightly

Remember to flash modules this time(download on first post). The thing with CRT animation, I think it has to be enabled at rom level also..

And one more thing can someone help me make a very small ramdisk?

EDIT: I'll push changes to github tomorrow :)
[Sony Ericsson Xperia Neo, Pro] demolatorul:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

As i know crt must be enabled in rom also, but lets see how this kernel perform, thanks
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
What do you mean? Just use mkbootfs binary to make a page-alignment-tagged cpio archive.
[Sony Ericsson Xperia Neo, Pro] paul678:
Well I use mkbootimg binary to "put together" the zImage and the ramdisk, the problem is that I use Williams ramdisk from lupus and it's pretty big in size 5mb or so and this results in the 6mb kernel. I'm trying to reduce the size to the smallest amount possible without breaking it as I know we had a problem booting small kernels. (my knowledge on ramdisk and recoverys is not so good :laugh: )

Anyway waiting for impressions about the kernel. At the moment I think KGSL is as up to date as possible, many things backported from 3.x. Let's see what I can do next :D
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Ok, so it's been a few hours and so far I've encountered a few bugs.

-LMK values behaving weirdly again. Leaving me with only 6-7MB of memory at some times which leads to awful UI choppiness.

-Ive attached a picture of a bug that happens sometimes when zooming in. Though it could just be surface dithering, because I've got that turned on.

-Also the phone started behaving weird at some point after I played a resource-heavy game and the it was registering normal touch events, but not hold and touch. Like if I wanted to move an app on my homescreen it would just launch the app. Though my device was connected to the charger at that time so it could have been just that. I've heard some people having similar problems and I think it's related to voltages personally.

Other than that everything else seems pretty fine. Performance is great. Overall great work on your part! :)

P.S. I'm sorry I cant find a screenshot of that bug, but I'll attach one if it happens again.
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
This?

This was on experimental #1 though, but I haven't experienced this on versions older than #1, and I didn't change anything of the ROM since weeks.
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Yeah, that exactly :D And I am using Experimental#2

Also, noticed the bug with holding events happening on my lockscreen. I'm using a pattern to unlock and it didn't register holding the dots. It has happened only twice so far, not on every unlock.
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
I don't have any other bugs on Experimental #1 (sorry, I meant Experimental #1)
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Well it could just be my digitizer going to hell I guess.
[Sony Ericsson Xperia Neo, Pro] tinyXperia:
More likely a bug with the ROM. Do you have many tweaks applied?
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Mmm no, none at all, except for the surface dithering and assets purging. Other than that, none.
[Sony Ericsson Xperia Neo, Pro] paul678:
-Well the touch problem has an unknown source, I had it on about 4 kernels but it disappeared on its own...(happened only on the pattern lock)However it can also be hardware fault or even the bug with the charger.

-About that zoom bug when exactly did it happen because I didn't have that problem so I need to try and replicate it.

-And finally LMK I only added a piece of code that check if the process was already been "sent to die" so it won't try and kill it again. The low memory situation shouldn't appear very often, maybe some poor coded app in the background. Anyway I'll test a more aggressive LMK this days and also try a new implementation with screen on and screen off ''profiles'' maybe it's better.

Thanks for feedback, I'm doing my best! Hope performance is good or great :D
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
mkbootfs is used to make the ramdisk image. This is from AOSP source, or you can grab a binary from e.g. my github.

I would take a look for you, but you don't seem to have the ramdisk on your github.

You can extract the ramdisk archive like this:

mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.cpio.gz | cpio -i

The CPIO archive is compressed in G-Zip usually. But I use LZMA compression on my kernel since its much higher compression and not noticibly slower at booting.

Anyway, you can do that and make the new ramdisk folder included in your git tree. Then you can build it in kernel make script like this (example only, your device values may vary as I'm sure you know):

GZip:

mkbootfs ./ramdisk | gzip > ramdisk.cpio.lzma
mkbootimg --base 0x00200000 --pagesize 131072 --kernel ./arch/arm/boot/zImage --ramdisk ramdisk.cpio.lzma -o boot.img
rm ramdisk.cpio.lzma

LZMA with max compression: (Smaller ramdisk but LZMA support must be enabled in kernel config)

mkbootfs ./ramdisk | lzma -9e -C crc32 > ramdisk.cpio.lzma
mkbootimg --base 0x00200000 --pagesize 131072 --kernel ./arch/arm/boot/zImage --ramdisk ramdisk.cpio.lzma -o boot.img
rm ramdisk.cpio.lzma

Make sense?

If you want to unpack your ramdisk archive to a new folder in your kernel source and push it to github, I'll take a look. That's a good idea IMO because then you can easily update ramdisk in source and the changes will be seen on github.

I won't be able to help too much because I've since switched my kernel to two-stage ramdisk (to allow for multiboot GB/ICS/JB ROM's with different RAMDisks).

You can get the mkbootfs binary from my repo if you need it - here. The .exe is for cygwin, don't use that.
[Sony Ericsson Xperia Neo, Pro] demolatorul:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Reporting, battery seams to be good and overall performance (didn't pay any game) but free ram is two times less than usually
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
The free RAM on Jellybean situation sucks. How much do you guys get? Turbo Kernel has max RAM capacity at 379MB, and in my MIUI5 beta which I've tried to tune to the max with some tricks, built-in memory freeing gets me to a highest of 156MB free - whereas GB could hit nearly 250MB free.
[Sony Ericsson Xperia Neo, Pro] paul678:
Well this one has 380mb, It got me to 180-190mb max on a clean rom but now I have 4pages of apps so...

First thing I'll look into for next release is LMK and OOm, real free amount should never drop to low and I've seen it today @2mb (this is terminal command not settings) but no UI lag at that value.

Do you all experience slowdowns with low amount of free ram?

@CosmicDan Thank you very much for the advice on ramdisk, I've read it and try to follow it!
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
Not sure if you're talking to me, but no I don't get slow-downs on low RAM because my LMK/OOM values are ones I've researched and tested/tuned a lot over the past year.

Free RAM in terminal command is free RAM as reported by the linux kernel - you would *never* want this to have too much free, because anything free there is being wasted. The best way for checking free RAM is inside Android with an app, any terminal command is specific to Unix and not the DalvikVM (remember - Android apps run in a VM called Dalvik, Dalvik is what should consume 99% of userspace RAM). Hope that makes sense.

Anyway, that 180-190 is not bad. Is that with an AOSP-style ROM e.g. SlimBean or CM10? Because I imagine they are naturally a bit lighter than MIUI5. I'll have to try out my AOSP 4.1.2 compile again, because if it's not similar then your kernel must have some nice memory-saving tricks.

EDIT: The "real" free RAM (terminal) fluctuates depending on I/O and native binaries, but if you have more than 20MB free then something is wrong with the ROM.
[Sony Ericsson Xperia Neo, Pro] paul678:
CM10 here, on pure AOSP you may get even more, and yes no slowdowns for me also. About the free reported by kernel I know it shouldn't get lower then 4-5mb but it shouldn't be a problem because it stays there for a very small amount of time. About the DalvikVM I know and it makes sense :) but I really think that the free ram reported by any app doesn't reflect that much if you have a good LMK, android caches many things and keeps apps in background for quick start but we all know that.

Anyway tomorrow I'm going snowboarding so I have 4 days to test the phone in day to day situations, if I find something wrong I try to fix it.

p.s I still need venoma333 or sdk16420 to tell me how to get that bug they showed me.
[Sony Ericsson Xperia Neo, Pro] CosmicDan:
Jellybean reports free RAM properly from what I can see - it does not count background/cached apps, only active memory from running services and foreground apps. It's not quite as verbose as e.g. SystemPanel but the values are always consistent across all the apps I use.

LMK doesn't mean anything when it comes to gaming. If all the RAM is consumed by a foreground app (e.g. game) it will have killed everything except essential services, regardless of LMK. But in the case of a game, especially on Jellybean, they will start to lag when RAM is full because there simply isn't enough memory to hold all the resources. OOM and LMK values make no difference at all in this case - free RAM is a good indiciation of how heavy the ROM is though.
[Sony Ericsson Xperia Neo, Pro] paul678:
Starting work for next release, have some ideas to implement.

Any more bugs?By the way no one told me how they got that "display or zooming" bug so I can't try to fix it.

If all goes well release will be on Saturday or Sunday :)
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Well you can't really recreate the zooming bug at your leisure. It just happens sometimes, but I can live with it :D
[Sony Ericsson Xperia Neo, Pro] bluestricker_21:
Hey Paul.why don't you request to the Op to move this thread

In development section, it will be better if this is present there
[Sony Ericsson Xperia Neo, Pro] demolatorul:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

I was thinking the same, I think it's better that way
[Sony Ericsson Xperia Neo, Pro] paul678:
Well maybe I'll get it some day and hopefully I can fix it :)

Moved :)

Sorry latest changes still not pushed to github, didn't have time but will do so before next release!
[Sony Ericsson Xperia Neo, Pro] venoma333:
Re: [Kernel][6MAR][Neo/V][JB]Experimental-Only testers

Ok, so far my impressions from the Experimental#2 + FXP210 are pretty amazing. I haven't encountered any bugs and performance is great.

Just sometimes games behave really choppy and are only fixed by a reboot... Any idea what's causing that?
[Sony Ericsson Xperia Neo, Pro] bluestricker_21:
Nice..it is already here..thanks op
[Sony Ericsson Xperia Neo, Pro] dugzino:
Awesome kernel! Ingress launches pretty fast with it :D

Thanks for your time Paul & Wedgess!
[Sony Ericsson Xperia Neo, Pro] paul678:
Nice to hear this and about slowdowns I hope they will be gone in next release :)

Testing different changes now.
[Sony Ericsson Xperia Neo, Pro] mido_fedo:
very nice my bro i try Experimental#2 + last nightly and the rom so far and very very smooth nice work
[Sony Ericsson Xperia Neo, Pro] dugzino:
Is the 720p recording, kernel related? By that I mean, is it possible to activate 720p recordings via kernel.

If yes, could you? Or will it eat more than those 30MB RAM you free'd?

As for Experimental #2, clean so far. I used to set "SmartassV2" as governor on Lupus but, "Interactive" on this kernel seem to work way better..