I've had it with Android

[Stannis the Mannis]

I think the reason it runs jellybean slow is 4GB of internal hard drive space, but having <1GB of ram doesn't help. Stock jellybean itself uses roughly 3GB, then you have to add touchwiz on top of that. Jelly bean slows down and becomes unstable if you have less than 165MB of space left. I imagine after the os, there's not much left. Then simply downloading apps would push one over the threshold.

3gb? When my phone updated to JB it was roughly 300mb in size, give or take.

 

[jhawkkw]

3gb? When my phone updated to JB it was roughly 300mb in size, give or take.

The file that you downloaded which installed the OS was 300mb, but when it installs over old files, and adds the new files, the whole OS takes up about 3GB. Then after that, you have have add the stuff that your oem adds including their launcher and other bloatware.

By looking at a Nexus device, which runs clean stock android with no bloat with a 16GB hard drive, after formatting and the OS, there's 12.92GB left. 16-12.92 = 3.08GB

 

[chanchan05]

I am about an hour away from finishing downloads for installing a JB ROM on my Galaxy SL with 1Ghz single core, 512MB RAM, PowerVR535 and 4GB internal memory. I'll be using RemICS which actually has the S4 look touchwiz on top of JB. I'll report on the performance later. I think this has enough power for JB, and so does the OP's Ace2. I think he's just a victim of a bad update. For example the official 2.3.6 update for my phone was horrible, but when I flashed the stock 2.3.6 ROM for some Euro versions, performance was awesome at the time.

Case in point as well is that I have seen the Galaxy Chat and Fame, running JB with single core 800Mhz procs and they seem to be doing well.

 

[jhawkkw]

I am about an hour away from finishing downloads for installing a JB ROM on my Galaxy SL with 1Ghz single core, 512MB RAM, PowerVR535 and 4GB internal memory. I'll be using RemICS which actually has the S4 look touchwiz on top of JB. I'll report on the performance later. I think this has enough power for JB, and so does the OP's Ace2. I think he's just a victim of a bad update. For example the official 2.3.6 update for my phone was horrible, but when I flashed the stock 2.3.6 ROM for some Euro versions, performance was awesome at the time.

Case in point as well is that I have seen the Galaxy Chat and Fame, running JB with single core 800Mhz procs and they seem to be doing well.

Yeah, processor and ram aren't the issue. The Nexus S runs JB like a champ with it's 1GHz single core and 512 ram. I'm curious to see how it runs with a hard drive the same size, though I'm guessing a custom rom will be debloated and deodexed so performance will be improved at least slightly.

 

[chanchan05]

Yeah, processor and ram aren't the issue. The Nexus S runs JB like a champ with it's 1GHz single core and 512 ram. I'm curious to see how it runs with a hard drive the same size, though I'm guessing a custom rom will be debloated and deodexed so performance will be improved at least slightly.

The Chat and Fame have smaller hard drives if I remember correctly. Plus its not fully debloated. Remember this custom ROM is built to put the new TouchWiz apps from the S4 onto the SL. So optimizations would be offset by these IMO. Anyway, if my old phone would run this ROM ok, then the OP should probably start looking at custom ROMs.

 

[funkylogik]

Ive had my phone a year and im hoping the hardware is future proof enough that good dev support will keep it relevant for another couple of years lol cant afford a new one

 

[chanchan05]

Ive had my phone a year and im hoping the hardware is future proof enough that good dev support will keep it relevant for another couple of years lol cant afford a new one

It most likely would be. I have a device that's more than 2 years old whose dev community isnt as vibrant as yours and I got it running on JB thanks to them! Plus, so far its working great! So I guess I'd think that the OP's problem isnt JB itself but the specific stock ROM he got.