Hey, guys - I remember back in the KK days having a Linaro compiled ROM offered substantial speed improvements.
I haven't heard or seen nearly as many ROMS being compiled with it anymore. This begs my question, does Linaro offer any noticeable improvements?
Planning on starting to compile my own AOSP rom and was curious about heading down this route.
it never offered REAL improvements, they were improvements that some people thought they saw, and they spread them around. but they never actually existed.
Related
So how long do you think it will be till we get some AOSP Roms?
Example I bought this phone because I had to have Wifi Calling since the area I lived in, and bought the phone for the specs.
But I know not everyone loves Sense and was wondering when we will see the full AOSP Roms that are just pure Android.
Also how long do you think it will be till we see some real kernels with features.
Full EXT4
BFS Scheduler
Overclock upto 2Ghz (if possible, since phones can do 1.78 fine)
Kernel update to 2.6.38
updated drivers
I know we got the kernel source from HTC.
Also when are we going to see good ol Cyanogenmod 7!!!
I would be happy with one good AOSP rom for right now
Here's an interesting article some of you guys might enjoy.
http://www.androidpolice.com/2012/0...e-and-now-parts-of-it-are-being-added-to-cm9/
News started to trickle out this week about a new Android build called Linaro. Basically, it takes stock Android 4.0.4 and makes it super-fast, and super-awesome(er). In fact, it can boost performance by up to 100 percent over stock. Considering how fast and fluid stock Android 4.0.x already is (especially compared to older versions of the OS), that's quite impressive. Don't take my word for it, though, here's one of the main Linaro guys, Bernhard Rosenkranzer, showing it off on a TI Pandaboard. The Pandaboard features the OMAP 4430 processor (the same one that's in the Droid RAZR), so this is definitely a real-world example of what Linaro is capable of:
As you can see, the Linaro build finishes long before the stock Android build. That's not the best part though: the parts of Linaro that make is so efficient and fast are coming soon to Cyanogenmod 9.
Basically, parts of the Linaro code have been submitted to the CM9 gerrit and are currently awaiting approval. Once commited, these tweaks will be added to the main CM9 code, giving all supported devices a drastic increase in performance.
The good news doesn't end there, though: Galaxy Nexus owners can already take an unofficial CM9 build with the Linaro bits for a whirl. From what we've read, this build is noticeably faster and more fluid right out of the gate. Awesome.
Since the first rule of CM is don't ask for ETAs, we have no idea when we could start seeing builds show up with Linaro code, so for now, we'll all just have to take comfort in knowing that things in the CM9 world are getting ready to get a lot faster.
Click to expand...
Click to collapse
There's already Linaro'd CM9 build for the GNexus. And Linaro tweaks are soon going to be added to the official CM9 even before Google can implement it. What do the developers here think of Linaro? Will you be willing to Linaro your roms?
Sent from my Samsung Infuse running AOKP.
I have a nexus and I can say that it is simply a placebo... gaming performance decreases and it's hardly noticeable while doing daily tasks - web browsing, video steaming, scrolling, listening to music, etc. My quadrant boosted by 300 - from 2036 to 2336... not great. I don't OC so I can't speak for those who did to augment the effectiveness of Linaro. I'm not saying Linaro isn't effective but your GCC tool chain must be compatible in order to fully implement some "raw" power.
Sent from my Galaxy Nexus using Tapatalk 2
This thread is pretty much dead but I thought I'd throw in my opinion. Atm, I'm running an unofficial build directly from Linaro and is untouched by any other dev, such as kernel, tweaks, OC etc..
Its not blow your mind amazing compared to past roms, what is amazing though is how much faster it is than stock (which was/is the main sell point of linaro project) My second GNex was stock for about 4 months before I decided to go back to custom roms. Obviously it would be faster/smoother but with my first GNex I spent quite a bit finding the right rom/kernel/tweaks/OC combo to made it this useable. With this build, I have added nothing. Plus from what I understand, its not necessarily a tweak but rather an optimization that uses an updated install method to better integrate the OS and its processes or something like that.
Linaro is definitely on to something here, or Google wouldn't be pulling pieces of Linaro code. Lol
Sent from my Galaxy Nexus using xda premium
It doubles ONE benchmark which is not a significant part of normal operation, it does NOT "nearly double ICS performance".
god I hate the game of "telephone" where people read one thing, pass it on with minor errors, and before long you have complete and total utter bull****.
In most benchmarks, the Linabug tweaks give no benefit at all. They also give very little benefit on devices where most components are binary vendor blobs.
The Linabug prep in CM has broken piles of stuff over the past two weeks, and if the compiler switch happens it's going to be hell - expect piles of obscure bugs that are next to impossible to track down.
Compiler tweaks are way overrated - I speak as a reformed Gentoo ricer here. I drank the kool-aid for years and then came to my senses.
Entropy512 said:
.
Click to expand...
Click to collapse
Sounds like you could use a few.....
Hello, just got my Nexus 5 in the mail and I'm happy to join this community along with my previous device forum
But my question is what's the difference between CAF and AOSP? And how would I tell if a ROM is based on CAF or AOSP?
I did a little research myself where CAF is Code Aurora Forums and that CM is now based off of it. It's also what's behind Qualcomm's kernel work and whatnot. AOSP is android as it is now. It was formerly based off CAF but bridged off a while back then and the .libs are a lot different from CAF now. Right?
(Thanks @poondog for getting me started on this!)
But how would I be able to tell if a ROM is CAF or AOSP? Would that really impact what kernels I flash and such? (like CAF ROM only CAF kernel)
Also what would the advantages between the 2, if there are any?
Thanks a lot!
Sincerely,
072665995
bump
CAF=cyanogen 11 based roms, not all kernels work unless they state CM support in the OP which isnt many nowadays.
AOSP=the majority of roms in the original development section, also you will have a larger choice of kernels to play with.
its your choice some people have always loved CM i personally love AOSP but i have used CM in the past but with the N5 the majority of kernel development is with AOSP.
I think you could look into using multirom and test AOSP and CM at the same time but be aware of kernels not supporting CM just read the OP carefully to avoid problems.
i dont know if this helps, if not ill get my coat...
Noob question: Isn't cyanogen based off of AOSP anyway since they're both android?
paranoidsuperhero said:
Noob question: Isn't cyanogen based off of AOSP anyway since they're both android?
Click to expand...
Click to collapse
yes http://wiki.cyanogenmod.org/w/About
" So what is the difference between Android and CyanogenMod?
About 1-2 times a year, the vanilla Android operating system (known as AOSP, or the Android Open Source Project) is internally developed, then released to the public, by Google. They provide the source code to anyone who wants to download it. The CyanogenMod community, comprised of unpaid volunteers and enthusiasts from around the world, takes this newest Android code and "ports" it to dozens of new and older (aka "legacy") devices. At the same time, other CyanogenMod developers start adding features, fixes, and improvements that Google didn't include to the CyanogenMod code, which benefits all the devices. The CyanogenMod community has a whole infrastructure for people to build and test experimental versions, report bugs, and contribute back to the source code.
Sometimes features that started in CyanogenMod have appeared in newer version of "official" Android. And every time Android does a new "code dump" of their latest version, CyanogenMod benefits from Google's changes.
In this way, CyanogenMod is one (but not the only) community distribution of what started as vanilla AOSP. The Android community is vibrant, with numerous "modders" and "themers" and "performance enhancers" taking the source code and doing incredible things to it. Generally, there is a spirit of sharing knowledge and empowering people to experiment with controlling their devices, often giving old phones new life, and hopefully having fun in the process. "
I mean, we have a GPE port. I know, I know, this is literally the definition of shot-in-the-dark. No source code release means extremely difficult to build for alternate devices, and unless Google chooses to release a preview for GPE devices we're screwed.
Still, I have to ask: is there even a tiny chance?
Oh there is always a chance of a crappy port. But you are better off just waiting for the official release. Look at the issues CM has and they have source.
Sent from my HTC6525LVW using Tapatalk
Of an official preview I would say nill. That a Dev will hack something together even if its just the GUI I would say put that pretty high.
I would bet a lot of the aspo devs have already looked at it and are trying to size up the challenge.
Sent from my HTC6525LVW using XDA Free mobile app
CM has source? I think Google is waiting on the Nexus 9 to release source. They always withhold source until the Nexus device that launches the new version is released. Then they release source and CM and the others start building. KitKat didn't get a Nexus device; if you remember, it was released on Halloween (31 October) last year. It was just released, source and all. And CM had releases inside a week. There's a developer preview out, but it's beta and has issues even in the official binaries. I'm not putting it on my N7.
We're getting L within 90 days from HTC. Then you'll see the Sense-based ROMs get it. But I imagine CM will beat HTC to the punch, so all the AOSP-alike ROMs will get it long before then. CM, LiquidSmooth, and such.
i think what @termleech was saying is look at how much time it takes for a "stable" CM release for any given phone. and they have a KK source base to work with.
also @termleech it wouldn't just be google to decided. google would have to ok it. then they would give the source to HTC who would then release a build.
But its really not in HTC's interest. Unless google is going hey where not changing any of these features other then for bug fixes then HTC would be putting in time to build and test a build that they will have to disregard when google changes major things.
Unfortunately, I think the chances of a preview build are very low; however, devs have already started baking in L features into 4.4.4 GPE roms which would be a decent substitute until the GPE M8 gets the update and is then ported to our device. In any case, we're pretty much first in line for HTC when it comes to pushing L out. They've already promised an update within 90 days of the release but it will probably be sooner.
Hey Folks,
I had no Samsung Device for ages but i got a brand new Galaxy S9+ in Gold for a nice Price and couldn't resist anymore. Now is the Question, is the Exynos Variant worth the Bootloader Unlock? I'm a Friend of AOSP / GSI Development and would like to contribute for My Device some Work. But how good is the Treble Support? Are GSIs working fine? Any Bugs or Features that i would miss compared to the locked stock OS? The ONE UI seems to be pretty nice and i'm very happy with My S9+ how it is. But i would also like a OS without all the Samsung Stuff and some Optimizations on top. All Opinions are Welcome!
Edit:
So i just decided to unlock My S9+ Duos and i'm already working on a Stock OS Project (Sadly since AOSP isn't that good rn). Anyways, the Samsung OS is pretty good. I will debloat it hardly and add Google Apps besides some heavy background optimizations on the System. That will be something new for Samsung Users... Stay tuned!
Edit2:
Project will be called GOSP (Galaxy Open Source Patch). Aiming on Debloating Samsungs Firmwares besides adding Google Apps, new Features and optimized System Configurations for better Performance, Quality and Battery Lifetimes. It will be open on GitHub for contributions and everyone is welcome to work with Me on a unified Stock ROM Project for all Galaxy S9 and S10 Variants (Also the coming Ones and Note 9/10 Devices).
The First Time that i haven't unlocked my Bootloader right after getting My Device. If no One explains Me the Pro and Cons am i keeping it locked. I don"t trust This Samsung Pseudo Security Stuff aka Knox and Counters... IT's like i said For Years. Samsung is just the better Apple. Can't wait to Hear News about Tizen lol
Not a lot is happening on the AOSP side of things, just a los 16 project that seems to be stable enough for daily use. There are a few very nice stock based roms like soldiers or ambasadii. Go and have a look on the cross development forums. For me personally there are pros, I like my device bloatfree and my kernel modified for my usage. But the cons are that there is not a big community (strange for a newer Samsung device.......), not much treble sGSI support at all, and a very small chance of getting a large number of different AOSP roms in the near future. Hope I helped
Haxomen said:
Not a lot is happening on the AOSP side of things, just a los 16 project that seems to be stable enough for daily use. There are a few very nice stock based roms like soldiers or ambasadii. Go and have a look on the cross development forums. For me personally there are pros, I like my device bloatfree and my kernel modified for my usage. But the cons are that there is not a big community (strange for a newer Samsung device.......), not much treble sGSI support at all, and a very small chance of getting a large number of different AOSP roms in the near future. Hope I helped
Click to expand...
Click to collapse
I'm wondering how @phhusson is working with Treble since he made various patches on his AOSP GSI Development. Do we use Stock Vendors with the GSIs? Hows the Pie Status? Many GSIs are out there who get many Updates over the Time including Phhussons Changes on the AOSP Base so i would push My Efforts in this Direction...
I've read that Hardware composing isn't working and that the Iris Scan isn't implented in AOSP. Is there anything besides that left? It looked to me that Phhusson fixed most of the Issues so far!? I'm really about to unlock My Baby... (Still hate Exynos lol)
Miustone said:
I'm wondering how @phhusson is working with Treble since he made various patches on his AOSP GSI Development. Do we use Stock Vendors with the GSIs? Hows the Pie Status? Many GSIs are out there who get many Updates over the Time including Phhussons Changes on the AOSP Base so i would push My Efforts in this Direction...
I've read that Hardware composing isn't working and that the Iris Scan isn't implented in AOSP. Is there anything besides that left? It looked to me that Phhusson fixed most of the Issues so far!? I'm really about to unlock My Baby... (Still hate Exynos lol)
Click to expand...
Click to collapse
I dont know how he is working, but sGSIs for out device are crap, and that is a good way to say it. There is no thread for the new LOS 16, but the HWC bug is solved in the new builds. Yeah the issues are fixed but the stability, battery life and other things are bad for my taste
Haxomen said:
I dont know how he is working, but sGSIs for out device are crap, and that is a good way to say it. There is no thread for the new LOS 16, but the HWC bug is solved in the new builds. Yeah the issues are fixed but the stability, battery life and other things are bad for my taste
Click to expand...
Click to collapse
I'm really sad that i can't get a Snapdragon Samsung Device in Germany but i Think ill unlock the Bootloader, make a Backup and try out some Things. Stock seems to be Very Good actually. Maybe do i something in that Direction Again. But also possible that i work on Treble... I just need a Day or Two to decide that.
Shouldn't hurt to start a new Project for such unbeloved Device. The Overall Hardware i Superb. But i never worked with Exynos. That will be a intersting Trip...
Alright, i will do a Stock Project aiming on Debloating the Samsung Stuff out of Stock Devices and optimizing of the overall System Quality. Or how i call it: "Patching".
Required will be a Stock Samsung OS or ROM and My Patch does the Rest. Included will be also new and hidden Features and a Google like Expierence with essential System Apps from Google. Think i will use My last AROMA Utility for it which includes AROMA File Manager and other Goodies...
Can't wait to see what i can unleash on Samsung Devices..
One UI is really far away from AOSP. Hard to implent Pixel Features and such... Not even Well Beeing from Google will be shown in the Samsung Settings.
Think i will give Linage OS from the first of this Month a Shot and See how it Runs...
Thank you for your involvement!
If you want to contribute to s9+ exynos community, you could also port the gcam from pixel. There are some ports, but they are bad, and discontinued.
https://forum.xda-developers.com/galaxy-s9-plus/themes/gcam-port-galaxy-s9-s9-exynos-t3814539/
Have a good day!
danimiu3 said:
Thank you for your involvement!
If you want to contribute to s9+ exynos community, you could also port the gcam from pixel. There are some ports, but they are bad, and discontinued.
https://forum.xda-developers.com/galaxy-s9-plus/themes/gcam-port-galaxy-s9-s9-exynos-t3814539/
Have a good day!
Click to expand...
Click to collapse
The Samsung Camera is actually pretty good. But i will take a look...
Is anyone willed to help me testing btw? Project will be called GOSP (Galaxy Open Source Patch) and i'm open for any Devs who want to join and contribute...