yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] brandonb0013:
So, I'm on the 11/29 cm12.1 build. I want to switch to MM but I need a mostly stable device as I don't have a spare. Basically I'm just curious how things are on the latest. I read through every page but couldn't find definitive answers. What's the best version of TWRP to be on, I seen the baseband and modems to use, which nightly seems most promising? Etc. Anything else I missed? Thanks everyone. Can't wait to run MM.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
The latest nightly has been good. Phone, text, mms, data works. Camera is hit and miss. Haven't tried Bluetooth.
[Verizon Samsung Galaxy S III] Master Cylinder:
I had this even on 2.4Ghz. Didn't notice it that often; Rebooted my router, too, but it looks like that wasn't it. On 1/12 now and haven't noticed anything.

My bluetooth sound not routing to the earpieces even though all indicators read go has not been fixed, but I've noticed 2 things:

1.) If I activate bluetooth during a call it will work, but won't work if I make a call immediately afterwards, or any other time.

2.) It works normally on [MENTION=2385005]invisiblek[/MENTION]'s unofficial builds! I had a couple of those nandroids around and I restored a couple and it worked great!! [MENTION=2385005]invisiblek[/MENTION]! What's the secret?

3.) On 1/11 the speaker call sound volume became adjustable again, even with the screen off - wasn't adjustable at all before, though display indicator moved back and forth.

4.) However, On 1/11 people couldn't hear me on speaker phone. Had the screen off. Were not recreational calls so I couldn't experiment further and haven't had the chance to check it since.

On 1/12 now ...
[Verizon Samsung Galaxy S III] Jaws4God:
i am having trouble taking picture with front camera.. 1/12 build
[Verizon Samsung Galaxy S III] Shakes The AssClown:
1/13 the browser will fc after a minute or two.
[Verizon Samsung Galaxy S III] Jaws4God:
front camera froze and rebooted phone on 1/13 build
[Verizon Samsung Galaxy S III] Fenix2002:
1/13 build:

Front camera working mostly OK. One reboot, one freeze, otherwise mostly OK. I *think* maybe the issue is either red-eye reduction or face detection. After turning these off in camera settings, it seemed to get more stable. (Lowering photo quality seemed to help too.)

Just noticed that light sensor still is not working. Phone tester app shows it just sitting at 1lux.

[Lol, was going to share a screenshot, but apparently CM13 screenshots are .png files, and XDA won't let me upload.]
[Verizon Samsung Galaxy S III] Master Cylinder:
Can you guys test bluetooth earpieces, or any other bluetooth function?

Congenital front camera issues continue for me on 1/13.

Chrome works normally - haven't tried stock browser for a few builds.
[Verizon Samsung Galaxy S III] Jaws4God:
I have already gone back to CM 12.1 (via backup). I have to have a stable camera to use as a daily driver.. will keep watching forum for updates.

Thank you.
[Verizon Samsung Galaxy S III] stevet86:
I used my earpiece today for about 20 minutes on two different calls without any problems. This is on the latest release.
[Verizon Samsung Galaxy S III] AdvaitT17:
Awesome rom. ....
[Verizon Samsung Galaxy S III] Fenix2002:
1/14 Build -- (things I've tested, and things that have been mentioned/asked about recently)

+ Speakerphone works (both ways, incoming/outgoing)

+ Bluetooth pairing with laptop and file transfer work (unsure about headset pairing/use) and SmartLock using trusted laptop BT works

+ GPS works

- Light sensor does not work

? Wi-Fi sometimes will turn itself off completely when out of range of known networks (not searching, but turned completely off), but I haven't had any issues of it disconnecting from my home network while I'm in range

-/+/?/WTF(lol) I can get the front camera to work, kinda. The interesting bit, it will work as long as the majority of the shot is dark. Like, I was testing it last night in low-light, and it worked fine. Turn on the lights and it freezes almost every time. (cue the "you're so ugly you broke the camera" jokes.. lol)

[EDIT: Front/Back camera seem more stable with lower picture size and picture quality. Idk, maybe test that out to see if it helps?]

Error output:

java.lang.RuntimeException: setParameters failed

at android.hardware.Camera.native_setParameters(Native Method)

at android.hardware.Camera.setParameters(Camera.java:1953)

at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:341)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:148)

at android.os.HandlerThread.run(HandlerThread.java:61)
[Verizon Samsung Galaxy S III] herbby:
I am on 1/14, using bluetooth in my car while trying to place a call it will not go to car speaker and may reboot if you try to change the setting while in call. The other issue I have found is if you call someone then place them on speaker it will work, but it sometimes reverts back to headset. It's just not 100%.
[Verizon Samsung Galaxy S III] yorkwar:
1/15 nightly, the sound still does not go to earpiece for bluetooth.
[Verizon Samsung Galaxy S III] Jaws4God:
anyone on the 1/17 version? any major fixes?
[Verizon Samsung Galaxy S III] Fenix2002:
Just tried out the 1/18 build. Still having the same issues with the camera, particularly the front camera. Light sensor still doesn't appear to work. Didn't test much past that.
[Verizon Samsung Galaxy S III] Jaws4God:
awesome. thanks! have a great day!
[Verizon Samsung Galaxy S III] Fenix2002:
Thanks. You too! I'll try to keep you up to date on the camera, at least!
[Verizon Samsung Galaxy S III] herbby:
Hangouts does not notify, yet there is a message
[Verizon Samsung Galaxy S III] Jaws4God:
i noticed that too.. is that a hangouts issue or ROM?
[Verizon Samsung Galaxy S III] HeinousJ:
I have been trying to uninstall stock system apps with titanium backup but the system crashes.. I only tried to remove gmail, chrome and a couple of other similar apps. I am also trying to integrate several apps to the system but I am unable to do so. Is there something preventing me from modifying the system apps with this rom? These are tasks that I have been able to complete in the past.
[Verizon Samsung Galaxy S III] Master Cylinder:
I had these same problems and after effing with it for the last couple of weeks and not throwing my phone against the wall, I figured out a simple solution that worked on mine: I had to deselect "Media" in the Bluetooth settings page for that device - touch the gear. (I could've sworn I tried this before!) Anyway, I had 3 earpieces that worked normally but 2 that didn't but this fixes it.

However, I noticed that /data/misc/bluedroid/bt_config.conf file mis-identified my problem earpieces vs. earlier builds in which they worked and on 12.1. So, Media should work and it will be a problem for someone if they can't play to their car, so this is still a problem. There must've been a change at some point and I'm still interested to track down a solution.

I don't know if you've figured this out yet but you have to move the contents of the TiBu backup folder, as I assume it's on your extSD. Finally found this on the TiBu site:

31. External SD Card problems (This Folder is NOT Writeable)

Since Android 4.4 and above, the SDCard permissions have been changed on how it is granted to an application. A quick way to fix this is by using SDFix application.

There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below). Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder – not to the entire card! In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/

If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/ Lastly, go to the preferences of TitaniumBackup, choose “Backup folder location” and choose the above specified folder.

Of course you gotta replace the card mounted name to the new one for MM. This fixed my problems, which were many. Not sure if this will solve your problem....

EDIT: Actually, TB didn't function at all before I did this.
[Verizon Samsung Galaxy S III] Fenix2002:
So.. Anyone on the 1/19 build that lost all of their QuickTiles in the dropdown shade? All I have is the brightness slider. I can add the tiles back... One at a time... And they're gone again on reboot.
[Verizon Samsung Galaxy S III] yorkwar:
If "Media" is de-selected, what about the sound from app, such as map navigator? That used to go to earpiece too before.
[Verizon Samsung Galaxy S III] Master Cylinder:
What the heck?! Where did they go? And, I can't find anyplace to reactivate them anyway! I have a brightness slider with a dot in the middle under it and that's it. Even Gravity Box, if I select for it to manage Quick Settings, doesn't do anything.

Yep, I don't know but it probably won't work. This is a work around since it's apparently a bit hosed up. Seems that it's not on all earpieces, but just some. When I get a chance I'll dig into it some more. There will need to be a revert it seems to fix it since it worked properly before.

---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------

Hey! If we're flashing nightlies it means we like to live dangerously!:silly:
[Verizon Samsung Galaxy S III] Fenix2002:
Idk what the deal is. If you press and hold on the settings gear with the shade pulled down (like you would've back when UI Tuner was first introduced by AOSP) until it vibrates, it will put you into QuickTile edit mode. You can manually add and arrange each tile that way. Or I could. But it was iffy if it stayed on reboot. :confused:

Cue Kenny Loggins,

"Highway to the Danger Zone

Ride into the Danger Zone!" Lol
[Verizon Samsung Galaxy S III] Fenix2002:
1/21 Build

- Front camera still semi-botched. It works in low light, but freezes in regular use.

- Light sensor not working.

- QuickTiles working again!
[Verizon Samsung Galaxy S III] kmoore11:
I haven't done a dirty flash in a long, long time, but I'm tired of wiping/reinstalling everything. What do y'all usually wipe before a dirty flash? Cache and Dalvik? I need to reinstall system things like gapps and xposed again too, right? Thanks for any help!
[Verizon Samsung Galaxy S III] Fenix2002:
As long as you're "upgrading" the same ROM, like going to a new nightly of CM13, you don't have to wipe anything. You can just dirty flash the new ROM, plus GApps, and whatever else like xposed. You can wipe dalvik/cache if you want, but my experience is that it doesn't matter, the new ROMs wipe that stuff anyway and rebuild it after flashing.
[Verizon Samsung Galaxy S III] kmoore11:
Thanks! I'm in Blacksburg too, I hope you're enjoying the snow!
[Verizon Samsung Galaxy S III] Jaws4God:
actually for an update you dont need to reflash the gapps.. it just over writes system files [emoji1]

Any 1/23 Camera updates?
[Verizon Samsung Galaxy S III] Fenix2002:
How cool! I'm actually about an hour South of the 'burg, now. I'm a Tech alumnus and moved away recently. We got a decent snow, but I'm sure nowhere near what Blacksburg got.. I can't say that I miss winter there. :p Hope you're managing to stay warm.

Awesome, thanks for that info. I couldn't remember, and I typically end up flashing GApps anyway, just to be certain.

As far as camera updates go, it looks to be more of the same. The 1/23 build still has mostly nonfunctional front camera, and no light sensor.
[Verizon Samsung Galaxy S III] Master Cylinder:
Xposed = Yes; GApps = No.
[Verizon Samsung Galaxy S III] AyUaxe:
Has anyone tried restoring backed up data from 12.1 after full wipe and install of 13?
[Verizon Samsung Galaxy S III] XdrummerXboy:
Edit: someone already mentioned it
[Verizon Samsung Galaxy S III] Fenix2002:
Assuming you mean using TiBU? Different people have had different results. Most seem to say TiBU doesn't restore on CM13.. I don't typically go that route, but I tried it once and the app restored perfectly. Idk what the difference is.

The good news is that you don't have to wipe the data partition when going from 12.1 to 13! Just wipe dalvik/cache, unless there's a specific reason you need to wipe it.

I go from 12.1 to the newest CM13 build every few days to test it, and haven't had any issues not wiping data.

Hope this helps!
[Verizon Samsung Galaxy S III] AyUaxe:
I was actually thinking of advanced restoration from nandroid in recovery, but the info you kindly provided probably applies about the same. Could only stay in the lp time warp so long. Back with more after i back up and flash the new nightly. Cheers!
[Verizon Samsung Galaxy S III] Jaws4God:
1/24 version.. front camera had error and closed.. Smart Lock had hard freeze after trusted face captured...
[Verizon Samsung Galaxy S III] Roger W:
Thanks for the tip - deselecting Media for my car stereo allows me to receive phone calls without the phone crashing, but unfortunately this setting doesn't seem to stick - every day or so, I haven't pinned down why, Media becomes checked again. I even turned off the corresponding media setting on the car side to see if that helps (but I haven't done a BT packet capture to see if this actually stops the car from advertising that protocol)

ETA: Hmm, even though Media gets re-checked automatically under the phone's pairing settings, with the car stereo's media setting off it seems to connect in "no media" mode, which is what I want for now until the real problem gets fixed.
[Verizon Samsung Galaxy S III] AyUaxe:
OK, backed up and flashed from last cm 12.1 last night. Just wiped dalvik and cache, flashed nukeit.zip, cm13 1/25, and Delta gapps 6.01 1/20, wiped caches again. Very slow 1st boot, long app upgrade for only 39 apps-usually shows @ 130. Smooth, but slow performance.

Can't get developer options in settings. 7 taps on build date gives something called "demo mode" that doesn't appear to do anything. Can't get pull down quick settings to work at all. Using open camera, main cam takes stills OK, but front cam froze immediately. Had to reboot. Flashed latest dkp kernel, which seems to have improved performance and battery some. Also, can't update SuperSU binary and Kernel Adiutor settings won't hold or re-apply on reboot, though set to apply on boot (was having the issue with volatile Adiutor settings on last LP, too). All in all, these irritations are not too bad for only a month or so into MM development. Thanks to [MENTION=2385005]invisiblek[/MENTION] and the usual suspects for getting us here. Hoping these issues will work out in due time (soon).
[Verizon Samsung Galaxy S III] Fenix2002:
At this point you shouldn't need nukeit. I haven't had any issues when flashing from 12.1 to 13 without it. I think that was at one point necessary between two 13 builds, but not anymore.

First boot on new install usually takes me about 20 minutes to build ~45 apps. It normally shows more for me too, but eh.

First boot can sometimes be weird until things initialize. I've had issues up to 5 mins in. Usually smooths out within 5-10 mins. Reboots sometimes help.

Try clearing the data for settings in the settings>apps section. Then, tap "BUILD NUMBER" 7 times.

If you've been reading posts, nobody is having much luck with the front camera. It'll get worked out eventually, I'm sure. Until then, avoid using it or any apps that use it primarily. Not sure about the quick settings shade not working. That seems odd. Did you enable demo mode when that screen came up?

dkp works wonders. Decimalman's tierservative governor seems to be the most stable for battery and performance.

To get settings to stick, you need to go into developer settings (see above) and turn on root for apps and leave it. That should fix it. I'm not sure why, but that setting seems to overrule other su methods.

Btw, I'm also having issues updating the su binaries, but so far nothing I've had to use has ACTUALLY needed them. TiBU and Superuser warn about it, but nothing seems to actually fail to function without it.

Long post, sorry for that. Hope it helps you out.
[Verizon Samsung Galaxy S III] AyUaxe:
Long=awesome in this instance! Thanks a ton!

Re: front camera, I almost never use it, just tried it out to report on 1/25 build. I know it's been an issue with stock and open camera and sure enough, still is.

Agree totally on tierservative as best governor. Experimented with them all in KK and LP. I also set vmin to 800; over/underclock to 1782/54; I/O-deadline for internal, sio for external, still playing with read ahead values--haven't found a good objective approach to that; O/C gpu to 600--doesn't seem to matter much; entropy--1024/2048; misc-TCP Congestion Algorithm=illinois (have to scroll the list--it's under "yeah"--seems significantly faster, though haven't measured objectively). These are the most significant settings for me and the reason having them not stick is more than a little irritating. More later. Thanks again.
[Verizon Samsung Galaxy S III] Master Cylinder:
You shouldn't be having these problems. Fast and slick is what you should be experiencing! I've always found that when a small number of apps optimize things won't work right till they all do, so pulling the battery might do it but pulling the SIM usually does.

EDIT: Or wipe Dalvik again, but it ain't gonna work right till they all get optimized.
[Verizon Samsung Galaxy S III] Roger W:
You want to multi-tap on Build Number, not Build Date
[Verizon Samsung Galaxy S III] Master Cylinder:
I posted a couple of pages back that TiBu works perfectly but you have to make some adjustments: Post on Fixing TiBu

:good:
[Verizon Samsung Galaxy S III] Fenix2002:
Sorry, must've missed that post or forgotten about it. I just remembered others saying it didn't work. Oddly, I never had to make any changes to anything for it to work. But that may just be a fluke? (Or maybe it's because I don't backup to SD with TiBu, and so I don't have to modify the filepaths?)

Regardless, glad to know it's working now. [emoji106]
[Verizon Samsung Galaxy S III] Master Cylinder:
That's right, it's only about the external SD.
[Verizon Galaxy S 5 General] aznjosh:
I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://xdaforums.com/showthread.php?t=3254434
[Verizon Galaxy S 5 General] MySonsDad:
Where do I find kernels to flash? I am willing to try this.
[Verizon Galaxy S 5 General] fates13:
What you can do for now is try running MobileGo using the kernel you have now. If you're lucky, it'll root. If not, you can read on:

So what I would do first is download the latest version of Odin: http://odindownloadxda.com/Odin3_v3.10.7.zip

Then you'd want to go to this thread for the Odin flashable stock kernels for older versions:

http://xdaforums.com/verizon-galaxy-s5/development/safestrap-odin-safestrap-flashable-t3161043

BEFORE YOU TRY THESE NEXT STEPS: I was unable to find the stock OG5 Odin flashable kernel in these forums. If someone could kindly extract it from the stock OG5 rom and post on here you can begin the next steps. Don't try this before you have the stock OG5 kernel on hand because the older kernels may not let your phone boot up into the rom and the only way to fix it is to either reflash the entire OG5 rom in Odin or to flash the OG5 kernel in Odin. I think you can make the kernel yourself if you have the stock OG5 Odin tar, just extract the boot.img and pack it into a tar.md5 using http://xdaforums.com/showthread.php?t=2446269 Here is a stock OG5 odin flashable kernel I was able to create for you: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU

Once you have the OG5 kernel as a backup, try flashing VZW_BOD5_RETAIL_KERNEL_ONLY.tar.md5 and run MobileGo, if that doesn't work move on to VZW_BOC4_RETAIL_KERNEL_ONLY.tar.md5 then trying the MobileGo and then if that fails try NI2_stock_kernel.tar.md5 since that's the 4.4 kernel that was rootable. However, there's a strong chance that your phone will refuse to boot into the Lollipop rom using a KitKat kernel. All you have to do is flash back the OG5 kernel in Odin 3.10. Once you go through the different kernels from OG5 -> OE1 -> OC4 -> NI2 and the MobileGo program fails to root on any of them, you'll know that this is not a viable root method for the S5.
[Verizon Galaxy S 5 General] MySonsDad:
I couldn't get MobileGo to connect to my phone on OG5. I flashed the OE1 kernel, connected to MobileGo, then used Mobilego's backup feature. After that I noticed that there's a notification reading SECURITY NOTICE Unauthorized actions have been detected. Restart the device to correct them. I tried the MobileGo root and after about 5 minutes it gave me a failure message. Then I tried to proceed to BOC4 but I kept getting failures from Odin. I cannot get back to OG5 kernel either. After a few tries, I now cannot even get into download mode.

The good news is my phone is working. What do I do now? Is this "tripping Knox?"
[Verizon Galaxy S 5 General] fates13:
Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.
[Verizon Galaxy S 5 General] Hariiiii:
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.
[Verizon Galaxy S 5 General] MySonsDad:
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.
[Verizon Galaxy S 5 General] MySonsDad:
I fixed it. I flashed the entire stock image from this thread:

http://xdaforums.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527

I am gonna try again, skipping OE1

---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------

Wait a second. I can't try again until we get a working OG5 kernel

How do I extract that?
[Verizon Galaxy S 5 General] fates13:
Hey, I might have created the flashable kernel incorrectly. Sorry, this is my first time creating flashable odin images. Try this one: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU

You can try flashing that over your OG5 rom right now since it's the OG5 kernel and it won't change anything on your phone even if it does flash.

---------- Post added at 10:03 PM ---------- Previous post was at 09:56 PM ----------

wondershare(dot)(com)/mobile-phone/root-samsung-galaxy-s5(dot)(html)

That guide is from before the OG5 update though. However, my basis for trying this is because it was able to root an S4 5.0.1 rom that was released well after the S5 OG5 rom was released. I was thinking that they would've implemented the same root-fixes into the S4 as the S5 so if the mobilego method worked on the patched S4 rom then it should have a good chance of working on the S5. I would test all this myself but I sold my brother's S5 a couple days ago.