yashsingh1/xdaforums huggingface dataset:
[Nexus 5 General] opssemnik:
i agree with you, but look at the nexus 4, it definetly could have received MM, which in fact runs better than 5.1

Edit:

Also about the image posted: its just a modified build.prop version of the nexus 6 one, it isn´t a port neither will work, we dont have a kernel, the image is too big for you system partition, neither the fundamentals, the drivers, proprietary apks, etc are there (compared with winmerge and md5)

edit: some libs were changed but not every, and we still miss a kernel, atleast an updated ramdisk for one
[Nexus 5 General] jabza:
That error is indeed a result of your heap size being to small, you're correct. However, you really cannot build the N preview. We don't have the source. Maybe you can build the kernel, but that won't do you any good - the actual system built will be Marshmallow. I'd also be surprised if the vendor blobs from M worked in N. You'd need all the other repos (system, framework, and so forth) to have the N source which we do not have.

Unfortunately, the only way for us to get the N preview running on the Nexus 5 is to port it from another device.
[Nexus 5 General] Raienryu:
It really was the heap size error. It got fixed when I declared heap size as 4GB and sucesfully built. But doesn't boot.

Firstly, I'm going to try to get some logs somehow.

I found this in the last_kmsg. Does this mean that we need permissive to boot?

[ 1.923077] init: SELinux: Could not load policy: Invalid argument
[ 1.923194] init: failed to load policy: Invalid argument
[ 1.923242] init: Security failure; rebooting into recovery mode...

If so, it's a prebuilt kernel, how do we make it permissive?
[Nexus 5 General] johngalt1:
Look, either belmox is trolling you guys, or he's trolling himself. Either way it's a waste of time.

For a real port, you probably wouldn't need to update kernel since we don't have new blobs. What you would do:

Remove Shamu blobs

Diff Shamu N ramdisk to M ramdisk

Make necessary changes to Hammerhead ramdisk

Add Hammerhead blobs

Cut down system size

See what happens in boot, possibly run into issues from libc and/or libm routines for Shamu chip

Edit: Add other built blobs from M (hardware/qcom ****) due to kernel differences (this might get out of control with deps though).

Edit2 : oh yeah, forgot about sepolicy.
[Nexus 5 General] :
Is there a guide that you could send me to learn how to do this?
[Nexus 5 General] neel_bat_beyond:
I'll be happy to try the zip! upload it if there is any progress!
[Nexus 5 General] Raienryu:
Hi. What's the status of your build?

I've tried building too, initially faced some issues and then finally made a build, but just like yours it shows the Google Logo and then recurs that and then goes back to recovery.

Although I did notice this in the last_kmsg logs

[ 1.923077] init: SELinux: Could not load policy: Invalid argument
[ 1.923194] init: failed to load policy: Invalid argument
[ 1.923242] init: Security failure; rebooting into recovery mode...

So maybe we need to try building kernel as permissive. So I guess we need to make appropriate changes in BoardConfig and device makefiles and make it build from kernel source available along with androidboot.selinux=permissive.

Though I've read through the thread and seen that many people are saying that compiling from source is useless, so I'm wondering whether we should continue or leave this approach and just try to port.

One thing I have a question about porting guys,

Since Nexus 6 is the only non 64 bit device, you people are using that as a base to port.

Assuming we use the blobs from our own device

But what about the framework and all those apps? Isn't the dpi different? How to get them to work properly? I've never 'ported' any ROM so I have not much experience in it.

Update:

Just a small update, I've taken the boot.img that came out of the build and unpacked it in Android Image Kitchen, changed lines to ro.secure=0 and ro.adb.secure=0 to make it permissive. Even then still same, boots to splash screen and then loops twice or thrice and then comes back to recovery. So I guess google did just push non working trees to git. Maybe porting is the only way then.
[Nexus 5 General] johngalt1:
Yes, as said earlier there's no source. Typically everything gets tagged when kernel source gets pushed for license compliance.

A lot has changed in AOSP since ports were commonplace though. We now have more chip-specific optimized routines in libc/libm, so porting from shamu may not be as easy.

Only hope (other than leaked source which has never happened) would be a port.
[Nexus 5 General] kicksilver:
Guys, I'm gonna ask again:

Is it possible for a developer to make a flashable ZIP for us to sideload, to upgrade do Android N, as if we had received the OTA from Google itself?

Or will it block the installation because it's not signed by Google, or something?
[Nexus 5 General] starkly_raving:
Different boot.img

Different libs

All sorts of different dependencies...whole new API...building a port today isn't as easy as it used to be...it'll take a seasoned developer for this port or we'll just have to wait till source is pushed to AOSP.
[Nexus 5 General] kicksilver:
Actually, I was talking about the official release.

After it is uploaded to AOSP and all..

Enviado de meu Nexus 5 usando Tapatalk
[Nexus 5 General] Raienryu:
I'm guessing the stock recovery will deny flashing unsigned zips.

The official release, if and when it comes will definitely be flashable as an OTA.... since it's official
[Nexus 5 General] starkly_raving:
That'll be late summer early fall. Google I/O isn't till May. So we won't likely see a source push till way later (historically its been late summer/early fall)
[Nexus 5 General] kicksilver:
Well, I kinda expected that.

I meant, if Google doesn't update the N5. Of course their official zip will be flushable...

Yeah, I don't expect to be running M before September (oficial or not)

Enviado de meu Nexus 5 usando Tapatalk
[Nexus 5 General] frikakwa:
[MENTION=1050103]sykopompos[/MENTION]: people here need your help for porting! ;) Please... give them some of your magic! :)
[Nexus 5 General] ast00:
Unfortunately he can't help us. In the Frank thread, he said he no longer has the device and he doesn't have enough time either.
[Nexus 5 General] ...Awesome...:
Unfortunately till we get a kernel this preview will not boot.
[Nexus 5 General] blemish31:
What are the options to get that kernel? Build one from scratch? Modify the marshmallow kernel?

Enviado desde mi iPad utilizando Tapatalk
[Nexus 5 General] Furrydaus:
We do not have anything to get Android N Preview Running. If you want one, you'll need to wait for a few months until a developer does it. Then again, no developer is that dumb to be going around code to try and get a small preview to run on the Nexus 5. Not to mention the preview is not all that special having only Android M Apps and minor modifications added to it. It's not worth it and will not happen till we get a KERNEL that works with Android N.

Even if Android N Doesn't come for the nexus 5, you can just simply wait for the developers to work on the more EASILY ACCESSIBLE and LESS BUGGY Source code to get Android N running on the Nexus 5. The Nexus 5 is already very fortunate to have loads of source code that can help out with getting Android N on it.

All of you here who think you can get Android N Preview running are chasing something that needs a high level of technical skill to do. Stop chasing it and just be patient for once. You all are like trying to bend steel with your own bare hands.
[Nexus 5 General] issamf666BSC:
Hello

I can test on my phone you want to i don't have any experience at porting and stuffs like that im ready to try that on my phone
[Nexus 5 General] blemish31:
So let's wait, thanks for the answer ;)

Enviado desde mi iPad utilizando Tapatalk
[Nexus 5 General] nihad15:
But, I need it now ? I can't take it anymore.

But seriously tho you are absolutely right.
[Nexus 5 General] :
Are you ever going to come back and update us?
[Nexus 5 General] dennes544:
There is NO source code for N!!!
[Nexus 5 General] starkly_raving:
There's nothing to update. Gonna just have to wait.

Sent from my Nexus 6P
[Nexus 5 General] :
Damn dude salty?
[Nexus 5 General] asacado:
I really wish that these nexus devices just didn't fall off of support. The N5 has hardware that can support anything that google can legitimately throw at us. Are they really so blind to see that a community would support a device for years on end? HTC HD2 is a great example. I really hope that my N6 will get support for a long while, but I can only rely on the following version.
[Nexus 5 General] starkly_raving:
Two years of updates...Google has established that now. Hard for them to hype and market moderate hardware updates without the hardware releasing with the next major software release. Its about money. Why would a Nexus owner go update a capable device if they have the same software? $$$$ its a passive aggressive way to make us keep buying a phone every couple years.
[Nexus 5 General] bonaries:
I hope google wouldnt let nexus 5 users down. The phone still has a lot of goods in itm
[Nexus 5 General] prog19:
If google doesnt update we will get at least an aosp version of the rom. In my nexus 4 i run the fake nexus and its even more updated than the cataclysm version im running in my n5

I'm a Brazilian without English Course, sorry and be comprehensive :)
[Nexus 5 General] vikrant699:
Yep I got it to building too, but doesnt boot, logo and then back to recovery, though with permissive marshmallow kernel, it took me to a black screen ahead of boot logo and then back to logo :3
[Nexus 5 General] Dungeon47:
In case you didn't know, Cataclysm is dead. Don't expect updates soon, if ever.
[Nexus 5 General] starkly_raving:
Again...you guys are looking at it from a users point of view. Google is a business. Their business is selling the platform of Android on their latest and greatest hardware. If their 3 year old former flagship can run the new OS perfectly and doesn't require a Nexus user to upgrade hardware...well its just not good business (look how bad the Moto N6 did in sales compared to the N5 & the 5X/6P) The nexus program is kind of set up like old carrier contract deals...you get your Nexus...which was/is cheaper than almost any OEM flagship of similar specs and for 2 years you'll get a full version updates...then security patches there after. They don't want you to keep your phone for over 2 years...they want you to buy the new one...and that's that. Doesn't matter if it can run the new version or not. We've had 3 full letter releases since launch. If we don't get an official build then I honestly won't complain. Its had a good official run.
[Nexus 5 General] imor:
Nexus 5 is and will be the Nexus Device which made Nexus Series what it is today.. Google was supposed to have that in mind and proceed with with a Nexus 5 N developer preview.. Not mention they were supposed to provide some support including the Nexus 6 to install an imprint sensor as they did on the first Video showing the technology.. If I could fit an imprint sensor on my Nexus 5 I would keep it for another 2 years minimum.. I am really frustrated Google choose to go with a so "cheap" decision and let Nexus 5 out of the N preview..
[Nexus 5 General] starkly_raving:
But again they have honored their own guidelines and commitments. As users we can be disappointed but they have held up their end of the deal.
[Nexus 5 General] imor:
I understand what you are saying, yet, Google is wrong here.. Nexus devices should be getting updates until cannot freaking move.. I bet balls deep that even Nexus 4 would run Android M smooth as butter yet they decided to stop supporting the device just to push people buying Nexus 5 and 6, the same thing they are trying to do now with 5X and 6P.. That is so immoral.. Nexus 5 still remains a beast, and it should be getting updates until the point that is no more applicable due to hardware limitations.. So far, Android N is just an update to M, nowhere similar to the KK to L.. Anyway, Almost 2 years with my Nexus 5 and I still feel and love it like day 1..
[Nexus 5 General] starkly_raving:
I completely agree its an amazing device and has a huge following. Probably the biggest following since the Nexus One. "But" again Google did what they said they'd do. I mean the average Joe would never update hardware if they got never ending guaranteed software support. Technology shelf life is short and in all fairness Google has done a lot for people who participate in the nexus program. A lot of OEM flagships that are a year newer and nearly double the cost are barely getting past 5.1.1
[Nexus 5 General] rmean:
You're right about that "push to buy". And that is why I'm not upgrading to 5X/6P. I'm more than satisfied with the N5, and I'd rather do without N than throwing away my baby :D
[Nexus 5 General] skiarte:
I am confident, the Nexus 5 will be the first mobile phone to receive 4 android versions!
[Nexus 5 General] JackNexus:
Hello everyone, my first post here!

Yeah, I despise it when companies do such a tactic. To be honest, I think the 5X is too overkill imo when you consider that even if the 5X's processor performs a bit better than the 5 it still uses the same 2GB RAM the 5 uses making the RAM the heftiest limiting factor for the 5X's CPU. As such, I don't see a lot of drastic differencs between the two in specs laden other than the 5X being 64-bit (And I don't recall any apps that I've seen that are only 64-bit compiled). That's why I'm sticking with my 5 and I why I don't see an excuse for ditching a 5 over a 5X. The 5 is still able to see another Android version, but because of the "push to buy" tactic it looks like we have to make the N lemonade ourselves using these lemons unless Google calls mercy rule.
[Nexus 5 General] opssemnik:
5*, the 2012 nexus got 4 updates (not counting revisions) and the 2013 n7 already got 4 versions too
[Nexus 5 General] prog19:
I'm aware, but im so busy in the last month that I couldnt search for another rom to flash. Also cata is so stable that I dont need to worry. But thanks anyway

I'm a Brazilian without English Course, sorry and be comprehensive :)
[Nexus 5 General] starkly_raving:
Look guys...Google is doing what they said. 2 years of major release updates...security patches after. You can't expect indefinite updates, we can feel left out, hurt or betrayed but they did what they said they'd do(Not like Motorola but that's another story). I'm not denying the N5 is great, it is and is more than capable, no doubt. I love mine. But let's think real world ...a three year old piece of hardware is a relic it the world of technology. You have to think about r&d, resource and personnel to support a 3 year old phone. I just don't think its realistic. Considering the Next Nexus (or pair of Nexus) is on the horizon. But whether there's an official release of N or not I'm sure there will be community builds.
[Nexus 5 General] LaserChicken:
Google's two year policy, while honored, could use further review. I don't think anyone is suggesting indefinite support--but perhaps, as the hardware is still relevant, support should be extended. I think it's worth the positive PR to recognize excellent hardware and loyal customers.

That said, over all, I'm a satisfied customer when it comes to the N5 and Android OS. So, it would be nice to see the extension, but I wouldn't jump ship over it.
[Nexus 5 General] pavik62:
Enough to philosophize! Let's do ROM. I can go to bootanimation. Can Logcat. Who can read can give a Logcat.
[Nexus 5 General] Raienryu:
Exactly my thoughts too. Was just about to hit submit reply when I saw you already made your post. :D

Definitely looks like art is not able to run dexopt on the apps after installd was called crashes all services fail, and then art calls installd again, system crashes again and this seems to be continuing infinitely

Have you (pavik62) tried porting it from Nexus 6?

if so What all changes did you do?
[Nexus 5 General] Santhosh M:
I have fixed the init panic of kernel in my device ( i am trying for my sd615 device) and currently in bootanimation. I could see someone posted here the kmsg and it had the same init panic as mine.

I will give a shot for hammerhead this week or so once i succeed for my device
[Nexus 5 General] J0SH1X:
If you fix the error with art would be nice if you could share the solution working on a n4 version

Gesendet von meinem LG-D855 mit Tapatalk
[Nexus 5 General] kontini:
Can anybody try to flash xposed framework? Maybe its runtime lib does the magic! :fingers-crossed:
[Nexus 5 General] iorem:
android.googlesource.com/device/lge/hammerhead/+/android-n-preview-1
[Nexus 5 General] F4uzan:
I'm not being rude or harsh here, but that has nothing to do with making N bootable for the Nexus 5, that's just the device tree being autotagged with the n-preview-1 tag. You still wouldn't be able to build anything with it.
[Nexus 5 General] cell2011:
I have an N4 too please share the solution once it works for N5
[Nexus 5 General] dekefake:
Take both Shamu N and a stock AOSP for Nexus 5.

Replace app, priv-app, media, framework, fonts, etc/permissions from N5 M AOSP by Shamu N Rom

Remove Shamu M app/Bluetooth and app/NFCNci by Nexus 5 ones (to get NFC and Bluetooth working)

Add back Nexus 5 M blobs ==> github.com/MrTumbles/android_vendor_lge/hammerhead/proprietary (add the blobs u deleted using Shamu app, etc...

IMPORTANT - For libs !

Use that libs from Shamu

lib/libart.so

lib/liblog.so

lib/libcutils.so

lib/libandroidfw.so

lib/libnativehelper.so

bin/app_process*

(LIST FROM XPOSED LIBART SHARED_LIBS)

Stock M kernel. Might boot. Get a logcat

Bonus : use Nexus 5 framework-res.apk/res/xml/power_profile.xml and storage_list.xml and replace shamu's framework ones. (to get proper mounts and power mgmt)
[Nexus 5 General] MounirHero:
"android sdk= 23"

android N is "24"
[Nexus 5 General] dekefake:
N is still 23 for now. Did u checked Shamu N build.prop ?
[Nexus 5 General] fix1147@gmail.com:
Do you really think they understald russian?

Ты серьезно думаешь они тебя поняли?) (the same)
[Nexus 5 General] TonyStark R.I.P.:
[MENTION=6046038]Ross Korolov[/MENTION] [MENTION=7345747]iorem[/MENTION] [MENTION=7346316]towell[/MENTION] [MENTION=5499742]dennes544[/MENTION]

Per XDA rules please...

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).​

Like this:good:

Thank you.
[Nexus 5 General] dennes544:
Why selinux is still works in enforcing mode after i change it to permissive? I've set ro.secure to 0 too, still the same, stuck at gatekeeperd service
[Nexus 5 General] dt3s:
Its possible that Google is only releasing previews to the newer devices for now and will still release N to the Nexus 5 I believe a similar thing happened to the Nexus 4
[Nexus 5 General] Santhosh M:
I just booted the android N preview on my sd615 device...It doesn't have any N features..Google has not pushed any of it's features to the preview branch...Even the security patch level is dated as late as Dec 2015..It's N without N features (basically marshmallow)

So don't bother much bringing it up...You can't taste N features via the preview branch :)
[Nexus 5 General] dennes544:
That is not N at all! Google spent publish their code until official release! So you didn't compiled "N without N features", but just latest Android M!

Please stop trying to compile it from source code, or at least write here about it

---------- Post added at 07:12 AM ---------- Previous post was at 06:27 AM ----------

Everybody who understand what is porting! Write to my PM your email address, I will add you to our hangouts conference
[Nexus 5 General] Sub-Zero[HammerHead]:
Why does Google do that!! N5 is soo much capable of Android N
[Nexus 5 General] Santhosh M:
It is not latest M....if you have seen the code you would know what has changed...The entire build system has now been modified with aosp ninja which is not the case of latest android M tag and lot of other source level changes...I had to modify all my device level support to adapt to the new code level changes. If you take the framework side too it's the same case
[ONE Android Development] MZO:
SlimROM is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.

The entire SlimTeam works together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.

All of the sources can be publicly viewed through GitHub and Gerrit.

/* #include <std_disclaimer.h>
*
* Your phone's warranty is valid
* This is a custom ROM developed by Warrior1208.
* You are flashing this on your OnePlus One at your own peril.
* I am not responsible for hard bricks, damages to SD Cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* I would definitely help you out if you are stuck somewhere, provided that you give
* me clear details of the mishap.
* Don't ask for ETA's cause there is a thing called "LIFE" outside XDA.
*/

WHAT WILL BE INCLUDED:

Android Marshmallow

Slim Center

Slim Launcher

Slim File Manager

Slim Heads Up

The Real Dark Slim User Interface

SlimPIE (inspired by ParanoidAndroid's PIE with a light touch of Slim)

Smart Card Service

Adaptive Backlight

Adaptive Brightness

Smart Lock

Privacy Guard

Sounds Tweaks(Audio FX and Music FX)

Status Bar Tweaks

Battery Saver Mode

Removed Bloatwares

Notification Reminder/Snoozer

Drawer Shortcuts

Lockscreen Shortcuts

Custom Quick Settings Tiles

Improved Performance

Camera - True View

Camera - Smart Capture

and Much More!

HOW TO INSTALL:

1. Download the ROM and the GApps and place them on your SD Card/Internal Storage.

2. Reboot phone to recovery.

3. Wipe data, cache(factory reset), dalvik/art cache and system.

4. Flash the ROM and GApps.

5. Reboot System. (First boot takes 5-6 minutes. Be patient.)

SOURCES:

My GitHub

SlimRoms Website

Google+

CREDITS:

SlimROMs Team

[MENTION=4139665]martinusbe[/MENTION] for kernel

[MENTION=4570506]indian84[/MENTION] & [MENTION=5165039]Setting.Out[/MENTION] for screenshots and testing

XDA:DevDB Information

SlimMM bacon, ROM for the OnePlus One

Contributors

MZO

Source Code: https://github.com/SlimRoms

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Latest CM13 FW

Based On: AOSP

Version Information

Status: Alpha

Created 2016-03-09

Last Updated 2016-03-09
[ONE Android Development] MZO:
Reserved

Download here
[ONE Android Development] MZO:
So far the buglist contains

No recents (use my navbar mod from android file host)

No Data

No NFC

///

NAVIGATION BAR FIX
[ONE Android Development] Setting.Out:
Some screenshots
[ONE Android Development] DooshPastesh:
Hey, nice job! Another good software! (Disclaimer is for Samsung galaxy sII :D)
[ONE Android Development] MZO:
Pure *_* I love this purit

Thanks for screenshots
[ONE Android Development] MZO:
That's what happens when you get lazy. Fixing it ... Was straight copy paste lol
[ONE Android Development] lapapunk:
Hi. It's support f2fs?
[ONE Android Development] MZO:
No
[ONE Android Development] David:
what firmware you using? mine cellular data doen't work
[ONE Android Development] MZO:
I'm using 0122 firmware. It works fine on Marshmallow. Cellular data is different, do you have correct APNs? If you have reception then it's not about firmware.
[ONE Android Development] Setting.Out:
Care to link your firmware?.. I have cell service, but no data, already checked settings, reapplied apns ect..
[ONE Android Development] David:
yes i have correct apns , what i must do now ? :rolleyes:
[ONE Android Development] MZO:
https://www.androidfilehost.com/?fid=24411628330025738
[ONE Android Development] KenjiHannya:
Tnx lets test :D
[ONE Android Development] anbinhv:
Thanks [MENTION=6304619]MZO[/MENTION]!

Does this rom have feature Double Tap To Sleep on lockscreen and Vibrate When Connected?