yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] AYEHAN:
So i made a good decision and slept at my usual time :) now hopefully right when i reach work the first thing i will have to do is reflashing :)

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] TheROMGuy:
This reminds me of the time when I was waiting for the Dev preview of Android L for the nexus devices.
[ONE Original Android Development] WalkingHat:
Is this only for OnePlus one?
[ONE Original Android Development] K900:
Yes.
[ONE Original Android Development] kdb424:
This is the thread for the oneplus-one in the proper forums. I'm sure there will be builds/work done for other devices in their appropriate forums. If you have AOSParadox for your device, then it'll probably follow.
[ONE Original Android Development] xtremez:
I tried this but it doesn't seem to work, did i miss out anything?

Update : Downgraded to TWRP 2.8.6.0 from 2.8.7.0, flashed .241 radio before updating again.
[ONE Original Android Development] CadBuRy.VN:
6.0 6.0 6.0 watting.... :p:p:p:p
[ONE Original Android Development] iamelton:
while not trying to spoil the "fun" many here are having when waiting for a marshmallow release, i would like to ask the devs if a lollipop release fix (in flashable patch format) would still be prepared as mentioned in previous times?

thx..
[ONE Original Android Development] AYEHAN:
+1

OnePlus One Powered By AosParadox 20151001
[ONE Original Android Development] Quasar:
Okay, so finally got around to testing the build, and it doesn't boot unfortunately. We're trying to fix the issue, and further updates will follow.
[ONE Original Android Development] ugvpkn:
Flash the whole firmware and not just the modem; try with TWRP 2.8.6.0.
[ONE Original Android Development] kalapapa:
Thanks for all your hard work
[ONE Original Android Development] ZeRoWaR:
Will the M release be Multirom compatible? :)

Also thanks for everyone involved and the great effort!
[ONE Original Android Development] drdrewdown:
posts like this have to be so damn frustrating for the devs...
[ONE Original Android Development] therohanchawla:
Just pls keep us posted.....
[ONE Original Android Development] aftmkt:
It's okay. Everyone here has to be patient enough.

Goodluck for the test(exam, not ROM test) :P. Hope you do well, it's more important that anything else. Have a good day.
[ONE Original Android Development] xda-amg:
Thank you for all your efforts.

I just wanted to ask you to create a new thread when you were ready to release the 6.0

This thread was originally for 5.1.1, and the last pages are filled with too many posts related to waiting for 6.0!

I think it would be difficult to follow the 6.0 related posts after its release in this thread.
[ONE Original Android Development] kalapapa:
I disagree. I'd rather them just change the title. No point of creating a new thread. It may be based off marshmallow but its still AOSP Paradox
[ONE Original Android Development] xtremez:
Yes i've managed to get it working already! Thanks for the advice.
[ONE Original Android Development] xda-amg:
It may be a little personal preference, but I want to point out to two things.

1- There are threads that, as you mentioned, the title is changed, BUT you have to go through hundreds of pages discussing things that are absolutely irrelevant to the latest build. Not to mention that you have no idea how many pages you have to pass to reach the very first relevant post.

2- Specially, I wanted to emphasis the above problem when it comes to a MAJOR release like moving from 5.x to 6.x.

It is not uncommon for many ROM developers as well as other tool/kernel developers to create a new thread when it comes to MAJOR release.

Anyway, that is just my opinion.
[ONE Original Android Development] ~KV:
Sad to know it didn't boot. Nevertheless, I hope you guys have identified the error and will be able to resolve it soon enough!:)
[ONE Original Android Development] Vekhez:
Would the not booting be due to the "hacks" in order to use the legacy branch? Now that we have the full CAF branch (iirc) would it be better to remove the legacy stuff and use full 8974 CAF, or has this already been done and I just didn't see it for whatever reason?
[ONE Original Android Development] Ofthecats:
This has been done
[ONE Original Android Development] h2o64:
I rebased everything but adreno/sepolicy is a problem.
[ONE Original Android Development] karthi89:
If u need any help regarding sepolicy, contact [MENTION=1050103]sykopompos[/MENTION]
[ONE Original Android Development] h2o64:
Don't worry about me ^^
[ONE Original Android Development] Crazy-Silver:
News? Last change on git were made 4hours ago. I don't ask for ETA. Only wants to know if there are some progress.
[ONE Original Android Development] Quasar:
Everyone's at school.
[ONE Original Android Development] cristianvaz81993:
don´t be stupid and lets work in peace, the do this free and have real life, work or studies, if there are some progress they told us
[ONE Original Android Development] scorpionhd2:
I've been lurking here since the first release, and seriously, all the questions about eta, progress and such are aa PITA. Even if you say "I'm not asking for eta, just asking if there is progress" is the same thing. Its annoying to have to read over 20-30 pages of the same crap! Let the devs work quietly. They will update when they see fit, as they have been doing until now. And no, I don't think they should open a progress thread to keep this one clean. Ots not fair to them to have to worry about that also. That's just asking to open Pandoras Box.
[ONE Original Android Development] h2o64:
And everyone is waiting for it to finish
[ONE Original Android Development] rogisha:
It would be nice to open a new thread in general section...and to keep this thread for troubleshooting and futher development of the future AOSParadox 2.0... We are all waiting for rom and there is too many OT posts...the same OT thing will continue once the build is bootable and ready for everyone who's waiting for it...

;)
[ONE Original Android Development] pSyCh¤_O_O:
Buddy [MENTION=4307328]Crazy-Silver[/MENTION] isn't stupid ...he's hyped...as we all are. I don't think he said anything outrageous that needed you chiming in and calling him stupid.

Also... post complaining about peoples OT are even worse than the actuall OT.... Devs clearly stated its OK for now... the thread will resume to normal behaviour once the hype is over.

Please don't answer to my post...just let the devs do what they do best and enjoy the hype.

Im also excited to see such hype in OPO forums..awesome[emoji6] [emoji106]

#whiteuimustdie
[ONE Original Android Development] TheNakedMam:
Texting while in school? Now, that's not the right way...
[ONE Original Android Development] cristianvaz81993:
I dont say this for him i say in global that in this thread there are a lot of comments about the same...

Only wait and Crazy-Silver that wasn't for you id for the user that comes and comes everyday asking eta
[ONE Original Android Development] Quasar:
Okay. Made a separate Q&A and banter thread. Now please use that or you'll have dreams of aardvarks in medieval chain mail wearing Ray Bans.

Here's the thread : http://xdaforums.com/oneplus-one/general/5-1-1-aosparadox-qa-banter-false-etas-t3224400

My, what a wonderful 2000th post!
[ONE Original Android Development] Maxoobidou:
Isn't msm8974 our beloved snapdragon 801 ?

CAF finished the update ?

I can't post link, but under QAEP and release, it seems like our device just got updated.
[ONE Original Android Development] K900:
It's been there for over a day now, and it's already been integrated into the code. There are other issues left to sort out now.
[ONE Original Android Development] Quasar:
Well, our glorious savior [MENTION=4792450]h2o64[/MENTION] has done it again! Apparently he's found out what's wrong with Bacon.
[ONE Original Android Development] therohanchawla:
This guy ought to get some donations... I would have by now... But i am a student my self....

I am running out of words of appreciation for you devs....
[ONE Original Android Development] K900:
[MENTION=5585603]Quasar[/MENTION] / [MENTION=4792450]h2o64[/MENTION]: do you guys need any help with bringup/testing? I can probably help out.
[ONE Original Android Development] RajRockyBalboa:
http://androiding.how/download-oneplus-one-marshmallow-rom/

I cant find it...

WTF ???
[ONE Original Android Development] iamelton:
just in case my previous one was overlooked by the devs in the sea of hyped posts.. thx..
[ONE Original Android Development] K900:
This is a 5.1.1 build, not 6.0. There is no functional 6.0-based build out there yet.
[ONE Original Android Development] jukiewalsh:
I don't remember ever reading that, someone stated that we had probably gotten our last LP build and they moved on to marshmallow
[ONE Original Android Development] hasnol143:
That whole article is a lie, I don't think they did the proper research.
[ONE Original Android Development] RajRockyBalboa:
True mate. Crazy people. Though waiting (im)patiently for the marshmallow build ;)
[ONE Original Android Development] rhandyrhoads:
[MENTION=4792450]h2o64[/MENTION] Hey, I am aware that the ROM is currently non-functional, but I am looking to try building it from source for the experience and the ability to be able to build any future revisions. I was wondering what your build environment is software-wise (OS, installed packages, any tweaks, etc...) Last night I threw Ubuntu 15.04 on a spare SSD and I tried building a couple times and the first few times I got an error after half an hour or so and after making some modifications (after each failure I would search up the error if easily visible/searchable and try to troubleshoot it) it failed within 2 minutes. Someone tell me if this is the wrong thread.

EDIT: Screwed up the name.
[ONE Original Android Development] iamelton:
check [MENTION=5585603]Quasar[/MENTION]'s post.. :D

http://xdaforums.com/showpost.php?p=63113645&postcount=913
[ONE Original Android Development] jukiewalsh:
Follow this guide,

http://xdaforums.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410

However the rom currently won't build from source until he pushes local fixes that he made. I've been trying to fix my own errors since yesterday but every time a new one pops up.
[ONE Original Android Development] johnb380:
Its the right thread but the wrong time friend. They are trying to get a bootable 6.0 Rom sorted right now. So I'd say to wait a few days until things calm down and you'll get some help then.
[ONE Original Android Development] h2o64:
A clear and understandable guide is linked on the OP
[ONE Original Android Development] jukiewalsh:
Oh I missed that, my apologies
[ONE Original Android Development] rhandyrhoads:
Followed that guide word-for-word minus the part replacing devicename with bacon obviously. Don't bother replying if you're too busy but I know that sometimes newer versions of an OS may act a bit weird with stuff like this so I was just wondering what your setup was.
[ONE Original Android Development] Quasar:
I build on Ubuntu 15.04 and it works alright for me
[ONE Original Android Development] rhandyrhoads:
Alright, thanks. I'm going to try a fresh install and using part of that guide someone else posted. Just out of curiosity, why do you recommend make -j8 otapackage? That guide states that it should be j(num of CPU cores +1). My CPU is an i5-3570K so under this rule it should be make -j5 otapackage right?
[ONE Original Android Development] Quasar:
Yeah. Stick to -j5.
[ONE Original Android Development] kdb424:
Depending on RAM usage, I've personally experienced on non hyperthreaded CPU's it's j = (Cores + .25). On an Intel with hyperthreading, you should run with j = thread count. So you'd want to run -j5 though on my 2500k I was able to still gain some small speed with -j6 on certain tasks. Don't expect a responsive machine at all when compiling. This comes from years of running Gentoo Linux where every single thing is compiled from source with experience on Intel and AMD platforms. When in doubt, run a benchmark. BTW, -j is just parallel threads, in case you don't know, though I'll assume that you do. As for why you run more than cores, it's to make use of wasted clock cycles, not exactly like hyperthreading does it, but pseudo similar.
[ONE Original Android Development] K900:
The real reason for the (CPU cores + 1) rule is that we assume that one thread will be blocked on I/O. So while that thread is doing I/O (which isn't too expensive), we still have a compilation task for every core.
[ONE Original Android Development] rhandyrhoads:
I have 16 gigs of RAM so I'm assuming that CPU will be the bottleneck.

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

Alright, thanks for answering my questions.
[ONE Original Android Development] aosp:
[MENTION=4792450]h2o64[/MENTION] Have you tried the newer bacon vendor blobs from the 5.1.1 h2os caf based builds?

https://drive.google.com/folder/d/0B60Mii9V3x83bDlsQzRQSExOejA/edit
[ONE Original Android Development] Quasar:
I don't think they would make a difference since we need new adreno blobs because Google modified boringssl, but there are a few hacks with which older blobs can be booted as well, so we're trying that out at the moment.
[ONE Original Android Development] K900:
Not sure if you're aware that this exists. Just compile and export LD_PRELOAD=/system/lib/libboringssl-compat.so in the ramdisk.

Edit: This may also be relevant, but it's probably better to postpone that until it boots.
[ONE Original Android Development] Quasar:
Yep. That's exactly what we're looking at ;)
[ONE Original Android Development] K900:
Do you guys have an IRC channel or something? I can't promise I'll be useful, because I'm feeling sick as hell, but I'd love to hang out and talk at least.
[ONE Original Android Development] Quasar:
We chat on Hangouts. PM your GMail ID.
[ONE Original Android Development] urcindalo:
(please excuse the off topic)

Oh! What a surprise! On January I'll have been using Gentoo Linux for 11 years! :highfive: Best OS ever :D

However, I've never tried to compile an Android ROM. Do you compile Android on Gentoo? Might I contact you privately in the future to know the details if you do?

I take the opportunity to thank the developers of this amazing ROM for their efforts, kindness and nice work.
[ONE Original Android Development] aosp:
boringSSL: restore EVP symbols needed for Qualcomm camera blobs

https://github.com/xboxfanj/external_boringssl/commit/d2a2e0921aa25d118a6567e9ba67b3553bb1e573
[ONE Original Android Development] K900:
I like the wrapper option way more, personally.
[ONE Original Android Development] kdb424:
I'm actually not a full on ROM dev. I have done some kernel hacking a few years back for android, but never bothered to compile a full rom. I've actually recently retired my desktop completely to give an experiment a shot. I'm running only on Android devices completely right now. I'm typing this on a Shield TV (Full android rom, not ATV), have a Transformer that I use as a laptop, and 2 android phones. Eventually I'll get a server up again for the rare time I can't do something in android, but I'm also using Arch Linux chroots on the shield TV for smaller things. I'd run Gentoo, but the compile times compared to my desktop would be terrifying. I'll probably run the server on Gentoo for misc tasks that need more grunt and media serving. Here I go getting off topic again in the thread that I keep trying to not be. *sigh*
[ONE Original Android Development] pcarenza:
I will definitely be bookmarking this! Great job in breaking ground for our bacon devices!
[ONE Original Android Development] Pank9j:
Waiting for Android M build. Thanks Guys for the great work.
[ONE Original Android Development] Aaahh:
Why didn't anyone tag me? *sigh*

Like I did this for the previews, and I'm working on the final, how far are you guys?

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

Mind sending that to me?
[ONE Original Android Development] 1asbak1:
Did anybody in here even slept for one minute the past 72 hours?! You guys seem to be some kind of superDEVheros!
[ONE Original Android Development] therohanchawla:
Welcome mate...... I am so sorry/sad that nobody taged you.... Cause we might have achived M a little earlier......

Late is better than never mate... Welcome to the party..... I hope all the efforts bear fruits and we have M soon....
[ONE Original Android Development] Aaahh:
Lol, I was playing about being mad...

I stop the last two days and tried cm13, but I went back to aosp, cm13 is too broken, none of the real caf is there. I went back to aosp, and working on that.

[MENTION=5585603]Quasar[/MENTION] can you add me to the hangouts? woohoomoo2u@gmail.com
[ONE Original Android Development] h2o64:
Happy to see you here ☺
[ONE Original Android Development] bobglaus:
If you guys wanna add me to your hangouts that would be cool. Im working with the other dev on radonx and I've been playing around with it for a few days after I found it didn't boot. I'd just like to see whats going on to see if I can't contribute or implement it into radonx which is based on aosp Paradox. Thanks ethanbanker2428@gmail.com
[ONE Original Android Development] h2o64:
What if I tell you that RadonX devs or old paradox devs ^^ we know them don't worry :P And we might work together if necessary
[ONE Original Android Development] bobglaus:
Huh that's pretty cool. I didn't know that. I just started working on radonx with him but I haven't been very active as I have school and I need to reinstall linux as my current version is messed up bad. Thanks guys you get m figured out so I can help work on a radonx version
[ONE Original Android Development] TheROMGuy:
The last commit on github was 34 minutes ago. It was vendorsetup.sh. hopefully getting somewhere soon. B)
[ONE Original Android Development] Mkkt Bkkt:
I hope its coming really soon because I really can't wait more :'(.

I appreciate your work guys <3
[ONE Original Android Development] :
Please read OP and respect the devs. These kind of posts are annoying.

FOR Q&A, BANTER AND ANY SORT OF ETA ASKING/TELLING US STUFF WE ALREADY KNOW/ANYTHING OTHER THAN BUG REPORTS OR ANY OTHER SERIOUS DEVELOPMENT RELATED STUFF, FOLLOW THIS LINK TO THE Q&A/OFF TOPIC THREAD K?​
[ONE Original Android Development] Adrian312:
Hi guys,

I am thinking to move from Euphoria to this ROM, really want to have CAF supporting rom. No problems with using AK kernel (CAF version) with this ROM? Also, maybe wrong thread, but do you think that Xposed will NOT be supporting Marshmallow from Day1? like it was with Lollipop before.

Thanks for answers
[ONE Original Android Development] phanitej:
I don't think you can flash ak kernel over this Rom. I have not tried the latest version, edit: don't really think it has the ak kernel compatible. Kat time I used this Rom was with egg kernel

Regarding marshmallow, I don't think xposed will be ready as rovo's version is still not completely compatible with many versions of lollipop. May be some other developer like romracer might get a tweaked version soon.

Edit: I'm probably behind the updates on xposed [emoji16] , the post below gives link to the update on xposed for 5.1.1

To be honest, I've just been following this thread since few days as everyone who is waiting for Android m for our beloved bacon

Sent from Nowhere
[ONE Original Android Development] kdb424:
To answer xposed http://xdaforums.com/showpost.php?p=63188361&postcount=21

And no, ak kernel will not work on this rom. No other kernels will work on this rom in fact. The one built into the rom is from the same base that AK uses, so unless you need something specific in AK, it should serve you very well. The boot.img (If I recall correctly) is changed. If you read the entire first post, the details are in there about no other kernels working with this rom.
[ONE Original Android Development] jukiewalsh:
No AK compatibility. no exposed for marshmallow yet, I don't think you understand how it works go read the xposed thread
[ONE Original Android Development] xtremez:
If I may input on the AK kernel situation, i did actually try flashing the CAF based kernel and it would work. However, in terms of compatibility i think use Egg that seems to be the recommended for this ROM.
[ONE Original Android Development] jukiewalsh:
No, eventhough it flashes AK kernel won't have Wi-Fi working with this ROM. Egg kernel is compatible though
[ONE Original Android Development] xtremez:
Alright, didn't really take note of that. thanks for the heads up
[ONE Original Android Development] Semper80:
I find it funny that we mention Xposed, custom kernel, etc given that Android 6.0 (original or custom) has not yet been released for other devices than Nexus.
[ONE Original Android Development] jukiewalsh:
We were taking about the current 5.1 version of the ROM
[ONE Original Android Development] Mkkt Bkkt:
I didn't asked for ETA , read again my comment.

I was only expressing my feeling about marshmallow updates (over hyped).
[ONE Original Android Development] Enddo:
"other than bug reports or any other serious development related stuff"
[ONE Original Android Development] kdb424:
Moto G 2013 has AOSParadox booted on it, so not true.

As this person stated, this is the thread for 1.0

As a reminder, any discussion for 2.0 (AKA Marshmallow) is in this thread. http://xdaforums.com/oneplus-one/ge...banter-false-etas-t3224400/page3#post63301296
[ONE Original Android Development] jukiewalsh:
Your comment qualified as "banter or "stuff we already know"

Everyone's excited about getting 6.0, move the hype to the off topic thread. There's been so much off topic posts about 6.0 here that the devs had to move to alternate chat forms to get some development done. If everyone just sat back and read we could see the development progress first hand if they were maybe able to use their own thread.
[ONE Original Android Development] Quasar:
Great to see you guys take the OP so seriously ;)
[ONE Original Android Development] therohanchawla:
Also Moto g (FALCON) Already boots M --> http://xdaforums.com/showpost.php?p=63301388&postcount=212

kudous to [MENTION=4792450]h2o64[/MENTION]....

These guys rock...Period ......

Just give them a couple days .......Hopefully less :D
[ONE Original Android Development] Cybertron™:
Ohhh nice
[ONE Original Android Development] jackeagle:
Mod Edit

Thread Cleaned.

Members all this drama ends here. follow the wishes of developers and stop asking ETA's or any such discussion. everything takes time and developers know when to release and all stuffs hence all such eta discussions ends here. be polite and respectful to all members here. have any issue just report and move on. no need to reply to it and flame on it.
[ONE Original Android Development] HARRINGT0N:
Can anyone confirm that they've gotten the capacitive buttons on the OnePlus to turn off with this ROM? I've installed Gravity Box and enabled soft keys but everything I've tried to keep the hard keys from lighting up hasn't worked. I've gotten them to stop working, but the lights still won't shut off.
[ONE Original Android Development] Aaahh:
LOL, yeah I had that problem with my port of the preview, pretty much I think they rely on cyanogenmod hardware jar which wasn't included for obvious reasons. Cyanogenmod seems to be doing something that'll make it easier to pull in changes, and similarly, switch to AOSP
[ONE Original Android Development] tekanina:
There's a guide in the OP. But instead of changing the brightness to 0 and changing permissions Change max brightness to 0 makes it a little easier. Also using es file explorer I bookmarked that folder to make it easier as it has to be done on every reboot.
[ONE Original Android Development] kdb424:
You could probably script it to run on boot with init.d support.
[ONE Original Android Development] tekanina:
Thanks. I'll have to look into it. I haven't done anything with scripts since the Galaxy S2 was still relevant.