Related
Apologies if this has been covered, but I've done multiple searches and have yet to find an answer. I'm in the process of picking a new phone, and I'm down to the galaxy nexus and gs3. (Damn you google for not releasing the n4 on vzw). In any case, my concern is around updates. I realize the CM team will continue to support the gs3 well into the future, but my question revolves around kernels. It's my understanding that the CM team will simply update the userspace - in order for there to be an updated kernel, there would need to be a release from Samsung for the appropriate kernel. In other words, if google updates android 5.x to a linux 3.6 kernel, and the last Samsung release was 4.2 running the 3.4 kernel, while I will get the 5.x android userland, I will be stuck with the old kernel, and potentially sub-par battery life/performance enhancements/etc. To the point I may not even be able to upgrade if they make significant enough changes to the kernel/userland interaction.
Are my assumptions correct, or am I off-base? I just don't want to get stuck like I am today with my droid-x that stopped being supported ages ago by motorola, and just barely supported by the community a year later.
There are custom kernels that have their own linux merges in so it would be very feasible that we have linux kernel updates beyond what Samsung gives us. The NA variant is on basically every carrier in NA so I am sure there are atleast a few excellent kernel devs who own the device that would be able to do this.
That isn't to say it isn't possible for us to get abandoned. But I think the dev community for this phone will last longer than previous phones.
con247 said:
There are custom kernels that have their own linux merges in so it would be very feasible that we have linux kernel updates beyond what Samsung gives us. The NA variant is on basically every carrier in NA so I am sure there are atleast a few excellent kernel devs who own the device that would be able to do this.
That isn't to say it isn't possible for us to get abandoned. But I think the dev community for this phone will last longer than previous phones.
Click to expand...
Click to collapse
I understand that as a whole it won't get abandoned. Unless Samsung is open sourcing drivers though, I don't see how it's possible to release updated kernels if Linus decides the kernel/driver interaction is going to change - which has happened in the past and likely will again in the next 2 years. Without the source to the drivers, I don't really see how the devs could hack something together short of trying to re-write them entirely.
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
ROM:
http://www.mediafire.com/download/0f12tn2klc66v52/cm-11-20141231-UNOFFICIAL-ovation.zip
MD5:
http://www.mediafire.com/download/u1xdu2d85851nw8/cm-11-20141231-UNOFFICIAL-ovation.zip.md5sum
Compiled with ArchiDroid optimizations & "Yellow Kernel"
https://github.com/JustArchi/android_build/commit/1125f60a15194e08fdf18feacefb47696647e05b
(-o3, gcc4.8, openjdk 1.7... lollipop's version)
Odexed, ext4 for now (a little hacking could accomodate for F2FS), not rooted. If flashed with a current TWRP recovery, TWRP will offer to root it (which works).
I removed the proprietary terminal from the build (with the intent of compiling one from source eventually. Until then, one can be downloaded from f-droid), prepared for USB camera support (rather than a 'camera stub'), & audio_policy.conf changes (USB headset,etc- which probably isn't supported in the audio_hw.c file... yet), and a few other experimental changes.
After the first boot, this has the fastest boot time I've seen of any ROM I've tested.
****source****
Device:
http://www.mediafire.com/download/hcffj8p6atb8kyo/device_bn_cm.tar.gz
Kernel:
http://www.mediafire.com/download/ja828194riarf81/omap_123114.tar.gz
Thank you very much for all the work you are doing to make this piece of hardware working so good!!
Since this is odex it will be really fast... I hardly wait to flash it!!
It would be great to have a f2fs build too!!
Odex + F2FS = super smooth!!
Can't wait to try f2fs cm11 build!
Sent from my SM-N900V using Tapatalk
Flashed this rom yesterday, so far so good. Complete wipe and flash. No gapps just side-loaded desired apps and running well. Feels like a current CM11 nightly
I am running this rom and i confirm that it works really well.
Great work!!
A F2FS version would be really the perfect rom.
@OT
frantisek.nesveda created this tool for Nexus 7 grouper, maybe it can be useful for Ovation too, with proper modifications:
http://forum.xda-developers.com/showthread.php?t=2748975
I can't get the download to work. Is anyone else having an issue with notbeing able to see the target captcha??
Nevermind, I got it on my laptop.
Will you make a hummingbird (Nook HD) version?
Many thanks, Jon! Requesting F2FS version as well...
I'm having a problem charging. If I use a higher capacity charger, ( iPad) it shows a green charge light and not charging, even though it's at 18%. If I use a lower capacity charger from my phone, it shows a blinking orange and doesn't charge. I used the same twrp 2.8 I used before for Slim.
I've never seen this before.
Update, it looks OK on a third charger. Who knows?
Switching to ART causes bootloop for me. Anyone else facing this issue?
infra_red_dude said:
Switching to ART causes bootloop for me. Anyone else facing this issue?
Click to expand...
Click to collapse
Yup, same here.
infra_red_dude said:
Switching to ART causes bootloop for me. Anyone else facing this issue?
Click to expand...
Click to collapse
I haven't tried ART on this device, but from my experience with other CPUs (tegra 3 and old Exynos) I think that Google started developing ART on Qualcomm Snapdragon (Nexus 4, 7 and 5). So, unless you have Snapdragon processor, I think that on Kit Kat is better to stay with Dalvik, especially if you have an odex Rom like this.
Only with Lollipop ART became mature to work quite well also with other architectures.
Monfro said:
I haven't tried ART on this device, but from my experience with other CPUs (tegra 3 and old Exynos) I think that Google started developing ART on Qualcomm Snapdragon (Nexus 4, 7 and 5). So, unless you have Snapdragon processor, I think that on Kit Kat is better to stay with Dalvik, especially if you have an odex Rom like this.
Only with Lollipop ART became mature to work quite well also with other architectures.
Click to expand...
Click to collapse
I'm using ART on my Nook HD without any problems. I run CM11 nightly fully installed to EMMC but with F-Droid and Amazon app stores and no Gapps (except Earth and an old version of Youtube which don't require Play Services). I switched to ART over the Christmas holiday. It takes a little while to rebuild the installed apps but it does work perfectly OK. I have experienced zero bugs with it and it does seem to make for a better experience.
@julian67
Are you running This build with Jon Lee's Yellow kernel or a CM nightly with the stock kernel. Art has always work for me with the CM stock kernel
Stock kernel, CM11 nightly (hummingbird on HD). I hope my experience and yours shows that ART working (or not) doesn't depend on system architecture/CPU. It is definitely worth switching runtime. If it doesn't work then it's probably just exposing deficiencies already present in omg_funroll-loops_optimilized-4-speed-ultraaar-stable-buttery-smoo......*crash* kernels and configs.
This is running great John.
Thank you, Jon.
I used all your roms.
All your roms are great.
This rom is really good, too.
But I'm sad that exFAT external memory doesn't work with this rom.
Please consider supporting exFAT external memory.
julian67 said:
I'm using ART on my Nook HD without any problems. I run CM11 nightly fully installed to EMMC but with F-Droid and Amazon app stores and no Gapps (except Earth and an old version of Youtube which don't require Play Services). I switched to ART over the Christmas holiday. It takes a little while to rebuild the installed apps but it does work perfectly OK. I have experienced zero bugs with it and it does seem to make for a better experience.
Click to expand...
Click to collapse
I'm running ART as well with the nightly from 1/5/15, the things I have tried have been working fine. Too bad BN got out of the tablet business, these are great little tablets.
Perhaps a bit of a rant here....
I'm sure the ART issue is a consequence of this build being odexed.
The exfat issue is a consequence of the archidroid optimizations (there is a patch for it which I failed to apply). All of my builds have been experimental in one way or another...
CM10.1.3 with the "Yellow Kernel" was perfectly long term stable (for me). I can't really speak for Slimkat because I didn't try it out that long, but Liquidsmooth and this CM11 are somewhat less than stable (for me). As another poster humorously pointed out, it's probably part to do with compiler "optimizations".
I'm quite glad that Hashcode came out with CM12, as it was mostly beyond my ability. I was tired and fed up with trying. So he saved me the effort....
This CM11 build may have some ffmpeg video codecs that the normal CM11 builds don't include (which would be one of the few advantages of using it).
Right now I'm working on compiling CandyKat (which is based on Slimrom). I'm learning as I go and the best I can hope for is that each subsequent build is an improvement over the last. Technically my true aim is long term stability. With that in mind, perhaps I should stick with CM10.1.3... or perhaps an AOSP build. I'm not content with leaving things well enough alone though. Behind the scenes I have more broken builds than builds that actually work.
Anyway.... /rant over.
Jon Lee said:
Perhaps a bit of a rant here....
I'm sure the ART issue is a consequence of this build being odexed.
The exfat issue is a consequence of the archidroid optimizations (there is a patch for it which I failed to apply). All of my builds have been experimental in one way or another...
CM10.1.3 with the "Yellow Kernel" was perfectly long term stable (for me). I can't really speak for Slimkat because I didn't try it out that long, but Liquidsmooth and this CM11 are somewhat less than stable (for me). As another poster humorously pointed out, it's probably part to do with compiler "optimizations".
I'm quite glad that Hashcode came out with CM12, as it was mostly beyond my ability. I was tired and fed up with trying. So he saved me the effort....
This CM11 build may have some ffmpeg video codecs that the normal CM11 builds don't include (which would be one of the few advantages of using it).
Right now I'm working on compiling CandyKat (which is based on Slimrom). I'm learning as I go and the best I can hope for is that each subsequent build is an improvement over the last. Technically my true aim is long term stability. With that in mind, perhaps I should stick with CM10.1.3... or perhaps an AOSP build. I'm not content with leaving things well enough alone though. Behind the scenes I have more broken builds than builds that actually work.
Anyway.... /rant over.
Click to expand...
Click to collapse
You did really an extraordinary job on this device: you succeeded in bringing F2FS (which I consider a great improvement) and you compiled among the best Roms available here.
This CM11 is near perfect, since its target is to bring more optimization and more performance, and I consider Odex+Dalvik smoother than Deodex+ART (which on KitKat is still experimental).
Only thing I would add is a F2FS version.
For next project I suggest to try a vanilla AOSP ROM, maybe also in Odex and F2FS version, since usually more functions means also more ram and CPU needed.
CPU and GPU are quite OK on this device, but the real problem is RAM.
Also Roms based on Slim should be fast and efficient.
Of course doing experiments can also disappoint someone, but from my point of view you reached great goals with your work on this device.
The purpose is to give users more choice: this ROM offers a different compiling approach than standard CM11, and if someone is disappointed can run standard CM11.
But this ROM gives the option to other users to try something different.
So I think that majority of users here are supporting your work and anxiously are waiting what you will bring next to Ovation.
Keep up the good work!!
I realise this is probably a bit of a controversial question to ask on XDA, however has anyone else just stuck with the stock Cyanogen OS on their OnePlus One?
I was thinking today when reading about Lineage OS I have pretty much kept my OnePlus One stock since i got it in July 2014, out the box Cyanogen OS had everything i'd otherwise flash a custom rom for. I did try some early Marshmallow roms around February last year, however due to various bugs I went back to stock and waited for the Marshmallow OTA.
These days i'd certainly take stability over having the latest and greatest version of Android. Of course I don't intend that as any disrespect to the developers on here, more than anything I think I just got tired of tinkering with my phone and have enjoyed just using it.
However I do plan on flashing Lineage OS in the future, which seems quite strange after not flashing a custom rom for almost a year.
It's great to see XDA is still going strong, even more so that the OnePlus currently has the most users of unofficial installs of Lineage OS :good:
My father does have the official builds hahahah we both have the opo but he's okay if it works, so keeping it simple is the best way for him.
As far as Cyanogen OS goes
It's bad and bloated
I tried to stay on it, and did for a bit when security updates were being applied
But had a bunch of reboots and overheating issues. Had to dump it.
Was on stock COS till today since i couldnt find a rom that suited my needs and passed safetynet. Today i flashed lineage OS official, everything is smooth and it passes safety net (i can now use my banking app while running nougat). So yeah today is the day i left COS and marshmallow
I don't even know why I'm still on official CyanOS. The screen time is dreadful. I think I'll give LOS a chance in the near future. It can't be any worse than 3-4 hours of screen time, what I'm getting now with official COS.
Cyanogen may be sold in the future and they can push harmful updates to your device, so I'd say updating is a very good choice.
I am keeping it. I would love that someone could recommend me a 6.0 rom alternative though, because can't switch to Nougat. MM has xposed and i need youtube background playback.
I do sometimes think maybe I should have stayed stock but then I think of all the fun I've had
Now I need my phone to work for calls and alarms as a minimum so take less risks now
I'm still on marsh 2.0 from way back last august
i would but cyanogen 13.1 has a problem with the mobile network.........
Luck Patcher
Fatsodonkey said:
I am keeping it. I would love that someone could recommend me a 6.0 rom alternative though, because can't switch to Nougat. MM has xposed and i need youtube background playback.
Click to expand...
Click to collapse
You can try Lucky Patcher. They have a custom patch for YouTube background playback. Works on Nougat. Hope this helps
For anyone who wants the best stable experience, I'd suggest sultanxda's CM13 ROM. May it be for girlfriends, dad's, whoever. That ROM will never fall behind.
Cheers.
Well I am still sticking with rooted cyanogen os. I have color camera, viper4android, Sony Media Apps like Walkman and xposed.
Can anyone enlighten me whether noughat build supports viper4android and a good camera mod like color os or cameranext mod? If so I don't mind installing it immediately..
I'm still on stock ROM, because I'm using NFC payments on the tube. Battery life with screen on is dreadful. I would upgrade in a heartbeat should there be any ROM that's signed by Google. Is there any hope to get that ?
My story sounds a lot like the OP. I got my OPO as soon as the invites started going out (I had signed up long before release) and I just couldn't wait to get it and start rooting and TWRPing and ROMing. I tried just about every ROM that was out there including OOS. But, as is often the case with enthusiast ROMS, there always seemed to be some little something somewhere that didn't quite work right. I also had terrible problems with the radios on almost all ROMs including the stock ROM. That got corrected during the second or third update though.
I have a lot of smartphones, so eventually, I moved onto other phones and other tinkering. Then one day, not too long ago, I wondered what it would be like to restore my OPO back to factory stock - no root; reset the tamper bit - and update to the latest official update - so I did.
I have to say that the OPO has never been as stable and reliable as it is in that condition. Best radio reception since I got the phone, silky smooth Android experience (even on two year old hardware), and rarely any crashes or FCs. Truly a STABLE phone.
But even as good as it is running now, I still worry about not getting any future updates and in particular security patches, so I will be looking to flash a good stable build of Lineage OS after reading up on other users' experiences.
Still have to say though that through all of my phones (Galaxy's, Lumias, iPhones, and everything in between), I'd still put my OPO up there with my trusted iPhone 6S for reliability and the "It Just Works" factor.
Hi! I'm running COS, the latest update i received via OTA. I'll wait for a stable build for Nougat, also, there are some xposed modules I cannot live without so i guess i wait for a little bit.
Fatsodonkey said:
I am keeping it. I would love that someone could recommend me a 6.0 rom alternative though, because can't switch to Nougat. MM has xposed and i need youtube background playback.
Click to expand...
Click to collapse
Which Xposed module let's you do that? please let me know. I know I can search but can't get one that works.
Fatsodonkey said:
I am keeping it. I would love that someone could recommend me a 6.0 rom alternative though, because can't switch to Nougat. MM has xposed and i need youtube background playback.
Click to expand...
Click to collapse
There's an unofficial Lineage OS 13 for our bacon, here in XDA. Stable no issues and xposed compatible
Until recently I've used a Sony, but a couple of bad experiences (+ 2 bad replacements) and need for wireless charging due to work + other HW features this time round, means I've switched to a Samsung S7 (G930F). Yeah, I know, Exynos development, but I needed the hardware spec and it came up cheap. Anyhow, it's rooted, unlocked and running TWRP, and I'm trying out a couple of roms..
I usually run without GApps (no flames or "Why use android if not using GApps", please!), and I'm happy to run 6.x + Xposed, or 7.x without Xposed. But as I've only ever used AOSP variants/CM, I'm a bit unsure about choosing a rom based on modding the official Samsung firmware, so I thought I'd ask here to find about the differences "under the hood".
The most stable roms for the G930F seem to be stripped-down derivatives of Samsung official releases - but how close can I get to a stable AOSP experience? I'm not only thinking about the user interface, also about "under the hood" - some custom roms might just strip out Touchwiz and apps, others might strip out a lot more and try to clean up or get closer to a AOSP/CM style "clean" rom underneath. That's more what I'm after, a good quality stable clean rom that's trying to get close to AOSP/CM as much as Samsung makes possible and without GApps already built-in.
But at that point I'm basically lacking knowledge, so... How close do roms based on Samsung's firmware actually get to AOSP? What sort of things get left in that detract from "pure" android? Which roms are closer to AOSP under the hood, or strip out "more" of the Samsung/Gapps code?
Kryx Rom or Extreme Debloated + Nexus Conversion Pack or Google pixel rom
Use LineageOS if you are willing to deal with a few minor bugs.
I'm trying out Lineage right now - it's mostly fine, the main practical issue is an over-aggressive noise gate on phone calls, it cuts off words and makes speech hard to understand at the other end. Other issues I'm seeing are lack of power menu volume panel and crash bugs in the internal web view used by some apps. Not bad for pre-release.
One main question/concern with using a trimmed-down Samsung rom is, I haven't got any idea what Samsung do to AOSP Android/kernel, nor how much of it is undone. Gods know how often manufacturer mods have led to problems and weaknesses in an otherwise good product, and so it's not a theoretical question, manufacturer versions often seem to leave the entire firmware in quite an unknown state. I know there can't be any absolute answers, but any light-shedding would be really useful.
noob924 said:
Kryx Rom or Extreme Debloated + Nexus Conversion Pack or Google pixel rom
Click to expand...
Click to collapse
Kryx 1.2 is coming up with zip sig failure when I try to flash it. No sign that it shouldn't be signed, or is expected to come up with this error though, otherwise I'd try it anyway.