yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] iamNumberThree:
Hi,

in my opinion/ according to my knowledge, Cyanogen-Mod ROMs can be compared to the operating system (OS) on your home PC. The operating system (on your PC and same way on the phone) are being flashed onto the "normal" SD-memory of your phone just like a hard drive of your PC- this kind of memory is not likely to fail due to flashing. CyanogenMOD ROMs ARE NOT flashing the firmware of the (hardware) phone components - only those have limited flashing cycles.
[Galaxy S III Original Android Development] viktor92:
I will wait for the first final CM13 version to try it again.

I can strongly recommend the setup of my signature.
[Galaxy S III Original Android Development] whoadood:
You are completely wrong in everything you have said.

* Desktop computers use hard disk drives that also have a limited number of reads and writes. Especially if they are SSDs, which have a technology comparable to the internal memory of a phone or a SD card. But mechanical drives can and will fail too with time.

* A SD card is built using the same technology as the internal memory of your phone, so yes, it can be read/written only a limited amount of times, although it's not really that important since SD cards are cheap and easily replaceable.

* CM is written to the same part of your phone the stock ROM is written: the system partition of internal memory.
[Galaxy S III Original Android Development] jerome0828:
thanks

I am currently running stable cm12.1 on my i9300, and it says that its ota updater was fixed,

im gonna try to use it, but do i need to download gapps 6.0.x?

and should i flash it manually or better to use ota updater? thank you so much

---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------

im currently running stable cm12.1 on my i9300, and it says that its ota updater was fixed,

im gonna try to use it, but do i need to download gapps 6.0.x?

and should i flash it manually or better to use ota updater? thank you so much :)
[Galaxy S III Original Android Development] maciocho:
+1
[Galaxy S III Original Android Development] iamNumberThree:
If you want to push the read/write discussion to the edge (which I didn't :)), you're right.

But it is more likely for a hard-drive to fail due to mechanical issues but due to running out of read/write cycles...

Same with the SD-Memory Technology --> How many-100-thousands of read/write cycles would you have to go through and how many times would you have to flash a ROM before the SD Card/Memory wears out?

Point I was trying to make is that CM isn't flashing any part of the phone/memory which wears out as EASILY as some of the (firmware) components would do.

So I guess, we actually meant the same thing...
[Galaxy S III Original Android Development] shalushahil:
problem with xposed on 19/04 nightly..after applying any xposed module phone goes to bootloop..
[Galaxy S III Original Android Development] rhyzan:
Report that to xposed thread please.
[Galaxy S III Original Android Development] Maxoobidou:
Been running 0417 with no issue for 3-4 days.

I did a clean flash, and use my phone heavily.
[Galaxy S III Original Android Development] tadydrift:
Build 19 is fine for me Smooth performance, testing 20042016 on my test device S3
[Galaxy S III Original Android Development] NiQ1:
Well that was my initial wish but there's absolutely no way of knowing when that will happen or even if it will ever happen. I would say that it actually kind of bugs me that these days there's nothing "in between" nightlies and stable releases (that is a general thing, not specifically regarding i9300) and I hope it'll change sometime in the future.

Anyway keeping an old version is no longer an option - The last update to a stable release of CM for i9300 is CM11 from January and the last update to the unofficial CM12.1 is even earlier (November). Multiple security vulnerabilities have been reported since then and you have the choice between the risk of flashing a nightly or the risk of getting pwned. As time progresses and no snapshots arrive I believe the second risk becomes greater than the first.

Thanks! Will try one of these.

Will still appreciate any more reports.
[Galaxy S III Original Android Development] tadydrift:
will make a review of 20/04/2016 on my S3 today once i get home ;)
[Galaxy S III Original Android Development] sunny1234590:
Lockscreen bug still persists?

---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------

Lock screen bug still exists?
[Galaxy S III Original Android Development] prabhu_mohan:
Downloading and Installing 20/04/2016 version now....

Got MD5 Verification failed error... whats this about?
[Galaxy S III Original Android Development] tadydrift:
We can say that bug is not 100% fixed but 99%
[Galaxy S III Original Android Development] Zenzfum000:
Have u downloaded the build with cmdownloader? If yes ignore the error, this app sometimes gave me this error. Anyway, download it from the cm site and dirty flash maually
[Galaxy S III Original Android Development] zayam5:
Bhai is software ks kya faida he?
[Galaxy S III Original Android Development] prabhu_mohan:
Yes. From about phone section and CM update.

I'll flash manually, without wiping the data. So I won't lose anything.

Thank you. Will keep updated here [emoji4]
[Galaxy S III Original Android Development] maciocho:
Yes, it's the same as 0419 nightly.
[Galaxy S III Original Android Development] Bilal54:
s3 cm13 nightly main bugs and problems

"cant connect to camera":crying::crying:

root does not work:crying::crying:

touch stuck on its own:crying::crying:

bootloops :crying::crying:

also gapps dont install
[Galaxy S III Original Android Development] cobras3:
Do you have S3 I9300? Continue in the Q&A Thread.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Zenzfum000:
From where you installed the gapps? is impossible that they don't work
[Galaxy S III Original Android Development] shalushahil:
does the rom bug fixes will include in delta update??
[Galaxy S III Original Android Development] g104:
try download Mediaserver killer
[Galaxy S III Original Android Development] repunk:
İ can't restore chat backup on whatsapp. And, the app is waiting on chat restore screen, so the app can't be used.
[Galaxy S III Original Android Development] shalushahil:
no problems here..iam on 19/4 nightly
[Galaxy S III Original Android Development] whoadood:
Hold the Home button, swipe WhatsApp away (so it's closed), then open it again.
[Galaxy S III Original Android Development] prabhu_mohan:
I'm not getting Facebook notification. April 19 build. Any work around this or it's known issue? Thank you!
[Galaxy S III Original Android Development] Logan:
Same here delay in notifications
[Galaxy S III Original Android Development] repunk:
Thank you. Solved. Your advise works.
[Galaxy S III Original Android Development] yoahmad1995:
I'm on 19/4 xposed works just fine.
[Galaxy S III Original Android Development] galen2:
No one cares on this development thread about facebook notifications, whatsapp restore or xposed problems, go to Q&A thread and stop that type of questions here please.
[Galaxy S III Original Android Development] Bilal54:
hello

yes i have i9300 and i cant root it
[Galaxy S III Original Android Development] tadydrift:
Fast and quick review of what's new in and bugs in nighlty 20/04/2016[YOUTUBE]9zRY3RmUUaA[/YOUTUBE]
[Galaxy S III Original Android Development] patmes:
I have on my internal storage 2 times 0 dir under storage

storage/0/0 and

storage/0/0

within the 0 dir both the same structure.

What are the dir 0
[Galaxy S III Original Android Development] maciocho:
Lockscreen bug is gone from first to every touch on the 0421 nightly :(
[Galaxy S III Original Android Development] sunny1234590:
Isn't this a good thing?
[Galaxy S III Original Android Development] Zenzfum000:
Why this sad face? Do u love bugs?
[Galaxy S III Original Android Development] maciocho:
No when you read it with understanding :) - it's present at every touch, so it's worst and can't really be a good thing ;)

---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------

To make it clear - lockscreen bug is still present and is gone worst as it can be seen at every screen touch.

Thanks,

M
[Galaxy S III Original Android Development] arifnasirshaikh:
Yes can confirm
[Galaxy S III Original Android Development] azazello22:
Dirty flashed 21/04 on 30/03 and no problems so far. Lockscreen works as it should.
[Galaxy S III Original Android Development] maciocho:
Tap the screen for assistance and please report back. Thanks
[Galaxy S III Original Android Development] azazello22:
Do you mean the little graphic glitch on the top? Lockscreen icons appear and disappear in less than 1 sec, not a big deal. It's hardly noticeable.
[Galaxy S III Original Android Development] dtb95:
Does this rom will ever have a snapshot version?
[Galaxy S III Original Android Development] sarath870:
Can't connect to camera error

I have just flashed cm13.When I tried to open camera,it is displaying an error.

Camera error : 'Can't connect to camera'.

Is this a known issue?? Anyone faced this error ?? Any solution for this??
[Galaxy S III Original Android Development] prabhu_mohan:
Are you trying to opening from lock screen? If yes then its already existing bug. Restart the phone and open the app regularly from drawer or main screen.

Even I faced same issue.
[Galaxy S III Original Android Development] sarath870:
Thanks. It is working now.
[Galaxy S III Original Android Development] joeyjoey022:
Just install the Camera Fix apk, it reboots the camera module so you don't have to hardware reboot everytime it happens. [emoji106]
[Galaxy S III Original Android Development] jam1445:
Hey Guys!

I need help.

I Clean installed 21th April build on my i9300. Everything works fine. But while using the phone, the display goes black while sensor and menu buttons are working fine. Then after a minute, display comes back.

It continuous to happen since then.

Any Suggestions!
[Galaxy S III Original Android Development] lukaaa477:
my alarm didnt ring this morning? anyone else same problem?

also has black screen on call been fixed on latest nightly?
[Galaxy S III Original Android Development] broken-arrow:
Yes, it happen to me to, I use Mars build.

I guess software crash, when a app don't respond.

A bug for my is even phonecall not work properly, some time I call or receive call the mic stop working (reboot or call back work).
[Galaxy S III Original Android Development] adeldani:
Internal alarm or 3rd party alarm app? It seems Marshmallow has some problems with 3rd party alarm apps.

Had the same problem about a month ago with "Alarmdroid" and switched to the internal alarm due to that reason. Now it works fine for me.
[Galaxy S III Original Android Development] mafia43:
Would a snapshot be available at any point in time? As i see, there are lots of problems with our phone whereas lots of phones have their second or third snapshot even nexus4.

Thank you for your hard work dev, still i believe it is not enough for daily use
[Galaxy S III Original Android Development] adeldani:
I use the 31.3 nightly as a daily driver, hardly any bugs and really smooth, I don't understand what should be "not enough" since it's one of the most stable roms i ever used. So I see no need for a snapshot and I think continuosly asking for it (not only your question but asked by many people here in the dev-thread) won't make anything better.

Flash a stable nightly (for example 31.3) and just be happy with it ;)
[Galaxy S III Original Android Development] broken-arrow:
I use 31.3 and it not stable for my, buggs and random reboots. This mobile and ROM not work wit my (not any I try, this is the closest I get). Webbrowsing is a nightmare, get kvick slow and can reboot or if I make a call/receive a call. Yeah I have many apps (10 att least), but it should not get slow so fast (I reboot at least 2/3 daily).

Yes clean install.
[Galaxy S III Original Android Development] Apmauj:
http://xdaforums.com/showpost.php?p=66169218&postcount=4857

Do you have MediaServer Killer installed..?
[Galaxy S III Original Android Development] vinibgomes:
Thanks for the tip!

Where can I find this apk?
[Galaxy S III Original Android Development] maciocho:
Lockscreen bug still present on 0422. Does anyone know if this is even planned to be fixed? Maybe it's present on all of the cm13 devices? If so I probably better stop reporting... ;)

Thanks
[Galaxy S III Original Android Development] wo88les:
Just dirty flashed 0422 and lockscreen seems fine here

Also slight performance increase
[Galaxy S III Original Android Development] lukaaa477:
i had mediaserver killer but says my device not rooted and nevers opens, so i uninstal it long time ago, and yes i use 3rd part app for alarm, timely ... so no mediaserver, what else?
[Galaxy S III Original Android Development] joeyjoey022:
?google it?
[Galaxy S III Original Android Development] davydm:
Unable to dirty flash?

Hi all

I'd appreciate any assistance with this -- googling hasn't gotten me anywhere )':

I've been using the CM13 nightlies on my i9300 since the very first day I heard about official support coming back for my old handset (thanks, everyone involved -- I really appreciate it).

My only issue (apart from breakages now and then -- but I expect that on a nightly channel, so no complaints) is that I can't seem to be able to dirty-flash, meaning I can't just update CM: I have to do a full wipe whenever I go for an update. If I don't, the install script seems to hang on the line:

detected filesystem ext4 for /dev/block/mmcblk0p9

And never progress past there. If I come back into recovery and wipe system, data, cache and dalvik/art cache, I can do an install just fine. The problem is that doing so means that, unlike when I chased the nightlies on cm11 and I could actually install the nightlies every day because install time was around 15 minutes total (including the reboot and re-optimisation), I now spend around 1.5 to 2 hours on an update, since I have to back up with TB, reboot-recovery, nandroid backup (in case I get something totally wrong after the wipe), install cm + gapps (from opengapps), reboot and restore all with TB -- and then re-tweak all system settings as I've found that TB's system data restore can cause oddnesses in behaviour on the system.

So I'm assuming I'm doing something wrong here, since I read that others are able to dirty-flash. Any pointers / assistance appreciated. I'd love to be back on updating daily with last nights build, as I was with cm11. I'm a bit of an update whore :/

---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------

O yeah, forgot to mention: I had this issue on TWRP 2.8.6.0; updating to 3.0.0 didn't help.
[Galaxy S III Original Android Development] rchtk:
No major bugs here. Any confirmed bug should be reported in cyanogen jira. In this thread it's just a waste of time.

If you're not happy with a nightly then take a CM12 snapshot.
[Galaxy S III Original Android Development] S /\ E E D:
:/

The bug exists on swipe mode ...
[Galaxy S III Original Android Development] mark1003:
I'am using twrp 2.8.7.0 with no issues. Maybe you should try this version.

A newer version is twrp 3.0.2-1. But until now i did not have a reason to try this.
[Galaxy S III Original Android Development] Borkse:
CM12 snapshot for the S3? Did I miss something? Please show me the link to this ominous snapshot.
[Galaxy S III Original Android Development] rchtk:
Yeah whatever. Cm11.

My point remains that the constant noise here is useless, there's a bug tracker for confirmed bugs.
[Galaxy S III Original Android Development] Llun:
Does anyone have problems playing Youtube videos? Since 20160418 Nightly i can´t play videos on Youtube because they are slooooow...
[Galaxy S III Original Android Development] yoahmad1995:
Clean flashed 2304 and notifications are broken.
[Galaxy S III Original Android Development] H4RTI3:
Yeah can confirm. And also GIFs on twitter show weird green lines and playing videos in e.g. the Google Photos app results in the whole app to lag (only sound but no vid).
[Galaxy S III Original Android Development] ajayshah95:
I just installed this and am experiencing a bug - notifications do not show and I cannot pull down the notification bar. The first pulldown works (to see time, date and status bar icons) but the second pulldown does not. Any ideas?
[Galaxy S III Original Android Development] Borkse:
Youtube videos work fine for me with the latest nightly. However, I access them via the browser app maybe it is only YouTube app related?
[Galaxy S III Original Android Development] lil11b:
Well I had that problem too, including airplane mode not showing up when holding the power button. What i did was wiping system and dalvik cache and cache and flashing cm + opengapps again. That solved my problem. Unfortunately Google Play services (com.google.android.gms) keeps crashing.

Btw I still have wpa supplicant problems, maybe someone investigate that issue ?
[Galaxy S III Original Android Development] Drollach Gûntar:
Cmxlog changelog site doesn't work.
[Galaxy S III Original Android Development] JohnSmit268:
Play store for sure!!
[Galaxy S III Original Android Development] sanguinesaintly:
It happens, but nothing to do with development. Just keep checking.
[Galaxy S III Original Android Development] joeyjoey022:
Can someone please point in the way of the general faq forum?
[Galaxy S III Original Android Development] aykuut:
Videos aren't playing correctly.. Just sound and the video freeze and my phone lags :(
[Galaxy S III Original Android Development] lukaaa477:
is there someone that is developing for this phone? if not lock this thread and R.I.P samsung s3 ..it seems noone is here, every new version = more bugs = phone unusable
[Galaxy S III Original Android Development] mkdr:
Same here, though it mostly also leads to kernel crash and you need to force reboot, otherwise phone becomes unusable slow/ frozen, and no carrier signal after a kernel-reboot.
[Galaxy S III Original Android Development] JohnSmit268:
You'd better check cyanogenmod gerrit before complaining about development. See the last commit's date:

https://review.cyanogenmod.org/#/q/owner:"Simon+Shields"

You know, most of the bugs are cyanogenmod general bugs and not something that our dev needs to fix. S3's dev will only fix device related bugs, not general ones. And if you're unhappy with bugs, that's OK. As you see there are stable snapshots on cm's site that provides a bugless experience. You can use them instead of nightlies. Have a nice day.
[Galaxy S III Original Android Development] sunny1234590:
You need to understand that every developer has their own private life. They work for us in there free time. If a developer is not online from many days on XDA doesn't necessarily mean that he is no more supporting our device.

Jumping to such conclusions are really a funny thing to do.
[Galaxy S III Original Android Development] JohnSmit268:
Which nightly version? You get freezes with SW or HW or HW+ decoder? If possible provide a logcat and provide more details. I myself use 20 April nightly and can play videos perfectly with SW decoder on MX Player app.
[Galaxy S III Original Android Development] aykuut:
Latest Version (23 April). I use the stock Video player.
[Galaxy S III Original Android Development] JohnSmit268:
Try MX Player with SW decoder if you received those freezes again provide logcats so the dev can take a look at your problem.
[Galaxy S III Original Android Development] sanguinesaintly:
You once said

"Your (sic) a senior member so should know, its disrespectful to the Dev to post a link to another rom in his thread"

Well, as a Senior Member, you ought to know how to be constructive, respectful and realistic.

Sorry for OT
[Galaxy S III Original Android Development] aykuut:
Thanks, it works now without problems.:)
[Galaxy S III Original Android Development] rhyzan:
I'm gonna rant for a bit. This is completely out the topic here but really relevant...

Anyone who has problems in the nightly read this post.

If something broke that works in the last nightly, Please reproduce the issue you're having and make a logcat. Then go to the bug tracker. Link in the first post. Type down what is asked, upload the logcat... Also indicate the time when you reproduced it.

If you're not sure what to do in the bug tracker site, just post your exact pertinent issue here, steps to reproduce the error and upload the logcat. Especially if you found a new bug, this is sorely needed.

If you know how to fix it, push it to the gerrit (not sure if I'm right here...)

If the dev replies to you and asks for more info, give them what they want. If they have any workarounds, nice.

If you found the bug and you're too lazy to do it, either stay and wait for the next one, switch back to the previous nightly or go to another ROM.

Now, any problems in CM13 (or any other nightly) WILL be fixed if one properly reports any bugs in the nightly. You can't expect the devs to "magically" fix the problem if you only say "X doesn't work please fix it." Or "X bug still exists why don't the devs fix it" without any proper documentation like logcats and screenshots. Come on lads! Read up! Do some research, be active in testing out and reporting bugs! This is CM13 nightlies! You test out this ROM because we as testers are tasked to find bugs and inconsistencies and the devs will do the rest.

And we also have a separate Q&A thread where any non-dev questions are entertained.... Just a heads up or whatever.

Damn, I wish we have a janitor in here. That's it

[/RANT]

---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------

And then we have this guy.

Oh god... "Senior member"... Please... No... Don't wanna swear...

Dude, you've been here longer than I am. YOU SHOULD KNOW BETTER.
[Galaxy S III Original Android Development] izopi4a:
damn updating to 23 nighty broke my phone ( bootloop ) using CM updater itself :((
[Galaxy S III Original Android Development] galen2:
SW decoder is crap, it waste a lot of battery to decode a video. HW+ is optimal but this rom have a broken hardware composer and dont work. Our dev said someday he will fix it, until that im on 12.1.
[Galaxy S III Original Android Development] tadydrift:
I think that nightly 21 is the best for now
[Galaxy S III Original Android Development] joeyjoey022:
Link to QnA thread please
[Galaxy S III Original Android Development] Maxoobidou:
Are you kidding ? It's in the first post mate.
[Galaxy S III Original Android Development] JohnSmit268:
You can use other cm13 Roms like nameless. They have a fully working HW composer.
[Galaxy S III Original Android Development] miketabs:
Dirty flash on latest build. Youtube crashing even on fb.
[Galaxy S III Original Android Development] Sma5hley:
Have you tried clearing data and cache for YouTube? And checking all permissions are granted?

If yes, please try to reproduce and create a log. May have something to do with the new open source bits just merged. I'm sure logs would help in finding the culprit.

See first couple of posts for details..
[Galaxy S III Original Android Development] torro32:
Hey guys I am listening my S3 through a 60 ohms Superlux hd668b headphones and I can say this thing delivers some serious hi-res hi-fi audio. Quality is definitely there but volume is on the quite side.

Now it's on a kitkat, my question is if i flash cm13 will it alter the sound in any way? What android version it has is not important to me, as long as it's not buggy since I will mainly listen music on this phone.

I see some ppl are mentioning voodoo audio app, if I install it I should gain on volume but will will I lose on the headphone quality. Because than I would rather buy some hp with higher sensitivity and less resistance.
[Galaxy S III Original Android Development] viktor92:
I have very good audio quality with boeffla kernel, but if your main interest is audio quality maybe you should stay with a TW (samsung) rom. QS KK 4.4.2 rom with Boeffla it's a real good combo.