yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] iamelton:
coming from OxygenOS and just installed the ROM..

first impression is quite nice, and will see how it goes..

a minor issue to report here..

in "Developer options", the option "OEM unlocking" is turned off and could not be turned on..

it doesnt matter much as my bootloader is unlocked (obviously), but not sure if that option still has any impact..
[ONE Original Android Development] Kattiq:
WHAT is the point of network activity arrows?! You make a minimal AOSP rom and you put NETWORK ACTIVITY ARROWS arghhhh I hate them so much they are absolutely pointless. Like seriously tho, they are ugly and pointless. Please remove them completely. Other then that, nice rom.
[ONE Original Android Development] Thecrazyskull:
Already done ;)

They will be gone next build :)
[ONE Original Android Development] ZenR2:
Eagerly waiting for the next build :)
[ONE Original Android Development] h2o64:
Calm down ^^ it's just a caf thing ^^ we didn't added it
[ONE Original Android Development] szaf:
When i go to mobile networks and try to change the preferred network type i get the message process com.android.phone has stopped.The weird thing is that this happens when i use the greek language-i am greek.If i use the english language everything works fine.
[ONE Original Android Development] h2o64:
Oh..

I must have forgot a translatable=false somewhere in overlay
[ONE Original Android Development] TheBKBurger:
Great ROM! Issues I am having:

- Some apps cannot be expanded on lockscreen

- 3G =/= LTE in US

- Google Messenger app doesn't show anything, but stock messenger shows sms threads

Once fixed, I will reflash! Eagerly awaiting! :D
[ONE Original Android Development] h2o64:
We are trying to fix locksceeen. 3G isn't a bug. It's the normal behavior, but seeing how much people complain, we changed it.

Try cache wipe or clean flash because the app should work as expected
[ONE Original Android Development] klassical:
Beautiful result, boys! And it is not even a final version of ROM and CAF kernel.
[ONE Original Android Development] aosp:
[MENTION=5585603]Quasar[/MENTION] [MENTION=4792450]h2o64[/MENTION]

Congrats on a true minimal stock AOSP ROM for the bacon ;)

Any plans for full layers support in the future?

https://github.com/The-Ancile-Project/platform_manifest/blob/frank-mutant-test-1/README.md

https://github.com/MinimalOS/androi...mmit/8681610df588647bdfa464b316895d33f78c3f9e
[ONE Original Android Development] tmimaesk:
just wondering if this helps with wifi hotspot being broken..

https://github.com/sultanxda/androi...mmit/5f1a455aae779421c68a570964e7ee6f0d53f0c6

it was broken from sultan's but he fixed it months ago..
[ONE Original Android Development] _ASSASSIN_:
Because they don't cause crashes, nor are they major...
[ONE Original Android Development] sonjaya:
It's Beta.. Read post #1 I

It's Beta.. Read post #1
[ONE Original Android Development] Meuuks13:
Nfc, hardware keys aren't major?

And just because a ROM doesn't crash doesn't mean it is stable. I can have a ROM with a broken wifi, bt, mobile radio and just because it won't crash won't make it stable

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

See the name in downloads
[ONE Original Android Development] aukdrck:
Not having double tap to wake kills it for me. Otherwise a great ROM. Incredibly smooth.
[ONE Original Android Development] deepaklunked:
This is just the beginning. Have patience if you want a stable build. Don't fill up the thread with posts that might frustrate the devs. As mentioned, it is still a beta.

And yea, if you can build a ROM like you mentioned, then very well. Go with it.
[ONE Original Android Development] Meuuks13:
I pointed out that its not fair to label something as stable when it's not. I never criticised the build or the dev, you are entitled to your interpretation. For filling up the thread, I don't think commenting about a ROM when the thread is about the ROM is filling it up, but again you are entitled to your interpretation.

Also you really need to understand case in point examples but then again I'm entitled to my interpretation of you
[ONE Original Android Development] h2o64:
Sorry. It's just a typo in our building script. Will be fixed asap.

However the whole rom is working like a charm. You can experience everything like in other ROMs. They are just little graphic glitches (3G, backlight). And wifi is 100% working.
[ONE Original Android Development] Quasar:
The 3G icon is a CAF thing, because technically LTE is still 3G. The gapps error must be something on the gapps side.

Well, to be fair, NFC is the only "dealbreaker". Hardware button lights wouldn't count as major. Everyone knows where their buttons are ;) though yes. We forgot to change the build type in the source. Anyway, the next build should be stable, so shouldn't be an issue.
[ONE Original Android Development] Meuuks13:
I am already using the ROM.... Its not doubt great... I was just pointing that out..

---------- Post added at 05:37 AM ---------- Previous post was at 05:31 AM ----------

Yup agreed... Also I really hope you fix hardware mapping
[ONE Original Android Development] Quasar:
Hardware mapping is more of a feature..... though we're looking to add our own implementation of the feature soon. You could modify the generic.kl in system/usr to edit hardware key actions. I might make a flashable zip with various functions if it's that much in demand.
[ONE Original Android Development] aukdrck:
Please add double tap to wake feature too if you can. This is the only thing missing for me to make this My all time favorite. Thanks a lot for your hard work.
[ONE Original Android Development] S1611:
Please take your time. As of me I switched back to Euphoria because I use hardware button s and was not able to use recent apps switcher and screen color adjustment, its too blue for me. Kudos to the developers:)
[ONE Original Android Development] Quasar:
You can edit the generic.kl in /system/usr to change the hardware button mapping as a rough fix. And this ROM has KCAL, so you can tweak your screen using savoca's app or kernel adiutor or any other kernel tweaking app. By default, the recent apps switcher is lon pressing the home button.

Will look into that.
[ONE Original Android Development] S1611:
When I was trying to install camera next apk it asked where to install it? Is it a standard feature of this ROM?
[ONE Original Android Development] Quasar:
Yep. A CAF thing.
[ONE Original Android Development] S1611:
So which option should I choose?
[ONE Original Android Development] Quasar:
"Let the system decide"
[ONE Original Android Development] S1611:
Looking forward to you work man, appreciate your work.:)
[ONE Original Android Development] :
This rom is a beauty... I hope you can implement the double tap to wake
[ONE Original Android Development] mucinch:
This ROM is scorching fast, there is no hesitation whatsoever, every thing responds immediately. Thank you for bringing it to OPO and as [MENTION=4484316]ianstump[/MENTION] said the only thing missing is Double tap to wake.

Since we don't have any custom kernels, can you provide a zip to disable the CPU underclocking?
[ONE Original Android Development] BBobby:
If I remember correct from previous posts, someone else asked this same question. They are not planning to add layers.

One plus One powered by AOSParadox
[ONE Original Android Development] kalapapa:
Yup they won't

http://xdaforums.com/showthread.php?p=62709079
[ONE Original Android Development] Kryspy:
Hi,

Super fast ROM. Great battery.

1. MMS is not working for me on current build. Using Google Messenger. Deleted all APN and added mine by hand. Still no go. Built in messenger and Hangouts works fine.

2. Bluetooth audio in my car does not show metadata the same as Oxygenos doesn't.

Kryspy
[ONE Original Android Development] kalapapa:
Absolutely love this ROM. Thanks to devs for allowing this to happen. Can't wait for the next build
[ONE Original Android Development] h2o64:
No plans for layers. They will be added in 6.0 anyway

We fixed it already on our incoming build

NB: I know we are talking about the next build since a few days. But we are trying to release the most stable build possible, with the least amount of bugs. So please apologize the delay ?

Can you provide any logs?
[ONE Original Android Development] abhi4328:
NO! Don't apologize ! You don't owe the people anything! and about the delay? pffff we aren't going anywhere! Take your own good time.
[ONE Original Android Development] BBobby:
That's right. I expected that when you said you uploaded the ROM for testing it would be a few days. Thank you for always promptly responding and giving us updates. We are loyal

One plus One powered by AOSParadox
[ONE Original Android Development] tmotard:
No problem with BT &metadata here.
[ONE Original Android Development] AYEHAN:
its just me i guess, i have no issues with the ROM, no location icon in statusbar no sms mms issue with any of the app i tried, stock google or even textra

no camera issues

i just have a little issue tough .. no battery life like you guys .. it was maxed out at 5hours SOT and in total 17hours Run time

and after [MENTION=6389733]darshan_dex[/MENTION] advised xposed and powernap right now am at 1d3h and 2.5h SOT but again in this charge didnt used the phone much, most of the time idle
[ONE Original Android Development] h2o64:
Bug reported. Thank you.

(lol)
[ONE Original Android Development] AYEHAN:
so as i like this ROM alot ... if any Dev wants a Invite to OnePlus2 let me know else first PM gets the OnePlus2 Invite (Just 1 invite)

[MENTION=5585603]Quasar[/MENTION] [MENTION=4792450]h2o64[/MENTION]

Invite Gone ..
[ONE Original Android Development] adinkwok:
Another dev has already forked their sources and has started implementing layers. Once it is done and working well, he will make pull requests to (hopefully) merge it in!
[ONE Original Android Development] tropenfrucht:
Same for me on german language, didn't try with english. Swichting network mode with Intelli3G (xposed module) works without problems.
[ONE Original Android Development] ~KV:
[MENTION=5585603]Quasar[/MENTION] [MENTION=4792450]h2o64[/MENTION]

Are the stock kernel settings tuned for the best battery life?

Stock governor is interactive and I/O scheduler is deadline...

If not what is the best combo for battery life?

Thanks.
[ONE Original Android Development] TheBrooster:
First off great ROM. I have been running it for a few days now and have just noticed that my 64GB device is only showing 16GB storage. Is this a partitioning issue?
[ONE Original Android Development] fmc000:
I'm thinking to try the next version but I'd like to know first if the compass works on this ROM, unlike CM12.1, and if there are any problems with GPS. Thanks in advance and kudos to the devs.
[ONE Original Android Development] thenessus:
I come from a nexus 5. The N5 has a lot of pure and minimal AOSP ROMs (Chroma best of them all). I was very disappointed to see that there are literally NO AOSP ROMs available for the OnePlus which are reliable and minimal (BrokenOS is bloat, for example).

I am very excited about this project, and eagerly await new builds. Kudos.
[ONE Original Android Development] premkang:
First of all, this is a terrific ROM but I have to say that no metadata on my VW either.
[ONE Original Android Development] Kattiq:
Awesome!
[ONE Original Android Development] BBobby:
64 GB here. Weird

One plus One powered by AOSParadox
[ONE Original Android Development] Kryspy:
[MENTION=4792450]h2o64[/MENTION]

I don't have any logs. I am one of those useless people that just went back to a previous ROM from backup LOL. No metadata was a problem with oxygenos as well. Kia Sprtage here.

Kryspy
[ONE Original Android Development] fmc000:
OK, the only bug related to GPS seems to be the persistence of the notification icon but there are no mentions of the compass withing the whole thread. Anyone can help me on this? No one use it?

Thanks again.
[ONE Original Android Development] Quasar:
No issues here.
[ONE Original Android Development] fmc000:
Many thanks!
[ONE Original Android Development] RoSk0BoSk0:
Greetings again! I banged my head a bit to figure out why does stock tk gapps don't install properly. Sounded error 70, that is designated as not sufficient space in /system partition. From all I've seen this partition is 1.3G stock, but suddenly it has shrunk to 1G after installing AOSParadox. After some reading here's the fix:

- You need TWRP 2.8.7.0, may be installed temporary if you want to be on 2.8.6.0 for proper firmware flash;

- Boot in recovery and perform a clean install;

- Go to Wipe>Advanced Wipe;

- Check /system partition and "Repair or Change File System";

- Pres the resize button and swipe to confirm;

- Now go back and install TK Stock gapps as usual.

*If you want you can now revert back to TWRP 2.8.6.0

Off Topic: This should also fix problems with flashing wrong userdata images, but respectively you'll need to select different partition.
[ONE Original Android Development] TheNakedMam:
Next update?

Not requesting one, rather asking wether will it be soon?
[ONE Original Android Development] David:
just wait .
[ONE Original Android Development] h2o64:
My bad. I know why.
[ONE Original Android Development] KenjiHannya:
[MENTION=5585603]Quasar[/MENTION] Disable CPU Underclock by Sultan flash that will work?

http://xdaforums.com/devdb/project/dl/?id=12808
[ONE Original Android Development] tmotard:
http://xdaforums.com/showthread.php?p=62704325
[ONE Original Android Development] miorli:
Got the same "issue". GPS icon doesn't disappear. No drain or battery usage, however.

I noticed another issue today. My mobile provider warned me that I've used up my whole traffic for this month. Pretty surprised I checked my usage and found that my browser (AOSP) used up 660 MB of data since I flashed AOSParadox on Saturday evening. I browse a lot, but I'm basically in range of some Wi-Fi all the time. The only time I've spent browsing without Wi-Fi were 60 minutes in the train and 30 minutes in the bus. Moreover the data usage log stated that 350 MB of those 660 MB were used in the background. But I only allow background preloading of links when on Wi-Fi. I'm sorry that I can't help more with this and maybe it's an user related issue, but I really can't explain how on earth I've used up 660 MB of data volume in less than 2 hours. Unfortunately I can't related this to anything in this ROM, but maybe some other people had similar issues. I've also got 80 MB of background traffic from Google Play Store despite having automatic updates only enabled by Wi-Fi. Would it be possible that there could be a bug that chooses mobile data over Wi-Fi despite both being available?
[ONE Original Android Development] fmc000:
Another couple of questions: on CM12.1 I use the CameraNext app because it doesn't have the "split image" bug when shooting with the flash on. I understand that this ROM uses OxygenOS camera. How is it? Does it work well? Any bugs to report?

Second: does this ROM support notification lights with different colors or is this a CM feature not present in AOSP?

Again, thanks in advance.
[ONE Original Android Development] KenjiHannya:
Thanks ✌
[ONE Original Android Development] Quiche:
This is indeed the flashable zip used to disable the default underclock.

It should make the CPU boost to 2.5GHz again.
[ONE Original Android Development] KenjiHannya:
I tried installing with TYR Kernel but not accessed wi fi. Why not enter? I wanted to use TYR Kernel and UKM in this wonderful room. Congratulations to the developers

---------- Post added at 08:44 PM ---------- Previous post was at 08:35 PM ----------

@fmc000 flash this zip, câmera Qualcomm for CAF Rooms. The best câmera for OPO

https://drive.google.com/file/d/0B6niOIsZY1vKenZUYzdzODdZVms/view?usp=docslist_api
[ONE Original Android Development] drdrewdown:
it doesn't use the O2OS Camera, it's using the libraries (libs) you can install/use any camera app you want

notification light options are not present in this ROM
[ONE Original Android Development] taufiqs:
it is lolipop feature. try use mobile radio pwn app.
[ONE Original Android Development] kalapapa:
Custom kernels don't really work properly with this ROM so stock with stock
[ONE Original Android Development] KenjiHannya:
?????

Thanks ✌??
[ONE Original Android Development] h2o64:
AOSP set white only for every notification type. So we stay with that :)

(I recon that custom led should become an AOSP thing BUT it can be very hardware specific at some point so it's complicated)
[ONE Original Android Development] Nalin12:
This is the first true aosp rom that is just perfect especially in gaming performance.

I am so happy to see that this rom does not have gaming lag of other roms especially cyanogen based ones. Also this is by far the smoothest rom that i have tried after oxygen os, it's that good.

My advise is to keep the aosp nature of this rom alive by not adding all the unnecessary cyanogen features in upcoming versions.

PS : These Wi-Fi arrows are just spoiling the fun, maybe it should be removed.
[ONE Original Android Development] klassical:
In the next build, ... developers already fixed it.
[ONE Original Android Development] aosp:
[MENTION=4792450]h2o64[/MENTION] Could you fix bug reporting in the next build please?

find7op: Use dumpstate directly for bugreports.

Use new broadcast flag on dumpstate to notify framework when a

bugreport finished. Remove older shell scripts.

https://github.com/sultanxda/androi...mmit/952dad5e50f1109cb809a8718c34c91a4b5e93cb

Also enabling local terminal in dev options doesn't work terminal app crashes on launch
[ONE Original Android Development] h2o64:
Alright
[ONE Original Android Development] fmc000:
It doesn't work on CM12.1, only takes pictures in HDR mode. Moreover, panorama mode crashes. Does it behave the same on AOSP?
[ONE Original Android Development] f.us:
Hi,

love how dedicated you work.

I'll give this a try as soon as the speakerphone bug is fixed.

Regarding bugs: is it possible to collect the reported and verified issues/bugs in the op (or somewhere for that matter)?

Right now, it just states the network arrows.

That's probably too much to ask though. But you might already have a list of some kind to keep track of them.

Keep up the great work.
[ONE Original Android Development] Quasar:
We have made a list locally. We'll fix the bugs as soon as we get some time (usually weekends) since we're juggling development along with school/college.
[ONE Original Android Development] thenessus:
Hey, can I ask for a small feature that is not implemented on any ROM?

Actually it is but only on OxygenOS.

If you eventually add modified battery icons, please add battery percent, but that the percent text is the same font size as the clock. Currently on all other ROMs the battery percent is tiny compared to the clock, which I find ugly and inconsistent.

Here is how it looks on OxygenOS:
[ONE Original Android Development] h2o64:
I noticed that but never tried to fix it. I'll check
[ONE Original Android Development] spanish33:
I got speaker mode working by changing system/build.prop

Change "persist.audio.fluence.speaker=true" to "persist.audio.fluence.speaker=false"

Source http://xdaforums.com/oneplus-one/development/fix-low-mic-call-t3055661
[ONE Original Android Development] fmc000:
The panorama crash is simple, the zip that was attached in this thread lacks a couple of libs ,

libjni_snapcammosaic.so

libjni_snapcamtinyplanet.so
[ONE Original Android Development] h2o64:
Thank you ☺
[ONE Original Android Development] Hetalk:
You cannot. It has to be implemented in the kernel.
[ONE Original Android Development] Hetalk:
Exactly. I meant it has to be implemented/fixed on the kernel side. GravityBox cannot add that feature.

Edit: I'm sure you guys are on it. Take your time. No hurry. Right now, it's pretty good for a 2nd build and a daily driver.
[ONE Original Android Development] Auriental:
Let's take a moment.

Hey guys,

Can we all take a moment and appreciate how much the devs have done for us. It really impresses me how almost everything we requested, is already being implemented in the next build. From DT2W, Wifi arrows, nav bar to more and more optimisations, making this ROM to be one of the best, clean, AOSP ROM out there. Guys, lets honestly take a moment for this two super devs,

[MENTION=5585603]Quasar[/MENTION] & [MENTION=4792450]h2o64[/MENTION] , one from South Asia & the other from Europe, being in different parts of the globe doesn't stop them from creating a wonder. I'm taken back by their work. I'm an AOSParadox user from the first build to the second, and man i've not seen a new ROM performing this well. From Samsung Galaxy 2 to all the other 8 android devices i've owned in the recent years, i've been a power user, and always have been on a custom roms. But i've

NEVER

came across a newly developed ROM performing as well as AOSParadox. Surely there have been many cosmetic glitches, but performance wise its superb. Battery life is amazing. Stability is rock solid. And that matters most than the minor errors. Kudos to this team. You guys are unsung heroes, that are soon to be legends in the AOSP custom roms community. Mark my words guys, AOSParadox will always be known as THE AOSP ROM in the coming years. I'd like to end my post with a big THANK YOU to the team behind this beautiful project, and all the wonderful supporters , users, contributors. Looking forward to the next release. #RESPECT.
[ONE Original Android Development] golden_life0807:
:( :( HELP !! BLUETOOTH BUTTONS NOT WORKING WHEN SCREEN OFF ONLY WORKS WHEN THE SCREEN IS AWAKE :( :(

Hi,

can someone help me i have been using OPO for the past 9 months and the only reason i didn't upgrade to Lollipop is because i am facing this strange problem even when i flash this ROM my Bluetooth headset buttons are not working.

they only work when in the screen is ON so i cant use the PLAY/PAUSE,SKIP buttons when in the screen turns off.

this is the only main reason i keep reverting back to cm 11s .

I really love this ROM its smooth,fast and i didn't have to look for wake-locks and even the battery life is the best i have seen since day one.

Is there a workaround for the Bluetooth issue because i am a frequent traveller so this is becoming a problem for me.

Thanks :) :)
[ONE Original Android Development] KenjiHannya:
In panorama mode does not work either. Moreover everything works.
[ONE Original Android Development] TheBrooster:
Might reflash to see if that fixes it.

Anyone else experiencing the same issue as me? That being a 64GB device only having 16GB after flash?
[ONE Original Android Development] h2o64:
It's a reported bug
[ONE Original Android Development] AYEHAN:
Not me atleast ... Still 64/GB :)

OnePlus One @ AosParadoX 20150911
[ONE Original Android Development] fmc000:
I fixed the panorama bug adding the required libs, still I can't understand why on CM12.1 only HDR pictures work.
[ONE Original Android Development] jukiewalsh:
Loving the ROM, so smooth. Many thanks to the devs!

Sent from my A0001
[ONE Original Android Development] Gapkobob:
Guys is it only me? Or amplify actually does not work on this ROM?
[ONE Original Android Development] AYEHAN:
[MENTION=6104683]Gapkobob[/MENTION] i didnt see it working too , tough its my first time using xposed no idea how to verify if amplify works or not

OnePlus One @ AosParadoX 20150911
[ONE Original Android Development] RoSk0BoSk0:
If you get stuck at starting it. It's a SE Policy conflict with amplify, it works fine but get some strange behavior at initialization.

Here's a quick fix:

1. Install and activate as usual;

2. When you run it for the first time and get stuck just swipe from the left side of screen and go to alarms;

3. Press the back button for the next step;

4. Repeat to complete the processes;

5. Profit.

:)
[ONE Original Android Development] AYEHAN:
P.S : or maybe all the things are already covered by the great devs that Amplify cares for

OnePlus One @ AosParadoX 20150911
[ONE Original Android Development] AYEHAN:
Didnt worked for me :/

OnePlus One @ AosParadoX 20150911