yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] arunkafley:
Cannot receive calls in the new nightly
[Galaxy S III Original Android Development] sunny1234590:
No such problem on my side. And try posting it in only one thread. No need to post it in two different threads all the time.
[Galaxy S III Original Android Development] ralfbergs:
Then why did he state he got a 9300?
[Galaxy S III Original Android Development] arifnasirshaikh:
Cannot call nor receive any phone calls... Data is working fine.. Already few people reported..
[Galaxy S III Original Android Development] fazla86:
can not make or receive calls on 16.02. nightly

sms and data is working
[Galaxy S III Original Android Development] :
So what should it be in your opinion? I have a t-mobile S3, too and it's GT-i9300. Or not?
[Galaxy S III Original Android Development] sunny1234590:
The T-Mobile Variant has a Snapdragon processor, isn't it? [MENTION=6713660]Black_Focus_X[/MENTION]

And if I am not wrong it is LTE variant. Please, check again, model should be something else.
[Galaxy S III Original Android Development] sanguinesaintly:
Possibly an i747 ? Sorry to prolong the OT.
[Galaxy S III Original Android Development] :
Hm ok. That's interesting
[Galaxy S III Original Android Development] hamza touati:
[MENTION=5405215]forkbomb444[/MENTION] i think we have a bug i cant make or receive calls in 16/02 nightly ????

will there be a fix in the next nightly ?????
[Galaxy S III Original Android Development] kewlpanda:
Having problems with it crashing saying unfortunately,setup wizard has stopped I reinstalled cm13 and still nothing
[Galaxy S III Original Android Development] sunny1234590:
You need to flash ROM and Gapps together else it will give error.
[Galaxy S III Original Android Development] kewlpanda:
I flashed cm13 then gapps nano then restarted to system
[Galaxy S III Original Android Development] whoadood:
Cleared /data ?
[Galaxy S III Original Android Development] xdawaldo:
Making/Receiving Calls Nightly 16.02.

Here the same, no calls poossible.

With 1402 Nightly all well.

Thnx for the great work !
[Galaxy S III Original Android Development] arsenico78:
Same problem for me, no calls possible since last update :(
[Galaxy S III Original Android Development] forkbomb444:
Does adding this line:

ro.ril.telephony.mqanelements=5

to /system/build.prop and rebooting fix calls?
[Galaxy S III Original Android Development] arifnasirshaikh:
Reverted to previously nightly but.. I'll give it go again..
[Galaxy S III Original Android Development] pupido:
I tried it and it worked.

You are a great.

Thanks.
[Galaxy S III Original Android Development] arifnasirshaikh:
Thank You..

and welcome :)
[Galaxy S III Original Android Development] FedericoPS:
Doesn't work.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] sunny1234590:
[MENTION=5405215]forkbomb444[/MENTION] sent a message see.
[Galaxy S III Original Android Development] arifnasirshaikh:
Nope not working...and one more thing i've i.e after system completes android upgrading process, device reboots
[Galaxy S III Original Android Development] forkbomb444:
Hmm, this may take some investigation then. I won't be able to look into it straight away, but I'll have a look as soon as I can. Stay on the 2016-02-15 nightly is my recommendation for the moment.
[Galaxy S III Original Android Development] Apmauj:
Can confirm the calls not working, for me it stands as "dialling" until i finish the call, then it shows "Hanging" and stays like that until i press home or something.

And if you open calls again, it shows a menu to use the numpad, return to call, or add another call, i have to reboot the phone in order to fix the dialer..
[Galaxy S III Original Android Development] mondogarp:
call not working

Hi, as already told by other people, cannot call or receive with 16/02 today nightly.

It seems that the call is received but not processed. If I try to call my mobile from another phone I heard the standard working tone on the other phone but no "incoming call" notification and sound on S3
[Galaxy S III Original Android Development] arsenico78:
Confirmed, same problem
[Galaxy S III Original Android Development] rahulkori:
same problem here also
[Galaxy S III Original Android Development] deardo:
I confirm myself. When I try to call hangs I can no longer even get I just reboot the system
[Galaxy S III Original Android Development] xdawaldo:
Not working

This does not work for me, thnx for trying to help.
[Galaxy S III Original Android Development] arunkafley:
Tried it, does not work. Reverting to 02-14 nightly
[Galaxy S III Original Android Development] wizkod:
I think that other operator like intl for GT-I9300 have already CM 13! Not me ?
[Galaxy S III Original Android Development] DrmohamedShawky:
call not working
[Galaxy S III Original Android Development] sanguinesaintly:
I think we've got the message now - calls are not working correctly - no need to keep posting the same thing - let the devs sort it out in their own time please.
[Galaxy S III Original Android Development] dare74:
Confirmed, same problem!
[Galaxy S III Original Android Development] whoadood:
We need 100 more confirmations to earn a Ferrari, please keep them coming.
[Galaxy S III Original Android Development] McMatias_2:
When i try download a PDF file in stock browser or Chrome browser, goes to download but doesnt download (and yes i had put the permissions ok)

anyone know how to solve this???

And another thing, in the notification bar , don't have meterology on ,when i have that option on :/ why?
[Galaxy S III Original Android Development] djwarlock:
Hi, this is my first post on the forum... :)

Anyway I just installed the last version of cm 13 but I have problem with calls I can't receive and make any calls, I have done something wrong? Maybe a setting that I didn't know? Sorry for my English is not my native language! :)
[Galaxy S III Original Android Development] Flummi.FFM:
Hi and welcome to the thread.

This Problem is well known and you should just flash the nightly of 14.02. until it will be fixed......

It is also a good idea to read the latest 5-10 pages of the thread or to use the q&a section if you will have General questions about the Rom

Greets and cheers
[Galaxy S III Original Android Development] cobras3:
Deleted because [MENTION=6816869]Flummi.FFM[/MENTION] was faster and he can read my mind
[Galaxy S III Original Android Development] arifnasirshaikh:
That's the way we should treat new members.. And talk to others members..decency won't cost you money or anything.. Sorry Out of topic but we should have some ground rules.. Many rudes post every now and then.
[Galaxy S III Original Android Development] justguesswho:
me too:crying:
[Galaxy S III Original Android Development] Trafalgar Square:
If you want, you can report the problem in my AICP Thread too.
[Galaxy S III Original Android Development] X301:
Not most stable, CM13 is in active development, AFAIK its official.
[Galaxy S III Original Android Development] chirag2718:
is doze working?

m here after a month so pls anyone could answer properly to it?
[Galaxy S III Original Android Development] izopi4a:
can soomeone tell me what i am doing wrong with the update please...

so after a couple of failed md5 sumcheck fails, finally the ota update is ok. I click update the phone reboots and tw recovery does something, reboots couple of time and enters the tw recovery menu where i click reboot -> system. When i check about phone i see still the build form 18. I did again the same thing and i get the same result, i tryed from tw recovery install -> select the zip which OTA downloaded sdcard/13-0.20151219-nighty, it complates reboot and still shows 18...

Thanks.
[Galaxy S III Original Android Development] monte22:
could you plz elaborate in steps how u got data working plzzzz:)
[Galaxy S III Original Android Development] chirag2718:
i found a new problem in todays update...

i formatted my SD card with exfat format n loaded with some data in it..

now when i mounted it in my phone... some data is visible and some is not..

and when i go to settings and click on storage and system i get a message as UNFORTUNATELY THE SYSTEM HAS STOPPED
[Galaxy S III Original Android Development] monte22:
yes G+ dont install

it also dont install from apk gives same error 505
[Galaxy S III Original Android Development] JohnSmit268:
Another bug added

I can't install my apps from the file explorer. When it was trying to load their pics I got a force stop. Even tried with es file explorer again force stopped. Then tried to send a apk using Bluetooth to my phone when wanted to install it, received the error that there is no application to handle this kind of file!! Finally installed es from Bluetooth folder using explorer could install it when it was only one apk in that folder. I tried moving that folder to somewhere else again force stopped maybe it only became stopped when it tried to load the icons. Know that it looks silly bug report but it's happening and I can't install apks.:eek:
[Galaxy S III Original Android Development] Logan:
I had an issue after flashing 18 nightli wifi turned to battery drainer (41% usage) reflashing/updated solved it but i don't understand how did that happened

And the music cm app force closed so using poweramp atm
[Galaxy S III Original Android Development] crisis_trustee:
Try install last Google Play Store - http://www.apkmirror.com/apk/google...google-play-store-6-0-5-android-apk-download/
[Galaxy S III Original Android Development] matt1966:
Use open Gapps full.

G+ is included and working.

http://opengapps.org/?arch=arm&api=6.0&variant=pico
[Galaxy S III Original Android Development] -=|MisterY|=-:
Here's my quick summary of today's experiences.

Clean-flashed version 18/12.

Found that CF.lumen does not work with the original driver (that requires root). Also, Greenify can't hibernate any apps. Titanium Backup can't write to a directory on external SD card, mounted as removable storage. Total Commander, however, has no issues writing to the same card.

Thinking this was some issue with root, I installed SuperSU 2.62 but that did not improve anything. I'm mentioning these issues here because I also have Android 6 (stock with SuperSU) on Nexus 7 and all these apps work just fine.

At some point the data connection disappeared. It turnes out that probably the APN was switched (somehow). Setting it manually to another one, that was also on the list, corrected this issue.

After going through the backlog of posts, I downloaded the build 19/12 via CyanDelta (thanks for the tip!). Flickering is still present but my subjective feeling is that it occurs less frequently. This could also be false because I was reinstalling and reconfiguring lots of stuff with the previous build and not so much with the new one.

Thanks for the work on the latest-and-greatest version of Android. Will report if I run into any other interesting findings.
[Galaxy S III Original Android Development] JohnSmit268:
For greenify to work use xposed framework+ donation pack and be sure to have version 2.7.1 not any beta versions.

For TiBU upgrade it to latest and it should work ( worked for me ) I have pro TiBU so far.

Any other app couldn't access storage give it the permission , close the app or reboot the phone open the app and if it works it's compatible with Android M and if not report bug to the dev of the app.

Anybody have issue with titanium backup just update it and it will work ( mine worked )
[Galaxy S III Original Android Development] achkap:
For tb (thanks to Killerdog)
[Galaxy S III Original Android Development] viktor92:
Flashed today nightly and all went fine. Most of the time I haven't flickering, but when it appears, it's a huge, epic flickering...
[Galaxy S III Original Android Development] knuckles1978:
I dirty flashed 19/12 official on top of the old build 7, and so far I haven't had any sign of the dreaded flickering.

Probably shouldn't have said that, you know what will happen now. :D
[Galaxy S III Original Android Development] -=|MisterY|=-:
[MENTION=6567265]JohnSmit268[/MENTION], [MENTION=2112467]achkap[/MENTION],

Thanks, guys! Those are great tips. Leaving the Beta program and installing the stable version fixed Greenify.

Tried reinstalling TB but ran into error -504. Fix for that is simply to delete the TB directory in /data/data (see https://forums.oneplus.net/threads/...kup-root-error-code-504-not-installed.239189/). Then used the storage provider as specified and everything seems fine.

Catlog was also fine after reinstallation.

The only odd case is CF.lumen. It crashes the ROM after allowing root access with the built-in su. That's not critical as there's a built-in lux but it would be nice to figure out what the problem is. Cheers!
[Galaxy S III Original Android Development] -=|MisterY|=-:
Deleted duplicate post
[Galaxy S III Original Android Development] tokict:
It's CM Bug, happen on every last cm 13 nightlies (all device)

Will be fixed on next nightlies.

http://review.cyanogenmod.org/#/c/125106/
[Galaxy S III Original Android Development] viktor92:
I've dirty flashed nightly 18 over build 7, and then dirty again nightly 19. It's very weird, as the flickering starts violently, and disappears almost instantly without any pattern. Disabling adaptative display reduced it quite a bit, at least in my case.

Finally I could uninstall system apps that I not use with TB, but I should enable internal root (despite having SuperSu 2.62 installed), and even that I should repeat the process many times with some apps, another weird thing...

All in all the rom is very fast and pretty stable, my external SD is still viewed as an USB storage from total commander, and still I have some write problems, but in the end, is incredible how fast is progressing MM on our beloved S3 :) :good::good:
[Galaxy S III Original Android Development] ansh1996:
Guys, please do not post screen flickering issue status with every nightly update. These updates are automatically built and daily changes are added.

If any fix regarding screen flickering is added it will be specifically mentioned in the changelog or posted by the dev himself in this thread.

Please refrain posting any status reports before 24 hours of device usage or at least two charge cycles, whichever earlier.
[Galaxy S III Original Android Development] forkbomb444:
More flickering fixes! Yay! Download this. If you see flickering with this build, post here. If you don't have any flickering after a day or two of use, post here *then* - the flickering is largely unpredictable, and there doesn't seem to be a reliable way to reproduce it.
[Galaxy S III Original Android Development] arifnasirshaikh:
Downloaded... Now i'll flash after this post
[Galaxy S III Original Android Development] azazello22:
No it is not. Please use the search function.
[Galaxy S III Original Android Development] 2phazt:
Does the nightly of 17.02. fix the call problem?
[Galaxy S III Original Android Development] sruday:
I am afraid, it looks like calls are still not working on 17.02 nightly

---------- Post added at 08:18 PM ---------- Previous post was at 07:58 PM ----------

I have now gone back to 14/02 nightly and calls are working.
[Galaxy S III Original Android Development] maciocho:
Yes, calls still not working for 17.02.

M
[Galaxy S III Original Android Development] sunny1234590:
The developer hasn't merged any commit regarding this issue. So, yeah it won't work until some nightlies.
[Galaxy S III Original Android Development] forkbomb444:
I have exciting news!

I've found the culprit. I'm able to provide a (temporary) fix, hopefully a proper fix will be included in the nightlies at some point in the near future(tm).

Instructions

Flash attached zip

Reboot

Profit

You will need to re-flash this zip whenever you install an update/reflash CM.

UPDATE: When this change is merged (*hopefully* before the next nightly), this fix will become unnecessary :)
[Galaxy S III Original Android Development] sruday:
Thanks . Your ROM is awesome. I will wait for this fix to be included in the nightlies.
[Galaxy S III Original Android Development] lithoc:
Hi,

Thank you very much, tested on 20160217 build and it working great
[Galaxy S III Original Android Development] Sneakdovi:
is wifi problem still present?
[Galaxy S III Original Android Development] Apmauj:
Wow, thanks for the fix, I tried 1602 yesterday and backed into 1402, now i just flashed 1702 and started to read the posts saying problem was still there...

Hopefully patch worked perfectly, thanks for your work.

Can anyone confirm if TWRP 3.0.0-1 takes way more time on flashing the nightlie? With old TWRP I flashed the ROM in 5 or less minutes, now it takes like 15 or 20.. (only tried dirty flashes for now)
[Galaxy S III Original Android Development] FedericoPS:
Yes, go back to TWRP 3.0.0-0.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] sunny1234590:
Wait, is that some sort of magic? It took you just one day to find the solution to it.

Amazing work there dev! :D
[Galaxy S III Original Android Development] whoadood:
Yes.
[Galaxy S III Original Android Development] forkbomb444:
Calls will be properly fixed in the next nightly.
[Galaxy S III Original Android Development] TWEAKiMP:
Thank you for your work. Can you say something about the issue that it is not possible to change the current track with the VolUp and VolDown buttons`?
[Galaxy S III Original Android Development] Maxoobidou:
Problem hasn't changed since the beginning and won't change ever for the s3.

Doze needs a low consumption sensor to work. S3 doesn't have one. So Doze doesn't work.

Forcing Doze to use the normal sensor would use more battery than Doze saves.

So No Doze on S3.

You can, however, get an app that enable Doze with other triggers. There's a few out there, you can probably find one. Hopefully you'll use the search button this time.
[Galaxy S III Original Android Development] sunny1234590:
AICP has doze enabled and battery life seems to have improved somewhat. I don't think it's a placebo effect. I think it's possible for S3 too.
[Galaxy S III Original Android Development] sanguinesaintly:
Other ROMs do indeed claim to have it enabled, so I really don't know. Some say yes, some say no.
[Galaxy S III Original Android Development] whoadood:
That's most probably a problem with CM, not with this device.
[Galaxy S III Original Android Development] wo88les:
Awesome work thanks :)
[Galaxy S III Original Android Development] dark_prince:
I'm really sorry for asking a noob question. Help a 1st timer on samsung out. I have bought a galaxy s3 just for skype calling for my mum. It had XXELKC JB 4.1.2 running on it prior to installing Cyanogenmod 13. Now I have unknown IMEI/Baseband and I do not know how do I fix it. If there is a restore or a fix to keep Marshmallow and restore no sim card/no baseband/no imei error please let me know. I'd love to have CM 13 on this phone just so make ease for my mum who's used to AOSP experience and touchwiz is completely new for her.

Thanking you in advance
[Galaxy S III Original Android Development] arifnasirshaikh:
Try flashing stock rom.. If you are lucky enough you'll get your imei back..

And be careful while doing full wipe.. Never touch efs..
[Galaxy S III Original Android Development] rp158:
[MENTION=479015]dark_prince[/MENTION]: I sent you a PM to avoid more OT
[Galaxy S III Original Android Development] infonote:
The nightlies are very stable. And since this is a secondary mobile, I use BOINC on it, and it did not even crash once.

However, Wi-Fi keeps disconnecting and connecting again. Other mobile devices do not have this problem.

I am updating to the latest nightlies but the issue still occurs.

Any idea?

Is this a known problem?

Thanks in advance,
[Galaxy S III Original Android Development] Brainyy:
I have the same wifi issue but only on specific wifi-s. I have tried to adjust the router's wifi mode (n / g) but that doesn't seam to be the culprit
[Galaxy S III Original Android Development] arifnasirshaikh:
Yes this is a known problem... But i never had any problems with wifi disconnecting or anything
[Galaxy S III Original Android Development] xdawaldo:
Auto-Rotate not working after some time

After reboot auto rotate works as expected. After some time (few minutes) it stops working.

In camera the symbol keeps rotating while rotating the phone. This indicates that the sensor is working.

But in all other apps (K9-Mail, Chrome, Browser....) auto rotate does not work anymore until reboot.

waldo
[Galaxy S III Original Android Development] zufa:
Thank youuu :) Great work dev! You just made my day ;)
[Galaxy S III Original Android Development] San716:
It worked! Thanks a ton!!
[Galaxy S III Original Android Development] scorthyn:
Can someone tell me the best LMK values for this rom or what setting to use on kernel adiutor (very agressive, agressive etc)
[Galaxy S III Original Android Development] arifnasirshaikh:
Check your inbox.. I've sent you pm
[Galaxy S III Original Android Development] hamza touati:
hello guys when will the phone calling bug fixed ????
[Galaxy S III Original Android Development] Scorpionea:
It will be fixed in next nightly
[Galaxy S III Original Android Development] toluca79:
I have the same Problem with my S2. Does this fix (#3240 ) work with the S2 too?
[Galaxy S III Original Android Development] Scorpionea:
And how we should know that ??

Just be patient and your issues will also be fixed, u have great devs in s2
[Galaxy S III Original Android Development] ansh1996:
And you can always backup and try it out. Most probably it will end up in a bootloop..but then you know fire sure that it won't work.

Or who knows, by magic it might just work and would save the devs and you some trouble. :)
[Galaxy S III Original Android Development] scorthyn:
I cant call people and when people call me nothing happens on my phone (using 17th nightly) is it a known bug? sorry just in panic and wanna know
[Galaxy S III Original Android Development] elhugo3:
Flashing that zip solve the problem

http://xdaforums.com/showthread.php?p=65368390

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] scorthyn:
WORKED

Thanks , worked
[Galaxy S III Original Android Development] pratspatel:
I cant get root access please help me at whatsapp 9426720561 plzzz
[Galaxy S III Original Android Development] arifnasirshaikh:
Check your inbox
[Galaxy S III Original Android Development] Hari23:
F2FS should be available in next build

http://review.cyanogenmod.org/#/c/132977/
[Galaxy S III Original Android Development] sunny1234590:
It would be optional. Those who wants to try it can give it a shot otherwise stay away from it. As Boeffla kernel developer says F2FS causes data damage and other such issues are there.

Anyways, if anyone gives it a try, do report here. :D
[Galaxy S III Original Android Development] xdawaldo:
Auto-Rotation

For me the same, works after reboot( not warm-reboot, only real-reboot).

---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------

a2dp to my car radio gets stuttered after a fiew minutes. Only rebooting helps for a fiew minutes. Anyone expierencing this too ? Any helping workarounds there ?

Have a nice day....
[Galaxy S III Original Android Development] arminbih:
16/32/64/128/192/256 best ever.
[Galaxy S III Original Android Development] sunny1234590:
People with auto rotation problem!

Guys, there must be some problem with the device itself. Ever since the first release of CM13.0 I have been using it and never faced it. I am talking about the Auto Rotation problem.
[Galaxy S III Original Android Development] xdawaldo:
I don't believe this, cause:

After every reboot it is working while i use phone. After a while of not using (sleeping) the autorotation stops.

The little camera symbol while trying to take a photo rotates further more

But believing is not knowing.....
[Galaxy S III Original Android Development] Hawaiihemd:
Please do a search and safe everybody's valuable time. This topic is all over this thread and Q&A.