Database Develop

[KERNEL] Generic Android 3.0 kernel source

I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.

Ezekeel said:
I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.
Click to expand...
Click to collapse
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.

Lol Ezekeel, I've seen you praying Jean-Baptiste Queru for the Crespo-tree sources! I Think we have to wait one or two weeks...

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
Pretty much all the device-specific stuff is missing, but maybe we are lucky and no changes have to be made in the device-specific source for the Nexus S and we can simply keep these parts from our current code.

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?

Luxferro said:
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?
Click to expand...
Click to collapse
JBQ said that even if gpu is the same (omap4430) in galaxy nexus and in pandaboard he wasn't able to run the gnexus driver on the pandaboard and vice-versa because of some library-dependencies. So I think the drivers will not work out of the box...

awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.

Nice to know

simms22 said:
awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.
Click to expand...
Click to collapse
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App

matt2053 said:
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.

Maximilian Mary said:
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.
Click to expand...
Click to collapse
In one of the google groups replies JBQ said that they will always focus on the flagship phone.
Up until recently that was Nexus S.
Now the torch was passed and it's Galaxy Nexus first.
They will not dull the luster of their flagship phone by making libs and drivers for released phones available before the flagship phone has had time to shine.

I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
That will be a huge effort to fix, and it would probably cause more harm than good if you managed to fix the conflicts. I'm sure we'll have our sources in one/two weeks tops, so that's not worth the hassle in my opinion.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?

dvgrhl said:
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?
Click to expand...
Click to collapse
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.

Ezekeel said:
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.
Click to expand...
Click to collapse
First thanks for opening this thread, is a good idea.
At this moment I will wait some days to see if the crespo kernel 3.0 goes into public git, otherwise I will join the project to move the kenel since it will have multiple benefits.
Kalim

[Q] Is there a Android source release available from Sony

Is it possible to download the complete source code that Sony used when they compiled the ROM for Xperia V. I know where to find the kernel source and of course Android is very easy to get but what about everything else. I'm especially interested in knowing if they made any changes to Android or if they only cluttered the phone with add-ons.
Since Sony did abuse the phone and broke it to badly to make a reinstall possible I'm mainly just interested in getting the sources for my own education and understanding of the system. Perhaps even to try some simple reverse engineering to fix some really absurd settings like NFC not working in lock screen and such before I sell the phone and never ever talk about or to Sony again.

please use search and/or google
http://developer.sonymobile.com/downloads/xperia-open-source-archives/
good luck in your development of this

gregbradley said:
please use search and/or google
...
good luck in your development of this
Click to expand...
Click to collapse
Thank you for at least answering me however, I have goggled a lot about this and the link you posted to the best of my knowledge contains only the kernel source plus a few other system programs that are used on the host side when compiling. I'm honestly quite surprised that the answer to this is not well known. I have also since yesterday tried to find out what branch of android is used but that too seem to be obscured in darkness.

AlgoJerViA said:
Thank you for at least answering me however, I have goggled a lot about this and the link you posted to the best of my knowledge contains only the kernel source plus a few other system programs that are used on the host side when compiling. I'm honestly quite surprised that the answer to this is not well known. I have also since yesterday tried to find out what branch of android is used but that too seem to be obscured in darkness.
Click to expand...
Click to collapse
from what I am aware of those are the full sources used to compile the ROM, not just the kernel.
what do you mean by "What branch of android is used"

gregbradley said:
from what I am aware of those are the full sources used to compile the ROM, not just the kernel.
what do you mean by "What branch of android is used"
Click to expand...
Click to collapse
Well, look at the size. It is about 250MB, about the size of the kernel. The Android source is in the gigabyte range, I also have downloaded and compiled the kernel and the file you download contains a kernel folder and a external folder with the helper programs I mentioned.
Well I can't links since I'm to new here but if you do a search for "Codenames, Tags, and Build Numbers" on Google you will see that there are several branches for each version of Android. But now when I looked closer at that list it just so happens that 4.1.2 only has one branch so you can ignore that question, i was tired yesterday and was looking for 4.1.1 that has more like six branches. Still seems hard to find out what would be the right one in that case.

OK, I see what you want.
I am not sure where to find that info, but there will be some on here that will know.
try PMing championshipswimmer or DooMLoRD
They are busy people, but they may be able to point you in the right direction.

[Q] Ubuntu Touch for Galaxy S4 Active (i9295)

Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby

Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM

TobiasFP said:
Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby
Click to expand...
Click to collapse
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!

Cederic said:
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!
Click to expand...
Click to collapse
Thanks for the pick me up
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?

TobiasFP said:
Thanks for the pick me up
Click to expand...
Click to collapse
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
TobiasFP said:
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?
Click to expand...
Click to collapse
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.

Cederic said:
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.
Click to expand...
Click to collapse
No, of course it is not easy, but what i was saying is, that when the i9505 gets going, which i believe it will, since they have been working on it for about a month now, i believe it could "easily" be converted to the i9295.
The i9505 is a lot more similar to the i9295 than the i537, they both share the same Krait processor, and the screen is already fully supported in the current CM build of the i9295, so i dont see that as a problem.
Of course it will take some time, but i believe (okay, a better word would be "hope") that when the i9505 has Ubuntu Touch ready, it will not take long for us.
See the development status here:
http://forum.xda-developers.com/showthread.php?t=2274387&page=4

[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.

Question about Cataclysm.

Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!

H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.

StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?

StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.

NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.

StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.

So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.

H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.

zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol

If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.

zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol

H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.

zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol

H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.

zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!

Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.

H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.

H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.

Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.

HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.