yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

We have Re-Opened the thread..........

To all in this thread......... A word of advice.......

If you do not do your part by researching your issue before posting..... lame redundant already posted issues will get deleted.

If you cannot post

On Topic

and post Respectfully you with get infracted.

The Moderators and the Devs are not here to learn for you or edit the unnecessary lame commentaries that derail a thread.

We are here (like most other members) to be respectful and learn how to advance our android experience... by Reading, researching and sharing our results.

Many of the people who seems to struggle the most, suffer from poor reading and research skills...... these are the staple of success in most jobs in real life.

XDA and its members are a good group, but ....... that does not mean we should "Learn For You"........ So, We state this all too often Post respectfully, stay on-topic do the research before you post not afterward...

Our moderating in this thread is going to get tougher moving forward......

Heed our warning and heed our advice...... Please......... Thanks

~~oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
Hey guys

I had an incredibly high cell standby time overnight. 8hrs and 50mins. In fact that's how long the battery lasted after I charged it. "Time without signal" was 0% and it's been on WiFi the entire time. Any suggestions? :crying::confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MOPhiPsi:
ROM rocks! Thx Task!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4Orr:
Thanks for sharing this ROM, Task! :) I'm looking forward to see where your development takes us!

Sent from my SGH-T999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vic_singh:
Can anyone on Bell network confirm that Bell Mobile TV works on WiFi with this ROM?

This app is design to work only on network data because you're limited to only 10 hours, previously I was not able to access this app on WiFi.

I accidentally discovered i can use it on WiFi.

Which is awesome if I get unlimited viewing.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Everything's great except in-call when I went to the home screen it started flickering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Just tried to duplicate this and couldn't get it to work. Maybe try a clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I think your still gonna get some screen flicker across all 4.2.1 roms.

ROOTBOX/Task Charged JB 4.2.1 fueled by Ktoonez 747 octaned kernel SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I have seen any flickering in quite a while. I'm pretty sure its all gone and has been for a while now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
I never experienced any flickering on any of your ROMS. I always stuck with the Kernel you bundle with the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airognol:
Running smooth right now. Thanks for all the hard work guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Nice. I don't think I mind if the capacitive Lights don't work. Flashing now. Thanks for your work. Gonna donate right now :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Confirmation number: 3CM53437HP554412K

:D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave2metz:
Has anybody had problems flashing this on T-Mobile? I got an installation aborted. Error in SD card.

Edit...I tried using the internal storage as well with no luck. Any help would be appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rev1vaL:
since this is for att...i would say post in q and a...or the q and a for this thread

Good looks task! flashing this as soon as it's done
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tophaholic:
Replace the battery cover with an AT&T cover.....now it should work.

:D

Awesome ROM....task and ktoonsez!!!!! Was refreshing this thread all day today to see if you guys release it today....and you did not dissapoint. Keep up the great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kociubin:
A2DP not working in JB

Thanks for the JB ROM. Nice work!

For those interested in A2DP, (i.e. playing music over bluetooth headphones) it does not appear to work in this 7/24 build. Audio is getting routed to the phone speaker. This seems to be an issue with all of the JB ROMs for our device. I remember seeing a post that a fix has been checked into the CM10 repository, but I can't find it for some reason. If it would be helpful I can look for it again.

Making calls using bluetooth works just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rybean:
I did a factory/data reset. Went to flash zip and got "failed to getprop("rp_product device)..... status 7

gonna restore, re-download and try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yokken:
If you open it up with WinRAR and find the updater-script in META-INF, save that to your desktop. You can edit that so anywhere it says d2att, replace it with d2tmo. It might work. Just throw it back where it goes, overwrite, and copy that over. Make sure you set it to "Store" for compression. You can also remove the first line of the script I believe, and it will also work, but I haven't looked at it for this ROM. I'm about to flash though!

You can try that fix as well.

Edit: Ugh, I got it too. Looks like I'll have to figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
Just got all set back up. And all I can say is this sh.t is bad a$$ not every thing is in rom control but I don't care. Very nice and donations on the way
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
do not post in this thread. It is for att version only. We do not support t-mobile so do not expect support from here. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
thanks dude! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tocirahl:
Thank you so much for this, Task! You're the best. What a great present for the first day I get my phone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
why would you give advice to an unsupported device here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] defnow:
update your recovery...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Ktoonsez is the best too then. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rybean:
downloaded again and moved from computer to SD Card, same error. Your AOKP worked great. Any ideas?

E: Error in /emmc/ jellybean.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jxs1984:
got the same error as well. downloaded again - still no go. (att s3)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tocirahl:
Lol, you two can tie. Thanks a lot guys.

---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------

If you're on stock, you'll need to do a CWM update through Rom Manager.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
No flickering on KT 1.10 either :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brian6685:
I've looked through the thread and FAQ and can't find the answer to this, so I'm gonna ask, if its a CM/AOSP thing, then just redirect me to the right place. When backing stuff up from touchwiz with titanium backup, or notes or anything, it works fine. When booting in AOKP, it doesnt find any of the backup files. The filesystem is not compromised and all the other files are there, but for some reason the titanium backup ones aren't? Its almost as if the aokp filesystem uses different locations or something? Does that make any sense?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
yes, it moves those backup files to the sdcard/0 location.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Not positive, but here's my guess -

TW is not 4.2.

4.2 places the internal storage in a different location, to allow for multiple users.

Try pointing your TiBu toward the new location: /storage/sdcard0/<whatever>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brian6685:
So TW 4.1 used /sdcard, and 4.2 uses /storage/sdcard0/ ? That makes sense.. however I still cant find the backups made while I was using touchwiz in either location. Oh well, not the end of the world, was just curious if there was a way to recover it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
TB/menu/preferences/search device for buckup folder/apply.... eat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brian6685:
Did that, doesnt find anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beaverslayer:
Not sdcard0, but 0. It's an emulated drive found in storage which is at the root or core of the directories.

---------- Post added at 12:52 PM ---------- Previous post was at 12:49 PM ----------

Just checked mine with a root browser and sure enough all my backups are there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Then you have no backups on your device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robg2008:
Loving this rom. Thank for all of your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
I'm having the same problem.. Was not able to find any of my back ups from TB... No big deal though as I reinstalled all my apps... I can always replay my games... Other than that. This is the best ROM I've used so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
It took me a while to find all my stuff but it was like mnt/0 or one of the other folders within mnt/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpom1983:
i do expect your help. if you dont want to help me fine, then thats your choice. you release something for the public to use, so of course as with any product you will get feedback. you could say, i release this rom, dont ever contact me about it. and then people know to use at their own risk. but you seem to want to know about bugs and issues.

i read the whole changelog, i can clearly see you stated this was fixed. but it isnt. also just so you know, bluetooth hasnt changed either. back like 10 updates. i read every issue possible in the Q&A i searched this thread and others looking for an answer. basically what its come down to is. ive updated correctly, i followed the instructions perfectly. ive tried going back to stock ive tried reflashing everything, it all comes back to working perfectly except the call answer length. which you seem to have acknowledged that it is an issue with your rom. so im telling you. would you like me to post a screenshot of my phone showing the version? do you not believe me or something?

basically people install your rom, they have questions about it. if you dont want to answer them, then dont have a thread for your rom. like the other guy who asked if it had wallpaper resizing options. it took 6 replies for the guy to get his answer because you were too cool to just say no that option doesnt exist in my rom. not everyone is a noob. and sometimes people do take the time to look and search and when they cant find what they need they just are simply asking for your help. its a community. stop being so quick to jump on peoples backs.

Make sure you have CWM or TWRP Recovery

MAKE A NANDROID

Boot into recovery

Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system!!!(If already on AOKP 4.2.1 you should be able to just wipe cache & dalvik. If you have ANY ISSUES, FULLY WIPE BEFORE POSTING IN THIS THREAD!!!)

Flash ROM

Flash Gapps

Reboot

Done, and still answer lag. no problems during updates.. even if you cant help me, then at the very least im just telling you it didnt work for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elementunkn:
I don't know if anyone else is having this issue, but even after a full wipe I'm still getting gaming lag on the 1.10 build. Also, after I close the game down my whole device lags until I lock and unlock it if that helps.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Widely reported.

Task says it's fixed for him. Ktoonsez acknowledges that it's only half-fixed.

Apparently, it depends on the game. Just be patient.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beaverslayer:
Hunh? Mine answers instantly. Also, I haven't seen this mentioned in a while. Strange.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you expect anything from me then you are definitely in the wrong place. You are not paying me for this nor are you my boss. So your expectations are absolutely ridiculous. This is not my job. This is a development site/thread. So now its on you to fix the issue if you like. The issue is fixed whether you like to think so or not. You are the only one reporting this out of thousands of downloads. That says something. You are not forced to use this ROM dude. So move on to the next one if you want. Its that simple. Now. Please do not post here anymore due to your lack of understanding and expectations that do not belong. This is a development thread. So either contribute by digging into the code or by providing something useful. You have done neither of the two. Please respect that. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpom1983:
me neither.. and nobody else said it didnt work since update so i dunno whats goin on with me... also my LED doesnt work at all. never comes on anymore with notifications or when i use LED app and hit test.

---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------

I get what your saying, you have no obligations to do anything. thats all fine and good. if i am the only one experiencing these issues and that says something.. what does it say? all i am trying to do is, use your rom, and report problems im having. maybe you would like to know it didnt fix it 100%. maybe you dont. i cannot write or read code, so i cannot help in that respect. but i can use and use and test and let you know if i find something. maybe i would write down an issue, and you will actually like to hear about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The issue is fixed 100%. Sure. It sucks that you have the issue. But it's just you. Like I said all reports say it's fixed. You are the ONLY one out of thousands that saying it's not fixed. What that says is it could be something on your end. Whether it be just a device that doesn't like this ROM to something on the installation side. Who knows. What do you really expect me to do about that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Well then the LED is probably broken on your phone lol

Sent from the Dank Device, aka my GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
My bad for the incorrect response task! Good to know. I dont get screen flicker but tearing of images every now and then. But no complaints here, it goes away after disabling hw overlays.

ROOTBOX/TASK Charged JB 4.2.1 fueled by Ktoonez 747 octaned kernel SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Hold down on the power button for 20 seconds, that will ensure you have no more problems that no one else has! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lavrentsii:
About the gaming lag: it appears to specifically be heavy-2d games like pewpew. 3d ones work fine for me though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
I think that a lot of the people that report issues would receive better responses if they would provide a logcat or that report you can pull after a reboot... desmeg or something. The name escapes me.

Sent from my AT&T GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
In call screen flicker stopped after restart. Now running on ktoonservative overclocked and undervolted. Performance and battery are great. Great work guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
I would also like to add that I found my back ups... They are in sdcard0/0/0

Not in sdcard0/0...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Upgrade your recovery. Then you won't have all of the nested 0 folders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oka1:
From the moderator

jpom1983...... I ll explain this so people do not get confused...... As of today there 5 to 12 locations at any given moment making the S3...... Depending on who made it...which vendor supplied the chips and how it was assembled results in "Not All phones are the same" ...even though they are ALL S3's or Note 2's etc...... this is why one person gets some weird bug only and no one else has it......... If this proves to be the case, then try flashing different Kernels or modems that are compatible with the Custom rom you are on.... in this case task's rom........ If that doesn't fix the issues (assuming you tried everything else recommended by the dev) Then you may have to switch roms......... But , my experience has showed me there is almost always a work around for it........ Hope that helps clarifys the issue Good luck on finding a fix

~~ oka1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpom1983:
I'm not sure, maybe give me a few pointers or tips that i havn't been able to find out elsewhere. anyway whatever. i like your rom, its great. i will continue to use it and deal with the side effects. which are not as bad as the side effects of stock. thanks for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Try redownloading the ROM, fully wiping again, and reflashing. That's about all the pointers I can gibe you at the moment. You're welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Clark Joseph Kent:
Since I have typed it before, thought I would just quote my own...any more stupidity being posted again will be dealt with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
So I disabled HW overlays, flashed ktoonsez's 1/10 kernel, and after boot, it sits for a second, then Nova launcher FCs, and I get rebooted into an AOKP boot animation that flickers like crazy.

I'm running your 1/9 build, since then, with no stability issues, except when I try ktoonsez's kernel. Great ROM, just can't figure out the custom kernel thing :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available in the OP for download or just check your OTA Updaters. ;)

AOKP 4.2.1 Jellybean 1.13.2013

Updated kernel (Linux 3.0.58 and a few other things)

Added option to use carousel animation when switching widgets in Lockscreen (Rom Control/Lockscreen)

Added CM's Chonus (Clock and Weather Widget)(Look in the app drawer. I might add it into Settings at a later point. ;) )

Added Performance Control Quick Link in Settings

Added new Keyboard (It's more like the CM one)

Added an option to change the device hostname

Added CnE (Connectivity Engine (CnE) provides advanced network selection per socket, reduced signalling traffic, and increased power savings.)

Added support for 5.1 sound

Made some changes to bluetooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This rom has nothing to do with that kernel. You will need to go over to that kernel thread to get support for it. Not all devices are made equally and your device probably just won't run that kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You can also try moving your data over to your extenal card and wiping/reformating the internal SD. Sometimes there are lingering settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
Thanks for constantly releasing updates for us man. Your work is greatly appreciated in our household. Running your ROM on two S3s!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markjo:
woooooo gonna try 1/13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brandimc:
Damn, Task. You spoil us with all these updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Erm... isn't this thread "Task & Ktoonsez"? I was under the impression this ROM was supposed to work with that kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Erm... no. This is a ROM thread. I maintain the ROM. Ktoonsez has an awesome kernel which has it's own thread. You need to go there for support for that kernel. There are two separate threads for good reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I know it has been a while since this issue was brought up, but with regards to screen time sometimes not being counted, I am able to reproduce it upon reboot, that is, immediately after reboot if I begin using the device and do not switch the display off, until the screen is cycled, the screen on time is not recorded. If I then cycle the screen, the time is recorded properly from then on. Thank you Task for all your hard work, this ROM is amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
OK. Thank you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I don't even pay attention to the battery portion of this device. This really isn't a big deal in my eyes. Constantly watching screen on time and battery stats pretty much defeats the purpose of actually using these powerful devices. Not really sure why people get these kinds of devices when the turn off all syncing, data, vibrations, ect... and not even use the phone to the fullest just to see/have the battery last for 3 days. Flip phones do the same thing and the battery on those things last a loooooong time. lol. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ObiWanJacoby:
Awesome job as usual Task!! Loving the new lock screen widget and carousel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I know, it really isn't a big deal to me either, I just wanted to make note of it for anyone else that was having that happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No problem. I really should just remove that section of the ROM to see how many people freak out and go crazy from just not knowing. lol. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] papaskispartan:
Thought I would share. Never had issues with OTA before. For some reason for 1.13.13 tonight, I got an error that UI had to force close, over and over again. I dont get why I got it this time, as all the other udpates this month never had an issue. So formatting system, sd card, etc, wiping everything and going for a fresh start.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No need to do all the usually. Just boot back into recovery and wipe cache and dalvik cache. If that doesn't work. Fully wipe your device at that point. These type of things happen because there are changes in the framework and other places in the system. It's just how it is. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
This shows the type of guy Task is. He has said in the past that he essentially doesn't give a **** about Bluetooth because he doesn't use it (even though several of us do), yet he has made slight changes to Bluetooth the past 2 releases. Thank you very much for devoting time to something that benefits you in no way :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Thank you. Happy to see a Dev and somebody with some respect around here finally say it. Gets tiresome with all these post about battery life.

I max this damn phone out to its fullest. CPU maxed out. A thousand apps with a thousand widgets. Screen bright enough to burn out your retnas.

If I'm ever concerned enough about battery life I'll just buy a second battery. Easy enough.

Sorry I'll quickly jump off my soapbox and let things get back on topic.

My bad.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] papaskispartan:
All is good task. I'm use to setting things back up, don't mind at all =) I did just wipe cache and dalvik a few times but still was getting the error. Instead of wasting time trying to fix, I fully formatted knowing its fresh. only one that gets frustrated is my wife =)