yashsingh1/xdaforums huggingface dataset:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] daedric:
Your points-of-view on this matter, succinctly resume the mess of ideas that linger in my head. Every since CM pushed a bunch of devs, running nightlies into "stable" (back in CM10.2), i started seeing them with different eyes.

To make matters worse, suddenly i was finding bugs in the official nightlies that didn't exist in unofficial nightlies. Then came the whole cyaninc fiasco and if already had 1 step back and took another two.

My point is, due to the massive size of official CM devices, and the extremely heterogeneous eco system of devices (even inside the same OEM), it becomes very difficult to release a stable. To make matters worse, it can take weeks for a fix to be incorporated, i had ART stable on the unofficial for the DesireHD, and crashing on the N7000 (didn't had the i9305 back then) fro 2/3 weeks. I saw the commit that fixed it, it was just waiting aproving (ART is just a example, other remained). When the N7000 passed from unofficial to official, it brought old bugs back, just by sync'ing.

As it stands, i found myself flashing AOSP roms, based on CM even, but running away from official CM, and weirdly, they're more stable. (probably placebo here :P)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] h8Aramex:
New build (was latest today IIRC) kills root. Just a heads up.

And Play Store. (if you go into All Apps, it will just throw an error. tried every google hit, nothing helped.)

the 08 nightly worked fine, but I had to take a pic of some papers today.

after 2-3 pics the camera froze like always, so I got mad and updated.

end of story.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] kroonys3:
Root and play store are fine for me on latest nightly.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] h8Aramex:
Weird. Sorry for the false alarm then. Been using the system without full wipe since... the data fix.

Guess I will just skip updates for now, as I will need the phone 100% functional.

How do you guys even do a full wipe? I mean...re-installing / setting everything up seems kinda ... boring. All the time, too...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] cheffy11:
Doesn't take that long with titanium backup ;)

But I can't find myself on a particular ROM for more than a week I'm a flashaholic!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] menvert:
+1 to that. My process is - Backup in recovery(for if everything goes horribly wrong)

Backup all (or select just what you want; to save space)using TiB to sd card.

Perform factory/reset

Reboot into recovery, Install ROM, Install PAGapps (sometime you have to reboot between these 2)

Boot, perform 1st time setup

Open google play, wait for all apps to re-download (sometimes it kinda hangs, and use task manager to kill, go back into play store\My apps to continue) - This assumes you always agree to allow play store to backup apps

Then use TiB to restore only the DATA part of the apps, and the bare minumum of DATA for system apps (such as data usuage, WiFi associations), I also restore application widgets/launcher data, which seems to work mostly.

Set most system settings manually (restoring system data may produce problems)

Oh and sms backup and restore is also great for your SMS's
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] h8Aramex:
Thanks for the answers. I will try to do a clean reinstall once I get the time. ( I consider myself lucky that blindly flashing nightlies did not kill the phone yet. Not that I would mind, would be the best day of my life. :D I have so much anger built up against this soap bar, I could crush it with my bare hands. ;_; )
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] cheffy11:
I just use Tib to restore apps, I never have anything sensitive saved on the phone so can do a new rom setup to my usual configuration cos I save my layout on nova launcher as well in about an hour so not too bad ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
My sound recorder keep hang and fc when i try to record wav file.. Anyone here facing this problem? Any solution? I really need this sound recorder for my project.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] earth08:
With latest nightly 20140522 I am having camera fc

Whenever I open camera app it fc.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Smedslund:
20140522 made my powerbutton go crazy and my screen was not shutting down. Reverted to 20140521.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
Can someone please explain why the i9305 doesn't get any M builds? Is it because of some bugs? If so, which bugs? It's probably explained somewhere in this thread but I couldn't find it.

And to all who contributed to cm11 on the i9305.... Thank you! I love it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] cheffy11:
Read the thread mate
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
I did. It's very long but I read the last twenty pages of posts and tried searching and still don't understand
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Sepp-Wurzel:
as far as I understood there are no special m releases. A dev sets a nightly release AS monthly and thats it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
That's what someone said here, but it's not true. M builds are the new stable builds. They branche off from the nighties and are tested and made stable over the course of a week. Straight from the CM blog: http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items.

I did a lot of searching before posting my question. So why do almost all cm11 phones get M builds, but not the i9305?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] menvert:
Quite likely because there is no official KitKat rom for the model so any CM11 build has to do it's own driver integration + whatever else is missing. It also probably has to do with the low number of owners and the time that dev's who own an i9305 have to devote to it.

The turn around for our 1 Dev in coordination with the CM 11 team for fixes to the nightly seems to be very long, no way 1 week would be enough to make an M snapshot given the turnaround I have seen. And then someone else in the CM 11 team seems to then remove the fix before we can then move to the next bug...

I also think our Dev has other commitments right now IRL too; so I wouldn't be surprised if 19305 development support ended entirely.

And as per the previous discussion on this, there really isn't such a thing as a stable version so far for the i9305 there are several significant bugs remaining...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
Thank you very much for the explanation. It's easy to see why supporting a less common exynos based device is harder. So kudos to the dev(s) involved, because as far as I can tell all divers are working and even the nightly releases are imho stable enough for daily use.

Is there an overview of the remaining bugs? I saw something about an unofficial bug tracker, is that still up to date? I'd very much like to see if I can contribute.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] menvert:
I don't really run this ROM any more (using OMNI which is CM 11 based) but I believe these are the main ones;

Data Connection dies if it goes idle (Unsure on status)

Using Home button to wake phone also activates the Recent Apps list

Audio Stuttering when Screen off/sleep mode (Bluetooth part is resolved I believe, still has a few an hour)

Camera stops responding, have to restart to get it working again (Unsure on status, some people seem to still have it come back)

No Internet After receiving MMS (still outstanding)

I haven't seen the Dev (mcampbellsmith) here or on OMNI thread for some time, so I am not sure if he's still active or what you can do, unless you are a Dev and can submit code changes...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] woodman:
Did you read my posts on OMNI thread about "no mobile internet after MMS" for all AOSP ROMS ?

If you are interested, here you are :

#1050 : http://xdaforums.com/showpost.php?p=52650507&postcount=1050

#1052 : http://xdaforums.com/showpost.php?p=52651992&postcount=1052
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
The main reason, probably, while other had 'stable' releases are people who do not understand the development process which happens here. That's is IIRC also one of the main reasons why the release name now changed to M, and it is not called stable (because stable didn't mean what people thought it means.).

The only real difference between 'stable' and nightlies was/is the possibility to report bugs, but mcampbellsmith actively follows his threads, and everyone can report any issue here.

Second difference is that 'stable' builds were more stable than first nightlies, and it had to satisfy some criteria, but that still didn't mean it was/is more stable then later nightlies. This is also device specific, but for people who follow forums, and are informed, there is no advantage in flashing M. For example there were some bugs fixed and interesting features added to current nightlies after the M release for S4 and there is no single advantage to flash M build over nightly for S4 i9505.

tldr;

M/stable makes sense (IMO) only for people who don't follow the scene, have no idea what here happens, but want to try CM. It will prevent them to flash one of the nightlies from the beginning of the development which usually have a lot of issues.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] menvert:
Hi, yes I did try that (I posted results in OMNI page already) my Provider doesn't allow MMS over the internet APN so I can't combine them. Personally I use MMS so rarely it's not an issue, but it's be the most 'critical' bug.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] woodman:
OK sorry, I didn't see your post (#1056 in OMNI thread) :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
Thank you for the explanation, but that doesn't explain why the i9305 doesn't get M builds and other phones do. Menvert posted a plausible explanation, but no-one seems te really know...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Adrianer:
Reading at least the last few pages is something, that everybody should do before starting to ask questions...

Page 175, Post #1746: http://xdaforums.com/showpost.php?p=52429415&postcount=1746
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
?

Ok, i9305 doesn't get M because mcampbellsmith, and others, if there are any, don't pronounce any build M. Simple as that. Why he doesn't do that, because he doesn't see a valid reason for it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
I agree, you should always read the last few pages before you ask a question. And the same goes before you comment on someone's question!

Someone already said there's no such thing as stable builds...

...and I already replied to it.

But...

So yes, it's always a good idea to read up on a thread before you post :-p
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
:) this one would be more appropriate IMO:

Edit:

You basically gave him a pointer to it :).

http://xdaforums.com/showthread.php?p=51920034
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Adrianer:
Yes, this is the link from the link I posted. I thought pizzaman79 would be clever enough, to click on that...

I did. But you even didn't click on the link I posted... In that link the maintainer explains, why there are no M builds for this device...
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
You actually got your answers. Mcampbellsmith is a developer who maintain i9305, he doesn't want to release it, and he doesn't see a point of releasing it. You can download the last nightly rename it to M, edit build.prop file and enjoy your personal M.

If you want to discuss why other devices have M, go to that device thread and ask your question.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] thorcyar:
HINT for audio stuttering

Hello

suffering as everyonelse from audio stuttering (on liquidsmooth for now). I read the suggestions to change the governor to "ondemand", then I checked the CPU state .... and saw "core 2" offline, not going back to life.

So I set up governor to "performance", and ..... core 2 is still offline (c.f. screenshot). So could it be that after some time (or in deep sleep), the kernel shuts down CPU cores and can not wake them up after that, when power is needed ?

For now, I have just rebooted with governor as "ondemand" and all 4 cores are online and scaling ...

EDIT : and after 50min of idle, I checked the phone, and core2 is offline again ... and quite hard to wake (but doable in launching apps and apps). what the ?!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
Like i said, I had read back 20 pages even before posting my question so i had already read Mcampbellsmith's post before that link was posted. However, Mcampbellsmith's post contradicts the explanation on M builds on the official cyanogenmod blog, which states "Every M release for CM 11 has gone through a very specific code preparation and release process...The last week or so is spent making sure that the code for release is tested and branched accordingly to the new ‘stable/cm-11.0′ branches" I think Mcampbellsmith's post led to misunderstandings.

Case in point:

who clearly thinks there's no difference between nightly and M builds (and deems it necessary to mock me for it).

So i guess it's just a personal preference of Mcampbellsmith to not release M builds. And he brought his arguments in a way that led some people on this thread to believe there isn't any difference.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
No really, it is only you being a smart-ass. Releasing M would not benefit anyone, except people who are liable to placebo.

mcampbellsmith is aware much better then you what resources, and possibilities they have, and if making a M release would make any difference.

M release of i9505 has no single advantage over the nightly released on the same day as M. Actually IMO, and IIRC that nightly is more stable then M.

M and nightlies are different branches, but that, and the mention of testing doesn't make M magically better/more stable. Testing doesn't mean testing, finding bugs, and fixing them. It is a different branch, which moves slower, and this doesn't have to be more stable at all. It is not that simple.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Ansem:
Hi guys,I read the latest pages, about the m releas.but I want to return at cm11. Do I ask you if the nightly are so much unstable, or if I can use then in daily use.

Do you have done other particular room that fit your experience it's very stable? Even if based on the Samsung stock Rom

I'm sorry for that question, but I can't follow the forum, so I don't know such Rom it's stable or not :(

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
I guess you know better than ciwrl. Or than the whole CM dev team for that matter, for creating the concept of M builds, and the devs behind all but a few of the other CM11 supported phones, who do decide to release M builds. I'll add another quote by ciwrl on the official CM blog: "When we introduced the M’s, the common consensus was that they were just specially named nightlies. This was close to true for the majority of the CM9 cycle and most of the CM 10.x cycle. With CM 11 though, this is no longer the case. "

But I guess you know better...

I use CM11 and find it stable enough. But if you want to know, the best way is to find out yourself ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Ansem:
When I had time,I did like you say, but now I have time fit change Rom every 2/3 months, So it's impossible do like you say :(

Just for curiosity,I always used cm and omni, but what about the Rom based on Samsung stock? I think that they don't have problem auth the driver right?

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
What rom are you currently running? If you have a i9305, Samsung will release an official 4.4 update, so you could just wait for that.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Ansem:
Actually I am with the latest omni :) I read that more in the Samsung stock Rom there is knock, for that I didn't tried any stock Rom from android 4.3

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] woodman:
I assume you meant knox and not "knock" ;)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Ansem:
Yes XD

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
I had stock 4.3 and Knox is optional, it's like an app you can install, but isn't even installed by default. All that happens is you get a counter that says if the know warranty is void. But so what?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
Of course I know better than anyone else here, but that's different topic.

Are you aware this is an official thread?

There are lot of different approaches, concepts, attitudes etc to everything, and definitely to the software development issues, and your reasoning 'do you want to say you or he, or your master, know better then my') was never a nice one.

We would stil use DC current instead of AC using that' reasoning'.

Software engineering and project management have a lot of buzzwords, a lot of design patterns and anti patterns. Singleton was an important know how back then, and now is considered more to be like anti pattern, etc. A lot of similar examples from all areas of software development and further.

Some people see the point in releasing the M, some do not. Even the situation is different from device to device. S4 simply had, and still had more support and works better with CM. i9305 always had an issue with developers and support, and what mcampbellsmith did here, and still does is an amazing work from his side. Maybe we should ask him to release at least one More, for you, so you can sleep well, and it could be named like pizzaman79?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] pizzaman79:
Careful, you're close to acknowledging that an M build is not just a random nightly with a different name :-p

I agree he did a great job. Uunfortunately there never was an M build for the i9305, so it wouldn't be one more, but rather a first.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
You just acknowledge you don't really read what people write.

I even mentioned that M and nightly are different branches, where M branch lacks stuff from the nightly branche, and that's for the sake of 'stability'. I even mentioned an example, and there are lot of similar ones, where nightly released on the same day as M is, behaves more stable, has critical bug fixes, while having additional, useful features added.

You know, just doing a mini freeze, or standard feature freeze can help, but it often doesn't help with stability, and fixing bugs. Under circumstances it could, but it would require more resources, and different priorities, like OpenBSD developers have, for example. Everyone there shares same priority, and prefers more clean, and stable code, to adding new features.

That is not how the things work here, it is obvious, and it is a big question mark above my head, why are you still incapable of seeing that having an M here wouldn't mean nothing.

M release with ****ed up basic camera features... Most of time camera didn't work well on this device (I think there were short periods when this seemed to be a bit better.), but it looks like this got better in the last time. I still have to play a bit more with i9305 camera.

There are similar discussions happening in Linux world, and some things and priorities change, different angles come to surface with the time, and again people see how biased they were.

It is like Debian, for the sake of 'stability' (because they tested it.) stayes on the years behind old release of a software like Firefox. That's just crazy, and it doesn't make sense. But Ok, M only reminded me on this, it is a different situation totally.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] thorcyar:
could you please end this fight in private messages please (and eventually respect mcampbellsmith's choices ? It's not helping the devs burrying posts that might be of interest).

REGUARDING audio lags, I did more tests to try to help pinpoint the problem (on liquidsmooth, but who cares, it affects every CM based rom) :

- default kernel, cpugovernor ondemand : a lot of lags

- agnikernel, cpugovernor pegasusq : a lot of lags

- agnikernel, cpugovernor pegasusqplus : a little less lags but still a lot on a 30 min listening session

- agnikernel, cpugovernor pegasusqplus, phone in airplane mode : I had some lags in the first minute, and maybe 1 in 30 minutes (but I'm not sure it was a lag, it could have been a track change with a continuous music)

====> soooo what if the audio lags where caused by the modem part of the phone, for example triggering IRQ's while searching/changing from cell or simply communicating with the operator's network ? Or maybe the modem part on the phone eats too much CPU or i/o at some point that get higher priority compared to music app

REGUARDING mdm_hsic_pm0 battery-sucker-kernel-wakelock ..... I also have a theory for this one :

- I switched off location service for 2 days, and had no over battery consumption.

- then I had to search on maps for some shop, so I switched GPS on for a few minutes then OFF when I had found the shop. And look at the following battery usage (the phone got hot in my pocket) ==> it's like GPS was still ON (or the GPS part of the phone's modem was stuck) no matter what, until I powered off/on the phone.

====> soooo what if this kernel W.L. was the kernel activating the phone's modem in some sort of "location / GPS searching infinite loop, not getting the off signal" ?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Hbohd:
Really interesting investigation, thanks for that!

I hope [MENTION=2709509]mcampbellsmith[/MENTION] will look at it when he is back :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] !crazy:
Regarding GPS, I remember I was having problems with wake locks related to it, I think exactly the one you mentioned, but only after hot reboots. Cold reboot would then 'fix' the issue. That was an issue since the beginning of CM on this phone.

Regarding your governor tests, have you tried changing CPU idle mode? Have you tried changing /decreasing sampling rates? Also IO scheduler is important parameter.

Edit:

Another thing related to the GPS issue and hot phone; lot of it is going on when one turns location services on. All apps which use location based services go crazy, Google cloud services, like Google now, and all which collect data also (G+, photos, even if you have it off, my experience at least.), so if not on wireless modem will get hot. I have the same experience also with other phones, so I don't think it is i9305 related, or even CM related issue
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] skyliner342007:
Samsung S3 for virgin mobile

Just wanted to confirm with everyone that this CyanogenMod will work with my S3 that i will be getting from Virgin Mobile in a few days???

Thank you everyone.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] cheffy11:
That depends on the model of S3 u have?

If it is an i9305 then it will work if it is any other it won't.

Check what model comes up when u switch the phone on or reboot. It will say on the first screen of boot which it is.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] skyliner342007:
Looks like it may be the SPH-L710.....and it appears that Cyanogen doesn't have a stable mod for this model or at least i can't seem to find it???

Do you know if a stable Cyanogen Mod is available for my model???