Develop Bugs

Post all Fixes/Work-arounds RE: [ROM]CM7-GX4(EX+4G)

Let's build a FAQ here to help everyone get the full benefits of this outstanding ROM! Let's not make this into a discussion thread so that it makes everyone's search alot easier to find what they need. I'm starting this since there is no FAQ or WIKI in the OP.
I'll start first...
MMS FIX: clear cache for your messaging app (whatever you are using) under Settings >>> Applications >>>Manage Applications>>All. Reboot into recovery, clear cache, Dalvik cache, and finally reboot.

I already posted this in the general forum but this seems more fitting. I installed CM7 on my Evo earlier today. Everything was amazing until I realized that the market app wouldn't work. Within a second of me tapping the icon I was back at my home screen. I wiped all my caches and wiped+ reinstalled CM7 but still no luck. I've reverted to a backup ROM for now until I can get this sorted out. Any help would be awesome!

Issue:
Bad Front Facing Camera Pics "Dark"
Bad Video on any setting other than "High"
Tried Different kernels:
SavageZen 0.0.3, 0.0.4, 0.0.5 no luck

Issue: Titanium Backup does not successfully install when I attempt to update from the market. Think it might have something to do with the GPS, but I don't know...
Attempting workarounds, anyone know if I can use Root Explorer to remove it and then re-download?

Hi Everyone
I would like to share what I have learned over the last week. First off. AWESOME ROM. Great job!!!
I discovered after many hours that a backup with Clockworkmod 3.0.0.5 does not restore on my HTC EVO no matter how I do the backup (i.e. manual or using Rom Manager). Good news is that if you revert back to 2.5.0.7 when you do the backup (either method), I have success on restore. I did the GPS fix by reverting back to a prior image and using the ##GPS….# method and then restored my CM7 and I am happy to report GPS is working.. I did flash Savaged-Zen-V0.0.5-CFS-HAVS-NoSBC-WiMAX-GB-Signed to see if that would improve things. I did them together so I can’t be totally positive which one fixed it. I believe the combination works though. 4G also works which is good news. I do not see signal strength or the icon in the notification but the Wi-Fi shows it is 4G connected (does not say sprint though). It also is consistent in range with what I had with the Sense ROM.
I also just confirmed that the Wi-fi hotspot also works on 3G (no 4G in my hood). I connected my laptop and ipad without problems and connected to the internet.
I tried everything flashing / restoring, etc to get Sprint Voicemail to work. I gave up and downloaded a program called YouMail. So far, I am happy with it (works very similar to the Sprint product and it is free).
Camera appears to also be working. I will do more tests.
I will keep you posted on the things I learn over the next few weeks. I hope some of you find it helpful.
I will answer questions if I can. Thanks for the great ROM. I look forward to updates.
Rico

Issue: No Disk Mode after flashing tast kernel.
Fix: Use savage kernel. Make sure its a Gb wimax kernel.
Issue: No WiFi tethering (bluetooth and wifi tethering both broken). I won't work in 3 or 4g.

xfullmetal17 said:
Issue: Titanium Backup does not successfully install when I attempt to update from the market. Think it might have something to do with the GPS, but I don't know...
Attempting workarounds, anyone know if I can use Root Explorer to remove it and then re-download?
Click to expand...
Click to collapse
Tried that. Didn't work. Used Root Explorer to search for all Titanium backup files. Erased. Checked in /system/app nothing there as well. Checked in Applications list to see if it was there, it was. Can't seem to erase it completely off. Tried to redownload and reinstall from market. No go.

hey guys, for the mms fix, i can't seem to get that to work. mainly because the clear cache buttons are greyed out for the original messaging app and chompsms

bhsvault said:
I already posted this in the general forum but this seems more fitting. I installed CM7 on my Evo earlier today. Everything was amazing until I realized that the market app wouldn't work. Within a second of me tapping the icon I was back at my home screen. I wiped all my caches and wiped+ reinstalled CM7 but still no luck. I've reverted to a backup ROM for now until I can get this sorted out. Any help would be awesome!
Click to expand...
Click to collapse
You need to flash the proper Gapps for CM7. Do a google search for 'Gapps-GB' and you should find the download for it. Save it to your Sd-card and flash it using recovery. Hope this helps.

I am not sure what the problem is. Are you using the built in wi-fi tethering. I read somethere what the tethering app does not work.. I have had no problems with the build in wi-fi tethering. I ran my phone yesterday with GPS and some calls, text msg, etc and left it on overnight to see how it would do. I woke up and still had 38% after over 20 hours since last charged.

I am currently expierencing terrible wifi reception on my evo, also the data seems to go in and out of connection sometimes
also my mms is not working properly and I cannot seem to fix it, I have ran fix permissions in ROM Manager, Clear cache in settings, and reseting app data in Titanium... I dont want to wipe my phone (too many settings to mess with to get it back to how I like it ) but I am willing to if thats how it will get fixed...

CM7 - Most Apps Force Closing

Hey guys,
I just flashed the CM7 RC, which CM stated to pretty stable and fine for everyday use. I downloaded the RC from within ROM Manager and did a wipe. Install went perfect and everything was as it should be. I then go into Market to download the Google Apps. When I try to open any of these apps though they all force close. I went and tried to download a few other apps(FB, Twitter, etc) and they all do the same. The apps that came with the ROM (Torch, FileManager,ROM Manager) all work fine...
I tried a reboot, but the problems continue.
I guess I'll try to flash again form the SD-Card this time to see if it has the same problems.
Any suggestions would be appreciated.
Thanks,
Incredible510

Read through the development thread, people are having problems with rc 1 build.
For the time being, im sticking to nightliessince they are stable most of the time.

Ok thanks.
Do you know the differences between the RC and the nightly builds?

Incredible510 said:
Ok thanks.
Do you know the differences between the RC and the nightly builds?
Click to expand...
Click to collapse
From what i have gathered, nightlies continue to be in development wirh new rhings being added. Rc are bundled wirh the most best applicable things and left as is...or to shiw what the final build will look like.
Nightlies continue even after final build most of the time.
A senior member might want to chime in on this as well.
Edit....in newer builds my simeji app seems to be colliding with android keyboard ap via adw launcher...dont know what to do haha.

Apps will FC because its gingerbread. Also this is a known problem with GB and CM7.
Sent from my ADR6300 using XDA App

Oh ok. So its on the app side.
So i went and downloaded it again, this time flashing from the SD-Card. Everything came up fine, but when I started up I didnt go through a google account setup and theres no market.
Any way to get the market app?
Thanks

Here is the deal, first the permissions are not right when you are getting the FCs. Go into rom manager and click fix permissions. Also I thought this forum had intelligent members .... gingerbread is not to blame for any force closing. It is completely backwards compatible. I am running CM7 RC and it is working after 2 tries and fixed permissions. No problems.
Sent from my ADR6300 using XDA App

And you forgot to download the Google apps package with your CM7. You will have to redownload and reinstall to get the market back on until they release a separate Google apps add on for GB
Sent from my ADR6300 using XDA App

Ok thanks, but where is that Google Apps Package download?
It came with the download from ROM Manager, but not when I downloaded it from CM's site(http://forum.cyanogenmod.com/files/file/220-update-cm-700-rc1-inc-signedzip/).
If you could direct me to the download that includes the GApps it would be really appreciated it.
Thanks.

jorny32 said:
Here is the deal, first the permissions are not right when you are getting the FCs. Go into rom manager and click fix permissions. Also I thought this forum had intelligent members .... gingerbread is not to blame for any force closing. It is completely backwards compatible. I am running CM7 RC and it is working after 2 tries and fixed permissions. No problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thank You So Much!
This fixed all problems.

I'm also running CM7 RC1 with zero problems. When I first installed it, I got tons of FC's on the first boot. I rebooted into recovery and did a factory reset. After that, everything has been running fantastic.

Everything has been fine for me running cm 7. Now today, force closes on anything internet related. Browsers, reader, market etc... Have fixed permissions, flashed clean on a factory reset. Any ideas?? Also are there other apps that fix permissions besides rom manager?
Edit: Got everything working off a clean install. Oh and cwrecovery fixes permissions (face palm).

Maybe unrelated but why does setcpu never give an accurate core speed report using the widget? Example: two hours ago I set the CPU to 1113 to test neocore. After the test I idled it back down to 998. The widget never updated and now two hours later it still hasn't updated and it still says its at 1113. The only way to get the widget to reflect my current setting is to remove it and then place it back on the screen.
DINC // CM7 RC2 // SLAYHER#9

[Q&A] Task650's AOKP(FAQ) (AT&T)(SGH-I747)(3-12-14)

This thread has been created strictly for
Questions and Answers​
[SIZE=+2]Dealing with[/SIZE]​
AOKP KK ​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow Task on G+
​
[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. ​
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
.
​
Please read the OP in dev thread carefully on latest update, it has some very important info in it.
​
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
POST 2
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​
POST 3
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.
http://forum.xda-developers.com/showpost.php?p=20972167&postcount=3
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://forum.xda-developers.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
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.
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.
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.

FAQ, Known bugs and helpful tips.
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.
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​
MD5 sum​
Modems​
OTA Update/Recovery​
OLD/OUTDATED versions of this ROM​
Performace settings​
REQUESTs​
​
SD CARD
Here is a guide for formatting external SD card without reader are here.
Guide_to_format_external_SD_card_without_reader.
Here is another way to format SD card http://www.online-tech-tips.com/comp...ive-to-fat-32/
My SD card is not working. Try this. EaseUS
Will my 64 gb sd card work? Except it works fine with a 64GB card. http://rootzwiki.com/topic/28124-doe...card-standard/ The SGSIII is the first phone to support exfatl, but the support is Kernel based, some people are having trouble with the replacement kernels and exfat support. The solution is to force it to format in FAT32. http://www.online-tech-tips.com/comp...ive-to-fat-32/ I know, because I've done it. --- Don't respond without actually doing research. I have no problem spoon feeding information, especially when the information you put out there can increase misinformation. The SGSII also supports a 64GB card as well. http://androidforums.com/samsung-gal...ing-sgsii.html
http://teamw.in/exFat
Facebook won't sync.
Try Friendcaster or facebook_contact_sync.
FAST CHARGE
Storage options will not work with fast charge on.
FAUX SOUND
Faux_sound_in_Playstore
Task has added patches to be able to use this. It is worth the money.
Disable HW to stop flickering
Disable HW tick will not stick after reboot. This is the way it is suppose to be. This will still help with any type of flickering, usually.
If you are having some weird sh!t going on.
Redownload rom and gapps
Wipe data factory reset
Wipe dalvik and cache
In mounts and storage select Format System
Then flash rom and gapps
Reboot task650
Gapps
You must flash Gapps AFTER every flash of the ROM.
Use the Gapps in Task's OP or any Gapps package you want. They are just Google apps.
Sometimes you may have to flash Gapps twice - they have been notorious for not taking the first time.
Read the OP to see if a new version of gapps is required.
UPDATING APPS INCLUDED IN GAPPS
Delete app you are wanting to update with titanium back up.
Reboot
Install newer version of app
Google now
Phone language has to be set to english for google now to work.
My google apps are working correctly. If it was just the play store force closing all you would've needed to do is reflash gapps. gapps is notorious for not taking the first try. but you always have to flash gapps after a rom install and make sure to clear cache and dalvik. no issues should occur if those steps are taken. Task. Make sure you are using the correct gapps!
Task and Ktoon do not support google wallet. There are fixes available but don't ask Task or Ktoon to fix it.
You can't remove the google search bar with default launcher but you can with nova or apex.
GPS
GPS not working correctly isn't always the ROMS fault. Sometimes its the satellites.
Make sure you have internel GPS selected.
Try flashing original stock and then come back to this rom if you have flashed a TW based rom.
To change your number of home screens
You must use Apex or Nova launcher, possibly some other third party launcher. But the default launcher will not allow you to do this.
You must use Nova or a third paryt home screen to disable search bar.
If you flash other things like inverted gapps or change things from the original packaging of this rom and something goes wrong or doesnt work. Think about it. We cannot support those issues here. This thread is for this rom and gapps that are posted in the OP. Thanks. task650
Inverted gapps are awesome but not supported in Tasks thread.
If you are using inverted gapps and having problems - full wipe and reinstall rom and gapps in the OP and see if problem still persists.
Go here for support of inverted gapps. > http://forum.xda-developers.com/showthread.php?t=2138156
IRC
Task has started and IRC channel for his rom. ##Task650_AOKP
KERNEL:
If you are using any kernel other than the one packaged with this ROM please post questions and problems to the appropiate kernel thread.
you need to understand that all devices are NOT created equally. one kernel might work awesome on my device while at the same time it may work horrible on your device. so to say that Ktoonsez says it works awesome, that means it works awesome for him. It has nothing to do with how it will work for you. If the symptoms that you're talking about are happening with that kernel it's obvious that your device doesn't like that kernel. Easy fix. Use a different one.
If you are using Ktoon's awesome kernel and experiencing problems, try reflashing with the kernel included with this ROM and see if the problem still persists. This may help understanding if the problem is kernel or ROM related and will help benefit development of both.You can full wipe and reflash rom and gapps to be back on original kernel.
If you wish to run another kernel other than what comes with the rom, Task suggest loading rom with included kernel, set up phone, then flash the kernel you want.
Governor/IO scheduler
Change these in performace control in settings
If you do not tick set on boot they will revert upon reboot.
This is a safety check in so you can try settings out before you make them permanent.
Last report in Feb is that Task uses row and interactive as his settings.
LED
LED charging works exactly as it should.
0%-%10 = Red
%10-%90 = Yellow
%90-100 = Green
You can't change the colors for LED Charging unless you download the source and rewrite that portion of code.
You can only change the colors for the Notification LEDs not battery indication color.
Make sure you have "pulse notification light" checked - uncheck to turn LED notification off.
Some colors will not work. Test LED color before relying on it.
Go here for some LED color talk. http://forum.xda-developers.com/showthread.php?t=1890774
DO NOT USE LIGHTFLOW WITH THIS PHONE - DOESN'T WORK WELL. LED CONTROL WORKS FINE ON ITS OWN.
To set LED for miss phones calls>>
choose Activities>Contacts>Phone/ activities.CallLogActivities
Please do not post links for Task's ROM or gapps. He wants to keep count of downloads. Thanks.
If you don't have LTE in your area it's not draining your battery.
AT&T is phasing out the old non LTE apn either way so we will all be using the same "LTE" apn. Network mode has nothing to do with you if your on AT&T service. That's only for the Canadians.
Also see 14 and 15 in FAQ post 1.
MD5 sum is located in goo.im via download link.
MODEMS
This ROM does not include a modem. You will have whatever you had.
Modems are location based. Try this and see which one works best for you.
Any modem questions should go HERE.
OTA Updates/RECOVERY
OTA updater is a convienence. If you have problems using the OTA update just flash manually through CWM or TWRP.
CWM 5.5.0.4
cwm flashable
http://www.mediafire.com/?8rs5rq2a0ldhgut
TWRP X.X.X.X
http://forum.xda-developers.com/showthread.php?t=1793224
Read this >>>> http://teamw.in/androidmultiuser about the 0 folder
Old/out dated versions
Go here> http://goo.im/ to get old/outdated versions of this ROM.
See Kernel for performace control
Use TRICKSTER for stable reliable control of these features
Last report in Feb is that Task uses row and interactive as his settings.
REQUESTS AND ETA'S:
Do not ask for requests, ETA's, features or changes on XDA use G+ request section.
Donations are for if you appreciate his work. He will not turn this into a job.
DO NOT ASK FOR ETA'S. THIS IS ANNOYING AND ONLY HINDERS DEVELOPMENT.

FAQ, Known bugs and helpful tips.
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​
​
RIBBONS
If you can't delete the icons in ribbons just use the menu and reset them.
Ringtones​
There is not a repeating ringtone on this rom(AOKP). Get a longer ringtone if you want more notification.
Ringtones are located in system/media/audio/notificating or ringtones depending on what you are looking for.
You need to set the permissions to rw-r-r and then reboot.
More RomControl Settings added
It will take some time to get all the rom control settings back in, be patient. This happens after any new OS.
If you see a major update as in a new kernel or OS, some items will take some time to be added back.
ROM CONTROL: This is a very customizable rom, please spend some time and learn the many features it has.
ROM MANAGER APP
It is advised not to use ROM MANAGER APP. Notorious for causing problems.
Runtime
Art or Dalvik
Art_VS_Dalvik
See_what_Task_has_to_say_about_it
SCREEN SHOT
To take a screen shot hold volume down and power button at the same time.
You can add screenshot option to the power menu.
Changing the color of Signal and wifi only changes the color in text mode.
SMS/MMS
MMS not downloading
Some suggestions offered that have helped people with MMS.
Add "hipri" in your APN type and save. This has been reported by several people to help.
This is being seen on several phones with different roms and even iphones. Call ATT.
Try auto retrieve on.
Set Authentication type to "none"
In text client make sure "auto retrieve" is checked in all boxes.
This ROM does not having a problems sending MMS. It is most likely an ATT problem. But you can double check your APN to make sure it is not on your end.
If you are using a third party app to SMS/MMS it is not supported by Task.
If you want to use the quick reply option make sure you have it checked in settings.
SOUND/VOLUME
If you are not getting sounds on something check your quite hours.
Make sure you have not accidentally toggled silent/vibrate.
Take a look at THIS in the play store. It's awesome.
Swag Pink hat - It's a joke. Either you have it or you don't. As cool as Task makes this phone he can't actually help you in this area.
Themes
If you are having graphical glitches and using a theme, try removing any theme and see if it still persists.
CM10 themes should work on this rom but if you encounter problems do not bring it to the thread.
Go HERE for themes.
Toggles
Are located in ROM control
The toggle for DATA is called SIGNAL
TOUCHWIZ FEATURES:
This is an AOSP rom, touchwiz(sammy) features are not incorporated into this rom. Reason you ask? Framework!!!
Chances are something you want from TW is probably in the app store.
Voicemail number missing. Use your call forwarding number.
Try this for ATT visual voicemail.http://forum.xda-developers.com/showthread.php?t=1641981
If your wifi won't stay on while phone goes to sleep check settings to keep on during sleep.
If your phone sometimes drops wifi check settings and uncheck avoid poor connections.
These are found under advanced settings in WIFI.
If you are having problems connecting or using tethering try changing your SSID and try unsecured.
Most of the time lack of WIFI connectivity is usually cause by router settings or router itself.
IF you are having wifi connections problems try rebooting your router.
ROGERS WIFI TETHER
Tether will not work on 4G/LTE unless you use a third party app.
Task can not test/fix since he obviously doesn't have a rogers phone.
Changing the color of WIFI/signal colors only changes the color in text mode.
Useful LINKS
KT747_KERNEL_BY_KTOON
BACKUP/RESTORE/FIX_IMEI_&_DATA_RESTORE_TOOL
BETTER_BATTERY_STATS]
FULL_NV_BACKUP_&_RESTORE
TWRP_RECOVERY
ATT_I747_-_(GUIDES/ROMS/ROOT/RECOVERY)
MODEMS_FOR_I747
AOKP_LED_COLORS
FIXING_BATTERY_DRAIN_ON_YOUR_S3
Task_custom_boot_animations
Titanium_Backup_User_Guide
Guide_and_Q&A_AOSP_LTE_ ​How to Update (Always follow OP directions)
Make sure you have CWM
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 JB/CM10 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
Troubleshooting/Comprehensive Re-flash
(Optional, but recommended) Back up any apps you may want restored (Titanium Backup's batch mode (a PROfeature) makes this painless! Set TB batch filters to User type only. DO NOT RESTORE SYSTEM DATA! Hell, don't even back them up.
Re-download the latest version of the ROM and Google Apps (even if it's the same version you have) from the OP. It's possible you may have a corrupted download.
Reboot into recovery. Follow the process below exactly, and there should be no NEED for a kernel cleaning script.
Wipe cache partition
Advanced > Wipe Dalvik Cache
(Optional, but recommended) Mounts and Storage > mount /system & /data
Install zip from sdcard > choose zip from sdcard (wherever you saved the download) > Flash [ROM] AOKP Task & Ktoonsez Run a Train (version)(TGFY ONLINE!!!).zip
(Optional, but recommended) Mounts and Storage > mount /system & /data
Install zip from sdcard > choose zip from sdcard (wherever you saved the download) > Flash gapps-jb-(version)-signed.zip Jelly bean version only
Reboot
PS. Sometimes all that is needed is a reboot again. Doesn't hurt to try it.
Test ROM, BEFORE restoring *any data* (if you did a full reset). DON'T RESTORE SYSTEM DATA! You have been told twice!
Fixing permissions in CWM/TWRP helps fix MANY *random* glitches.
If you still encounter problems, do a FULL reset ( Recovery > Wipe data/factory reset) & follow the steps again. THEN, you can report issues!
You may have to redownload ROM and/or Gapps. Sometimes you can get a corrupt download that will cause issues. It happens.
Thanks to avidmovies for the above instructions from S II AOKP FAQ. (with small modifications)

FAQ, Known bugs and helpful tips.
reserved for grubby by the archangel

I get the "AOKP Statistic" all the time. Clicked on it (was disabled by default) and closed it.
Unfortunately it came back after a few minutes. So I enabled and then disabled it. No change.
Anyone solved zhis problem or does anyone experienced the same?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Will svoice work on this if you manually install it?

3NDL3R said:
I get the "AOKP Statistic" all the time. Clicked on it (was disabled by default) and closed it.
Unfortunately it came back after a few minutes. So I enabled and then disabled it. No change.
Anyone solved zhis problem or does anyone experienced the same?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not have that problem I would redownload the ROM and do a fresh install aka a a full wipe off all data that tis the first thing to do and see if fixes the problem.
from my AOKP galaxy s3

iastonish said:
Will svoice work on this if you manually install it?
Click to expand...
Click to collapse
It will work but not to the full potential that it has on TW based roms. I believe it will not speak back plus a few other bugs.
If you would like something like svoice but on an aosp rom then I'd suggest trying cm10 and using google now.

I flashed the rom last night but when I woke up, I noticed my contacts still did not sync their pics with Facebook. Is this a known issue? It's not a big deal, but I prefer to have contact pics.
Via my Samsung Galaxy S III - rooted

Jhvoorhies said:
I flashed the rom last night but when I woke up, I noticed my contacts still did not sync their pics with Facebook. Is this a known issue? It's not a big deal, but I prefer to have contact pics.
Via my Samsung Galaxy S III - rooted
Click to expand...
Click to collapse
Not heard of before, however fb has never been stable w/ Android. You will find most cases devs will not include w/ rom builds, for that reason

Alright I'm a little confused here. From what I can tell, everyone seems to indicate the Camera is working 100% - but it's still FC'ing for me. It opens fine, shows the live preview for about 2-3 seconds, then force closes.
My install procedure:
Latest CWM recovery (non-touch)
Wipe cache
Wipe dalvik
Wide data/factory reset
Install AOKP (latest 07-16 build)
Install gapps (ics 04-29)
Reboot
Didn't touch a single setting in the ROM.
I've done this twice and the FC'ing persists.
Am I missing something, or could this be related to the fact that I have an I747M (Bell)?

tomween1 said:
Not heard of before, however fb has never been stable w/ Android. You will find most cases devs will not include w/ rom builds, for that reason
Click to expand...
Click to collapse
Yeah fb sucks for the most part, but with touchwiz, it syncs contact pics pretty much instantly.
On aokp, I just have tons of gray squares instead of the pics. I did a fresh install, and I still get the same thing happening.
Does the ktoonsez aosp kernel work better with this rom than the one that is included?
Via my Samsung Galaxy S III - rooted

CNAM Name Caller id for Rogers
Great ROM....just one issue for me
Rogers exclusive in Canada "name caller id" has issues. When call is received from someone who is NOT listed in contacts, I still get NAME of the person calling but Name doesn't stick in LOG and only number shows afterwords.
It works fine in stock ROM.
Can that be fixed? I can commit 5/6 beers as I know its your time. Thanks
This maybe helpful http://review.cyanogenmod.com/#/c/11168/

radeon_x said:
Alright I'm a little confused here. From what I can tell, everyone seems to indicate the Camera is working 100% - but it's still FC'ing for me. It opens fine, shows the live preview for about 2-3 seconds, then force closes.
My install procedure:
Latest CWM recovery (non-touch)
Wipe cache
Wipe dalvik
Wide data/factory reset
Install AOKP (latest 07-16 build)
Install gapps (ics 04-29)
Reboot
Didn't touch a single setting in the ROM.
I've done this twice and the FC'ing persists.
Am I missing something, or could this be related to the fact that I have an I747M (Bell)?
Click to expand...
Click to collapse
Try this full wipe flash rom. Don't instal gapps. Boot the phone see if the camera works. If it does then clear cache and dalvik then flash gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

radeon_x said:
Alright I'm a little confused here. From what I can tell, everyone seems to indicate the Camera is working 100% - but it's still FC'ing for me. It opens fine, shows the live preview for about 2-3 seconds, then force closes.
My install procedure:
Latest CWM recovery (non-touch)
Wipe cache
Wipe dalvik
Wide data/factory reset
Install AOKP (latest 07-16 build)
Install gapps (ics 04-29)
Reboot
Didn't touch a single setting in the ROM.
I've done this twice and the FC'ing persists.
Am I missing something, or could this be related to the fact that I have an I747M (Bell)?
Click to expand...
Click to collapse
I had your same issue. It took me flashing cwm from rom manager to get a working camera
Sent from my SAMSUNG-SGH-I747 using xda premium

crash822 said:
I had your same issue. It took me flashing cwm from Tom manager
Click to expand...
Click to collapse
Sorry man, my manager has never been good

Is there any way to reformat my 64gb microSD to FAT32 without a USB reader? AOKP doesn't want to recognize my card in exFAT it seems.
I know there's the SGS3 UMS app, but I don't think it works for AT&T phones.

Aanyone seen any icon packs for the lockscreen? Chrome is the only icon that doesn't follow the same theme as the other icons on the lock screen. I found a post in the nexus forums where someone made some icons for the lock screen but whenever I try to choose one of those icons it fails asking me if I am sure my SD card is mounted
Sent from my SAMSUNG-SGH-I747 using xda premium

Is there an option to use the original Samsung camera app?
I tried installing from a backup I have of the original stock ROM, I just get an error of 'package not installed'.
Thanks,
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

aviramido said:
Is there an option to use the original Samsung camera app?
I tried installing from a backup I have of the original stock ROM, I just get an error of 'package not installed'.
Thanks,
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Samsung camera app requires touchwiz. Aosp based roms like aokp do not have touchwiz
I am on phone so expect errors

Front Camera Lag/Stretch in 3rd Party Apps

I'm having an issue on my SPH-L710 where the back camera works in all cases, but the front camera is laggy and stutters, and has a skewed / stretched aspect ratio in all applications except the camera app itself. That is, the front camera works as expected, fast and looks normal in the stock camera app or the google camera app, but when it is embedded in another such as facebook, snapchat, etc., it exhibits the problems above.
This is not a problem on ND8 (4.4) stock, but has happened on all the custom roms I have tried in the list below :
Slim-d2lte-4.4.4.build.7.0-OFFICIAL-5979
Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
cm-11-20140814-NIGHTLY-d2lte
cm-11-20140805-SNAPSHOT-M9-d2lte
BeanStalk-4.4.4010-20140722-d2lte
Quantum.4
I do a factory wipe and erase the cache every time. I have tried force closing the camera and gallery apps and clearing their data. None of these solutions have worked. What roms are other people using that don't have this issue? If the issue is this widespread, I would think there would be more posts regarding it.

I just tested the front camera on Facebook and another app. I was not able to replicate the problem and experienced no issues with the front camera preview.
Tested and working on CM11 20140812 Nightly w/ stock kernel and just finished testing with DKP kernel.
It could be hardware related if you are not seeing this as a common issue in forums.

Higgs_Boson said:
I just tested the front camera on Facebook and another app. I was not able to replicate the problem and experienced no issues with the front camera preview.
Tested and working on CM11 20140812 Nightly w/ stock kernel and just finished testing with DKP kernel.
It could be hardware related if you are not seeing this as a common issue in forums.
Click to expand...
Click to collapse
Can't see it being hardware related if the camera works just fine in the stock camera. I'll install that nightly and see how it works.

tulient said:
Can't see it being hardware related if the camera works just fine in the stock camera. I'll install that nightly and see how it works.
Click to expand...
Click to collapse
Right. You did mention that detail. Hope another nightly works for you.

Just tested cm-11-20140812-NIGHTLY-d2lte and I am having the same issue. No idea what could be wrong. Are you sure its not skewed in any way on the front camera?
I wiped and installed the nightly and gapps-kk-20140606-signed, went straight to google play, installed messenger, and tested the camera. No funny business, and it doesn't display correctly.

tulient said:
Just tested cm-11-20140812-NIGHTLY-d2lte and I am having the same issue. No idea what could be wrong. Are you sure its not skewed in any way on the front camera?
I wiped and installed the nightly and gapps-kk-20140606-signed, went straight to google play, installed messenger, and tested the camera. No funny business, and it doesn't display correctly.
Click to expand...
Click to collapse
I am 100% sure there is no skewing, distortion, stretching etc. on apps accessing the front camera outside of the stock camera app.
The only difference between our setup is that I use this GAPPs package:
pa_gapps-stock-4.4.4-20140629-signed
I also use the DKP kernel, as I mentioned before. But, as I also reported, stock kernel worked fine for me, too.

No luck even with GAPPS pa_gapps-stock-4.4.4-20140629-signed with and without the DKP kernel dkp-aosp44-d2-20140726.

tulient said:
No luck even with GAPPS pa_gapps-stock-4.4.4-20140629-signed with and without the DKP kernel dkp-aosp44-d2-20140726.
Click to expand...
Click to collapse
I was reading around a bit more on the Internet. Have you tried going into the Google Camera app settings when you launch the camera from one of the apps in questions and changing the resolution? I read on a few sites that this might fix the stretch issue. I'll keep digging around.
I don't suspect that it's a code issue, since mine is working normally. Do you have more than one camera app installed that is possibly tweaking the resolution? Just a thought.

I have tried to change the picture size from 1:1 to 4:3 of the front facing camera in the camera app, as well as change the resolution from 1.9 to 1.3, but neither change is reflected in the facebook messenger camera. I also tried using no GAPPS and installing the facebook messenger APK only after a fresh install, and still have the problem, so it's not a separate app causing the issue. Are you sure you're using a SPH-L710?
I'm assuming the problem is in whatever base all these custom roms are built on, but since it's working for you, I have no idea.
For the record, I am installing CM11 with recovery CWM-6045_touch_d2spr_naddict and the other roms philz_touch_6.48.4-d2lte only because CM11 wont install with philz due to assert failures.

tulient said:
I have tried to change the picture size from 1:1 to 4:3 of the front facing camera in the camera app, as well as change the resolution from 1.9 to 1.3, but neither change is reflected in the facebook messenger camera. I also tried using no GAPPS and installing the facebook messenger APK only after a fresh install, and still have the problem, so it's not a separate app causing the issue. Are you sure you're using a SPH-L710?
I'm assuming the problem is in whatever base all these custom roms are built on, but since it's working for you, I have no idea.
For the record, I am installing CM11 with recovery CWM-6045_touch_d2spr_naddict and the other roms philz_touch_6.48.4-d2lte only because CM11 wont install with philz due to assert failures.
Click to expand...
Click to collapse
Yes. I have a SPH-L710. I encourage you to ensure that you are using the correct and most current version of Philz recovery for our device, as I am able to successfully install CM11 using Philz.
Please download and try the latest Philz recovery here, and try wiping and reflashing the ROM and GAPPs.
PhilZ Download Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
(Came from this thread: http://forum.xda-developers.com/showthread.php?t=2446393&page=56)

The following procedure fixed the front facing camera 3rd party apps for me, but in turn now the camera app itself is broken. Still trying to figure this out.
Flash philz_touch_6.48.4-d2lte.tar.md5 with Odin 3.09
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Ensure root (apps) is enabled on ROM (slimkat defaults to disabled)
1. Enable Developer Options - Click Settings / About Phone / Build number 5 times
2. Enable root (Apps only) - Developer Options / Debugging / Root Access
Install root browser (jrummy)
Install facebook messenger
Verify camera does NOT display correctly in facebook messenger
Using root browser, delete system/lib/hw/camera.MSM8960.so (Give root browser permission to superuser when prompted)
Using root browser, rename system/lib/hw/camera.vendor.MSM8960.so to system/lib/hw/camera.MSM8960.so
Verify camera still does NOT display correctly in facebook messenger
Reboot (Reboot necessary? Camera saved in memory?)
Verify camera does display correctly in facebook messenger

tulient said:
The following procedure fixed the front facing camera 3rd party apps for me, but in turn now the camera app itself is broken. Still trying to figure this out.
Flash philz_touch_6.48.4-d2lte.tar.md5 with Odin 3.09
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Ensure root (apps) is enabled on ROM (slimkat defaults to disabled)
1. Enable Developer Options - Click Settings / About Phone / Build number 5 times
2. Enable root (Apps only) - Developer Options / Debugging / Root Access
Install root browser (jrummy)
Install facebook messenger
Verify camera does NOT display correctly in facebook messenger
Using root browser, delete system/lib/hw/camera.MSM8960.so (Give root browser permission to superuser when prompted)
Using root browser, rename system/lib/hw/camera.vendor.MSM8960.so to system/lib/hw/camera.MSM8960.so
Verify camera still does NOT display correctly in facebook messenger
Reboot (Reboot necessary? Camera saved in memory?)
Verify camera does display correctly in facebook messenger
Click to expand...
Click to collapse
All you did there was delete and rename a camera library, which are stored in the kernel, and that I perceive to be the reason the camera broke.
Are you savvy on ADB?
I think at this point the best thing for your to do would be to:
Flash ROM Slim-d2lte-4.4.4.build.7.2.1-WEEKLY-6080
Flash GAPPS pa_gapps-stock-4.4.4-20140629-signed
Get everything back up to a freshly flashed ROM with GAPPs, then:
1. Enable Developer Options
2. In Developer Options, enable USB debugging
3. Connect phone to USB port on PC
4. Launch ADB
5. Input command: adb devices (to ensure the device has been detected by adb)
6. Input command: adb logcat
7. Launch and switch to front camera in 3rd-party app
8. Disconnect USB cable
9. Copy and paste text from ADB terminal into a Notepad document. Save document (e.g. logcat.txt).
10. Upload Notepad document as attachment (.txt file) to this thread on XDA.

Yes, well by deleting the one camera library and replacing it with the camera.vendor, everything works exactly as it should in the 3rd party application. Its just when using the stock camera app where it doesnt work now - essentially making the opposite situation I started with. FYI with the fix the stock camera looks fine and can take a picture but usually closes and forces a reboot right away.
Here is the logcat for opening messenger, opening the camera option and snapping a (stretched) picture.

It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
EDIT: My changes didn't help any.

decimalman said:
It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
Click to expand...
Click to collapse
Sir, your presence here is most appreciated. Thank you.

decimalman said:
It seems I've been summoned.
I didn't see a whole lot in the logcat (or rather, the camera spews so much debug info that nothing stood out). So far, I'm able to reproduce the stretched preview thing but not the lag. I think the lag probably depends on the app, so I'll try a few more.
I think I know what's causing the stretching, but I won't know for sure until I get a ROM built.
EDIT: My changes didn't help any.
Click to expand...
Click to collapse
Thank you tremendously for trying!
Any idea why it would only be affecting his phone in other apps?

Guessing there's no solution to this until someone in the CM main trunk figures it out.

[ROM][CM12.1] UNOFFICIAL CM12.1 for LS970

Installation Instructions:
https://wiki.cyanogenmod.org/w/Install_CM_for_ls970
Click to expand...
Click to collapse
Changelog:
​20160814:
Updated using branch cm-12.1​20160127:
Updated to CM-12.1 using codebase cm-12.1-YOG7D
Updated libs from mako, which fixes GPS, Encryption, & some dirty log messages.​
Click to expand...
Click to collapse
Special Thanks:
Looking at the commit log, I've got to say thank you to Shelnutt2 and Ricardo Cerqueira. Seth, for his work on porting this device & permission to post this build, and Richardo for maintaining the gproj kernel.
Click to expand...
Click to collapse
I've been using this with Ting. Seems more stable than the CM-11 build that I was using. Mms & cell data are the two things that do not work out of the gate for me. Wondering how this shapes up with Sprint. I vaguely remember cell data working, but I don't think the default mms app did. However, I was able to use a third party mms app for pictures.
If this works well for people I'll see what I can do about getting my changes pulled upstream.
XDA:DevDB Information
UNOFFICIAL CM12.1 for LS970, ROM for the Sprint LG Optimus G
Contributors
fuzzy7k, Shelnutt2, Ricardo Cerqueira
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-01-28
Last Updated 2016-08-17

What gapps version to use?
Thanks for providing this! I've installed it, to replace my cm-12-20151108-NIGHTLY-ls970.zip ROM. But I haven't been able to find a gapps download that will work with this (all Google services keep crashing) or fail to installed (Status 6). Any help will be appreciated.
Thanks!

gapps version
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.

For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate." Have you run into this issue? Any known fixes?

For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate."
Click to expand...
Click to collapse
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.

geodosch said:
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
Click to expand...
Click to collapse
Yeah I just went through unrooting and going to stock (where it worked fine) and now tried again to install without luck. I don't understand this problem or what could possibly be the issue at this point.
Edit: I have noticed that I'm not seeing my 5 GHz network although it was available in stock.

Profile switcher
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.

geodosch said:
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
Click to expand...
Click to collapse
Hey geodosch, same experience here with pop up errors with one difference, I was not able to get into Play Store... I only have four com.google.* green droid icons, and after clicking them I get 'App isn't installed'. Which gapps did you install, any other tips?
Many thanks!

I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!

A couple of issues
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.

Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.

curiousGeorge said:
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
Click to expand...
Click to collapse
Did you click the "Downloads" tab near the top of this topic? (Between "Discussion" and "Reviews") There should be a link there to "cm-12.1-20160127-UNOFFICIAL-ls970.zip", dated 2016-01-28.

Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
geodosch said:
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
Click to expand...
Click to collapse
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?

Ah, looks like I was right. It's the silly SELinux thing. The trick is to go here http://forum.xda-developers.com/showthread.php?t=2524485 and set the phone to permissive. Which you can totally do because you can go into the build info and click build number until you get "developer mode" enabled and enable root access in apps. Then everything works perfectly, even from a seemingly glitched install, regardless of GApps version. Pretty nice eh?
I'm gonna let everything update and then try reenabling SELinux, for kicks.
[edit]Ah, rebooting screws everything up again until the SELinux changer finally loads and changes things to permissive. So it doesn't exactly stick at boot. Still looking for a permanent fix...

curiousGeorge said:
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Click to expand...
Click to collapse
I'm running ClockworkMod 6.0.4.7. It's been a while since I originally installed the CM ROM, but I know I didn't have any luck with TWRP, though I can't say for certain that it was at fault... it may have been due to some other issue which I later fixed, and switching to CWM may have been incidental.

I've found that using the official CM recovery fixed my gapps woes.
On another note, GPS isn't working for me.

So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
geodosch said:
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
Click to expand...
Click to collapse
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
geodosch said:
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Click to expand...
Click to collapse
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.

geodosch said:
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
Click to expand...
Click to collapse
It's there, under "Power menu". Just search for power.

Nicene Nerd said:
On another note, GPS isn't working for me.
Click to expand...
Click to collapse
I read somewhere that you may need to get a lock in a ZVC build before flashing. Try that. It sounded like hog wash to me, and didn't work when I tried it. But, after updating the libs, all was fine. So, maybe both conditions must be met. On a positive note, I rarely have GPS enabled, but when I flip the switch, it comes on. So, it's not like you need to leave it on across reboots.

fuzzy7k said:
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
Click to expand...
Click to collapse
fuzzy7k said:
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
Click to expand...
Click to collapse
Glad to see you taking I look here. I really don't want to replace my Optimus G, since all phones now seem to be either low-end performance or over-sized. So I'm glad I can still keep mine going with these builds.
fuzzy7k said:
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
Click to expand...
Click to collapse
I hadn't tried adb before rebooting (Murphy's Law: whenever it happened I was often doing some time-constrained task, so I just rebooted as quickly as I could.) But the next time it happens I'll connect and check the logs. It's interesting that you mention multiple profiles, because it seems to have happened several times in my car, and I have profiles set-up to switch when the car bluetooth connects/disconnects.
If you're going to be poking around in the code, another issue that I've been having is the default app for the browser no longer seems to work consistently. I know this worked on an older CM12 build, and think it used to work on this one. But when something launches a browser I'm very often prompted for which one (Chrome or Browser.)
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
fuzzy7k said:
It's there, under "Power menu". Just search for power.
Click to expand...
Click to collapse
In the power menu, I see an option to switch users (which is disabled, since I don't have multiple users set-up), but I don't see an option for Profiles.