Related
Hi guys..
I sad Google developed 2.2 to improve snapdragon cpu and becuase of that the benchmarks shows 3X faster cpu on nexus,
will work 2.2 on galaxy like nexus ? or not for SGS cpu!
at all what you think about power of CPU/GPU in SGS on 2.2 ?
Is nexus cpu better than galaxy on Android 2.2 ?
The Galaxy's CPU/GPU is the best on the market right now and with 2.2 it should fix a lot of software problems with the SGS.
Actually can't wait for 2.2, and it's released around about my birthday!
When is your birthday
22nd September mate. You can buy me a Galaxy S as a spare if you want
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
matty___ said:
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
Click to expand...
Click to collapse
If it has rfs file format and TouchWiz, consider it ****ed up.
kgk888 said:
If it has rfs file format and TouchWiz, consider it ****ed up.
Click to expand...
Click to collapse
If froyo on the SGS sucks, then the chefs in here will cut it open and make it run properly and it won't matter what the FW was like when samsung sent it out. Also, TouchWiz is fine, even if it does have a dumb name.
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
shep211 said:
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
From what I've seen and read, the 2.2 builds for the Galaxy S do NOT have a JIT compiler enabled which explains the lower scores. The N1 got the huge CPU boost from having JIT enabled. That doesn't explain the Droid X's scores, but then again I haven't read enough about 2.2 running on the DX to see if it has JIT installed.
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Vogie said:
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Click to expand...
Click to collapse
I would wait at this time before purchasing an SGS if that's your concern.
Out of the box, the current phone/software is laggy and disappointing. If you're willing to hack it with some of the various fixes found here (I prefer samset with mimocan kernel), then you won't be unhappy with the phone, but there's no guarantee that Samsung will get FroYo right, and that if they do get it wrong that the devs here will be able to bring you a hot, non-laggy, super FroYo ROM before there's better, or at least comparable hardware done right by the manufacturer available.
That's no reflection on the devs here at all, I'm just thinking that Samsung won't release the firmware until the end of September, the devs will need a couple of weeks to make magic at least, and so now we're well into October. By October, the SGS will be a six month old phone. Six months is a very long time in the Android hardware world, and we'll likely see a landslide of new phones with faster CPU, maybe even dual-cores in the fall for the holiday season. The only thing the SGS will have over other phones at that point is the Super AMOLED screen by Samsung, since they're holding it all to themselves. I wouldn't be surprised if Moto or HTC try to kang the iPhone display tech for newer models if they can't get Super AMOLED for themselves.
In the android world it is nearly impossible to but a device that won't be out of date within at most a year and sometimes within 6 months.
Having said that, I don't see anything that will topple the sgs quite that soon. Although there is talk of dual core snap dragons, there has been nothing announced yet, and indeed the two new Desire handsets are still on the same chip.
I wouldn't expect to see anything that will have more raw power than the sgs until at least mid 2011. If there was anything closer than that it'd already be getting hyped.
If you keep looking at what is just over the horizon then you won't end up ever getting one, because there always seems to be something new out in a few months time. The sgs isn't prefect, but it beats the hell it of most anything that you'll be able to buy this year.
My humble opinion of course, but I think that if you want top end hardware, the sgs will serve you very well.
Sent from my GT-I9000 using XDA App
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
shep211 said:
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
The hummingbird core is widely recognized to be faster than the snapdragon core. Benchmarks do not tell you everything. Reference:
You might think that the Hummingbird doesn’t stand a chance against Qualcomm’s custom-built monster, but Samsung isn’t prepared to throw in the towel. In response to Snapdragon, they hired Intrinsity, a semiconductor company specializing in tweaking processor logic design, to customize the Cortex-A8 in the Hummingbird to perform certain binary functions using significantly less instructions than normal. Samsung estimates that 20% of the Hummingbird’s functions are affected, and of those, on average 25-50% less instructions are needed to complete each task. Overall, the processor can perform tasks 5-10% more quickly while handling the same 2 instructions per clock cycle as an unmodified ARM Cortex-A8 processor, and Samsung states it outperforms all other processors on the market (a statement seemingly aimed at Qualcomm).
Click to expand...
Click to collapse
Here is a GPU comparison for some of the leading smartphones:
Motorola Droid: TI OMAP3430 with PowerVR SGX530 = 7-14 million(?) triangles/sec
Nexus One: Qualcomm QSD8x50 with Adreno 200 = 22 million triangles/sec
iPhone 3G S: 600 MHz Cortex-A8 with PowerVR SGX535 = 28 7 million triangles/sec
Samsung Galaxy S: S5PC110 with PowerVR SGX540 = 90 million triangles/sec
Click to expand...
Click to collapse
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
ickyboo said:
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can't really say froyo is over hyped, I mean its free, and beyond that its an incremental upgrade.
I don't see why anyone would be staying on eclair once official froyo drops, and you can't deny that it will bring a performance boost.
Now I doubt it will bring quite as much of a boost as it gave to the N1 until we get a few months of development to really get it running sweetly, but all the same its still not over hyped if I ask me.
With optimized ROMs and whatever fixes we need (cuz samsung WILL break something) I figure the sgs will shred the N1's new scores. I recon we'll see around 3k in quadrant.
Considering how far ahead of almost everything a lag fixed non-stock-rom sgs is now, we'll see something really special once froyo starts rocking our crotches.
Sent from my GT-I9000 using XDA App
The.Opethian said:
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
Click to expand...
Click to collapse
Why powerfull phone? ok i'll tell u:
Because I don't like to buy an expensive phone (like SGS) that power is lesser than a chipper phone (like N1) !
Because I'd rather a phone without stalling (lagging) to play games and running big applications. I will very gray if i'll se lagging/stalling...
Because I need a phone with a good support (it's enough, don't need mazing support). a phone with a clear (alive or nice) Future
JIT for Hummingbird should be promising.
High Mem
anyone got any idea on the high mem issue?... when i was browsing the Gmarket.com, i realize 305 total available memory is not enough for me... and the web page just closed....
I've been reading a lot of discussion on this and would love to hear some opinions and see some benchmarks.
I currently own a Nexus One & where I live they are priced about $150 dollars more for a Nexus than a Galaxy S (It's my understanding Nexus are regarded as cheaper phones in America?) So basically I can sell my 4 month old Nexus One & buy a brand new 16GB Galaxy S for no extra cost. Here is what I am wondering...
I know the Galaxy S has an amazing GPU, it facerolls the Nexus One & even seems to stomp the Droid X with its improved GPU so that is great.
The CPU however seems to under perform in every benchmark I can find versus the Nexus/Droid2 & many more current high end Androids.
I realise these devices are running Android 2.2 with JIT. I've seen Linpacks of 2.2 running Galaxy S devices and JIT enabled ROMs that still don't compare with these other devices.
Question 1
What I'm wondering is the difference we can see in CPU benchmarks going to be surpassed with the addition of a proper 2.2 JIT rom on our devices or is simply that the Snapdragons & other Qualcomm CPU are actually better than our Hummingbird.
Question 2
My Nexus One is Linkpacking 30 MFlops atm, I think with OC etc I can get it higher too. Does anyone have any evidence of a Galaxy S phone (running 2.2, JIT, lagfix or anything) that competes (or even comes close to competing) with this? I have been unable to find anything.
Question 3
Is the current Quadrant scores that I'm seeing people reporting in the Lag Fix threads (2000+) actually representative of speed or are these (as Cyanogen & others seem to be claiming) distorted?
(I realise a lot of people are reporting lag fixed.. what I'm asking is the number represented there (x2 N1 Froyo's score) actually accurate. I don't understand the mechanics behind the I/O benchmark so I don't understand if the lagfix is distoring the reported results from it.)
1. Hummingbird is apparently faster.
2. We don't have JIT yet.. Compare Nexus One 2.1/Eclair with Galaxy S 2.1, and I remember seeing we are faster.. JIT has a massive impact on mflops (because the benchmark uses bytecode, not compiled code).
3. No benchmark is really representative of speeds (no matter what people tell you). Because different apps have different workloads. You might get 50mflops in a CPU test, but for 3D games, the number of triangles matters more. It has recently been shown the I/O test for quadrant can be tricked too.
Benchmarks aren't really comprehensive enough for anything more than getting an idea of the performance.. But don't rely on them.
The reason why we get crappy benchmarks is due to having ****ty filesystem (rfs) which don't let us have multi writes. That's what lag fixes help. Cpu wise we eat snapdragons for breakfast, lunch and tea.
Sent from my GT-I9000 using Tapatalk
andrewluecke said:
1. Hummingbird is apparently faster.
2. We don't have JIT yet.. Compare Nexus One 2.1/Eclair with Galaxy S 2.1, and I remember seeing we are faster.. JIT has a massive impact on mflops (because the benchmark uses bytecode, not compiled code).
3. No benchmark is really representative of speeds (no matter what people tell you). Because different apps have different workloads. You might get 50mflops in a CPU test, but for 3D games, the number of triangles matters more. It has recently been shown the I/O test for quadrant can be tricked too.
Benchmarks aren't really comprehensive enough for anything more than getting an idea of the performance.. But don't rely on them.
Click to expand...
Click to collapse
what he said ^^^
regards
ickyboo said:
The reason why we get crappy benchmarks is due to having ****ty filesystem (rfs) which don't let us have multi writes.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Source please.. I never have actually seen anyone prove this here, but I hear it being thrown around increasingly. How was this proven? I'm becoming increasingly concerned that this conclusion was made by playing chinese whispers
andrewluecke said:
Source please.. I never have actually seen anyone prove this here, but I hear it being thrown around increasingly. How was this proven? I'm becoming increasingly concerned that this conclusion was made by playing chinese whispers
Click to expand...
Click to collapse
Well, if you look at pre-Froyo benchmarks of Snapdragon devices, they generally get around 6.1 in Linpack, vs ~8.4 for a Galaxy S. That's a pretty big delta, and carriers through most other synthetic and real world benchmarks, roughly 20% faster at the same clock speed. Same thing can be seen with the TI processors in the Droid line, at 1Ghz, they score in the 8's with 2.1.
Froyo benchmarks are suspect for a number of reasons, mainly because most of the benchmarks were designed with 1.6-2.1 in mind, and partly because Google spent a lot of time optimizing the base Froyo build for a Snapdragon processor. HTC, Sony, Dell, etc can piggyback off this work with their version, whereas Samsung and Motorola have to start much closer to scratch. Which is also why the HTC devices got Froyo sooner.
Believe it or not (and despite the marketing hype) the Snapdragon chipset is a budget solution, with less complex/expensive memory subsystem, and a far less costly integrated graphics solution than what is found on the Galaxy S.
It's cheap to produce, it has almost everything in a nice tidy package that makes it cheaper to engineer handsets (when I say everything, I mean CPU/GPU/Radio/WiFi/GPS/USB).
It's a pretty good package for companies like HTC, who don't do any real hardware engineering, and try to keep costs low. They do software (very very well, I should add), industrial design, and mass manufacturing, but they've NEVER designed a chipset (or display), they always source those from a third party, in this case Qualcom for the chipset, Samsung/Sony for the displays, etc.
However, they were the first to market with 1Ghz speed and it's a solid and stable hardware setup. Just keep in mind that clock speeds don't tell the whole tale.
The Galaxy S, (and to a lesser extent the Droid series) use a better stand-alone CPU solution and a far superior non-integrated (has its own chip) GPU. Samsung does do their own in-house chipset engineering, and they didn't cut corners on the CPU design, and they learned a lot about how to squeeze a lot of performance out of the ARM instruction set from their own products and the work they did for the iPhone processors. In brute-force, they smack the Snapdragon chipset around like a *****, but they get slapped around in turn by HTC's superior software engineering.
HTC has a real advantage in lots and lots of PDA/Smartphone software experience. They know how to make the most of the hardware they purchase, and seem to spend a great deal of time optimizing the software, be it Windows Mobile or Android, and lessons learned from a decade of making PDAs, under their name and for others.
If HTC used a Hummingbird or TI OMAP chipset with PowerVR GPU, I have no doubt they'd be able to more quickly wring more performance and stability out of it than Samsung or Motorola can.
Croak said:
Well, if you look at pre-Froyo benchmarks of Snapdragon devices, they generally get around 6.1 in Linpack, vs ~8.4 for a Galaxy S. That's a pretty big delta, and carriers through most other synthetic and real world benchmarks, roughly 20% faster at the same clock speed. Same thing can be seen with the TI processors in the Droid line, at 1Ghz, they score in the 8's with 2.1.
Froyo benchmarks are suspect for a number of reasons, mainly because most of the benchmarks were designed with 1.6-2.1 in mind, and partly because Google spent a lot of time optimizing the base Froyo build for a Snapdragon processor. HTC, Sony, Dell, etc can piggyback off this work with their version, whereas Samsung and Motorola have to start much closer to scratch. Which is also why the HTC devices got Froyo sooner.
Believe it or not (and despite the marketing hype) the Snapdragon chipset is a budget solution, with less complex/expensive memory subsystem, and a far less costly integrated graphics solution than what is found on the Galaxy S.
It's cheap to produce, it has almost everything in a nice tidy package that makes it cheaper to engineer handsets (when I say everything, I mean CPU/GPU/Radio/WiFi/GPS/USB).
It's a pretty good package for companies like HTC, who don't do any real hardware engineering, and try to keep costs low. They do software (very very well, I should add), industrial design, and mass manufacturing, but they've NEVER designed a chipset (or display), they always source those from a third party, in this case Qualcom for the chipset, Samsung/Sony for the displays, etc.
However, they were the first to market with 1Ghz speed and it's a solid and stable hardware setup. Just keep in mind that clock speeds don't tell the whole tale.
The Galaxy S, (and to a lesser extent the Droid series) use a better stand-alone CPU solution and a far superior non-integrated (has its own chip) GPU. Samsung does do their own in-house chipset engineering, and they didn't cut corners on the CPU design, and they learned a lot about how to squeeze a lot of performance out of the ARM instruction set from their own products and the work they did for the iPhone processors. In brute-force, they smack the Snapdragon chipset around like a *****, but they get slapped around in turn by HTC's superior software engineering.
HTC has a real advantage in lots and lots of PDA/Smartphone software experience. They know how to make the most of the hardware they purchase, and seem to spend a great deal of time optimizing the software, be it Windows Mobile or Android, and lessons learned from a decade of making PDAs, under their name and for others.
If HTC used a Hummingbird or TI OMAP chipset with PowerVR GPU, I have no doubt they'd be able to more quickly wring more performance and stability out of it than Samsung or Motorola can.
Click to expand...
Click to collapse
Thanks, that was a really insightful post.
So basically even though our processor should outperform or ATLEAST match the snapdragons. Due to the mass optimization of 2.2 JIT for Snapdragon devices it's likely we'll never see the same performance. Unless Samsung gets really keen to do some optimization themselves.
I searched all over the internet to see why the CPU scores in Quadrant and other benchmarks are waaaay lower then the Nexus ones, but still I can't find anything.
Does Samsung disable the JIT in their Froyo ROMs? Because both Snapdragon and Hummingbird are still based on the same Cortex A8 cores
"It's clear that FroYo's JIT compiler currently only delivers significant performance gains for Snapdragon CPUs with the Scorpion core. This in turn explains why, so far, only a beta version of Android 2.2 is available for the Cortex-A8-based Samsung Galaxy S — the JIT compiler is the outstanding feature of FroYo. For the widespread Cortex-A8 cores, used in many high-end Android smartphones, the JIT compiler needs to be optimised. A Cortex-A8 core will still be slower than a Scorpion core at the same clock speed, but the Scorpion's advantage may not be as much 260 percent."
Click to expand...
Click to collapse
http://androidforums.com/samsung-ca...ant-scores-why-humming-bird-doing-so-bad.html
There are multiple reasons, not optimised jit, slow memory for caching and more. Most of them are solved in the CM roms (it performs on par with the N1), and i can tell you that when Gingerbread comes it will blow the snapdragons away.
Which custom ROM provides CPU performance close to Snapdragon?
[ignore this post please]
Still the 1Ghz humming bird out performs the 1Ghz snap in real world performance
Even the LG Optimus One ARM11 600MHz Core scores better than Galaxy S. I still believe it's a software problem.
http://lgoptimusonep500.blogspot.com/2011/01/custom-rom-for-lg-optimus-one-p500.html#more
Another benchmark:
http://www.anandtech.com/show/4126/nokia-http://www.anandtech.com/show/4126/nokia-n8-review-/7
...where the Nexus S proves that the Hummingbird can do more than it currrently does in Galaxy S.
Since Project Butter was announced as groundbreaking for Android devices, it would be good to know what the community thinks about it as the official JB ROMs have launched.
Please provide your input as a casual user and your day-to-day experience, and also as a more techie user or a developer.
The intent is to provide Samsung, if they still lurk on XDA, feedback on how they can improve future development to make Android really smooth, even though the UI is not treated with priority, as it is on iOS.
As far as I am concerned, I didn't notice any difference from ICS to JB on a stock ROM; essentially, Project Butter doesn't exist for my device. The device still stutters where it did on ICS.
4.1.2 JB LSZ Ultimate 5.2 ROM, KSO Modem, Phil's LSZ kernel, Carrier: AT&T (US)
incisivekeith said:
As far as I am concerned, I didn't notice any difference from ICS to JB on a stock ROM; essentially, Project Butter doesn't exist for my device. The device still stutters where it did on ICS.
Click to expand...
Click to collapse
I would agree with your assessment. I think that the stock JB is very stable, however there is no noticeable difference in speed compared with, say, LRQ.
When I press "contacts" or "phone" button, there is still a lag. My understanding of project butter (rightly or wrongly) was that these kind of lags are supposed to be almost eliminated.
Interestingly, when my wife's galaxy S was running slimbean 3.0, it was close to what I expected "project butter" to deliver. However I reverted her SGS back to ICS due to stability issues.
edit- I'm on LM5
edit 2 - Interesting that 90 people have viewed this thread so far, and nobody has disagreed with Incisivekeith's review. Perhaps we can conclude that "project butter" is not included in LSZ or LM5.
To my mind, Project Butter means an entirely GPU accelerated UI. That is what explain this "buttery" feeling when you drag down the notification bar, when you scroll in the browser, etc..
It is certainly activated in our JB roms, because if it was not the case, the rom would be much more laggier, and touch wiz would be the pain it has ever been since the Galaxy S.
However, I'm sure our PB is a far less efficient one than used in the nexii phones. You can easily tell, there are still some lag in the appearance of the notification bar (when opening an app, laoding something..), and the whole feeling is absolutely not like any Apple device (that I despise, of course ).
I have none of the technical skills to give a more detailed answer, but I remain amazed by the fact our devices are not free of any lag, in spite of their double core, big GPU, 1gb RAM etc...
To realize project butter you need a high speed camera. If you running heavily skinned OS has TW you will tend to see some lags. Remember Our note is almost year and half old....
Project Butter and How it Works
Galaxtus said:
To realize project butter you need a high speed camera. If you running heavily skinned OS has TW you will tend to see some lags. Remember Our note is almost year and half old....
Project Butter and How it Works
Click to expand...
Click to collapse
Thanks for the link !
But we don't have the choice, i don't think any android AOSP/AOKP rom includes project butter, am I wrong ? These roms feel more laggy than any touchwiz rom, though they also feel lighter. And it's a shame (I blame samsung) because they are innovative and functionnal.
AW: Is Project Butter effective on the Galaxy Note?
As far as I understand, pb is not an acceleration for the hole system, but an acceleration for gui: no micro-lags in launcher, scrolling in Browser and apps. And it does really better, than ics for me. Just compare xda app on both systems and you'll understand what I mean
Sent from my GT-N7000 using xda app-developers app
crash-petard said:
Thanks for the link !
But we don't have the choice, i don't think any android AOSP/AOKP rom includes project butter, am I wrong ? These roms feel more laggy than any touchwiz rom, though they also feel lighter. And it's a shame (I blame samsung) because they are innovative and functionnal.
Click to expand...
Click to collapse
I tend to disagree on the part which states that these AOSP/AOKP ROMs feel more laggy than TW ROMs. As of today, I run Asylum ROM 25/02 which includes major improvements concerning the overall UI experience. It is snappy and smooth. I do explicitly avoid the term "buttery smooth" as it is misleading.
They are not finished products, that's for sure-but being heavily developed. :thumbup:
Any TW ROM running 4.1.2 won't be "buttery smooth" neither, whereas the leaked 4.2.1 ROM for the S3 already showed improvement and thus where helpful to update the Mali blobs for CM10.1, which are successfully implemented. They do work nicely!
If permitted to ask: when did you last try out an AOSP/CM ROM?
Side note: if you blame Samsung, you're always right! I fully agree.
Galaxtus said:
To realize project butter you need a high speed camera.
Click to expand...
Click to collapse
I'd like to step in here, and this is entirely wrong: Project Butter was not included in jb for viewing in high speed cameras: it was mainly to reduce lag and stutteriness in Android to make the experience amazing for common, general public. Not for professional photographers.
Personally, when my one v is over clocked to 1.5 GHz and above ( and using a jelly bean ROM), the effect is mind blowing. I'd say the device comes near smooth as an iOS device, if not smoother. There are absolutely no lags and waits, and the device performs like a breeze.
Have you ever used a nexus device? That's the best implementation of a device blessed with project butter combined with the blessing of great developers of Google. I have not seen a nexus 4 lag ever. EVER.
Personally, I don't get what's it with galaxy note. I can't understand what's wrong with it to lag so much, I mean, sometimes it lags more than my one v which is a 1ghz single core processor ( I'm not talking about over clocking here).
I think only a professional dev can put light on this.
Sent from my One V
AA1973 said:
I tend to disagree on the part which states that these AOSP/AOKP ROMs feel more laggy than TW ROMs. As of today, I run Asylum ROM 25/02 which includes major improvements concerning the overall UI experience. It is snappy and smooth. I do explicitly avoid the term "buttery smooth" as it is misleading.
They are not finished products, that's for sure-but being heavily developed. :thumbup:
Any TW ROM running 4.1.2 won't be "buttery smooth" neither, whereas the leaked 4.2.1 ROM already showed improvement and thus where helpful to update the Mali blobs for CM10.1, which are successfully implemented. They do work nicely!
If permitted to ask: when did you last try out an AOSP/CM ROM?
Side note: if you blame Samsung, you're always right! I fully agree.
Click to expand...
Click to collapse
I totally agree with you, and the fact that an incredible amount of great work is put in AOSP roms remains undeniable. As I said, I blame Samsung, and my respect for developers is unbounded.
My last try was for beerbong's paranoid android v2.99, and I've tried almost any rom in the original dev section. Still, it's been a long time since I have tried, so i'll have a look ! Of course, there are other things that make me stick to stock, SPen integration mostly (looks like there is still no way to use palm rejection in CM roms).
Anyway, I'm glad to see JB leaks help CM developers, I thought the only workaround required kernel sources.
@soham_sss
I see I'm not the only one wondering what could prevent the note from being smooth...
For me, JB is very smooth. Don't forget, that our GNote has just that little Mali GPU which has to drive this huge 1280x800px (Macbooks of 2011 have this resolution ) screen. Based on that fact, JB is buttery smooth.
I suggest to set all animation times in the developer options of your phone to 0.5 (don't forget to reboot, to get the new speeds everywhere in the OS). It makes the Note feel much quicker and more responsive.
When you are there, also try "Force GPU rendering". Every app compiled with the 2.3 SDK has the GPU rendering flag set to off, this option forces it on. I haven't found any apps that don't like this setting and crash. Also, when you google for this, you won't find any apps neither that refuse to work.
I'm very happy with JB. It's smooth and the CPU doesn't have to render anything anymore. Nice!
As I'm thorough, I tried Asylum ROM, as advised. :silly: One thing immediately stroke me : the notification bar is not smooth. It just isn't, there's a discomfort that should not be as if it was still CPU run. And I don't think I'm picky, it's a raw feeling. The rest of the rom is, indeed, pretty snappy (the browser appear much much lighter), but I really need this element of my UI to be impeccable as it come to smoothness, just like the home screens transitions.
hihipunkt said:
For me, JB is very smooth. Don't forget, that our GNote has just that little Adreno GPU which has to drive this huge 1280x800px (Macbooks of 2011 have this resolution ) screen. Based on that fact, JB is buttery smooth.
I suggest to set all animation times in the developer options of your phone to 0.5 (don't forget to reboot, to get the new speeds everywhere in the OS). It makes the Note feel much quicker and more responsive.
When you are there, also try "Force GPU rendering". Every app compiled with the 2.3 SDK has the GPU rendering flag set to off, this option forces it on. I haven't found any apps that don't like this setting and crash. Also, when you google for this, you won't find any apps neither that refuse to work.
I'm very happy with JB. It's smooth and the CPU doesn't have to render anything anymore. Nice!
Click to expand...
Click to collapse
I was not aware that the Note uses Adreno? I thought it was Mali
crash-petard said:
As I'm thorough, I tried Asylum ROM, as advised. :silly: One thing immediately stroke me : the notification bar is not smooth. It just isn't, there's a discomfort that should not be as if it was still CPU run. And I don't think I'm picky, it's a raw feeling. The rest of the rom is, indeed, pretty snappy (the browser appear much much lighter), but I really need this element of my UI to be impeccable as it come to smoothness, just like the home screens transitions.
Click to expand...
Click to collapse
+1 couldnt agree more.
Ive always had nit picks with my android devices (mainly samsung, some HTC's in the past) and have always experienced some sort of lag, with stock and custom ROMs.
But, correct me if im wrong, I believe this is down to the overlay put on by these companies, they cram the devices with ridiculous amounts of bloatware and eye candy and I feel that has an effect on the overall smoothness.
Ive yet to own a pure AOSP device (such as the nexus's) but i cant recall many people complaining about them.
But I prefer the looks of TW / Sense over AOSP (and ive tried lots of AOSP ROMs) so I accept that bit of lag for the overall look and functionality of things.
tommy_vercetti said:
I was not aware that the Note uses Adreno? I thought it was Mali
Click to expand...
Click to collapse
Oops. I will change that. Nevertheless: That GPU just isn't the fastest anymore.
And that AOSP is faster, is just normal when you don't unbloat your phone. It's the same with every other Android phone out there. Also AOSP doesn't offer multiwindow, I bet many people aren't really aware of the technical difficulties this brings with it. And therefore this phone is very smooth.
Also try tinkering with the build.prop a little.
windowsmgr.max_events_per_sec
persist.sys.use_dithering
persist.sys.use_16bpp_alpha
can help a lot with the "lag".
But I don't have any lag, so I'm not changing anything. Another thing to maybe consider: Do you have a corrupt install?
The point of this thread is to discuss whether Project Butter is effective on the Note or not, WITHOUT any modifications.
4.1.2 JB LSZ Ultimate 5.2 ROM, KSO Modem, Phil's LSZ kernel, Carrier: AT&T (US)
It isn't since AFAIK Samsung doesn't release source code for Exynos.
If those on a TW JB ROM could download and install "Epic Citadel"(preferred via WiFi as it is a 150mb package) and play the demo. I bet it won't get beyond the 40fps in high quality..
I didn't advise to install Asylum and don't quite get the point of the notification bar. As long as Samsung fails to deliver "proper+sources" we won't get the real "butter" experience.
Apparently the leaked S3 ROM based on 4.2.1 went into a better direction as some Mali blobs could be used, but close to nothing from the 4.1.2 ROMs...
@incisivekeith It may be "project better", but not project butter.
All we need is the official source code and then everyone will be happy n_n
_____________________________
via GT-N7OOO using XDA-2
soham_sss said:
I'd like to step in here, and this is entirely wrong: Project Butter was not included in jb for viewing in high speed cameras: it was mainly to reduce lag and stutteriness in Android to make the experience amazing for common, general public. Not for professional photographers.
Personally, when my one v is over clocked to 1.5 GHz and above ( and using a jelly bean ROM), the effect is mind blowing. I'd say the device comes near smooth as an iOS device, if not smoother. There are absolutely no lags and waits, and the device performs like a breeze.
Have you ever used a nexus device? That's the best implementation of a device blessed with project butter combined with the blessing of great developers of Google. I have not seen a nexus 4 lag ever. EVER.
Personally, I don't get what's it with galaxy note. I can't understand what's wrong with it to lag so much, I mean, sometimes it lags more than my one v which is a 1ghz single core processor ( I'm not talking about over clocking here).
I think only a professional dev can put light on this.
Sent from my One V
Click to expand...
Click to collapse
First of all this is not one v thread or an iOS speed competition. Different devices get different sources to work with. So it doesnt mean that one v is superior. I am happy that at least cm team is giving us nice smooth, fast and daily ROM. TW is for noobs. I don't care about other devices or bull**** until I choose them personally. High speed camera was just for fun...
Cheers from Hell.... :sly:
once you remove bloatedstuff, like automated test, and about 30 others, own risk, reboot, flush cache/dalvik, you will notice considerable improvement, most of the time, but yeah it still stutters sometime.
damn endless tweaking, dont forget some to disable some triggers on boot fo apps you only need on demand.
all own risk buddies
is there someone that are thinking to develop a rom for s advance based on android L 5.0 that are coming up?
i think s advance has some potential, so i hope someone make a rom
From this thread:
Android 5.0 Lollipop from Team Canjica probably will never see the light. In our opinion, Galaxy S Advance and in generally STE-based devices are too weak to handle well another Android major release.
The fact is that more time passes, more OS and applications become heavier and complex.
Was a pain to get a "stable" (between quotes since still has some issues like huge battery drain, that can't be fixed) Kitkat.
Another major release means heavier, more complex, CPU even with OC is too slow to handle and execute well threads, RAM memory is too little and this means lags, impossibility to run big apps and the Mali 400 single core GPU is too weak for more complex graphic effects in games that will come and especially in transitions between menus, pull down status bar etc. The last perfect major release for this device is Jelly Bean 4.3, to build any major release means that we need to research and find (with A LOT OF TESTING) how to fix bugs, means that we need to develop new OMX patches to make camera and videos working. KitKat is okay but huge battery drain and a lot of lags are signal that it's the last major release that these STE devices can handle in a non-stable way against JB 4.3 that it's almost (to not say "totally") stable. Now, stop a moment and imagine Lollipop, totally ruined user experience. Do you wanna live together with device lagging 99/100 times (1/100 without lags rightly after power on, maybe) and with charger always connected? We should be lords of our devices, not slaves. Nobody of us still uses a STE device and without is totally impossible to develop what has never been developed, if you want to keep updated I'm sure that you would change device asap, today even a 100€ device is more powerful than these. Janice will be 3 years old on April 2015, it's just the future coming...
We loved this device, development, known good guys here... Officially this device died on 4.1, Team Canjica gave you 3 major releases!!!
Never forget
Do you have anyone the extreme kernel v2.1 for the Xiaomi Mi9? and also what happens with Extreme Kernel website?
Why don't you ask the developer instead of starting spamming, again, the forum?
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Daenjel said:
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Click to expand...
Click to collapse
Arter is a good boy. Always working on f2fs.
BTW why people need that stupid kernel with high antutu score?
Kollachi said:
Arter is a good boy. Always working on f2fs.
BTW why people need that stupid kernel with high antutu score?
Click to expand...
Click to collapse
People seems to be so superficial sometimes, they base the performance of their devices on just numbers without knowing what the OC does to the CPU/GPU and the components in general, just to get those fancy numbers..
I need this kernel because in the last 2 months I'm using the extreme kernel v5 60hz and I have 10-15% better performance...yes on Android games my phone overheating but on any emulator for example dolphin, ppsspp, damonps2pro my phone isn't overheating with gaming and screen recording at the same time. Also on Android games through the Extreme Kernel Manager I choose lower GPU frequency (450 mhz) on these games and better cpu/gpu mods (for throttling at a higher temperature than normal) and I have supper stable gaming without framedrops. So I need in a few months the overclocked Snapdragon 855 with 30%, or the lowest 20% gpu overclock (blackshark 2) for emulators, for better content on YouTube (my name is Greece Mobile) and the comparisons with my future Laptop (gtx 1050, i7 6cores 12 threads). Also the overclocked Snapdragon 855 it has almost similar performance than the gt 1030 and also on my YouTube channel I will test on 2-3 weeks the Malakas Kernel, the most optimize kernel for the Pocophone F1 with 9400 geekbench score without cpu overclock and similar GPU overclock than the extreme kernel.
Overclocking should become a habit, especially as nanometres becomes smaller.
Big wall of text for a YouTube channel advertising.
Nuno Oliveira said:
Big wall of text for a YouTube channel advertising.
Click to expand...
Click to collapse
Not exactly.. This is my love and also I watch these videos since 2014, techutopia, unbox therapy and many others YouTube channels famous or not
Also just yesterday I discovered how I can play the only IR nunchuck + wii remote games like COD 3, COD Modern Warfare Reflex Edition, Moto GP 2008 and many other << unplayable >> Wii games and I am very happy ?
Great advertise...
Also, I wont tell you why OC on mobile devices is bad and didn't make sense over the last 5 years, you can search it for yourself, but yeah, this kernel/project is officially dead, at least that's what the "developer" said on his Telegram channel, if you found a backup/old ver. then great! But don´t expect updates soon..
Daenjel said:
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Click to expand...
Click to collapse
That's how the vast majority of custom ROMs are built these days. More often than not the ROM devs aren't aware of bugs until users report them. Some devs build ROMs for devices they don't even own or for devices they do own but don't actually use.
This is especially the case with ROMs and kernels for OnePlus phones because devs don't use OnePlus phones but it happens with many other brands and models as well. Bugs are now normal and expected on "stable" builds of custom ROMs. That was not the case 5 years ago. Back then CyanogenMod was the only custom ROM that always had bugs--because they were building for so many devices they couldn't do proper testing.
I'm not sure why there would be a scandal because the Extreme Kernel was built like virtually every other custom ROM and kernel.
jhs39 said:
That's how the vast majority of custom ROMs are built these days. More often than not the ROM devs aren't aware of bugs until users report them. Some devs build ROMs for devices they don't even own or for devices they do own but don't actually use.
This is especially the case with ROMs and kernels for OnePlus phones because devs don't use OnePlus phones but it happens with many other brands and models as well. Bugs are now normal and expected on "stable" builds of custom ROMs. That was not the case 5 years ago. Back then CyanogenMod was the only custom ROM that always had bugs--because they were building for so many devices they couldn't do proper testing.
I'm not sure why there would be a scandal because the Extreme Kernel was built like virtually every other custom ROM and kernel.
Click to expand...
Click to collapse
Yeah you're right, but it doesn't meant that it should be that way.
Building blindly is risky as always, and yeah, every time you flash something to your device , you're doing it by your own risk, but it doesn't mean that the developer can just overclock your CPU/GPU, fill a kernel with "gosht" features and call it a day.. Or even don't knowing that overclocking a cpu/gpu blindly, could lead to "kill" the device in a near future...
Btw, this wasn't the scandal from where he left his projects, it was a lot more behind, that's why I said that everyone should visit that Twitter account from before, to learn why everything from this particular kernel wasn't okay at all...