yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] GirishSharma:
Yesterday when I had a wish to flash Radioactive kernel on this ROM, I took nandroid backup. After flashing kernel, when I wanted to restore app+data from Titanium backup of an app, Titanium backup could not restored the app, while Titanium backup restored the same app and its data, from another ROM's nandroid backup. I tried by Nandroid backup manager too, but it also failed to restore app+data of this ROM's nandroid backup.

So, I think there is something which is restricting to restore from nandroid backup of this ROM. Give it a try, take nandroid backup in twrp, and try to restore app+data by either Titanium backup or nandroid backup manager. If anyone succeeded, please report here. Thanks.
[ONE Original Android Development] KenjiHannya:
AOSParadox 2016.03.13 + Radioactive AOSP Kernel v1.21 + Poweramp + XtremeMusic v7.0.3 + SuperSU 2.70

https://plus.google.com/+JPKenji/posts/c1R4nZv6KAy
[ONE Original Android Development] Silent7x:
What's the difference between 3.13 and 3.14? Is 3.14 sweeter?
[ONE Original Android Development] KenjiHannya:
03.13 corrupted folder. Flash the 03.14 mate ?
[ONE Original Android Development] KenjiHannya:
Test 3, 2 and 1

https://plus.google.com/+JPKenji/posts/Bt4pSYJcWA3
[ONE Original Android Development] GirishSharma:
And this is mine. Simple usages pattern.
[ONE Original Android Development] SirSoviet:
Latest build is laggier than expected (even after changing animation speeds) but battery life is pretty outstanding.
[ONE Original Android Development] wenrou8023:
mmb29m？？？？？so old
[ONE Original Android Development] merothh:
I've found a workaround to make the backlight LEDs permanently disabled after every reboot

Pre-Requisites

1. Have SuperSU(imp) installed !

2. Have A file manager to edit root permissions.

It goes like this..(i've modified OP)

Disabling the Hardware keys:

1. Go to /system/usr/keylayout/generic.kl.

2. Scroll down and find the following keys and add # before each of them.

It should then look like this:

# key 139 MENU

# key 158 BACK

# key 172 HOME

3. Save and Reboot.

Enabling softkeys:

1. Go to /system/build.prop.

2. Scroll down to the extreme bottom.

3. Add this line there : "qemu.hw.mainkeys=0"

(Without inverted commas)

4. Save and Reboot.

Permanently disabling LED backlight.

1. Go to /su/su.d

2. Create a file named "DisableSoftkeysBacklight"

3. Give it full permissions ("rwx rwx rwx")

4. Paste this stuff inside the File (without quotes)

" #!/system/bin/sh

echo 0 > /sys/class/leds/button-backlight/brightness

echo 0 > /sys/class/leds/button-backlight/max_brightness "

5. Save and Reboot.

6. Let me know whether it worked !
[ONE Original Android Development] acuicultor:
It isn't, try another browser.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] payne_307:
[MENTION=4792450]h2o64[/MENTION] What camera HAL and blobs are the new Beta builds using? The one which is marked stable I guess used Sultan's camera HAL and kernel. What does the current one uses?
[ONE Original Android Development] h2o64:
We won't ever use his blobs
[ONE Original Android Development] SirSoviet:
Welp, I'm using my AOSParadox with SuperSU 2.70 and there isn't any su.d or su folder anywhere. I tried other methods but they didn't work or weren't applied on boot.
[ONE Original Android Development] merothh:
Odd. Wait I'll do my research and update you.

Basically there's no need of su.d if you have init.d support in ROM. There's an universal init.d enabler in some thread (Google it)..this ROM doesn't have init.d so flash that and place scripts in /system/etc/init.d

Cheers (I'll return with my findings after some time about su/su.d)
[ONE Original Android Development] SirSoviet:
Ohhhhh. I tried the method that required me to make a file called 90userinit in /system/etc/init.d/ but I went back to jgcapps' CM13 just because it didn't work. Thanks!

Edit: Tried Universal Init.d Enabler, that didn't work. Tried emulating init.d, that didn't work either.
[ONE Original Android Development] Killerkip:
Thanks for pointing out the su.d method [MENTION=6020447]theratedrock[/MENTION], disabling the backlights really made me scratch my head as I had originally placed the DisableSoftkeysBacklight in the init.d folder and figured init.d wasn't working.

For su.d to work you need to create the su.d folder in /system and place the DisableSoftkeysBacklight file you created there with permissions 700 (owner rwx) and it should work (it did for me).

FWIW I'm using SuperSU 2.70 RC.
[ONE Original Android Development] merothh:
well, I've tried 2.70 RC on the November build and it's working perfectly.. It must have been something wrong on your side.. Get SuperSU from these threads

N-Preview (2.70 RC and backward compatible)

http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726

Beta (2.68)

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Stable(2.65)

http://xdaforums.com/showthread.php?t=1538053

[MENTION=6917522]SirSoviet[/MENTION] From now on press thanks instead of saying thanks.

Cheers.
[ONE Original Android Development] merothh:
I had stated in my first post..but yeah no probs !

Glad to help !

This was the only thing that was keeping me away from this ROM..h2o64 told that he would look into bringing a soft-key switch toggle..so it shouldn't be of any significance very soon.
[ONE Original Android Development] Killerkip:
Wasn't trying to take credit or anything, I thought I'd just put down what worked for me :).
[ONE Original Android Development] merothh:
It worked right (just to make sure nothing's wrong with the original post) or I'll edit the post with that file attached so that you guys would just have to copy it to /su/su.d
[ONE Original Android Development] Killerkip:
There's no need for the /su folder, you just need to create the su.d folder in /system (afaik there are no su folders by default) and copy the file to /system/su.d and it doesn't need full permissions, it only needs permissions 700 (owner read, write and execute).
[ONE Original Android Development] SirSoviet:
Tried everything, still not working :I

I can wait for a new build.
[ONE Original Android Development] merothh:
Permissions I wasn't sure abt it..that's why. But it makes sense owner is root and it only needs the permission.

Even with SuperSU 2.70 there is a /su/su.d folder..but before(before systemless came) the su.d folder was in /system.

So that's why it must have worked..

---------- Post added at 04:32 PM ---------- Previous post was at 04:32 PM ----------

Soft-keys ?? If then I'll add the File to the post..just download and paste there. And feel free to PM on hangouts.

---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------

Check my previous posts abt the /su folder it's there.
[ONE Original Android Development] Killerkip:
I see, my bad, then either must work (/su/su.d or creating a su.d folder in /system and placing the file in there) assuming you used the /su/su.d folder.

Afiak AOSParadox doesn't support systemless root so even the newer versions of SuperSU that support systemless root wil install in system mode.
[ONE Original Android Development] merothh:
I don't think a ROM is responsible for systemless root. Converse might be true..if the kernel has sepolicy patched.
[ONE Original Android Development] Killerkip:
Yeah, from what I've read the boot.img is responsible for systemless or system mode but for me thats a non issue as I prefer it installed in system mode anyway.
[ONE Original Android Development] payne_307:
So what are you using on the current builds? CM or Oppo Find7 blobs?
[ONE Original Android Development] h2o64:
Oxygen blobs
[ONE Original Android Development] payne_307:
This makes me try this ROM right away. On to your download site already. I'm very critical of the battery and camera performance and have reviews for camera performance on each blobs. If you are up for some feedback I can share some after flashing the ROM. I don't care much about RAW & 4K recording so I should not be hard to please if the average Joe pics come out clean and nice. Basis the reviews I can trust the Beta build can be a daily driver as well. Will see and hope the stable build is round the corner. AOSParadox was the 1st ROM to entice me to move out of CM builds and try AOSP/CAF builds for Bacon. So your ROM is a pioneer in some way.
[ONE Original Android Development] DarKAngel1234:
Hey bud try Darkobas or BrokenOS. Camera is better right now on Darkobas however.

---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------

Is this project dead or just slow?

---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------

Download link doesn't work?
[ONE Original Android Development] merothh:
Download links @ download.AOSParadox.org

The project is NOT DEAD ! He is working on it and taking his time.

And don't recommend other ROMs in the development thread for a ROM. It's discouraging sometimes for the devs..

Cheers
[ONE Original Android Development] SirSoviet:
[MENTION=4792450]h2o64[/MENTION] is likely doing most of the work all by himself, so it can take a while to release new builds.
[ONE Original Android Development] payne_307:
Agree. And hey [MENTION=4792450]h2o64[/MENTION], I tried your build with the latest RadioActive Custom Kernel v1.21. No qualms about the performance. (Didn't have it for long so yet can't speak for the battery life). But the camera has the same issue as those of Sultan's CM13, Darkobas, etc. Basically all the ROMs that are using Oxygen OS blobs/Sultan's Custom HAL. The HDR mode is too much sprinkled with extra colors that is nowhere close to the object you actually shot. I tried it with these cameras -

1.) Stock SnapDragon Camera in your ROM

2.) CameraNext Stock

3.) CameraNext modded v10

4.) CameraNext modded v22

5.) Oppo Camera v2.67 by BOOTMGR

6.) H2O Camera

All of them had the same issue in HDR mode. Non HDR was ok but still more saturated than what it should be. But at least on non-HDR mode you have camera apps that allow you to adjust sharpness/saturation/etc. But in HDR mode there is nothing you can alter. The extra color is highly tilted towards being warmer on the Red shade. Everyone I shot using HDR mode looked like a Red Indian.:p

I don't know how far you are in your development but I can tell you with great confidence that the blobs used by Omni are the best for the OPO. Yes you will not have RAW and 4k (unless you use Oppo Camera) but I guess you don't have them anyway if you are using Oxygen OS blobs. So if its possible try using Oppo Find7op blobs and get better camera output. And then if you make the Oppo Camera v2.67 from BOOTMGR as your default camera then you have a star on your side. CameraNext modded version are sometimes wonky on Marshmallow so might better lookout for the version released on COS13. But even then Oppo Camera with Oppo blobs is the best allrounder. Just my 2 cents. Rest I leave it your personal preference and fine judgement. Otherwise a far better ROM to be labelled as Beta. Cheers !!
[ONE Original Android Development] merothh:
Hey anybody using opengapps stock with the November or latest builds ??

If so please specify the date of the package you are using too.

Thanks a Load.

Cheers !
[ONE Original Android Development] evronetwork:
I'm a bit confused, tittle says "[6.0.0]" but in first post I see

"ROM OS Version: 5.1.x Lollipop" so which is right?

P.S. I'd love to test a non-cm rom that works without issues :P
[ONE Original Android Development] darjwx:
I think the latest stable build is based on android 6.0.0. But there are builds of 6.0.1 also.

(Afaik the op is not updated)
[ONE Original Android Development] GirishSharma:
For me Slim_mini_gapps.BETA.6.0.build.0.x-20160314-1420.zip working without any issue.
[ONE Original Android Development] DarKAngel1234:
Try Darkobas, non CM rom running marshmallow AOSP/CAF, simply amazing camera, will blow your mind.,

Find it on Google Plus only.
[ONE Original Android Development] abhibnl:
Guys, please do keep these recommendations to PM-only. It's disrespecting dev's work to recommend another rom in this thread. He's already working hard to bring an experience which is as close to AOSP as bacon can get. So appreciate [MENTION=4792450]h2o64[/MENTION] efforts, and stop recommending Darkobas or any other rom within the thread. Take these recommendations to PM please. Thanks! :good:
[ONE Original Android Development] h2o64:
Knowing that this ROM is AOSParadox based.. Yeah..
[ONE Original Android Development] GirishSharma:
I am not a camera fan, so for me, this ROM is like a blessing for my phone because :

1. Highest SOT; around 8.5-9 hrs.

2. 2% wakeup reported by wakelock dectector.

3. Installed xposed and gravity box for tinny things.

4. Camera is too doing best; as a camera can do in a tiny device with its limited sources.

5. None issue in firmware/modem, best signals.

6. None reboot so far.

7. Let me explore more....

So, I am happy like most happiest person in xda...
[ONE Original Android Development] payne_307:
Agree with the rest not with your verdict on the camera. Camera on the OPO can do wonders. If you don't know doesn't mean doesn't exist. The best for OPO right now is the blobs used by Omni which is from Color OS 2.1.5. Rest all including this ROM have issues. Using Oxygen OS blobs gives too high color saturation making it look like an over saturated AMOLED panel without the deep blacks. But rest is all good here.
[ONE Original Android Development] joefso:
Yes this has been my own experience too, I think there will be more gains than losses this ROM is going to.implement find7op camera blobs
[ONE Original Android Development] evronetwork:
cool :D

I'm already on that, after I wrote my comment - very happy with it. I always prefer small size rom but feature rich and it's sweat :D

P.S. Only thing I miss is a dark theme. In the past I used slim rom because of it's size and it was feature rich, so as darkobas rom and it has snapdragon camera which is great(love the slow motion recording)
[ONE Original Android Development] Sam3087:
Its been a while i used that rom. But just try this - in developer options (the one that you get after tapping build number in About Phone 5 tikes) yhere is an option called theme - this has a dark option
[ONE Original Android Development] h2o64:
New build !

Hello everyone !

Finnally AOSParadox 2.1 is here !

Many many many many changes have been made and the ROM has been redone from scratch !

I don't really know what to put in the changelog ... Let's put the core features :

- Up-to-date with sultanxda kernel
- Up-to-date vendor blobs
- Remade all the commits overlay (we conserved dark mode)
- Remade all the frameworks/all the manifests/all the branch organization
- Many code cleanup
- In-bulilt prima driver
- Many more to discover ...

Download :

http://download.aosparadox.org/AOSParadox/

Off Topic :

So, many things happend during this period. As a real scientific, I'll make a list :

- The ROM won the YU Android M challenge : http://forums.yuplaygod.com/threads/results-yu-android-m-aosp-bring-up-challenge.33013/

- We added support to YUREKA / YUPHORIA / YUNIQUE / ONEPLUS X

- We added a new member to the team

- We bought a server/website

- We, obviosly, remade the whole ROM

- Many exams have been passed

- So much things ... But I'll answer any questions :)
[ONE Original Android Development] nikhil18:
So now WiFi modules are not needed
[ONE Original Android Development] Xynoclafe:
Can someone test and tell me if Location issues are fixed? That's the only issue I had with this ROM. Currently on Darkobas and even though it's good, it's slow charging is killing me and I want to get back to this ASAP.
[ONE Original Android Development] therohanchawla:
One of those things that make ur day...

Thanks and congratulations man...
[ONE Original Android Development] h2o64:
Everything has been redone and all the previous issues are fixed
[ONE Original Android Development] Xynoclafe:
Which Gapps do you recommend?
[ONE Original Android Development] pa1281:
What about on screen keys?
[ONE Original Android Development] h2o64:
Camera, torch, music gestures have been removed and are in the process of being redone
[ONE Original Android Development] pa1281:
Great...This build doesn't have a switch for on screen keys?

Any plans of adding advanced reboot option?

In cellular networks , y network selection has no 2g,3g or 4g options ?(no idea abt options available now, sry)
[ONE Original Android Development] rt235130:
Why is there a fm radio app? Obviously we can't use fm radio lol.
[ONE Original Android Development] SirSoviet:
This is the best day of my OPO's life WOOOOO

Seriously, thank you team!
[ONE Original Android Development] thenessus:
Flashed.

So far so good. No bugs I see as of yet.

Very glad this came out finally.

Update:

The speed, the zero lag, the raw AOSP... this is too good.

I love the fact it has zero UI customization, allowing for %100 Xposed compatibility.

This is in my top 3 now, along with Sultan's CM13/12 and Omnirom
[ONE Original Android Development] Xynoclafe:
Which Gapps did you use?
[ONE Original Android Development] payne_307:
Is this ROM by default underclocked like Sultan's ROM? Also, is this still using Oxygen OS blobs?
[ONE Original Android Development] thenessus:
I had a strange issue flashing Banks, it didn't finalize the flash and I had to reboot.

So I flashed Open Gapps (nano) and it worked just fine.

Never had this issue with Banks, and I used the same file with a few other ROMs this past week....
[ONE Original Android Development] h2o64:
Yes and yes
[ONE Original Android Development] aclup3:
Does this ROM still has f2fs compatibility?
[ONE Original Android Development] Xynoclafe:
Which camera does this have by default? can we flash Sultan's Snapdragon Camera?
[ONE Original Android Development] kapooya:
Are you planning to support the oneplus 2 in the future?
[ONE Original Android Development] David:
You awesome ! thank you
[ONE Original Android Development] h2o64:
There's other devices in our target but we considered it

---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------

Yes

Snapdragon camera is default
[ONE Original Android Development] dendi:
[MENTION=4792450]h2o64[/MENTION] have u implement display commits or drivers also from sultans kernel buddy ? because we ( new opo users , i.e opo manufactured with LG displays ) have issues with sultans kernel ! we get this display light leaks ! so i ask this ! please can u get back to me with this info or my download will be a of waste if this doesnt work me for me :) thank you again sir
[ONE Original Android Development] h2o64:
I guess you'll also face this issue as sultan's kernel is nearly untouched here
[ONE Original Android Development] dendi:
aww ! MANN ! :( one small favor ? this issue was present on DARKOBAS ROM ( another AOSP ROM ) , but [MENTION=4633983]nikhil18[/MENTION] helped fixed this issue there :) can u please talk with and work together also fixing in your rom ? please man :)
[ONE Original Android Development] thenessus:
Got a small bug on Snap Camera.

Notice strange bar at top left of viewfinder.

Edit: it seems the bar is not present on screen captures. Weirs.

Removed the filem
[ONE Original Android Development] h2o64:
Darkobas ROM = AOSParadox 2.0 Edited
[ONE Original Android Development] dendi:
looks like the only way to confirm if the issue is present is to test it ! ill get back to you in some time after testing ! it take me 5 hours to download 1 rom ! thats why i asked :) np ill check it
[ONE Original Android Development] evronetwork:
Yeap found it, thanks - It's not dark-black, more like gray but still better than white :D
[ONE Original Android Development] Irseq:
The installation seems to be freezeing on "Target: oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys" for me. Tried with system partition mounted and unmounted before. Data and cache are formatted in f2fs.
[ONE Original Android Development] Jeffrey98:
Looks promising! Could anyone post some screenshots from the ROM?
[ONE Original Android Development] thenessus:
You won't see anything special. UI is pure AOSP
[ONE Original Android Development] Jeffrey98:
That's true, but I'm actually interested in which apps are included by default (I've seen ROMs in the past including holo applications in their material design ROM)
[ONE Original Android Development] thenessus:
Stock AOSP cam alongside Snap cam

Holo design stock AOSP music app and M stock Browser.

FM radio too for some reason :)
[ONE Original Android Development] aclup3:
same problem here.. can anyone help? wich firware should i use?
[ONE Original Android Development] Jeffrey98:
Use the CM firmware (Just flash one of the firmware packages which could be found on XDA, or flash the latest CM nightly.

---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------

I really like the Snap Cam. Is there a way to disable the AOSP cam and the AOSP music player?
[ONE Original Android Development] aclup3:
and what about the flashing error? any idea?
[ONE Original Android Development] SirSoviet:
Lack of init.d support is a dealbreaker :(
[ONE Original Android Development] Jeffrey98:
It may be a corrupted zip or if you've got f2fs partitions, maybe they broke the feature... You may check the MD5 of the zip if it's provided . Otherwise just wait for the dev to come to the thread.

---------- Post added at 01:57 PM ---------- Previous post was at 01:47 PM ----------

Yup. It is :(
[ONE Original Android Development] payne_307:
I had really high hopes from this ROM. But these 5 things are such a deal breaker -

1.) That underclocked stock kernel from Sultan .. meh! (yes there are custom kernels but still)

2.) Those horrible Oxygen OS blobs (horrible defet of over color saturation when HDR mode is used). Hard to look beyond anything other than the ColosOS 2.1.5 blobs/HAL for the OPO at present.

3.) Not having at least d2tw if not the torch gesture (though the Dev may get the gestures back)

4.) No init.d support

5.) F2FS support questionable - as people are reporting flashing errors (could be a hoax too)

Was having more expectations from this than any other stock/custom ROM. But it gives an Oxygen OS kinda job. Great in some areas, pretty ordinary in most. I will still stay around for some more time if there is another update to fix some of the glaring issues, camera most importantly.
[ONE Original Android Development] Miksel12:
[MENTION=4792450]h2o64[/MENTION] Will these work on this rom: https://www.androidfilehost.com/?w=files&flid=51648
[ONE Original Android Development] h2o64:
You can flash others camera blobs if you really wants to. Double tap to wake works just fine and we are recoding the gestures. I'll add init.d support if you want. f2fs is tested and functional.

Try and see ?
[ONE Original Android Development] thenessus:
Yup just disable them in app properties

---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------

DT2W works though
[ONE Original Android Development] Xynoclafe:
I had encountered that issue. Kept the phone idle for about 10 min. It finished installing after that. no issues.
[ONE Original Android Development] KenjiHannya:
Here

https://plus.google.com/+JPKenji/posts/ZT6SfERtapQ

I prefer last 00011.

Good luck

---------- Post added at 01:05 PM ---------- Previous post was at 01:05 PM ----------

Delete the apks from system.
[ONE Original Android Development] Irseq:
So it actually finished installing, just took a long time. Flashed latest open gapps afterwards. However when I rebooted it got stuck on the OnePlus logo. And for some reason twrp fails to mount data partition now. Too bad I had a backup there, wonder if I can fix that. That's really weird, honestly.

edit: I genuinely have no idea how it was possible to actually corrupt the data partition by flashing a rom and a gapps package. Fortunately formatting the partition made it usable again. Going to flash the latest CM nightly now and start again from there.
[ONE Original Android Development] Kamalk:
Hi,how to disable the dt2w?
[ONE Original Android Development] Jeffrey98:
If you could add init.d support it would be amazing :)