yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Semper80:
It will be a new update until end of the week? Just asking! I'm curious. ;)
[ONE Original Android Development] abhibnl:
And that 'just asking' is called ETA which is against XDA rules. We all are waiting for the new build mate. I bet it'll be worth the wait.

Sent from OnePlus One
[ONE Original Android Development] g3minII:
I bet too but the wait is becoming unbearable. My flasholic thirst is not being quench [emoji6]

Sent from my A0001
[ONE Original Android Development] iamelton:
the "long" wait means the devs are not compromising on the build quality just for the sake of satisfying the impatient (including me.. ;) ), which is actually a good thing..
[ONE Original Android Development] notanoob:
I believe mobile radio bug is only going to be fixed in M , someone correct me if I am wrong .

There is always this misc usage showing in battery stats on 13th build , even though I don't have xposed installed . I'll get BBS stats as well to figure it out .

Doze in Lollipop ?[emoji15]

Seems to be system ui app is causing wake locks

Here's one more from Wld
[ONE Original Android Development] kalapapa:
I had that too but I think it's caused by ambient display.
[ONE Original Android Development] AYEHAN:
How do i get rid of this msg
[ONE Original Android Development] h2o64:
We are now all free and available to make progress. We are targeting this weekend for a release
[ONE Original Android Development] elementalfusion:
Looks like it's gonna be a great weekend!
[ONE Original Android Development] taufiqs:
To reduce usage of the power button. it is very convenient rather than push the power button.

you should use prevent accidental wakeup instead of completely remove the option to enable/disable it. IMHO.

yes +1 for the switch.
[ONE Original Android Development] spanish33:
[MENTION=4792450]h2o64[/MENTION] Google removed the miscellaneous battery stats in release builds do you think you can remove it also, or at least give us the option to turn it off and on?

https://android.googlesource.com/platform/packages/apps/Settings/+/android-5.0.0_r5.1^!/

https://github.com/SimpleAOSP-Lolli...mmit/d025994f90722139dfcf236f275e05236ec47491
[ONE Original Android Development] Setting.Out:
Been running great!!.. :)
[ONE Original Android Development] Semper80:
It will be an update today? :)
[ONE Original Android Development] santoshvaza:
[MENTION=4792450]h2o64[/MENTION],

new version can be dirty flashed over previous version..?

---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------

[MENTION=5585603]Quasar[/MENTION],

,

Thanks for great ROM,

pls keep it as pure AOSP as possible.
[ONE Original Android Development] darshan_dex:
Is this your own home build?
[ONE Original Android Development] :
Don't know if its official or not, but you can give this one a try, its from the 25th.

https://www.androidfilehost.com/?fid=24052804347822322

EDIT, build by [MENTION=5441030]jukiewalsh[/MENTION] so be sure to than him vvvv
[ONE Original Android Development] jukiewalsh:
Been running it since this morning, stock source built. probably gonna take it down after I get back from class because I don't think the devs wanted shared builds out and didn't think someone would already have found it lol.
[ONE Original Android Development] :
My bad then.

You could keep them up and just not post it on the thread, the project sources are open for a reason. I'm sure the devs just don't want the hassle of having to support home builds on their threads.

But I may be wrong, hopefully a dev will give a clearer answer.
[ONE Original Android Development] lokesh.3440:
Buddy have they included Dt2W and h/w button customizations in recent build ??? Then I am surely gonno flash it soon
[ONE Original Android Development] jukiewalsh:
Yeah that's what I was thinking too, I'll just wait for now
[ONE Original Android Development] Semper80:
I hope the battery life to be as good
[ONE Original Android Development] h2o64:
?

We leaked a lot of stuff. But nothing today indeed..
[ONE Original Android Development] Setting.Out:
I saw it uploaded, didn't pay attention to who built it.. Nice build :)

No, and no..
[ONE Original Android Development] joefso:
This build is running ok, no wars yet :)
[ONE Original Android Development] AbhishekS:
Calm before the storm. It's coming! ;) :D
[ONE Original Android Development] darshan_dex:
Two questions:

1. When?

2. How do you know? :p (source)
[ONE Original Android Development] jukiewalsh:
1. No ETA's on XDA

2. They said they had more free time now and are working on it again, check the git.
[ONE Original Android Development] darshan_dex:
Yeah, I know that rule. I didn't bug the devs by asking them. I asked that guy.

Oh Alrighty, Thanks! :P
[ONE Original Android Development] KenjiHannya:
Hopes suffered ?
[ONE Original Android Development] AYEHAN:
A indian tech website released a list of Brands/Models that gets Android 6.0 update

http://www.jgsdroid.in/2015/09/list-leaked-android-60-marshmallow-will.html?m=1
[ONE Original Android Development] Vekhez:
Obviously not totally accurate, I don't think there has been anything saying that the One is going to get official OxygenOS 3.x (assuming they change to 3.x for Marshmallow), I mean we have Oxygen OS support till Jan 1st 2017, but I mean we have had Oxygen support for 202 days since there has been 5.1.x and we are still on 5.0.2. So what's saying that we have 202 days from M's release before we get it..

It also doesn't say that the Z5 is going to get Marshmallow, which it basically guaranteed is going to get it.
[ONE Original Android Development] AYEHAN:
As i read it, it stated OnePlusOne and OnePlus 2 but with Oxygen/Hydrogen, so it means we will have CM 13/6.0 not the Oxygen/Hydrogen
[ONE Original Android Development] Vekhez:
Geez I'd rather wait for Oxygen that Cyanogen.. we are going to have system wide Cortana and a million other buggy features..
[ONE Original Android Development] notanoob:
Thanks for the valuable info , let's stick to the op from now on [emoji6]
[ONE Original Android Development] AYEHAN:
We ate sticked to OP, thats why we ate here, it was a just a little headsup while waiting :)
[ONE Original Android Development] AYEHAN:
Oh and thx [MENTION=5441030]jukiewalsh[/MENTION] for the home build, nd thanks alot to devs 9/24 is awesome in battery life, i guess more optimizations added ... Cant wait for official build now :)
[ONE Original Android Development] AYEHAN:
Nice battery and stable Code
[ONE Original Android Development] BBobby:
Error. Xda app did not want to upload pic

Any who. , 8 hrs of running, worst wakelock is 7 minutes long. NLP wakelock with 14000+ entries.
[ONE Original Android Development] Rohitgomes:
xposed modules not working
[ONE Original Android Development] jukiewalsh:
Everything's working fine for me, what particular module? Make sure you flash the right framework
[ONE Original Android Development] AYEHAN:
Xposed working fine for me, am using amplify, powernap and gravitybox

Tested working on both builds official and jukiewalsh home build
[ONE Original Android Development] h2o64:
Can you screenshot the bottom of the page too?
[ONE Original Android Development] AYEHAN:
Here you go
[ONE Original Android Development] wollah_91:
I dont know if it's already mentioned but when i take a picture, while on silent mode, the shutter still makes a hard sound when the picture is being taken. Is there anyway to shut that down?

My appologies if this already has been explained.

Great rom! Been using it for as a daily driver now for a 1,5 week or so. Great job!
[ONE Original Android Development] AYEHAN:
Waking up in morning is very hard thats why i have 5 alarms 0700 0710 0720 0730 0740

Now the issue is first two alarms went fine always but on third alarm at 0720 screen never wakesup and after the phone stop ringing alam(snooze) the phone soft reboots.

Edit : the last two alarms also went fine after the soft reboot, will try 6 alarms tomorrow if the 2nd time it happens or not
[ONE Original Android Development] wollah_91:
I flashed the following framework & installer and it works.

Flash the framework in recovery and make sure to wipe cache and dalvik or you will experience softloops at boot .

Downloads:

Framework: http://xdaforums.com/attachment.php?attachmentid=3469283&d=1441910102

Framework installer: http://xdaforums.com/attachment.php?attachmentid=3383776&d=1435601440

Good luck!
[ONE Original Android Development] joefso:
Lol x2

Same problem, I use alarm on my PC that plays hardcore music - horrible crap, I know but it is very effective. I also need to get up from my bed to walk to the PC.

Keep us updated.
[ONE Original Android Development] h2o64:
[MENTION=5585603]Quasar[/MENTION] any clues about an issac?
[ONE Original Android Development] spanish33:
I had to remove powernap module because of this. Well at least for me that was the issue.
[ONE Original Android Development] Vekhez:
So obviously the this weekend release goal is not going to be or?
[ONE Original Android Development] BBobby:
They said they had time to work on a new build this weekend. Nevertheless, it is practically illegal on XDA to make statements like yours. It'll be ready when it'll be ready. This ain't Motorola, these folks don't get paid to release builds. You know... Personal life?

One plus One powered by AOSParadox
[ONE Original Android Development] Barbi®:
This is just my advice: if you want daily build install builduntu in virtualbox then follow instruction in OP, it's easy, you just need about 100 free GB on your PC and a decent network connection. First build will take probably a whole afternoon (repo sync and build CCache from scratch) but then next builds will be ready in less than 30 minutes, and you can have all the latest updates whenever you want. ;)
[ONE Original Android Development] miguepereira77:
[MENTION=5441030]jukiewalsh[/MENTION]
[ONE Original Android Development] jukiewalsh:
It's just a home build I had put on androidfile host that was intended to stay hidden for a few days haha. I had asked if you wanted me to take it down and I thought you said it was okay?
[ONE Original Android Development] Vekhez:
Woah woah woah, 1, I do make home builds, and I was more so just saying that yes, there isn't going to be a build this weekend clearly. I wasn't asking for when the next one is going to be or anything like that, merely just making a statement so calm down. Thing is that not all the things that they are doing are able to be added to homebuilds, eg dt2w.
[ONE Original Android Development] AYEHAN:
What if i add clock into enduarance mode
[ONE Original Android Development] h2o64:
Alrightly. Just avoid making them public
[ONE Original Android Development] jukiewalsh:
I didn't before people just found it, sorry I made it private now.
[ONE Original Android Development] jukiewalsh:
Anyone able to get android pay functioning? I thought since it's based off caf/aosp instead of cm the extra dependencies would be included but I can't figure it out. Tried rootcloak, SuperSU method, and an unrooted clean flash
[ONE Original Android Development] AdrianM:
Android pay won't work on custom roms, no matter how much you try to hide root. More on that:

http://www.xda-developers.com/google-security-engineer-explains-issues-with-root-and-android-pay-in-the-xda-forums/
[ONE Original Android Development] _ASSASSIN_:
last time I checked you have to edit the build.prop and not have root.

The reason being is that android pay doesn't work on user builds, it only works on OEM builds, such as COS 12 or touchwiz etc.

One way to fix this is by changing all of the things in the build.prop that have it to be something like "release keys" instead of "userdebug" for a something like ro.build.type
[ONE Original Android Development] jukiewalsh:
Yeah but I had read a comment somewhere about it being cm based vs aosp because a nexus user said he got it running.

Thanks I'll try that out
[ONE Original Android Development] TheNakedMam:
Will it work on OxygenOS (for the One)?
[ONE Original Android Development] jukiewalsh:
Starting to get off topic now, but no I think it has to be cm12s or a fake build.prop
[ONE Original Android Development] TheNakedMam:
Shoot...I prefer the cleaner stock-like experience of the OxygenOS.

UPDATE: Now that Android 6.0 is coming in just a week for Nexus devices, when can the developer community expect the source code?
[ONE Original Android Development] FunkyRasta:
October 5th I believe. Dont take it for granted though, don't remember where I've read it.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] ananbanka:
The code is being pushed to AOSP on 5th, I think! In really hoping the next update is the last lollipop update! ?
[ONE Original Android Development] AYEHAN:
Or maybe there will be no lollipop again for AosParadox :)
[ONE Original Android Development] johnb380:
That's Aosp for the Nexus devices so there will be a few weeks if not months of turn around for the code to be adapted to the oneplus one.
[ONE Original Android Development] h2o64:
But lucky you this ROM is aosp. CAF usually push their sources one day max after the release. Just hope that the chipset is still supported.

We agreed together (in the team) that Wednesday was the last chance. If nothing is up for Wednesday. That means that it was the last lp release.
[ONE Original Android Development] Quiche:
We will make one last lollipop update for sure. After this release we'll be moving to Android M. This last lollipop update (if all goes well) will be released later today.
[ONE Original Android Development] Gapkobob:
Spamming my f5 key, too exciteed for update!!!
[ONE Original Android Development] dmanlfc:
Awesome work guys. I hope you can get CAF & Android M playing together quickly for the OnePlus One.
[ONE Original Android Development] mikecantreed:
Lol what? 1st of all it will take at least a month for the first CM beta to be released for the OPO and second of all when has the release of a new beta version of Android ever stopped development of the previous build? Hint: the answer is never.
[ONE Original Android Development] h2o64:
We are not CM.

And if the M build are bugless we will stop supporting lollipop
[ONE Original Android Development] mikecantreed:
I'm actually in the wrong forum but let's be realistic M is not going to be "daily driver ready" from the start on non-Nexus devices. Therefore its pretty absurd to think there's any chance the next release of any ROM that gets built semi-regularly will be anything other than Lollipop.
[ONE Original Android Development] BBobby:
I don't think you understand what the devs are trying to explain. CAF has great benefits, and they are taking advantage of that 100%. But also, I don't blame you because historically CM has been struggling with eliminating bugs (it took them nearly 2 years to make any camera work). This is pure, unmodified source code that is adapted to the given device. Very different from a wannabe OS

One plus One powered by AOSParadox
[ONE Original Android Development] Thecrazyskull:
As [MENTION=4792450]h2o64[/MENTION] already mentioned, we are directly based off CAF, and as soon as they get their stuff ready (usually 1-2 days after source drop) we can go for it.

The changes from lollipop to marshmallow, are very small when it comes to the device specific trees (kernel, device and vendor).

The only changes are some sepolicy stuff which we can easily adapt in a few hours max, after the source drop.

We arent saying it will be completely bugfree (maybe it will, we will have to see), but im almost 100% sure the first Marshmallow release will be ready to be used as a daily driver :)
[ONE Original Android Development] johnb380:
Lmao over here. Boy I've been on Android since 2008 and I have yet to ever see a first release of a new version to be bug free! Good luck getting Marshmallow on the One+ 1 within days of release. Cuz I can tell you that it took weeks to get Aosp on a supported device aka N4 when lollipop was first pushed out. And the first version was almost unusable to me. I think you guys are hoping for the best but are actually in turn getting alot of people hopes up for no reason and will have a lot of disappointed people to deal with soon!

As always... That's just my 2 cents!

Edit: And just to add a few more points the One+ 1 has been out for over a year now and We still don't have a bug free AOSP ROM for this phone. So how are you guys seriously going to guarantee all these things for an Android version you haven't even seen yet. Maybe you've seen the developer preview but that is it and I can tell you from past experience they hold back a lot of things in the dev preview and the final builds could be so much different in a lot of ways. So I know you guys mean well but let's be realistic here and say We'll see what happens when Marshmallow is released and go from there. Because to me anything other than that is just irresponsible to the whole community friend!

? Good Luck and GOD BLESS!! ?
[ONE Original Android Development] Thecrazyskull:
We never said it will be bugfree, but it will be daily-driver ready ;)

And there is no bug-free one yet, because we just started it :)

People are thinking we will redo device trees, but nope thats not the case we will continue with our current trees and as mentioned earlier, the only changes are some sepolicy stuff which can be done in mere hours.
[ONE Original Android Development] fards:
There was a very good working aosp build of lollipop out for Sony xz within a couple of days of source drop.

So it is possible ?
[ONE Original Android Development] drdrewdown:
Awesome stuff happening on Github right now. Keep up the good work team Paradox
[ONE Original Android Development] miguepereira77:
Edit: Found it! LOL!

https://github.com/AOSParadox
[ONE Original Android Development] drdrewdown:
it's hard to describe how to follow it, just look at the source you'll see the various repo's that have been updated & then look at the proper branch which for us is lollipop_bacon to see the changes
[ONE Original Android Development] drdrewdown:
Almost...

-sent from OnePlus-
[ONE Original Android Development] Silent7x:
F5 F5 F5! I can't wait for this release and you're only teasing us with that screenshot haha. This will be one last flash and then I'll join Flashaholics Anonymous.....until Marshmallow drops :).
[ONE Original Android Development] drdrewdown:
haha it's just a home build after i saw the commits got excited. they don't appear to be functional yet & also AppOps was removed
[ONE Original Android Development] h2o64:
I kind of rushed the latest build wich meant to be the "Wednesday build" (I stayed up all the way up to 2 am). We are nearly done.

---------- Post added at 05:40 AM ---------- Previous post was at 05:39 AM ----------

AppOps was unstable. We really hesitated
[ONE Original Android Development] drdrewdown:
it's all good. i had to start tracking lollipop_bacon instead of the msm8974 repo for packages/apps/settings to get that far with my home build.

i'll be keeping a close eye on github :cool::good::highfive:

[MENTION=4792450]h2o64[/MENTION] <3 https://github.com/AOSParadox/andro...mmit/feb1e119e0dcfe53ff3351996f6355cee6c565aa
[ONE Original Android Development] miguepereira77:
Saw u have french and italian translation for "off screen gestures"... If u need spanish one...I can help... :laugh:
[ONE Original Android Development] Quiche:
We're very sorry that we didn't make it to our deadline (yesterday), but there's good news! [MENTION=4792450]h2o64[/MENTION] has done alot of good work and the new build is being uploaded! [MENTION=5585603]Quasar[/MENTION] and me will test it first, so the build should be presented to you guys in a few hours!
[ONE Original Android Development] kalapapa:
Thanks for all your hard work and dedication
[ONE Original Android Development] johnb380:
Sorry for what? This is YOUR GUYS BUILD that you just so graciously decided to share with us!

We all appreciate all the hard work you and the team have put into this build and project.

Seriously you guys have nothing to apologize for honestly. Thanks again.

? Good Luck and GOD BLESS!! ?
[ONE Original Android Development] xda-amg:
Some issues

First of all, thank you developers for this work. It is a really small ROM with little memory footprint.

I wanted to point out some bugs/issues, neither one major, but just reporting.

I have come from cm11 44s. Clean flash and wiping everything, and even installing every single app, no restore from my backups!

I wanted a truly clean system ;)

1- I noticed that when you dial *#*#4636#*#* and go to service menu,

when you want to select bands, the dropdown list does not populate.

It was previously something like (when I was on CM 11s), Automatic, US bands, Europe bands ...

2- Battery does not charge as fast as before. Previously (CM11s) with OPO charger and cable I could see the reported current (a text file ...) as

-1100 or so, but now it hardly reaches -850 or so. Correspondingly my full charge takes a little more.

I am just wondering that CM kernel has something to detecting the charger and getting more juice out of it?

3- My play store crashes sometimes. I have installed tk gapps nano and then everything from Play Store. It is also automatically updated to new version automatically. Recently I also notices that rarely my Play Newsstand also crashes. Any Idea?

4- status bar quick settings are sometimes unresponsive. when clicking on icons, nothing happens! although the other parts of user interface are fully responsive, just the quick settings.

Just a report on battery life. It is not as great as some users report.

It is just similar to cm11s that I had, around 5 hours SOT, with all my apps installed, no greenfly or what so ever.

BUT, considering that every new version of Android has been more power hungry than its predecessor, keeping SOT in 5.1.1 as 4.4 is very good, IMHO.
[ONE Original Android Development] thenessus:
This ROM sucks.

It makes the user obsessive-compulsive and hit F5 repeatedly and obstaining from using other ROMs. It is absolutely as dangerous as Cocaine.

You should be ashamed of yourselves.
[ONE Original Android Development] drdrewdown:
Having dt2w back is so nice!

Thanks for the efforts to helping bacon continue to live on. (Better than ever)

-sent from OnePlus-
[ONE Original Android Development] unknown1205:
no need to be sorry. what kind of dev apologizes to their users that they couldnt make it on time? i been a long time xda member and this is a first!!
[ONE Original Android Development] xda-amg:
Depends on what you expect from daily driver.

In my case, I did not upgrade from Android 4.4 to 5.0 because even for Nexus devices it was very buggy!

I waited until 5.1 in which most of the bugs were fixed, and there were many happy users.

Moreover, at first that lollipop came, some apps did not work with it. Not to mention the Xposed framework.

That was another reason that I waited for 5.1, because I wanted that, or more specifically. I relied on some modules on that.

I am sure the situation is the same with Android 6.0 (or any new versions of Android in the future).

Obviously it has bugs at first. I prefer to wait until I see that the user feedbacks are positive and seems that major bugs are resolved.

Then, I can say the build is ready as "daily driver".

Of course we can test anything, but I do not want to test them on my daily driver phone. Since I rely on that.

EDIT: sorry guys, I replied to wrong post!

but that is my opinion on Daily Driver.
[ONE Original Android Development] AYEHAN:
i am just curious, if you want a perfect working system then what are you doing at XDA, or even at AosParadox thread ...
[ONE Original Android Development] thenessus:
Or using any mobile device