[Warning] Never set VM Heap size too low on Galaxy Note

[LowDef]

I had been playing with the VM Heap size. My note was working fine with the value of 128m and 64m. However after tried changing down to 32m the Note's re-start stuck in glowing SAMSUNG logo with no choice but to re-flash ROM.

So guys be careful playing with this tweak. I won't touch it again and leave it at default setting.

 

[zylor]

I had been playing with the VM Heap size. My note was working fine with the value of 128m and 64m. However after tried changing down to 32m the Note's re-start stuck in glowing SAMSUNG logo with no choice but to re-flash ROM.

So guys be careful playing with this tweak. I won't touch it again and leave it at default setting.

I actually always put it on 128Mb to have a smooth experience!

VM Heap is the maximum memory allocated for an application to run smoothly!

 

[LowDef]

I actually always put it on 128Mb to have a smooth experience!

VM Heap is the maximum memory allocated for an application to run smoothly!

I checked VM Heap size on my stock rooted ICS last night and found that it's 256m. So I think the 128m is not optimum for Note.

 

[zylor]

My bad.. 128 is for SGS2 lol

you are right my friend

 

[Kanalcommander]

I checked VM Heap size on my stock rooted ICS last night and found that it's 256m. So I think the 128m is not optimum for Note.

Just because it's the stock setting it is not said it's the best setting. If stock settings were always the best settings there would be no need for custom Roms and tweaks.

Gesendet von meinem GT-N7000 mit Tapatalk 2

 

[LowDef]

Just because it's the stock setting it is not said it's the best setting. If stock settings were always the best settings there would be no need for custom Roms and tweaks.

Gesendet von meinem GT-N7000 mit Tapatalk

Now what is the right value then?

Don't just leave everything upon the cookers settings since so far their ROMs have never been being the best.

 

[Atomix86]

Honestly what app needs 256mb? I always set mine to 128mb.

Sent via carrier pigeon

 

[LowDef]

What is the benefit for reducing it to 128m? or even increasing it higher?

 

[alex3305]

Although your thread title is right, your information can be a bit misleading.

The heap is a Java term that is used for storing application related resources into memory. For instance layouts, Java-code, strings or arrays with information. But in all versions below Android 4 (ICS), The default size an application needed was about 3MB for this. Bitmap's were placed outside the heap for some stupid reason. That's why one could get away with an heap size of 32MB or even lower. At the time this was probably a good idea because devices tended to have small internal memory (256MB or 512MB) and so Bitmap's could be swapped by the OS.

Anyway, with current devices and the current state of Android, the Bitmap's - which are a large portion of the allocated memory - are placed inside the heap. Also if you turn on to force GPU an app will use an extra of 8MB internal memory. So if you would add things up, you would at least need about 11MB for only starting the program. About 1MB for random values and quite a lot of memory for 'non-compressed' images. I guess about 16MB if your device would want to draw the entire screen without any compression with one 16-bit image! After which your app would use about 40MB of memory.

Now, take the Android launcher for example, that's an app with loads of images cached in memory. So my guess is that an app like that would use around 70 - 80MB of heap size just to run in GPU mode. This shouldn't be a problem with today's devices as we have more and more internal ram and processor speed available to use. So I think the ideal sweetspot for todays apps should be 128MB, as you could fit about ~6 apps running at once in the main memory. If you put the heap size at 256MB you could run about 3 apps at once. Including drawing.

 

[kacs]

Hi!!

Although your thread title is right, your information can be a bit misleading.

The heap is a Java term that is used for storing application related resources into memory. For instance layouts, Java-code, strings or arrays with information. But in all versions below Android 4 (ICS), The default size an application needed was about 3MB for this. Bitmap's were placed outside the heap for some stupid reason. That's why one could get away with an heap size of 32MB or even lower. At the time this was probably a good idea because devices tended to have small internal memory (256MB or 512MB) and so Bitmap's could be swapped by the OS.

Anyway, with current devices and the current state of Android, the Bitmap's - which are a large portion of the allocated memory - are placed inside the heap. Also if you turn on to force GPU an app will use an extra of 8MB internal memory. So if you would add things up, you would at least need about 11MB for only starting the program. About 1MB for random values and quite a lot of memory for 'non-compressed' images. I guess about 16MB if your device would want to draw the entire screen without any compression with one 16-bit image! After which your app would use about 40MB of memory.

Now, take the Android launcher for example, that's an app with loads of images cached in memory. So my guess is that an app like that would use around 70 - 80MB of heap size just to run in GPU mode. This shouldn't be a problem with today's devices as we have more and more internal ram and processor speed available to use. So I think the ideal sweetspot for todays apps should be 128MB, as you could fit about ~6 apps running at once in the main memory. If you put the heap size at 256MB you could run about 3 apps at once. Including drawing.

Ok thanks .....
Im creat a video ok? And I am upload to youtube.

 

[denizenx]

lol yeah just bricked my phone...

 

[lukasspro777]

I have got an Xperia Play

I am rooted this .

One day I am buy the Rom Toolbox Pro

Well I am go to the build.pro tweaks and I am set the VM Heap to low ..... after its asked to me DO you want to reboot your phone and iam reboot it.
And its stuck in the where i can write the PIN Code. But i can not unlock my device in the lockscreen because its reboot but i dont know why

Well what i need to do whit my device?????
PLS help me
ANd sorry for my bad english

Not sure if trolling, or just stupid.

Sent from my GT-N7000 using xda app-developers app

 

[exb0]

I have got an Xperia Play

I am rooted this .

One day I am buy the Rom Toolbox Pro

Well I am go to the build.pro tweaks and I am set the VM Heap to low ..... after its asked to me DO you want to reboot your phone and iam reboot it.
And its stuck in the where i can write the PIN Code. But i can not unlock my device in the lockscreen because its reboot but i dont know why

Well what i need to do whit my device?????
PLS help me
ANd sorry for my bad english

I had that problem oso wit my xp3r14 pl4y.. U n33d 2 m1cr0w4v3 it 2 f1x 1t.

Sent from my Galaxy Nexus using xda premium

 

[howard bamber]

I had that problem oso wit my xp3r14 pl4y.. U n33d 2 m1cr0w4v3 it 2 f1x 1t.

Sent from my Galaxy Nexus using xda premium

Me too

From the man hiding in the attic....

 

[Constantin92]

Galaxy Note I : I did a big mistake... please help

Hi, guys.

It's a pity I didn't read your advice earlier, before I make my mistake.

I have the Galaxy Note I, rooted, and everything was working fine.

I had this evening the bad idea of trying to tweak VM Heap Size.

Previously set at 64m, and I tried to set it up at 36m. The application asked me confirmation for reboot, and from that moment, I cannot complete the boot anymore. I'm stuck at SAMSUNG logo, and that's all...

I didn't install CWM recovery or anything like that...

Do you have any idea of how I could get rid of that, please, without loosing all my data ?

(I'm posting from France, I'm sorry for my English, I hope you will understand my questions)

Constantin.

 

[noteandfound]

maybe factory reset if NOT on stock ICS kernel...
just a thought. I never tried it..

Recognized Distributor™

 

[Constantin92]

thanks

I'll search for more informations about that, and then I'll try it if I can ever find somewhere that it will not harm

Thank you

 

[howard bamber]

When you mess with this stuff just never set it to set on boot, so you can reboot to get back to normality

From box 13......

 

[kaosdroid]

Hi,
for build.prop modif problem like this and you are stuck at boot.


If your device is rooted,you have the ability to recover this noob modification!

If you use flashTool or something like that(maybe odin)

start the program and connect your phone stuck at boot logo.
The program reconize your phone.
now ask for root permission(for ok response,you need to have register your device before in the program,if not the ask could not be done and you are dead at this point !)
now you have root acsess there is an option in the program to write in build.prop/edit file
So load it and give the right path in and change thing you have made wrong(VM=64/128/256)
Save it and reboot

Done!

 

[Addestro]

Yeah brick it down stuck logo