Database Info

[PORT] [ROM] Android L Developer Preview for HTC One [ALPHA 2]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Say hello to Android L Developer Preview for HTC One​
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What is this?
This is a direct port of Android L Developer Preview, which was released for the Nexus 5 and Nexus 7 (2013, WiFi). This is not a SDK port, this is the real deal!
How did you do it?
Magic! Just kidding, a lot of hard work went into porting everything. Special thanks to these mega awesome guys, this ROM would've not been possible if they didn't help us (make sure you thank them too):
sykopompos - For helping me out with ramdisk and providing useful tips
poondog - For helping me fix the graphical glitches in kernel (and yes, I am using his awesome kernel)
feltox and manups4e - For helping me in additional debugging of the builds
What works and what doesn't work?​
At the moment, this port is in alpha stages. We are working really hard every day to fix the major issues quickly, but since this is a non-Nexus device, it's quite complicated to get things working smoothly. Half of the things work, half of the things don't work.
You are more than welcome if you want to help us in fixing bugs, together we can eliminate the bugs and fix issues faster
What doesn't work at the moment:
WiFi
Bluetooth
Data DATA WORKS NOW (thanks to @manups4e)
Sensors (except GPS)
Camera
Sound
What works at the moment:
Everything else as far as I know, but do let me know if you find anything else that doesn't work
Once again, this is currently in ALPHA stage and we are working to fix whatever is not working, so please don't spam this thread with posts like "Camera does nt work, what 2 do"
Screenshot
How to install:
Download the ROM
Place the ROM in your internal storage/SD card
Reboot into recovery (MUST BE LATEST TWRP/CWM)
Wipe the following partitions: cache, dalvik cache, data and system
Flash ROM
Reboot
First boot takes around 10-15 minutes
Download
ALPHA 2: https://docs.google.com/file/d/0B64IJ9xlDpb4UFRiTkVOWm9rVkU/preview
Changelog
10/8 - ALPHA #2
> Fixed data (3G/4G now works)
11/7 - ALPHA #1
> Initial build
FAQ
Q. Can I flash a custom kernel on top of it?
A. No, we use a heavily modified ramdisk and kernel, so if you flash another kernel the ROM will stop booting. DO NOT FLASH ANY CUSTOM KERNEL ON TOP OF THIS
Q. XYZ doesn't work
A. This ROM is currently in ALPHA stages so that is expected. On top of that, Android L is currently a developer preview so any bugs in the developer preview will show up on this port as well.​

Hi everyone,
GPL required Kernel source here, more info soon
https://github.com/poondog/android_kernel_htc_msm8960

looks nice, great job!! I will try it when few bugs are ironed out, don't have time right now. Keep up the good work :highfive:

Camera dnt work, wat 2 do?
Sent from my C6916

ahahahahahahahhahahah

keep it up...hope others can also help solve the existing problems

lewonsky said:
keep it up...hope others can also help solve the existing problems
Click to expand...
Click to collapse
Those bugs should be fixed much quicker now that more people have acces to it... at least I hope so.

you forgot to mention that mtp doesn't work properly too....to me htc one is shown on mobile devices but i can't access the sdcard without adb

What is the kernel used? Maybe that is the main reason for most of the bugs since most of them are driver related issues.

manups4e said:
you forgot to mention that mtp doesn't work properly too....to me htc one is shown on mobile devices but i can't access the sdcard without adb
Click to expand...
Click to collapse
I'm not sure what one of my guys did to fix that but it was fixed. What are you guys using for your base? N5 and n7 mixed or the n4 port? We fixed a lot of things in the port that wasn't working right in the Dev preview
Sent from my C6916

the kernel is aosp with cyanogenmod cafs (thx poondog) and the ramdisk files are the cm ones updated with latest android L strings

sykopompos said:
I'm not sure what one of my guys did to fix that but it was fixed. What are you guys using for your base? N5 and n7 mixed or the n4 port? We fixed a lot of things in the port that wasn't working right in the Dev preview
Sent from my C6916
Click to expand...
Click to collapse
N7 2013 + app, priv-app and framework from N5 + proprietary files from GPE

ARNOB said:
What is the kernel used? Maybe that is the main reason for most of the bugs since most of them are driver related issues.
Click to expand...
Click to collapse
The kernel is by @poondog, he modified it a bit to fix the graphical glitches on our ROM.

proprietary files from gpe have different dimensions then the cm ones....if we are using cm cafs isn't it better to use cm proprietary files?

manups4e said:
the kernel is aosp with cyanogenmod cafs (thx poondog) and the ramdisk files are the cm ones updated with latest android L strings
Click to expand...
Click to collapse
I've split the boot image and seen that yesterday. I might look at the gpe ramdisk tomorrow and maybe that can be cleaned up a bit better then mucking around in the cm one removing the extra crap that you guys don't have and if you did would probably break L
Sent from my C6916

manups4e said:
proprietary files from gpe have different dimensions then the cm ones
Click to expand...
Click to collapse
libs don't have "dimensions" lol
manups4e said:
if we are using cm cafs isn't it better to use cm proprietary files?
Click to expand...
Click to collapse
I am not using anything from CM in the latest build, it's all from GPE

ssrij said:
N7 2013 + app, priv-app and framework from N5 + proprietary files from GPE
Click to expand...
Click to collapse
You guys should have used the n4 port as a base, there is a lot of stuff that we went through and fixed in it that is broken if you use the developer preview bases. I thought you switched to us for your base and that is why I couldn't understand why some things weren't working when I knew they were working and fixed in the n4 port
Sent from my C6916

ssrij said:
libs don't have "dimensions" lol
Click to expand...
Click to collapse
ahahaha i'm italian...forgive me...in italy bytes and multiples are called "dimensioni" and i translated accidentally wrong ^^ what i was saying is that cm proprietary files and gpe proprietary files have different filesizes ^^

sykopompos said:
You guys should have used the n4 port as a base, there is a lot of stuff that we went through and fixed in it that is broken if you use the developer preview bases. I thought you switched to us for your base and that is why I couldn't understand why some things weren't working when I knew they were working and fixed in the n4 port
Sent from my C6916
Click to expand...
Click to collapse
I tried to but was having way more issues. Anyway, I'll look into that again tomorrow, right now I have to clean the builds, there are lots of libs and files that are specific to flo and serve no purpose to m7 so gotta throw them away.

Android Lollipop in our phone

Hi guys! Maybe this question has been already posted here, but is there any developer that will do a rom for our device with android lollipop?? Thanks so much and sorry for bad english!!
Sent from my GT-I9070 using XDA Free mobile app

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

From this thread:
NOTE FOR EVERYBODY
Copy & paste this answer in any thread like this.
Android 5.0 Lollipop from Team Canjica probably will never see the light. In our opinion, Galaxy S Advance and in generally STE-based devices are too weak to handle well another Android major release.
The fact is that more time passes, more OS and applications become heavier and complex.
Was a pain to get a "stable" (between quotes since still has some issues like huge battery drain, that can't be fixed) Kitkat.
Another major release means heavier, more complex, CPU even with OC is too slow to handle and execute well threads, RAM memory is too little and this means lags, impossibility to run big apps and the Mali 400 single core GPU is too weak for more complex graphic effects in games that will come and especially in transitions between menus, pull down status bar etc. The last perfect major release for this device is Jelly Bean 4.3, to build any major release means that we need to research and find (with A LOT OF TESTING) how to fix bugs, means that we need to develop new OMX patches to make camera and videos working. KitKat is okay but huge battery drain and a lot of lags are signal that it's the last major release that these STE devices can handle in a non-stable way against JB 4.3 that it's almost (to not say "totally") stable. Now, stop a moment and imagine Lollipop, totally ruined user experience. Do you wanna live together with device lagging 99/100 times (1/100 without lags rightly after power on, maybe) and with charger always connected? We should be lords of our devices, not slaves. Nobody of us still uses a STE device and without is totally impossible to develop what has never been developed, if you want to keep updated I'm sure that you would change device asap, today even a 100€ device is more powerful than these. Janice will be 3 years old on April 2015, it's just the future coming...
We loved this device, development, known good guys here... Officially this device died on 4.1, Team Canjica gave you 3 major releases!!!
Never forget

@giovibob
Dont worry. Nova fusion (maclaw) will (propably) build CM 12 for us [emoji1] .

MikiGry said:
@giovibob
Dont worry. Nova fusion (maclaw) will (propably) build CM 12 for us [emoji1] .
Click to expand...
Click to collapse
Fully working..
Sent from my GT-I9070 using XDA Free mobile app

giovibob said:
Hi guys! Maybe this question has been already posted here, but is there any developer that will do a rom for our device with android lollipop?? Thanks so much and sorry for bad english!!
Sent from my GT-I9070 using XDA Free mobile app
Click to expand...
Click to collapse
Here you go:

I really dont think so.. (bad) .. But.. One never know.. Perhaps someone here can give us a surprise. :fingers-crossed:

Guys did you see s3 mini has got lollipop from developer Maclaw hats off to him. So now my question is as our has the Novathor soc wouldn't it be easy to port this to our device??

hrishikeshgramani said:
Guys did you see s3 mini has got lollipop from developer Maclaw hats off to him. So now my question is as our has the Novathor soc wouldn't it be easy to port this to our device??
Click to expand...
Click to collapse
Look on list of non working stuff there. Probably he will release it for our device too, to gain more money from ads. :laugh:

Mclaw is shady.. Enough said.
Sent from my XT1023

revenat said:
I really dont think so.. (bad) .. But.. One never know.. Perhaps someone here can give us a surprise. :fingers-crossed:
Click to expand...
Click to collapse
Nope, sorry, we all have new devices. @diego-ch is the last one to join the qcom familiy (LG G3), @Rox- has a Galaxy S3 Neo, and if I remember correctly, @frapeti has a Galaxy S4. And @zwliew (for those who don't know him, he as contributed a lot to the kernel we use for both janice and codina, he had the latter, codina) got a Moto X 2013 (I think that's right?). Heck, even cocafe has a new qcom device (Xperia z1).
And because Lollipop (and CM12, and OminROM versions of it too) has arrived, we are focusing on our new main devices. So, for now, no Lollipop love for janice (and Antares already said what we think as whole), yet still we may do something on the future (no promises).

@Paul L. And olso no chance for updated CM 10.x builds ?
Wysłane z mojego nexusowego tablecika.....

MikiGry said:
@Paul L. And olso no chance for updated CM 10.x builds ?
Wysłane z mojego nexusowego tablecika.....
Click to expand...
Click to collapse
We are tired to work on a device that nobody of us still has...
Inviato dal mio GT-I9505

Guys, it's simple: if you want to have the latest software updates will have to buy a new phone . Why .. ? because everything moves and is logical and normal that the developers change their phones and stop giving importance to the devices that few people have these days . The S Adv is a phone of 2012. Personally I still have this device because it fulfills , for now, my requirements . I know not everyone can change their phone but as I said , everything progresses and is logical that requirement . We are going great KitKat . We can not ask for much more .
Regards .

yes, there is
i booted up cm12 on my s advance, it has some bugs.. like vibration, some sensors, and others

for those still waiting look in original development thread
,near stable cm 12 has been built by hastalafiesta.notable bugs include video recording doesnt work(stills work fine though),auto brightness(manual adjustment works),wifi direct,compass,gps.the rest(calls,data,wifi) work just fine.ui is fluid enough.i suggest u flash the 12/05/2015 build.personally tested the 03/05 build ,the latesf one only got better
install process is same like any kitkat rom:
for the 12/05/2015 build,simply clean install over stock jellybean firmware(installed thru odin of course).no need to install any special kernels in the intermediate process,simply clean intall thru temp cwm recovery.just remember install seems blocked at "found ext4 partition at mmcblk03,05,03...."something like that,dont panic its still installing...takes nearly 30 mins for the install to complete

[ROM][Stock][D850] D855 Lollipop Stock Rom for D850

First off to give credits to - @robalm for the Base/rom here http://forum.xda-developers.com/lg-g3/development/stock-t2961073
And Credit to - @autoprime for posting, boot,modem,images and so on!
Rom Status - STABLE​Rom Details:
Stock based on D855 v20i
LG apps/LG Update Center (Works?)
Stable?
Stock international on D850 what else is there to say?!
Current Bugs:
Error Message random times at boot: Check HERE ( I have not tried this, flashing may fix?)
Root Can it be rooted by flashing supersu 2.40? (I haven't tested yet)
ONE WARNING: This does change your model number to D855 in Build.prop. You can prob always change it to D850 but I have not tested that. You can however always flash back to a D850 rom. Which I recommend before flashing back to 100% stock if you ever do.
Screenshots:
2nd Post
Download Links:
Main Server - HuntersPad_20D855_20Rom_20V1.zip - 980.8 Mb
Mirror Server (Might be faster at the moment) - http://hunterspad.com/rom/​

Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Another Reserved

So can we just flash this on d850 just like any other rom?

Lol ???
2SHAYNEZ

shayneflashindaily said:
Lol
2SHAYNEZ
Click to expand...
Click to collapse
whats so funny?

So you can't make calls?

omnomnommm said:
So you can't make calls?
Click to expand...
Click to collapse
You can make calls, you just can't hear anything or be heard...... Perfect for calls with your singificant other.... blame it on the phone..... :angel:

I think I know how to fix the no-call-audio bug. I'll give it a look this evening, since I've spent one day on AOSP and I'm actually not liking it too much.

TemporaryTester said:
I think I know how to fix the no-call-audio bug. I'll give it a look this evening, since I've spent one day on AOSP and I'm actually not liking it too much.
Click to expand...
Click to collapse
Thanks!
Sent from my iPhone using Tapatalk

This should resolve call audio. Flash in recovery.
I also tried to bake in the cust fix earlier, but it doesn't do anything. Still throws that error.
Credits to @Cloudyfa, as I reverse-engineered his work to figure this out.

TemporaryTester said:
This should resolve call audio. Flash in recovery.
I also tried to bake in the cust fix earlier, but it doesn't do anything. Still throws that error.
Credits to @Cloudyfa, as I reverse-engineered his work to figure this out.
Click to expand...
Click to collapse
So, does it fix the no-sound problem? Somebody else tested it?
Does this ROM have the tethering working ok?

dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply

jacktackle said:
dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply
Click to expand...
Click to collapse
Sorry No don't have it.
Sent from my iPhone using Tapatalk

jdfloresd said:
So, does it fix the no-sound problem? Somebody else tested it?
Does this ROM have the tethering working ok?
Click to expand...
Click to collapse
Though it may carry no weight, I've been running this ROM since I posted that fix. I've had no issue with standard, speakerphone, Bluetooth, headphones, rear speaker sound, etc. Mute works as expected too. This hack was reverse-engineered from CloudyG3 (which, I think, is just the sound drivers and profiles pulled straight from the D85020f ROM); it causes the ROM to handle sound in the way that is identical to his.
Native wifi tethering works flawlessly for me.
jacktackle said:
dev,
is it possible to get a tot file for your base rom? which is d855 20i
waiting your reply
Click to expand...
Click to collapse
You can probably find a TOT somewhere on the international G3 forums, but it won't flash onto a D850 due to the model mismatch.

Rom Status has been changed to STABLE

Can you patch this to 20p?
Images are here.
I hope someone dumps D85021l soon, so that we can get VoLTE working here too. I'll update my fixer zip after, unless you want to integrate it into the base zip (which, by all means, do).

Well, looks like this thread and general interest in stock international ROMs has died, but I still use it. Figure someone else does too.
Patched to D85520w. This uses the original D85020f kernel, as D85021-series kernels are incompatible. Modem has been patched up to D85021r, as that does work for some reason.
Google Drive download.
Thanks to @hyelton for the original zip, and all credit for its components allocated as such.
Thanks to @robalm for the D85020w dump.
Thanks to @Cloudyfa for the hack to make D850 sound work.
Thanks to @Yoshi_Guy for the D85021r modem.

Would this still change the model to D855? You know if the Music app bug is solved?
Thanks

plguzman said:
Would this still change the model to D855? You know if the Music app bug is solved?
Thanks
Click to expand...
Click to collapse
No, it should rename it to LG-D850. In-call and normal audio should be functional.
What's the Music app bug? I use the Music app and have no issues.

[PORT][LL ONLY] LG G3 QuickRemote for AOSP

Greetings!
I have ported the latest version of LG G3's QuickRemote.
DISCLAIMER: I won't be responsible for any loss of data or other mishaps resulting from using this port. Always backup before flashing anything. Use or test at your own risk.
Information
Latest QuickRemote version ported
Modified some UI Elements to Material Design
This app will run only on Lollipop-based ROMs.
For reference, please check this thread.
Update (v4.50.19)
Flashable ZIP
APK (For updating)
Older version (v4.40.12) here
Thanks to @RieGo for the original scripts and to @Yoshi_Guy for providing files for the recent update.
NOTE - This port is not guaranteed to run on all LG Devices & other OEM's since i only have G3 on mind while porting this one, so apologies in advance if i may not help in fixing it for your device.

Did you try thisw on a G3 with an AOSP rom yourself? It looks like the only thing changed from the working zip is a newer version of the apk file, with the rest of the stuff in that zip file being exactly the same. It just force closes for me, using xenonHD (09-01-15) on LS990

Yeah i just replaced from there. I only tested it with D855 on CM12.1 so there might be some problems yet. if you can give a logcat, that can help

I'm using Resurrection remix and i have the same problem like the other port for quick remote for AOSP.
When i choose Tv there is no list of manufacturers.Wipe cache/davlik every time but nothing change.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you set selinux to permissive?

hikarisei23 said:
Greetings!
I have recently ported the latest verion of LG G3's QuickRemote. Please test at your own risk.
Information
Latest QuickRemote version ported (as of this thread's writing)
Modified some UI Elements to Material Design
This app will run only on Lollipop-based ROMs.
For reference, please check this thread.
Download here
Thanks to @RieGo for the original scripts.
Click to expand...
Click to collapse
Tyyyyy
Sent from my Nexus 7 using Tapatalk

Yeah i just replaced from there. I only tested it with D855 on CM12.1 so there might be some problems yet. if you can give a logcat, that can help
Click to expand...
Click to collapse
sure, here you go.
Ive tried so many things to get a newer version of QRemote to work on an AOSP ROM, with nothing doing. Ive been using other remote apps in the meantime, but nothing out there is as clean and easy to to use than LG's.
Good Luck!
I do have a bunch of stuff on this phone right now, like xposed, that could be causing my problem. Although the [1-13-15] zip works fine. Maybe the material design changes you mentioned could be it? Ill try it on a clean rom soon and see if i still get the same errors in the logcat soon and let you know.

syndre said:
I do have a bunch of stuff on this phone right now, like xposed, that could be causing my problem. Although the [1-13-15] zip works fine. Maybe the material design changes you mentioned could be it? Ill try it on a clean rom soon and see if i still get the same errors in the logcat soon and let you know.
Click to expand...
Click to collapse
Hmm i've skimmed through the logcat and i havent noticed anything strange, will get back on it later
the changes i made was minimal but i'll look into it. Notify me when you're done testing it on a clean rom

Does not work. Cm12.1. d802

the changes i made was minimal but i'll look into it. Notify me when you're done testing it on a clean rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Your work is fine, the problem was mine. Im not sure what happened to the ROM i was using, but it was messed up. I noticed all of the folders in /data/data had different ou/rwx permissions, among other problems. Anyways, I wiped my whole phone clean and flashed a new ROM, and your zip, and the app runs perfectly!
Thank-you!

syndre said:
Your work is fine, the problem was mine. Im not sure what happened to the ROM i was using, but it was messed up. I noticed all of the folders in /data/data had different ou/rwx permissions, among other problems. Anyways, I wiped my whole phone clean and flashed a new ROM, and your zip, and the app runs perfectly!
Thank-you!
Click to expand...
Click to collapse
Alright, Glad to know it works

works fine with CM 12.1 thanks.

Please before I install it, someone can tell me if in stb there is the brand patrick? Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk

yay, I used flashify on the zip, reboot, then http://forum.xda-developers.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245
juiceSSH for the terminal commands.
then soft reboot cyanogenmod then the manufacturer list shows up!
time to live the good lazy life again with touch screen remote control.
thanks for the port

CM12.1 not take

Works fine on standard resolution and DPI, but force closes on 1080x1920, DPI 380. D855, AICP, 777 R17.

Yes, same here. I am using full hd res and 360 dpi, app force closes. (Cm 12.1)

To those having problems try using this to switch to Permissive
http://forum.xda-developers.com/showthread.php?t=2524485

ahk31 said:
Works fine on standard resolution and DPI, but force closes on 1080x1920, DPI 380. D855, AICP, 777 R17.
Click to expand...
Click to collapse
gok90 said:
Yes, same here. I am using full hd res and 360 dpi, app force closes. (Cm 12.1)
Click to expand...
Click to collapse
AFAIK most of LG's apps crash when your DPI is below a certain point, so yeah, it's not going to be an easy fix if there is.

hikarisei23 said:
AFAIK most of LG's apps crash when your DPI is below a certain point, so yeah, it's not going to be an easy fix if there is.
Click to expand...
Click to collapse
OK, I see, but [APP][5.0.2][IR]LG QuickRemote for AOSP [1-13-15] is working just fine with custom resolution and DPI.

Do we have a Nexus-like ROM?

I've searched for it but I haven't found yet. Can anyone help me?
I know there are a lot of AOSP based ROMs for our device along these threads, but I mean a different brand of "pure", something more like Nexus phones, which would contain basically only the Google major apps installed. Has anyone done it yet? (It is even easier to do than porting an AOSP, as it would consist in removing the maximum Motorola stuff and adding Google stuff to the STOCK).
Thanks in advance.

radichification said:
I've searched for it but I haven't found yet. Can anyone help me?
I know there are a lot of AOSP based ROMs for our device along these threads, but I mean a different brand of "pure", something more like Nexus phones, which would contain basically only the Google major apps installed. Has anyone done it yet? (It is even easier to do than porting an AOSP, as it would consist in removing the maximum Motorola stuff and adding Google stuff to the STOCK).
Thanks in advance.
Click to expand...
Click to collapse
Try NX Rom
Sent from my MotoG3 using Tapatalk

Nope aosp 6.0 hasn't come out yet for osprey we only have aosp 5.1.1

http://nxrom.us/motog3.html

NX Rom is about as close as your going to get to Nexus-like... but like it's on steroids.
If you are meaning a really basic, plain AOSP based ROM like Chroma, Plain-Andy, or Purity, then nope... No one has built a striped down speedy, battery friendly demon for the G3 based on Marshmallow. I contemplated building Purity ROM like I did for the LG G2 but I just never got enough of a wild hair to do it.

Need Nexus Rom for merlin

vaibhav800 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Moto G Turbo Edition support VoLTE it's great
..
Click to expand...
Click to collapse
Sorry no offence, but it isn't related to this thread I think.
Broadcasted from Zeta Reticuli

Well, I use Krexus AOSP. Its literally the most stripped down Rom I've ever used. Is a 205mb download, comes with the absolute basics to get you up and running. No browser, no calculator, no gallery. Just the framework of Marshmallow, and a ton of potential. Its essentially bug free, and FAST! After initial install, and one reboot.... I show 515mb of free ram on my 1gb model. It also boots in about 15 seconds from power on, to your home screen. This can be further decreased with L-Speed or PBM scripts to speed up boot by removing the boot screen animation.
Its even described as the closest thing to a nexus rom you can get by its developer. And I swear by it.
You'll need to get SuperSu if you want to root it, run a barebones Gapps, and install a few things you might want like a browser, file manager, and text message app.
I think once its installed, theres about 7 apps on it. Its built for people who want a true custom rom. You don't have to download some 350mb behemoth of a rom with every single option available. Krexus is literally just a framework, to allow you to add whatever you'd like, and forget the rest.
Try it out, you won't regret it.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
The reputable Flashhhh is now the maintainer of it.
I highly recommend downloading his version here: https://www.androidfilehost.com/?fid=24591000424941605
As the original version had some problems. So don't download the OP's version in the first post download link. Use the link above to get the better version. ITS FAST!! ITS SMALL!! Its built for those who don't want or need a ton of options. You can literally build it exactly how you want it.
From the Krexus AOSP description:
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
Click to expand...
Click to collapse

AOSP-OMS is a pretty new ROM but with a "Stock" gapps package it would be almost exactly like a Nexus ROM.