This thread has been created strictly for
Questions and Answers
Questions and Answers
[SIZE=+2]Dealing with[/SIZE]
AOKP KK
[SIZE=+2]This thread has been created for people to share issues and question they may encounter while using this version of AOKP[/SIZE]
[SIZE=+1]Please do not clutter the Development thread with non related development chatter.[/SIZE]
Go to his G+ to do that.
Go to his G+ to do that.
PLEASE make sure to thank task650 for his dedication to this body of work
Thanks to all the members of XDA and Task's threads, credit goes to everyone as I have just taken info from users input and located it to one place. Thanks to you all for helping us learn everyday
.
- BUG REPORTING: Very minimal at least read the thread from the date of the update you are running. If you see a couple posts about a paticular bug then consider it noted by devs. They do read these. Remember if they can't duplicate the problem then they sure as hell can't fix it. IF you are going to report a bug - include the necessary information or it will be ignored.
- thanks for understanding that after a few bug reports are made and i acknowledge them, that the unecessary 100 that follow are ridiculous. Task
- Always read the OP. If it says full wipe then do a full wipe. If you don't follow the OP please don't post problems. This isn't helping anyone. Full wipe isn't a big deal. You can backup and restore your launcher settings with Nova or Apex, Backup and restore apps with Titanium backup(pro has the batch feature and is worth the money) and you can backup and restore most of your AOKP settings with AOKP backup. ***AOKP BACKUP can cause issues when restoring. If you have errors after restoring with AOKP BACKUP try the process again without using it.*** Using these three methods takes about 10 minutes. This is barebones backup/restore. If you have a lot of tweaks and kernel changes it will take you longer. So as stated in the OP if you have problems do a full wipe before you report any problems.
- Read the change log. This will answer a multitude of questions.
- This is for the AT&T version of the Galaxy S3. This rom may work on different variants of the phone, but as for now Task and Ktoon do not have the time to support other versions. If you are on a different version of the Galaxy S3 and report a bug please understand that this ROM is AT&T supported only.
- This is just to help Task and Ktoon keep repetitive questions out of there thread. If any information in this post conflicts with Task and Ktoon's OP or ROM thread then ALWAYS follow their information first.
- Below is am alphabetized list of FAQ, bugs, known issues and tips.
- This is just a collection of answers that have been posted in the thread. Use as a guideline not as a rule of thumb. Always follow the OP.
- Read this>>>>>>> Helpful_Information
- Annoying (small issues) repeatedly posted about
- AOKP BACKUP
- App FCing, freezing or causing reboot or just not working properly
- 2g Toggle
- Black screen/Phone locked up/Can't wake
- Battery life
- Bug Reporting
- Bluetooth
- Bootloader
- BenchMark Scores
- Canadian users
- Capacative Buttons
- CM10
- CRT animation
- Data working
- Data connection speed symbols
- Error 7 in recovery
- External SD card
- Facebook
- FAST CHARGE
- Faux Sound
- Flicker
- Full wipe per task/Weird ****.
- Gapps
- Google Now/Google
- GPS
- Home Screen/Home Button
- Inverted Gapps
- IRC channel for task - ##Task650_AOKP
- Kernel
- LED
- Links/External Links for ROM/Gapps
- LTE
- Modems
- OTA Update/Recovery
- OLD/OUTDATED versions of this ROM
- Performace settings
- Recovery - SEE OTA
- Requests
- Ribbons
- Ringtone
- ROM control settings
- Rom Manager
- Runtime
- Screen shot
- Signal/WIFI colors
- SMS/MMS
- Sound/Volume
- Swag (Pink Hat)
- Themes
- Toggles
- Touchwiz
- Voicemail
- WiFI/Tether
- WIFI/Signal colors
- Useful links
- Annoying bugs/glitches reported
- Make sure you always have the latest recovery if you have problems flashing roms. See 17 of this posting.
- Not all ROM control settings are back yet. As always this will take Task some time when updating to a new OS. Be patient. If you don't see it just "wait for it". See post 3 #3.
- AOKP BACKUP
- AOKP BACKUP is a great app for restoring most of your settings, but may cause some issues
- Third party app not working properly
- This ROM has nothing to to with 3rd party apps. You would need to contact the developer of those respective apps to get support for them. You also need to understand that not all apps support the Jellybean 4.4.x OS yet and need to be updated by the developers in order for them to work correctly. task650
- Trying clearing data for that app
- If you used TIBU to restore app, clear cache and data and delete the app and download it fresh from the Playstore.
- Some people are reporting third party camera apps not working correctly and/or causing stock camera problems. This could be true for a number of third party apps that could be conflicting with system apps.
- If any given app/process is giving you problems or fc'ing- try clearning data for that app and/or fixing permissions.
- Make sure you have the app updated to latest version. The existing version may not be up to date for 4.2.X or whatever version the ROM is.
- If your app won't sync or no notifications - try logging out and then back in. Or try deleting the account and add it back.
- 2g toggle
- If you can't get your phone to wake up-
- Hold down the power button for up to 30 seconds - it will restart. You should not have to pull the battery after using this step to restart. It does work and may take a few times for you to get it right.
- BATTERY LIFE:
- We all at some time have been proud or dissapointed in our battery life, but please keep battery stats out of the development thread.There are threads for this and the Development threads are not one of them.
- There are way too many variables that influence battery life to be concerned with in a DEVELOPMENT thread. This has been stated daily by the Developers.
- Install betterbatterystats and figure out if the problem could be something causing a wake lock keeping your phone from entering deep sleep.
- Go here to discuss BBS wakelocks and read the how to in the app. It is very beneficial.
- It is a known fact that it may take a couple charge cycles for your battery to calibrate and settle in. Also it should be known that these batteries do not need the data cleared for them. THEY WILL CALIBRATE THEMSELVES.
- If you are getting over 3 hours of on screen time on a single charge that is nothing to complain about. IF you do see a post in the development thread about battery life, ignore it. Once again, no one uses their phone the same and their set up is probably not going to influence your phone significantly.
- Sometimes an app or process is just sticking and a reboot will help.
- You could possibly see battery showing charging when not plugged in or a dramatic change after a reboot. Once again this is just the battery fuel gauge recalibrating itself. This is normal.
- For some good tips on fixing battery drain go HERE.
- Bugs/reporting
- Bug reports should contain a logcat or information that would help. saying this doesn't work or this is happening doesn't help us at all and at that point belongs in Q&A. task 650
- Some bugs are being reported by a few that Task, Ktoon and others are not seeing. Follow avidmovies notes below on trouble shooting/comprehensive reflash and Task's suggestion above on weird sh!t. Stick to the basics and see if problem is there still - such as stay with kernel that is included with rom, skip restoring anything with titanium back up, other words just try the basics and if a certain app has been giving you problems download it from the market instead of TIBU and see if problem still persists. Some apps have been reported to make ROM features malfunction.
- If you had a spontanious reboot, we need the file last_kmsg from the /proc folder.
- If you have n FC on an app, thats when we want a logcat
- Guide on how to logcat. http://xdaforums.com/showthread.php?t=1726238
- All In One Android Logger > AIOlog
- Catlog - https://play.google.com/store/apps/detailsid=com.nolanlawson.logcat&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5ub2xhbmxhd3Nvbi5sb2djYXQiXQ..
- If you do not have the latest update of this rom consider it unsupported. This is why they update- to get rid of the bugs that we may be having on older versions.
- BUG REPORTING: Very minimal at least read the thread from the date of the update you are running. If you see a couple posts about a paticular bug then consider it noted by Task. He does read these. Remember if he can't duplicate the problem then they sure as hell can't fix it. Bug reports without a logcat or a random reboots without a last_kmsg will be ignored.
- "Thanks for understanding that after a few bug reports are made and I acknowledge them, that the unecessary 100 that follow are ridiculous." Task
- Just follow this practice and you will be golden.
- If you see a bug reported once - go ahead and report it again with a LOGCAT or proper info.
- If you see a bug reported twice and you are seeing it consider it a known bug and the following will probably happen-
- Task has the same problem or enough info from LOGCATS provided and will fix it or
- Task is not having the problem and can do nothing about it unless a LOGCAT is given
- Point here is Task can't fix problems with out the proper information.
- "Be patient for the galaxy s3 settings to be fixed." Task --- Some stuff is taken out, left out or temporarily removed for good reason.
- If you are going to report a problem, include some details. Kernel, UC/OC, circumstances, etc...
- Once again TALKING about a bug without the proper info including either LOGCAT or last_kmsg is nothing but A WASTE OF TIME.
- Read THIS posted in the development thread by Task.
- HOW_TO_PROPERLY_REPORT_A_BUG
- Please put logcats in a text file so it doesn't take up a whole page in the thread.
- BLUETOOTH
- If your phone switches to vibrate when you connect to bluetooth. Check here
- Settings>Rom Control > Bluetooth A2DP connected action
- No action
- Vibrate Mode
- Silent Mode
- Settings>Rom Control > Bluetooth A2DP connected action
- If your phone switches to vibrate when you connect to bluetooth. Check here
- 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.
- Instructions for updating to the LK3 BOOTLOADER are HERE
- 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.
- The I747UCDLK3 bootloader is needed from rom update 5-17 and on.
- Benchmark Scores
- The devs have stated many times that these scores are BS. If you run a benchmark and want to discuss it, there are threads that are purely for discussing these random numbers. The development thread is not one of them.
- Canadian
- It has been reported that this rom works with the canadian version phone
- Please understand that Task does not support canadian users because he does not have that phone.
- Feel free to use his rom with the understanding that he does not support it.
- GO HERE for help with LTE/Data problems using this ROM.
- Reported that you must turn off LTE to tether.
- CAPACITIVE BUTTONS
- For instructions to disable capacitive buttons go HERE!
- CM10
- This is not a CM10 ROM nor is it based off one.
- Comparing the two makes no sense. This is based off Google as is CM10. Other than that there is NO comparison. Please understand this. If something works or is in one rom doesn't mean it will work or is in the other.
- If you want to compare CM10 and Tasks AOKP take it to the general section. A development thread is not the place for it.
- CRT animation
- If you put your animation speeds below .75 CRT will not work.
- There are now toggles and more options for CRT - familiarize yourself with them.
- DATA CONNECTION/SPEED
- If you have no data after a flash, dont freak out.
- Try rebooting
- Make sure you have data toggle turned on.
- Try toggling airplane mode
- Check APNs.
- If you have no APN's make sure your SIM card is in good and reboot.
- If SIM card is not detected during a reboot - your APN'S will/could be blank.
- DO you have your IMEI intact?
- GO HERE for help with LTE/Data problems using this ROM.
- DATA SPEED PROBLEMS
- Data speed can vary greatly depending on user traffic and distance from towers.
- SpeedTest app is not a reliable source of accurate data speed
- The ATT APN is being phased out by ATT. You need to use the ATT LTE APN - task650
- Network mode is for Canadian users only
- Just because your stock ROM said 4G doesn't mean you actually had 4G/LTE. ATT roms report H/H+ as 4G where as this ROM gives you true data connection.
- If you have no data after a flash, dont freak out.
- DATA Symbols
- I flicker between H and 3g. AOKP shows true connection where as stock roms just show 4G. Also this rom controls data connection and kicks it down to 3G when not using data and kicks to H+ when you need it. This is a feature to save battery.
- Blue symbols means you are connected to google servers - gray means you are not
- Symbol equals>
- G=GPRS
- E=EDGE
- 3G=3G
- H=HSDPA/HSPA
- H+=HSDPA+/HSPA+
- LTE=LTE
- You must have d2att recovery to flash Task and Ktoon's JB rom or you will get error 7. task650
- This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this - check MD5 sum.
- Update or try a different recovery.
- Remove the build assert in the updater-script.
Last edited: