I understand that Development (for in particular Custom ROMs) is being scaled down for Flagship Phones. Is the A8 in that same classification ? Is the Stock ROM very similar to the Galaxy Note one with the usual Native email client supporting full Corporate Mail Systems (Exchange)
Related
Hello Everyone,
I am new to XDA, a friend told me about this website and it apparently is the place to be
Here is the situation I am in:
I currently own a Lumia 920 (I am impressed with the quality of the phone and social media integration natively)
I require a smartphone that has the highest native compatibility between worlds (i.e. Apple, Android, and Windows). I think that the S4 may be the solution but I wanted to ask the forums before purchasing one, as I have never owned an android phone before.
I do/need the highest integration between:
Exchange email, IMAP, POP3 and Activesync
Facebook, Twitter, and Reddit - Manage the businesses social media)
Great Battery Life (I will be away from the office/home for 10+hours a day
Security - Sensitive data on the phone
Can someone please go over the benefits of owning an android phone,especially the GS4
Thanks a bunch!
Kyle
Questions go in Q&A
Thread moved
I'm a long-time Omni user on my Nexus devices. My wife recently got a Samsung Galaxy Note 10.1 2014 Edition (LTE) as part of her contract, and I cannot begin to explain how frustrating it is to be back in "Samsung's world". The hardware is incredible (Snapgragon 800, 3GB RAM, 2560x1600 display) but it is loaded with bloat on an outdated 4.3 ROM (only the wifi-only model (Samsung Octa) has Kitkat so far).
Now I know that for a device to be supported, it needs a maintainer. This is a very expensive, niche device, and I presume that there are not many users out there that will be suitable. So my question is, what does the job of a maintainer entail exactly? I've built CM for a couple of devices from source before, but that's about the extent of my knowledge with regards to custom ROM development. Is that sufficient?
I'm thinking that this device should be a fairly easy bring-up, being based on the same SOC as the Nexus 5 (amongst others).
How can I make this happen?
StNickZA said:
I'm a long-time Omni user on my Nexus devices. My wife recently got a Samsung Galaxy Note 10.1 2014 Edition (LTE) as part of her contract, and I cannot begin to explain how frustrating it is to be back in "Samsung's world". The hardware is incredible (Snapgragon 800, 3GB RAM, 2560x1600 display) but it is loaded with bloat on an outdated 4.3 ROM (only the wifi-only model (Samsung Octa) has Kitkat so far).
Now I know that for a device to be supported, it needs a maintainer. This is a very expensive, niche device, and I presume that there are not many users out there that will be suitable. So my question is, what does the job of a maintainer entail exactly? I've built CM for a couple of devices from source before, but that's about the extent of my knowledge with regards to custom ROM development. Is that sufficient?
I'm thinking that this device should be a fairly easy bring-up, being based on the same SOC as the Nexus 5 (amongst others).
How can I make this happen?
Click to expand...
Click to collapse
Being a maintainer takes a LOT of reverse engineering skills. Integrating the OEM's blobs with "normal" AOSP or CAF sources can be a royal pain.
The best bet is to try and start your bringup by using a similar device as a starting point. Same platform is OK, same platform AND OEM is better.
For example, all of the Exynos 4210 devices (except the Tab 7 Plus/7.7) share a common device tree and kernel nowadays (the 7Plus/7.7 were too different from others in the family)
All of the Exynos 4412 devices have a common device tree that's inherited, and a common kernel.
Unfortunately, unlike the Note and Note 2, the Note 3 is significantly different from the GS4. However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
The best way to learn maintainer skills is to find a device that is semi-supported and start working on figuring out how to fix its features that aren't quite working right. (In my case, I worked with atinm on resolving I777-specific issues to get that device lit up, then started working on remaining I9100/I777-common issues in CM back in the ICS days, then started on the Note which was similar to I777/I9100)
Expect to spend a LOT of time Googling stuff and searching through code. "grep", "strings" and "readelf -d" are your friends. (grep is for searching anything, strings is for looking at the strings in a blob, readelf -d shows you what libraries a blob depends on)
Even an experienced maintainer spends ****-tons of time searching for things and digging through data.
Patience is the most critical thing for a maintainer to have.
Entropy512 said:
Being a maintainer takes a LOT of reverse engineering skills. Integrating the OEM's blobs with "normal" AOSP or CAF sources can be a royal pain.
The best bet is to try and start your bringup by using a similar device as a starting point. Same platform is OK, same platform AND OEM is better.
For example, all of the Exynos 4210 devices (except the Tab 7 Plus/7.7) share a common device tree and kernel nowadays (the 7Plus/7.7 were too different from others in the family)
All of the Exynos 4412 devices have a common device tree that's inherited, and a common kernel.
Unfortunately, unlike the Note and Note 2, the Note 3 is significantly different from the GS4. However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
The best way to learn maintainer skills is to find a device that is semi-supported and start working on figuring out how to fix its features that aren't quite working right. (In my case, I worked with atinm on resolving I777-specific issues to get that device lit up, then started working on remaining I9100/I777-common issues in CM back in the ICS days, then started on the Note which was similar to I777/I9100)
Expect to spend a LOT of time Googling stuff and searching through code. "grep", "strings" and "readelf -d" are your friends. (grep is for searching anything, strings is for looking at the strings in a blob, readelf -d shows you what libraries a blob depends on)
Even an experienced maintainer spends ****-tons of time searching for things and digging through data.
Patience is the most critical thing for a maintainer to have.
Click to expand...
Click to collapse
Thanks Entropy. Sounds like I don't have what's required for the job.
Entropy512 said:
However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
Click to expand...
Click to collapse
The Note III (LTE) is the N9005, and I think the device code is hlte. I can't find a version of Omni for this device either.
StNickZA said:
The Note III (LTE) is the N9005, and I think the device code is hlte. I can't find a version of Omni for this device either.
Click to expand...
Click to collapse
Yeah, no one has done an Omni bringup yet. IbrahimA was considering doing one based on the CM bringup but he hasn't had the time.
Im just sharing Rom link with sources and download links.
There are many reasons why free and open source software is great. It allows someone to take a project and evolve it into something else that they see fit. Naturally, they have to follow the proper licenses that come with those projects, but when done right we can get software projects like /e/. /e/ is a fork of LineageOS that aims to be completely free of everything Google. Not only that, but there are a number of goals the developer has in mind for /e/ that more people feel are vital to a mobile operating system. This week it has been announced that the first beta of /e/ is now available for a limited number of devices (linked down below).
The original idea of /e/ came from Gaël Duval, an open source advocate, last year when he wrote a series of articles titled “Leaving Apple & Google. . .” It was in this series of articles when he announced that a new smartphone OS was currently being planned. The new mobile operating system had three goals including:
Be free from Google (no Google services, no Google search, no Google Play store, etc.)
Be far more respectful of user’s data privacy
Be attractive enough so that Mom and Dad, children and friends would enjoy using it even if they aren’t technophiles or geeks
It’s been a year and now the first beta of /e/ is available to the public. As mentioned, /e/ is a Google-free fork of LineageOS with this first beta being based on version 14.1. The ROM comes bundled with microG by default with the Mozilla Network Location Provider backend so location functionality will work even without GPS. The mail app is forked from K9 mail, the SMS app is Signal, the default chat app is Telegram (or you can use Signal), there’s a weather app, a note-taking app, a tasks app, and a map app (that, unfortunately, isn’t open source yet.) The account manager allows you to choose a single /e/ account for all services. The search engine is a fork of Searx, but Qwant and DuckDuckGo are available alternatives in the default browser (LineageOS’ Jelly.)
Depending on the addition of more build servers and more contributors who can maintain or port to specific devices, they are hoping to see the list of supported devices grow. Speaking of, here is the official list of devices that can test out this first beta of /e/ right now.
Essential Phone
Essential PH-1 – “mata”
Fairphone
FP2 – “FP2”
Google
Nexus 4 – “mako”
Nexus 5 – “hammerhead”
HTC
One (M8) – “m8”
Huawei
Honor 5X – “kiwi”
LeEco
Le 2 – “s2”
LG
G5 (International) – “h850”
Motorola
Moto E – “condor”
Moto G – “falcon”
Moto G 2014 – “titan”
Moto G 2015 – “osprey”
OnePlus
OnePlus 2 – “oneplus2”
OnePlus 3/3T – “oneplus3”
OnePlus One – “bacon”
OnePlus X – “onyx”
Samsung
Galaxy A5 (2017) – “a5y17lte”
Galaxy s6 – “zerofltexx”
Galaxy s7 – “herolte”
Galaxy S III (International) – “i9300”
Xiaomi
Mi 5s – “capricorn”
Mi 5s Plus – “natrium”
Redmi 3S/3X – “land”
Redmi Note 4 – “mido”
The developers are working on changing the DNS server from Google’s and bringing up the ROM to the LineageOS 15.1 (Android 8.1 Oreo) base.
Download links of the first beta build of /e/ for supported devices
https://gitlab.e.foundation/e/wiki/en/wikis/devices-list
Download link for Mi 5s Plus natrium
https://gitlab.e.foundation/e/wiki/en/wikis/device/natrium/info or
https://images.ecloud.global/nightly/natrium/
-source :https://hackernoon.com/leaving-apple-google-e-first-beta-is-here-89e39f492c6f?gi=da3aa461de7c
Credits: Romain Hunault , Gaël Duval for project e
Its Good to know new rom are still coming for our natrium devices
Screenshots
link no work natrium
I think mobile phone must need to use gapps. what is this rom different comparing the previous rom?
kuto232 said:
link no work natrium
Click to expand...
Click to collapse
https://images.ecloud.global/nightly/natrium/
Try this
Penchock said:
I think mobile phone must need to use gapps. what is this rom different comparing the previous rom?
Click to expand...
Click to collapse
There is micro G which worls alternative to google services. So all your apps runs without google services. This rom is google free rom.
I am not able to import contacts from the SIM option does not stop
I don't get why this is becoming a big thing, it's just LOS with microG. There are already automatic builds found at https://lineage.microg.org which are the exact same thing, but directly built from LOS roms. Maybe the difference is that there are different system apps?
GREETINGZ 2 ALL
Can someone plz explain to me wut do these 3 desinationz mean in conjunction with romz? Thx much peace.
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
- SM-N915F/G/P/R4/T/W8: tblte
The Samsung Galaxy Note 4 has 13 models and variants. Generally the variants are the same device models with some different features and specifications, as the amount of internal storage, processor or just 3G/4G frequencies that may be different depending on the country the Samsung Galaxy Note 4 is available to.
They can be group in the above 3 categories.
More info about that you can find here as well:
https://www.phonemore.com/models/samsung/galaxy-note-4/
The 3 groups above will help you to determine what is your phone's type and accordingly chose a rom for your needs.
PS. those are for the snapdragons models.
those that have Exynos cpu in them, have different letters , too
According to Alumia Italia there's a 2022 version of Galaxy Tab S6 Lite coming:
https://twitter.com/i/web/status/1522831548642385921
This new version has a Snapdragon 720G CPU in stead of an Exynos 9611 in the 2020 version
Noob question here.
When I look at LineageOS supported Samsung devices, I see the majority are Exynos. There are a few snapdragon devices supported for Samsung and of course other manufacturers.
Since the 2020 Tab S6 Lite seems to be one of the newer tablets that is supported by LineageOS, I'm wondering if this move to Snapdragon means the 2022 version is unlikely to be supported.
Not asking about future predictions, but rather because I'm ignorant of the differences between the chips/chip mfgs/device mfgs.
Is there something inherent about Snapdragons that make it hard to open up for customizing?
Is it more of a difficulty due to Samsung decisions around how they implement devices with Snapdragons vs Exynos? (Google pixels for example, of course have snapdragons and are great for LineageOS/Graphene
Anyway, would appreciate a small explanation if anyone can say why custom ROM support on Samsung non-Exynos devices seem to be so rare.
Thanks
The reason why you see so few custom ROMs for Snapdragon-based Samsung devices (phones, mostly) is that these devices are usually ones in the North American market, whereas Exynos is used internationally. Samsung's NorthAm devices are locked down tight with their Knox nonsense, which means the bootloader can't be unlocked (a prerequisite for installing a custom ROM). That's why you tend to only see custom ROMs for international versions of their phones.
Tablets, I think, are another matter, at least for the Wi-Fi-only variants (I can't speak to all the LTE variants as I don't own one or have any experience with them). Tablets are generally region-agnostic and can usually be used anywhere, so it makes no sense for Samsung to clamp down on them (unlike their phones), no matter which processors they use. So, if Samsung were to release a Snapdragon refresh of the Tab S6 Lite, I'm betting that it'll be able to be unlocked... provided this whole thing actually comes to pass, of course.