[ROM] *×xREQUESTx×* AOSP KitKat 4.4.2 - Galaxy Note 10.1 (2014 Edition) General

We could REALLY use an AOSP ROM over here on the Galaxy Note 10.1 (2014) -P600/WiFi Only tablet.
I know there's someone out there who is interested in starting a new project as the first developer to produce an AOSP ROM for this kick ass device:fingers-crossed:
...hopefully!
So, who here is willing to donate? I know I DEFINITELY am!
Maybe we'd even be lucky enough to get an INCREDIBLE developer like we did for our TouchWiz HYPERDRIVE(sbreen94) <---- thanks for that!!!
Perhaps even @blindndumb or @albinoman887 would be interested!!?
IF YOU'RE WILLING TO DONATE FOR AN AOSP ROM, LET IT BE KNOWN!!!

and for P601

Correct me If I'm wrong, but Exynos 5 (P600) is not really supported by AOSP roms, so only Snapdragon variants like the P605 are likely to be compatible with any AOSP rom. It's likely better to purchase a P605 and run CM11, than wait for an Exynos 5 AOSP build.
Also, why would you want to remove the S-Pen features from a Tablet, who's main selling point is the S-Pen?

I won't be complaining if it happens but personally I can't really see any real benefits to having an ASOP Rom on this device at this point in time.
I prefer ASOP on the original note n7000 as you can get the latest Android OS that hasn't been released officially for that device. Also the older hardware is lacking and slow under the TW interface so you get big performance boost by having a lighter ROM.
This tablet has plenty of grunt and currently the latest Android OS so yeh not much point having ASOP imo.
With Android L coming out that might make a port more worthwhile

I would be happily willing to donate if someone prepares a P601 version.

I don't think Samsung releases binaries for the Exynos, so that's going good to add a layer of difficulty.
Plus with a device like this, you're going to lose a lot of functionality like all the spen stuff, multiwindows, floating Windows, ir transmitter, etc...

Related

I know I'm not supposed to ask this but:

Why is Cyanogenmod taking so long!? They posted a teaser on October ~16th and have made one more post after that, I'm actually getting fed up waiting for CM, If only I had the skills to port it myself, I tried stumbled across a few problems, anyone with Developing skills want to assist me in building CM11 for our SM-N9005 (hltexx)?
Why are there No developers attempting to make an unofficial CM Rom, or any AOSP rom. AOSP/AOKP as long as it runs like Stock. Tired of the bloating of Touchwiz.
No Flames please. ;D
Maybe because there's too many users not wanting to jump ship due to love for proprietary SPen stuff.. That means unless a developer has the phone (not many of the great ones have) and wants to run aosp, there won't be much progress.
Guess you could be the first
I'm also so desperate after aosp that I've considered trying to learn and make a aosp rom, but it's a huge jump for someone who hasn't developed; Even temasek (great kanger) hasn't tried anything on his own, and he has both great skills and a n3.
Alas, guess the whole community is waiting for cm to make the first move, once it happens there'll probably be an onslaught of aosp roms for our device.
Omnirom would be my first priority
I guess we could ask around for good devs with the n3 and perhaps somebody would start, or buy/raise money for one for Pulser, or somebody else, on a good aosp team.
Eddiemc said:
Maybe because there's too many users not wanting to jump ship due to love for proprietary SPen stuff.. That means unless a developer has the phone (not many of the great ones have) and wants to run aosp, there won't be much progress.
Guess you could be the first
I'm also so desperate after aosp that I've considered trying to learn and make a aosp rom, but it's a huge jump for someone who hasn't developed; Even temasek (great kanger) hasn't tried anything on his own, and he has both great skills and a n3.
Alas, guess the whole community is waiting for cm to make the first move, once it happens there'll probably be an onslaught of aosp roms for our device.
Omnirom would be my first priority
I guess we could ask around for good devs with the n3 and perhaps somebody would start, or buy/raise money for one for Pulser, or somebody else, on a good aosp team.
Click to expand...
Click to collapse
Definitely waiting for Omni or PA, as they let us keep the S-pen features (from what I hear)
Keep SPen..? Not so sure.. Pa was a highly regarded rom on note 2, and omni have their take on multiwindow, but neither have SPen features as they are on stock. But as long as you have a registered pen pull out and return, everything can be made possible. I'm a huge fan of gmd pen gestures, so I've turned off all the Sammy pen stuff and I'm using that instead. Also it gives me peace knowing that I'm not getting used to proprietary Sammy stuff I'll loose on aosp.
Eddiemc said:
Keep SPen..? Not so sure.. Pa was a highly regarded rom on note 2, and omni have their take on multiwindow, but neither have SPen features as they are on stock. But as long as you have a registered pen pull out and return, everything can be made possible. I'm a huge fan of gmd pen gestures, so I've turned off all the Sammy pen stuff and I'm using that instead. Also it gives me peace knowing that I'm not getting used to proprietary Sammy stuff I'll loose on aosp.
Click to expand...
Click to collapse
The s-pen is a gimmick, got over it after the first week, would've been good to have it. But I can live without it.

[Q] Note 3 drivers & CyanoGenMod

Dear Note3 users,
I am wondering about buying the Note 3 - however, I am afraid it will turn out the same as with my Note 1 - lack of proper drivers for newer AOSP/CyanoGenMod and the resulting problems (especially - phone reboting when taking pictures and occasional UI stuttering etc.). I remember devs blaming Samsung for not releasing the source-code for the Exynos-based devices back then..
I suppose the current CM KitKat builds are fine with N3 - what about future builds, especially when moving beyond KitKat? Has Samsung done a better job at supporting the N3 and AOSP/CM thus far (when compared to the N1)?
Thanks for all your replies..
Jan
I can't answer your question directly - I don't use CM/AOSP - but I'm interested in the way you asked your question.
I don't see that Samsung have any onus or responsibility all to "support" CM and/or AOSP. As I understand it, they release the source codes for all drivers that they are legally obliged to and no more.
I'm sure the rest is a PITA for CM/AOSP devs, but is that unique to Samsung? Don't Sony, HTC etc do the same?
Personally the only thing I like about CM is the theme choices, and now there are Xposed modules to port many themes to TW based ROMs. If I wanted CM/AOSP, I'd buy a Nexus.
I've nothing against TW framework, it's never let me down, and I've had the SGS/2/3 and Note 2 previously. I don't use the TW launcher, stock icons or stock kernels. I have tried a fair few CM ROMs over the years, and never had a single one that was 100% bug free.
Put it this way - I like stability in my phone, and by definition any ROM that needs nightly builds isn't going to supply that "need".
My 2 cents. Whatever floats your boat is fine, that's why we don't use iphones

[Q] AOSP on the Note - what are the roadblocks?

Hi,
Could anyone explain why we don't yet have an AOSP ROM for the Note?
I'm looking forward to getting rid of TouchWiz and I'm curious what the challenges are that prevent developers from just compiling the AOSP code to run on the Note 4.
I'm coming from a lot of Nexus devices so I'm not familiar with the roadblocks in developing ROMs for Samsung devices.
You know only samsung can make feature for s pen and other stuff. If this is a normal phone, that would be easy to make a AOSP rom lollipop like my old galaxy tab 10.1 with 3 year old.
But, this is note with only samsung can create stuff for us. So keep calm and wait
https://plus.google.com/109781780227026386444/posts/ABurAWxbk4V
I'm not particularly interested in using the S-Pen or all the other Samsung stuff, I just want a replacement for my Nexus 4 that has better specs. All that other stuff can come later or not at all really.
Thanks Batfink33 for the good news, really looking forward to some AOSP or CM goodness

[Q] Need advice on choosing a ROM

Hello.
I need advice/suggestions on choosing a Rom for my Samsung Galaxy S 4 (I9505/jfltexx). What I am looking for is a ROM that is stable and actively maintained with regards to bug and security fixes, preferably AOSP based. I have no need for neither all sorts of bells and whistles, fancy eye candy nor bleeding edge features. Rushing to the latest major android version is not a priority, having my phone fully working is, though.
Here is some "background data" om me in the hope of providing a more complete picture of what I am looking for based on my previous use/experience.
I have owned 3 android capable devices. HTC Legend, Samsung Galaxy SII and Samsung Galaxy S 4. One can argue these have been poor choice of devices but it is what it is. I have been running mainly Cyanogenmod since 6.1 I believe on all devices. Fact is, flashing CM has been one of the first thing I have done after buying a new device as I tend to "gag" on HTCs and Samsungs firmware. The first few years I used to tinker about with the devices a lot, flashing stable, RC, milestone and nightlies, different ROMs/kernels frequently but always found my way back to fairly default CM. It has been a bumpy ride on CM (yes, I realize this is in part due to my choise of devices) and while I am not here to lash out at CM in general, recent choices from the CM team and increasingly inconsistent support for my current device leads me to looking for alternatives while really appreciating the sheer amount of great work the CM team have done over the years.
So, what drew me towards CM in the first place? Well, mostly the flexibility/customizability of the ROM and the power/control I felt I had of it, the openness of it and what once was an active, positive community around it. Admittedly, SenseUI and TouchWiz probably pushed me towards it as well. The most recent year or two I have moved a bit away from tinkering and have had a higher need for a stable and maintained ROM that "just works".
I had decided to go for OmniROM, it seemed to be a decent alternative but I am under the impression that my device is no longer supported. Have been considering CopperheadOS as well.
Anyway, I am open to suggentions.
Cheers.
Slimsaber and Slim roms are constantly updated. They are also mantained by the same developer.
Resurrection Remix. I use this rom for some time and I have no issues. But this depends from phone to phone.
It is pretty feature rich.
The GPE rom is also a good choice. But GPE 5.1 is still pretty new and may not offer a stable and bugfree experience. You might want to try GPE 5.0, but it is not mantained anymore, since the move to 5.1.
There is a pure AOSP rom. It's basically the same thing you find on a nexus device.

AOSP or Google-based ROM?

Are there any AOSP or stock Google Android ROMs out there for the S8? I'm not keeping my hopes up because I owned the S7 Edge ever since it came out and it never really came through. The reason I am asking is because I just found out there's a MultiROM tool for the S8 and I'd like to take advantage of that. If there aren't any AOSP ROMs, what are the lighest, most de-bloated TouchWiz based ROMs out there that feel like stock? I'm currently on BatMan ROM and it will be my primary ROM and I am looking for a light second.
Thanks!
There are no aosp roms yet.
Why is it that it takes so long for AOSP ROM's or Lineage based ROMs to come out for exynos devices? I'm just curious because Samsung released the kernel source for the exynos variants. I might be just asking a noob question but I'm curious what's involved in making a AOSP ROM for these devices.
TacoTuco said:
Why is it that it takes so long for AOSP ROM's or Lineage based ROMs to come out for exynos devices? I'm just curious because Samsung released the kernel source for the exynos variants. I might be just asking a noob question but I'm curious what's involved in making a AOSP ROM for these devices.
Click to expand...
Click to collapse
Kernel development, porting, baking, bug fixes before release. There are a lot of steps involved that need someone decently motivated to take.
MansonDroid said:
Kernel development, porting, baking, bug fixes before release. There are a lot of steps involved that need someone decently motivated to take.
Click to expand...
Click to collapse
do you know if any one working on aosp rom for the s8 ?
imzaki1994 said:
do you know if any one working on aosp rom for the s8 ?
Click to expand...
Click to collapse
I'm willing to bet a few developers might be messing around with Lineage/AOSP. You have to consider the fact that there has never been an Exynos device running AOSP straight from Samsung. They have to build Android from the ground up for Exynos devices instead of just rooting and adding tweaks.
AOSP based roms for SnapDrgaon phones are a dime a dozen. Developers can look into other phones for bug fixes and common issues. With exynos, the developers have to fix bugs with no preexisting knowledge base to draw from. Besides what they know from Touchwiz Android builds.
Give it some time. The longer the phone has been out for the more hands it gets into. Especially when discounts are put out.

Categories

Resources