yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] nfsmw_gr:
Happy flashing mate! :)

You don't need a second zip!You only need to flash this!

(don't forget to wipe ;) )
[Galaxy S III Original Android Development] Aksuli83:
goo.im/gapps

He needs to flash gapps =)
[Galaxy S III Original Android Development] nfsmw_gr:
Aaaah...that's what he meant with the second zip!Haha..

I automatically do that and i forgot it! :P
[Galaxy S III Original Android Development] fervorous:
I am currently on RC2. When i listen to music through bluetooth, the music will be choppy as if the bluetooth is out of range or having bad signal. Can anybody confirm this with their devices?
[Galaxy S III Original Android Development] fervorous:
I have confirmed this. The bluetooth signal is weak on CM9 RC2, I dont know about the nightly builds before. I played music and get my phone closer to the bluetooth headset and the music is clear, once I put the phone in my pocket the music can't be heard through the bluetooth headset.
[Galaxy S III Original Android Development] m0ngstr0us:
Yup. Wiped and wiped and wiped still to no avail. lol.

Sms works fine tho.
[Galaxy S III Original Android Development] Damov3:
Yes!
[Galaxy S III Original Android Development] garyd9:
I've been playing around intently with the GPS stuff, and I think I've managed to capture part of what I've been describing here. (Though I can't find anything in the logs that appears helpful.) This test was done with the 20120719 nightly from get.cm, and I used "GPS Test" (from the market) to measure times, identify when I had GPS lock, etc.

Here are the steps shown in the attached logs. Also important is that I didn't move the phone AT ALL through this test.

Boot the phone.

Wait a minute, run GPS Test. The device locks on to many GPS birds nearly instantly and displays a "first lock" time of 4 seconds.

Exit GPS Test

Wait a couple minutes

Run GPS Test again. This time, only 1-2 birds show up as "in view" (but not locked) and it eventually gets up to 4, then a while longer to 5 and soon after jumps to a full sky of birds in view and a lock. This second time, it takes 1 1/2 minutes for first lock. It appears that during this much longer delay, the program doesn't know there are 20+ visible birds in the sky, and just hangs out thinking there are only 2-5. Eventually it figures things out.

What I haven't managed to log (but will if its significant to actually log it) is that sometimes any attempts to lock can take up 5 to 20 minutes (while standing in front of a window!) (I didn't see anything in the logs that would be helpful, so I didn't work too hard to capture the extreme cases.)

(Ironically, as I'm typing this, I ran the above pattern 2 more times (not logged.) The 3rd run took about 30 seconds to get more than 2 birds "in view" and then spend about 2 1/2 minutes with 4 or 5 "in view" before it finally managed realize that there are 12+ birds in view and locked. - total of ~3 minutes for first lock. The 4th attempt took about 5 minutes for first lock.)

I don't always get a quick (4 seconds!) lock after rebooting the phone - sometimes it'll take a few minutes and sometimes I get tired of waiting after 5 or so minutes. Earlier this evening, I put the phone in a window sill with a very clear view of the cloudless sky, and it hadn't locked after leaving it there for 10 minutes.

In contrast, I always get a quick lock (< 10 seconds) with the samsung (stock) firmware. With the stock firmware, I can even get a lock inside a shopping mall, in my basement, or seemingly anywhere else. (Only mentioning this as I tested repeatedly to ensure the GPS hardware in the phone wasn't defective.)

Two logs: a logcat (from alog) and a dump from dmesg (gps.kmsg.txt)

Take care

Gary
[Galaxy S III Original Android Development] der_bert:
confirming aforementioned gps behaviour
[Galaxy S III Original Android Development] ev!denz:
It is recommended to do beteween various nightlies a full wipe or is it sufficient to flash the new one over the older one?
[Galaxy S III Original Android Development] ageva:
Wipe cache and Dalvik cache, nothing more is needed.
[Galaxy S III Original Android Development] dboechat:
I also have this problem.
[Galaxy S III Original Android Development] YDardeer:
Why not to restore Titanium Backup apps WITH data? Why is it gonna cause FC? I don't wanna lose my WhatsApps chats for example... Can anyone confirm that restoring the apps with data in TB does in fact causes force closes?
[Galaxy S III Original Android Development] dboechat:
It does not.
[Galaxy S III Original Android Development] sodeknetters:
I tried some more to see if I could replicate the gps assistance problem. I have disabled and enabled gps multiple times, went inside and made sure the reception was bad, disabled gps, went back outside, enabled - BAMM!! GPS lock on 13 satellites in 2 seconds :-)

So Im afraid I really cant replicate
[Galaxy S III Original Android Development] TecQuality:
what are the differences between RC and the latest nightly?
[Galaxy S III Original Android Development] nfsmw_gr:
Check the changelog here!

http://changelog.bbqdroid.org/#i9300/cm9/next

Also this link is available on the first page of the thread,just saying! ;)
[Galaxy S III Original Android Development] DvTonder:
Just flash over the old one - no need to wipe anything, the install takes care of everything.
[Galaxy S III Original Android Development] TecQuality:
a cache and dalvik wipe could be required :)
[Galaxy S III Original Android Development] ThunderWolf78:
Now I too have the no incall sound problem, tested this morning for the fun of it. Modem was lxxg3(worked yesterday) and 1807 nightly. Had just disconnected my A2DP headset and called a workmate, he couldn't hear me but I could hear him, then he called me back and the same happened, I heard him fine but he couldn't hear me. Logs provided. Calling works perfect as long as I use the headset but I almost only use that for music while on the train...

Logcat: http://db.tt/dDs7O3UX

Dmesg: http://db.tt/DsIYAlm4

painstakingly sent from my h4x0r3d up GT-I9300 with Tapatalk 2
[Galaxy S III Original Android Development] unfnknblvbl:
I've never had a problem with any of my Android devices (check my .sig) - transferring backups with data from one phone to another, phone to tablet, tablet to phone, tablet to tablet.. Never a problem at all, ever.

Now on a more pertinent note, what the hell is with the SGS3 and modems? Why does everybody have a different experience with the same configuration? What a cluster**** this is turning out to be - especially for the CM10 users/testers.

Surely there's a way to work out just what is going on - some kind of systematic check of modem experience vs serial number or something..?
[Galaxy S III Original Android Development] detritu5:
How about yhis modem to cm9?

XXLG3

Will be work?

I have trobles with bluetooh. Can´t send apk´s
[Galaxy S III Original Android Development] Capt.Insano:
Working for me, testing it at the moment. So far so good!

I tried it because XXLBF started giving me trouble out of the blue. The issue doesn't seem to be solely modem related because XXLBF was working fine for me up to today.
[Galaxy S III Original Android Development] Neokazaki:
Same issue here, LFB was working fine for over a week (currently running nightly 0712). Restarted my phone some minutes ago (without flashing anything) and now I have no audio. Will try the other modems once my device is charged. But I agree, seems a bit strange...
[Galaxy S III Original Android Development] nfsmw_gr:
Hey...i wiped everything and installed the rom from scratch....but still i have the phone issue!

I noticed it only happens if i have my earbuds connected and someone calls me...otherwise there is no problem!

Any user suggestions?

Except from the on/off lockscreen sound trick of course..:P
[Galaxy S III Original Android Development] Astrofrigo:
I never had any trouble with Titanium either, whether be it an official ROM, custom or CM9/CM10 (tested CM10 enough) there wasn't any problem. I don't understand why they'd JUST say "don't restore apps with Titanium Backup!"... at least I would love an explanation.

Ignore what I said about modems. :P
[Galaxy S III Original Android Development] Capt.Insano:
Signal is not the issue, I had full signal but one or both parties on a phone call could not hear the other. Also I had been using the correct geographical modem for me!! XXLBF was working and then started causing issues.

Don't get me wrong, I love team hacksung's work so far!

The Capt.
[Galaxy S III Original Android Development] mcored:
My SGS3 (International) just lost the ability for me to hear from the other end or for the other person to hear my voice. I read above that you need to flash a different radio; but why? I never flashed a different firmware for my SGS2 or SGS1 so why this time it is different?﻿

I went from I9300XXLE8 to I9300XXLFB and still the same problem! :crying:
[Galaxy S III Original Android Development] mariotme:
Just activate screen lock sounds and reboot
[Galaxy S III Original Android Development] nfsmw_gr:
This is a problem we're all trying to understand so far...keep an eye here,right now what fixes the situation is to disable and re-enable the lockscreen sounds then reboot the phone and after that to do the same....
[Galaxy S III Original Android Development] mcored:
Wow! After nearly 16 hours without calling anybody I can finally make a phone call now.

Settings > Sound > Screen lock sound -- check did the trick.

I had it turned off! But I know it should not have anything to do with making calls. So switching modems had no effect!?
[Galaxy S III Original Android Development] nfsmw_gr:
Nice to see that working!

Yet i don't know,i'll flash LFB modem now and check...maybe some of the other guys here can give you an answer! :)
[Galaxy S III Original Android Development] mariotme:
No one can answer it lol. Its puzzling really
[Galaxy S III Original Android Development] mcored:
A phone is for making phone calls. I can't believe how CyanogenMod 9 for SGS3 jumped to RC2 with this type of a showstopper error.

I believe switching to LFB had no effect. It was the Screen lock sound that did the trick. It must have turned on some internal functionality, inadvertently.
[Galaxy S III Original Android Development] nfsmw_gr:
Yeah,i know....:p

I was talking only on the modem part.
[Galaxy S III Original Android Development] GGSunny12:
There's a gap in my battery chart after flashing the latest nightly.
[Galaxy S III Original Android Development] betobody:
Do the following: switch to the front camera and take a picture, see if you will hang the picture taken. So the only way the camera work is returning to the camera back.

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III Original Android Development] furyau:
Thanks for this, worked the trick!

XXLG3 is working fine, just need to have screen lock sounds ON (and reboot)
[Galaxy S III Original Android Development] labbe-:
the gap always appears when you reboot or are in recovery, because the os isnt taking battery stats then :genius:
[Galaxy S III Original Android Development] Bulut.O:
I am running RC2 ATM... No call problem and no other problem here so far...

For me it feels like 1807 was smoother...

I can feel and see a big difference when typing something in SMS or WhatsApp...

There is no LogCat for my feelings :)

Just wanted to point that out..
[Galaxy S III Original Android Development] RoadXY:
Flash stock rom and your done: Calling works!
[Galaxy S III Original Android Development] Astrofrigo:
Thanks for the explanation, I clearly didn't know which were the real problems about the modems.
[Galaxy S III Original Android Development] b3er:
For those who haves a problem with calls after disconnecting headphones (people on the other side cant hear you)

1. unzip the attached archive

2. push the unzipped file with adb to /system/etc/sound/

it's not full solution( atm you cant speak to internal mic with headphones connected)

i'm owning the device just two days :)

but the problems with mute after disconnecting hp gone away.

tested and working on RC2
[Galaxy S III Original Android Development] ThunderWolf78:
What exactly has been changed in it and does it unmute the handset mic after you disconnect a bt headset? I am asking because I want to know what changes affect this... My phone gets the mic muted thing when I disconnect my jabra handsfree...

painstakingly sent from my h4x0r3d up GT-I9300 with Tapatalk 2

Nevermind the above, compared the two files and found the difference and it makes sense indeed. Good work. :)

I will try this thing out and see if it works with A2DP too, I guess the phone itself sees the stereo BT handsfree as a pair of headphones...
[Galaxy S III Original Android Development] nfsmw_gr:
Just used this,can't test right now though!

I really wish this works! :)

If it does why not tell the team about this so it can get pushed in later nightlies of cm9,it would help soooo many of us here! :D

At cm9 devs...i saw that busybox in the latest nightlies is static...:(

I tried installing another version but it doesn't work..can you fix that please?
[Galaxy S III Original Android Development] tof9:
I read this in the instructions too and I could not understand why. Has someone tested restoring apps from Titanium Backup on CM9 and confirmed problems or is it ok?

So the muted mic on the first call is fixed by disabling lockscreen sounds, then re-enabling them again and then reboot the phone? Why you say to do the same again? Do you mean every time you reboot the phone you must disable then re-enable lockscreen sounds to fix your muted mic?

Also from the "Known Issues", I see:

You must use the LFB modem to have in-voice calls.

Actual as of 9th July, 2012

Is this still true that you must flash to an XXLFB modem for calls to work?

Cheers guys. :)
[Galaxy S III Original Android Development] psynapse:
Got my SGS3 just yesterday.

Tried to endure what Samsung had done to ICS but after using CM9 on my old SGS1 i could stand it no longer!

Just rooted and installed CM9 21/07 nightly on my SGS3. So far everything is working perfectly.

Awesome work guys :cool:
[Galaxy S III Original Android Development] tof9:
Same thing mate. I went from CM9 SGS1 to a HTC One XL but couldn't stand Sense (HTC One XL still doesn't have a safe way to flash, eg. TriangleAway) and just got a SGS3. Definitely can't deal with TouchWiz.

What modem are you using and do you have issues with the muted mic?
[Galaxy S III Original Android Development] furyau:
I am usng LG3 and Nightly2107

If I untick lock screen sounds - mic mutes

If I use headphones and then unplug them, the mic is mute

Apply the patch from b3er and it worked a treat to fix the headphones bug.
[Galaxy S III Original Android Development] koboltzz:
No, the warning is right. If you restore SMS/MMS/APN from Stock on CM9 or CM10, you will get irreparable fc's on SMS app. In the past, restoring bluetooth pairs will let bluetooth settings fc. Seems to be fixed now, but it is not recommended to restore those things with Titanium Backup.
[Galaxy S III Original Android Development] luexi:
Need help guys, I was on the 18/7 build and I tried to go in storage in the setting and I got a fc. It was saying "unfortunately setting has stop" . Any of your have similar case?

Only storage giving me this issue while other is all working fine.
[Galaxy S III Original Android Development] ThunderWolf78:
Disable google backup and reboot, redo your test and see what results it yields... I wiped and reinstalled yesterday and left google backup which somehow hung itself and happily chugged 20% battery just like that...

painstakingly sent from my h4x0r3d up GT-I9300 with Tapatalk 2
[Galaxy S III Original Android Development] RavinShubh:
You might want to recalibrate your battery. Charge it full while it's off and then go to cwm and wipe battery stats under advanced.
[Galaxy S III Original Android Development] Krypt0n1te:
Grab BetterBatteryStats from XDA or support the dude by purchasing it on Play store. Do some reading on the subject and post your result in that thread. Some extremely informed people there.
[Galaxy S III Original Android Development] _neutron_:
Wiping battery stats doesn't recalibrate the battery...that's a misnomer...common error of thought
[Galaxy S III Original Android Development] Bozmo:
Hi,

The camera in CM9 seems a little buggy. When I take a picture to share, for example with whatsapp, the photo does not freeze but keeps going so I cannot see the picture I will be sending when I push confirm to send. Also, some times when I change settings it will lose connection to camera until I restart the phone.

Where could I find the stock Galaxy S3 camera apk to install for now?

Thanks in advance.
[Galaxy S III Original Android Development] Krypt0n1te:
I loose about 2% in 9hrs
[Galaxy S III Original Android Development] xedamen:
Download the battery calibration at Play store ;)

Tapatalk 2-vel küldve az én GT-I9300-ről
[Galaxy S III Original Android Development] Cucoo:
Not an issue, standard battery behavior. It does that because charging to 100% and keeping it there is bad for your battery.
[Galaxy S III Original Android Development] TecQuality:
it's normal mate :)
[Galaxy S III Original Android Development] demonstone:
You can't use stock Samsung's camera on cm9 because of the framework.
[Galaxy S III Original Android Development] Spiralzz:
Its designed to be that way, that's what I read somewhere. This is because the moment u plug out the charger, your phone starts using the battery, so it can't remain 100%, it will be something like 99.9% which is shown as 99%.... tho u can search google.. u may find a better explanation ;)
[Galaxy S III Original Android Development] fenstre:
Does the LFB modem work with stock ROM?

If I flash the modem to try CM9, can I use clockworkmod to restore stock, or will I need to find an acceptable modem?
[Galaxy S III Original Android Development] cm6291:
Anyone have Amy ideas why I get no video but sound when playing Netflix or Tvcatchup. I get both sound and video with YouTube and my own recorded videos.

Note: They all work fine on stock Rom with TW. But no joy on cm9/AOKP.

Thanks
[Galaxy S III Original Android Development] TecQuality:
A log could help the devs mate ;)
[Galaxy S III Original Android Development] ididnt:
I noticed the flashlight is flickering from low to bright when switched on via the power widget (nightly 20120719)
[Galaxy S III Original Android Development] nfsmw_gr:
Yes,i agree with you..:)

But the meter on mine says everytime i unplug it 100 and if i don't use it it stays there for around 3 hours! :D

Maybe it's because i calibrated my battery,i get amazing battery life now...:) (12+ hours WITH usage...)
[Galaxy S III Original Android Development] 90paolo:
As said many and many times, even from a google engineer, battery calibration is just a placebo and has no effects.

In cm9 as other roms (even stock) battery in charged on 99% to dodge pericolous overcharges that may ruin the battery.

You can just wipe battery stats in CWM after flash a new rom or update a cm9-nightly and make some full charge/full discharge cycles.

Anyway, this is the cm9 developers thread and imho isn't the right place to discuss about battery life/stats.

cheers.
[Galaxy S III Original Android Development] fervorous:
Hi. Anybody else have this problem? Using Jabra Clipper.
[Galaxy S III Original Android Development] ThunderWolf78:
I pushed this config file to my phone this weekend and I can now confirm that it works with A2DP bt headsets aswell because now my phone's mic is no longer muted when I try to call someone after the headset's been disconnected. There is something fishy with the led notifications tho, it seems to miss out every now and then. Nightly 0721, fresh and full wiped install with gapps 0417, the aforementioned config file for sound. Logcat here: http://db.tt/txt06qya

painstakingly sent from my h4x0r3d up GT-I9300 with Tapatalk 2
[Galaxy S III Original Android Development] rbf101:
Hey guys,

something I was wondering about: the icons in the status bar seem to be pretty dark. When I get a text, the icon is showing up in full saturation but is going back to darker, greyish look, once the notification disappeared. That makes the icons hard to see in sunlight. Is there any setting, that can change this behaviour? Do you know, what I mean?

Thanks :)
[Galaxy S III Original Android Development] BattleCat:
VIDEO BUG (Plex & TvCatchup)

I'm experiencing a problem on all builds with Plex and TVCatchup (they work on stock roms)

Plex when attempting to stream video 'hangs' instantly (black screen with media auto still playing) and comes up with a force close option and sometimes the video is playing perfectly behind the 'Wait / Force close' dialog, when Wait is pressed it goes back to black screen. I assumed it was a Plex issue but have the same problem with TVCatchup so I guess its the video drivers?

Checking the logcat, the following is the same in both apps:

E/SECHWC_LOG( 2035): Error in VIDIOC_DQBUF

E/SECHWC_LOG( 2035): Fail : v4l2_dequeue()

E/SECHWC_LOG( 2035): int hwc_set(hwc_composer_device_t*, void*, void*, hwc_layer_list_t*)::runFimc fail : ret=0

E/SECHWC_LOG( 2035): int get_src_phys_addr(hwc_context_t*, sec_img*, sec_rect*)::

E/SECHWC_LOG( 2035): format = 0x101 : Not GRALLOC_USAGE_PHYSICALLY_LINEAR can not supported

I can imagine this would be WAY down on your priority list but thought I'd report it away. Loving your work!
[Galaxy S III Original Android Development] maniAK-:
Hello iv just bought a GS3 few days ago is this rom stable enough for everyday use ?
[Galaxy S III Original Android Development] box4m:
Very stable
[Galaxy S III Original Android Development] gorylutza:
Guys one question.

Today we have a new build 23072012, but when i looked at the changelog it says "THERE WERE NO CHANGES IN THIS NIGHTLY"

What does this mean ?
[Galaxy S III Original Android Development] Cucoo:
...not sure if serious? :D

It means there weren't any changes.
[Galaxy S III Original Android Development] mariotme:
It means that there was no changes made :)

The build starts automatically as far as i know so even if there was no changes made the Bot would build a newer version
[Galaxy S III Original Android Development] demonstone:
Simple... there were no changes in the nightly but the buildbot built and published it anyway
[Galaxy S III Original Android Development] minipaolo:
Just a quick question.

I was thinking about flashing this rom over my previous Omega which actually works great.

I have been using Cyanogenmods before and always had issues with stock low brightness settings. Is there a way to increase standard auto brightness?

Any annoying issue or I can flash and enjoy for daily use?

Thank you for your kind help. I :)
[Galaxy S III Original Android Development] djglenn1337:
I believe hardcore included the brightness fix in his kernel, so you could use speedmod with CM9, and have the brightness fixed
[Galaxy S III Original Android Development] Alf55:
Please anyone could tell me how to config SpiritFm on this ROM? thanks
[Galaxy S III Original Android Development] nrg:
Cm has full customizable brightness support. There are also apps like lux which support custom brightness values.
[Galaxy S III Original Android Development] minipaolo:
Could you please explain how to make it a little brighter in all conditions, using CM controls? :)
[Galaxy S III Original Android Development] norpan111:
Gosh, I'm in the decision of rc2 or newest nightly :) anything broken after rc2?

Edit: crap, thought I was in discussion thread

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] gorylutza:
Ok, thanks for the reply.

I did not understand why the build if no changes.
[Galaxy S III Original Android Development] nrg:
This isn't the q and a section.
[Galaxy S III Original Android Development] box4m:
Supported app for voltagetweaks with cm9 kernel? Setcpu etc works?

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] gee2012:
Setcpu and Voltage Control are both good. Begin with -50Mv and raise to -75 after a day`s use.
[Galaxy S III Original Android Development] Timpppa:
Has someone tried Navigon with latest build? My Navigon is just shutting down.