yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ghmail2:
don't waste time to implement useless features. xposed+gravity box gives almost all the features. (double tap to wake to sleep,key mapping) just fix the nfc, name it stable. we are then good to go. pure aosp that is
[ONE Original Android Development] h2o64:
Basing is another question.
[ONE Original Android Development] zurden:
Sorry, did a rollback of nandroid backup. I use. Opengapps because it replace the aosp apps for the Google ones and also with gapps-config I can only install the apps I need.

If I try again to install it again, would you please tell me the steps to provide an useful log.
[ONE Original Android Development] Quasar:
http://xdaforums.com/showthread.php?t=1726238
[ONE Original Android Development] ALD76:
The crash is because google webview replaces the inbuilt version but the rom cant use it. Just add webview to your exclude list.
[ONE Original Android Development] S1611:
I'm getting one of the best Standby time of all time. What's amazing is that its without using any app blocker or greenify. Really great work guys! Thank you!
[ONE Original Android Development] zurden:
Hey [MENTION=6223408]ALD76[/MENTION] you are right. I excluded webview and I finished the wizard successfully. Thanks!
[ONE Original Android Development] h2o64:
Maybe [MENTION=5585603]Quasar[/MENTION] could mention it in the op :)
[ONE Original Android Development] arifqur:
Can you please guide me as to where in the GravityBox settings is the option for Double tap to wake.

Thanks in advance
[ONE Original Android Development] mittimus:
Is xposed working on it?
[ONE Original Android Development] karthi89:
Audio cranks at start.. Whenever I receive a notification, sound cranks at start.. Experienced the same with oxygen.. Never had this on CM based roms.. Also 9gag force closes frequently.. Will post log later.. Standby time is really good.. Great work guys..
[ONE Original Android Development] gd6noob:
I didnt see this in the "What Doesnt work" section in the first post.

No LTE... I went into phone settings and manually set to LTE only and it still only shows 3G...

Also went to manually set the APN... still doesnt work.

Sending SMS doesnt work with Messenger and Messaging apps. I had to us Hangouts to send out normal SMS to friends.

Are these known issues also?
[ONE Original Android Development] Quasar:
Have you flashed MaxxAudio? That caused the issue on Oxygen. Audio is fine for me using a newer MaxxAudio

It shows 3G, but it's actually LTE, because LTE is technically 3G. Messaging with the stock messaging app works as well.
[ONE Original Android Development] gd6noob:
thanks for the quick response.. i love the rom so far... fast and snappy...

about the msg... when i send out the msg, it doesnt how up in my chat history.. so its a blank... i tried to send out 1 msg to friend and 1 test msg to my brother...
[ONE Original Android Development] karthi89:
I never used maxxaudio.. System is clean. I didn't modify anything..
[ONE Original Android Development] Quasar:
Strange issue. Try reflashing.

Maybe some APN settings? Everything's working fine for me, as well as another tester.
[ONE Original Android Development] roemicha:
Having issues with notifications being able to be expanded on lockscreen.
[ONE Original Android Development] Quasar:
Notification expansion is not supported on AOSP.
[ONE Original Android Development] roemicha:
Thanks. Explains why I'm having issues. Great ROM!!!
[ONE Original Android Development] h2o64:
We doesn't use CM audio low latency.

But we can trick audio policy eventually
[ONE Original Android Development] ~KV:
No AppOps? How do I control auto-start,keep awake and wake up permissions?!

Please do not suggest using xposed as I don't want to bloat this ROM with that....

Also, dt2w is enabled by default and can't be changed it seems...how do I disable it as I presume that would just drain the battery more....:(
[ONE Original Android Development] BBobby:
Set correct APN
[ONE Original Android Development] h2o64:
This isn't cm. However you can't fix dt2w by building yourself the rom
[ONE Original Android Development] ~KV:
Yeah I get that!:D

That's the best part of this ROM that it ain't cm! But my question was wouldn't Google play services and other apps drain battery on standby without AppOps? How would the auto-start permissions be taken care of?

Doesn't dt2w drain battery on standby?

Would be great if at least network activity arrows and battery percentage could be added!:)
[ONE Original Android Development] spanish33:
For App ops you can try https://play.google.com/store/apps...p+ops&pcampaignid=APPU_1_Pl8SVq7OK4S9eIehsNgK

You can set selinux to permissive mode and you would be able to uncheck dt2w, I saw it is already fixed in the source code.

Edit : if you just want the percentage to show in the battery you can use https://play.google.com/store/apps/...abler&pcampaignid=APPU_1_XWISVpmpAoXJeo2wsKgF
[ONE Original Android Development] KINGVADER:
Amazing! Truly amazing ! Smoothness of this ROM is ∞

---------- Post added at 12:13 PM ---------- Previous post was at 11:48 AM ----------

And please add appops in next build no user considers it as bloatware its an essential feature [emoji28]

DARK SIDE™
[ONE Original Android Development] miguepereira77:
It was broken...that's why they didn't add it at the end
[ONE Original Android Development] BBobby:
You need to read at least the early posts instead of talking about already-addressed issues. If you want to control auto starts there is an app called autostarts. App ops wasn't added because they will be default on M. But there's an app-module if you want that too
[ONE Original Android Development] kylethelife:
Is anyone else having issues with lockscreen notifications? I can't expand the lockscreen notifications so I can't mark the SMS I receive as read from the lockscreen for example. When I try to expand it, it just goes back being "unexpanded"

I actually had the same issue on the last build but I was hoping it would be fixed. Anyway, great job otherwise! The lack of hardware mapping just forced me to get GravityBox
[ONE Original Android Development] Quasar:
Expanding notifications is a CM thing. Doesn't exist on AOSP, plus it's just a minor hassle, so we never really bothered adding it. ;)

Also, for everyone asking about stuff like AppOps, Layers support etc. All these things are natively supported on Marshmallow, and since Lollipop is now EOL, there's no point working on adding those features for a build that will last a week or so tops, so please wait patiently (or impatiently, like we are) for Google to drop Marshmallow sources and then CAF to do their magic. :)
[ONE Original Android Development] ananbanka:
Would you considering adding soft keys activation via settings on M? :)
[ONE Original Android Development] Quasar:
We're already trying to get it working on L via a flashable zip.
[ONE Original Android Development] ananbanka:
Thanks guys! Love your work! :)
[ONE Original Android Development] ksigit:
Just FYI. Latest build supposed to have f2fs support, but somehow it won't boot, stuck in oneplus logo. It boot OK with Render-CAF kernel, but wifi is broken.
[ONE Original Android Development] raggatokan:
about soft nav buttons:

That is great to hear! Awesome ROM btw.

Meanwhile, is there any way to change menu button (hardware) to recent and long-press home to google now? With xposed maybe (if so, which module?).

THANKS!
[ONE Original Android Development] TheNakedMam:
Still waiting for that magic! I hope you guys don't run into any major issues with the first M build, that would really suck :/
[ONE Original Android Development] johnb380:
The source hasn't even but pushed yet so how could they be working on it?

I did read just now that OCT 5 is supposed to be the date its released so we shall see soon enough if that's the case or not.

? GOOD LUCK and GOD BLESS!! ?
[ONE Original Android Development] miguepereira77:
U can use GravityBox to customize almost everything on r liking...
[ONE Original Android Development] h2o64:
I'll link to the op the only commit needed to make a custom kernel fully working. (and if we are lucky, it might even work with non-caf kernel)
[ONE Original Android Development] jukiewalsh:
6.0 factory images are live! Only a matter of time now
[ONE Original Android Development] AbhishekS:
Yay!!!
[ONE Original Android Development] kdb424:
That was the perfect post for number 1000. That made my day even better!
[ONE Original Android Development] Quasar:
Looks like Google's started pushing the Marshmallow source!

https://android.googlesource.com/device/lge/hammerhead/+/marshmallow-release
[ONE Original Android Development] beatbrot:
Hope we see a Marshmallow-AOSParadox-build soon *.*

Need that battery life because my university got free Wifi this week and now i just use my phone the whole day :P
[ONE Original Android Development] FunkyRasta:
Everything is better with bacon, Marshmallow will be no different. Thanks to you, guys !
[ONE Original Android Development] BBobby:
Gravity box
[ONE Original Android Development] thenessus:
Marshmallow and bacon, must taste gooooood.
[ONE Original Android Development] beatbrot:
We need that Doze so much!
[ONE Original Android Development] jukiewalsh:
And whenever that finishes, the next mashing f5 lobby.

https://www.codeaurora.org/cgit/quic/la
[ONE Original Android Development] kdb424:
Did Marshmallow source drop? I thought it was only images.
[ONE Original Android Development] kalapapa:
Images are up and ota should start soon

Google right now is uploading marshmallow source right now so it will take awhile
[ONE Original Android Development] kdb424:
Dang. I didn't realise that we were getting both drops in one day. I think there was a delay with lollipop. That's good to know. I'll be flashing the first one ready for the 1+1! I know it'll be a while. There's a new build system it would seem by looking at the new pages on compiling android source, so it'll probably take a bit longer. Times like this I still owned a computer. All I own are android devices these days. In any case, back on topic. Very much looking forward to the pure CAF image. Good luck, and I'm here for testing when the time comes.
[ONE Original Android Development] Quasar:
The full Marshmallow source is up. Now we're just waiting for CAF to wake up.
[ONE Original Android Development] ugvpkn:
Anyone know if T-Mobile WiFI calling will work with Marshmallow ? Thanks.
[ONE Original Android Development] jukiewalsh:
Does it work on lollipop with this phone? I thought it was proprietary software.
[ONE Original Android Development] ugvpkn:
It does *not* work with L. The reason I asked is because it is supposed to be baked in and no longer requires a carrier specific build. It might still be device specific since I didn't see any success noted in the Nexus 5 forums. Hence the question. Thanks.
[ONE Original Android Development] johnb380:
You know you can use hangouts dialer and it even shows your number in the caller I'd to the person your calling!

It works great and uses all WIFI unfortunately you can't receive calls thru hangouts dialer unless you link Google voice account but I save alot of minutes a month using it!

? GOOD LUCK and GOD BLESS!! ?
[ONE Original Android Development] kdb424:
I have the $30 t-mo prepaid with 100 minutes, and because of that, almost never do I have a single minute used. I get calls through LTE too, which is pretty nice. That's why I won't port the number to project fi even if I get a supported device :D
[ONE Original Android Development] johnb380:
Ya that's the plan I have too. You just can't beat it its really the best plan on the market. Me and my wife both have the same plan we went from spending 150 a month to 65 with it.

? GOOD LUCK and GOD BLESS!! ?
[ONE Original Android Development] AYEHAN:
The news i really wanted to hear early in the morning :)

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] ~KV:
Is it possible to just make a non-CAF build now instead of waiting for CAF, now that the source code is up for M? Why wait for CAF? At least we'll get to try M:D
[ONE Original Android Development] KINGVADER:
No in my opinion CAF is better and the ROM IS CAF BASED!!!!!!!

DARK SIDE™
[ONE Original Android Development] h2o64:
Because this is a CAF based ROM?
[ONE Original Android Development] Aka91:
Was that a troll? It looked like a troll. ??
[ONE Original Android Development] Quasar:
Pure AOSP is difficult if not impossible for a non-Nexus device. CAF AOSP is the closest we can get.
[ONE Original Android Development] issawillwin:
Do you guys think that it will be as long as last year to get the first build ?
[ONE Original Android Development] Quasar:
Mostly no. If CAF wake up quickly and start mass-merging, we could have a build as soon as tonight or tomorrow if there aren't any device specific tree complications
[ONE Original Android Development] arifqur:
Hope that is the case
[ONE Original Android Development] AYEHAN:
[MENTION=5585603]Quasar[/MENTION] i have no knowledge what am talking but just to pass time while wait

On CaF site generic device and msm8*74 is updated couple of hours ago .. Is it what i should look if i wanna make a estimated time just for my sake

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] jukiewalsh:
Hasn't started yet, wait until you start seeing new branches like "aosp-new/marshmallow" although I'm not sure they'll merge for bacon right away so watch under device/shamu or device/hammerhead
[ONE Original Android Development] FalconFX:
can you plz add prevent accidental wake up on dt2ww, it keeps activating in my pocket :o
[ONE Original Android Development] AbhishekS:
This.

And honestly speaking, without this dt2w gets so annoying that I wish to turn the feature off. [emoji14]
[ONE Original Android Development] renaltosonylevi:
Do you guys have working proximity sensors? Because for me everything seems to work as it should. If I cover the proximity sensor DTW will not work.
[ONE Original Android Development] AYEHAN:
Yup just tested covering proximity and DT2W didnt worked

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] Aka91:
Use dt2w once while leaving it uncovered. Cover it and do it again. ;)
[ONE Original Android Development] jukiewalsh:
Gravitybox can fix the proximity sensor, but I haven't noticed any issues yet.
[ONE Original Android Development] tekanina:
I just enabled this in gravity box cause my phone was on in my pocket for 1.5 hours at work and it wasn't all at once. Had apps open and music playing, I had the volume down though.
[ONE Original Android Development] tekanina:
Apologies for double post said they both failed when sent.
[ONE Original Android Development] BBobby:
Hey guy have you heard of transparent pants? :p

Me too. I work in healthcare and my phone is on my chest pocket (which is kinda loose and makes the phone boune around quite a bit. Not once have I seen the screen turn on "accidentally"

Built in "prevent accidental wake", baby!!!
[ONE Original Android Development] AYEHAN:
I use original flip cover so its a issue with me either

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] roemicha:
This may not be the place to post, but was trolling AFH and found a Stable release of AOSParadox 10.05.15 uploaded by [MENTION=6240827]Quiche[/MENTION]. Has anyone tried?
[ONE Original Android Development] Quasar:
That's just a little test build he's uploaded with random crap that he wanted to try. Don't flash that. ;)
[ONE Original Android Development] FalconFX:
for me the preventing accidental wake up works intermittently !
[ONE Original Android Development] jukiewalsh:
go check caf guys!

itshappening.gif
[ONE Original Android Development] Vekhez:
I know that I'm not supposed to ask things like this, but everyone is thinking it and I just can't resist.

What is the possibility of CAF merging and us getting a ROM that doesn't have any NEW features or changes from the Oct 1st build, other than M?
[ONE Original Android Development] AYEHAN:
Dont know whats happening .. I will wait for it into a flashable happens :)

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] jukiewalsh:
The devs already said it will *most likely* be an easy bringup to M once caf finishes merging aosp and shouldn't take long. But that's not a guarantee and doesn't mean we'll necessarily have a build right away so give them some time to bring us the awesomeness! :good:
[ONE Original Android Development] kdb424:
It's been stated here (A long ways back, I don't blame you for missing it) that the last release should be the last release of 5.1.1. There may be changes, but nothing massively planned as they plan to move over to M source ASAP. Which bites as it'll be a while for the update, but that means 6.0 even sooner, which is good in my book.
[ONE Original Android Development] h2o64:
I confirm.. Not too late.. Unfortunately,it's not the best day to dev for us.
[ONE Original Android Development] jukiewalsh:
No problem I think we're all willing to wait, yet excited for when you guys do get a chance to start!
[ONE Original Android Development] thenessus:
Devs, are you going to cover my expenses for a broken F5 key? I'll take it to court if I must. I will!

And no, a refresh button on a browser is a lousy alternative.
[ONE Original Android Development] KINGVADER:
??????

dark side™
[ONE Original Android Development] imam.krismanto:
[MENTION=5585603]Quasar[/MENTION] do you have plan to build Android 6 from AOSP source?
[ONE Original Android Development] Hetalk:
Nope. They'll be doing it from CAF sources. :good:
[ONE Original Android Development] L0X0R:
Just wondering what it would take to use the sources released onto the OPO. Like do you have to modify them to work with the OPO? Or can you just build it easily enough ?
[ONE Original Android Development] Hetalk:
I'm sure there will be some modifications. But, this team has done it once, they can surely do it again. :highfive:
[ONE Original Android Development] L0X0R:
I'm sure they will. Just really keen on M. Even if I have to build it myself! hehe.

Waiting is hard man.. :p
[ONE Original Android Development] xda-amg:
Perhaps you can do nothing to prevent from wakeup, but having a lock screen like password or pattern prevents it from accidentally running some programs.
[ONE Original Android Development] Quasar:
By the way, for at least a month or so, Marshmallow builds might not have the bells and whistles that the lollipop builds have. It'll most likely be vanilla CAF AOSP. Nevertheless, we are all anxiously tracking and cursing CAF, waiting for them to release.
[ONE Original Android Development] ananbanka:
Please implement soft keys with your M release if you can! :)
[ONE Original Android Development] L0X0R:
I think I'd rather plain M rather than fully featured L atm. I at least wanna give it a go. Interested in the potential battery performance.

Is the caf git what you are tracking?

Here https://www.codeaurora.org/cgit/quic/la somewhere?
[ONE Original Android Development] ~KV:
Yeah, as far as cursing is considered I'll help you with that:p

BTW, how long does CAF generally take??
[ONE Original Android Development] Ofthecats:
What do you mean by this? Missing customizations or missing features?
[ONE Original Android Development] Quasar:
Yep

Last year it took a day

Well, I'm sure you know what vanilla AOSP includes.
[ONE Original Android Development] L0X0R:
bacon doesn't have a repository. which device chain does opo use?
[ONE Original Android Development] xtremez:
Has anyone tried flashing the Oxygen OS radio? Cause i've tried that and it seems to have killed my wifi :( i was previously on Blisspop but decided to give this a shot.
[ONE Original Android Development] Quasar:
MSM8974. We use our own device tree. The branch is in the thread title, though that will probably change with the M release.
[ONE Original Android Development] L0X0R:
Oh thanks. I thought it was something weird like that :P

Sweet. Just sittin, waitin and keeping myself busy till it's out :p
[ONE Original Android Development] thenessus:
Heh... don't think so.

Appearently Google did not fix the infamous Mobile Radio Active bug in M, contrary to their promise.

Doze or not, that is miserable. :(
[ONE Original Android Development] taufiqs:
I have observed that the sultan kernel tends to lock minimum freq to 1267MHz. This freq is the second higher after idle freq 300MHz. Anyone have notice this? This maybe the reason why screen on battery life is not so good. I dont play games. Mostly on whatsapp. 300MHz should be enough for this app though. Why boost to 1267MHz where you dont need it?
[ONE Original Android Development] cantthinkofagoodname:
Do you have a source for this?

Because that would be a real bummer. It's the only reason that I was looking forward to 6.0.

I'm back on Kitkat for that reason a few months now.
[ONE Original Android Development] thenessus:
Me and you both, buddy.

Check out the M bug tracker, as well as M discussion threads for Nexus devices (usually in General Discussion section).
[ONE Original Android Development] _ASSASSIN_:
Touch input for responsive interactivity of the app. Android made touch boost a long time ago.
[ONE Original Android Development] L0X0R:
Watching an M review. I want it so bad.. :P

Gonna be sleeping soon here in aus. Hoping it'll be out ;)
[ONE Original Android Development] johnb380:
Built in Doze and app standby are the only new things for Android M. So idk why everyone is so excited for this as we've had both them things in custom ROMs for over 6 months now.

So what is this big refresh fest for? There are literally no cosmetic changes to M over L. It truly should of been Android 5.2 not 6.0.
[ONE Original Android Development] issawillwin:
You forgot native rro support, multiwindow, google on tap, new launcher.
[ONE Original Android Development] johnb380:
Aosp won't see any of those except rro support maybe. The rest is closed source for Google.
[ONE Original Android Development] _Man0waR_:
Well, the permission management is not a cosmetic change AFAIK and it's much better and a very important part of the OS. I know you will tell me XPrivacy is even better :)

Anyway this is not the place to discuss this.
[ONE Original Android Development] Akath19:
It's quite likely that all those things are in aosp, except for the fact that they all need GNL, which is a Play Store download away.

The fact that all those things are closed source doesn't mean that custom ROMs can't have them.
[ONE Original Android Development] johnb380:
No but it means that the Aosp code won't have them. Anything that's proprietary to Google won't be in Aosp only open source is include in Android Open Source Project!

I'm saying they won't be in this ROM not that they won't be in any ROM eventually. But it will be a looooong time til CM has a stable CM 13 ROM available for our device since everything has to be adapted to this phone since its not a nexus device and its not a priority anymore since the One+ 2 is out now we will be waiting awhile before we see any true Android 6.0 ROMs for the One+ 1.

Aosp is probably the only chance well have for 6.0 honestly. And we all know Aosp is very stripped down so it is gonna almost be the exact same thing as 5.1 ROM for us.
[ONE Original Android Development] TheNakedMam:
Then where the f*ck is the point in releasing "major" updates of Android when it's features are locked down to Nexus devices? Android doesn't seem so Open-Source now that I know thi crucial information.