Database Users

linux patch that MASSIVELY improves smoothness

http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1
This is a 200 line patch that according to linux was according to Linus the most impressive result of code that is elegant - 200 lines long - and should be wound into the phone linux as well
---- edit - and here is why it isnt going to be of any use for us...
http://forum.xda-developers.com/showthread.php?t=822756&page=210
and the meat of it from bilboa1 :-
Originally Posted by giulio.alfano
Have you seen these? w_w_w.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1
Phoronix(and Linus) say that is a miraculous 200 lines patch to increase interactivty? Can you consider the inclusion, of course if group scheduling in android 2.6.32 kernel is compatible?
the process groups are created per tty, that wont work on android
you can create process groups by hand however but it doesn't make a lot of sense for android in that case. the goal is to have some intensive tasks into their own group, but theres no intensive tasks and we don't have issues like audio or video lagging
their tweak is especially good if you run a compilation in the background and want to browse the web while waiting without having slow downs.
on android if you browse the web you dont have other cpu heavy tasks in progress usually (like encoding a video or what not)
i hope that was clear enough

I've off works urlaub would bei awesome
Where are the developers, who can say, if it works?
Sent from my GT-I9000 using my Brain

Wouldnt get too excited,phoronix is like the sun of linux news
Sent from my GT-I9000 using XDA App

Already discussed - its useless on phone. Phone will be even slower.
Sent from my GT-I9000 using XDA App

dupel said:
Already discussed - its useless on phone. Phone will be even slower.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Lets save statements like these after it has been actually tested.

KhaaL said:
Lets save statements like these after it has been actually tested.
Click to expand...
Click to collapse
Not everything needs to be tested. If you make a program to draw a circle, it wont make a square, let alone cook eggs. (it's the case for this patch at the technical level, beyond the "wow" words from 1st post)
Note: there's other patches in 2.6.37 for responsiveness which are different from the one spoken about here which are actually likely to improve things. But probably not as drastic.

dupel said:
Already discussed - its useless on phone. Phone will be even slower.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Got any links to where I can find out what you know?
I was *hoping* that if it made desktops much more responsive under heavy loadings that it would help with the phone - its not like we have slow cpu's in these things Or is it cpu architecture that allows the improvments and the phones just are not compatible? or something else?
just wanting to know more and to hopefully get a dev who thinks its worth taking a look to see - 200 lines of code - *cof* (ducks behind armour) "how hard could it be?" *runs for cover*
i get this sinking feeling from the subtle - and not so subtle comments from you guys tho - that its just not really suited for how android works on a phone....

cbdrift said:
Got any links to where I can find out what you know?
I was *hoping* that if it made desktops much more responsive under heavy loadings that it would help with the phone - its not like we have slow cpu's in these things Or is it cpu architecture that allows the improvments and the phones just are not compatible? or something else?
just wanting to know more and to hopefully get a dev who thinks its worth taking a look to see - 200 lines of code - *cof* (ducks behind armour) "how hard could it be?" *runs for cover*
i get this sinking feeling from the subtle - and not so subtle comments from you guys tho - that its just not really suited for how android works on a phone....
Click to expand...
Click to collapse
Read last 5 pages in hardcore kernel topic.

knowing one and the other about linux, I have to disagree with those who say: it's gonna make your phone slower..
why? in linux, things constantly run in the background. and what this patch does, is give priority to foreground processes. True, there isn't MUCH in the background, so results may not be super, but the compile with 64 threads is just AN EXAMPLE of what it can do. That's the PERFECT situation to demonstrate. This doesn't mean that it sucks for everything else! It just means that it works
So stop *****ing and just test it before you start yapping that it's bad, doesn't work on phones etc... There is no right and wrong here, there is just: test it and see if it works!
i'd like to have a REAL technical discussion with these people here that are so-called experts... Because their arguments (excusez-le-mot) SUCK.
so please adapt your first post, because what they are saying is just guessing and not based on experiments nor experience, which renders it completely useless
Just my 2 cents

dupel said:
Already discussed - its useless on phone. Phone will be even slower.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
discussion is worthless, you can't convince me with some "maybe this, possibly that", if you say it's useless: give hard numbers or (sorry, but...) stfu!

UPDATE:
i've been reading up on the lkml and i think there are some very interesting possibilities here...
What this program does, is put the tty-bound processes in a special cgroup. While this is done automatically, there is also a possibility to just do the same in userspace. (check Lennart from redhat's solution).
It basicly creates a different cgroup for foreground processes, he does it in the bash profile. But i think that with this in mind, we can create cgroup handler for our "most important" apps to make them more responsive!
I've been looking into hardcore's kernel and it already has cgroup support built in, so it's actually just a matter of using it properly
how? check lennart's comments further in the lkml thread because you have to look out to clean up cgroups when no more processes use it.
Anyway, when properly tuned, it should be even better than the kernel patch people talked about!

These type of changes would suit more underpowered devices like the Hero or G1 but imho I dont know why the galaxy S needs it, my IO after applying OCLF is 2300+ apps, any lag issues are not due to the current modded kernels available as they are really good..

Idk why people don't understand simple things
cgroups does not magically makes your apps more responsive. It makes groups of processes which are scheduled together at the same level instead of doing it per process.
So, the group of "make" processes during a make -j64 get all globally a lower share of resources (than if they weren't grouped), allowing the group "browser" process to get enough resources to be smooth.
Without, each make process (64 of them) would get an equal resource time, which would also be equal to the browser, which ends up not being very nice for the desktop.
Now on the phone.. do you have a make -j64 running [IN THE BACKGROUND]? nope. do you have an heavy process or group of processes running [IN THE BACKGROUND]? nope.
Your front task is always the one taking most resources. If you put it in a group you might even decrease it's performance and responsiveness.
It's a double edged sword. You see, when they schedule the make -j64 process group, your browser is smooth but the make -j 64 process group is *slower*.
So unless a group of processes on the phone are taking too much cpu (i know of none doing that unless they're on the foreground), it's useless

bilboa1 said:
Idk why people don't understand simple things
cgroups does not magically makes your apps more responsive. It makes groups of processes which are scheduled together at the same level instead of doing it per process.
So, the group of "make" processes during a make -j64 get all globally a lower share of resources (than if they weren't grouped), allowing the group "browser" process to get enough resources to be smooth.
Without, each make process (64 of them) would get an equal resource time, which would also be equal to the browser, which ends up not being very nice for the desktop.
Now on the phone.. do you have a make -j64 running [IN THE BACKGROUND]? nope. do you have an heavy process or group of processes running [IN THE BACKGROUND]? nope.
Your front task is always the one taking most resources. If you put it in a group you might even decrease it's performance and responsiveness.
It's a double edged sword. You see, when they schedule the make -j64 process group, your browser is smooth but the make -j 64 process group is *slower*.
So unless a group of processes on the phone are taking too much cpu (i know of none doing that unless they're on the foreground), it's useless
Click to expand...
Click to collapse
very true... that's why it still might be possible to group "your current task" and "all the rest". That (might) give you an advantage still...
and as said: i'm not saying it IS better, i'm saying it might be worth testing
hence the suggestion i put in post 11: make something that puts the application you start in foreground in a dedicated group and EVERYTHING else in another. When you background that process, move it to the "pool" group
it might just help!! (so... don't shoot the idea too soon )

Android accelerator - A Magic runs same speed than a Nexus

Hi all,
Very impressed after watching this video on the Cyanogen Mod :
Demo video : http://forum.cyanogenmod.com/topic/...aster-flexycore-thanks-cyanogenmod-community/
I m pleased to share it with you and would like to know what you're thinking about this "droidBooster" which make an old HTC running at the same speed than a Nexus One! :

Whats the point of this?
What does a video of a video player proove? Wouldn't some real time benchmarks like linpack or quadrant be more proof.
Still why didnt they have 2 Nexus One's and show how much faster the one with droidbooster got.
All these booster softwares sound abit like all the BS booster softwares for windows.
sceptical...

Hmm I suspect that they are overclocking because they didnt mention anything about clock speed but lets hope that its legit
Edit: they have an apk in the market
Sent from my Nexus One using Tapatalk

Imperial.mack said:
Hmm I suspect that they are overclocking because they didnt mention anything about clock speed but lets hope that its legit
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
I hardly think they are overclocking becose that would make the software only runnable on rooted devices. Which would remove a huge part of their possible market share.
And overclocking with that much improvement in performance? Youd have to double the clock rates. Which on nearly all devices is damn close to impossible. Except for Desire-Z for example.
Unless they somehow are without Root overclocking it or changing the kernel to their own super optimized i dont really see how this is done.

nd the nexus one can fly beyond their limits?

They posted this video showing how it works basically:
http://www.youtube.com/watch?v=tEAz9fRoDmA

Their software modifies the Dalvik code, which means that you do not only need to be root, but you also can't install this software without modifying your ROM.

From the web page http://www.flexycore.com/droidbooster-overview.html
"DroidBooster technology enables to compile any Android Java code in optimized native binary when generating the ROM, taking full power of the underlying CPU for high performance and low power execution."
This is not overclocking, but maybe be a paid app (and very expensive app)
Sorry 4 my poor english

It's actually more like Jit.
See this video for further explications : http://www.youtube.com/watch?v=tEAz9fRoDmA
Lol ok took me so much time to answer that already 4 ppl posted !!

After looking at the company website who developed DroidBooster, I discover an other Video with a principle presentation of droidbooster.
"DroidBooster relies on compiling and executing any embedded Java Code of an Android system as binary." according to the video available here:
ww.youtube.com/watch?v=tEAz9fRoDmA[/url]

this thing is kinda bs imo. And the guy's voice is just gay

LoL
I hope to come out soon

If this thing really does what the company claims, then Google will probably buy the code from them. Also limiting this software to rooted phones means it wouldn't make a ton of cash, and then expecting them to cook and sign their own ROMs is a weird business model. In other words, it's meant for developers only, so we kinda have to wait for official incorporation.

exciting! hope they support the nexus ..

DDM123 said:
If this thing really does what the company claims, then Google will probably buy the code from them.
Click to expand...
Click to collapse
No, I doubt this code is worth anything to google. All they say they are doing it converting the dalvic code into native code. If google wanted to do that they could very easily, the JIT they included with Froyo already does do it to some extent.

I won't believe this for a second. I have both the N1 and Magic, and I can safely say the N1 is MUCH faster. It should be a no-brainer, just look at the specs. The Magic was what -- the second Android ever!? They were bound to improve, and the N1 set the bar high a year ago. Now look at the plethora of fast devices we have, and the N1 can be thanked for that. I once read that one of the reasons Google launched the Nexus was to jump-start the "super" smart phone market, because manufacturers weren't pushing the bar far enough in their devices. N1 set a standard for the rest of them. The way I see it, the Magic was nothing more than an early experiment.
And I never had an issue playing videos on my Magic anyway. What proof is that? The N1 is definitely more responsive, boots 10x faster, never runs out of memory. The Magic pretty much requires an app killer; never needed one on the Nexus. I can go on and on, but I think I made my point.

Bloodflame said:
I won't believe this for a second. I have both the N1 and Magic, and I can safely say the N1 is MUCH faster. It should be a no-brainer, just look at the specs. The Magic was what -- the second Android ever!? They were bound to improve, and the N1 set the bar high a year ago. Now look at the plethora of fast devices we have, and the N1 can be thanked for that. I once read that one of the reasons Google launched the Nexus was to jump-start the "super" smart phone market, because manufacturers weren't pushing the bar far enough in their devices. N1 set a standard for the rest of them. The way I see it, the Magic was nothing more than an early experiment.
And I never had an issue playing videos on my Magic anyway. What proof is that? The N1 is definitely more responsive, boots 10x faster, never runs out of memory. The Magic pretty much requires an app killer; never needed one on the Nexus. I can go on and on, but I think I made my point.
Click to expand...
Click to collapse
Not really. The point is that this guy is claiming to make java code run in native binary, thus ensuring that the CPU isn't doing unnecessary work to interpret and run java code. If possible (who's to say) then it would make a Magic run much faster than it does. It might even be feasible to suggest that it would run as fast as a stock Nexus.
Think about it this way, why is it that the original iPhone UI is so smooth? The code is optimized and run as a native binary, not some VM that has to be compiled and run by the CPU every time it wants it. Native code would make the Magic much faster.
The whole point is moot though, because this isn't something that you will see bundled into an .apk anytime soon. It might be novel code that Google picks up on and uses in later OS revisions though. Who knows.
sassafras

As i understand it will cost a high memory consumption, where 512mb of ram will be not enought for it (Actually its already not enough on miui rom with Dalvik VM, on nexus1 i have only 130mb free). And high power drain.
Welcome back to Windows Mobile
Btw i dont believe it, they just want to make some money with air bubbles

Tim4 said:
As i understand it will cost a high memory consumption, where 512mb of ram will be not enought for it (Actually its already not enough on miui rom with Dalvik VM, on nexus1 i have only 130mb free). And high power drain.
Welcome back to Windows Mobile
Btw i dont believe it, they just want to make some money with air bubbles
Click to expand...
Click to collapse
"Only" 130MB free? It's 130MB that isn't ever used by the system, making it wasted 130MB, and you're referring to it as "only"?
This point was discussed zillions of times in Autokiller Minfree and "Don't need task killers" threads. Android has efficient memory management, Nexus having it VERY efficient since Froyo, much more efficient than really needed. It never uses its 400MB of user memory or even close to it.
Funny, how marketing affects people. They want more of the things they don't need.

Jack_R1 said:
"Only" 130MB free? It's 130MB that isn't ever used by the system, making it wasted 130MB, and you're referring to it as "only"?
This point was discussed zillions of times in Autokiller Minfree and "Don't need task killers" threads. Android has efficient memory management, Nexus having it VERY efficient since Froyo, much more efficient than really needed. It never uses its 400MB of user memory or even close to it.
Funny, how marketing affects people. They want more of the things they don't need.
Click to expand...
Click to collapse
Yeah, i call it "the only free memory."
Take a look:
You have 130mb left.
1)browser eats 65mb of ram. 65mb left
2)+some other apps that running at background/service.
So what i have in result?
My apps often be killed by android because out of memory.
The most anoying thing is when im surfing, writing some stuff on forums i get my browser killed with data lost. Its rare but still hapens.
Another real example: Dungeon Defenders. When i play it, i got almost all my apps be kicked from memory.
P.s. I know about wipe. Just moved to latest 1.1.14miui, have wiped everything 3 times.
P.s.2 ofcource it depends on how many apps you have and which rom you use. No problems with ram on stock android but i just dont like it, so...

Anyone got any comparison screenshots between stock camera and Jishnu's Camera MOD?

I'd like to see everyone's sample shots that installed Jishnu's Camera MOD. Thanks!

I had them. But deleted already. I am not a fan of super proffesional photos, but i was able to see the difference.
Just try it yourselg. Image size is bigger anyway when you use his MOD. This is already a good reason to change camera apk and libs.
And this is not a Q&A tread. Please post your questions in right thread.

I see a lot of talk about bigger, but I'm thinking bigger ≠ better, or else LG's engineers would have set compression differently. Something in the tune of 2% subjective improvement with a 80% increase of file size isn't worth it either.
I'd also like to see some comparison shots, the thread is just too messy to get anything meaningful out of it in terms of quality experience, it's just "does it work / please test this / omg my phone is bricked".

Incep said:
I see a lot of talk about bigger, but I'm thinking bigger ≠ better, or else LG's engineers would have set compression differently. Something in the tune of 2% subjective improvement with a 80% increase of file size isn't worth it either.
I'd also like to see some comparison shots, the thread is just too messy to get anything meaningful out of it in terms of quality experience, it's just "does it work / please test this / omg my phone is bricked".
Click to expand...
Click to collapse
Why not?Its not like the photos are 100mb each.Anything that will improove the quality of the photos,even the slightest,is welcome.Aside of that,the files arent that big either,maybe some kbs more and very rare to go further than 1mb...

Incep said:
I see a lot of talk about bigger, but I'm thinking bigger ≠ better, or else LG's engineers would have set compression differently. Something in the tune of 2% subjective improvement with a 80% increase of file size isn't worth it either.
I'd also like to see some comparison shots, the thread is just too messy to get anything meaningful out of it in terms of quality experience, it's just "does it work / please test this / omg my phone is bricked".
Click to expand...
Click to collapse
I wonder you work for LG??

byhoung said:
I'd like to see everyone's sample shots that installed Jishnu's Camera MOD. Thanks!
Click to expand...
Click to collapse
I tried The EXTV3 version and returned back to the stock camera. Too noise in photos on my opinion. Many people like the mod so i think i will try again the updated version and post shots soon.

Thanks for sharing. I think many people are on the edge of trying it out but are not sure whether it objectively improves camera quality. I would be beneficial for OP as well since he will gain more downloads and potentially gain more donations. It's a win-win.
Camera MOD users, if you want to help out, you can spread the word by posting comparison shots.

Hey brother listen! Just use the stock cam and then flash this! You will see the difference.. and why are you concerned about donations? Did i beg you for that? This kinda man pisses everyone off frankly speaking..
It doesnt matter whether you get a good pic or not.. why dont you understand, this thread is not a part of my universe.. I dont have to deal with 14Fps video, you have to.. got it?
Sent from my LG-P880 using XDA Premium 4 mobile app

Jishnu Sur™ said:
Hey brother listen! Just use the stock cam and then flash this! You will see the difference.. and why are you concerned about donations? Did i beg you for that? This kinda man pisses everyone off frankly speaking..
It doesnt matter whether you get a good pic or not.. why dont you understand, this thread is not a part of my universe.. I dont have to deal with 14Fps video, you have to.. got it?
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm confused why you're offended.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Lets not cause offence to anyone here. Try them both out yourself and make up your own mind weather it makes a difference or not.
Thread closed

Super Touch , smooth scrolling. Need help dissecting it.

There is this app called Super Touch that phone arena covered. Supposed to smoothen the touch experience on android by a significant margin. The developer offers no explanation as to how the app works. I've yet to test it because it is building something right now and it takes a long while to finish. From what i can make out , i think it builds some sort of scrolling cache and offloads them to GPU ? I don't know the internal android structure that well and analyzing the source if there is one , is beyond me. If there is a developer that can explain the intricate workings of this app to people , so people could stop comparing this to "snake oil" if it's legit , if it's not we can ask google to remove it from google play , that'd be great. Thanks.
The link to the article ;
http://www.phonearena.com/news/Spot...d-up-your-sluggish-Android-smartphone_id75851
I don't know if it is against forum rules to post links to articles , if it is please warn me and i will remove the link.

boltthrower56 said:
I don't know the internal android structure that well and analyzing the source if there is one , is beyond me. If there is a developer that can explain the intricate workings of this app to people , so people could stop comparing this to "snake oil" if it's legit , if it's not we can ask google to remove it from google play , that'd be great. Thanks.
Click to expand...
Click to collapse
Why is this such a great deal?
Pros
* It seems to work
* It passed google's requirements and malware checks
* Does not need root
Cons
* Closed source
Just because we (you) can't comprehend how it works, is not a reason to question its viability.
Keeping it closed source and not revealing its workings is just a way to prevent competition and/or code copying.
There are lots of fake apps that pretend to be doing something you should be more worried about.
I wouldn't really worry about this one, but if you don't trust it, don't use it.
To answer your question; I would say its either one of these
* Animation caching
* Reducing element-sizes, and thus stretching it to save system resources (since the app needs to know you screen resolution)
* System optimizations for animations (Altho these things usually require root)
On a side note, since you are posting this on the Nexus 4 forums, I assume you own/use one. The article you linked clearly says older devices benefit more from this app, since newer/better devices already handle things pretty smoothly. This means that the result of this app on a Nexus 4 may be unnoticeable. Could it be that you question this app because you don't see any result?

MerynGoesAndroid said:
Why is this such a great deal?
Pros
* It seems to work
* It passed google's requirements and malware checks
* Does not need root
Cons
* Closed source
Just because we (you) can't comprehend how it works, is not a reason to question its viability.
Keeping it closed source and not revealing its workings is just a way to prevent competition and/or code copying.
There are lots of fake apps that pretend to be doing something you should be more worried about.
I wouldn't really worry about this one, but if you don't trust it, don't use it.
To answer your question; I would say its either one of these
* Animation caching
* Reducing element-sizes, and thus stretching it to save system resources (since the app needs to know you screen resolution)
* System optimizations for animations (Altho these things usually require root)
On a side note, since you are posting this on the Nexus 4 forums, I assume you own/use one. The article you linked clearly says older devices benefit more from this app, since newer/better devices already handle things pretty smoothly. This means that the result of this app on a Nexus 4 may be unnoticeable. Could it be that you question this app because you don't see any result?
Click to expand...
Click to collapse
No , it could not be because i had not tested the app when i wrote that. (Had you bothered to read , you'd know.) We question everything on this forum , that's how we learn. I did not assume that it was "fake" by the way , if that's why you're hostile (and arrogant). People on other forums compared this to "snake oil". I wanted to share the app with friends so it could grow. That's why i wanted to make out how it works. I can't share this app before knowing that it's not "snake oil".
When i said i'm not "that" affiliated with Android ecosystem , i didn't mean i'm illiterate btw.
Anyway , i could already make those out from the description of the app (Yes , i too read it ). I wanted more of a technical answer but thank you , nevertheless...
On a side note , In a help thread please just answer the question if you can , skip the lectures people didn't ask for. I asked "available devs" to explain the intricate workings of an app so as to clear the air , not only did you not provide that but you tried to give me a lesson on morality. Please refrain from doing that. And please do not write a lengthy and angry reply to this. I'm just not interested in arguing with you.

boltthrower56 said:
I don't know the internal android structure that well and analyzing the source if there is one , is beyond me.
Click to expand...
Click to collapse
Made me think you were new to Android development and coding in general. Normally people like this with these questions do not want/need a specific and technical answer which is why I told you to not worry about it.
I don't know if it is against forum rules to post links to articles , if it is please warn me and i will remove the link.
Click to expand...
Click to collapse
Again, made me think you were new here.
if it's not we can ask google to remove it from google play , that'd be great.
Click to expand...
Click to collapse
This sounded to me as if you just wanted it to be removed.
My post was not intended to sound the way you describe it, and reading it again I wonder how you came to the conclusion I was 'teaching you a lesson'. Just because I did not overflood my post with happy smileys and kind words does not mean I'm hostile and/or trying to be arrogant.
To me, your post sounds the exact same was as how you described mine.
That aside, here are my technical thoughs.
The app stores quite a lot of data on your phone, close to 7MByte on my phone, to an app-size of 2,86MByte, so I assume it makes use of some kind of caching.
It probably uses some other techniques for different element optimizations, meaning not all improvements are via caching.
My guess is it takes the animations it knows, and "replays" them, capturing the animation and storing it in its data for quick access. When you start the app and set it up, it needs time and says "building fast event for x action", which is why I think it works this way.
From the app:
When using the same smooth level, the better the GPU performance is, the smoother the operation wil be. If the GPU performance is not up to the demand, it may cause frame loss when sliding screen. Higher level may take longer time to start, a better CPU may take less time.
Click to expand...
Click to collapse
The animation is probably "scaled" down in size, which makes it less computing-heavy. This also explains why the higher the setting, the longer it takes. (more compression = more computing power needed. Since a better CPU can do more instructions per second, it will be faster at rendering its own "database" of the animations, which is logical.
Not sure what the author meant with "better the GPU performance is, the smoother the operation will be". Operation could either refer to the process Super Touch does, or the process of animating the animation when using the phone. Personally I think this refers to using the GPU for rendering animations normally (without Super Touch), which can cause frame drops as he explains. GPU's with lower performance will have a harder time rendering an animation than a GPU with high preformance. Pre-rendering takes this load off of the GPU, making it more "smooth" in real performance.
With this method its can just 'grab' an animation from its memory and 'play' it instead of calculating it on-the-fly.
Looking at the permissions the apps needs, the app uses "draw over other apps". This is probably used to "show" the animations it stored instead of the animations of the app that is being used. How it is actually able to replace this animation is something Im not sure of.
The app has permission to run at startup, this is probably needed to "load" the core service that does this replacement.
I do not exactly know why it needs permission to read phone status & identity and change audio settings, but my guess would be that it is related to the power saving mode.
The developer offers no explanation as to how the app works.
Click to expand...
Click to collapse
Unless he does, we can probably only assume how his app works. Decompiling the app and looking at the source might give you an answer, but this is not something I can help you with, mainly because my last decompiling experience is 3 or 4 years back.

Using it for 2 days. And I have to admit that it works, really well, without harming battery, which is a amazing win-win solution.
I asked on the Google play store and get the answer from the developer: the app offload the working process from the CPU to the GPU, hence everything gets much smoother and the performance level depends on your device's GPU.

After optimization, sliding is very smooth.

SNAPPATCH XZ Premium - Device specific Feedback, Discussion, Troubleshooting

This is the official Feedback/Troubleshooting Thread for the Xperia XZ Premium. Feel free to discuss about the Patch, and to ask for Help if You face Problems or Bugs on Your Device. Stay friendly, be respectful and keep the XDA Rules in Mind!
Main Thread - LINK

Not a bug or anything, just letting people know that the first boot will take a while. Don't worry if it sits at the pixel boot animation for longer than a few minutes.

hello, it's for an opinion, I'm with Carbon ROm and SNAPPATCH, I have a concern:
* 1) with the autofocus of Open Camera .... autofocus has trouble with close subjects, I tried all focus modes but it's still the same, typed 15 times its screen to have a correct focus, my photos always come out with just a little blurry (and with luck no ...)
2) when taking the picture, the clarity of the screen is still there but to view the picture the intensity of the screen drops a little bit and does not give the effect of having taken the same picture, it's normal ?
So, thank you for a nice answer and good work on SNAPPATCH

blweldon2 said:
Not a bug or anything, just letting people know that the first boot will take a while. Don't worry if it sits at the pixel boot animation for longer than a few minutes.
Click to expand...
Click to collapse
That's helpful, thanks for Your Feedback! Hope You enjoy the Patch
CRYX said:
hello, it's for an opinion, I'm with Carbon ROm and SNAPPATCH, I have a concern:
* 1) with the autofocus of Open Camera .... autofocus has trouble with close subjects, I tried all focus modes but it's still the same, typed 15 times its screen to have a correct focus, my photos always come out with just a little blurry (and with luck no ...)
2) when taking the picture, the clarity of the screen is still there but to view the picture the intensity of the screen drops a little bit and does not give the effect of having taken the same picture, it's normal ?
So, thank you for a nice answer and good work on SNAPPATCH
Click to expand...
Click to collapse
Thanks for You constructive Post! There are a lot of Configs and i'm not even aware of what the best Values would be. Means a lot of testing and finetuning for the next Time. At all is it already a good upgrade but i can confirm that there is still a lot to do and to figure out how what works and which Configs are the best. I'm also looking around to get HDR Video Recording and i already made some Steps in the right Direction like it seem. I'll keep You informed on the Main Thread and the Changelogs when something changes or improves! Hope You can live for now with the Camera...
BR

When trying to install Substratum, its getting half way done building the overlays, seems stuck. Any ideas?
BTW Im hitting the 8.1 and build & enable
Also what a good app to use to change those kernel numbers

Tested it: performance is much slower than stock. Geekbench shows 60% less performance.
Wifi is stronger.
No X-reality.
Safe charging doesn't exist.
Camera is very good, but the focus is off, cannot take pictures of nearby objects.
Back to stock for me

amakuramio said:
Tested it: performance is much slower than stock. Geekbench shows 60% less performance.
Wifi is stronger.
No X-reality.
Safe charging doesn't exist.
Camera is very good, but the focus is off, cannot take pictures of nearby objects.
Back to stock for me
Click to expand...
Click to collapse
You don't even tried the Real World Performance such as Task switching or Gaming Performance? X-Reality? Sounds not like testing for Me...
And what is Safe Charging? It does Quick Charge (3.0) as Safe as Possible. Otherwise would it just start heat up or totally stops the charging since there is a Controller for such Things.... Besides that seems the Device to stay a lot Cooler while Charging (Booted in Android).
Don't get Me wrong. But Posts like this are the Stone on the Development Grave here. It just tells People that something is sh**, and they don't even think about to try it out. Half of the Posts i see on the Xperia Forums are non Sense, complaining, or feature request. That's isn't helpful to anyone and just keeps Devs from joining the Development here. See the TWRP Thread from Myself5 or the Kernel Thread from AndroPlus (Both long Time Contributers). It's a wonder that Myself5 is still providing his Carbon Builds on the Forums....
To be honest, besides the ROM from Myself5 and My Patch is there nothing great to find for the XZ Premium. If You can't believe that go back to Nougat or use this trashy ROM from Turbo which contains non working "Tweaks" and seems to be 90% based on Superrs Kitchen without additional Optimizations (My 5 Years old Brother can do that). Just removed some Content and Copy - pasted a Kernel with the DRM Fix. It's sad...
And before i start to talk more about the Problems here am i out for now. New Patch is up and i'm looking forward to more Enhancements which You will NEVER get on Stock!
BR

Miustone said:
You don't even tried the Real World Performance such as Task switching or Gaming Performance? X-Reality? Sounds not like testing for Me...
And what is Safe Charging? It does Quick Charge (3.0) as Safe as Possible. Otherwise would it just start heat up or totally stops the charging since there is a Controller for such Things.... Besides that seems the Device to stay a lot Cooler while Charging (Booted in Android).
Don't get Me wrong. But Posts like this are the Stone on the Development Grave here. It just tells People that something is sh**, and they don't even think about to try it out. Half of the Posts i see on the Xperia Forums are non Sense, complaining, or feature request. That's isn't helpful to anyone and just keeps Devs from joining the Development here. See the TWRP Thread from Myself5 or the Kernel Thread from AndroPlus (Both long Time Contributers). It's a wonder that Myself5 is still providing his Carbon Builds on the Forums....
To be honest, besides the ROM from Myself5 and My Patch is there nothing great to find for the XZ Premium. If You can't believe that go back to Nougat or use this trashy ROM from Turbo which contains non working "Tweaks" and seems to be 90% based on Superrs Kitchen without additional Optimizations (My 5 Years old Brother can do that). Just removed some Content and Copy - pasted a Kernel with the DRM Fix. It's sad...
And before i start to talk more about the Problems here am i out for now. New Patch is up and i'm looking forward to more Enhancements which You will NEVER get on Stock!
BR
Click to expand...
Click to collapse
hi Miustone...... i know how you feel...... if i would get upset with all reports like that, i would be 10 years older..... get use to this.... here in xda, this is normal.....
he did his best.... some people are good reporting issues, some others don’t.... you need to get the positive and re-evaluate the negative ones..... just don’t take it personal...... i know, some times we are not in the mood.... i know.... but i learned a lot, from forums like these..... believe me, i've been in all....
you did an impressive job coding all these scripts.... i saw them all...... this tell me a lot from you...... not everyone can see them.... users, just use them....... and they don’t know the effort it takes, to get there....
just enjoy your passion, coding and developing..... my respect.....
TURBO

TURBO2012 said:
hi Miustone...... i know how you feel...... if i would get upset with all reports like that, i would be 10 years older..... get use to this.... here in xda, this is normal.....
he did his best.... some people are good reporting issues, some others don’t.... you need to get the positive and re-evaluate the negative ones..... just don’t take it personal...... i know, some times we are not in the mood.... i know.... but i learned a lot, from forums like these..... believe me, i've been in all....
you did an impressive job coding all these scripts.... i saw them all...... this tell me a lot from you...... not everyone can see them.... users, just use them....... and they don’t know the effort it takes, to get there....
just enjoy your passion, coding and developing..... my respect.....
TURBO
Click to expand...
Click to collapse
Thanks for You nice Words Mate! I really take My at off to You for Your calmness! I'm 24 now and around 6 Years posting on XDA. I still can't accept that XDA has changed over the Years, and i think that's My Problem. It's not the Users Fault, XDA just mutated to another Place and no one can change that except for the Owners of this Site. And i don't see that coming. XDA is still under Construction since Years (DEV DB, Thread Features, Site Designs, Post Editing), and there is no End...
I looked often around for other Places to share My Work, but looks like i have to live with that here... At least do i know that here are still some Friendly Devs and Users, and that's what keeps Me here at the End. So Thanks again for Your Post! And keep You also up Your ROMs! It would be really Silent in our Forums without You...
BR

After days of using,here's my simple feedback.
(G8142,lastest official CarbomROM)
1.Battery life is as good as,if not better than that of stock.
2.When slipping the screen,it lags.(compared to stock)
But i believe it is the rom to be blame.
3.Actually game performance is not good,for example,Fate/Grand Order and HearthStone,the animation of which lags.
4.The Pixel-like UI is cool! i love it.
keep developing,and i will stay on AOSP

SuzutsukiKaede said:
After days of using,here's my simple feedback.
(G8142,lastest official CarbomROM)
1.Battery life is as good as,if not better than that of stock.
2.When slipping the screen,it lags.(compared to stock)
But i believe it is the rom to be blame.
3.Actually game performance is not good,for example,Fate/Grand Order and HearthStone,the animation of which lags.
4.The Pixel-like UI is cool! i love it.
keep developing,and i will stay on AOSP
Click to expand...
Click to collapse
Thanks for Your Feedback!
I can't tell if the Patch is causing it or not, but it runs just well on My Axon 7 using AOSP Extended. Same for Gaming or Multitasking. Graphic intensive Games are running more fluid and with less heat, and the App switching is much faster. But i see the Lags all few Seconds on the XZP. Are You also using the Carbon ROM?
Think i will try out pure AOSP after some sleeping...
And yes, i will continue the Development! There is much left to do, and i think a own AOSP OS from Me including many of the Patch Features will also come in the next Time (AOSP Project for Xperia Devices). At least at this Point should be all Lags be part of the past...
Hope to see You around again! BR

Try change g google play services and the lag will go.

Miustone said:
Thanks for Your Feedback!
I can't tell if the Patch is causing it or not, but it runs just well on My Axon 7 using AOSP Extended. Same for Gaming or Multitasking. Graphic intensive Games are running more fluid and with less heat, and the App switching is much faster. But i see the Lags all few Seconds on the XZP. Are You also using the Carbon ROM?
Think i will try out pure AOSP after some sleeping...
And yes, i will continue the Development! There is much left to do, and i think a own AOSP OS from Me including many of the Patch Features will also come in the next Time (AOSP Project for Xperia Devices). At least at this Point should be all Lags be part of the past...
Hope to see You around again! BR
Click to expand...
Click to collapse
hey, i have tried the latest AOSP by SonyAOSP team,and now i am on it.
It is smoother than stock,without any lag.
however i could not boot into recovery,which makes me unable to flash the latest Snappatch.
i think we are getting closer to it...

Inerent said:
Try change g google play services and the lag will go.
Click to expand...
Click to collapse
I'm on the Beta right now and all seems to be fine with the latest Patch Version. Hope You can also enjoy it now!
SuzutsukiKaede said:
hey, i have tried the latest AOSP by SonyAOSP team,and now i am on it.
It is smoother than stock,without any lag.
however i could not boot into recovery,which makes me unable to flash the latest Snappatch.
i think we are getting closer to it...
Click to expand...
Click to collapse
Great to hear so far, but what's the Problem with Your Recovery? Mine works fine here...
Have You tried flashing the last One from TWRP.me with Fastboot? The Patch should not affect it in any way. So it's a really strange Issue... ?

Miustone said:
I'm on the Beta right now and all seems to be fine with the latest Patch Version. Hope You can also enjoy it now!
Great to hear so far, but what's the Problem with Your Recovery? Mine works fine here...
Have You tried flashing the last One from TWRP.me with Fastboot? The Patch should not affect it in any way. So it's a really strange Issue... ?
Click to expand...
Click to collapse
i have tried 3.2.1-0 and 3.1.1-0,but both couldn't function normally.
it just slashes and reboots.

SuzutsukiKaede said:
i have tried 3.2.1-0 and 3.1.1-0,but both couldn't function normally.
it just slashes and reboots.
Click to expand...
Click to collapse
Yes indeed, with yesterday compiled Sony AOSP TWRP is broken.
With the whole source from the end of March all was fine. But I got weird errors with this patch which rendered the phone unusable at all.
Sadly I have no clue how to debug a recovery. TWRP only worked before first boot.

Thread closed rule 5