yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Agreed. I'm running the 10/16 build somebody built and posted yesterday and battery life is much better than M2 for me as well (had tried it with both CM10 kernel and Leankernel). Phone also got quite warm on M2.

And this build definitely feels snappier and smoother as well. Very impressed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mysterysnake:
I've been having the exact same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I only flash the latest Rom and latest gapps from cm or task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Did you try a different car?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
I see it has been reported to CM so hopefully it gets resolved soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BourqueJ:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
How are you able to tell when something has been reported? Where do you check?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mysterysnake:
You can check here http://code.google.com/p/cyanogenmod/issues/list
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
@Task650

Thanks for the custom build! It fixed all the glitches.

I had to nan back to 10/09, then to 10/17 to fix my video playback problem but then your build fixed the glitching.

Now will we have to look to you to get a new build after every nightly or do you think this fix might make it in an upcoming one?

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Look to me for nightlies? Nope. I was just helping out today. Cyanogen does a great job as it is. He maintains this device. So you will look to him and the CM Team for your nightlies. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
My issue may be similar in that the sound skips often and I have to try all kinds of disconnect/reconnect, reboot, repair, etc. I can't figure out the pattern. I never had this problem with s, s2, or any other Bluetooth source. There was one comment here that I should blame the Ford sync, but I have no reason to suspect the Ford, and circumstantial evidence that points to the phone.

Ford Sync, 2011 Edge
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
@Task650

Haha I was joking about all that. This rom could go no further and I'd be quite happy. I'd be interested to know more about what you changed, or pulled from the build to fix the glitches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
And no offense but I find your style... alil silly.. but I guess you got to have fun eh :good:

We are all on the same team anyways just different styles.

He added underwear to the device info.. Probably other stuff as well I am sure =p

*Yeah and fixing the flickering was nice*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Finished: SUCCESS

Ok so tonight it's positive

Package complete: /home/jenkins/android/workspace/android/jellybean/out/target/product/d2att/cm-10-20121018-NIGHTLY-d2att.zip""
6d83e85d44af82c519b0cdb8099708ea cm-10-20121018-NIGHTLY-d2att.zip

real	22m6.814s
user	152m34.336s
sys	20m47.106s
Saved manifest to /var/lib/jenkins/android/workspace/android/archive/core.xml
Archiving artifacts
Finished: SUCCESS

Link here:

cm-10-20121018-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
My style? Not sure I understand what you mean. Underwear is the name of my computer so its automatically added when I compile. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Task one question it's easy to fix Flicker issue? It needs compiling CM again or how do it works if you can fix tonight nightly would be amazing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bmvik:
just flashed to 10/17 from 9/25. wiped cache, dalvik, flashed, wiped cache, dalvik, fixed permissions, rebooted.

Everything functions but face unlock. It says Face Unlock couldnt start. tried fixing permissions again. didnt help. wanted to know if this is a bug before I wipe data... dont want to start from scratch with my apps, passwords etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
yes! Touch to clock/date to launch app has been merged into the 10/18 build! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
You named your computer underwear?

haha... That is pretty awesome.

But yeah when I tried AOKP out all the silly little "joke" things in there like the swag mode is what I was talking about for style.. More or less AOKP and CM10 are the same or atleast very similar in a lot of ways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Im on 1018 face unlock works perfect try updating to 1018 if not working clean flash!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
So we only have to wipe dalvik and cache right? Unles issues arrise.. And that keeps are folders and crap/homescreen/ apps ect ect

also is the flicking bug in 10/18?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. I couldn't think of a more appropriate name for my computer other than underwear. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Correct, and yes there's still flickering..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
In thaat case.. I am not installing it.

Thanks for doing science man :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
You can flash the 1017 that Task posted a previous pages back he fixed the flicker.

Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
How about someone reporting the flickering instead? Because if the flickering is back in this new nightly, there must be something wrong on their end. Mysterysnake gave me this link earlier: http://code.google.com/p/cyanogenmod/issues/list

I would do it myself, but I'm not sure how and idk what a logcat is or how to make one. If you don't know either, then maybe task can submit his fix there since I'd think he would know how to do so?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
I finally am putting use of my brand new iMac. I got parallels for free and I'm running Ubuntu, mountain lion, and Windows flawlessly all the same time. I am just finishing up and learning how to compile builds and what not. I have never been happier compiling my own builds. I have a transparent status bar with group mms. Best part is its my own personal build.

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
I just flashed the 10/18 nightly(full wipe) and have absolutely no flicker.

Edit: just discovered flicker in the YouTube app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
NO NIGHTLIES, UNOFFICIAL, SNAPSHOT, home-builds, or anything "based on"

CyanogenMod.

Just stable versions..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javadahutch:
Settings/Display/Notification Light

Settings/Display/Battery Light

I too would like an option to back up these settings...or to know if there is a way to safely restore backed up system settings with titanium backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
Ah, I saw that now. Well why are the top 24 issues on that page for the M2 snapshot then if it says that the issue tracker isn't for snapshots? Also, if that's not an issue tracker for the nightlies, then how are the people working on the builds made aware of the issues? Do they actually look through this forum? Cause I wouldn't think so. Sorry, still new to all this and learning a little bit about the process and everything each day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
No problems at all watching video on the way to work this morning. Nice job, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Flyarnk:
Can someone please test this and share the results

1.Connect to car audio/hands-free through Bluetooth.

2. Turn on Google navigation. Voice guidance should stream through car audio.

3. Make a phone call.

Ideally, when you make a phone call through car Bluetooth, voice guidance should stop. But here voice guidance goes on when when you are talking on phone. Very disturbing!

This issue has been there since weeks on all different CM builds. I have tried every possible trouble shoot but no luck. Tried clean install rom, reinstall maps etc etc.

Btw this issue is only with Google map voice guidance. If streaming music, it mutes during call as it should.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I have been backing up and restoring system settings for years without issue. Generally, the system data elements in green in TiBu can be restored without issue*. Settings 4.1.2-eng will keep your light configurations.

*Don't restore any system data from one ROM to another. Nightly -> nightly you're going to be ok, but dont be surprised when when you go AOKP -> CM or AOSP -> Touchwiz and it doesn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bmvik:
df-bpa-21 resolved

Wanted to share how I resolved play store error.

After having issues with Face Unlock force closing after doing 'dirty flash' from 9/25 to 10/17 (my previous post), I did full wipe etc - http://xdaforums.com/showpost.php?p=32723972&postcount=5660 Everything was great but I couldnt download purchased apps. It would show $price instead of Purchased. Also clicking on price gave me df-bpa-21 error. Tried clearing data in the "Google playstore" and

"Google service framework", resetting. No change. Fix permissions. No change. Closed Play store, disconnected from Wi-Fi, opened play store and it was fixed just like that. Looks like it needed to communicate with Google servers via data connection, not Wi-Fi, to get going.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Hi

What could cause the original roms and cm10 to have a such a diff of benchmark?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I hit thanks instead of quote. Ugh... Anyway, maybe because it is a better random number generator on certain roms? Benchmarks mean nothing.

Edit: Removed pictures, because HUGE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankJL_:
I dont understand the obsession with useless benchmarks.

Your phone runs fine correct?

I highly doubt you will notice any difference from when i twas high to low.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wcypierre:
You can try the link at my siggy if you want to make a logcat. It's quite noob proof, don't worry ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Who cares. How does your phone feel? This rom or any JB rom eats ICS. There is no comparison in how both roms operate. Benchmarks are useless garbage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
I tried this a few minutes ago, and had the same thing happen. Voice guidance comes through the BT device at full volume. I don't normally use the voice with navigation, so I never noticed before. Good find!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Celidonius:
Do you guys think the WiFi issue will ever be addressed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
bro what are you talking about?? What wifi issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
You know the issue where be needs a new router ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
He isn't kidding. My netgear causes me so many problems. I might seriously go back to a wrt54g. I hate netgear and linksys was so reliable. Anyone know how the cisco routers are with android?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
I am using a Netgear WNDR 3700 and have not had one issue with Cm10 or Aokp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Anyone find voice typing not working very well?

Not sent from my toilet with a soap bar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Ditto the Netgear WNDR3700 (running DD-WRT) being flawless. I upgraded to it 6-months ago (for 802.11N) from a similarly flawless ~7-year-old WRT54GS (also running ddwrt).

I think the wifi problems a lot of people run into is just interference from so many other nearby people sharing channels on G.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I hate to be off topic, but I have that router and I want to throw it at a wall!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Yep. Building Android is fun, like how compiling your own Linux kernel is fun when new to linux/unix (~20 years ago for me). :)

FWIW, it takes 35mins to cleanly build CM10 on my miniitx i7 w/ 16GB ram. Hope your iMac doesn't burst into flames compiling it inside a VM. :)

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

Give dd-wrt a try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
This is an interesting note from CM developer, Ricardo Cerqueira: https://plus.google.com/115049428938715274412/posts/HxPFHBQJdTL

Excerpt: "...We intentionally left placebo operations out of the CM OTA updater, and explicitly wrote one click upgrade. So now we get:..."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Celidonius:
My WiFi always disconnects for no reason. WiFi sleep policy is off. Isn't this a CM thing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzricezz:
I tried nagivation today using Google map and Waze and both of them doesn't have voice guidiance. Anyone else have this issue running OTA 10/17?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cuddlesy:
10/17 running great on my S3, getting about 22 hours or so with medium to heavy usage (Wi-fi and Bluetooth on almost all the time, browsing over 3G, playing music and screen brightness on auto).

Camera works great now, phone runs really well. Only problem is the screen flicker, but I can cope with that for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Works good with Android? Worth doing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatbigmoose:
I wouldn't generalize that DD-WRT works well with Android but,

I also have a wndr3700 and it's awesome. If you have a NAS on it you can format it to ext3 and install optware, and it becomes an almost full featured Linux box.

But it's 100% worth doing. So many features it's unbelievable.

As for wireless mine's actually been pretty spotty but I think it's because of interference within my house.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Everything works decent with my Wndr3700 but my phone and my printer. Both of those cause headaches. Stupid netgear haha. Sorry, back on topic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Here's a question for people who code for Android. Where is a good place to start? I am fairly new to Android but I want to start coding and looking into the CM10 code to make my own mods.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
I also have this router and have never had problems with it. I did a lot of research back in December 2010 when we bought it and CNET rated it very highly and it had lots of good reviews on there and Best Buy's website. Only complaint about it is that the 5.0ghz band doesn't have very good range and speed, but I never use it anyway, so it's fine by me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzricezz:
OK found out what the problem was. The phone was connected to my car stereo system over Bluetooth so all the audio was directed to my car audio so when I switch to aux BT I heard the voice guidance. Any way to direct the audio back to the speaker? And the audio was very low over BT. I had to max the volume on the car stereo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Start with the Cyanogen wikis on how to compile from source, learn about android here: http://developer.android.com/index.html , and compile a few apps, providing you know Java. Then step-by-step make your modifications to whatever you want in the code, test, and if it works well, consider submitting a patch to Gerrit. That's how open source works. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cellgeek:
Anyone notice the 10/17 build switching between LTE and HSPA a lot? It seems to camp on HSPA and seldom find LTE. Previous versions were solid on LTE if it existed. Running LH9 radio. Couldn't find any mention of this for the current builds.

update..

Traveling when I posted this. Seems that the issue was being in San Francisco. Back home and LTE is solid on 10/19 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I noticed this as well except I am using BT headphones. I had the headphones maxed out and the bluetooth volume on the phone turned up all the way and I couldn't hear the show I was watching. Tried music and I can hear it but its not as loud as it has been in the past.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
THE best site to get yourself started

http://www.kernel-xp.net/index.php/en/guide/25-android/32-compilare-cm10

learn your way around by just googling questions and things.

Make sure you have soemwhat of a decent connection internet connection and a really nice computer. I have a kinda okay DSL but my computer is an iMac i7 ~3.0ghz with paralllels and ubuntu running on the it. My repo sync failed three times but i synced them again right after it failed and presto. Builds compile in about 1hr 40min for me. When you repo sync it it downloads about 10gigs of data i think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
Thanks for the link. Could you maybe answer my question I quoted me asking from last night? Because what's the point of doing a logcat if there is no stable version of cm10 yet and that's what the issue tracker requires? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
fantastic rom, best one I've used to date (cm10 m2). great job cm team!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bgaccord:
Great battery life with cm10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpion667:
Wow, home button wakes up the screen consistently on 10-19 Nightly. Awesome! Used to work only half the time on all other aosp/aokp/cm10 type ROM's I've tried
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjcore:
Check back in at the end of the day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paniro187:
Or you could always do it "your way" and build your own and release your own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mad Medik:
Frustrated... Downloaded a new copy of the nightly (oct19) and JB Gapps. Have CWM recovery 6.0.1.2 installed and CM9 running. Followed above. As soon as I get past the boot animation and into the "Welcome" screen, I get a series of pop up notifications. They are all in the form, "Unfortunately, XXXXX has stopped." XXXXX includes Email, Exchange Services, the process com.google.process.gapps, Google Search, Google Play Store, android.process.media.

I'm new to the S3 but not new to custom roms but I'm stumped. I'm on an SGS3 (I747M).

MM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Looks like a bad flash probably. Wipe everything, system, factory reset, cache, dalvik, and flash both again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ferris2375:
Exactly. I always think the home button issue is fixed but then it happens. With the 10/18 build I have to hit the damn thing 3 times to turn it on, but it's totally random. It will work fine for hours, then all of the sudden, it just stops. Really annoying, probably my only gripe with this ROM. Otherwise it's excellent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_boris:
This interference must be ROM related then, because it never appears on TouchWiz, only on CM based ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Going to repost this. Again.

01. Wipe Data \ Factory Reset - ok

02. Wipe Cache - ok

03. Advanced => Wipe Dalvik Cache - already done in step 1 (/data/dalvik-cache/)

04. Mounts and Storage => format /system - ok

05. Mounts and Storage => format /data - already done in step 1

06. Mounts and Storage => format /cache - already done in step 2

07. Advanced => Reboot Recovery - not needed

08. Wipe Data \ Factory Reset - already done in step 1

09. Wipe Cache - already done in step 2

10. Advanced => Wipe Dalvik Cache - already done in step 1

11. Mounts and Storage => Mount /system - useless

12. Mounts and Storage => Mount /data - useless

13. Flash ROM - ok

14. Flash Gapps - ok

15. Advanced => Fix Permissions - ok but usually unnecessary

16. Reboot system now - ok

Additionally, turns out wiping caches isn't required, either: https://plus.google.com/115049428938715274412/posts/HxPFHBQJdTL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
The only time in cm10 that I have experienced gapps FCs is when I have zipalign scripts which includes /system to zip.

in any case, wiping /system removes the whole system rom and gapps to it should start you fresh flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mad Medik:
Force Close FC

Thanks, again ;) I looked over your notes and observed the system log as I performed the steps so I see your point as far as the redundancy. In my case, I was out of ideas as to where the problem was so repetition wasn't a concern. I probably would have even given "hold phone in raised left hand, spin around three times while chanting please take me home..." :laugh:

Thanks for the reply. Tried all those, more than once...

Thanks.

******* Appears solved ********** Posting for the benefit of anyone else who has this situation.

Not sure what the actual culprit was, but I wound up reformatting everything including the internal and external SD cards. I downloaded a copy of the latest nightly and JB-gapps on my PC. I removed the SIM card and microSD from the phone. I used the PC media interface to put it on the microSD then put it back in the phone. I booted into recovery and flashed CM10 Nightly from the external SD. I rebooted the phone at this time and only got one error: Unfortunatly, Email has closed. This message repeated. I tried to open the email app and it would FC. Thinking that perhaps the Email app needs an internet connection to open the first time, I connected to WIFI but still got this error.. I shut down, inserted the SIM and rebooted. No more error! I rebooted into Recovery and flashed Gapps from external SD and rebooted. So far, no errors.

Thanks again for the tips.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Just FYI, this happens when you flash wrong gapps. Or corrupted gapps.

I recently spent 2 hours trying to figure this out. Turns out I was flashing ICS gapps on CM7 (different phone).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Thanks. I've done a little Java programming before and still have my book from the class I took.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javadahutch:
Got a text msg yesterday that Midland,Tax officially launched LTE here for att but I still get the same old 3g/h/h+ cycle with h+ being the most common in town....used the post from rootzwiki to set my APN properly and had been using that for the past couple months...reset apns to default this morning because of no true 4g and thought that may fix it...att late APN bearer is set to let...network mode is late/gem/wcdma and cannot be changed...have 4 bars signal...latest cm10, kt747, and h9 modem...before I try it will flashing another modem affect lte reception?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Not sure what APN is on rootz but are you using PTA? http://xdaforums.com/showpost.php?p=27789771&postcount=2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I have 2 phones and a printer that argue with that router all the time. 1 stock GS3 and mine is CM10. The printer is HP. Either way. Hate it!

Anyone seen any commits on the group sms?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Im Just getting sick of flicker its really annoying and it's not gonna be fixed soon :s

Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ferris2375:
I haven't had flicker problems in quite a while, home button seems good on 10/19 and that's been my biggest issue.