Originally Posted by nicholas099

Perm solution is to increase the ram
That should be the reason why they increase the RAM from 1GB to 2GB

I will be doing it as soon as i can source the 2GB RAM from eBay.
Anyone know this?

Just open the phone and insert an extra gb ram, it will work well! I just inserted 2gb extra and installed some water- cooling while at it. Overclocked to 4ghz it turns on itself and start a game before I even knew I wanted it to start.. It's THAT fast! Still having redraws... So I can confirm its software related issue

Sent from my GT-I9300 using xda premium

Originally Posted by UpInTheAir

This works for me.........

Faster home screen scrolling; change value 256m > 128m ;

dalvik.vm.heapsize=128m

I'm part of the Omega team, and I was testing various build.prop tweaks regarding vm heap size a few days back.

I found the following settings to be optimal on my GS3 with Omega 4.1/4.2

dalvik.vm.heapstartsize=8m (This is the initial size of a Dalvik VM heap when created)
dalvik.vm.heapgrowthlimit=64m (This is the maximum size a Dalvik VM heap can grow to)
dalvik.vm.heapsize=64m (This is the maximum size a Dalvik VM heap can grow to for 'large heap' apps - apps that specify android:largeHeap=true in their application manifest)

I saw good results with these settings, but, I cant be sure that dalvik.vm.heapsize set to 64m wont create problems on some larger apps that Ive not used extensively, or dont have installed.

So I'm recommending the following settings. These settings didnt make it into Omega 5.0 but hopefully will make it into the next version by default:

dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=128m

Originally Posted by UpInTheAir

Force launcher to stay in memory; add to build.prop

ro.HOME_APP_ADJ=1

Doubt it's placebo, but seems to be working Very little redraw with TW Launcher

Complete Placebo

in ICS, and ADJ settings in build.prop are ignored.
These settings in ICS are in services.jar

@ subvertbeats

Thanks for your comments and posting of past test summary.

I'll give your settings a go, and reduce the heap size to 64. See how I go.


Sent from my GT-I9300T using xda premium

Originally Posted by UpInTheAir

@ subvertbeats

Thanks for your comments and posting of past test summary.

I'll give your settings a go, and reduce the heap size to 64. See how I go.


Sent from my GT-I9300T using xda premium

Let us know how you get on

Originally Posted by subvertbeats

Ive seen a bit of misinformation flying around various threads regarding home screen redraws....just some background for those interested:

I was testing various build.prop tweaks regarding vm heap size a few days back.

I found the following settings to be optimal on my GS3 with Omega 4.1/4.2

dalvik.vm.heapstartsize=8m (This is the initial size of a Dalvik VM heap when created)
dalvik.vm.heapgrowthlimit=64m (This is the maximum size a Dalvik VM heap can grow to)
dalvik.vm.heapsize=64m (This is the maximum size a Dalvik VM heap can grow to for 'large heap' apps - apps that specify android:largeHeap=true in their application manifest)

I saw good results with these settings, but, I cant be sure that dalvik.vm.heapsize set to 64m wont create problems on some larger apps that Ive not used extensively, or dont have installed.

So I'm recommending the following settings. These settings didnt make it into Omega 5.0 but hopefully will make it into the next version by default:

dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=128m

Complete Placebo

in ICS, and ADJ settings in build.prop are ignored.
These settings in ICS are in services.jar

OK, to follow up on this...

Attached is a patched services.jar for Omega 5.0 that has launcher priority set to 1 (Die Hard) vs the stock value of 6.

1. Download this file to your machine.
2. Open a command prompt / terminal at the location of your downloaded services.jar
3. Connect your SGS3 to your machine via USB
4. Use adb to push the file to your machine:

adb devices
// just to validate your device is seen
adb remount
// should see message indicating remount is succesful
adb push services.jar /system/framework/services.jar
// should see message indicating transfer complete: (1396054 bytes in x.yyy s)

5. Open a terminal on your device and set correct permissions on the file:

cd /system/framework
su
busybox mount -o remount,rw /system
chown 0.0 services.jar
chmod 644 services.jar

6. Reboot into recovery and wipe Dalvik cache
7. Reboot into ROM

8. Report back here if this has helped improve any homescreen redraw issues you may have been having


Credits to zeppelinrox for the research behind this one and his useful webapp for patching services.jar.

Reporting back after 10 mins of heavy usage with above post settings.

Opened just about every app I could and left them in ram or running in task manager. Used Google Play for a bit and XDA.

Early result: Improved redraw of TW home screen, particularly with the weather widget.

Sorry, can't give a longer test yet and determine if it's sporadic, as need to charge battery. Edit: onto the tab

Sent from my GT-I9300T using xda premium

Originally Posted by UpInTheAir

Reporting back after 10 mins of heavy usage with above post settings.

Opened just about every app I could and left them in ram or running in task manager. Used Google Play for a bit and XDA.

Early result: Improved redraw of TW home screen, particularly with the weather widget.

Sorry, can't give a longer test yet and determine if it's sporadic, as need to charge battery. Edit: onto the tab

Sent from my GT-I9300T using xda premium

You just mean the dalvik vm heap build.prop weaks right?

I see you're not on Omega - so dont use that patched services.jar (for those on Omega 5.0 that should mean that the launcher is killed far less often (and hence redraws will happen far less often)

Originally Posted by subvertbeats

You just mean the dalvik vm heap build.prop weaks right?

I see you're not on Omega - so dont use that patched services.jar (for those on Omega 5.0 that should mean that the launcher is killed far less often (and hence redraws will happen far less often)

Sorry, yep 64m

Looks like I might CWM backup and give Omega a run . Tomorrow.......

Will see how 64m runs for a while first.

Sent from my GT-P6810 using XDA Premium HD app

subvertbeats....

can you let us know when you think you have definitively fixed this problem and it's included in the Omega rom... I will wait until then before downloading.

Many Thanks

Originally Posted by SidharthaXx

subvertbeats....

can you let us know when you think you have definitively fixed this problem and it's included in the Omega rom... I will wait until then before downloading.

Many Thanks

It seems good so far, but havent been using my phone heavily.

Would appreciate others testing. Only then with a broader sample than just me will I recommend it being included in the next version of Omega.

---------- Post added at 02:22 PM ---------- Previous post was at 02:02 PM ----------

Originally Posted by nicholas099

Perm solution is to increase the ram
That should be the reason why they increase the RAM from 1GB to 2GB

I will be doing it as soon as i can source the 2GB RAM from eBay.
Anyone know this?

Please tell me your post is a joke