yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] flupke02:
I updated exactly the same way as I always do using the CM updater in my menu (which always worked fine sofar), with the same recovery (Twrp 2.8.6.0), that I've used for several months now. Gapps (full) package I used was the one you linked to at the first page of this thread. Now I'm using the mini version, also via that link, but as said, that's still giving error notifications... In other words: I did not do anything else than I'd normally do, nor were there any system changes or anything like that...

I could try to find out how to get a log to you (I am not skilled like you ;) but as you wouldn't have time to look into it anyway, that seems quite useless...

I know you're a busy guy and I am very grateful for all the work you do, but it's a bit disappointing that you're suggesting the problem can only - and only - be at the user side...

I guess I will be sticking with the 21 September version then with mini gapps... Thanks anyway...
[ONE Original Android Development] IamsKs:
guys who are having encryption on this rom, do u have any performance issues like slow performance.. battery issues. or any other problems l. i want ti encrypt but still be sure first.
[ONE Original Android Development] m@++:
Same here, but I also didn't experience the reboot bug from the Oct. 23 build either. :D
[ONE Original Android Development] tosonny:
Clean install finished with mini gapps. Everythings works so far.

Edit: I suppose too big gapps (that were already installed) have a problem with the new rom-release. Rom ist ok, full gapps are ok. Rom and full gapps together = problem.
[ONE Original Android Development] AncientJames:
No performance issues at all. I was actually pleasantly surprised with that, especially after hearing about how sluggish the Nexus 6 could be.
[ONE Original Android Development] GertBagley:
1. Potential issue 1 is TWRP 3.02 is recommended in the OP. Not sure why you didn't try updating your recovery before posting.

2. Potential issue 2 is Gapps. I'm not sure if you're dirty or clean flashing. If dirty don't reflash Gapps.

3. XDA has detailed instructions on how to grab a log. No skill required you just download an app and export a text file. Or for reboots you grab a last_kmsg.

Sidenote: There should be an XDA quiz on Day 1 knowledge that you have to pass before posting. Really annoying to have uninformed noobs cluttering up the thread with their BS. It would be like sitting in an Intro to Calculus class and have some moron screaming about how he doesn't understand addition. Learn how to help yourself and then others will be more inclined to help you.
[ONE Original Android Development] tosonny:
Is this rom only for developers ...don´t think so. So it´s absolutely clear that there will be questions if suddenly strange errors occure (that you cannot solve by using google and trying differnt things). Where should we ask our questions? I don´t want to post in a forum that is not exactly related to this rom. If there is no "user section" we have to ask here. Only my opinion.
[ONE Original Android Development] flupke02:
Because this version always worked so far...

I know, but that does not change the fact that updating the rom failed before reflashing gapps, dirty or not...

As I said, I could find out how to get the log (don't think it's rocket-science), but that is not really useful giving the fact that Sultan won't look at it right now. Which I do understand as he's busy with the rest of his live, as he should be...

I truly apologize for not being part of the elite here. I try to understand what I am doing, read what I can find and try to learn as much as possible and figure it out myself. And still I am no specialist, nor will I ever be. Sorry.

Though you seem to be nice enough to try to answer some of my questions/remarks, guys like you are exactly the reason why it's always scary to ask things around here... Hope you are nicer to the people around you...
[ONE Original Android Development] Ruvy:
Music app crashing as soon as "Play Next" is selected in song's option. Cleared cache and data of amusic app and now its not even playing anything. Dirty flashed over 24th Oct. build. Rest of the ROM is as flawless as it could be.
[ONE Original Android Development] tosonny:
And how should I find out that suddenly the (in the very first posting) mentioned full apps are not working anymore with the newest release ...except of asking and getting answering here? Come on. I know what you mean but this here should not be reserved for developer questions only.

Edit: and what basics for the one is already quite a know how for an other.
[ONE Original Android Development] flupke02:
One last effort though: if you would have read what I actually wrote, you could have seen that Twrp 2.8.6.0 DID work for me, for several months without any issues. As it worked fine for a lot of people... It's only just now that this version COULD be the problem... (Oh, and version 3.0.2-0 is in the OP only mentioned related to the "oppo.verify_trustzone" error, as far as I can see. But I guess you have way better eyes...) And better words too... Lots of words...

I'll give updating a try though, you never know, thanks for the tip. Pity that you are not capable of talking in an adult, respectful way though. Have a happy life.
[ONE Original Android Development] Sultanxda:
Just because I won't look at your log now doesn't mean that I won't look at it later. If nobody gives me any log then I guarantee that I will spend zero time investigating this, as I cannot reproduce it.
[ONE Original Android Development] flupke02:
Okay, my apologies, you are right naturally. I'll try updating Twrp first, see if that makes any difference. If not, I'll post a log...
[ONE Original Android Development] twowheeler:
Clean flash with mini Gapps and no more problems whatsoever. Way to go [MENTION=4800121]Sultanxda[/MENTION]

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] Raainman:
I have updated the ROM with 2.8.6.0 without issues, and as you said as long as it works... Don't change it.
[ONE Original Android Development] dannymx:
Clean flashed and installed mini gapps to fix the Google Play Services crash problem.

But still no LTE.
[ONE Original Android Development] Sultanxda:
Prove it is an issue in the ROM by testing the September build right now.
[ONE Original Android Development] megatomic:
It's because CM has included the bloated POS software called Gello. It takes up so much room in the system partition that we are forced to use the miniature versions of OpenGapps. I think this is BS personally.
[ONE Original Android Development] dannymx:
I'll do it after I get home, I'm at work and my battery is at 40% after all the flashes I did today.

Here's the things I did so far today just FYI:

- Dirty flashed 10/23, I encountered only the LTE problem.

- Dirty flashed 10/25, still no LTE and now with Google Play Services crashing every second.

- Clean flashed 10/25 with mini gapps. GPS crashes stopped, but still no LTE.

I'll report back later tonight.
[ONE Original Android Development] Sultanxda:
OxygenOS is much larger, uses full Gapps, and does not have any issues. I'm not in front of my computer right now, but the OPO should have 1324 MB of space for /system, which should be plenty. The official CM nightlies are more bloated than my ROM and have Gello built in, and AFAIK nobody has complained about this on the nightlies.

Just shooting in the dark is not going to get us very far. We have yet to know *why* Play Services is actually crashing, and until a log is posted, that will remain a mystery.
[ONE Original Android Development] megatomic:
http://xdaforums.com/showpost.php?p=69221762&postcount=7319

I did some reading after seeing that and seems like this is the general concensus. I don't blame you at all Sultanxda, it's all on the CM team.

---------- Post added at 02:26 PM ---------- Previous post was at 02:24 PM ----------

Oh and my claims are strictly related to flashing the ROM and Gapps package, not Google Services crashing from within the OS.
[ONE Original Android Development] Sultanxda:
Lol wtf, that's ridiculous. Gapps failing to install on a clean flash due to space limitations makes things very clear.

I will remove Gello.
[ONE Original Android Development] megatomic:
Thank you. I never meant to insinuate that you had a problem with your ROM just to be crystal clear.
[ONE Original Android Development] takkischitt:
Installed (OTA) yesterday's update and all was well. Phone was running great. Installed (OTA) the latest and I'm getting that Google Services crash. So much so I can hardly get the little box to go away lol. I've always used the recommended full GApps and TWRP is most recent version, I think. I updated it not that long ago.
[ONE Original Android Development] Odysseus1962:
OK, after reading several pages of issues since the update and Sultan's excellent responses, let me jump in with my two cents. Begin rant:

If you're having problems do some troubleshooting before posting. If you can't figure out how to troubleshoot, you shouldn't be flashing ROMs, and you shouldn't be hassling the developer unless you can give him enough documentation to be able to help you.

This version of the ROM as I noted a few pages back, is much larger than previous versions. I bet many issues are gapps related, because they haven't adjusted to a smaller gapp package.

If you have an issue, the first thing to try is doing a full wipe and clean installing. Then if no issues restoring data from your nandriod backup. Many times people have issues because of third party apps that are installed. If f you run into a serious issue, clean install, then add apps back one at a time until the issue reoccurs. This is how you troubleshoot potential problematic apps.

Make sure you're on a recent TWRP or other suitable recovery.

If still having issues take a logcat and post along with your problem. If you don't know how to capture a logcat then search.

Don't post complaing about your issue if you can't provide information to research your problem. There is nothing anyone cab do without data to diagnose the issues.

Use some common sense people!!! [MENTION=4800121]Sultanxda[/MENTION] is not a mind reader! He says he'd like to help, but no one has provided any information for him to go on.

If you can't figure this stuff out, then don't run a custom ROM, just go back to stock, and quit wasting everyone's time posting useless complaints.

OK, rant over!!!

---------- Post added at 02:39 PM ---------- Previous post was at 02:34 PM ----------

If you don't like it, remove it! Duh!!! On open gapps you can customize the install to include or remove any app on the ROM or in the included gapp package. If you aren't smart enough to read the gapp wiki and learn about how to customize it, using their excellent scripts, you shouldn't be flashing ROMs.
[ONE Original Android Development] megatomic:
Ok, so I am pretty tolerant most of the time but... I don't want to use a trimmed down version of OpenGapps, and I have trimmed out packages before with the script feature. This time the ROM, due to upstream changes not created by our dedicated custom ROM developer, broke what I and other users had been accustomed to having used this ROM and Stock OpenGapps for a long time. If you were to try to install Stock OpenGapps on current CM Nightlies or the current Sultanxda ROM it would fail almost immediately due to not enough space in the system partition. Due to Gello it turns out. Granted using a smaller Gapps package fixes the symptom but it doesn't fix the root problem - Gello. Sultanxda has generously offered to remove Gello - who uses it anyways? It's crapware added to CM and needs to be gone as it is.
[ONE Original Android Development] maroonmed:
Flashed 10/23 from 9/21 without issue, but 10/25 broke Google Play Services making my phone virtually unusable. (Still have LTE, though...) Dirty-flashed mini GApps like some suggested and while this fixed the Play Services crashing it did break some other major apps, e.g. the Google Dialer, Keep, and GroupMe. Will clean-flash 10/25 and reflash mini GApps and let you know how it goes.
[ONE Original Android Development] acwest:
You probably don't need a totally clean flash, just wipe system before installing the rom and gapps
[ONE Original Android Development] maroonmed:
Thank you based Sultanxda :eek:
[ONE Original Android Development] W99DEY:
I only install the mini as the full version is full of bloat! Any additional google apps can easily be installed from the market place. This is not a new problem. It has been the norm for other ROMs for months.

---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------

open_gapps-arm-6.0-mini-20160219.zip is the one I have used before. Probably a later version now though... ;)
[ONE Original Android Development] AksHay1994:
Clean Flashed 25/10 with Pico Gapps, Xposed, SuperSU. no problems at all. Smooth and Stable. Thank You Sultan.....:)
[ONE Original Android Development] megatomic:
It's not bloat if you use the apps. Right?
[ONE Original Android Development] takkischitt:
Sorry for the ignorance, but if sultan removes the apparent cause of this bug, will the next OTA fix the problem? I'm just wondering as I'm not sure when I'll next have time to run through a full clean install etc, so just trying to plan so I'm not left with an unstable phone (for work etc). This isn't a criticism or anything. Thanks.
[ONE Original Android Development] megatomic:
What he said he was going to do is remove Gello from the ROM so that larger Gapps packages can be installed in recovery. I haven't seen that anyone has identified the source of the Google Services crashing problem yet so there probably isn't a fix in the works for that yet, if there is anything for Sultanxda to fix that is.
[ONE Original Android Development] dannymx:
The fix is to clean flash and flash mini gapps, not full gapps.

Other than that I don't know how to fix it without clean flashing.
[ONE Original Android Development] sToRm1nG:
[MENTION=4800121]Sultanxda[/MENTION]

I quickly checked my Oneplus One and I have no issues at all with LTE or GApps. I dirty flashed and I am not sure what GApps I was using, I asume it was Banks GApps.

No issues with Google Service crashes, everything runs smoothly.
[ONE Original Android Development] megatomic:
Sultanxda says he is removing Gello so we will be able to use whichever Gapps package we prefer to use. That is a fix, using smaller Gapps packages is a workaround. But semantics... sorry.
[ONE Original Android Development] B3L13V3:
Try updating your recovery, maybe that'll alleviate your issues.
[ONE Original Android Development] W99DEY:
There is no way in the world that all the apps will be used. When I clean flash, the google updater, when logged in reinstalls all apps anyway including ones not in the mini pack that I have installed . I presume they get installed in another storage area. The only part of the gapps pack you need is a working market place.! All the people here spitting their dummies out will just end the support from the OP!
[ONE Original Android Development] megatomic:
Whatever you say. Why would OpenGapps create a package of apps that no one uses?
[ONE Original Android Development] AncientJames:
I decided to clean flash with mini G apps and all is well, LTE and all (T-Mobile).

Would have spent the time troubleshooting, but I'm at work and I needed my phone. Awesome, snappy build, even with encryption enabled (need for my Google for Work account). Appreciate the great work.
[ONE Original Android Development] twowheeler:
Just checking: is it normal that on every boot the "starting apps" screen is visible?

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] takkischitt:
Oh, I thought that he meant that the cause of the problem was actually that Gello app, as it was the only major change to the system (and package size). I don't know about how the system allocates space, but thought that maybe due to the size of Gello, the Google Services wasn't able to run correctly. Looks like I might have to put up with this until I can do a clean install. Thanks for clearing that up.
[ONE Original Android Development] megatomic:
No problem, it's hard to keep these two issues separate and straight. At least is was for me.
[ONE Original Android Development] hmzuleta:
October 25 build works perfectly for me. I dirty flashed on top of the September 21 build, flashed SuperSU 2.78 and wiped caches.

LTE works.
[ONE Original Android Development] Sultanxda:
A new build is up with Gello removed. Unless this build sparks nuclear war and causes humanity to go extinct, I'm not going to make another build for at least a few more weeks.
[ONE Original Android Development] jenaplisken:
Gello it's the only difference?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] W99DEY:
Ha ha... Well done Sultan... ;)
[ONE Original Android Development] megatomic:
Thanks, I appreciate it a lot.
[ONE Original Android Development] Sultanxda:
Yes, that is the only difference. So if you're using a Gapps package that is larger than America's debt, then installing the 10-26 build won't make your phone explode.
[ONE Original Android Development] TekRantGaming:
Sorry if this comes across as rude I'm not trying to be

Will you drop support for us

I know ur busy i do follow the thread

Again sorry if that came across as rude thanks for all your work man :)
[ONE Original Android Development] jenaplisken:
For me any of your build is perfect. But if gello it's the only difference i will stay with 25/10. It's one week i flash every day a new build (beta and stable) [emoji6]

Anyway thanks thanks for this awesome build. I hope your op3 rom is like this....

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] KnightGalahad:
Hey, i've found that after the most recent update, none of my recovery flashed applications are functioning (ie. they do not install, and do not show up in my applications) Before the 23/10/16, update everything was working fine, but now, they no longer show up. I realise that this isn't a critical issue, but i'd like some feedback on how to fix this, if possible

Thanks,

KnightGalahad
[ONE Original Android Development] megatomic:
Well I feel a little sheepish but I still had to flash the Mini Gapps package in order to not have the Gapps install fail due to size limitations. Crap.
[ONE Original Android Development] THEVAN3D:
Can't record video. In any camera app. Not just the stock one.
[ONE Original Android Development] flupke02:
Well, updating Twrp to the latest version indeed did the trick! Another lesson learned... :)
[ONE Original Android Development] Odysseus1962:
All you had to do was create or modify your open gapps script to remove Gello if you had a problem with it (the script allows you to remove any app preinstalled on the ROM)! Now you folks have forced [MENTION=4800121]Sultanxda[/MENTION] to remove Gello, which some us liked and had no problems with, just because you're to lazy to do some work yourself! WTF! The Stock open gapps package is going to be too large for any of the upcoming Nugat builds anyway, so why not just make adjustments now?

Installing the full stock open gapps package is ridicules anyways! Nearly all of included packages can be installed from the store, and are constantly being updated. Once they're updated the newer version is installed in your data partition and the old one in your system partition just sits there no longer being used, creating wasted space unless you're continually updating your gapps every single time an updated app appears in the store. The freaking stock gapps update is nearly 650mb! Most would think it's foolish to waste 650mb of their monthly data allotment to update 15-40mb apps that are being updated several times a month, or sometimes a week! Use your head and think about it!
[ONE Original Android Development] X-Nemesis:
I've just updated to the latest build. How do you solve the "Google play services has stopped" issue?
[ONE Original Android Development] Mr hOaX:
Restore to factory version of Google Play Services by uninstalling the update

Reboot the device

Update Google Play Services App

Everything works great

You should try doing a clean flash
[ONE Original Android Development] mongoosesRawesome:
How do you uninstall the update? I cannot even get into Google play store.
[ONE Original Android Development] dylanraga:
If you're not using it already use the 241 modem.
[ONE Original Android Development] 3rt41:
After the latest update, when i went out of wifi range, my data connection was not up, still, and i had to go in and out of airplane mode again to fix that.
[ONE Original Android Development] neisor:
Is it only me that hears a silent sizzling when in call through the ear-speaker? It is the most noticeable when there's silence while in call. It's not loud but it's there. Haven't experienced it with the CM12.1 by you, [MENTION=4800121]Sultanxda[/MENTION] .

Thank you for considering this.

EDIT: Okay, now I see that this bug is reported in the Nov. 16 Bug-Thread (post number #1763).
[ONE Original Android Development] JasonEddie:
Trying it out now, thanks
[ONE Original Android Development] PivotMasterNM:
are you running the november 16th build with built in or different modem?

---------- Post added at 12:08 ---------- Previous post was at 12:06 ----------

don't necessarily compare this CM13 version to the CM12.1 version, this version is expected to still have bugs and is not by any means based off of a stable CM brachn like the CM12.1, hence the UNOFFICIAL name. (:

---------- Post added at 12:10 ---------- Previous post was at 12:08 ----------

turns out I simply didn't press it long enough haha thanks for the reply.

---------- Post added at 12:14 ---------- Previous post was at 12:10 ----------

does it sound like white noise? I suspect that it has something to do with your carrier &or the phone on the other end.
[ONE Original Android Development] neisor:
It's not carrier related, that's for sure since I had not this issue on any other ROM at any given time.

And yes, I know that this ROM is expected to have bugs, that's why I reported it here :) So in future builds it won't have such an issue.

Thank you!

EDIT:

I found another bug which is not reported in the Nov. 16 Bug-Thread:

The camera app when double pressing the power/sleep button will start by itself.
[ONE Original Android Development] TimV_:
Already did that problem stiil present
[ONE Original Android Development] Renosh:
What exactly did you do?

You wiped all /system /data /dalvik /cache and then installed ROM + open gapps (gapps-config.txt in the same folder), are you sure your downloads aren't corrupted?

Give more information in your post to get better help
[ONE Original Android Development] TimV_:
Yes I did all that multiple times also downloads the rom multiple times without gapps the roms works fine and yes placed the config in the same folder as the zip
[ONE Original Android Development] beukie76:
I can't download languages for Swiftkey: "unable to save language pack to storage".

I checked permissions and storage should be ok.

Can anybody help?

Thanks!
[ONE Original Android Development] jarylw:
Delete /storage/Android/data/com.touchtype.swiftkey/files and reboot
[ONE Original Android Development] sgroimax:
Hi guys. On the 11/16 release (latest one) I have found a huge bug. Root explorer and file manager can't grant root access. Titanium run good instead. I tried to flash SuperSU and bootloop it. So I re flashed the ota update without wipe anything. ROM booted well. All works as usual but issue with root persists.
[ONE Original Android Development] Lupin The Third:
How is this possible!!! :o
[ONE Original Android Development] sgroimax:
I really don't know how
[ONE Original Android Development] sgroimax:
This is what I had. Repeat: titanium works well as root
[ONE Original Android Development] AlexTheMatrix:
Might want to add:

Setting for on-screen nav buttons doesn't persist between reboots