Database Develop

[Q] Official ICS Build Incoming?

I have a cousin who works with B&N, and he says that they are rushing to get the 3.0 kernel on the NC to accompany their locked-down skin. He says that there are some incompatabiliies, but that they have made progress. What are your thoughts? Is he crazy? Are we ever going to get a proper ICS OTA?

If B&N drops 3.0 kernel source for the Nook Color, the devs here will be quite happy because the current old kernel is the major impediment to ICS on Nook Color.
You sure they aren't doing this just for the Nook Tablet?

3.x is honey comb, not ICS. They'll prolly skip that all-together.

gallahad2000 said:
3.x is honey comb, not ICS. They'll prolly skip that all-together.
Click to expand...
Click to collapse
Talking about the linux kernel.

It makes little sense to me for them to update the core Android OS and Linux kernel if their reader, custom apps, and the apps in their store work fine with Froyo. But if they're going to keep selling the NC as the budget media tablet model for a while longer then a more up-to-date Android version makes sense in avoiding any possible compatibility issues down the road that could prevent them from seamlessly bringing the latest and best versions of Android apps across to the B&N market. Their separate B&N market wouldn't be very sustainable or a good selling feature if they had to only offer older versions and/or ask developers to add backporting compatability fixes for a two year old version of Android. Then again, that's just a lot of speculating on my part

I don't have hope for that, in fact, I doubt it.
They just released v.1.4.1 and it still is Froyo, I don't think they implement ICS for NC.

I could actually see them doing this just so that it will be easier for devs to convert their already tablet friendly ICS apps for the BN market.
---------------------------------
Sent from my LG Optimus V using Tapatalk

I would think they would like to keep the operating environment the same across units (if possible). This will cause less customer confusion/dissatisfaction and fewer support issues. Apple IOS is a good example of this IMO.

gmanvbva said:
I would think they would like to keep the operating environment the same across units (if possible). This will cause less customer confusion/dissatisfaction and fewer support issues. Apple IOS is a good example of this IMO.
Click to expand...
Click to collapse
Apple allows old devices to upgrade to newer iOS versions (my gf's 3g is running iOS 5). They just cripple the features they don't want those devices to have (siri, folders, etc). Apple's relative lack of issues comes from controlling the hardware (no powerVR, tegra, qualcomm incompatibilities, short driver list), OS (no carrier or manufacturer modifications) and app store (too many bugs and your app is gone).
I doubt B&N would drop the full functionality of ICS on their customers (especially when they've fenced them in from froyo). ICS would open the door to tablet-centric apps which would help them compete with Amazon. It will most definitely come to the Tablet but I wouldn't expect it to come to the Color (since they need to differentiate the models to justify the price difference).

Would be great if they did release it, but lets face the truth, its unlikely.
If you guys want ICS your best bet is buying dalingrin and / or fattire a beer.
Sent from my NookColor using Tapatalk

MrColdbird said:
Would be great if they did release it, but lets face the truth, its unlikely.
If you guys want ICS your best bet is buying dalingrin and / or fattire a beer.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Maybe true, but if this works it would certainly give dalingrin and fattire some help with the issues they're having, not to mention speed up the entire process.

Limvot said:
Maybe true, but if this works it would certainly give dalingrin and fattire some help with the issues they're having, not to mention speed up the entire process.
Click to expand...
Click to collapse
If what works? I'd love to have official ICS on my NC, but as others have said, they're still using a fluffy coating on Froyo. No GB and no HC means ICS is highly unlikely.
Now what would be very nice would be an updated kernel, as well as some direct contact with B&N techs about drivers for the chipset and other hardware. But I find that to be unlikely.

The newer Nook Tablet is based on Gingerbread, isn't it? Perhaps they're working on this first and foremost to crank out a third future device that supports APIs from ICS such as fragments. The updated code would then trickle down to Nook Tablet and possibly eventually NC.
Sent from my Nook Color!

zombieflanders said:
If what works? I'd love to have official ICS on my NC, but as others have said, they're still using a fluffy coating on Froyo. No GB and no HC means ICS is highly unlikely.
Now what would be very nice would be an updated kernel, as well as some direct contact with B&N techs about drivers for the chipset and other hardware. But I find that to be unlikely.
Click to expand...
Click to collapse
No HC doesn't mean anything as it was not open source... This is not completely unthinkable. Remember the NC was on 2.1 before the 1.2 release where they upped it to 2.2.
Sent from space

votinh said:
I don't have hope for that, in fact, I doubt it.
They just released v.1.4.1 and it still is Froyo, I don't think they implement ICS for NC.
Click to expand...
Click to collapse
Of course, 1.4.1 came out just before ICS source was released, so maybe B&N figured they do a quick patch of the existing ROM, rather than go through all the work to do a rebuild on GB and then to ICS...

any news/rumors about this?

speedfreak007 said:
any news/rumors about this?
Click to expand...
Click to collapse
Other than slow but steady progress on the CM9 build (and no new releases for now), no.
traumadog said:
Of course, 1.4.1 came out just before ICS source was released, so maybe B&N figured they do a quick patch of the existing ROM, rather than go through all the work to do a rebuild on GB and then to ICS...
Click to expand...
Click to collapse
You have more faith in the B&N corporate staff than I do, but your optimism may be warranted, given that the NT doesn't seem to be totally ignored by the press in the same way the NC was.

zombieflanders said:
... You have more faith in the B&N corporate staff than I do, but your optimism may be warranted, given that the NT doesn't seem to be totally ignored by the press in the same way the NC was.
Click to expand...
Click to collapse
I wonder how much other integration B&N is looking for with other content providers to match what Amazon is doing. I would think upgrading to ICS would make some business sense, in that with a fresher underlying OS, you might be able to keep app developers in the fold working on the NT.

cmstlist said:
The newer Nook Tablet is based on Gingerbread, isn't it? Perhaps they're working on this first and foremost to crank out a third future device that supports APIs from ICS such as fragments. The updated code would then trickle down to Nook Tablet and possibly eventually NC.
Sent from my Nook Color!
Click to expand...
Click to collapse
From what I understand... The new Nook Tablet has a locked bootloader, more or less precluding it from easy rom replacement.
Though, perhaps I have been misinformed.

Yoinx said:
From what I understand... The new Nook Tablet has a locked bootloader, more or less precluding it from easy rom replacement.
Though, perhaps I have been misinformed.
Click to expand...
Click to collapse
Difficult if not impossible for 3rd parties providing roms but not for B&N. They have the security keys allowing them to provide whatever rom they choose within the hardware limits.

Kit Kat's memory optimizations for our nooks?

Hey all. So it's looking like 4.4 has some memory management changes for devices with low ram. Think it would help our tablets? http://www.androidguys.com/2013/10/31/notable-features-android-4-4-kitkat/

Yes, but only after we move to android 4.4. We are on 4.3 now.
Sent from my BN NookHD+ using xda premium

Yes, it should improve performance on all devices with KitKat, compared to devices with earlier Jelly Bean builds. However, as leapinlar mentioned, only when we move to Android 4.4. We're on Android 4.2.2 right now stably, with Android 4.3 nightlies.
A little off-topic, what I'd like to see with Android 4.4 is devices still stuck on Gingerbread with dual-core processors and 512MB RAM updated to KitKat. That would be astonishing, but perhaps a little too much to ask for.

I really hope to see kitkat come out for the hd real soon and hopefully the optimizations will give us a decent performance boost

I imagine the biggest hurdle will be getting the drivers for the components that make up the device such as the TI SoC. Remember, Google isn't updating the Galaxy Nexus, even though it would likely breath new life into the device, and I heard it's because of the lack of driver support from TI since they are no longer in the SoC business

Galaxy Nexus already has some unofficial 4.4 ROMs. Motorola Defy also got one. And it looks like TI released new drivers for omap4.

leapinlar said:
Yes, but only after we move to android 4.4. We are on 4.3 now.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
I'm currently on the RC2 10.1.3 - pretty satisfied with it actually, just curious about a time frame on 4.4, that is, IF it becomes available for the HD+. Any idea/guess?

sequoia464 said:
I'm currently on the RC2 10.1.3 - pretty satisfied with it actually, just curious about a time frame on 4.4, that is, IF it becomes available for the HD+. Any idea/guess?
Click to expand...
Click to collapse
i believe both carbon and cyanogenmod teams are working on it.
obviously asking for timeframes isnt a thing when people have actual jobs and lives which come first.

gotbass said:
i believe both carbon and cyanogenmod teams are working on it.
obviously asking for timeframes isnt a thing when people have actual jobs and lives which come first.
Click to expand...
Click to collapse
Thanks .. Always interested in these new ROMs.

[Q] What is the situation of CyanogenMod?

CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/

csfrank271 said:
CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/
Click to expand...
Click to collapse
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
Thank you, I was just wondering about the state of the official ROMs, it seems like the P880 has been forgotten about by CM
But, as you say, we are very lucky to have these fantastic devs building even better custom ROMs

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure

JoinTheRealms said:
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure
Click to expand...
Click to collapse
Hopefully we can have the issues fixed
Can't wait to see the community development though, the new Android RunTime looks very fascinating :3

why dont u enter cyanogenmod and see with your eyes ? anyway. of course we dont see any support. its a miracle that we had that much support too. who will support a phone which doesnt even has the support of the official company ? LG only had 4.0.3 and 4.1.2 and thats all. isnt it already a miracle that we have 4.3.1 ? and we have also so many good developers that work for 4.4 ?

I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app

Zhus06 said:
I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app
Click to expand...
Click to collapse
Everyone wants KitKat because... Well, because it's new! Why not? I believe that pushing one's expectations beyond what is already achieved represents a strong impulse to improvement. Experimenting, trying new solutions, feeling the awesomeness of something that did not exist before is a powerful spring to the change, the change in itself is something that animates the developers and makes them work with no reward as if this was their job.
It has happened with all Android versions, and always there had been someone who felt amazed and wondered why should we need a new version.
kK can be (and probably is, but who am I to judge) one of the worst Android versions, but I am happy to see people trying to overcome all the problems related with making it work on a relatively old device, and I am happy if by testing what is being developed, and by giving my opinion I can be of some help to somebody.
Want to call it a game? Why not! Want to consider people like me as grown up kids that need something to play with? Well, yes, I am, and will always cheer a new Android version working on one of my devices with grateful heart.

Ricardo Cerqueira is no longer the maintainer of our device?
there is no one who will replace him?

It should be possible to join the CM team, if the 4.4 is running.
The tegra3 problems will hopefully not be a trap for it.
If there is a maintainer who can update CM once, there will be no real reason not to get official support.

Good news everybody!
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone

Bye Bye CM !

DarkFantasy6 said:
Bye Bye CM !
Click to expand...
Click to collapse
Why do you say that? :-/

csfrank271 said:
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone
Click to expand...
Click to collapse
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!

faabak said:
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!
Click to expand...
Click to collapse
Yes, hopefully!
But hey, a stable CM10.2 would even be fantastic, the community devs would appreciate it surely

We never got the m1 and stable so i hardly belive it that we get cm11. And without a good 3.4 kernel source from lg we wont feeo many adventafes of 4.4. but the awesome awesome optic would be nice Maybe im going to buy a Nexus 5. Im so frustrated of my lg optimus 2x and 4x. ONE update -.-

[Q] Android L (5)

How soon do you guys think a ROM will be made for Nook HD/HD+ after Android L releases? Any guesses? Cyanogen have done a great job with 4.4

That's just going to be a lot of assumptions

sandsofmyst said:
That's just going to be a lot of assumptions
Click to expand...
Click to collapse
Probably why you were the only one to reply xD Thanks man

Just don't like to see 0 replies. That said, there's one now and then that I won't reply to. However, L is of much interest to me and some of the supposed improvements will hopefully be great. Plus L on the nooks would hopefully be even better. So I share your enthusiasm.
The release time could be shorter or longer depending on the amount of porting work to be done. There's other variables too. But someone else might also before cyanogenmod which would be fun.

Thanks for the reply, I agree on L being even better on the Nook varieties. Can't wait!

I was finally starting to look into bumping stock off og my HD9 and saw this... guess I can wait 4-6 months for this to all take shape... I wouldn't want to lose my progress in PvZ2 at this point anyhow

My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
With the nook being the nook... you could be right. The latest tech really makes android smooth, not android on the older tech.

OSs don't tend to get faster as they get fancier and the latest tablets and phones have much faster hardware (and more RAM).

Well I mean take a look at the iPhone 4S, it used to be able to run IOS 5 and now it's up to IOS 8 and it's still pretty fast. These companies need to focus as well on making the newer OS work well with older devices. I mean the HD/HD+ is only 2 years old...

Corkerman said:
the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
It might be 2 years old but the hardware was never really all that great as it wasn't a top-of-the-line tablet when it came out.
Anyway, that's why I'm hoping 5.0 does something to improve performance, but wouldn't expect miracles from it if anything at all. Android just does better on newer hardware.
_________________________
Looks like cm11 m12 improved responsiveness a noticeable amount and finally too. Still not the same amount newer hardware would cause but a welcome improvement.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster than 4.4.4_r2. With kitkat, art sped up menus and navigation, but not really much else. Lollipop is all art - no dalvik option - and not only are menus and navigation faster, but it seems to speed up apps as well, mainly the Chrome browser. I've been using Lollipop for a couple of weeks now, compiled 5.0.0_r2 with 4.4.4 blobs, and I've been pretty impressed. I just built 5.0.0_r5 from source yesterday with the new 5.0 blobs they released. I haven't had time to install it, but I would imagine the performance to be the same as 5.0.0_r2.
Unfortunately, the Nook HD depends heavily on CM source, and quite frankly, it's a little above my expertise. So I'll just have to wait for verygreen, bokbokan, and leapinlar to give us a lollipop build for the Nook HD and HD+.

cahrens said:
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster
Click to expand...
Click to collapse
That's great to hear it's indeed faster even though it's on a Nexus! Great job and hopefully the three guys can work some magic into the HD's

Corkerman said:
I mean the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
In consumer products, that's an eternity.

I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?

Jon Lee said:
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Click to expand...
Click to collapse
If it were me, I'd look here http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155 or here http://forum.xda-developers.com/kindle-fire/development/slimpop-otterx-t2957450 for some guidance.
Hashcode is a legend on XDA and he has almost single-handedly kept the very old, TI OMAP 4430 Kindle Fire alive. As for lovejoy777, currently, he has been the most active, hard working dev for that same KF. Hashcode has CM12 working and lovejoy777 has Slimpop.
Since our device is so similar to the KF and Hashcode has contributed to the Nook in the past, looks to be a good resource??? Then again, verygreen could also pop in sometime down the road.
Mike T

It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L

Jon Lee said:
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Click to expand...
Click to collapse
One of my first android devices was the 1st gen KF and Hashcode helped make an inexpensive E-reader a very viable android tablet. I would PM Hashcode and/or lovejoy777. Hashcode is usually very busy but he has always been helpful towards other devs, I know he gave some assistance to lovejoy777 with SlimPop.
As for lovejoy777, he's fairly new at development but seems to be very helpful. I think he also may have gotten some help/guidance from MwisBest who built a LP rom for the OMAP 4460 Galaxy Nexus. I mention this because I believe he knows the importance of cooperation among devs. As an aside, while reading his thread I think I read that he was in the process of "cleaning up" his github. So, he could be a good source.
Maybe also PM killersloth. He built quite a few nice roms for our Nooks last year and just recently expressed some interest in trying to get LP on our device. Maybe if you contact him, you guys can make something happen. I'm an old fashioned XDA'er that believes cooperation amongst devs and end users is essential in the community. Every little bit can help.
http://forum.xda-developers.com/showpost.php?p=57255968&postcount=14
Anyway, you seem to be a very sharp guy. I wish you luck in getting LP to the Nook. I wish I could contribute more but I'm more of a file swapper and modder of existing work than a dev. :laugh:
Mike T

Moving to Texas in three days, been hectic around here lol.
I had major issues with hwc, selinux, and our old configs. Hashcode must have plowed through it if its running on otter. I'd check his commit history for some tips.
We needed this for prebuilt boot image before
http://review.cyanogenmod.org/#/c/36813/1
I needed it a few weeks back when attempting to build. They might have brought up their own method since then.
I wish they would have called it SlimPop instead of SlimLP ??

A 5.0 build for hummingbird would be nice. Hopefully it won't be hard to modify an ovation build since all the devel appears to be on ovation.

Thread Closed

Thread closed to avoid confusion.

Info.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother? In AOSP Nougat, the Snapdragon 800 and 801 chips using the Adreno 330 GPU are no longer supported as well. I guess my question is if it will it be possible to reverse engineer OMAP-4 drivers for Nougat that can support the new surface view texture renderer?
Sent from my Asus Nexus 7 (2013) using XDA Labs
Click to expand...
Click to collapse
I MIGHT be possible to support it, but would take a bit of work, offloading that stuff to the CPU (which is just what we need, right?) and all of which is above my skill level.
Bobcus Leper said:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother?
Click to expand...
Click to collapse
The performance problems are probably a mix of slowish eMMC (have to load the precompiled ART files, and they're not exactly tiny), lack of main memory (ART has a bigger memory footprint), and an unsuitable CPU that was outdated when the phone was built, nevermind nowadays. The latter two are what seem to really kill us in CM13; if we're not stuck reclaiming memory, we're saturating the CPU : \
Having Motorola stroll in and develop some up-to-date, optimized drivers sure would be cool, though...hardware is hardware, but good firmware can make a lot out of little.
Nougat is apparently taking a step back and re-introducing JIT execution...so if our resident maintainer does somehow pull off yet another miracle and we get CM14 on here, I'd expect less I/O and memory pressure at the very least. The stock partitions would become viable again too, what with /data/ not being clogged by ART precompiles, and being able to run off them might also offer a (small) performance increase. /system/ is gonna be a tight fit, though...
But using drivers built in two previous, different eras of Android, most of which were for another device...seems like it's gonna take some serious work.
Sent from my Asus Nexus 7 (2013) using XDA Labs

Galaxy Nexus has Nougat!
MWisBest said:
Nougat build is up. No, I have not died, and neither has the Galaxy Nexus.
Decided to take an extra couple days to get this build stable rather than rushing out something that boots and does nothing else, sorry for the delay.
I can't verify the full functionality of the RIL since I don't have a SIM in my GNex these days, so let me know if there's any issues with that.
Everything else should be working well though.
No idea what to do for GApps at this time. I haven't tried them yet.
Download: aosp_n_tuna_2016-08-27.zip
As usual this was a team effort. @Ziyan helped, and @Hashcode (who I thought had died) helped as well.
Click to expand...
Click to collapse
Sent from my Asus Nexus 7 (2013) using XDA Labs

Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.

1f5 said:
Last time i talked with i Dev about Andoid 7 on the Droid 4, i was told that it would not be possible because of SELinux. But that Info is almost a year old. Maybe someone has more up to date information about this.
Click to expand...
Click to collapse
Thanks! Maybe we should ask @stargo about it. Although, I know stargo likes to surprise people with a new Android version.
Sent from my Motorola XT912 using XDA Labs

Really hoping this old beast will get CM14 due to the coding magic of stargo or some other guys out there.
I recently aquired a completely new Droid 4 from a Verizon reseller in mint condition. Now I never want to live without a slider again!
It is a bit slow, gets hot sometimes and becomes pretty much unuseable with Google Play installed, but who needs that stuff anyways.
Can keep me warm in winter and after replacing stock apps with Naked Browser and Simple Music Player it runs well and fast.
Please don't let this slider die. The only alternative to this device is the Photon Q and this needs to be soldered due to the missing SIM slot.

Bro i think it will have a cm14 for the droid 4
Bro, there say that it is official for the droid 4 to get cm14 check on gammerson .com

Some new info from JooJooBee666.
u.b.o.o.t said:
Hi folks! I had some spare time to setup CM13 build tool chain and - maybe too late for @Septfox - I made a custom kernel with LMK accounting for swap memory, i.e. LMK does only consider memory pages as free which won't require swapping, now. In order to not spam this thread anymore with LMK issues and memory tuning, I created a new thread: http://forum.xda-developers.com/droid-4/development/wip-custom-kernel-lowmemorykiller-t3470411
Click to expand...
Click to collapse
JooJooBee666--
This is cool. I'll test these out here as well. If things look good I'll see about getting LMK changes added to the cm13 kernel and upcoming cm14 kernels (work just began).:good:
Bobcus Leper said:
CM14 confirmed?:fingers-crossed::good:
Click to expand...
Click to collapse
JooJooBee666 --
Not really confirmed (as in no promises it will ever be fully functional as of yet). Just started working on getting things compiling. After that, it's along ways a way from anything usable as there are some new hurdles to overcome thanks to additional lock-downs on SE Linux. So yeah, :fingers-crossed: is right.

Bobcus Leper said:
Thread closed to avoid confusion.
Click to expand...
Click to collapse
Please ask a Moderator to close your thread - otherwise it isn't actually closed....
I've closed it anyway.