Android OS Forum banner
1 - 9 of 9 Posts

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #3 ·
OP updated with GB modded build.prop, to flash that either flash the kf2 deodexed in cwm then the performance.zip or manually push using a file explorer with root access
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #6 ·
Flashing this does the following and more:
sets rom's heapsize to be at 32m
makes your data connection better meaning better uploads and downloads(its suppose too)
makes scrolling extremely smooth
helps ext4
enables jit
improves battery life
etc

:p
 

·
Premium Member
Joined
·
92 Posts
ok first of all, jit is not always enabled on froyo by default :p

second, i have done strenuous testing with the build.prop and its values for the sgs4g and 32vm seems to be better
the whole point of this was to improve performance, speed and battery life so why would i do something to slow it down?

as for ro.rilhtcmaskw1.bitmask this is used to help improve data connection along with the other 5 or 7 lines that come with is starting with hsxpa and literally has nothing to do with htc

please before you put your opinion in know what you are talking about :p
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #11 ·
AsX said:
I thought Google enabled JIT on all 2.2 versions. Maybe some manufacturers chose to overwrite this but on our phone it is definitely enabled by default.

The bigger heapsize, the less often garbage collector has to run, which is definitely a good thing as the garbage collection is very expensive thing in terms of resources. There is a tradeoff between the total memory amount and the size of the heap, but on our phones 48MB seems right. It certainly should be better than 32MB. 32 was probably a tweak for some other phones with 256MB of RAM that actually increased it from even lesser default number. On our phone decreasing it doesn't make much sense, you'd only lower performance and decrease battery life in the end.

There is another tweak that stands out as a little bit excessive. It's windowsmgr.max_events_per_sec set to 200. This value tells how often Windows Managers can send events to a window. The default value is 55, which is about every 18ms. 200 changes it to 5ms. Looks too extreme, there is no need to put that much strain on the manager and consequently the CPU. It may increase responsiveness slightly, but at the cost of utilizing more CPU and battery. I'd leave this at default or at lease set it to something way more conservative, like 16-14ms (values between 60 and 70.)
have you even tried the build.prop? im guessing you havent, it dramatically improves the phones, speed, smoothness, and battery life

everything your saying would be right if the build.prop actually made things worse which it doesnt it only improves things

you dont have to use my build.prop i posted this for people who wanted better performance out of their phone

seriously though i do appreciate your opinion :) it is always good to know EXACTLY what your about to put into your phone
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #12 ·
also what you said is right, what i meant to say is that even though what your saying is right thats not the case for everyphone

thats why this build.prop is special it fits this phone :p
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #14 ·
AsX said:
That's exactly my point. I try to avoid putting anything on my phone without understanding what it does.

It's hard to test our phone by just running it, it's so fast already that any perceptive increase or decrease in speed can be attributed to a placebo effect.The battery life is hard to test either because you'd need to run the phone exactly the same way for few days to compare the results, which is course impossible. There are objective tests that can be created, but they really have to be written to test certain aspects of the phone. For example to test the Dalvik heapsize performance one would need to write a program that allocates and deallocates lots of memory, time it for a while, and compare results.

Btw, I there is still a question was the 48MB of heap size the Samsung/Android default or was it tuned by the Bali kernel. If it was Bali, maybe there is a reason to lower it to 32B after all.
yea i believe bali does set it to 48 as an automatic
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #21 ·
Jonathon Grigg said:
Interesting, would you mind if I used the tweak block as a starting base to find similar tweaks for the Nexus S? Proper credit and everything of course, but it's up to you. Particularly interesting because being a T-Mobile device too it could be very similar except the 4G parts (well HSPA).

Sent from my Nexus S using RootzWiki Forums
Go right ahead my friend, EXACTLY why i put them up :p
 

·
Premium Member
Joined
·
92 Posts
Discussion Starter · #23 ·
All the tweaks are compatible for every phone the only thing I can think of is whether your running ext4 or not and also max events per second, also your vm.heap might wanna be at 48 or 64 just takes some testing try the prop as it is and see how it performs

sent from my sgs4g 2.3.3, finally
 
1 - 9 of 9 Posts
Top