yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There a general forum for these types of things. Wiping and/or options in a recovery don't have anything to do with this ROM. I would check out the recovery thread you're using for info on that. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aklbeach:
I'm getting this issue too. The caller ID shows no info and the dialer had the same problem where it looked all misaligned. Not using the hacsync app or whatever it's called
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
I have had the same thing happening to me periodically.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxwithanx:
Google Voice calls not showing up correctly in the call log is a big issue for me so I tried playing around with Jermaine's CM11 KitKat build (call logs work correctly!)....but too unstable at this point.

Going back to Task's 10.22.13 build...should I use the 10.31.13 gapps or back to 10.7.13?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
I had the same issue. I went back to the 10/22 build and am using the 10/31 gapps with out a problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is the exact type of post that doesn't help to fix issues. We need bug reports here. Not workarounds. Otherwise whatever is broken will stay broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This thread is for this ROM. Not others. Please stay on topic and report the bug with info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
No more updates??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
He posted a log of the issue in this thread back on November 4th.

http://xdaforums.com/showthread.php?p=47095132
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's cool. But where's your logcat of the issue? If you report and issue. I need your logcat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
Honestly, I don't know how to make one. I'll look it up, reflash 10/31 and get it to you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All the info you need is in the OP of this thread. Please always read OP's of threads before posting in them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
I got the dreaded "read the op" phrase! Sorry Task.

Found the instructions, attached the log. Again, the problem is that when dialing out with google voice the call log switches to the throw away number google uses. This problem is new to the 10/31 build. I had this problem in the past on another phone and rom and I believe it came down to the phone.apk.

The call is placed at 11-23 19:46:13.750

The throw away number (5043023683) appears at 11-23 19:46:13.980

Happy to help in the development in such an awesome rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
I have read through the original posts on this thread and the Dev thread, I have searched to no avail.

I am really stumped on this boot loader and modem. I'm trying to flash the 10/31 build, my current modem and boot loader is EMJ2.

I tried flashing DLK3 for the modem and boot loader as advised in the OP, but I still get the boot loader error in recovery (I'm on Touch).

I just reflashed EMJ2 and am on the i747z ROM until I figure this out.

Help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattio781:
Odin back to stock dlk3 worked for me many times, not just flashing the modem, there isn't a boot loader in that file. Always go back to oem stock if having issues, and don't forget to back up you Rom, and re root
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meanhacker:
to my best knowledge, you need to flash bootloaders with Odin, not recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
I flashed the zip file found in the thread of boot loaders made by that guy who links to it in his signature (can't remember the username). That zip file was supposed to be flashable with a recovery, but whatever, c'est la vie.

I'll probably just end up digging up Odin and messing around with it. Thanks, meanhacker! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meanhacker:
did you see this post?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rkant18:
Does this rom mess with the bootloader. I want to flash this on my att s3 on 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
No. Searching would have brought up about 5 million answers for this lol. You have to use Odin to change or mess with bootloaders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Every so often I install and run into the bug that drains 10%batt every hour regardless of what the phone is doing (standby). I've got that bug now. Tried resetting and reinstalling with no success. I know it's not the ROM but I can't figure out what happens which cuaes this or how to solve the problem.

Searches have been unfruitful. Appreciate any help. Happy thanksgiving!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
use betterbatterystats to find whats causing this. you havent given any info for us to work with here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Omg I used betterbattstats today and it says my WiFi was not on, but "running" 100% of the time regardless of the settings telling me its off and using cell net. Does this sound like something that can happen and totally destroy batt life?

I tried reinstalling the ROM and resetting it. Both which I've done in the past and one has usually solved the problem. Haven't run into it for maybe a year before now.

Thanks for the help, any more please? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
I've been having same problem. Unfortunately no solution. I reinstalled ROM twice and still WiFi is always running. I just deal with it because I love this rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Holy moly task you're a genius in so many ways and suggesting that app this is just another. Any way you can help us out?! Thanks for everything always!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
No.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
I apologize for the rudeness but you are absolutely zero help.

I did however find this that IS helpful and I hope solves my problem. Post #5. http://xdaforums.com/showthread.php?t=2531745

Also, it seems just cycling the WiFi tether may have done something too. I'll report back in a few hours when I see the results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you don't find something helpful then don't respond to it. Move along to the next. Its pretty simple.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
I know but its just extremely annoying. The good news is that it seems to have worked (only been a short testing time though)! Amazing news since I have run into this problem several times over a period of years! Thanks for the guidance, hope it maintains and doesn't revert.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
I can't possibly understand how have determined that the WiFi being "on" in has been draining your battery in little over a hour, but hey if you needed a placebo effect, more power to ya.

In actuality, the WiFi being on has little if any impact on your battery life and I have tried both keeping WiFi off during sleep and not. The only difference it made was a slightly higher cellular data usage on my device.

Excusing the two brief moments I had plugged in my phone to transfer files, I'd say my battery life has not been affected by WiFi being on the whole time.

http://i.imgur.com/NENHTqE.png
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
I was wrong. It seems to have helped a little with actual use time, but I'm still draining at 3-4% every 10min just sitting on standby. Oh woe is me. :(

Batt stat app says deep sleep the correct amount of time and shows little else use; all legitimate and lower than expected CPU use too. Would one of the posted kernals possibly rectify this?

And as for Jaspah, if you actually read my first post you would have understood that WiFi is OFF but the battstat app says it's "running" 100% of the time. Regardless that problem was solved with a wif-tether cycle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xsever:
I ran into a similar problem where the Google+ app was keeping both cores at full speed although i never use that app.

Solved it by stopping the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ZzB3B0zZ:
I'm on leak 4.3 touchwiz and I tried to flash latest aokp and fail in both latest CWM and TWRP recovery I download the bootloader and fail in every version of Odin what I'm doing wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
I reinstalled a third time. No luck, nothing helpful from betterbattstat. 9-11% drain per hour when on standby. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
This isn't normal behavior. I'd try redownloading the rom, gapps and doing a complete wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meanhacker:
are you in download mode?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ZzB3B0zZ:
Yeah it was on download mode
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Wurd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Lol no. The only time that scam was ever installed on my phone was when my girlfriend installed it to send herself lives. That's when I realized how much of a scam it was.

I just installed the 10.23 date version and I still have the same batt draw. I haven't changed anything else since the previous older edition I had.

The drain is so fast that a computer USB's 500ma current can't keep up. The 1A wall charger gives me like ~20%/hr of charge, and my 2A charger is the only thing that can give me any tolerable charge speed.

Just typing this out took 3% of my batt. This is rather extreme. I also checked the physical batt, no bubbles, seems totally normal.

Just an off point thought: I've repaired so many broken iphones and its damn easy to just install a bigger batt and screw on a diff backplate. Why dont any products exist to do that? Rather people have extra large batt cases with needless electronics and ports...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cruton502:
Have you tried reverting to stock (rom & bootloaders) to see if the drain happens there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
Well no. My next step is to go back to the somewhat buggy version of task650 I was using previously for months. I've always had task650. This is the first batt issue I've run into with his. I hope whatever happened isnt so bad that I must test stock crap.

Heading home today so I'll know what I previously had stored on my computer...black travel day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're next step should be to flash back to stock, FULLY WIPE, and reflash this ROM. If you haven't noticed, you seem to be one out of thousands that have downloaded and flashed with this issue. You need to find out what's going wrong on your end. I think taking up 4 pages of this thread should be enough to figure that out. Either you have an app going crazy or you have a defective device.

P.S- "Somewhat buggy" is a ridiculous statement without facts (logs, last_kmesg,ect...) to backup that claim.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatkabab:
I apologize for that. It was an aquired buggyness from the crap I was doing to it. I have a nandroid of it is was planning to try. Updating solved those issues. Your work is always excellent. I could not thank you enough and have more respect.

As for this issue, it's a rare occurance I've encountered with several devices/roms since the donut days. I find it very interesting how it's still a rare mystery like many human diseases...

Sorry for the needless discussion, I'll flash back to stock and give that a go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tuxattack80:
[MENTION=2928662]task650[/MENTION] beer is on me bro, been using your ROMs since the i777 days and never have i once been disappointed with the quality of the release you give us. Didnt want to clog up your dev forum so i posted this here. Thanks a million man, now get back to work and give us some more of that underwear goodness! Lol! Transaction ID:

02150981FY996590X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
So i just rooted my at&t i747 with this http://xdaforums.com/showthread.php?t=1963790 and did method 2 and have the latest twrp, Im trying to flasht his and it gives me a fail. and this is what comes up.

assert failed: getprop ("ro.bootloader") == "I747UCDMG2"

getprop ("ro.bootloader") =="I747MVLDMF1"

getprop ("ro.bootloader") =="I747MCLDMF1

getprop ("ro.bootloader") ==I747MUMBLK3

getprop ("ro.bootloader") ==I747MUMBLL1

E: Error executing updater binary in zip '/extern

Error flashing zip '/external_sd/aokp_4.3_d2att_

and in red it gives me fail?

---------- Post added at 12:23 PM ---------- Previous post was at 11:35 AM ----------

Also how can I post a log that I made so it won't take up the whole page
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
8

You can edit your post, paste the log then you can use the hide tags which are used as follows.

{hide} the information you want to hide such as the log you don't want to take up the whole page{/hide}

doing this will give you a button like the one below. you must replace the { } symbols with [ ] symbols.

the information you want to hide such as the log you don't want to take up the whole page
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
ok cool you mean edit in the log recovery i made.?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theramsey3:
Edit your previous post and add the log you don't want to take up the whole page. Or just add a new post. But use the hide tags and you get the button that hides the information you don't want taking up the whole page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
Read the OP man, update your bootloader via Odin, then you'll be golden. Searching would have provided this info. It's been gone over a million times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Well I have been told and seen in other threads NOT to update bootloader leading into a brick.

I747 (AT&T)

Please stand by while these files are replaced with safer versions.

This is for your own safety, to prevent accidental bricking of devices.

·

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

Ok so then If I do im guessing that after the bootloader update it will work all 4.3 roms not just this one?

Just tried to flash it and in Odin said fail I added it to the PDA slot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cehf:
do NOT use the bootloader that is packaged with the official att 4.3 release. that is the bootloader everyone is warning you about. the bootloader from 4.1.1 or 4.1.2, I747UCDMG2, works fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Damn I cant thank you I reached my limit but where is that link for the right bootloader then? My baseband is I747UCUEMJB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You are jumping to conclusions here. The guy actually has updated his bootloader and its NEWER than the one shown in the assert. So please don't say read the OP and update when you don't even know the whole story. Task needs to add these newer bootloaders to his asserts just as CM has been doing.

So thanks for trying to help but you are confusing the poor guy with misinformation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Well thanks to theramsey3 helped out in my post because I had brick and had to use the hard brick img to SD card hack. Thank goodness my phone is up and running thanks to that guy and yes we looked into it and have a newer version of the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meanhacker:
today I received an HDMI MHL cable for the S3, tried it out, so much nicer on a 50" TV, but for some reason there was no audio - it was just coming out of the phone's speaker. anyone else have this issue? does audio over HDMI work with this task's ROM? cable tested with a galaxy s4 resulting in sound over HDMI so I know the cable is capable of transferring audio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
This has nothing to do with tasks rom. Please stay on topic :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thoughtMaze:
wifi

Why does the wifi not connect automatically? got to airplane mode on off before it kicks in... always problems with this rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its because you have absolutely no clue what you're doing. Always problems with uneducated users. You should try learning something dude. It would be good for you.

**Look! I can co tribute absolute useless nonsense too**
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thoughtMaze:
haha good one. I guess we on the same level.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
I know the apn issue has been reported a few times (can't change the apn settings) but I was wondering if anyone knows of a work around that would allow me to edit the apn settings. I've looked on the play store and there's no apps that allow you to override android OS and just edit the apn list. Is there a file somewhere on the phone that I can edit to modify my apn list? If not, I'll have to wait for the next update.. Thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psm510:
Where can i delete ringtone/notification tones i dont like?

I deleted a bunch out of root/system/media/audio but there are still more i want to get rid of. Where would i find them?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anken74:
ROM seized?

This came up in the development thread by Helloworld294:

The development of this ROM has been seized. Everyone please start withdrawing from the TaskAOKP addiction.

Is this really true?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
No updates in 6 weeks. I would say it's safe to assume so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
Task just posted this in the Dev thread:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
How would anyone be able to answer this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@ everyone

You guys really shouldn't believe things that someone that has nothing to do with this ROM says. I post on g+ about what's going on. I've already invited all of you to that community and its even linked in my signature for those that didn't see my posts. I keep updates there. I had to get a new computer and have started a new job. Things need to slow down for me to have some more time for this stuff. But things are being worked on. My github it public for everyone to see what's happening. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anken74:
Sorry Task. He had a senior member status so I assumed he had his ear to the ground. I'm still pretty impressed with your work. You must be one of those guys that gets bored too easily because I've only seen a fraction of what you do. Good on ya.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Any jackhole can get senior member status. It's only related to how many posts you have, not how long you've been on XDA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ns4smi:
Hi, is the latest build ( 10/31) compatible with the 4.3 MJB boot loader? If this ROM is packaged with an older bootloader where would it be located?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) No

2.) Custom ROMs should never be packaged with bootloaders. That would just be ridiculous and dangerous.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I'm getting something similar in Touchdown emails and Gmail - Touchdown seems to be rendering blocks of text jumbled, Gmail too with text and images. Touchdown did a fresh install and resynced messages. Full wipe, format system, standard gapps. Did load Ktoonsez' 8/1 kernel.

EDIT: Dolphin browser is having issues rendering as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Infuser86:
This is what it is doing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
And here is what it should look like:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
I see this too and have read a couple posts here and there about this. i have always just put my number in voicemail settings and never thought more about it. Will add to FAQ.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
What is? (You were trying to attach a screen perhaps?)

In any case, I'm seeing the same issue. 'hadn't noticed until somebody mentioned it. (full wipe/format/install. flashed gapps right after rom, then rebooted.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Ok @ everyone if you have not noticed Task and Ktoon are suggesting full wipes before flashing so there must be some major sh!t going on with this build. Make sure you follow the OP and full wipe even format system. This seems to solve the problem with several of these REPEAT problems. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkstar765:
Same problem here. Otherwise ROM is perfect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Infuser86:


This is what it is doing in my end. A reboot seems to have fixed for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drlynes:
Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
^^Do what the man says! You will be happy campers^^

​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aquethys:
Which kernel does this ROM automatically package? Ktoonsez? If not, do I flash ktoonsez after or before flashing the ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
It flashes the kernel built with the ROM - Ktoonsez helps with it though, I think. You should follow the instructions to finish installing the ROM (wipe, ROM, gapps, boot, log in, reboot, make sure install is finished) and THEN flash ktoonsez kernel if you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goob1284:
Does anyone else's phone become extremely warm towards the bottom of the phone? I can feel it through my case. I did flash a different kernel and is slightly oc'd. But if I put it back to regular clocks its still the same. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
If it doesn't settle down, you probably got a bad flash. I'd restore and make sure that's stable, then try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
Quite normal if playing a game video or heavy downloading especially with over clock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bori1030:
go to setting from the dialer and scroll to call forwarding when it loads up you'll see a number in every slot copy that number go to VM and paste that number in there and VM should work just fine I also now got the at&t VVM app working to... hope this helps... goodluck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfleischman:
Capacitive Lights

I know that a method for turning these lights off has already been mentioned. I am interested in getting them to work properly. Has anyone gotten these to work like in AOKP for ICS? If so how please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Interesting I'm getting the exact same problems with Google Reader as well

Edit: never mind a reboot didn't fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Narcistic:
Have this issue with gmail..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Infuser86:
Just did a factory reset and flashed again and still having the above issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
Merry Christmas Task!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sounds awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] londonandlawson:
Any help would be appreciated, can you please help? I also uploaded the bootloader like post 9 states and have wiped it again