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

When connected to my PC, I'm unable to view my S3 in explorer unless I have USB debugging enabled. When it's not enabled, it shows up as a device in Device Manager, but it doesn't appear as a device I can explore from My Computer. However it works fine on my laptop, and I can see it with our without USB debugging enabled. Therefore I'm guessing it's an issue with drivers on my desktop. It's not a massive problem but it would be nice to not have to turn USB debugging on whenever I connect it. Has anyone had this problem and managed to fix it, or have an idea how I might be able to? I've uninstalled and reinstalled Kies but that hasn't done anything.
 
Was having some problems so i've done a complete wipe of v91.

I keep having an annoying youtube issue. when i watch a video full screen, every time i get a notification, it turns the page portrait and pause it, so i have to return it portrait to landscape again and replay it. Even if there is a existing notification hanging in the tray, it still seems to stop it.

Have done a complete wipe and reflash, have also reinstalled youtube.
 
How rapidly and fast does Temasek's CM11 updates release?

I'm thinking of changing to the SlimKat ROM series. I know it uses the CM11 sources, although I think the updates are less intense and closely spaced out. I know it is good having quick updates, but the publisher could do numerous tests himself and find a lot of bugs that way (saving the public and general users of CM11 and his ROMs a lot of time). On the other hand, it may also save him time in the long run as well.

Flashing them every night near enough can be time consuming, especially if you're busy and have a lot to do (like me). I'm always seeing a new ROM every time I check this thread (every couple of days to a week).

Only 2 weeks ago I was flashing the final builds of the v79. Now we're into the v90 zone with v91? D: :eek:

It's annoying having to do a Nandroid backup via Recovery, flash the new ROM and restore the Nandroid backup via certain methods (using apps such as Titanium Backup).

I don't use CWM Recovery, or Philz Touch Recovery, because I use TWRP Recovery. I find this particular recovery console the most useful and ease of use. It has advanced features, although I rarely need to use them.

Sorry for so many edits - I was adding and correcting given information. :p
 
Last edited:
Since installing Slimkat I've noticed the Gallery shows loads of blank pictures in the Camera album. I know they aren't pictures with just the thumbnails missing because QuickPic lists about 230 photos, whereas Gallery lists about 930. It looks like this:

2014-06-05%2012.28.11%20%28Small%29.png


Having done some searching it appears to be an issue with media scanning/cache having been deleted and a re-scan not being done, I'm not entirely sure. I know things were changed in 4.4 regarding media scans, so it's not as easy to do as before, but I have seen at least one app that claims to do it (https://play.google.com/store/apps/details?id=com.gmail.jerickson314.sdscanner). However what I don't know is whether this will actually remove the "incorrect" blank pictures or not. I read elsewhere about clearing the data for the Media Storage app, but I'm a little uneasy about doing that just yet.

Has anyone else had this problem and managed to fix it, without manually deleting all the "blank" pictures?!
 
Last edited:
Since installing Slimkat I've noticed the Gallery shows loads of blank pictures in the Camera album. I know they aren't pictures with just the thumbnails missing because QuickPic lists about 230 photos, whereas Gallery lists about 930. It looks like this:

2014-06-05%2012.28.11%20%28Small%29.png


Having done some searching it appears to be an issue with media scanning/cache having been deleted and a re-scan not being done, I'm not entirely sure. I know things were changed in 4.4 regarding media scans, so it's not as easy to do as before, but I have seen at least one app that claims to do it (https://play.google.com/store/apps/details?id=com.gmail.jerickson314.sdscanner). However what I don't know is whether this will actually remove the "incorrect" blank pictures or not. I read elsewhere about clearing the data for the Media Storage app, but I'm a little uneasy about doing that just yet.

Has anyone else had this problem and managed to fix it, without manually deleting all the "blank" pictures?!

Damn, I'd prefer the stock ROM to that.
 
Since installing Slimkat I've noticed the Gallery shows loads of blank pictures in the Camera album.

Having done some searching it appears to be an issue with media scanning/cache having been deleted and a re-scan not being done

Has anyone else had this problem and managed to fix it, without manually deleting all the "blank" pictures?!

Settings > Apps > All > Media Storage > 'Clear Cache' and 'Clear Data'
Then reboot and it'll do a full media rescan.
 
Settings > Apps > All > Media Storage > 'Clear Cache' and 'Clear Data'
Then reboot and it'll do a full media rescan.

Cheers that worked. Since then though I have had problems with the Gallery app not re-scanning the SD card, and also showing some photos out of sync with when they were taken. :mad: My conclusion: the Gallery app is a pile of ****. I've since switched to the much more capable QuickPic.
 
Temasek has updated to android 4.4.3 with v94:

Build V94
md5sum: 35a3b183c6c917457d2f966b99feb02b

CHANGELOG SINCE V93
Android 4.4.3_r1.1 - KTU84M
- This update includes many fixes & changes that spans over MANY repositories. Mostly under the hood except Dialer which spots a new look. TRDS mode for Dialer needs update. I will look into it soon or wait for SlimROM to commit an official fix.
FIXED - Swiping down status bar in full screen expanded mode
FIXED - Apps2SD option "Move to SDCARD" not showing in apps settings
Camera QS Tile: Launch default gallery app when long pressing active camera tile
Themes: uninstallThemeForAllApps shouldn't check if map is empty if it's null
- Potential NPE introduced in previous builds
UsbDebuggingManager : Handle race condition when toggling rapidly
- When toggling adb enable/disable rapidly, you can have the situation where the thread's
run() gets invoked but mAdbEnabled is already set to false, hence listenToSocket() never even gets invoked in which case mOutputStream/mSocket are both null. This patchset adds checks around that.
Don't cleanup overlay mapping for non-theme apps
- mOverlay structure should keep all app/theme mappings even if the app does not exist. Otherwise we will have to insert back the mapping for every app that is installed which would be time consuming.
- Without this patch an upgrade app loses its applied theme until the device is rebooted.
appops: enforce appop for bluetooth disabled action
- Bluetooth disable action should be enforced in the same manner that the enable one.
Add a HAF access permission
- This is signature protected, and extremely dangerous since it grants system GID.
MediaExtractor: Add more skip conditions for the second-pass extractors
- If the stream's container is opaque (DRM) or a known skip condition (cached-source MPEG4), don't push it through the deep scanner
Updated cm sources

There is also a flashable fix if you have an issue with trds and the dialer.
http://temasek.hopto.org/?dir=Samsung Galaxy S3 - i9300/CM11.0
 
Settings > Apps > All > Media Storage > 'Clear Cache' and 'Clear Data'
Then reboot and it'll do a full media rescan.

The Media scanner Issue is related to the process being too aggressively terminated when the screen goes into standby mode. If you keep the screen alive for 10-15mins (depending on size and speed of your SDCARD) on reboot it will then refresh the image cache without a problem. My Wife's s2 has the same problem running SLIMKAT.
 
I think my phone has given up the ghost now :(
The screen started playing up a few days ago, the screen wouldn't turn on but you could feel the haptic feedback of the lock screen.
Sometimes it'd start working again but then it'd stop.

Now I can't hear anything through the earpiece, so kind of negates the point of the phone.

I'm actually a bit disappointed with Samsung tbh, this phone has only lasted me a year!
I had to have it replaced when the screen broke last year!


I really like the HTC M8 but I don't like the menu buttons, I prefer the capacitive buttons like the Samsung phones.

I'm at a loss for now :(
 
I think my phone has given up the ghost now :(
The screen started playing up a few days ago, the screen wouldn't turn on but you could feel the haptic feedback of the lock screen.
Sometimes it'd start working again but then it'd stop.

Now I can't hear anything through the earpiece, so kind of negates the point of the phone.

I'm actually a bit disappointed with Samsung tbh, this phone has only lasted me a year!
I had to have it replaced when the screen broke last year!


I really like the HTC M8 but I don't like the menu buttons, I prefer the capacitive buttons like the Samsung phones.

I'm at a loss for now :(

The S3 has a two year warranty, unroot the thing and put it back to stock then get it repaired.
You can either then keep it or, sell it on, simples.

Mick
 
Things move fast in Custom ROM world, upto V98 With Temasek and looks like V99 will be in the offing. Now quite looking forward to Andriod 4.5 or 5 which is rumoured in the next few months. Considering my S3 ain`t going to get anymore official updates this just superb, no need to upgrade to a new phone!
 
Back
Top Bottom