yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] sanguinesaintly:
Wireless or graphics acceleration to blame for battery drain reported by some users ? Or both? Or neither? Maybe some stats based on completely clean systems would be useful. No GApps, no xposed , no apps. Just an idea. Troubleshooting starts with eliminating everything and loading one at a time over a sensible period of time to enable meaningful results. Sorry I can't do this because I've never had any issues with battery drain,but maybe someone out there who has these problems can step up.
[Galaxy S III Original Android Development] whoadood:
I don't have any wakelock problems at last, after they fixed wifi. But LMK is still a problem, and screen tearing and FPS drops are still a huge problem. And I have the feeling that GPU acceleration is not working correctly, the CPU governor is plain bad, or whatever. Take a look at this:

https://developer.android.com/tools/performance/profile-gpu-rendering/index.html

If any line goes over the green horizontal line, that's a FPS drop. I am attaching a (slightly severe, I admit) GPU profile. There is just no way to tap on something without getting a stuttering animation. To me, this hints to the GPU not working properly, and the CPU being clogged, unable to paint so many frames at once, and consuming lots of battery. Of course, this is all speculation.
[Galaxy S III Original Android Development] anil2941985:
no network, imei not showing...

After flashing cm 13 27 build, i am unable to get network. when sim is not inserted, IMEI no is seen correctly. But after inserting sim, IMEI no goes off. i have my efs backup made before flashing rom. how to restore it? i tried partition and backup app, terminal emulator, but not succeeded. any solution please?
[Galaxy S III Original Android Development] jacksp:
Tested it couple of days ago. Everything works as expected.
[Galaxy S III Original Android Development] arifnasirshaikh:
Use twrp to restore backup or you can use odin as well..
[Galaxy S III Original Android Development] anil2941985:
I made backup with efs backup app. now having four file. efs_backup.tar, efs_backup_tar.gz, radio_backup.tar, radio_backup.tar.gz

which one to use for odin?

i tried .tar file in ODIN PDA option. but got some preload error.

how to use twrp for this files?
[Galaxy S III Original Android Development] vkopzon:
On nightly 27. All is perfect! Thanks to devs!!!

A minor issue with BT (wasn't on 18). During music playback call picked up correctly, but on call termination BT connection is lost and immediately reconnected again with playback...
[Galaxy S III Original Android Development] arifnasirshaikh:
Okay.. Download that app again, see if it has restore option..
[Galaxy S III Original Android Development] sanguinesaintly:
Get a working system - stock with Odin if necessary.. Flash TWRP 3.0.0.0 - Backup EFS with it. Flash new ROM and restore EFS.
[Galaxy S III Original Android Development] sunny1234590:
[MENTION=5405215]forkbomb444[/MENTION] USB OTG seems to be broken. Please, see!
[Galaxy S III Original Android Development] foober:
On latest version in build root don't work. When flash latest beta supersu system don't boot.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] sunny1234590:
Deleted
[Galaxy S III Original Android Development] foober:
Which version supersu work on our cm13?

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] Sigi_cz:
You should set Root Access to Disabled (Wylaczony) when using SuperSU (beta 2.67)
[Galaxy S III Original Android Development] himmon:
Built in root access not working for me as well, also tried SuperSU 2.67 beta which bootloops now. Tried clean flash of today's build.

---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------

Noticed there's a newer 2.68 build of chainfires SuperSU, will give it a try now.

---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------

SuperSU 2.68 link BTW for anyone using chainfires instead of built in SuperSU http://xdaforums.com/showthread.php?t=1538053
[Galaxy S III Original Android Development] viktor92:
Worked for you latest SuperSu ?, because every time I try CM13 the only SuperSu that works for me is v2.65.
[Galaxy S III Original Android Development] himmon:
Unfortunately not, will try a clean flash again. If a no go, I'll wait for tomorrow's build as not a deal breaker.
[Galaxy S III Original Android Development] Misterxcs:
HI

in nightly 01.03 the device id got broken ! I cannot connect via ADB anymore. it does not find Samsung-GT-I9300

Would be nice if you can fix this issuse !!! Must switch back to nightly from 28.02
[Galaxy S III Original Android Development] matasa:
file manager

In nightly 01.03 the cm13 file manager doesn't start any more. Does anyone experience such a problem?
[Galaxy S III Original Android Development] NobodyNobody:
Hi,

before CM13 I used CM11.1 on my S3.

First: Great works, thanks man! I like CM13, but sadly I found some issues:

- Apps are opening faster, but it takes way longer to load the content of the app

- While this the CPU is loaded with 100%

- It crashes from time to time resulting in rebooting

- Webbrowsers are crashing often if you have more than 10 Tabs open

- DSP-Manager from CM11.1 is hardly missed! I installed Viper4Android, but I have some issues:

--> The sound with DSP-Manager was better

--> I cannot connect to my Car-Audio with Bluetooth. While the playback on earphones is smoothly, it is haltingly on my Car-Audio with bluetooth

--> When I update to a new nightly, Viper4Android isn't working anymore. I have to reeinstall SuperSU, reinstall Busybox, set SELinux to permissive again, reinstall the Audiodriver and sometimes even to reinstall Viper4Android.

- The SD-Card cannot be used by every App (i don't use this option where i can expand my internal memory) and cannot be acessed by computer over USB or Airdroid

- The Clock has blue background - black was nicer

- sometimes the phone says "no SIM-Card" and I have to reboot the device
[Galaxy S III Original Android Development] JohnSmit268:
You're right. It won't open. Anyway fix is simple. Use another file manager. Personally never loved cm file manager. There are better ones out there.

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

Most of these are not device related. You know, the dev only works on i9300.

And with this heavy load of customizations you made, you'd better not to report bugs. If you use pure cm 13 then return and report your bugs. And missed things are missing, this is the whole cm 13 development process. If they drop something, you have to get over with it, and SD problems is because of the apps not supporting marshmallow, try contacting the app's dev. For browser use a light one like CM Browser.
[Galaxy S III Original Android Development] whoadood:
Most of those problems are well known and we are waiting for a fix from the developer.
[Galaxy S III Original Android Development] daywalk3r666:
root access is broken.any workaround?
[Galaxy S III Original Android Development] NobodyNobody:
I made heavy load of customizations? Are you kidding me? Why i shouldn't report bugs which I've found? Most of them appeared before using the "heavy load customization" called Viper4Android.

And yes, even the CM Browser keeps crashing.

BTW: Swift-Keyboard isn't working as well

[MENTION=4893848]whoadood[/MENTION]: really? That gives me hope that it will be fixed soon
[Galaxy S III Original Android Development] Holla_Boy:
Please tell me how to make a transparent lock screen on the offical CM13? Any help
[Galaxy S III Original Android Development] whoadood:
Not really, I've been waiting for over two months. I guess it will be fixed eventually, but don't hold your hopes up, heh. I recommend you to go back to stock or CM11 in the meantime, because some things, like web browsing, are unbearable.
[Galaxy S III Original Android Development] Trafalgar Square:
Hey,

they wouldn't merge something, if they didn't test it. If they do it, we won't have nightlys because they would fail.

Root is working on other devices. And always remember: They can't test every device if it's working after a patch. Trust me: They know how to use Gerrit. They wouldn't comment with +1 or +2, if the patch is rubbish. And always remember, this is a Development Thread. Development means, this ROM will be tweaked from every version. You are not forced to install a new Nightly. You can wait for feedback here.

And now: Wait for new Nightly. And maybe it will be fixed. I can't find the commit, which could broke Root :eek:

Regards
[Galaxy S III Original Android Development] whoadood:
First, nightlies would fail if compilation failed. A logic error for example won't make compilation fail. As far as I know, there are no unit tests either, so...

And second, Chrome developers (Chrome is an example, it's just another big project which uses gerrit) also test the changes before they post them to gerrit. And that means nothing. There are always corner cases, etc. A thousand things can fail which aren't apparent when you look at them. That's the reason gerrit exists, because 10 eyes, for example, can see more things than 2.

I can't, either. Very weird.
[Galaxy S III Original Android Development] Trafalgar Square:
Hey,

And please remember this.
[Galaxy S III Original Android Development] Misterxcs:
[MENTION=5405215]forkbomb444[/MENTION]

Please consider to fix the device id. Since nightly 01.03. its broken and i cannot connect anymore via ADB because no compatible device was found

thanx in advance !!!
[Galaxy S III Original Android Development] strider184:
I'm on nightly 2016.02.27 and my experience with my bluetooth headset has increased exponentially. I haven't had to restart my phone to get rid of stuttering audio for two days. I would usually begin to get stuttering problems after connecting my headset around 3-4 times but I've been disconnecting and reconnecting my headset for these past two days and have experienced no issues. Was this the result of a fix or have I just been really freaking lucky these past two days? I'm almost scared to update to the newest nightly because I'm afraid something weird might happen (as it always does with me) and it'll go back to crappy bluetooth.
[Galaxy S III Original Android Development] marcemartinsj:
the network signal falls, coming and going, can not call or send sms, you can be? I need your help .. I clarify, imei okay ..

---------- Post added 2nd March 2016 at 12:05 AM ---------- Previous post was 1st March 2016 at 11:56 PM ----------

the network signal falls, coming and going, can not call or send sms, you can be? I need your help .. I clarify, imei okay ..
[Galaxy S III Original Android Development] whoadood:
I have never had those issues with this ROM, sorry.
[Galaxy S III Original Android Development] marcemartinsj:
which may be?
[Galaxy S III Original Android Development] tadydrift:
Try to wipe cache / dalvik cache / system and reinstall the zip.
[Galaxy S III Original Android Development] gauravlnx:
Bootloop(on Galaxy s3 logo) with March 1st nightly. Flashed back the 27feb nightly.
[Galaxy S III Original Android Development] tadydrift:
downloaded it but didn't install it yet, actually runing smooth on 28 feb nightly
[Galaxy S III Original Android Development] Hemilpatel3296:
Bootloop on latest update after flashing supersu.
[Galaxy S III Original Android Development] sunny1234590:
Just don't install the latest nightly build. Just wait for another build to come.

P.S: positng the same thing doesn't solve your issue. You gotta read the thread before you post something.
[Galaxy S III Original Android Development] disthomuc:
Nightly of 2nd of march internal root working again. Rom is smooth.
[Galaxy S III Original Android Development] himmon:
Chainfires SuperSU v2.68 working also.
[Galaxy S III Original Android Development] Pasindu88:
2nd March internal root doesn't work for me. But chainfire root is working perfectly :good::)

Edit: https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
[Galaxy S III Original Android Development] himmon:
Very fast scrolling and smooth transitions in this ROM, responsive app loading. Very good build so far, thanks to Dev.
[Galaxy S III Original Android Development] oclf:
calendar sync issue with outlook.com

maybe there's an issue with the calendar? i used the nightly 2016-03-01 but i noticed the issue with the nightlys bevore.

i added an outlook.com exchange account to the phone (push, and mails whole time). the account contains 4 calendar:

- main calendar for all my appointments

- subscribed google calendar (german soccer league)

- subscribed google calendar (premiere league)

- subscribed google calendar (primera division league)

(subscribed calendar from fussball-spielplan.de)

all calendar looks good in the online account of the outlook.com, the same at the workstation e-mail software.

at the first time i added the account to the S3 all works fine, but after a while it shows me only 1 of the 4 calendar from this account.

after i removed the account and set it up from scratch all looks good again, but after a while (half an day / one day) there is the issue again.

can anyone confirm this? is there something to solve this issue?
[Galaxy S III Original Android Development] lkkeyan89:
How to stop cell broadcast message in this rom
[Galaxy S III Original Android Development] himmon:
TWRP 3.0.0.2 released and working too with this ROM, they've fix the build number being displayed correctly as well as other fixes.

https://dl.twrp.me/i9300/
[Galaxy S III Original Android Development] guhvanoh:
How to search the thread or ask in Q&A thread?
[Galaxy S III Original Android Development] yoahmad1995:
YouTube issue still present in latest nightly. :(
[Galaxy S III Original Android Development] Lucifer III:
Anyone?

Can anyone confirm that yodays nightly fixed root?!?!
[Galaxy S III Original Android Development] guhvanoh:
If we knew what yodays is maybe. Having said that, it is your job to download and test. It is also your job to read the last few pages of this thread to see if answers to your question are posted. I suggest you do that.
[Galaxy S III Original Android Development] foober:
Again root don't work. :(

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] Lucifer III:
Do we have the same problem ?when start youtbe it says that there is no connnection

And when i try to sing out and sing in again it wont show my account..
[Galaxy S III Original Android Development] forkbomb444:
Hi there! I'd like to direct you to these all-new entries in the FAQ:

Again take a look at the FAQ :)
[Galaxy S III Original Android Development] Lucifer III:
Yeah but some say it works and some say i doesnt...i don't want to wate my time at downloadig a broken nightly
[Galaxy S III Original Android Development] pesci2k:
For me root works.
[Galaxy S III Original Android Development] sanguinesaintly:
Maybe so, but this is a development thread, and it would be useful if you took the time to try it and report any bugs. That's not wasting your time, that's helping the community.
[Galaxy S III Original Android Development] Sigi_cz:
is it me, or search in settings doesn't work as expected? I know I could search "usb" before, and now it shows no results. It worked on 20160104 for sure, then I updated to 20160228 an I "think" it worked too, but while trying to find something yesterday, I had no luck. I'll try reinstall later, just to test it ...

logcat: do I need to be connected to PC via ADB to be able to see logcat?? on CM11 i had Logcat Extreme installed on phone, and I could see everything on it. Now it shows nothing ...
[Galaxy S III Original Android Development] Hawaiihemd:
If getting a logcat via adb is too much hassle for someone I can recommend Andy Log App. Really convenient and simple to use.
[Galaxy S III Original Android Development] Sigi_cz:
doesn't work, saved log is empty. I tried also Logcat Extreme (which I used on CM11), aLogcat and Cat Log, none of them works. The log is always empty.

I'd like to provide logs for problems I'm reporting, but I can't sit by my computer all the time ...
[Galaxy S III Original Android Development] forkbomb444:
If you install a terminal (this one works nicely) and type this:

su

then, accept the superuser prompt, and type

logcat -d > /sdcard/logcat.txt

it should save a logcat at /sdcard/logcat.txt.
[Galaxy S III Original Android Development] Sigi_cz:
Yes, I do. 0B big empty file.

I did full erase of my device before installing 20160228, and I don't plan to do it again, but I'm just unable to get logcat working. (it didn't work for me on 20160104, which I used before, too)

---------- Post added at 11:58 AM ---------- Previous post was at 11:52 AM ----------

ADD logcat:

it works in all programs if I set SElinux to permissive (terminal "su" and then "setenforce 0")

I'm also using BETA-SuperSU-v2.67

EDIT2: SuperSU seems to be the culprit. After system reflash without SuperSU and activating built-in superuser, I can see logcat right away.
[Galaxy S III Original Android Development] yoahmad1995:
[MENTION=5405215]forkbomb444[/MENTION] I totally understand and I apprentice all your work to our beloved S3 but first I have already attached a logcat in previous posts. Secondly, YouTube had no issues in first nightly builds. I thought my device was the issue but I borrowed my brother's device which he don't use and found the same problem with YouTube. Thanks so much again. :)

---------- Post added at 01:56 PM ---------- Previous post was at 01:50 PM ----------

The problem I have in YouTube (on both s3) is it works for a video or two and after that it shows a there's a problem wihle playing error. I have to close/reopen the app to fix or it never gets fixed until I reboot. And sometimes it never works unless I hard reboot the device or sometimes the error pops while a video is being played.

PS: I have quality set to auto since my connection is bad but never had such problems on stock, cm11, cm12 or old builds of cm13.
[Galaxy S III Original Android Development] anil2941985:
It didnt worked.. i flashed back stock rom, now imei no is showing correct, but getting error: not registered on network..

ny solution?

---------- Post added at 02:38 PM ---------- Previous post was at 02:28 PM ----------

Did this too... now IMEI no showing corrent one.. but getting error as not registered on network.

When i flash cm13, withoout sim, get correct imei no, but when insert sim, no imei no...

plz help,.. what to do now?
[Galaxy S III Original Android Development] whoadood:
http://review.cyanogenmod.org/#/c/134705/

Thanks [MENTION=5405215]forkbomb444[/MENTION], I'm your sex slave now.
[Galaxy S III Original Android Development] irot3k:
Edit: got the first prob solved. Now i got anotherone. Is it possible that the new cm doesnt recognize the romanian vodafone sim? I do use it via roaming, im just curious.
[Galaxy S III Original Android Development] himmon:
Damn, this is like the Muppet show, people whining about root access, read a few pages back, there's a new chainfire SuperSU 2.68, twrp 3.0.0-2 etc. I have tested a clean fresh build of todays cm13 build and the built in root access in developers mode and chainfires SuperSU 100% work.

FYI, I have also tested upgrade from yesterdays build and both root methods work.

If you're still having issues, reflash or complete a clean build.
[Galaxy S III Original Android Development] sunny1234590:
This is the second time when this is happening!

It didn't work that good at that time I guess. So, the commit was reverted back.
[Galaxy S III Original Android Development] Scorpionea:
After some time on 4.4.4 it's time to be back on cm13

Full clean wipe including internal storage and so far everything good,including battery :D

Don't have any issues with root but will check YouTube as some of u reported not working after few videos..
[Galaxy S III Original Android Development] Perooo1:
I'd imagine you flashed from stock 4.1.2 ROM, right? You actually had to flash stock 4.3 first because it upgrades to new v2.0 efs file folders or something along those lines, I don't quite remember atm. I had the same issue two years ago when upgrading from stock 4.1.2 to 4.3. IMEI was correct but I was getting that "not registered on network" when trying to check my sim status, make call or send a message. I'm sorry to say, but I've been trying to fix it for a few weeks and absolutely nothing worked for me, I had to send it for a repair. I think they had to get me new IMEI or something. Granted, that was 2 yrs ago and some things may have changed, I doubt they did, but that's my experience with this issue. I wish you best of luck working this one out! :)
[Galaxy S III Original Android Development] whoadood:
Yes, so I guess it's the ultimate fix™ now.
[Galaxy S III Original Android Development] mloc33:
I can't remember, which do I select when flashing the IMG, boot or recovery?

Sometimes, for no reason, the very top part of the screen, either in landscape or portrait, I can't select anything, I see the buttons, but there not pressable, a restart solves this temporarily. Anyone else experience this?
[Galaxy S III Original Android Development] himmon:
Recovery, then select the new image and flash, good luck
[Galaxy S III Original Android Development] Andi17:
Use the app flashify from playstore to Update the recovery
[Galaxy S III Original Android Development] whoadood:
Can you use F2FS for /system ? When I install the zip, it reverts the /system partition to ext4. Is that a bug, or is it intended?
[Galaxy S III Original Android Development] sunny1234590:
No, filesystem cannot be changed for system partition. No matter what you make it, it will become EXT4 only as soon as you flash a ROM.
[Galaxy S III Original Android Development] Michael1986:
Hi, two things i noticed:

- cardboard APP: "eyes" are too far apart... Dont know what could be the reason. Maybe other dpi than stock?

- Bluetooth audio works OK for me, but Volumen doesnt change when i try vol+/-. Audiofx takes effect, though
[Galaxy S III Original Android Development] JohnSmit268:
You're right. I thought you're using boeffla kernel. Sorry for misunderstanding. And yes, if you don't use greenify to free up your RAM, Maybe (not in my case even without greenify) you will receive crashes. I can open 15 tabs in CM browser without any problems, only some slowdowns. But chrome will hang and force close of course.

---------- Post added at 09:26 PM ---------- Previous post was at 09:18 PM ----------

I couldn't change my filesystem to f2fs with this build. Anybody can confirm that?
[Galaxy S III Original Android Development] Cr453r:
Cardboard works on 240 DPI. With higher i had problems.

In 3.0.0.0-2 I could not do anything. It did not read inernal storage for me. It showed that internal storage partition was 0mb. Flashed back 3.0.0.0 and everything works
[Galaxy S III Original Android Development] Sma5hley:
F2FS has been removed from TWRP 3.0.0-2 apparently it had issues. If you want F2FS stick with 3.0.0-0.

http://xdaforums.com/showthread.php?p=65596110
[Galaxy S III Original Android Development] DualJoe:
Where is init.d? How is it meant to fire up scripts here?
[Galaxy S III Original Android Development] Peixoto21:
any fix for snapchat/messenger video?
[Galaxy S III Original Android Development] JohnSmit268:
Take a look at the first and second post of the thread. This is a known issue and the dev is hopefully working on it. If it is fixed. It will be removed from the known issue list and the fix will be merged and delivered to you.
[Galaxy S III Original Android Development] Piero Jose:
I need rom 6.0.1 for galaxy s5 exynos please
[Galaxy S III Original Android Development] badesh:
the music player doesn't sort by id3 tag but by filename... is this meant to be so?
[Galaxy S III Original Android Development] viktor92:
We all need something, but you are in a GALAXY S3 thread...
[Galaxy S III Original Android Development] miketabs:
Re-Flashing build 20160228 and still root access is missing. any advice?