yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Kord:
SCREEN NOT TURNING ON AFTER THE CALL

I'm trying to investigate what is causing screen not turning on after the call and what I found is, that after some time, when I have screen near my face (example during a call via telephone, skype or messenger), the proximity sensor is turning off and that's why screen isn't turning on. Also, after the call, my S3 is always locked (I see lockscreen) and I'm convinced that I should have phone app ( or Skype, messenger - depends from which app i made a call) on the foreground instead of lockscreen. I'm right?
[Galaxy S III Original Android Development] Bojmjma:
60/75/90/105/134/170
[Galaxy S III Original Android Development] tokict:
Anyone on 02/02 nightly build having problem while sending SMS? I can't send SMS at all, but can receive it.

EDIT : SOLVED after set my SMSCENTER number
[Galaxy S III Original Android Development] wjneto:
I can not access my sdcard and internal memory via USB
[Galaxy S III Original Android Development] Andi17:
Did you select MTB After connection your Phone with the PC?

---------- Post added at 05:40 AM ---------- Previous post was at 05:39 AM ----------

Use the app flashify and install the latest twrp recovery.
[Galaxy S III Original Android Development] yoahmad1995:
Thank you very much... You made my day!
[Galaxy S III Original Android Development] scobo16:
İs it working usb tethering? I am trying but it is not working.help me
[Galaxy S III Original Android Development] tokict:
Working as it should for me
[Galaxy S III Original Android Development] sunny1234590:
New build has live lock screen! What exactly is this?
[Galaxy S III Original Android Development] Cis#:
Yes, forgot to mention it, I did. Then it reconnects but the option falls back to "loading" again (first option).

Now I retried it at work and it seems to work and it has a different icon, so my only clue is my Windows has cached the old connection and it's not valid through different ROM. So when I'm home I will try to uninstall the driver to let it install again.

Flashify is a great tool, I finally could replace my recovery. The TWRP recovery is very neat, I've to admit. Now it could install gapps, successfully. Even Xposed v80 SDK 23 ARM works like charm. I'm very satisfied.

Thank you!

-----------------------------------------

Now, I installed the nightly from yesterday, but there is already a new nightly. This was a good situation to test updating. But the newest nightly (3rd February) fails on the MD5 check when download is complete. Anybody got the same issue?
[Galaxy S III Original Android Development] Andi17:
Download it from the officiell cm Homepage. Ich neuer hat Problems.
[Galaxy S III Original Android Development] Stefo1978:
Hi everybody! Just a little question: now I'm on latest CM11 snapshot for I9300. Can I dirty flash these nightlies on my current system, without wiping data?
[Galaxy S III Original Android Development] forkbomb444:
Yes, you should be able to. I would make sure you have a backup of all the important stuff though, and flash an updated gapps package when you flash the CM13 nightly.
[Galaxy S III Original Android Development] dagustl:
Hello.

I have flashed a frieds S3-i9300.

Can anyone confirm FC on Setup Assistant and Google Play Services after flashing the GAPPS?

I have installed Flashify and installed TWRP (downloaded with flashify) and tried with CM13 from 2.2.2016 and 3.2.2016 always with clean install and flashed the GAPPS after first rebooting once.

No Problem after reboot after install CM13. Everything is fine.

The FCs appear after flashing the GAPPS. (Cache and Dalvik wiped of course)

Have tried Micro and Pico GAPPS.

When i tap on "ok" on the FC Setup Assistant message, i can see shortly the FC message from Play Services and then FC message from Setup Assistant appears again.

Maybe someone has a solution?

Thanks :)

EDIT: Have also downloaded just the Playstore apk from APKMirror and installed with the Filemanager in Android; But the same FCs appear...
[Galaxy S III Original Android Development] JohnSmit268:
Try flashing gapps along with the ROM at the first time and not to reboot to the ROM and then flash gapps. And use an updated gapps file from opengapps.org(any ARM 6.0 gapps package of your choice).
[Galaxy S III Original Android Development] maciocho:
Phone calls over Bluetooth only in 2g

Hi,

I already asked about this but there were no replies, can anyone confirm that phone calls only work properly over Bluetooth in 2g?

Thanks
[Galaxy S III Original Android Development] Flummi.FFM:
Try to flash both cm13 + gapps together without reboot before flashing gapps. This worked for me
[Galaxy S III Original Android Development] dagustl:
Hi JohnSmit268

I already had the newest gapps from opengapps.org. There is a Link to this page on first post. ;)

Did again a full-wipe (this time also with formatting internal storage) selected ROM and also GAPPS Pico as a second file in TWRP and flashed them at once.

Seems to work fine now. Opened PlayStore and added my account-data just for testing. Also works.

Will report if something will FC again, but seems to be ok for now.

Thanks ! :)

[MENTION=6816869]Flummi.FFM[/MENTION]

Yep, JohnSmit268 also wrote this. Works for now.

It just did a reboot on the S3, because on my ArcS i must do this before flashing the GAPPS. If i flash them directly after the ROM i sometimes got problems.
[Galaxy S III Original Android Development] MaThiuu:
got 2 problems here

1_ i cant unlock the device with Miband, it connect but when i try to add it to smart unlock it doesnt work

2_ i dont have mobile data, i tryed another APN and its not working

Any suggestion?
[Galaxy S III Original Android Development] FadeFx:
So you read untill the downloadlink and not a word after? Try reading the first post again, your problem is mentioned exactly there... ;)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Apmauj:
1- I have a Mi1S, you need to set the pin and in smart unlock under (screen block ~ Pantalla de bloqueo) you need to get into "trusted devices" and "add new trusted device". I have paired it normally via BT then realised about this feature, and it's working pretty fine (from time to time the phone asks for pattern anyway e.g after reboots)

2- mobile data working fine on 0302, there was some post some pages back that someone was having a similar problem with APN and it's configs..
[Galaxy S III Original Android Development] Flippiej:
At the moment this gives you a lockscreen where the colors changes all the time. Can't find other live lock screens so far to download though. Does anyone know a place for this?
[Galaxy S III Original Android Development] MaThiuu:
yeah i know how to pair it but when i put add new trusted devices it doesnt work, just doesnt search. thnx anyway!

EDIT: ok problem solved with mobile data, just switched 2g/3g and it worked
[Galaxy S III Original Android Development] JohnSmit268:
The battery life is epic on the new build(with greenify) and I love this aspect but it's likely that I get WiFi disconnects each 2 seconds!!! It's maybe from this commit(not sure): WiFi: Ensure supplicant stopped in WiFi_stop_supplicant can somebody confirm this?
[Galaxy S III Original Android Development] azazello22:
Never had problems with Wi-Fi on any build (now I'm on 3/2).
[Galaxy S III Original Android Development] Flapdrol2005:
Does smartlock work with cm13?

I can't get it to work with locations on my s3 with the cm13 release.

does annyone have a tip?
[Galaxy S III Original Android Development] pensanto:
Help aiutooo

Salve io ho un grandissimo problema... non mi funziona la connessione dati come mai??? cosa posso fare???

Hi I have a big problem ... it does not work the data connection why ??? what can I do???
[Galaxy S III Original Android Development] MaThiuu:
try switch 2g/3g, works for me by this way
[Galaxy S III Original Android Development] plomizo:
I have been experiencing wifi dropouts during sleep for some weeks now. I often switch on the phone and find it connected to 3G instead of the wifi. After switching on, it quickly reconnects.

After some digging in logcats and in other threads, I have now found dropouts follow the WPA key renewal, that's every 10 minutes. As a workaround, I have setup a non encrypted SSID, and the dropouts don't happen any more. That also explains why dropouts don't happen at work, because the wifi at work is also non-encrypted, protected with a captive portal.

I have also seen people with different devices with the same problem, and all IPhones, iPads and Windows PCs at home work ok, so it all seems to point more towards AOSP than a device-specific issue...

But then it also seems that most people here do not see this problem. Is everybody using WPA2-PSK with no problems? It could also be something in AOSP in conjunction with the way my router (Fritz!Box 7390) manages WPA key renewals...

My 2 cents
[Galaxy S III Original Android Development] MultiPDev:
The wifi dropouts happen to me also, but they're not too often. - on WPA2-PSK

---------- Post added at 23:50 ---------- Previous post was at 23:49 ----------

Hey guys, which cm version do you think is faster? cm12 or cm13? I tried cm13 but it got really slow with time(maybe because of xposed?), I just flashed cm12 and it seems smooth but which is better on the long term? BTW, which kernel do you recommend me?

Thanks!!
[Galaxy S III Original Android Development] rlon23:
CM11 with boeffla, yes CM11. I am using Xposed and CMs own Superuser.
[Galaxy S III Original Android Development] rchtk:
There's a bug report, in fact several.. on these symptoms and it is linked to another device so it is indeed not specific to the s3.

When the s3 station enters in sleep mode, network problems appear. As a consequence, when AP performs a rekeying and sta does not answer then association is broken.

If you have rekeying problems when awake then that's another bug.

Google being mute on the problem is unacceptable, they simply need to allow the user to disable this bloody power saving mode (which in my case only saves 1%/2h btw). The problem is very easy to reproduce given the number of AP/android affected.

Could be that the wireless driver or firmware doesn't have a direct interface anymore (ioctl maybe?). I am not getting this problem on LP.

Putting a wifi lock is supposed to keep the radio on (as long as the app is kept in memory) but I don't see it in practice :lock gets removed for whatever reason (could be scanning)

etc...
[Galaxy S III Original Android Development] JohnSmit268:
Take this kind of discussions to the Q&A thread. This thread is for active discussions on development and tracking bugs. Not for asking for which ROM to install or which custom kernel to use.
[Galaxy S III Original Android Development] thopiekar:
Have the same problem with the WiFi dropouts the same router (Fritzbox 7490)!

I also upgraded my Samsung Tab2 (p5100) and there those problems do not appear.

So I guess it's kernel or driver specific.
[Galaxy S III Original Android Development] rlon23:
A PM to the OP would be enough, I just answered what he asked (couldnt pm him). Better to answer than having them asking again and again.

You guys get a little annoying with your posts about off topic.
[Galaxy S III Original Android Development] wo88les:
Flashlight not working here, also I have su icon in notification constantly
[Galaxy S III Original Android Development] wjneto:
my solution ...

settings

About phone

Click 5x to unlock "developer options"

return settings

enter " developer options"

Click on "Select USB Configuration "

Replace with charging and return to MTP

return to home

Connect the phone to your PC and see if solved
[Galaxy S III Original Android Development] FadeFx:
Flashlight should work, it dies for me. Pull down qs and hit the su tile, it will tell you what app has aquired su, if you don't see the su tile, just add it. If you know what app is using su permanently, you know why the icon is there and what to do against, es-fileexplorer is an example for not releasing su after usage...

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] miketabs:
Hi Guys,

after flashing cm13 with gapps from http://xdaforums.com/android/general/gapps-gapps-6-0-1-minimal-t3276606 because of status(6) issue on cwm recovery my WIFI connection is stable but when i flash superSU 2.67 cause i wanted to install boeffla app and kernel my WIFI connection begun to OFF AND ON. anyone encounter this problem or did anyone notice it?

Thanks.
[Galaxy S III Original Android Development] baltics:
Yes the phone app for XDA is hit & miss when posting.
[Galaxy S III Original Android Development] monte22:
OK thanks will keep in mind.
[Galaxy S III Original Android Development] baltics:
As the creator of Boeffla advises, there is no need to wipe anything when installing his kernel over a stock kernel.

In fact after installing the zip, TWRP simply advises 'to reboot'.
[Galaxy S III Original Android Development] hamsharana:
Does fat32 sd card work in last nightly update
[Galaxy S III Original Android Development] baltics:
Since installing Boeffla beta 2, on today's update I have not experienced any flickering.

I use a bc config file with the kernel. That may help too.

This kernel by default sets as 'enforcing:.
[Galaxy S III Original Android Development] monte22:
TWRP 2.8.7.3

but i flashed kitkat cm 11 rom just to check there mobile data working normally on start up
[Galaxy S III Original Android Development] baltics:
I had this problem when I first installed v7 of the ROM.

I had manually wiped system data etc rather than factory reset.

I fixed it using factory reset and wiping cache etc after installing.
[Galaxy S III Original Android Development] puzzle29:
After a ROM update (dirty flash) need to installing boeffla kernel again ?

And where I can find it ?
[Galaxy S III Original Android Development] sanguinesaintly:
http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm/cm13.0_download/Test/
[Galaxy S III Original Android Development] DrmohamedShawky:
i had flickering with it :D
[Galaxy S III Original Android Development] puzzle29:
Thy
[Galaxy S III Original Android Development] ashjas:
It doesnt help.

BTW, i cant imagine why, G+ can request a permission:erm=com.android.gallery3d.filtershow.permission.WRITE :eek:
[Galaxy S III Original Android Development] Hawaiihemd:
Generally you are correct. That's why everybody should announce their setup with their problem. That can lead to problem solving by exclusion.

Just to let you know: dev has stated that current "flickering problem" is *not* kernel related (see here).

See here.
[Galaxy S III Original Android Development] izopi4a:
hello lads,

does anyone knows how to fix "md5 verification failed" in OTA update ?
[Galaxy S III Original Android Development] fonfox:
Think its dowload Problem

on older Version this appears for me to. Try several times and it works. Or download it manuell
[Galaxy S III Original Android Development] chirag2718:
flickering is not coz of boeffla kernel.. the same has been said by simons (our CM maintainer) this might be fixed soon he is working on it
[Galaxy S III Original Android Development] Scorpionea:
I did have same issue on previous builds but this time I stayed at settings untill it was finished

Also go to apps and show system then in cm updater ,storage permission disable and enable it and try again

Sent from my GT-I9300
[Galaxy S III Original Android Development] matt1966:
Anyone knows how to get Navigon navigation running?

Keeps telling me there is no SD card and closing right after this message.

Can't install any cards for navigation.
[Galaxy S III Original Android Development] viktor92:
Is there any SuperSu what works with nightlies ?, integrated root access seems don't remember well the choices made...
[Galaxy S III Original Android Development] RajashekarReddy.A:
Did you get something positive by flashing the latest nightly ?
[Galaxy S III Original Android Development] ansh1996:
CWM is all but outdated. Use TWRP latest version, that should solve the gapps problem.

Why would you need superSU to install boeffla?
[Galaxy S III Original Android Development] miketabs:
Hi ansh1996,

cause boeffla app wont open. can remember the exact message .

thanks for the reply. :)
[Galaxy S III Original Android Development] azazello22:
There are some guidelines to follow: TWRP as recovery, and use the internal SU as it is working perfectly. Boeffla app surely don't need SuperSU as Boeffla himself suggests not to flash SuperSU, as it is not needed and seems causing lots of troubles.

Then, report issues only on stock configuration.
[Galaxy S III Original Android Development] Cis#:
Thanks, but it's a problem with my PC, on work everything works.

To everybody: Guys do you use Titanium Backup and could you restore your backup after upgrading to CM13? It does not detect my backup files, already tried to set SELinux to permissive, but ain't working.
[Galaxy S III Original Android Development] miketabs:
Thanks, i dont notice that TWRP has internal SU. copy and noted. :good:
[Galaxy S III Original Android Development] rlon23:
He's referring to the SU that comes with Cyanogenmod.
[Galaxy S III Original Android Development] Cr453r:
Not TWRP. CM13 has internal root access option, in developer options you can turn it on
[Galaxy S III Original Android Development] Andi17:
Yes it Works. Please have a Look in q&a thread post 87.
[Galaxy S III Original Android Development] Cis#:
Where is that Thread, got a link for me please?
[Galaxy S III Original Android Development] Andi17:
http://xdaforums.com/galaxy-s3/help/qa-cyanogenmod-13-nightlies-i9300-t3275604

Here, Look on post 87
[Galaxy S III Original Android Development] Cis#:
You sir, are my personal hero! All that was required was to use the DocumentProvider to browse to my backups. Ouch! :D
[Galaxy S III Original Android Development] Andi17:
The way is not complicated but you have to know it. I used the same Video. :)
[Galaxy S III Original Android Development] wo88les:
Rebooted phone and flashlight works again I think cam driver had crashed, could the su icon be coming from boeffla? Just started showing constantly on 3feb build and boeffla is only root app I have

Edit. Scratch that greenify is root app just realised sorry guys :)
[Galaxy S III Original Android Development] Sneakdovi:
wifi still not stable, ON and OFF everytime... why so hard to fix?
[Galaxy S III Original Android Development] stewazy:
Is this room more stable than archidroid 3.15?
[Galaxy S III Original Android Development] izopi4a:
because this rom is free ...
[Galaxy S III Original Android Development] sgs9:
wait some hours, i will test archidroid 3.15.
[Galaxy S III Original Android Development] Apmauj:
Pretty much the same, I was using it until January, you can say this is a daily driver (at least for me, i don't have all pro problems related to 3G, camera, wifi, etc) :confused:
[Galaxy S III Original Android Development] Cis#:
Audio shuttering on Bluetooth

Can anybody confirm or even provide any solution to this?

The latest nightly of Feb 03 seems to have shuttering audio when listening via bluetooth. BT Headset is fine. I'm unable to listen to music. It's like the music is playing for one sec and then it stops transmission and starts it again and stops it again and so on in few ms cycle.
[Galaxy S III Original Android Development] wo88les:
Just a quick note, battery performance on Feb 3rd build is much better :) awesome work devs
[Galaxy S III Original Android Development] Apmauj:
Hi, I have a chinese BT earphones (M2), was listening to radio (3.5mm jack plugged for antenna), now I tried hearing music using "little bit music" player, it's also working with my car's audio for music and calls (a home to work trip), and it's working fine, no shutters, pauses or noise... (a Mi1S bracelet is also connected in backgound..)

Edit: Are you using many apps at the same time as audio player...?
[Galaxy S III Original Android Development] MultiPDev:
Oops, you're right. I'm sorry. I'm gonna ask it in the Q&A thread.
[Galaxy S III Original Android Development] NickName98:
A reboot will solve this. I also have the same issue after a few hours using the phone without a reboot. I'm not sure what's causing it.
[Galaxy S III Original Android Development] Cis#:
No, as stated, it's not my headset and it happens on all kind of apps (WhatsApp, video player, browser). None of them are running parallel. Before I was using this headset on the same phone with CM12 (unofficial). It must be a bug, hoping I'm not alone here.

Reboot seems not to solve it.
[Galaxy S III Original Android Development] JohnSmit268:
[MENTION=5405215]forkbomb444[/MENTION]

Description

In the 3 and 4 Feb nightlies I have heavy WiFi disconnects. Likely every 2 seconds!! I think the new WiFi commit in 3 Feb nightly caused this. It makes the ROM unusable for me. Crap!:(

Logcats

Attached(the logcat is xposed free)

Edit:Sorry, my bad. It happens only on one of my WiFis so it is not about the new nightly sorry for mistaking and low testings.

Note: that WiFi works fine on CM 12.1
[Galaxy S III Original Android Development] sanguinesaintly:
Clean flash ? I haven't seen other reports of such frequent dropouts.
[Galaxy S III Original Android Development] cobras3:
I have clean flashed the newest nightly +open Gapps. There aren't WiFi disconnects. Only in standby, when the screen is off. You should clean flash
[Galaxy S III Original Android Development] JohnSmit268:
Yes of course if you check logs you can see that I even don't have gapps. I clean flashed to take this log fresh and totally spam free.
[Galaxy S III Original Android Development] Logan:
Guys anybody got an idea how to stop camera from auto focusing in videos and sometimes stop button doesn't work in recording video using the camera
[Galaxy S III Original Android Development] sanguinesaintly:
What recovery do you use to wipe and flash - TWRP 2.8.7.3 I assume ?
[Galaxy S III Original Android Development] arifnasirshaikh:
Found a bug.

After every restart live lockscreen auto enables.. Have to manually enable and then disable to get rid of it..
[Galaxy S III Original Android Development] JohnSmit268:
Not facing it. Do you use anything custom? If not try taking a log. But note that even if that bug exists this is not device bases and it is a CM bug so this is not the place to report this bug. Try reporting it using cyanogenmod jira.
[Galaxy S III Original Android Development] Bojmjma:
You don't need to reboot, use (Mediaserver Killer) from playstore to fix it.
[Galaxy S III Original Android Development] androbot2020:
Search the thread for bluetooth stuttering and try that solution. BT is working ok for me after doing that.

Víctor
[Galaxy S III Original Android Development] forkbomb444:
If it's that simple you can fix it :)

If you turn wifi off, does it improve? For me it's mostly fine except for when there's wifi activity.

known bug
[Galaxy S III Original Android Development] rhyzan:
I don't know if anyone has this weird issue. It happens just a few days ago. Good thing it didn't happen again but I would try to replicate the issue soon.

So after the battery drains normally the device would turn off. For some reason my device boots to Factory Mode. Removing the battery and putting it back again turns the device on again and either it goes to Factory Mode or the charging screen (I didn't plug my charger during that time.)

Obviously I don't have any logs for this but I'm on Jan 30 build and on Boeffla Kernel if that helps.
[Galaxy S III Original Android Development] flynn1411:
I´m on 20160127, I have video playback problems; it stops playing and says: "video cannot be played" whenever I try to forward some part of the video, also the audio is faster than the video I can notice it. Does anyone has the same? The rom is really awesome, great battery life+performance. Other than the video bug, everything works fine!
[Galaxy S III Original Android Development] tokict:
Try to update to the latest nightly release. I don't have problem you've mentioned with the latest nightly build.