[Q]will AOSP roms be likely for verizon S5? - Galaxy S 5 Q&A, Help & Troubleshooting

Wondering if AOSP roms will be easily flashable for the Verizon S5? Specifically LiquidSmooth. I know newer S4's etc have a hard time installing AOSP roms with SafeStrap. Think same will remain true for S 5?

Non-stock roms would result in certain features ceasing to work. For example, I'd say the fingerprint scanner will never work outside of stock. Also, the camera is likely to lose a lot of features, the on the fly HDR mode and multi focus shots being two of them, not to mention an overall loss of quality in comparison to the Samsung camera drivers. The camera for me is the primary reasons for upgrading from the S4. This is the first Android phone I will own where I'm not that bothered about non-stock roms being available, TW isn't as offensive as it used to be and it's improved even further on the S5.
As for the question, the open source nature of the Snapdragon architecture will almost certainly result in AOKP/AOSP/CM based roms becoming available, and the locked bootloaders on the American carriers will be overcome eventually. Just don't expect it to happen immediately or for that many of them to appear as the majority of reputable developers will probably be avoiding the S5 after the Knox debacle. Which is a shame but understandable, Samsung have really f**ked up with Knox. I wouldn't be getting an S5 if it wasn't for being offered a deal that was too good to turn down.

Related

custom rom developement

strange their is no massive improvement in custom roms section as compared to HTC ONE. No more devs are taking intrest for our beloved s4. it's really strange. Waiting for some nice custom roms.............
not strange since the exynos version has closed drivers which samsung won't release so Aosp for it would be a pain but custom touchwiz Roms there will be a lot of these
as for qualcom one there seem to be more users but still not enough
so give this device some time and a 4.3 update and this place will be flowing with custom Roms and some nice kernels 2
I was wondering the same thing but then looked closely. A lot of the One's roms are based on stock with tweaks and stuff.. We still have all the aosp/aokp/cm etc roms built from the ground up for the i9505 at least.
Give it time, still a relatively new device. Runs well so far as it is. Should pick up once the GE edition is out, more so for the i9505 if based on same hardware. Although I for one prefer TW due to it's features, camera etc.

I need your experience

After being aware that the knox e-fuse on my note 3 is irreversible I am unsure whether I should flash a custom rom or not.
Here I present my reasons for the sake of understanding and validating through your experience if you may share thankfully:
1. I have used nobloat app & root to freeze/disable most stock bloatware.
2. I am not experiencing any lag in real world experience. So I wonder if the speed increase of the custom roms is real or just placebo effect.
3. There is still hope that Samsung will release the 4.4.4 Android for Note 3 as it already did for the Sprint version. Seems to be very soon.
4. I believe the resale value of the note 3 will decrease if I triggered knox and void warranty.
5. I can't spot the touch wiz services in the processes and not sure if it's taking too much ram or its the Android operating system itself that is consuming.
And finally every flashing instruction out there put a lot of warnings and lack of responsibility if the phone is bricked and there isn't even one rom where the forum users don't complain about lack of functionalities so I become unsure whether I should trust the users or they're just noobs who don't comply to the instructions properly.
So I need some advice to end this confusion, are the custom roms worth losing spen functionality along with all samsung features and triggering knox?
iamarto said:
After being aware that the knox e-fuse on my note 3 is irreversible I am unsure whether I should flash a custom rom or not.
Here I present my reasons for the sake of understanding and validating through your experience if you may share thankfully:
1. I have used nobloat app & root to freeze/disable most stock bloatware.
2. I am not experiencing any lag in real world experience. So I wonder if the speed increase of the custom roms is real or just placebo effect.
3. There is still hope that Samsung will release the 4.4.4 Android for Note 3 as it already did for the Sprint version. Seems to be very soon.
4. I believe the resale value of the note 3 will decrease if I triggered knox and void warranty.
5. I can't spot the touch wiz services in the processes and not sure if it's taking too much ram or its the Android operating system itself that is consuming.
And finally every flashing instruction out there put a lot of warnings and lack of responsibility if the phone is bricked and there isn't even one rom where the forum users don't complain about lack of functionalities so I become unsure whether I should trust the users or they're just noobs who don't comply to the instructions properly.
So I need some advice to end this confusion, are the custom roms worth losing spen functionality along with all samsung features and triggering knox?
Click to expand...
Click to collapse
Hello.
for me it is down to personal preferences. Some people, like me, hate the bloated touchwiz and the lack of customization and sometimes the occsional laggs turns me off. With custom rom, you may get a better performance if you know how to tweak your setting, plus you have tons of customization ( esp with CM, AOSP roms etc), but you have to sacrifice the s-pen features. If you rarely use your s-pen, it should not be a problem, right? Nevertheless, there are many roms out there with s-pen features still intact, like the tweaked touchwiz rom, S5 port etc. so really it is down to your preferences. I personally dont mind the knox status, as many general consumer wouldnt know about it either if we're going to sell our device to them. Just flash stock rom and everything should be okay.
and oh about flashing, just follow the instructions provided slowly and carefully, in time, it will be a walk in the park for you, lol. :silly:
there are many good people here, even if you are to mess up, there will be help and solutions, most of the time.:fingers-crossed:
iamarto said:
After being aware that the knox e-fuse on my note 3 is irreversible I am unsure whether I should flash a custom rom or not.
Here I present my reasons for the sake of understanding and validating through your experience if you may share thankfully:
1. I have used nobloat app & root to freeze/disable most stock bloatware.
2. I am not experiencing any lag in real world experience. So I wonder if the speed increase of the custom roms is real or just placebo effect.
3. There is still hope that Samsung will release the 4.4.4 Android for Note 3 as it already did for the Sprint version. Seems to be very soon.
4. I believe the resale value of the note 3 will decrease if I triggered knox and void warranty.
5. I can't spot the touch wiz services in the processes and not sure if it's taking too much ram or its the Android operating system itself that is consuming.
And finally every flashing instruction out there put a lot of warnings and lack of responsibility if the phone is bricked and there isn't even one rom where the forum users don't complain about lack of functionalities so I become unsure whether I should trust the users or they're just noobs who don't comply to the instructions properly.
So I need some advice to end this confusion, are the custom roms worth losing spen functionality along with all samsung features and triggering knox?
Click to expand...
Click to collapse
A) I believe some custom ROMs are still based on Samsung ROMs, in those you might retain pen and so on, but basically those are 100% what you can also achieve yourself with root, the right programs and the right configuration
B) In my (limited, but still) side-by-side experience the Samsung-stock-based ROMs correctly debloated and configured do not appear in any way less snappy than any custom ROM (running the same programs installed), and the Samsung-based kernels have always shown (much) better battery life. The key part here is however is "correctly debloated and configured"!

[Q] A question about features on AOSP based roms for SGS5

I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
AndroidDeveloperLB said:
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
Click to expand...
Click to collapse
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
stevey500 said:
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
Click to expand...
Click to collapse
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
AndroidDeveloperLB said:
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
Click to expand...
Click to collapse
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
stevey500 said:
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
Click to expand...
Click to collapse
I see. So it takes a lot of work.
Say, you mentioned the SGS3. I have this device. Do you think it will ever support screen recording on CM ? Currently it's very very slow. I've tried the special customized rom that's based on Note 2, and this feature worked fine there. I've left this rom because of some reasons I don't remember about (maybe stability).
All those features are available in samsung based custom roms. Why does it have to be AOSP based?
Sent from my SM-G900F using Tapatalk

No Spen for 5.1.1 [HLTE/TMO/SPR/VZW][ROM][CM12.1][5.1.1_r26] Temasek's UNOFFICIAL

Hi everybody
After flashing rom 5.1.1 from [HLTE/TMO/SPR/VZW][ROM][CM12.1][5.1.1_r26] Temasek's UNOFFICIAL Build v18.4, i can't find anything relates s pen, s note, air command. It means that i can use s pen function. Can anyone tell me : does 5.1.1 support s pen?
Thanks so much.
Regards.
All im gonna say is wow !!!
sorry, i don't understand what your mean ?
no you can't use spen with cm roms, you may need to download third party apps or any mods, like trying to install moded spen air command.
He thought maybe Samsung made cm.
Sent from my SM-N920F using Tapatalk
Support? Yes and No. Cyanogen Mod supports S Pen with some apps, honestly I have no interest about CM and stuffs, but you can ask on that particular ROM's thread which apps you might use as replacement to S Note and all that. And by no I mean the integration is nowhere near as flawless as it is on TouchWiz based ROMs, but then again that's quite normal.
MINH19051991 said:
Hi everybody
After flashing rom 5.1.1 from [HLTE/TMO/SPR/VZW][ROM][CM12.1][5.1.1_r26] Temasek's UNOFFICIAL Build v18.4, i can't find anything relates s pen, s note, air command. It means that i can use s pen function. Can anyone tell me : does 5.1.1 support s pen?
Thanks so much.
Regards.
Click to expand...
Click to collapse
Let me explain.
The official firmware made by Samsung is called TouchWiz, and there are ROMs based on it, and all of the functionality of the device is kept by flashing such a ROM.
Downsides: as much as the developers here making TouchWiz ROMs are trying, TouchWiz' innate lag is close to impossible to deal with, and people who cannot simply stomach that, flash AOSP ROMs.
AOSP stands for Android Open Source Project: code provided by Google themselves, which allows developers to create a ROM based off pure Android.
Which means that when you flash an AOSP ROM (Cyanogenmod, Tema's version of CM, Resurrection Remix, Slim, etc.), you are flashing a ROM that basically turns your device into a Nexus.
Nexus phones don't have S-Pen.
Pure Android doesn't support it.
Anything you found on TouchWiz as functionality CAN be achieved to some extent on an AOSP ROM by flashing various mods and installing apps and frameworks and whatnot, but it will not work as well as on TouchWiz.
So my suggestion is that if you use S-Pen regularly, you will want it with it's full functionality, and for that you find a TouchWiz based ROM, we have a couple of good ones. AryaMod, Audax, various ports of the Note 4 and Note 5...
If you go AOSP on the other hand, your phone will be A LOT faster and more responsive, but you will find a hard time restoring some S-Pen functionality with it.
Yeah, well let me state some FACTS here as well, in case some amateur completely misses the main flaw in the above post.
Yes, TouchWiz lags, that's beyond any question, but who said flashing a Cyanogen ROM turns your device to a Nexus phone? That's beyond ridiculous! AOSP is great, fast, stable, as good as Android could and should be. But Cyanogen isn't that! It's based on AOSP, but with plenty of bugs, and not tiny bugs either. I don't have any time or interest about pointing them out, but just Googling will reveal them.
A Nexus is a Nexus, which runs on naked Android without any sort of customisation whatsoever, which is called AOSP. A Cyanogen port can never have same stability or bug free nature like a AOSP ROM, N E V E R. Now I honestly don't care if some troll or fanboy comes and say there are no bugs, well that's as usual hilarious. You have to have use a stable and bug free thing first to notice or comment on which are bug free, which are not, LOL!
This is the actual sum up:
TouchWiz: Stable, slow, laggy sometimes (when people say the lag is impossible to bear, well that's when you should find your dictionary and look up for the word 'exaggerate'), but with every feature possible, needless to say S Pen integration is excellent.
Cyanogen mod/ or any AOSP port: Turn your Note 3 to something other than Note 3. ROM will be faster than TouchWiz, but again, it's not that fast that it would make a world's difference, and you lose all the Samsung features, and some of them are quite important ones, and there are bugs, some of them are quite important as well, like poor call quality or degraded photo/ video quality! But then again there will always be people who don't call form their "mobile phone" or snap any photos, and then there is the S Pen. But look at the bright side, you can now scratch your ear with it.
At the same time, I would prefer if Samsung moves to clean Android like Motorola or Sony, keeping some of their useful apps like S Note, Messaging an Dialler app etc., cause there is no real point of having a totally heavy kinda skin on top of Android when the main Android is pretty good itself. They can add a bunch of apps, they don't necessarily need to add a whole framework for that.
Thanks everybody so much i choosed tazzy-audora rom. This is great rom

[Q] Marshmallow roms stability

Hello, I would like to know how are the android 6 roms, especially aosp/aokp or cm?
I want to buy s4 but i need to know if there will be restarts, fcs or other things on custom MM roms in front of stock LP roms.
Thanks
Depends on what model you plan on getting.
Also, stability varies a lot from user to user.
I personally never have any issues with ROMs I use.
Hi there
I would say that Official Cyanogenmod 13 is a good choice or a more optimised one like JDC is a great choice. They are definitely stable and usable as a faily driver.
In terms of which S4 to buy... I would say hold off the American Carrier ones as they prove to be a pain when flashing custom Roms. I'd say the i9500 may not be the best option as though it has slightly better performance with its octa-core processor than the snapdragon ones, it doesn't have 4g capability which instantly makes the phone feel dated. i9506 seems good as it supports the LTE advanced and is faster than i9505, however the main drawback is the custom rom support is not as good as the i9505 model. Overall I would reccomend the i9505 model with Snapdragon 600 processor, LTE capability and the mass custom Rom support.
Please leave a like if this helped!
I would get I9505. Last I used CM on xperia x8, it was fast but had many random reboots and other problems. Since this I have used stock or stock based custom roms with almost no problems. Sometimes when I read about CM/aosp I still find random reboots posts but also posts presenting no problems. Thats why i am asking

Categories

Resources