***The Official Samsung Galaxy S III Thread***

Nice Guide Cheers for that mate. All up and running. I was using CWM recovery, always been fine in the past, but for some reason it couldn't mount my SD card, so no zip installs :( Using Philztouch now, looks pretty. One thing i would recommend, which works for me is ROMNUKE. I change Roms a fair amount and a lot of the time the storage mounts at different points and messes up the file system a bit. Leaves all the old data from the previous rom.

This is a ZIP you install in the same way, which is a script which just nukes all the internal storage partitions to leave them nice and clean. my previous rom was showing as 7GB used as soon as it was installed, because the rom before that mounted at a slightly different location which the new ROM didn't install over.

Must say, not a big fan of that google apps package, everything was using the old icons, even after updating play services it still looked a bit ropey. Went for the CM11 Gapps one instead.
 
Last edited:
HecFam said:
Nice Guide Cheers for that mate. All up and running. I was using CWM recovery, always been fine in the past, but for some reason it couldn't mount my SD card, so no zip installs :( Using Philztouch now, looks pretty. One thing i would recommend, which works for me is ROMNUKE. I change Roms a fair amount and a lot of the time the storage mounts at different points and messes up the file system a bit. Leaves all the old data from the previous rom.

This is a ZIP you install in the same way, which is a script which just nukes all the internal storage partitions to leave them nice and clean. my previous rom was showing as 7GB used as soon as it was installed, because the rom before that mounted at a slightly different location which the new ROM didn't install over.
Click to expand...
Scripts like this are not need if you use Philztouch as it has a built in wipe for new ROM option. Most of the time hangovers from old ROMs is normally because Google sync backs up your system partition and auto restores these folders and files, I've started turning that option off when doing a full wipe as its a pain in the behind when your trouble shooting a ROM.
Must say, not a big fan of that google apps package, everything was using the old icons, even after updating play services it still looked a bit ropey. Went for the CM11 Gapps one instead.
Click to expand...
I was using Banks core Gapps but had some issues with sync so tried the Slim one when installing SlimKat on the wife's s2. I will take a look at the CM11 package as I remove Goggle Music and Hangouts as I don't use them.
 
I've gone back to CM11, same Temasek rom was really nice.

I just kept having a problem, when a notification came in, it would freeze the screen black with only the hard keys lit up. It would stick from anything from 30 secs to a couple of minutes. I could always force a restart, but its not ideal. I will defo go back to his rom, but hopefully a new update when its working for me.

going to see if there is a beta i can try or something.


Edit, im reinstalling Temasek v77 but going to give the kernal a miss, just to see if it improves.
 
Last edited:
HecFam said:
I've gone back to CM11, same Temasek rom was really nice.

I just kept having a problem, when a notification came in, it would freeze the screen black with only the hard keys lit up. It would stick from anything from 30 secs to a couple of minutes. I could always force a restart, but its not ideal. I will defo go back to his rom, but hopefully a new update when its working for me.

going to see if there is a beta i can try or something.


Edit, im reinstalling Temasek v77 but going to give the kernal a miss, just to see if it improves.
Click to expand...

The Notification/lockscreen issue was caused by a CM11 code update in the nightly build Temasek used for v75-6, it was a memory leak of some type. He has implemented a fix in to v77 so far I've been running it for 8hrs with out an issue!
 
BigBoy said:
The Notification/lockscreen issue was caused by a CM11 code update in the nightly build Temasek used for v75-6, it was a memory leak of some type. He has implemented a fix in to v77 so far I've been running it for 8hrs with out an issue!
Click to expand...

Good to know, I just did a full wipe and flashed v77 before posting my S3 to my brother :p
 
BigBoy said:
The Notification/lockscreen issue was caused by a CM11 code update in the nightly build Temasek used for v75-6, it was a memory leak of some type. He has implemented a fix in to v77 so far I've been running it for 8hrs with out an issue!
Click to expand...

Nice one, all up and running the way i like it. How do you update to a new version, flash it over the top of the old one? or is it always a clean install?
 
HecFam said:
Nice one, all up and running the way i like it. How do you update to a new version, flash it over the top of the old one? or is it always a clean install?
Click to expand...
No need to wipe data just do the following.

Boot into recovery
Mounts and storage
Format /system /cache /preload
Advanced and wipe dalvik
Flash new ROM and gapps package reboot and jobs done!

If you use a theme set it to system before flashing the new ROM or it will be come corrupt (the theme not the ROM).
 
Tasty, all my themes are stock. I know you used to get new nightlys with Cm11, which installed in settings, wasn't sure if there was a similar thing for temasek. as long as data is ok, i think im a happy bloke.
 
Sho said:
No kitkat update gt-i9300
http://www.sammobile.com/2014/05/08...-galaxy-s-iii-gt-i9300-and-galaxy-s-iii-mini/
Click to expand...

Unless they give an official link to the Samsung Mobile website, then I won't really believe it. I've seen devices with 512MB and a dual core processor running the 4.4.x (KitKat) update smoothly.

The Samsung Galaxy S3 (GT-I9300) as you may have noticed is a previous (of the years 2012/2013) high-end device.

A basic example of how this is complete lies is the LG L40 (D-160), if you take a look at the specifications and evaluate them you'll see this particular device is a low-end device running 4.4.x (KitKat).

What I see when I look at numerous articles is outdated information previosuly used in old news articles made to fool someone.

Hopefully it gets updated to 4.4.x (KitKat), if not then Samsung will have to either remove their TouchWiz UI and make the S3 an excpetion to the official stock android 4.4.x (KitKat) ROM. Samsung should let their users have 4.4 without TouchWiz or alternatively they could have TouchWiz 4.3 (patched as a mention later). Alternatively Samsung could fix and patch the 4.3.x update with extra features imported and complete from 4.4.x (KitKat).

Come on look at these photos from the news article posted on SamMobile which ISN'T an official Samsung Mobile website:

S3-Dev-Report.jpg


kitkat-Update-status.jpg
 
Last edited:
BuZ said:
Unless they give an official link to the Samsung Mobile website, then I won't really believe it. I've seen devices with 512MB and a dual core processor running the 4.4.x (KitKat) update smoothly.

The Samsung Galaxy S3 (GT-I9300) as you may have noticed is a previous (of the years 2012/2013) high-end device.

A basic example of how this is complete lies is the LG L40 (D-160), if you take a look at the specifications and evaluate them you'll see this particular device is a low-end device running 4.4.x (KitKat).
Click to expand...
Sammobile may not be an official Samsung website but they are a very reliable source and are usually spot on with what they say. How is it lies just because an LG phone with less ram will run kitkat? The LG phone doesn't run touchwiz (which is a massive resource hog) and I'd say touchwiz bloatware is very likely the reason why they are struggleing to upgrade the i9300 up kitkat.

Even the Galaxy s2 has 1gb ram and runs a less bloated version of touchwiz, so in theory that will be getting kitkat too? Nope! That's stuck on 4.1.2. and always will be (excluding custom roms of course :) )

Samsung seem to support software updates for around 18-24 month. That's what they did with the s1, s2 and other phones. The s3 is now 24 months old and unfortunately I'd say sammobile are spot on with what they're saying.
 
Just installed Temasek v79, seems very smooth and slick. The only thing i miss from TouchWiz, is the reliable camera drivers. I would never go back to a TouchWiz rom purely for the camera though.
 
I full wipe every time. If i use another camera app, it works fine. It was only when they started using the Google camera that it stopped working. No problem really, just a gripe. Been rooting and roming for a while, so I'm used to it.
 
I'm looking into installing a custom ROM. I need a list of the most stable ROMs (most stable to stable/fine). I am thinking Cyanogenmod 10/11 is the most stable and has a lot of features compared to most other custom ROMs.

I am confused on what to install.

I know I should I either use CWM Recovery or TWRP Recovery and I need to have my phone rooted in order for me to perform any of the above tasks.

Anyone have any suggestions for me?
 
You must log in or register to reply here.
Back
Top Bottom