yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] xknobi:
skype video call

Anyone had problem with Skype's video call? With the recent CM 10.2 version I got crashes in Skype when I tried to place a video call. Phone restart. In the newest version I had to try many time in skype to make a usable video call, because of no sound, video screen of myself shows only black sometimes.
[Galaxy S III General] petrolcan:
Battery life for 13/09 nightly :D
[Galaxy S III General] Tuxi1990:
Thanks! Clearing gallery cash helped!
[Galaxy S III General] ajobbins:
Only when using with Bluetooth. Works fine when just using the phone
[Galaxy S III General] tsvikrn:
remote wipe

has anyone checked the cm account yet ?

i was able to locate my phone (both s1 and s3) but not to remote wipe it.

does someone know if anything needs to be done on the phone to allow it ?

thanks
[Galaxy S III General] cink40:
Security /device administrator
[Galaxy S III General] schnullifax26:
New nightly works fine. But still sometimes problems with wifi.

cheers Sven

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III General] andreMusers:
Hi guys. I want to ask some question. The Official nightly Android 4.3 versions have the fix for the sudden death
[Galaxy S III General] venkatesh.velmani:
Hey Guys.. Has the graphical glitches problem been solved in the latest 4.3 nightly?
[Galaxy S III General] fabfor:
Yes, fixed a couple of months ago. Flash also latest CWM recovery to be safe

---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------

Yes, fixed a couple of weeks ago
[Galaxy S III General] venkatesh.velmani:
Thanks man! :)
[Galaxy S III General] chrisxpierce:
Camera locking up and force close on gallery periodically on latest nightly.

HTC one. ATT.
[Galaxy S III General] alexferdean:
That's very bad! Did you get at least one hour screen time?

Galaxy S3
[Galaxy S III General] SaphirX:
Try clearing cache of camera and gallery under settings - app
[Galaxy S III General] petrolcan:
Bad? I'm very happy with it. I believe screen time was about an hour.
[Galaxy S III General] vittogn:
Great.

The screen on time isn't more than 20 mins though!
[Galaxy S III General] petrolcan:
As per previous post it was about an hour.
[Galaxy S III General] Striatum_bdr:
Sds was fixed in January....
[Galaxy S III General] oae08:
You can still get much better, because for me standby time the battery statistics is straight line not decreasin like yours which means your phone isnt deep sleeling much. Maybe you have apps waking it up, check BBS
[Galaxy S III General] SaphirX:
Are you guys using stock battery?
[Galaxy S III General] petrolcan:
You are most likely correct but even when using the phone heavily I get excellent battery life. Maybe some day I'll start looking closer at battery stats but it's not a high priority right now.
[Galaxy S III General] oae08:
Yeah stock battery i get about 16hours total but about 5 hours screen time
[Galaxy S III General] Daelyn:
Cody: I just did some Exif checks on recent photos and I noticed we're "missing" the dodgy "User Comment" field which contained Current FW string. The "Unique Image ID" field is also missing, which contained that same firmware version id.

This is not disturbing in any way, but I do wish having FW ID somewhere in there. Can it be considered a regression perhaps?
[Galaxy S III General] 2k13i:
is there call recorder build in? for calls? :) looks nice btw! I may give it a try on my other device!
[Galaxy S III General] FDisk80:
No, but InCall Recorder kind of works.
[Galaxy S III General] chrisxpierce:
The volume to wake feature still only works for a few seconds after phone sleeps.

This has got to be fixable, in the ARHD 13.3 Rom, this feature works flawlessly.

Thanks for all your hard work!

Chris
[Galaxy S III General] petrolcan:
Yup, stock battery.
[Galaxy S III General] rogerone:
Covering the sensors prevents phone to go to sleep and lock screen

Hi

Thanks for the great build. Battery life is getting better every Nightly 10.2.

I have a booklet cover on my Galaxy S3 and when I close the cover without putting the phone into sleep the phone sometimes does not lock and the phone does not go to sleep. This results in that the lock screen does not appear when I want to use the phone again. But I am worried if this happens also when it is not me activating the phone and thus blows every security i put in place.

I think it is related to the sensors. I saw the same behaviour on my Nexus 10: when I open the cover the Nexus switches on but in the lock screen.

I did multiple tests but I have no detailed info on when it exactly happens. Sorry.

---------- Post added at 05:30 PM ---------- Previous post was at 05:27 PM ----------

Optimizing the code further could give the same 4 - 5 days as on the Nexus 4 :)
[Galaxy S III General] xrad:
MDNIE settings ever to return?

WIll the MDNIE UI settings ever return to stock CM? As a work-around I currently use Temaseks kernel + stweaks, but I hate to use a custom kernel for just this thing.
[Galaxy S III General] KKTHX:
Anyone have problem with calls. Every few calls you can not hear other person who is calling. And after you recall, as we will you cant hear. Silent. But after restart or 2, magicly everything working fine... for some time.

And bluetooth headset. Samsung HD 1000. Working fine now?
[Galaxy S III General] chrisxpierce:
No problems with that on my HTC ONE. Are you able to use the volume button to wake your phone? After its been asleep for a minute or two? That's really the only issue I'm having.
[Galaxy S III General] KKTHX:
Bluetooth in S3 don't see HD1000.
[Galaxy S III General] rockambole:
does anyone know why the recorded messages on whatsapp have such a crappy quality?
[Galaxy S III General] memaxxx:
Bluetooth bug?

The radio in my car has a Bluetooth dongle. I can easily pair it with my sgs3 and i can hear music over Bluetooth. The only thing is that i am not able to Fall over this Bluetooth connection. The voice i recieve is very unclear. Could anybody confirm?
[Galaxy S III General] 9376:
Bluetooth seems to make problems in different parts.

For me, the sound is sometimes crickeling. This happens as you said after the screen is off for some minutes.

Additionally,

if the device is connected, it sometimes can not be used by the car - just as if it is unconnected.

And in most cases the phone crashes when ich try to connect.

So all in all, Bluetooth does work very bad.
[Galaxy S III General] krayvitz:
Is it true that battery is good on 10.2 is better than 10.1? Phone wakeup trigger is insane.
[Galaxy S III General] svetloslav:
Not true. Bluetooth works flawlessly for quite a long time already, in fact it has been working very stable since CM10.1. The only glitch so far has been the short range, but that problem is to be blamed on Samsung for not providing the native code for the drivers. I have a Sony stereo in my car and both streaming music and calls work like a champ. On certain occasions, while the car is running and I walk out for something with the phone on me, the connection to the stereo drops and after returning to the car it won't reconnect on its own. A quick toggling of the Bluetooth on/off, restarting the phone, or the car ignition solves the problem. I have a separate indicator in the stereo display for the streaming connection and for the calling availability and that gives enough feedback so not to get confused about a dropped connection. So if one learns to ignore the short range annoyance, overall bluetooth on Cm 10.2 is a joyful ride.
[Galaxy S III General] ajobbins:
I disagree. I'm have a number of Bluetooth issues. A number of times when making a call only a broken, crackling sound is heard (and the handset itself makes a few similar sounds. It's almost like it can't decide where to route the audio.

Also, voice dialling over any Bluetooth device fails. There is no sound in or out, so the voice dialler app cannot hear what you are telling it, and nor do you get any audio back from it. But it works completely fine when not connected to Bluetooth.
[Galaxy S III General] ereziel:
Connect to USB, and use 'adb logcat' command (without comma).

You can look that on google for more information.
[Galaxy S III General] chronosk:
I usually make a backup, and then I do all the wipes and format system partition so there's no leftovers from previous installation
[Galaxy S III General] bartekxx12:
Alright, I've figured out logcat under 4.2.2. The only problem is, as far as I can tell USB Debugging needs to be enabled for it to work and since it's impossible to get into settings with the newest build I'll have to flash the build from the 27th, enable debugging and then flash the newest build on top of that. I am hoping that debugging will stay enabled.

EDIT :

Well so here it is, logcat from the latest build. From start to end I did this - Unlocked the device -> Clicked on a random app (GMail I believe) -> Caused a re-boot -> waited for it to complete and unlocked again. That is all the log contains.

http://justpaste.it/39cw

I believe this is where it actually happens

[ 07-31 02:48:29.113 17412:17639 I/ActivityManager ]
START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.gm/.ConversationListActivityGmail bnds=[192,899][352,1099]} from pid 17728

[ 07-31 02:48:29.123 17436:17453 D/PermissionCache ]
checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (302 us)

[ 07-31 02:48:29.128 17436:17437 F/libc ]
Fatal signal 11 (SIGSEGV) at 0x61f59000 (code=1), thread 17437 (SurfaceFlinger)

[ 07-31 02:48:29.228 1894: 1894 I/DEBUG ]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

[ 07-31 02:48:29.228 1894: 1894 I/DEBUG ]
Build fingerprint: 'samsung/m0xx/m0:4.1.1/JRO03C/I9300XXDLIB:user/release-keys'

[ 07-31 02:48:29.228 1894: 1894 I/DEBUG ]
Revision: '12'

[ 07-31 02:48:29.228 1894: 1894 I/DEBUG ]
pid: 17436, tid: 17437, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<

[ 07-31 02:48:29.228 1894: 1894 I/DEBUG ]
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 61f59000

[ 07-31 02:48:29.233 17412:17543 W/NativeCrashListener ]
Couldn't find ProcessRecord for pid 17436
[Galaxy S III General] ereziel:
Yes I think so. Segmentation faults are a severe memory management error, though I can't know where it is happening. Let leave it for [MENTION=640797]codeworks[/MENTION]
[Galaxy S III General] entertainyou:
Workaround for internal storage

#from /init.smdk4x12.rc on device, seems the sdcard services failed some how

#start manually

adb shell

su

nohup /system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023 > /dev/null

exit

exit
[Galaxy S III General] :
I did a dirty hack work to see what is the minimum to get the internal and external sdcard working. I took the 2nd build from xplodwild which had the external sdcard working. I tool the fstab fix from codeworkx and repackaged the kernel (boot.img) and stuffed it in the CM unofficial zip. Unpack the previous boot.img and the ramdisk, put in the new fstab and repack it. It works! I am not trying to showoff, this is dirty hack and not developer work. Just to show that things are looking great.
[Galaxy S III General] LegendM:
Tons of bugs caused by storage issue

GT-I9300 cihazımdan Tapatalk 4 Beta ile gönderildi
[Galaxy S III General] henke002:
Oh come on, dirty hacks are beautiful :)

Especially in live environments with no dokumentation.

EDT: sry, thought this was the discussion thread ;-(

Skickat från min GT-I9300 med Tapatalk 4 Beta
[Galaxy S III General] Moster2:
It is the discussion thread Oo
[Galaxy S III General] LegendM:
Good idea nice work

That means in next build storage issue will fixed ;) great cause like i said 2 post ago tons of bugs just caused by storage issues

Keep it up good work guys ;))

GT-I9300 cihazımdan Tapatalk 4 Beta ile gönderildi
[Galaxy S III General] henke002:
Yea, seems lite tapatalk pulled a fast one on me =)

---------- Post added at 11:23 AM ---------- Previous post was at 10:41 AM ----------

So its a "working" flashable zip you're sitting on? Is it possible you could sent that to me or upload on my server, I want my internal memory back :)
[Galaxy S III General] overflyer:
Yeah I also think it would be really nice if he shared that dirty-hack-flashable zip with us. Unless he WAS just trying to show off :) :P
[Galaxy S III General] timbremer:
Yeah!

Gesendet von meinem GT-I9300 mit Tapatalk 4 Beta
[Galaxy S III General] :
It is not my work and I _am_ not trying to show off. It is the work of xplodwild & codeworkx (and the CM team). By sharing it publicly, I am disrespecting them. I am a long time XDA user and there are unwritten rules one should not break. I am very sorry but will not share the binary. However, I will give the detailed steps to do it if anyone wants to build.

Prerequisites:

1. Working GNU/Linux system

2. Xplodwild's 30th build and Codeworkx 30th build

3. Command line tools: unzip, unpackboot, mkbootimg, gzip and cpio

$ TOP=`pwd`

# Let me call xplodwild's zip as X.zip and Codeworkx's zip as C.zip in folder ${TOP}

# Extracts cody kernel

$ mkdir C

$ cd C

$ unzip ${TOP}/C.zip ${TOP}/boot.img

$ mkdir c-boot

$ cd c-boot

$ unpack -i ../boot.img

$ mkdir ramdisk

$ cd ramdisk

$ gzip -d -c ../boot.img-ramdisk.gz | cpio -i -d

$ cd $TOP

# Unpack Xplodwild's kernel

$ mkdir X

$ cd X

$ unzip ${TOP}/X.zip boot.img

$ mkdir x-boot

$ cd x-boot

$ unpack -i ../boot.img

$ mkdir ramdisk

$ cd ramdisk

$ gzip -d -c ../boot.img-ramdisk.gz | cpio -i -d

$ cd $TOP

# Copy the fstab.smdk4x12 from Cody to Xplod

$ cp C/c-boot/ramdisk/fstab.smdk4x12 X/x-boot/ramdisk/fstab.smdk4x12

# Let us repack the kernel

$ cd X/x-boot/ramdisk

$ find . | cpio -o -H newc | gzip -9 > ../boot.img-ramdisk.gz

$ cd ..

$ mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --cmdline "$(cat boot.img-cmdline)" --base $(cat boot.img-base) --output ${TOP}/boot.img

# You now have the repacked boot.img at the top

Replace the boot.img in the Xplodwild's zip and make a new zip file (sure, you can figure that out). The superuser needs a separate fix. I build Superuser.apk and pushed it into "system/app". For the real lazy, just start superuser daemon manually

$ adb root

$ adb shell

$ su --daemon &

$ exit

Have fun, it was fun figuring all this today.

Edit:

An easier way to get 'su' working

1. Enable developer option by clicking on the build information (try with terminal emulator on phone first)

2. Enable ADB for both app and shell

$ adb shell

# Try this from terminal emulator first, I did not try

$ su

3. Go ahead and disable developer options if you want to be super safe

You are all set! Once 'su' runs, you can reboot and see that it starts on its own. I am looking at code to see what magic happens after the first run.

To confirm 'su' is running after a reboot

1. Open terminal emulator on phone

$ pgrep su

You will see the PIDs of su running
[Galaxy S III General] overflyer:
I meant my ironic remark in a very joking way and did not want to disrespect you in any way. I honor you for not disrespecting the unwritten rules of the scene. Thanks A LOT for the detailed instructions!
[Galaxy S III General] :
Mods (and cody), sorry for going off topic:

No offence taken. I probably would have reacted similarly when someone is making tall claims. XDA is a nice place to learn. However it can either make you arrogant (which is easy) or very humble (harder path). Each one chooses his/her own path. Fortunately, a lot of core CM maintainers have chosen the path where they help if you put in your effort. Enjoy the learning!
[Galaxy S III General] iSaoHatake:
i think i don't understand it, this is CM10.2 but on changelog says CM10.1Okay now i understand this is unofficial builds, so what's the changes from 4.2.2 to 4.3 FOR GALAXY SIII, only for Galaxy SIII?
[Galaxy S III General] Moster2:
Those are still some experimental builds, so the changelog is not adjusted I guess. Atm, xplodwild is trying to get it running, so I dont think there are much i9300 specific changes.
[Galaxy S III General] infrag:
I managed to compile 10.2 for the i9305. However it has the same problems as described by others in this thread. It boots fine but as soon as I try to get into a program it reboots. I can scroll through the apps menu and if I'm fast I can get into settings but then if I tap anything else it loops again.

I realise this is early days but if any progress is made to why this is happening I'd love to know how to fix this and get on to the next stage so I can enable ADB + logcat to see what else is going on :) I've been trying to figure out what changes are being made by codeworkx and xplod but I dont know what they are doing to fix it. Anyone have any idea what is causing the reboot to start with?

I dont claim to be any good at this either (obviously I'm not, I'm just experimenting and trying to get 10.2 also on the i9305 (buggy or not.. current state is a little too buggy :) )
[Galaxy S III General] xrad:
Kudos to your efforts, but this is the I9300 / CM10.2 thread...
[Galaxy S III General] xrad:
There are far too many reports here of not working BT combinations to dismiss them so easily. Also note that you can't compare the BT implementations of 10.1 and 10.2. Google has done a lot of changes to this in Android 4.3. Having said that, I seem to belong to the lucky ones with a working BT facility with my Peugeot 5008.
[Galaxy S III General] romwhacked:
Never had any issues with Bluetooth here, connects instantly with my car DVD with call function,data sharing is fast and uninterrupted with my iPad so can't complain

sent from third rock...
[Galaxy S III General] -error:
Hello.

Do you guys see that huge battery drain as I do? It may be not related to CM, but...
[Galaxy S III General] clamitas:
I hade those two walelocks too.

Go to Settings - Location - Uncheck Wifi and Mobile network. That will take away the wakelocks.

The phone will take a bit longer to set location though.
[Galaxy S III General] unrealps:
I don't agree. I have problems with bluetooth too. In my car only the first call works fine, after that I miss the sound, if phone ring and i answer without had disconnected/connected the bluetooth before i don't listen anything. So i think there are some problems with sound routing when using bluetooth.
[Galaxy S III General] aouni_tahech:
Same here with my Motorolla TX 500 ! Not a single issue.
[Galaxy S III General] romwhacked:
its all device related or position of the moon or what you had for breakfast ,so on and on and on.... :p :D

sent from third rock...
[Galaxy S III General] aouni_tahech:
Or where I live. Dubai ;)
[Galaxy S III General] romwhacked:
so true.. we Dubai guys have all the fun. :beer:

sent from third rock...
[Galaxy S III General] memaxxx:
Maybe the changes

<<ANDROID_PACKAGES_APPS_DSPMANAGER 2013-09-17 07:31:50

Merge "Listen to A2DP profile connection instead of device connection." into cm-10.2>>

will make everything good :)

---------- Post added at 12:01 PM ---------- Previous post was at 11:56 AM ----------

Seems good....

h t t p ://review.cyanogenmod.org/#/c/50479/1/src/com/bel/android/dspmanager/service/HeadsetService.java

Can't wait to download the newest build :D
[Galaxy S III General] svetloslav:
I noticed that in 4.3 Bluetooth has started consuming less battery (especially in a stand-by mode) and connection stability for me has remained the same with big brands equipment. Off-brand devices with flaky Bluetooth implementations on the other hand have had always problems. The nasty bug of power drainage after a call however keeps propagating through revisions. I find this a really important thing to work on.
[Galaxy S III General] Moster2:
We currently have no active device maintainer. Codeworkx is busy unfortunately and I dont know if xplodwild is still interested in cm
[Galaxy S III General] svetloslav:
That is one darn sad news.
[Galaxy S III General] simono_pl:
Yes, but we must have fixed little issues. CM10.2 is almost perfect for me with some issues with that we can live for some time. Now this rom is most stable for daily use.

Wysłane z mojego GT-I9300 przy użyciu Tapatalk 4
[Galaxy S III General] Milmar71:
did you fix battery drop after call ?
[Galaxy S III General] Moster2:
You could have read at least this page. We talked about it and no, its not fixed
[Galaxy S III General] gaui:
I'm on nightly 16.09 and the notification and ringing volumes are really low. Wasn't like this in previous nightly
[Galaxy S III General] SaphirX:
If I'm listening to music and my phone is on silent or vibrate and I get a message or an email I also get a notification sound. In addition my phone switches to non-silent.
[Galaxy S III General] chrisxpierce:
I went back to ARHD 13.3. The volume wake feature is a must, and it simply does not work on CM.
[Galaxy S III General] benand:
can you check the baseband version ?

I had simililar issues and for the moment it disappear after flashing a Samsung based ROM for 4.2.2 Xxufme07

Envoyé depuis mon A500 avec Tapatalk 4
[Galaxy S III General] SaphirX:
Under settings - keys the second option from the bottom is about waking up your phone with your volume buttons.
[Galaxy S III General] endolin:
No call in audio

In the last nightlies the "no call in audio" bug reappeared. My workaround currently is to enable/disable speaker during call. after this the issue is solved until reboot.

logs from nightly 17.09.2013

logcat: http://pastebin.com/8Ry2mGgK

radio: http://pastebin.com/VkrSHyua

it seems that earpiece is set as standard audio output in call.

...

E/audio_hw_primary( 1912): Entering IN_CALL state, in_call=0

D/audio_hw_primary( 1912): select_output_device: AUDIO_DEVICE_OUT_EARPIECE

...
[Galaxy S III General] fenritz:
Wifi randmly disconnects

Hi I have weird issue with Wifi. This problem also persisted on 10.1 RC2. Wifi randomly disconnects and reconnects very quickly. Same thing happens on different access points. On Sammy roms or AOKP I never had such problem before.

Any ideas how to fix or how to debug what's going on?
[Galaxy S III General] chrisxpierce:
Yep, got that checked. It does work, just not after it goes into deep sleep.

---------- Post added at 06:06 AM ---------- Previous post was at 05:20 AM ----------

Yep, got that checked. It does work, just not after it goes into deep sleep.
[Galaxy S III General] Scarface1991:
Great News!!!

CyanogenMod is now a company. Steve (the founder of CyanogenMod) and other members of the CM Team have made CM their daily job. This is amazing! This means CM will be even better in future because they are focusing on this full time now rather than it being just a hobby.

Here are pictures from the new company posted by Steve (Cyanogen) himself ;)

https://plus.google.com/100275307499530023476/posts/A86JnqUoLM5

Read about it on Android police:

http://www.androidpolice.com/2013/0...res-7-million-in-funding-and-opens-cyngn-com/

Great things are coming guys :)
[Galaxy S III General] killall:
Well I hope they hire a maintainer for the SG3:p
[Galaxy S III General] Scarface1991:
As a matter of fact, they are hiring designers and engineers. So if anyone is skilled enough and interested, take the chance :P
[Galaxy S III General] xrad:
It also means they intend to somehow moneterize CM. As far as I understand they haven't yet shared how they plan to do this. Hopefully we'll soon learn more about this, until then I'll hold my breath.
[Galaxy S III General] Scarface1991:
Well I don't think that the ROM will cost anything to use but they could implement some kind of ads or they could make deals with Hardware manufacturers to release their devices with CM already installed (Android Police mentioned that they already have at least one hardware partnership in the works)
[Galaxy S III General] Xbto:
The Cyanogenmod team is also doing a reddit AMA. If you have any questions for the CM team ask them there! :good:

LINK
[Galaxy S III General] Scarface1991:
For now they don't seem to focus on money. They first want to build an even stronger user base and other compelling features. Afterwards there are numerous ways to monetize the product as Koush explains on Reddit:
[Galaxy S III General] BrunoAlkmim:
I have problems with cyanogen camera, video mode, can not use the flashligt, sorry for my bad english,