yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Parisaurus:
Atm i'm in OmniRom 6.0.1, not sure if the change worths... How much sot with 1.7 - 1-9 cpu?
[ONE Original Android Development] aclup3:
hi guys, can anyone tell me how's 28/11 rom, on the beta folder running? is it as stable and dailydriver as 15/11?
[ONE Original Android Development] ksigit:
It doesn't boot.
[ONE Original Android Development] aclup3:
thanks dude.. i am really needing an update, because theres really too many fc's and slowdowns...
[ONE Original Android Development] KenjiHannya:
For my daily use

https://plus.google.com/+JPKenji/posts/gzUE1J2S1qs
[ONE Original Android Development] ksigit:
Just wait a little bit, devs promised a new update build around Christmas.. There's unofficial build dated 20151119, if you can't wait. Search this thread..
[ONE Original Android Development] aclup3:
thats the one im using... the official stable one is just half a rom and even less stable
[ONE Original Android Development] LecterMe:
I am using that version too and it's rock solid for me. Currently at 191 hours uptime. No fc or slow downs at all.

Sendt fra min A0001 med Tapatalk
[ONE Original Android Development] aclup3:
i was gaving some bad laggs, slowdown and battery was never reaching 4hours SOT... using cm13 while i wait ;)
[ONE Original Android Development] FalconFX:
This is the only rom that gave me 6.30hrs of SOT,plus its very stable for me, so.e fc's on Instagram app, but nothing major
[ONE Original Android Development] :
Is this ROM jittery for anyone else? Latest nightly, most noticeable on graphic apps, such as Google Calendar with its images parallaxing every now and then. If so, what did you do to solve it? Custom kernel? Any recommendations?
[ONE Original Android Development] p-d:
Stable, good battery life, no lags.

But i have touch issues...
[ONE Original Android Development] hellcat50:
Hast du eine Schutzfolie auf deinem Oneplus One drauf?

Do you have a screen protector on your phone?
[ONE Original Android Development] p-d:
Yes, using a screenprotector, but with other ROMs/Kernels got no touch issues. The touchpanel seems to be extreme sensitive now.
[ONE Original Android Development] hellcat50:
I would wait for the new release which should be released before christmas.
[ONE Original Android Development] KenjiHannya:
Oh yeah ?

It is a big present for all ?
[ONE Original Android Development] payne_307:
Camera, OS featues & Kernel details

Hello All.. I'm currently on Sultan's MM for Bacon. I love that ROM because he uses Oxygen OS libraries for camera which gets rid of a split picture when using flash on Google Camera, plus the pictures taken are quicker and better. However, I always prefer a more cleaner AOSP build like Nexus devices.

Question for users here :-

1.) Which camera the ROM includes (I would guess stock AOSP Camera)? Does it use Oxygen OS libraries/blobs to avoid image distortion when using Google Camera with flash?

2.) Does it have the infamous Mobile Radio Active active bug when on cellular data? Every MM Custom ROM I have seen has this bug

3.) Does it have screen off gestures?

4.) Once hardware keys are enabled (using the flashable zip : link mentioned in OPs first post), can you configure actions on long press vs. short press, etc?

5.) Does is allow to modify the status bar (like position of Clock, batter icon/percentage, etc.)?

6.) What is the standby and Screen-On time on this ROM with location on (high accuracy) and sync on for all accounts - (Google, Facebook, WhatsApp, etc)

Thanks in advance for your help.
[ONE Original Android Development] Spider-Vice:
The camera should be the same as Sultan's, given he and OnePlus on OxygenOS simply use the CAF libraries. Except this won't have Sultan's modifications to it.

Mobile Radio active is present on all ROM's, it's Google's incompetence.
[ONE Original Android Development] joefso:
1) oxygen os cam libs, but not sultan´s Camera HAL work.

2) yes - google has to fix it, deeply rooted problem

3) no

4) Not sure but most likely yes. Will requires some further searching

5) From the top of my head yes, but not anything fancy.

6) Differs from each users and what is more used, but generally more than CM based roms.
[ONE Original Android Development] pocii:
Is the latest build the Christmas one everyone has been talking about?
[ONE Original Android Development] hellcat50:
[MENTION=4792450]h2o64[/MENTION] [MENTION=5585603]Quasar[/MENTION]

Where is the new build?

And please enjoy christmas first :)
[ONE Original Android Development] Olivier:
Tru, me need new build too

Plz no enjoy Christmas tilll new build k?

Inviato dal mio iPhone 9S con Crappatalk
[ONE Original Android Development] Quasar:
Don8 $$$ get builds k?

Inviato dal mio Galaxy S12 con Crappatalk
[ONE Original Android Development] deepaklunked:
Chill out pal. People are so desperate to see your work. Anyways, a merry Christmas to you, your team, family, and friends. And also to my fellow XDA members.
[ONE Original Android Development] Quasar:
Of course I know Oli wasn't being serious xD it's frowned upon to ask for donations on XDA. Cheers, Merry Christmas to you too.
[ONE Original Android Development] deepaklunked:
Lol. I just thought you were freaked. Never mind, glad your are cool.
[ONE Original Android Development] payne_307:
Does this work with Xposed v79 SDK 23? I'm getting bootloop it seems on flashing the zip
[ONE Original Android Development] :
There are screen of gestures in Display.. DTtW, Camera & Music.
[ONE Original Android Development] payne_307:
I can't get GPS to work in Google maps. Is everyone facing the issue of GPS not connecting at all?
[ONE Original Android Development] Xynoclafe:
That is the only serious bug I faced with this ROM. Location services don't work. But there is a new build on the way, so hopefully it will be fixed by then.
[ONE Original Android Development] payne_307:
That's indeed a big bug. Looks like the Devs said a build will be posted before Christmas. But there isn't.

Devs just asking - Will you be posting new build today? I'm checking so that if you will be posting the new build, I'll flash that. Otherwise I'll go and get to either COS 12.1 or Sultan's CM13.
[ONE Original Android Development] joefso:
do not expect a build today, it is christmass lets just enjoy the holidays and see what is going on when we´re past these festivals/celibrations
[ONE Original Android Development] hellcat50:
Best English mate :D
[ONE Original Android Development] :
Does this or Sultan's CM13 generally have better SOT? I'm on Sultan CM13 so far, but the battery life feels kinda meh (coming from a Z3 Compact).
[ONE Original Android Development] payne_307:
I used it for some time. Here is my review of it. It has the same kernel as that of Sultan's CM13. Since Sultan's kernel is CAF based and not CM based it works well, but not without its own disadvantages. First it underclocks your CPU to 2GHz only as is default in Sultan's kernel. Secondly it's based on a build of Sultan's kernel when he was struggling with battery drain due to WiFi. He still has issues with WiFi with the WiFi disconnecting itself randomly at sometime during standby. But on this ROM the drain is lot more pronounced. If the makers of this ROM can take care of the kernel better, then this can indeed be a great ROM. On the ROM other than location not working at all in any app (cell triangulation or GPS) this ROM otherwise was clean and smooth. But kernel, damn that was a downer. I'll love this ROM to pair with a better kernel which can do justice to its simplicity and cleanliness
[ONE Original Android Development] renaltosonylevi:
What makes you think that this is all the kernels fault?

Have you tried other kernels and if so what would recommend?
[ONE Original Android Development] KenjiHannya:
Yes, we could recommend radioactive AOSP MM for him
[ONE Original Android Development] payne_307:
The reason I can say this is kernel fault is because I have gone through the exact same set of issues on this ROM when I was on Sultan's CM13 during November. Which forced me to flash back COS 12.1 as was to be traveling internationally and I couldn't take the risk of bugs like these when my phone mattered to be a lot more. After I came back, I was delighted to see Sultan fixing most of the bugs and hence I moved to his version of CM13. Honestly I do like it with the Snapdragon Camera but being a Nexus user for a long time I'll always prefer clean AOSP. This ROM is important for the community as there are many which are CM based, but hardly any which is trying hard to remain as clean an AOSP build as possible. Hopefully the Dev updates this sooner than people lose interest in the so called plain boring AOSP
[ONE Original Android Development] Quasar:
Sultan's as well as CM's kernels are both CAF based. Sultan's kernel is just rebased off of the latest CAF release. I've noticed waaaay too many people having the misconception that Sultan's kernel is CAF based while CM's is not. Just to clear that out, every non-Nexus device's kernel is CAF based. It's just that CAF has many branches and you can rebase the kernel to another branch or keep it updated with the latest CAF upstream. That, and some other bits of code here and there.
[ONE Original Android Development] payne_307:
Yes I agree. When I say CM based it means using the kernel included in CM builds than basing it on some device tree and latest CAF releases. Anyway you as a Dev get it, and for most users it doesn't matter. Your build is clean and decent. But it can be better with a kernel that ably supports it. Sultan recently made a change to have the boost frequency to be at 1196 MHz. He says that makes device super smooth. Well that is true to an extent but it costs heavily in SOT. I would suggest you have a look at that aspect in case you are going to be including it in your next build.
[ONE Original Android Development] hellcat50:
Didn't knew that, thanks for the info!
[ONE Original Android Development] payne_307:
I know what it will call for when asked in a forum, but I can't hold myself back without asking - When is the update going to roll out?
[ONE Original Android Development] Quasar:
Soon.
[ONE Original Android Development] carrthee89:
U joined oneplus [emoji12]?
[ONE Original Android Development] Quasar:
Eh.... No. Why do you ask?

Whoops. Took me a couple of reads to get that xD. Nah, we're just busy with stuff.
[ONE Original Android Development] Sultanxda:
Underclocking is a disadvantage? Is driving your car at 65 MPH instead of 80 MPH also a disadvantage? Running your CPU past 2 GHz heats it up very quickly, so quickly that your CPU would soon get throttled down to below 2 GHz in order to cool it down (but this doesn't happen in official CM because their thermal mitigation software doesn't work). 2 GHz is already more than enough power, and you can even disable the underclock if you want. Going up to 2.5 GHz is ludicrous, and it's pretty much a gag frequency to make consumers think the device is somehow more powerful during daily usage (consumers love frequency numbers and CPU core count).

What exactly do you mean by "take care of the kernel better"? You want new WiFi drivers that aren't designed for our firmware, so that you can watch your WiFi crash and burn?

There's more to WiFi than what's in the kernel.

The kernel is at fault? The WiFi driver currently in use is the one designed for our firmware. What other issues do you think are kernel-related?

You couldn't take the risk of bugs... and installed COS 12.1? If you think the kernel in AOSParadox is faulty, then one look at the COS kernel would make you faint.

It costs heavily in SoT? Seems like you didn't look at my boost driver (or anything else, for that matter). My driver only boosts 1 or 2 CPUs (1 CPU when there is more than 1 CPU online, and 2 CPUs when there is only 1 CPU online), and it dynamically reduces the duration of the boost depending on how many CPUs are online. CAF's boost driver, which all kernels not based on mine are using (i.e. the official CM kernel), boosts all online CPUs every time you touch the screen, and it boosts all of them for the same amount of time. Which option sounds like it would cost more heavily in SoT?

Even though it uses input-boost durations that are much shorter, official CM boosts much, much more than my kernel does. They're using thread-migration boosting in addition to input boosting, which absolutely obliterates battery life. Thread-migration boosting is boosting the CPU that receives a thread from another CPU (boosting the CPU that receives a "migrated" thread). CM boosts the destination CPU to the same frequency as the CPU that the thread migrated from (with a max boost frequency of 1574 MHz), for 20 milliseconds. In some cases, there can be 100+ thread migrations per second (100 boosts per second). That doesn't sound very good for SoT either, does it?

Everyone uses boosting, even Google (Google boosts a lot with their Nexus devices). Next time, please do your homework before jumping to conclusions.
[ONE Original Android Development] aclup3:
Thats the answer we've been getting for 2 weeks :p

There are some nasty bugs that many other ROMs fixed and you think that your ROM is already daily driver material... Well its not, not right now....
[ONE Original Android Development] Quasar:
Well, I haven't said that. Also, we have a lot of other IRL stuff going on. For crying out loud, we're a bunch of 15-17 year olds cycling this up with school/extra-curriculars etc. I know it's frustrating to wait, but we're just completely tied down atm. To give you an idea, two device bringups have been pending for the last month or so because of other commitments.
[ONE Original Android Development] aclup3:
Yeah, I know you guys are young and like me, have a lot of thing to do, but didn't you ever considered like a nightly program? Everyday, after finishing your work... Would be awesome to see this ROM grow
[ONE Original Android Development] Quasar:
There need to be changes made for nightlies. Right now, I'm busy with school (3 months worth of exams and other stuff) and h2o64 is busy with exams and some other commitments. Mainstream development probably won't take off for a bit unless h2o64 manages to free up some time.
[ONE Original Android Development] payne_307:
Yes there could be. I'm not getting into technical else I should have had been a recognized contributor on XDA. But since the 2 ROMs on which I faced WiFi disconnections have been yours and AOSParadox, I just drew the paradox that its the Kernel. Didn't face this issue on other CM based builds, including official nightlies on build 18th Nov, 21st Nov, 4th Dec, 13th Dec & 21st Dec. But that has other ugly heads, mind you , a lot of them. Including the pathetic pictures taken no matter what the camera or the mod used.

May be yes it would. But let's say the kernel on COS 12.1 is consistently pathetic. It doesn't give me high hopes. As its the ROM I have spent most time with, I know it can't surprise me with a corner. It may not deserve the time I have spent/wasted on it. But everyone does give the stock ROM a longer rope than it deserves, right ? ;)

Google's Nexus line until Nexus 6 all are plagues by the issue. I wouldn't disagree. I haven't seen or used 6P so can't say about that. That is the reason its hard to find a Nexus battery stat even with moderate usage, to find anything using more battery than the screen. When you introduced the boost, I loved it the first few hours. The UI felt buttery smooth. And then when the time to plug my phone into charger came I realized why I left the fluid touch on the Nexus line for an OPO. It was battery juice. I found SOT on your ROM decrease by anything between 30 mins to 1 hr due to the boost. And hence would say that I could happily trade the smoothness for few more minutes of precious SOT. Plus even on Google navigation (even though we aren't touching the screen) the drain has been higher. And I have to use navigation quite a lot. The exact reason why I had to leave the AOSParadox ROM, because there was no way I could make the GPS work on the build.

Your work is great. My OPO is still rocking your MM build of Dec 21st. May be I will be tempted to go to the next build after I hear the feedback for the 27th build which has reverted to the proprietary libraries. But nonetheless, its a good build. This AOSParadox build is a supremely clean AOSP build, where everything you want additionally is extras on the order than a big supermarket bundle. So personally I would want this ROM to succeed and have a decent patronage. Most people ridicule minimalist builds for features. But I would always prefer minimalist builds. Keeps me away from getting hooked to a feature and always keeps it easy for me to get back to the Nexus line with stock ROM from Google (faster updates and bug fixes being the key drawers).

My suggestion was only to make sure it's paired with the kernel that doesn't give a whole lot more reason for people to rant about the ROM. May that kernel be your's Sultan with all the bug fixes as you continuously do as the maintainer of OPO. But on the current build it isn't match made in heaven. Cheers to the great Devs on both ROMs !! I might be a critic but I'm no less a patron either of your work. :)
[ONE Original Android Development] joefso:
just do your homework next time instead, saves you the embarrassment. :)
[ONE Original Android Development] payne_307:
Well there is no embarrassment. People correcting you isn't always embarrassment. You learn few and teach few. I did my homework. But obviously I couldn't become a pro like Sultan overnight and neither will I attempt.
[ONE Original Android Development] hellcat50:
Thanks for the heads-up, mate! I thought that more GhZ= better performance! But you cleared up some things!
[ONE Original Android Development] payne_307:
More GHz never means better performance. It depends on multi threads, cores (both physical/logical) and L1/L2/L3 cache. I work with Big Data and build my own hardware platforms for my company to run things like Teradata, SAP HANA, Hadoop, etc. Since the basic principal doesn't change, its valid even at a mobile device level. In this case however, sometimes the OS stutters due to CPU limited at 2 GHz. But in theory we are doing everything right. In practice its being marred by certain apps which aren't coded the way we would want it to be. If every app followed the same design language, trust me we would probably be a lot closer to iOS in terms of hardware advancement. We still won't match iOS because of the difference in garbage collection between iOS vs Android, but the point being made is - GHz alone are pretty useless unless you come up with some app coded equally uselessly.
[ONE Original Android Development] hellcat50:
I'm just a normal user, so I didn't knew those things, but thanks for the info.
[ONE Original Android Development] merothh:
Having some issues in getting root..Can somebody state which version of SuperSU you have used to get root !!

A Fast Reply would be appreciated..
[ONE Original Android Development] siju2012:
[MENTION=5585603]Quasar[/MENTION] I am trying to download source of AOSParadox and I am getting this error both for M and L. Could you please help?

repo init -u git://github.com/AOSParadox/local_aosparadox.git -b marshmallow_bacon

fatal: Couldn't find remote ref refs/heads/marshmallow_bacon

fatal: cannot obtain manifest git://github.com/AOSParadox/local_aosparadox.git

repo init -u git://github.com/AOSParadox/local_aosparadox.git -b lollipop_bacon

fatal: Couldn't find remote ref refs/heads/lollipop_bacon
[ONE Original Android Development] cyril279:
"getting started" directs you to use "marshmallow_bacon", but that branch doesn't actually exist. You will need to choose one of the current branches (available in the pulldown) to get the sync started.

ex: "marshmallow" or "bacon-par-6.0"

happy building

-Cyril
[ONE Original Android Development] :
hey guys, in reading thru the last 8 pages or so, its pretty obvious u dont hear this much these days, so thanks for working on this rom. (too many of the comments revolve around eta.) its pretty impressive that ur young & able to donate your time for others' enjoyment. like u mentioned, ur busy & trying to juggle a lot of things..

anyway, i just wanted to say: good luck on ur exams (#1), all ur other commitments (#2), & xda looks forward to the next update (#3), whenever its released.. have a good one!!
[ONE Original Android Development] siju2012:
If I use marshmallow or lollipop branch, i get default.xml not available error. I need to download code for Lollipop

From git://github.com/AOSParadox/local_aosparadox

* [new branch] bacon-par-6.0 -> origin/bacon-par-6.0

* [new branch] falcon-par-6.0 -> origin/falcon-par-6.0

* [new branch] lollipop -> origin/lollipop

* [new branch] marshmallow -> origin/marshmallow

* [new branch] old/marshmallow_bacon -> origin/old/marshmallow_bacon

* [new branch] old/marshmallow_falcon -> origin/old/marshmallow_falcon

* [new branch] old/marshmallow_titan -> origin/old/marshmallow_titan

* [new branch] yu-caf-6.0 -> origin/yu-caf-6.0

fatal: manifest 'default.xml' not available

fatal: manifest default.xml not found
[ONE Original Android Development] stryker09:
I get the same here as well
[ONE Original Android Development] merothh:
I'm only asking this because I can't find it after reading a lot of pages from the from and back..

[MENTION=5585603]Quasar[/MENTION] In the OP there are instructions to enable nav bar,disable hw keys and then disable the light (which is said to renable after reboots)

In the first few pages it seems like you planned to add nav-bar functionality directly to the ROM (but I guess that was on AOSParadox 1.0)

So isn't there a permanent way to have the he keys backlight disabled ??
[ONE Original Android Development] Ush1:
Is this ROM stable as a daily driver or is there any known issues?

I'm moving from Oxygen OS as people can't hear me when I call them now.
[ONE Original Android Development] aclup3:
That problemas of the mic is still presente here.. Por at least it was for me. Apart from that, you have some FC, some slowdowns, now in TAP wasnt working, and location wasnt that stable. Wait for the next update that will be released soon
[ONE Original Android Development] h2o64:
It's a WIP

It's a WIP

It's a WIP

It's a WIP

OP gives everything

Guys, first I'm stabilizing AOSParadox 2.1 on 8919/8939, then I'll fix 8226 and finally 8974.

I spent the past two months working on the YU M Challenge. And big exams are coming next week. I'm in touch with testers and people who built WIP stuff... Don't worry, I know we recently have been featured on the portal... But that won't affect the ROM spirit. I do not release RC, BETA, ALPHA. Only stable builds

Cheers
[ONE Original Android Development] KenjiHannya:
[MENTION=4792450]h2o64[/MENTION] Thanked and has all my respect ?﻿

Take tour time, your personal life first ?

And come back with everything that has to be the best or one of the best

And for those who criticize the work here, **** them ?
[ONE Original Android Development] abhibnl:
Hope you would win the YU M challenge and the price money. BTW, which YU device are you developing for?

Sent from OnePlus One
[ONE Original Android Development] h2o64:
All of them ?
[ONE Original Android Development] abhibnl:
Lol! That's serious bounty. I can understand if you devote all your free time to yu challenge. Best of luck!

Sent from OnePlus One
[ONE Original Android Development] heitoradv:
How to Installing the beta?

Enviado de meu A0001 usando Tapatalk
[ONE Original Android Development] :
Over my head, but worth a read for the devs. I see it's for CM but it seems like it applies to WiFi firmware. (Link says CM 12 but OP is for CM 13).

http://xdaforums.com/oneplus-one/development/rom-cm-12-builds-t3045053/post64590747#post64590747

Edit: Link above looks like firmware required to flash latest radio, link below.

https://forums.oneplus.net/threads/...genmod-13-0-with-3-4-0-kernel.401179/page-152

Notes: it seems like TWRP 2.8.6.0 is required.