With the release of Android 10, we have yet to realize the state one ui will be in when Samsung gets around to the update, however my question being is one where porting might be an option from tab s4 to tab s3, or is it just custom roms until developmentally impossible? (the developmentally impossible part being unlikely)
I want to start a real conversation about advance compatibility porting, as is the issue with dex, if we could get a bare bones port started until we could make our own variants stable, just like we did with the google lens.
I understand the issues with infringements, and hard bricks, but I believe if we could make a port just like the one ui/pixel experience rom. [see thread(https://forum.xda-developers.com/note-fe/development/rom-team-pixel-pie-1-0-t3934106) for details] We could maybe port oem updates to different devices ((minding scaling and resizing issues) not the best example, I know).
Now I'm not too keen on porting whole oem updates from proprietary device to proprietary device, or even from oem apps, but maybe we could come up with a solution.
Any response will be appreciative.
Related
This is sort of a technical question regarding the architecture of the Android OS and possibly its licensing, etc... For most Windows computers, you can simply download, or buy a copy of Windows directly from Microsoft, install it on any x86 hardware and it will be fully optimized (speed, battery life, etc...). Why can't Google make a build of Android like this so I can simply buy a copy from them and install it on my phone with OEM hardware overtop of their bloated and skinned version of Android? For example, why can I not buy, say a Galaxy SII, and then buy a copy of 'Vanilla Android' from Google and install it legitimately and have it work? I realize that I can flash a copy of CM7 or some other custom ROM from open source developers but I would like to be able to just simply buy a copy of stock android, directly from Google, install it on my device, and have it work, just like with a Windows computer. Is the reason Google does not do this due to licensing issues? Or is there some other reason for this seemingly obvious solution to all the annoying OEM and Carrier bloatware that most Android phones are subject to?
Note: I realize this question has already been asked but I was hoping for a reason for why Google can't (or won't) provide an alternate build of android that works on all devices in addition to the stock builds that come with phones. As well, why do device manufacturers insist on being total d'bags and not just simply release all the drivers for their phones so we can choose the best phone for the reasons you want to (i.e. speed, build quality, price, specs etc...) and not because of the stupid bloatware or lack thereof?!?
Because, stock Android means absolutely NO drivers installed for a specific device so your phone WILL NOT function (No Touchscreen, No signal, etc). Samsung releases their own firmware after compiling their own Baseband, Kernel and ROM. This contains their touchscreen drivers, wireless drivers, etc. When you change the ROM, you essentially void the warranty, so manufacturers do not encourage it, but they do allow you to combine their components together for you to make your own custom ROM (using their baseband, kernel and/or Samsung official rom as their base roms)
They build their own ROMs so that they know what they are managing, and what they need to fix and update. Also there's also a USP for every product released, let's say, Sony Ericsson's UI with Timescape, Samsung's Touch-Wiz UI, Motorola's Blur, etc. If you want a stock phone then I suggest you go for the Galaxy Nexus, or one of those Nexus phones that Google themselves maintain.
If you want a stock copy of Android OS on the Galaxy S II, try CyanogenMod, it is a custom ROM which is very stock and runs on every device, BUT each device, you need to download a DIFFERENT rom, because their different drivers. If you expect Google to release drivers for each phone for their stock OS'es, they will go insane as their are an uncountable amount of Android devices released on a weekly basis
Great answer Nicholas I read this about an hour ago & spent 10 minutes trying to come up with a detailed answer that would make sense to a user of any experience level. Then I gave up
I'm referring to all smartphones not only SGS2 here.
Ad part 1 - It could be difficult. Every device is different and going this way Google would have to prepare/upgrade it's OS for every device on the market. This is hell of a job, so it's up to device manufacturer or community to do this. I think smartphones differ to much (much more than PCs), so it's not possible to create one system for all. Besides, warranty issues - manufacturer of the device could not be responsible for problems caused by someone else's OS (this is understandable). It's also worth to notice that flashing a smartphone is a process completly different than installing OS on PC as PC cannot be bricked in this process. Give users easy way to flash anything on their phones and you have another gate to problems as they will surely flash everything including windows dlls on their phones. You say that on PC any OS can be installed, I say FOR NOW. In a few years You will have a choice - cheaper PC, windows only, OS only from manufacturer or more expensive one and you install anything You want. Why do you think UEFI was created? It will happen unless PC market collapses, because according to some market analytics we are entering post-PC era and mobile devices will became our main devices.
Ad part 2 - It's just business model. Manufacturer/carrier does not sell You the device (that's how they see it), they sell You some bunch of features and have no interest in You adding more of them to Your device. SGS2 is a flagship phone and it's kernel sources are released. It has unlocked bootloader also. You payed accordingly - so you free to do much more things, and use full hardware potential. With lower-end devices - manufacturers prefer that You buy another device instead of upgrading current one. Market insist on lower prices, but with every device unlocked/released drivers etc. prices would be much higher and smartphones much less affordable. Devices like SGS2 are created for very specific users - power users/devs/businessmans/enthusiasts.
I think that You want impossible. IMHO it's almost miracle that Samsung released some smartphones with unlocked bootloader so You can flash everything You want. (btw. it was the reason for me to choose sgs2). And about that "bloatware obsession" - I just don't understand why some people are sooo obsessive. I don't find some app usefull - I don't use it, period. But TBH I must say that Samsung put some serious s**t preinstalled on SGS2. Sometimes it outranks even worst market junk.
Hi!
I have been a heavy user of custom ROMs for more than three years now on all my Android devices. Lately, although I have a phone that not so long ago was still Samsung's flagship (the galaxy S4, I9505), the pictures I get with it really suck. A couple weeks ago, the phone could not detect my SIM card (pure hardware issue), so I re-installed the stock firmware and took it to the repair shop to get the warranty repair. They fixed it and I got my phone back. Just to make sure it was working fine, I decided to use the stock ROM for a while, and oh surprise: the camera takes much better pics in low light conditions or indoor than the same camera with any custom ROM app (usually AOSP-based, AOKP or CM-based). I tried to download the Google camera, and the low light pictures really suck. Then I tried a bunch of camera apps from the Play store, but I invariably got similar results to what I got with my custom ROMs.
That got me thinking. I'm no dev nor programmer, so I won't get technical, but it seems to me that there can be two reasons for the samsung app to work better:
- Either it has access to (proprietary) hardware drivers that other camera apps cannot access, and therefore it can get everything out of the camera hardware
- Or Samsung (which is not known to be great for its software) has developed a great camera software.
I would think it's something along the lines of the first reason. So does that mean I am either stuck with a ROM I cannot stand (Touchwiz is awful, has always been, and may always be) and a decent camera, or a decent ROM but a camera that is kind of useless when I'm indoor?
If so, how are the cameras on other similar phones (I'm thinking Nexus 5, Sony Xperia, etc.), running on custom ROMs compared to the stock camera apps? Is there also a noticeable difference, or is it just with Samsung?
I understood that you cannot run the Samsung camera apk on a custom ROM (even one on a Samsung phone), because the camera relies on some kind of Samsung proprietary framework.
Does this mean I should be looking for a phone that is running not only on open source software, but also open source hardware, does that even exist?
Anyone has noticed something similar? Am I the only one to be bothered by this?
I'll post here a couple pics taken in the same ambient light conditions. One with the Samsung camera (Auto setting), one with Google camera, and one with another camera app from the market (don't remember which one, but I tested about 15 of them and their results were quite similar).
Anyway, even if you don' have a solution to the problem but can point me to information that could help me understand how to choose my next phone, I would really appreciate. Thanks!
Cheers,
Fa
fabecoool said:
Hi!
I have been a heavy user of custom ROMs for more than three years now on all my Android devices. Lately, although I have a phone that not so long ago was still Samsung's flagship (the galaxy S4, I9505), the pictures I get with it really suck. A couple weeks ago, the phone could not detect my SIM card (pure hardware issue), so I re-installed the stock firmware and took it to the repair shop to get the warranty repair. They fixed it and I got my phone back. Just to make sure it was working fine, I decided to use the stock ROM for a while, and oh surprise: the camera takes much better pics in low light conditions or indoor than the same camera with any custom ROM app (usually AOSP-based, AOKP or CM-based). I tried to download the Google camera, and the low light pictures really suck. Then I tried a bunch of camera apps from the Play store, but I invariably got similar results to what I got with my custom ROMs.
That got me thinking. I'm no dev nor programmer, so I won't get technical, but it seems to me that there can be two reasons for the samsung app to work better:
- Either it has access to (proprietary) hardware drivers that other camera apps cannot access, and therefore it can get everything out of the camera hardware
- Or Samsung (which is not known to be great for its software) has developed a great camera software.
I would think it's something along the lines of the first reason. So does that mean I am either stuck with a ROM I cannot stand (Touchwiz is awful, has always been, and may always be) and a decent camera, or a decent ROM but a camera that is kind of useless when I'm indoor?
If so, how are the cameras on other similar phones (I'm thinking Nexus 5, Sony Xperia, etc.), running on custom ROMs compared to the stock camera apps? Is there also a noticeable difference, or is it just with Samsung?
I understood that you cannot run the Samsung camera apk on a custom ROM (even one on a Samsung phone), because the camera relies on some kind of Samsung proprietary framework.
Does this mean I should be looking for a phone that is running not only on open source software, but also open source hardware, does that even exist?
Anyone has noticed something similar? Am I the only one to be bothered by this?
I'll post here a couple pics taken in the same ambient light conditions. One with the Samsung camera (Auto setting), one with Google camera, and one with another camera app from the market (don't remember which one, but I tested about 15 of them and their results were quite similar).
Anyway, even if you don' have a solution to the problem but can point me to information that could help me understand how to choose my next phone, I would really appreciate. Thanks!
Cheers,
Fa
Click to expand...
Click to collapse
So here come the pics. Of course XDA compresses them, but you'll get the idea.
Fa
That is the example difference between things that are built for the device over using open-source options. Software will always be better from the OEM. You see the same thing with HTC and Sony devices. Take the m7 and m8. They have great cameras as long as you use HTC Sense. Other wise all you get is a basic 4 mpx camera that sucks. If you want one that works the same no matter the rom then get a nexus. This is something OEM are doing to make people want to use their software
Thanks @zelendel,
A Nexus could be an option, but the screen size of the Nexus 5 was already too large for me (and so is my current phone, the Galaxy S4), so there's no way I'm getting a Nexus 6 (plus it's prohibitively expensive, at least here in Europe). When will Google make a Nexus mini or compact? That would rock, especially if they go the Sony way (not compromising too much on hardware features). The only downside of Nexus phone is their lack of MicroSD card slot, but that's off topic.
Anyway, what about the Google Edition phones? As I understand, they have the same hardware as their OEM counterpart (don't they?), but instead of running on proprietary stock ROMs, they ship with a pure Vanilla Android. Does this mean they ship with a camera that sucks, or is there some kind of tweak included to get the most of the camera with those editions, too? If so, would flashing that ROM help (if I can get my hands on it)? Unfortunately it seems the whole Google Edition concept has not gained a lot of traction (maybe because of the unavailability of the handsets in many places, maybe thanks to the OEM who did not play fair game and rather managed to get their crappy proprietary stock versions in the hands of customers), so I'm trying not to get too excited about this either.
I guess I will have to go to my local phone shop, spend time there with different devices and see if some of them have less heavily customized skins than TouchWiz. That means I'll no longer go for a Samsung, which have been my only devices so far. The end of an era...
fabecoool said:
Thanks @zelendel,
A Nexus could be an option, but the screen size of the Nexus 5 was already too large for me (and so is my current phone, the Galaxy S4), so there's no way I'm getting a Nexus 6 (plus it's prohibitively expensive, at least here in Europe). When will Google make a Nexus mini or compact? That would rock, especially if they go the Sony way (not compromising too much on hardware features). The only downside of Nexus phone is their lack of MicroSD card slot, but that's off topic.
Anyway, what about the Google Edition phones? As I understand, they have the same hardware as their OEM counterpart (don't they?), but instead of running on proprietary stock ROMs, they ship with a pure Vanilla Android. Does this mean they ship with a camera that sucks, or is there some kind of tweak included to get the most of the camera with those editions, too? If so, would flashing that ROM help (if I can get my hands on it)? Unfortunately it seems the whole Google Edition concept has not gained a lot of traction (maybe because of the unavailability of the handsets in many places, maybe thanks to the OEM who did not play fair game and rather managed to get their crappy proprietary stock versions in the hands of customers), so I'm trying not to get too excited about this either.
I guess I will have to go to my local phone shop, spend time there with different devices and see if some of them have less heavily customized skins than TouchWiz. That means I'll no longer go for a Samsung, which have been my only devices so far. The end of an era...
Click to expand...
Click to collapse
The GPE device dont come with stock android completely. I have a GPE HTC M7 and the gpe software has some of the closed sourced drivers and such for things like Beats audio and the camera. As I run pure AOSP I wind up with a 4mpx camera that really sucks. While i agree alot of the newer devices have huge screens that make it almost pointless for me. The m7 is not bad at about 5in. But then again it doesnt have an SD card slot but comes with 32gb of storage which I think is plenty for my use. Part of me misses my old samsung devices but I made the mistake once of getting the one with the Samsungs chip and not the snapdragon which killed development.
zelendel said:
The GPE device dont come with stock android completely. I have a GPE HTC M7 and the gpe software has some of the closed sourced drivers and such for things like Beats audio and the camera. As I run pure AOSP I wind up with a 4mpx camera that really sucks. While i agree alot of the newer devices have huge screens that make it almost pointless for me. The m7 is not bad at about 5in. But then again it doesnt have an SD card slot but comes with 32gb of storage which I think is plenty for my use. Part of me misses my old samsung devices but I made the mistake once of getting the one with the Samsungs chip and not the snapdragon which killed development.
Click to expand...
Click to collapse
Alright! Well, if I could find the GPE edition for my phone (I9505), then I would get all the camera features and none of the TouchWiz crap, which would already be quite an improvement over what I have now (complete TW stock). I guess another possibility would be to flash a stock based ROM that is rooted and from which I could remove all the bloatware...
OK, the hunt is on for a new ROM!
Cheers!
Fa
fabecoool said:
Alright! Well, if I could find the GPE edition for my phone (I9505), then I would get all the camera features and none of the TouchWiz crap, which would already be quite an improvement over what I have now (complete TW stock). I guess another possibility would be to flash a stock based ROM that is rooted and from which I could remove all the bloatware...
OK, the hunt is on for a new ROM!
Cheers!
Fa
Click to expand...
Click to collapse
If you want all the features of the camera then yes I would run a stock de bloated rom. I used to run Samsung devices and you can remove most things which will give you the camera app which has all the best features.
Hello dear people, I hope I can be forgiven for asking a potentially stupid question.
With my 850F batteries failing, I am hoping to get some more months out of this once expensive phone. So I've been looking at some custom ROMs to see if they make a difference. But it seems like the fingerprint reader never works. People tell me it's because the driver source isn't available.
So, is this a question of legality (the driver cannot legally be included with roms) or of possibility (the driver is deeply dug in)? Because if it's the former, I was wondering if there's some file I can take out of the stock firmware and put onto my phone to make the fingerprint reader work with any rom?
Also, I would like to express my dissatisfaction with the terrible support Samsung has given for this phone. We got one late update from Kit Kat to Lollipop. It looks so vanilla it makes one wonder why it took so long. The black background colors from Kit Kat changed to white, a terrible choice for an OLED screen. So with regard to the already meager battery, this update has been a regression.
I'm trying to get as many months out of this phone as I can until the next generation of phones comes out. I love the Samsung hardware but I might look for brands that are either more frequent with updates or open source enough so that custom firmware development is not hindered by unsupported hardware.
I'm thinking the next phone should just be under 5 inch and powerful enough to be a desktop computer running full Linux, like Ubuntu OTA 11 (if someone introduces Android compatibility) or Maru OS, so I don't have to carry around a laptop anymore.
Fingerprint scanner works fine with all Samsung based ROMs (OzcanROM and EpsilROM) only CM ROMs (CM and ResurrectionRemix) don't support it (aswell as heart rate monitor)
93drago said:
Fingerprint scanner works fine with all Samsung based ROMs (OzcanROM and EpsilROM) only CM ROMs (CM and ResurrectionRemix) don't support it (aswell as heart rate monitor)
Click to expand...
Click to collapse
I hadn't even thought of the heartrate monitor yet!
Yes, I tried those non-Samsung ROMs. I thought if I use the Samsung-based ROMs, I might as well use the Samsung ROM.
Because they use proprietary drivers, and samsung does not disponibilize them, well, when marshmallow launch, its is POSSIBLE that Samsung bundle the source code with a generic fingerprint driver, as fingerprints reader support is a generic and system wide thing in MM, just like when hardware acceleration via GPU was an propietary thing in android 2.3 and being default on android 4.0
Greetings,
I'm posting this on the General as the forum associated with this mobile device is pretty much dead ATM. It falls very much more in the category of "I need help figuring out how to do this Android Global thing" rather then a very specific issue with a device.
The long and the short of it is the Samsung Galaxy On5 SM-G550T/1 was a fairly short lived phone in the US. It's a barebones phone that has a lot of features of design choices of the Galaxy S5 and S6 while having very minimal accessory hardware (which as an altimeter and advanced GPS systems).
This phone, however, has seen *A LOT* of popularity in Easter EU, Middle Eastern or Indian markets and thus there is a TON of Rom development still active for this phone.
The SM-G550FY has significant differences with the Sound Drivers, Camera Drivers, Bluetooth Drivers and Modem Drivers that makes the ROMs, in general, compatible enough to be installed, but not compatible enough to have the Sound or Camera work and has varying levels of Modem and Bluetooth viability; more often then not, they work though.
Someone finally dropped a hint that most these drivers are in the /system/lib folder requiring CHMOD of 740 to work; but no one to the best of my knowledge has actually gotten this "workaround" to work. This was something that was completely foreign (no pun intended) to many of us who have posted in that forum. I've had zero success with this, but it seems to have gotten me looking in new directions for fixes.
So my questions are a few fold that I hope the XDA greater community can help with:
#1.) Is there a way to import the correct drivers that are verified working in the same version of Android from another rom?
#2.) Are drivers for different versions of Android the same (IE 6.0 and 7.0 since those are the ROMs being regularly released) or are we reliant on Samsung to release a properly working set of 7.0 drivers to get Android 7.0 working on the US/CA variants of the phone?
#3.) I'm looking for good resources to learn how to build an installer for a ROM to try to build and release a patcher to make SM-G550FY roms compatible with SM-G550T/1 Roms. What resources could you suggest to get myself better up to speed to doing this.
#4.) I'm also looking for good resources to learn how to build ROMs perhaps based on Lineage for my model of the phone. Where would I go to learn more about that?
Thanks for any help you guys can provide.
I'd like to get to as close to vanilla as possible. Not a fan of Samsung's ui or bloat. I'm coming from the tab s1 which had some pretty good roms. There are none for this device and it's almost 6 months old. I would make one myself but lack the necessary skills
Most of the newer top end Samsung Tablets get very little developer support since they cost so much. Happens with every new tablet having people asking where the developer support is for it. Samsung newer UI much nicer and any vanilla roms would take away most of the functionality that makes the tablets great. Apparently the S5e has some dev support.
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Markeee said:
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Click to expand...
Click to collapse
Not everyone gets the update at the same time (don't know how they handle when and who should receive the update). I only got a November update a few days ago (though some claimed to have already gotten it) and it offered few improvements. The tablet still feels the same as usual.
As one must choose between custom ROMs and Knox (especially warranty), I'm currently at a loss myself, and for the time being I haven't heard of anyone trying (or succeeded in) booting a GSI on S7/S7+ probably because of this, although it's theoretically possible (again thanks to Treble). At least we now have TWRP... it might be better if one day custom kernels become available.
So far this is the only tablet I know that can offer 120Hz display. My current phone (Razer Phone 2 which is also 120Hz-capable) still doesn't have a specialized ROM but I can already run GSIs on it with adequate performance. For new devices, going for GSI might be easier, but performance-wise it still has a way to go compared to specialized ROMs.
Think it has to do with the fact that snapdragon is locked on samsung