yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
Update on the Chromecasting Test Build

So I have been using the Chromecasting Test Build for a few days now. It still Casts Screen Mirroring just fine though I have had a few issues that I am not sure are caused by the Casting feature but have not been an issue until recently. I have had lock ups that required me to reboot, not Force Closes but so much Lag like the CPU is overworking. One of the noticeable issues I can recreate anytime is that my Google Music isn't able to load any of my songs. They are in the lists of Songs and Artists but will not play. Another issue that I have actually experienced on many ROMs is random rebooting. This only happens when I am Streaming Google Music to my car via Bluetooth 4.1 while wirelessly charging my phone and using Google Maps to navigate me to job sites (Multiple Tasker Profiles are in use here as well)!. Task if you want me to recreate the issues and pull logs let me know. I would like to see this continue to work on future builds and anything I can do to help I will.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't own a chrome cast so you won't be seeing any support from my side.

This is a development thread where issues with the appropriate info should be attached. This is all explained in the FAQ/Q &A thread that is located in the OP. All issues should be posted with logcats considering I don't even own this device. It doesnt really make any sense to post issues without them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A Ham Sandwich:
Did something with the stock Google keyboard change?

If I freeze or uninstall Google Keyboard in TiBu, the capacitive keys stop functioning entirely. Won't even light up.

Never had this happen before the 7.29 release.

But it's not crashing or FC, so will a logcat help?

I apologize if this is not ROM-related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
http://xdaforums.com/showthread.php?p=54240770

not to be....uhhh out of bounds here, but might get more help in Q&A thread(link above and in OP) . and just guessing but would say a logcat would never hurt(for those who can read them, i cant. lol)

good luck.:thumbup:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
I know all about the OP and the FAQ/Q&A. I also know that you don't own this device which is why I left it up to you whether or not you wanted to support it. Based upon your answer and not having a Chromecast on top of not owning this device I won't waste either of our time posting logs. Again I do appreciate you setting up that test build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Google Keyboard is a 3rd party app that can be obtained from the market. Uninstall or reinstall it. It's your choice. Google Keyboard doesn't have anything to do with capacitive lights.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You said you were having reboots dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Hey I've been experiencing something specific only to this ROM.

I just got a different GS3, my first was having tons of hardware issues. I noticed that when I have the USB cord connected, with 7/29, and then turn the phone on, the LCD screen does NOT work at all.

However, if I turn the phone on unplugged, and then plug it in, it doesn't make a difference. But upon getting the new GS3, I flashed the rom and during the bootup the phone's LCD wasn't working. I noticed it was still plugged in, so I unplugged it and rebooted.

Then the screen worked again. So this issue affected 2/2 phones I flashed this on, the touchscreen doesn't work if you boot it up plugged in
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Anyone know where I can find an older version, maybe 4.2 or the newest CWM update.zip for the ATT S3?

I can't plug my phone into the computer anymore due to a faulty port and I was extra stupid and tried installing 4.4 with the old CWM so now it won't turn on...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
okay got everything fixed. When I install 7.29 I just get a boot loop. I tried it several times. I can install CM10.1 no problems. Any time I try for 7.29 no go...I can't even complete a factory wipe without it rebooting once 7.29 is installed.

help appreciated. sorry if I'm just stupid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please usee the Q & A as you question has nothing to do with this ROM or thread. Its really obviously posted in the OP of this thread dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All you have to do is follow the installation instructions. Its what I did when I flashed this released. Works great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BLKNGHT22571:
AWESOME!

I took my wife's S3, because we got her the S5, to use as a backup and test mule. The biggest issue she had was battery life. I installed this ROM with Ktoonsez kernel overclocked to 1.9gHz. I have had the phone turned on running WiFi only (no SIM) and fiddle-farting around with it since 8AM yesterday. It is now 9:50PM, and it still has 24% battery remaining. I am thinking about swapping my SIM to it to see how it does with the AT&T network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Hey task, any idea if the issue I reported as reproducible (happened on both phones I flashed this on) is confirmed or fixable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I really have no clue at the moment. Don't own the device so I can't reproduce it personally. But I remember reading something about offline charging or something in CMs gerrit a few days ago. Not sure if it was for this device or jflte though. When I get some time I'll see if it has anything to do with the issue you're talking about. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iraqmilner:
Awesome! I love this Rom! Does this update, by chance, provide us with lockscreen shortcuts? Man, I miss those babies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Read the changelog that's linked in the OP to see the changes dude. That's what its there for.

Use the Q & A for non-development. That's also in the OP.

Searching prior to posting (a rule here at XDA) would've also answered this for you. No. Lock screen shortcuts are not and will not be a part of this ROM. There's no need considering the many other options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iraqmilner:
Thanks for the um... helpful comment. I was essentially saying thanks, trying to keep this dying thread alive, and more or less giving you the hint that it would be great to see lockscreen shortcuts. Shame. Shame. Too.... dense.... to .....:cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm glad you like it dude.

Download counts rather than thread content on XDA are two totally different things. A ton of people download and install this ROM. ;)

P.S- G+ is where a lot/most of the d2 guys went for this ROM. Link has been in my sig for a while if you wanna check it out. Its pretty cool. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frigers:
Most people that post on this thread these days gets torn to pieces unless they have a logcat attached. I love Task's roms and I'm certain a lot of people still download and use it but it feels like there's little reason to post on this thread anymore, which sucks because I loved when the community was alive and welcoming. Oh well, there's always G+ right? :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I hope this helped you in some way.

There is little reason to post here without a log. I don't own the device anymore so nothing will get fixed without them anyways. There's a dedicated thread for everything else though. Not a big deal. :)

Also. I totally agree with you on the there's always g+. Just take a look at the bug report section. Most all of the contributions come from the d2 device guys. Logs posted all the time no problem. They're the readon why i keep support for this device. It's like pulling teeth here sometimes just to get the community to post info that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriongaby:
Audio stops working when I connect headset

Hello, first of all I've been loving this ROM. It is very fast, battery life is great and I haven't had any problems besides this.

The problem I'm having is that when I connect a headphone/headset/audio line the phone's audio stops working completely. Even after unplugging the cable, the audio doesn't work, no ringtone, no notifications, no media audio and no incall audio either. The only way to get it back working is rebooting.

When I plug in the headphones and audio stops working I can hear a low volume high pitched static like noise.

It doesn't happen always though, sometimes the headphones work and sometimes they don't, but most of the time it doesn't work. There has also been instances where I plug in the headphones, verify that audio is working with PowerAmp, and then when I open a YouTube video it stops working and I hear the static-like noise again.

I have tried the 6.19.2014, 7.29.2014, and the 8.10.2014 releases of this ROM and I have encountered the problem on all of them. I have also tried QuantumKernel-7-25 thinking it might be a kernel problem with no avail. I have also reflashed numerous times, reformatting system, data, cache/dalvik, and even the internal storage.

I went back to UCDLK3 stock ROM to verify if it is a hardware issue but it worked perfectly on stock ROM.

I hope somebody can help me fix this issue because I honestly love this ROM and I do not wish to go back to a TouchWiz based ROM.

Phone Info:

SGH-i747

I747UCDLK3 Bootloader/Baseband

task650's 8.10.2014 build ROM/Kernel

TWRP 2.7.1.0 Recovery​

Logs of when audio doesn't work:

dmesg

kmsg

logcat

Logs of when audio is working:

dmesg

kmsg

logcat

If there's any other info that might be important but I missed, tell me and I will happily provide it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zinnz:
Sounds a lot like a hardware issue.

I have had many different s3's (I kept getting amolded ink blobs really bad, and was constantly switching it with my provider)

The headphone jack on the s3, is not very strong, and I'm willing to bet if you tried another s3 with this Rom, you wouldn't have a problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
My battery lasts all day with this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] distracto:
Thanks for the ROM, been running it for a few days now. When I choose device settings, I get settings has stopped error. Is this a known issue? Running on a galaxy s3 on Rogers using your kernel. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its not an issue. Device settings has been removed. Wipe your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] distracto:
wow fast reply, got in there before i could fix my typo.

i did a clean install from PA, factory reset and such from TWRP. when you say wipe do you mean format the sd card?

to be honest it isnt a huge deal at all, just thought i would bring it to your attention if it indeed was worth reporting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greysonofusa:
NE4 Bootloader?

I went back to stock to see if I was missing out on anything. Nope KitKat skinned touchwiz is even worse than jelly bean. So here I am with the NE4 Bootloader and I want my task650 back ;)

Has anyone flashed this with the NE4 Bootloader?

Forgive me but I searched OP and FAQ and all I could find was DLK3 was the recommended bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greysonofusa:
Bootloader

The I747UCDLK3 bootloader is needed from rom update 5-17 and on.

Instructions for updating to the LK3 BOOTLOADER are HERE

LK3 is not the latest bootloader but it is that one Task calls for.

Bootloader and modem(baseband) are not the same thing.

Use ROOTCHECKERto check what bootloader you are running.

Task has given instructions to Delete the bootloader assert from the updater-script HERE

Messing with bootloader can be dangerous to your phone - MAKE SURE YOU UNDERSTAND WHAT YOU ARE DOING.

So should I flash the rom? Flash rom with caution? or Flash rom with significant risk of bricking my phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It's your phone. You decide what you do wit it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available in the OP. Grab the latest Gapps. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
Got suck on boot animation on newest release 8/24. Wiped twice, still nothing. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Where's the logcat? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
Same here - will try to dump a logcat with cwm and upload
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
And same here. I can't grab logs because it won't boot, have to restore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You can grab a log even if it doesn't boot. Just try, you'll see. Same here posts haven't helped us find the issue yet dude. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Logcat

Uploaded logcat...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Are you having an issue other than what's been reported? Information is a great. Especially if I'm supposed to be looking into something. Thanks. :)

You should head to g+. That's where all the test builds are being released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
That is the same issue few users have reported. Installed newest update, and phone boot animation never goes away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Alright. Old news. I've already gotten quite a few logs and thrown out some test builds on G+ for that stuff already.

Did you check out the log yourself dude? Seems like a waste to have other "developers" post logs with no information, not even a description of the issue until asked for, no help, no nothing? It's kind of the point of XDA. My source is linked in the OP if you'd like to check it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
You seem a little aggressive, I was just posting the logcat for the same issue that users are reporting; I only see people commenting that they are rolling back to previous version, so I though, maybe I can help with the logcat, but her, maybe I was wrong.... You are right, I am a developer, but lately I don't have time to get involved with development, that is why I am using your ROM. Just because I am a developer does not prevent from being a user... I did check the logs before sending them over to you, and it appears related to a native library problem...

Thanks anyway...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Aggressive? Not at all. You're more than welcome to interpret posts as you choose though. That's kind of the fun in the internet I guess. :D

I was just commenting on the fact that you didn't even offer a description of the issue and basically posted a random logcat. That's really weird considering you said you looked at the log and didn't even bother mentioning anything. I mean you did have enough time to grab the log, upload the log, and then post the log. Users give more info than that most of the time so I'm not sure I see your point? Anyways. This is all old news. Thanks anyways though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
So with all that being said, have you looked at the log, determined the issue and posted a new build? OP still says 8.24 but your comment says its old news and already been taken care of. I didn't see a test build in G+ either. I'm not too familiar with G+ and may have over looked it but did not see a post with an update or anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All testing and test builds for this device are at g+. You need to look in you device's section. Everything related to test builds, testing, ect.. are being held over there. That's where I get all the help so that's where I'm going to do deal with any issues.

Fixed the OP for you. As far as this threads concerned the latest release is 8.10.2014 now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
Yeah, I got a Nand backup of that build. If you need me test anything or pull logs let me know. I read on G+ that you had plenty of logs but strapped for time with work and all. I got time today to play around and run test, let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eMadman:
Upgrading got me stuck at the pink boot screen so I reverted back. I'll have to try again tonight. Maybe it needs a clean install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Who knows. Without you posting any type of info (log), there's nothing that can be done for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
LoLoLoLoL Got thrown off by the 8/10 vs 9/10 date. Flashing tonight! Thanks man.

Update...

Full Wipe/Clean Install. CWM v6.0.4.7. ROM MD5 checks good. ROM Flashed successful. Boot Loop... Got an unusual error after flashing and rebooting:

ROM may flash stock recovery on boot. Fix?

THIS CAN NOT BE UNDONE.

I chose Yes - Disable Recovery Flash. Get a boot loop.

Gave them a solid 10 min to boot, just in case the initial boot was just rebuilding the files.

I'll get the logs tomorrow evening...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] raniosman:
Clean flashed latest (aokp_task650_d2lte_kitkat_9.10.2014) and installed GAPPs.

Been 15 minutes now and still circling gears/AOKP unicorn booting screen.

Not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If it's not working then where's the logcat? I can't do anything for you without one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Is there anyone who could tell me how to get a log cat while in recovery. I am using twrp recovery btw so we could help task help us figure out what is going on with the rom. Task it is a great rom btw especially when it works. Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
http://bit.ly/1D8Hhpr
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You don't get a logcat in recovery. If the device is bootlooping and doesn't boot into the OS, you just need to wait for it to loop a little and then run "adb logcat" in terminal just like a normal log is taken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
liltitiz... wow, I haven't used that in a while, still cracks me up. Here are some other links you can reference in case the XDA Search or Google Search or Q&A aren't working.

How to use ADB - http://xdaforums.com/showthread.php?t=2141817

How to Logcat - http://xdaforums.com/showthread.php?t=1726238

How to pull other logs - http://xdaforums.com/showthread.php?t=1520508
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Or an even better idea would be to read the OP of the ROM thread that you are using and click on the important link that has a ton of useful information. It looks something like this...

Then, when you've clicked on that link you can navigate the section that explains exactly how to get a log. That looks like this...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Thanks for the info. I haven't used adb in long time but I'll give it a try. It's nice to learn new things. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conkrete:
Oh Noes!

After flashing ROM my battery caught fire! It's All the DEVS FAULT!

Here is my logcat [IMG="LogCat"]http://karencarpenterdiedforyoursins.files.wordpress.com/2012/11/cat-on-a-log.jpg[/IMG]

All jokes aside, this is working great, thanks for your hard work :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TexasLTE:
:laugh: :laugh: :laugh: LOL .... nice ....... AOKP FTW ! :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
HaHaHaHaHa Sweet, but did you flash another Kernel with the 9/10 build? Everyone else is having an issue with the 9/10 build and its stock Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sublim3_Tilt:
For those who don't know. Task posted on G+ that he is leaving for 18 months so we may not see any further development on this. Maybe another Dev will pickup where he left off. Thanks for all that you've done man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dvazriel:
Dude Logcat or it didn't happen dude [emoji6]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nwbmonkey:
Sorry but that was funny. Btw, I think the 8.10 build is the last stable build. Gonna miss the updates and tasks work. Later homie.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
first jb bootloader question

is the first JB bootloader from mid 2013 (lk3 or lk4) the minimum needed to flash all the roms/updates since then? so basically want to know..if that was flashed back then.. it would have worked for all the roms since then and the 4.3 jb bootloader wouldn't have been needed?

For the life of me...can't figure out which one was on there... trying to fix one of my devices that is bricked.. had been using task for long time and had updated all the way to recent...could it have been done on that FIRST JB bootload...ie 4.1 or 4.2..whatever it was.. or would the 4.3 bootloader have had to been flashed at some point?

this is in the QA OP:

Bootloader

The I747UCDLK3 bootloader is needed from rom update 5-17 and on.

Instructions for updating to the LK3 BOOTLOADER are HERE

LK3 is not the latest bootloader but it is that one Task calls for.

Bootloader and modem(baseband) are not the same thing.

Use ROOTCHECKERto check what bootloader you are running.

Task has given instructions to Delete the bootloader assert from the updater-script HERE

Messing with bootloader can be dangerous to your phone - MAKE SURE YOU UNDERSTAND WHAT YOU ARE DOING.

so is it possible i've been (successfully) flashing all the roms..right up to 4.4.4....on THAT bootloader or is that impossible and the 4.3 had to have been flashed sometime?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Is there any way to carrier unlock the phone on 4.4.4

I know this kinda doesn't have to do with the ROM but I would appreciate a little direction if possible. Or just shoo me away... :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
It's a hard habit to break... Scrolling down to check on Task's thread:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meanhacker:
what is your bootloader version? if you are on 4.1.1 or 4.2.2, here are two links for you (I have yet to do it for my own device):

Guide:

http://xdaforums.com/showthread.php?t=2363882

Stock Rom (recovery flashable):

http://xdaforums.com/showthread.php?t=2363882
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Long time?

So how long should it take for this to boot up...seeing gears for 10 minutes now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Might have to wipe and flash again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxFatiHxX:
Can i ınstall for i9300 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Trafalgar Square:
No, you can't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martiroskg:
So guys i installed as it was written in instructions. and its not going further then logo after i reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mojar7070:
I suggest doing some searching within the thread. Development for this Rom has long been abandoned.

From what I remember you need to be on a certain BL and radio combination since the rom is so old (2014) in addition, on some US models, if you have updated via OTA you cannot unlock BL to downgrade the firmware. Resulting in a boot loop or worse a bricked devices. Use caution.

This was one The best SGS3 Rom in its day. Used it for a long time when I had the device. However, like all phones these days, it became obsolete because of new technology.

Anyways.... Good luck.