yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fendulon:
So I am having a sort of strange issue with signals. It appears to be on all AOSP ROMs. So far I've had it happen on this ROM and JellyBAM (I know it isn't supported on this site). But now that I've had it happen on Task's AOKP it seems a little more relevant.

I always do a completely clean flash, and I have the newest bootloader.

Whenever I travel a decent amount of miles away I lose all internet connection. For instance, I live in Adrian, MI, and I will travel about 35 miles away to Ann Arbor, I no longer have any internet at all. I cycle airplane mode multiple times, I reboot multiple times. Internet REFUSES to come back. As soon as I start coming back to Adrian, MI, my internet connection eventually kicks back in.

I also experienced this again on vacation. I flash this ROM, the 5/17 version, while I was in Myrtle Beach, SC. Everything worked beautifully. Then I took the plain home to Michigan, landed.... no internet. Did all sorts of airplane mode and restarting and internet will not work.

Both times if I simply restore a TouhWizz backup internet works perfectly.

It is like the phone is having trouble switching to new sets of towers.... I have roaming and International Roaming enabled if that makes a difference.

Any clue what's up with this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
-- nice story, bro

Check your APN settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fendulon:
I don't see any issues with my APN settings. They are set up in the same fashion that any other ROM on any other phone has been.

Unless I'm missing something? Not sure why by default anything would need to be changed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
I dunno about anyone else but I don't seem to have connection to the Google servers so i cant use hangouts.... any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Works just fine. Just got off of a hangout a few minutes ago. Also. This ROM has no control of googles servers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
I Didn't have any issues connecting to the servers before I updated to latest. came from 5/17, I also couldn't use hangouts on that build. Kept having to uninstall and go back to talk. I'll try a reflash to see if it fixes it.

Edit: Did a reflash still no connection to the servers. This is both over wifi and Att network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
How do I install the latest JB boot loaders ? Getting error due to that.. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
Ok so I don't know what Is up. I can access everything but hangouts on my device. Im still grey in the notification bar. I have no clue as to why I can't connect to the servers now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Follow the instructions I've given. Is there any particular reason that you've decided not to read the OP of the ROM thread and all the posts here about it? The directions are even posted twice in the OP. You can't miss them. I'm quite unsure what the problem here is. I've made it very simple for you guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't know what is up either. Working fine on my end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
Flashed back to 5/17 build with older gapps and have no issues now. If I go to the latest update I lose my connection with the google servers. It's very odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Stay on whatever release works for you. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] j_r17ca:
Hey task any option for for group contacts for sms? I mean where i just have to check the contacts that i want to send sms to not just typing each name. Cant find it on the sms settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
OK so if I use the old gapps with your latest release all works. Any idea why your new gapps release would be disagreeing and not allowing my device to connect to the Google servers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm pretty sure I've already stated this a few times now. No I don't have any idea. Works fine for me. Use what works for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
I'm just trying to sort this out. There has to be an issue with those Google apps if I can connect with one release the 5/8 gapps release, and not the latest. It just doesn't make any sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm not going to change the gapps package. So it seems to me that it would make sense for you to use whatever works for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
Dang. OK just bringing it to your attention good sir. Just on the fat chance someone else has the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Great ROM - Message for i747M users

For any Canadian users I have flashed the latest ROM 05/21 on my phone and it seems to work perfectly on my Telus S3. Your experience may differ. Also, Canadian users need to realize from my own read of many of the messages here and the the post in development that Task doesn't support a device that he doesn't own and this ROM is provided on an use at your own risk basis with your own knowledge and a google search as your best support. Therefore we Canadians are using it at our own risk even though it should work. Please keep that in mind when flashing this or any ROM.

Task...I know this is not a Q&A and I apologize for the post, but I did see a couple of posts in the dev thread about Canadian users and thought I would post my experience here in an attempt to answer that. I looked and never saw where anyone else had done so. If I am wrong someone just needs to tell me and I will remove this post. Thanks again for the hard work. My phone seems even snappier after the latest build and I really didn't think that was possible...:).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
A fix I found for other devices was to uninstall Google Play Services, then reinstall it. Hangouts will ask you to update it per usual so do it. Once it's installed try opening Hangouts again and it might give you the same error once or twice, but eventually it will go through. Worked for me, hope it helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
Thanks I'll give that a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
Task, I take it Hangouts outgoing audio is working for you as well? I've searched a few different threads and can't seem to find a solution, but if your mic is working than that's a good sign.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chdrummerdude:
Boland that worked! Thanks for the info

I used titanium backup to uninstall the Google play services. Then just Google searched Google play services in the browser. Use the first link to the app store. Finally all updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
Glad to hear it! Now if we can just figure out this mic routing issue with Hangouts and CM/AOKP ROMs...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task if I already updated the bootloader on 5/17 do I need to update it again for 5/21 or no?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Think about it a little.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I am going to say yes I guess :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Wow. This ROM doesn't touch bootloaders. It never has and never will. That's why I had to have you guys flash them separately. So if you flashed them once I don't see why you would ever have to flash them again. You shouldn't play around with bootloaders if you don't have to and t's always best to do research on these types of things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Got it thanks for the info, I was aware about the bootloader not being part of the ROM, I just thought because you repeated the same link in the new update that we had to update the bootloader once again but now that you cleared it out for me it makes sense thanks ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There are a ton of people who decide that they are too good to read changelogs and OPs so I have to keep information like that marked on a few releases so that they will see it and not clog up my thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddiehl:
As far as updating to the new bootloader, was it determined that the file name needs to be re-named to exclude the .md5 extension or flash as is?

Getting ready to give this a shot..

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Go read the directions that Ive given in two places of my OP. Follow them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Task from a developer perspective what do you think about this new Google Edition S4? The reason I am getting an S4 soon is because you are going to support it and not to mention that Dan Rosenberg has the hack to unlock the bootloader to the AT&T version of the S4 which is awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merpius:
Bootloader in Linux

Has anyone identified a way to flash the new bootloader in Linux? It appears that heimdall still doesn't support the S3 (unless I'm missing something), and, of course, mobile Odin won't work for bootloaders (or so I've been told).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This has absolutely nothing to do with this ROM.

2.) Start a thread in the Q & A Forums if you would like support for this question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It's the same phone. This is an sgs3 thread. Please stay on topic which is support for this ROM. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JeRrYFaR:
Unless things changed, I thought task wasn't gonna support it because they pulled an Apple.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAR7MAN:
Okay so I'm having a bit of a problem and was looking for some assistance. I clean flashed the 5/21 build and 5/21 gapps with no problems, until I rebooted. I keep getting the "System UI Has Stopped Working" error. I tried clean flashing a couple times and all is good up until I reboot...then this error keeps coming up. It happened on the 5/17 build as well....exact same thing.

I wipe cache/dalvik, fully wipe, and format system every time before flashing.

Is this a common problem? Or is there something I can do to prevent it?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickod:
new build

Hi,

I use this rom since i get a S3! so yeah i love the work on this !

i update over and over, sometime (or if i see a bug) I do a fuuulll Savage wipe :)

so now we need to update bootloader with odin etc etc... (no problem)

i got a 747M so Canadian package, flash with odin all was perfect reboot in recovery

i use TWRP 2.5.0.0 ( I'ts ok) ? before i used CWM

easy like usual.. download the lastes rom and gapps and kernel but I got an error with the rom and i have read that a guy on the forum as confirmed the canadian package Work and he have the new rom so if you got an idea why i get this error?: (i have downloaded the rom many time)

checking for md5 file...

skipping md5 cuz no md5 found ( it's cool)

assert failed: getprop("ro.product.device") == "

E:Error executing updater binary in zip /sdcard/blahblah to AOKP 4.2.2 Jellybean 5.21.2013

i have missed something?

Thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
You missed that this rom only supports AT&T :) any thing else is hit or miss, and there is no support for the "miss"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickod:
i see.........

---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------

So i'm now able to flash the new build... Just use CWM and the update pass like usual!

no comment lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
[MENTION=2928662]task650[/MENTION], I know this is off topic but thanks for opening you developers thread again. Maybe it will stay on track!

SGH-I747 underwear kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It won't stay on track. It's a never ending cycle. But I can definitely try and slow down the bs. ;)

P.S- I spoke too soon. The children want to whine about things that they have nothing to do with. I'll open it again at a later time. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merpius:
I think #1 is debatable, but I won't debate it. Instead I followed your advice. However, instead of seeking support, I made a HOWTO for this: [HOWTO] Flash the new bootloader in Linux

Posting here so that, when people search it, this thread isn't a dead end, but, instead, a path to upgrading to the latest task AKOP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not sure how you think its debatable? Heimdall and/or how to use it has nothing to do with this ROM. There is nothing in this ROM that would have any effect on Heimdall working or not working on your computer. It has dependencies that YOU need to setup correctly on YOUR computer for it to work properly. This ROM has nothing to do with your computer either. So in turn. Not really debatable. ;)

P.S- I use heimdall just fine. Always have. I don't have access to any computers running windows so heimdall is necessary for me. Also added something to your thread that might be important. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunnersluver:
"YOU MUST BE USING THE LATEST JB BOOTLOADERS TO FLASH THIS RELEASE!!!

Click this link 1ST!!!"

Is it necessary to do that if I'm coming from stock 4.1.1 AT&T?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
How much searching have you done? Have you even tried to flash the ROM yet? Try to flash it and see if it works first dude. If you're not on the latest bootloader the ROM will not flash. There is a ton of info on this already here in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
USB not getting recognized

hey guys

so im having trouble having my laptop recognize my phone. im on build 5-09-13

i have developer option off and the phone is still not being recognized.

windows keeps saying "usb device not recognized" everytime i plug in my phone.

any help is appreciated :) thanks in advance

i have also provided a log cat if it helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Do you have the drivers for the phone installed on the laptop? Also, this doesn't really pertain to the ROM. This is a very basic thing most people start with when getting a new phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
i have had this phone since the came out. i do have the drivers

and the reason im posting here is becasue it started to happen after i put this build on it.

but ill check for the drivers again thanks

---------- Post added at 03:20 PM ---------- Previous post was at 03:11 PM ----------

just checked my drivers....uninstalled them and reinstalled it....same situation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Then different computer, different cable, restore your nandroid backup and try that. Or redownload, full wipe, reinstall, and don't load anything but gapps. It's definitely NOT the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I'm unable to update Play music. I get the error message: "Package file not signed correctly. Uninstall the previous copy of the app and try again." I searched and found this:

"Package file was not installed correctly" error

If you receive the "Package file was not signed correctly" error, this is because your device is not on a user build. If your device is on a "userdebug" build with "test-keys" in the build description, the Google Play Music update will not be able to be installed from Google Play at this time.

Normally I'd just say eff it but I can't do the All Access trial on the version from Gapps package. Anyone know any workarounds?

Edit: Forgot to mention I tried uninstalling with TiBu. Installing from scratch says the package is not compatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Take it out of the Gapps package. Instructions are around here somewhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Forgot to mention I unistalled with TiBu, but wasn't able to install. Same thing as taking out of the gapps package right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
after installing latest build and latest gapps, I don't have a mic on the keyboard. So I installed voice search from play store, and still nothing. Any help on getting the microphone on the keyboard?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Search. Easy fix somewhere in here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
didn't help installing google serch, or voice search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
How about thoroughly going through phone settings... it's there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pssnn:
System settings-language &input, make sure Google voice is checked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
it doesnt stick after I choose it in settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miraclestone:
Is it normal to feel like hanging myself after reading both the Dev and Q/A threads?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
Nice spoonfeeding.

Fix permissions. Doesn't work after reboot? Full wipe.

You're not the only one dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Av.:
First off all love the rom, been using since i got my phone. I updated to the 5/21 build and its running amazing, aside from not being able to connect to 4g.

Under Mobile Networks I have LTE/GSM/WCDMA as the preffered network, but no dice. Forgive me if this has already been covered, typing this from my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Where you are typing from has no bearing - that's a computer in your hand, and it has a browser and Google works just fine. Just use XDA as one of the search terms.

4G works fine, BTW. And this phone doesn't lie like the carrier ROMs and call it "4G" when it's not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
fixing permissions didnt work, onto full wipe again. After full flash it only works on symbols keyboard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Av.:
nevermind. phone just picked up 4g out of no where. Carry on and keep up the amazing work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miraclestone:
This is Q/A right? OK, I might have special feelings for her. Do I have a chance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
If my baseband currently says that it is I747UCDLK3, does this mean i do not need to flash the bootloader first? (I'm sure it wouldnt hurt to just do it anyways, but figured id ask.) Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
It means you have the LK3 modem/radio, but doesn't mean you have the most up to date bootloader. If you've been on a stock 4.1+ rom before, then you have the up to date bootloader. Just follow the OP, if you get an error when you try to flash, then you need the new bootloader.

Sent from my SGSIII on Task's AOKP

Try a new Task650 AOKP boot animation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qbnb:
I got it to work by: uninstalling it in TiBU, rebooting into recovery and wiping cache and davlik, rebooting and reinstalling from the Play Store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunnersluver:
Oh ok. I was a bit confused since im on stock and I have flashed AOKP builds before but the bootloader post was a little confusing. Thanks anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
What are your most significant wakelocks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Yes, if you would have searched, you would already know that.

-- nice story, bro

---------- Post added at 06:44 AM ---------- Previous post was at 06:38 AM ----------

If you wipe and wipe and wipe and wipe and wipe, those feelings should pass - but check the FAQ.

-- nice story, bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jubin0:
battery life

sir i am using this ROM from last three days loving this ROM only problem i find is the battery problem. i am only getting maximum of 2 hours of screen on time and i clean install the ROM any suggestion sir...:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Looks like you're not running the kernel included with this kernel (underwear.) Task can't support things other than what he includes in his OP. Also, battery life is variable across all users and devices so your best bet is to find the settings that work best for YOU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Also, you're OC'd. Gotta expect less battery life. (You min Mhz is WAY too high)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jubin0:
battery life

thank sir for your response, i have reduced min MHz frequency :fingers-crossed: i hope it will work but can you suggest me best suitable kernel for this ROM coz if changes doesn't do any thing then i have to change the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
There isn't a ''best'' kernel per say. We all have our personal fav as well as them acting completely different on every device. If it doesn't work, you'll have to do some testing on your own.

Bring down your min Mhz to 384 and that should be a great start.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ale408:
google music player fix

This worked like a charm. Thanks for the workaround/fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Why are you changing kernels when Task just merged "8 million" commits to the kernel for the 5/21 release? My battery life has been outstanding on these 1st two cycles.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAR7MAN:
My question got buried, so I'm just bumping it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Constant system UI crashes are definitely not a common thing. I'd recommend redownloading and flashing exactly as the directions in the development thread state. If that doesn't help, your phone may be best fit with a different ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
The GTALK_ASYNC_CONN partial wake lock is messing with my battery life, any idea on how to get rid of it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAR7MAN:
I've been on the ROM for a long time and it has been virtually flawless for me almost every update up until now! I will try re-downloading and then flashing. Hopefully that works. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Don't quote me on it but I think I remember someone having a similar issue and the only thing that worked was using the second most recent gapps package. It's worth a shot if you can't figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beaverslayer:
Blacklisting numbers

Did there used to be an option in the call log to blacklist a number? Seems that it's been removed if it indeed was. I searched the thread and looked at the changelog and only saw where there was an update to the blacklist feature on the 2nd and 14th. Also, I made sure it was enabled. Seems the only way to blacklist a number now is to enter it manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niksha:
Distorted on voice calls

On the 5-9-2013 rom .Whenever i am talkiing on the phone they say that my voice is distorted -even when i put it on speaker-.Any settings i need to change?Thanx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Old builds aren't supported.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Update to fix it. Why would you report a problem on an old build?