yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] vvMINOvv:
plz help, I'm getting a status 7

model: SGH-T999V

Android Version 4.3

Rom: root66_GLW_T999VVLUEMK5 (from mr. Robinson)

Kernel version: 3.0.31-KT747-g7121b3d (from ktoonsez)

Baseband version: T999VVLUEMK5 (from DocHoliday77)

Build number: JSS15J.T999VVLUEMK5

Recovery: CWM touch 6.0.4.5 d2tmo

Carrier: Wind

I tried installing CM10.0, CM10.1, CM10.2 none of which worked. All give the same error

assert failed (getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo")

Following some shady advice given to someone else on here somewhere, I commented that out, and tried installing it. Still failed, only no identifying error at all really, something along the lines of

Aborting installation

I also realized in that same file with the assert:

assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");

and running

getprop ro.bootloader

yields T999VVLUEMK5 ....so doing what any, insane person would do lol...I commented that out too. Still no cigar!

I tried CM One click installer, worked all the way through. The windows side of the installer even said it's finished successfully. The phone side looked perfect, then on the restart I saw the stupid Samsung splash, and don't you know it, it friggin boots into stock...sigh

Aaaaaany help would be incredibly appreciated. I'm a programmer, heavy linux user, and not afraid of terminal so even if it seems farfetched, just let me know please.
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
What recovery are you using?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Just use Odin to flash twrp d2tmo 2.6.3.1
[T-Mobile, Samsung Galaxy SIII] mondokat:
so, nightly 20140119 has this change for bluetooth:

http://review.cyanogenmod.org/#/c/57825/

Which seems to have fixed my random disconnect issue, at least on first impression. I need to run it through the paces a bit more. However, there is a change saying "update bluetooth to latest source drop", in the 20140120 nightly, so I am hesitant to update. Anybody having any luck with these recent builds?

That second merge is here:

http://review.cyanogenmod.org/#/c/57406/
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
You can use the goo.im app to flash it right from the device. Faster then using odin
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
I'm on 1 19 and it connects and disconnects properly, no issues.
[T-Mobile, Samsung Galaxy SIII] vvMINOvv:
Thank's I just added that to the list (totally forgot it)

I'm currently using CWM touch 6.0.4.5 d2tmo

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

Any reason you suggested TWRP? I'm running the latest CWM touch 6.0.4.5 d2tmo
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Personally I like TWRP better due to it having more options (fix permissions, simpler delete, can flash multiple files) but I rarely use CWM anymore because I like the TWRP interface better.

Try dropping down to CWM 6.0.4.3 (if it's compatible with KK roms) or upgrading to TWRP 2.6.3.0 and see if that works for you.
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
CM 1/19 nightly is the first 4.4.2 build I've flashed in a month or so that I have had no issues using in my '13 Focus with SYNC and my JamBox. I'm gonna test my Motorola BT S305 headphones later tonight, but I don't expect any issues. Hopefully the Bluetooth "mess" is behind us. Also, I'm running the stock CM kernel. The only issue I've had with 1/19 is that upon every other or every third reboot, I lose the data connection and have to reboot again to restore data. MJC baseband.
[T-Mobile, Samsung Galaxy SIII] silverton:
So today I thought I'd play with the bluetooth. After connecting it to a speaker set up, and unpairing and turning it off, I had some epic battery drain. ~50% in an hour. A reboot didn't exactly fix it either. Went from 23-16 in about 25 minutes.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
There's a new Bluetooth experimental build on the downloads page for 0121 for anyone wanting to give that a try
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
I'm not having crazy battery drain, but it is significantly more than before. I am pretty light use through the day, and usually have about 40% by 5pm. It's not quite 7 and I'm down to 10% now.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Lots of changes in the 20140121 build. Anybody try it yet?
[T-Mobile, Samsung Galaxy SIII] :
Downloading it now.
[T-Mobile, Samsung Galaxy SIII] mondokat:
i'm super happy bluetooth started working again on the 20140120 build, so when i see 7 bluetooth related commits in the next build and another queued up for the next build, i'm a little weary of trying it out just yet. It does seem like my battery is worse on this build though, so if there's fixes for that stuff, i'm itching for a fix.
[T-Mobile, Samsung Galaxy SIII] :
I haven't had a chance to try the build in my car yet, but I tried to connect my phone to my Mac via bluetooth. As soon as I turned on Bluetooth, I got the error message "Bluetooth Share has stopped working". Now, before somebody says it's a problem with the nightly build: I use a 3rd party kernel (dkp) and noticed that decimalman put out a new build today because of CM's kernel merges. Updated to the new dkp kernel. Good news: bluetooth no longer crashes. Bad news is that, while I can pair my phone to my Mac, I can't seem to send files.

It could also be user error as well. :p

I will let you know later on how the bluetooth with my car goes.
[T-Mobile, Samsung Galaxy SIII] :
Well, after testing the 1/22 build, it appears something broke in the bluetooth again. It seems like my phone was behaving the same way before the 1/20 build. Also, it seems that battery life is degraded somewhat using the new build. So, I'm going back to the 1/20 build since everything for me was working perfectly.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Yeah. I upgraded from 20140120 to 20140123 and the random bluetooth disconnects came back. So lame. I reverted to 20140120 as well.
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
I too had my bluetooth issues return on the 012214 nightly. I restored back to 1 19 and am working properly again.
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
I can't get on-screen navigation buttons to show up with the build.prop edit.
[T-Mobile, Samsung Galaxy SIII] omarvel0us:
How stable is cm11 other than Bluetooth problems? How's battery life,data,calls,texts, any reboots?
[T-Mobile, Samsung Galaxy SIII] silverton:
I daily drive it. I get the occasional reboot, like once a week maybe. the last one was a couple days ago while scrolling through my Facebook feed.
[T-Mobile, Samsung Galaxy SIII] omarvel0us:
Alright thanks for the info.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
100% rock solid. I have been running it since 1223, delta updating when I feel like it.

No random reboots. Great battery with dkp kernel. Only issue is Bluetooth (and that's semi random, it works fine for me 75% of the time).
[T-Mobile, Samsung Galaxy SIII] jxordan:
Does anyone know if the front facing camera is working correctly in snapchat yet?
[T-Mobile, Samsung Galaxy SIII] eugenile:
What kind of batt life you getting with that dkp kernal
[T-Mobile, Samsung Galaxy SIII] PrimeNemesis:
Glide

Is anyone having issues using Glide?

I haven't been able to use it in weeks. I'll get on and it won't record. It will let me send text messages, but no video. If I hit the center camera button or the button to the left, it becomes completely unresponsive. The only way to get anything done is to quit out the entire program.

Suggestions?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
3-4 hours combined screen/calls, 6 hours streaming music on h+, 18-20 hours total. Not undervolted or tweaked for battery.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
The front camera has had problems since jellybean with 3rd party apps. Gotta stick with crapwhiz for front camera compatibility without issue.

I've never worried about the front camera. I don't use instagram, never have had a reason to use snapchat. My sexts are sent normal so I can enjoy them over and over again. Snapchat defeats the purpose of everything IMO
[T-Mobile, Samsung Galaxy SIII] :
So...73 commits on last night's build. :eek:

Has anybody given it a try yet?
[T-Mobile, Samsung Galaxy SIII] niphoet:
I tried downloading it but kept getting a 36mb file so I didn't flash it.
[T-Mobile, Samsung Galaxy SIII] yanikd:
No issues here.
[T-Mobile, Samsung Galaxy SIII] :
Have you tried bluetooth?
[T-Mobile, Samsung Galaxy SIII] yanikd:
No. I don't have any Bluetooth accessories.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I flashed it with cyandelta and have had no issues with it. Smooth as always. Don't have a bluetooth device so cant test it
[T-Mobile, Samsung Galaxy SIII] PrimeNemesis:
Static

Whatever issues that creeped in between the 20 Jan Nightly and today's 29 Jan Nightly is gone for me.

However, I get intermittent static and it's not always automatically connecting to my earpiece.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
and there's still no way to have a seperate lock screen wallpaper?
[T-Mobile, Samsung Galaxy SIII] crespi_:
Pretty sure you can easily do this using xposed framework and gravity box/xblast other modules like that.

Do you already use xposed for greenify? If so, just download the gravity box module, it's super easy and very useful.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Thanks for the reply... I would actually prefer not to install xposed or anything that really modifies the system besides CM11.. I like to keep it minimal. If the feature never returns to CM, I'll live..

I have another question though. Can someone explain why the latest nightly replaced a good launcher (Launcher3) with an inferior one (Trebuchet) that doesn't allow grid customization?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
I assume because launcher3 is AOSP while trebuchet is CM. I imagine CM devs are working on feature patches for trebuchet to make them equal. In the mean time, you can extract the launcher3 apk from a previous nightly, push it to /system/app, set permissions, and reboot.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
That makes sense. Thanks for the advice but like I said I really don't feel like messing with the default configuration. I'll just adapt to having 12 icons on my home screen instead of 16, until they return the feature at least.
[T-Mobile, Samsung Galaxy SIII] Muffycheeks:
Is Bluetooth operating properly with the latest nightly?
[T-Mobile, Samsung Galaxy SIII] heybobitsme:
Since it hasn't been mentioned in a while, Instagram video is still borked, at least for me anyway. It records video just fine but the app crashes at the "choose cover frame" bit. I talked to a guy on G+ yesterday who says it's working on his d2att, but at this point I'm not sure I believe him. I've done everything I can think of from an end user standpoint to get this to work - clean flashed, cleared app data, removed folders, etc. Is this working for anyone? I'm on latest nightly 20140201.
[T-Mobile, Samsung Galaxy SIII] PrimeNemesis:
BT still needs some work. Static and connecting are my biggest issues.
[T-Mobile, Samsung Galaxy SIII] eugenile:
I think that guy is bluffing unless the d2att specifically works. Everytime I update I ALWAYS do clean install.. And never even the latest nightly does instagram vid work. It will record but crash when you submit it/pick cover. It won't even upload prerecorded edited vid. Same will crash
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Ive had a few BT related hard lockups on 1/30. Complete freeze requiring a battery pull.

Awesome when you have an otterbox and need phone GPS. Oh well, beta is beta. No case when I'm driving for now.
[T-Mobile, Samsung Galaxy SIII] Muffycheeks:
I guess I'll stick with 1/20 nightly until.......?
[T-Mobile, Samsung Galaxy SIII] kingston73:
Can't you use volume/power/home button to reboot? Unless you have a new kind of freeze that's always worked for me.
[T-Mobile, Samsung Galaxy SIII] crespi_:
Both of you... You're flashing CUSTOM NIGHTLY ROMs.

N I G H T L Y

I

G

H

T

L

Y

What you may want to look for is a..

S T A B L E

T

A

B

L

E

rom.

Just a thought.

( ͡° ͜ʖ ͡°)
[T-Mobile, Samsung Galaxy SIII] Six6Sicks:
Tried a dirty flash from 2/1 to 2/2 because my wifi just stopped working on 2/1.

2/2 just locked up.

Then tried a complete 100% wipe/clean install of 2/2.......

and it locked up again.

Back to 2/1 again? I dunno.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Same here...
[T-Mobile, Samsung Galaxy SIII] ami2510:
Just tried flashing 2/2, looks like there is a launcher and trebuchet launcher now. Choosing any of those will freeze the GS3.

I had to flash back to 1/29
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Same here, flashed back to 1/31 with no issues.

Sent from my SGH-T999L via Planet Express.
[T-Mobile, Samsung Galaxy SIII] snipinu:
02/02/2014 Nightly is messed up locks up on startup and no response on the touch screen even after a complete wipe and reset. Random reboots etc are evident I recommend do NOT Flash
[T-Mobile, Samsung Galaxy SIII] ami2510:
OK I just flashed 2/3 and it works now, without freezing.

Everyone skip 2/2 and use 2/3. Now we can change launcher stuff in the settings and the phone will not freeze anymore.
[T-Mobile, Samsung Galaxy SIII] snipinu:
Ne1 know what caused it? It completely borkd
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I'm going to guess "API 1.1", because it was implemented in 2/02 and reverted in 2/03.

Sent from my SGH-T999L via Planet Express.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Is Bluetooth working for anyone on 2/3? I can pair but not connect. Even re-pairing doesn't establish a connection. Updated via cyan delta.
[T-Mobile, Samsung Galaxy SIII] crespi_:
I must be lucky to not ever have to worry about blue tooth. never owned a single blue tooth device.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Not even a laptop?
[T-Mobile, Samsung Galaxy SIII] ami2510:
My Bluetooth on my car works great!
[T-Mobile, Samsung Galaxy SIII] crespi_:
lol. I mean a device that I've found a practical use for. I have it on my sgs 3 of course. but I have never found myself needing to use blue tooth on it ever. in fact I use my own gapps package that removes nfc and blue tooth just because I never need them. am I weird? ( ͡° ͜ʖ ͡°)
[T-Mobile, Samsung Galaxy SIII] PhrostB:
Yes! :D
[T-Mobile, Samsung Galaxy SIII] omarvel0us:
I never use Bluetooth either lol
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Well for anyone who does use Bluetooth, it's fixed on 2/4. Auto connect, manual connect, and a2dp streaming work as expected. Haven't tried a call yet.
[T-Mobile, Samsung Galaxy SIII] :
Good news is that bluetooth seems to be connecting no problems. Bad news - my phone still won't wake up when I tell my car or my xlink to make a call. I have to wake the phone first before it will call.

I also noticed that there's both a Dialer and a Phone app. Bluetooth will activate one (I'm assuming the Dialer app) but when I press phone, I get a completely different app.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Update: Bluetooth autoconnect worked for me when toggled in inside the car. Meaning car BT on first, then phone BT on, they find each other and connect.

If the phone BT is on first, then I get in the car and turn car BT on, the devices will not auto connect. Additionally, at some point while driving, the phone BT toggled itself, requiring me to manually connect again. This did not happen on my way to work, when I turned the phone BT on after getting in the car.

In short, toggle Bluetooth on after turning on your accessories if you want auto connect to work.

[MENTION=4900821]Bass_Man25[/MENTION]: you should clean flash. I have only one dialer app, the one that opens when I click the phone icon in the app drawer. In TiBu there is a "phone" entry (which is voicemail settings backup) and a "dialer" entry (the actual "Phone" app).

As for not waking to dial out, what kernel are you using? Other possible explanation, have you messed with app ops, permissions manager, or frozen/removed any system apps in titanium?
[T-Mobile, Samsung Galaxy SIII] :
Adreaver, I clean flashed (wipe data/cache/dalvik, format system, install ROM, wipe cache/dalvik again, reboot) only the ROM as delivered and paired the device - no GAAPS; no custom kernel. I can get the autoconnect to work beautifully. If the phone is awake and I try to make a call from my xlink, then the phone dials out no problem. Once the phone is in deep sleep with the screen off, if I try to do the same thing again, the phone will not wake up to make the call. I even turned the lockscreen setting to no locking and still the phone won't wake up.

--EDIT-- Since I'm new to CM, I'm wondering if I'm missing a setting? I've been searching for an answer and some threads talk about some setting to allow calls when the phone is locked. Does anybody know if CM has such a setting?
[T-Mobile, Samsung Galaxy SIII] silverton:
I've noticed over the last week, that if I take a picture. I mostly notice it inside the SMS app, that I get increased battery drain until I reboot the device. Basically take how quickly your phone charges... cut that in to 2/3 and that's the kind of drain I'm talking about. Essentially 1% a minute and the phone gets HOT. The other morning I woke up and the battery info said "overheat" and it was showing 50*C, which comes out to 122*F. Scared me because I've seen the articles about the S4 fires...

Anyone else notice? I've recently formatted the system partition so that it was a clean'ish install, but it's been an age and a half since doing a completely clean install.
[T-Mobile, Samsung Galaxy SIII] :
Well, the good news is Bluetooth works perfectly now in the latest nightly. The bad news is that it's got some pretty wicked wakelocks for "Bluesleep" and "msm_serial_hs_dma" - they seem to stay on for as long as I have BT on so my phone never goes to deep sleep. So, it looks like CM is going in the right direction.
[T-Mobile, Samsung Galaxy SIII] crespi_:
Do you use better battery stats?

Just going off my own personal experience, but a couple of things that could cause this:

1) Media scanner service going rogue and not stopping when it needs to.

2) faulty SD card or something gone wrong with how your system reads it

So, if you were to change check out better battery stats, you'd see something like mmc1 detect, or indexing service or media scanner etc.

Really there is no easy way to drill down what it is with out using better battery stats or some sort of monitor. I guess that while you experience this issue, you could go into your running services/apps and see if there is anything running that shouldn't be. But for sure, SD card problems, media scanner / gallery related things can definitely cause huge drains and heat if they go rogue.
[T-Mobile, Samsung Galaxy SIII] silverton:
I'm mostly interested in knowing if anyone else is having problems. If not then it's time to start from scratch. I do not have BBS though, I think it's a paid app and I'm a cheap bloke!
[T-Mobile, Samsung Galaxy SIII] crespi_:
http://xdaforums.com/showthread.php?t=1179809
[T-Mobile, Samsung Galaxy SIII] skewty:
Any camera issues experienced?

Anyone experiencing any camera issues in the nightly builds?

Some I have experienced on the Jan-20 build:

Doesn't focus well (macro mode)

View finder is too dark

Locks up (needs to reboot or phone eats through battery)
[T-Mobile, Samsung Galaxy SIII] silverton:
Thanks!

This is what I was talking about! I don't have the focus or view issues. But it will lock up if I'm trying to take a picture in a SMS and I hit the "retry" button. Or when I'm in the actual camera app and when I switch from camera to camcorder, when I go to switch back to camera.

---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------

After installing BBS, and doing what it takes for the camera to crash and battery to drain fast. "msm_camera" keeps the kernel in a wakelock
[T-Mobile, Samsung Galaxy SIII] crespi_:
Well, there ya have it. You should be able to find out what to do about that now. Glad I could help. :)
[T-Mobile, Samsung Galaxy SIII] skewty:
Well, there ya have it

And what is that?

Uninstall CM and install a TW ROM? (CM isn't interested in bug reports on the nightlies last I heard.)
[T-Mobile, Samsung Galaxy SIII] crespi_:
Not to come off as rude, but I recommend just doing some quick research/googling. Use specific keywords and try to find xda and other appropriate forums for help threads regarding similar issues. This is kind of the frustrating fun part of running nightlies in.

You seem so quick to jump ship on cm11 just because your current nightly has a [mostly] minor issue. If this makes in unsuitable for your daily driver, then indeed you should try a new nightly. There are numbers of people who generally report that a certain nightly is more or less stable for them as a daily.

But this isn't really what this thread is for, and that's why I [politely] suggest just doing some quick googling and seeing what you can come up with. Try some new things, take some risks. You're running nightlies what's the worst that could happen. ( ͡° ͜ʖ ͡°)
[T-Mobile, Samsung Galaxy SIII] silverton:
My 5 minutes of googling concluded in trying a different kernel. Which I have not. I take pictures so rarely lately that it doesn't bother me to reboot the device after taking one.
[T-Mobile, Samsung Galaxy SIII] km00000:
My friend has a At&t version of the GS3. A SGH-I747. Should he install d2tmo or d2att?
[T-Mobile, Samsung Galaxy SIII] kingston73:
Seems pretty straight forward, the ATT version gets the d2ATT rom, right?
[T-Mobile, Samsung Galaxy SIII] :
Latest CM11 Nightly for d2tmo has a couple of RIL fixes in it. This seems to have fixed the "Bluesleep" and "msm_serial_hs_dma" wakelock issue.
[T-Mobile, Samsung Galaxy SIII] :
Quick question about the CM11 nightly releases: if I decide to skip a nightly release or two and see that a later release has some fixes I want to get, can I just download that nightly or do I need to download all of the other nightly releases in between?

Thanks.
[T-Mobile, Samsung Galaxy SIII] dzasta:
Yes. All releases include all the prior fixes. All of the monthlys and RC's etc are the same as well.
[T-Mobile, Samsung Galaxy SIII] pgarcia777:
Anyone know the features that come with cm 10.2.1 statable ?
[T-Mobile, Samsung Galaxy SIII] mondokat:
Just the latest...
[T-Mobile, Samsung Galaxy SIII] omarvel0us:
Is there a fix for snapchat front camera out there? Its really choppy on cm11
[T-Mobile, Samsung Galaxy SIII] Adreaver:
I highly recommend CyanDelta for everyone wondering about nightly updates. It detects the build you are on, and shows the ENTIRE changelog between your build and the current nightly. Also, it downloads most nightly updates at less than 20MB, and just patches your previous zip.

Most days, I am able to wake up, start the update, go to the bathroom, and come back to the new nightly. About another 30 seconds to re-enable Xposed, change dpi with ROM toolbox, and reboot. Hasn't failed me yet *knocks on wood*.

Also, the old version of the zip isn't deleted until you choose to do so; if you have issues immediately after updating you can easily roll back to your previous nightly.
[T-Mobile, Samsung Galaxy SIII] silverton:
So I spent about a week on CM10.2 cause the camera wakelock was driving me bonkers. Came back completely fresh, and unfortunately the camera issue is still there. But it only seems to happen when I take a picture INSIDE an SMS. Slightly annoying but not a deal breaker.

Another thing happened yesterday. I had sent a text message, no problem, took a shower and when I came back my touchscreen was unresponsive. Menu, back, and home still worked, but nothing from the screen. Had to do a battery pull. Didn't think to pull a log either so... wheird!!
[T-Mobile, Samsung Galaxy SIII] crespi_:
You went back to a stable release, it worked fine, and now you're on nightlies again and things are more buggy? Wow that is weird, totally not what one would expect. ( ͡° ͜ʖ ͡°) Obligatory whore post for increased post count.