Related
Hi all,
I've tried several passes at Google searching and haven't found these answers. I'm sure this community can help.
I've already rooted my Kindle Fire and put the stock JB ROM on there, good experience and it gave my KF new life.
So I am thinking about rooting and romming my T-Mobile Galaxy S3, but I have a few concerns and questions.
- What TMobile and Samsung features will I lose if I rom? Obviously for the most part none of their apps matter. But I heard that I would lose the ability to call/text over my Wifi connection, which would be a deal breaker considering the cellular connection quality in my house. Is that true? Are there any other features I might care about, that I'd lose?
- Will the face buttons on the S3 still work as they do now?
- Is the "Google Experience" ROM the same as the "stock" ROM? I heard about the "Google Experience ROM" on a podcast but cannot find this ROM in the forums.
- Anything else to consider? This is my first time rooting a phone - S3 was my first smart phone.
Thanks!
Dave
Just because you rooted, won't make you loose any of these features you do actually use. On the contrary you get to remove crap you don't care for. Without Root, your were previously prevented from removing some of the pre-installed apps.
Here's a good link for you to see what can be safely removed.
Now if you chose to install custom Rom, you stand to potentially loose Fabled Wi-Fi Calling. Face Unlock will still be there on other Roms.
Something else you need to know. There are 2 types of Roms. One that Samsung provides is called Touchwiz or TW Rom based on the framework of the same name. The others as you referred to as "Google Experience" Roms. These are commonly called as AOSP Roms. These roms don't have the Touchwiz framwork so won't support features such as Wi-Fi calling, since those only work on Touchwiz. There are other Non-Samsung Touchwiz roms. You will see a list of those and the AOSP Roms in my second link bellow for the Bible.
Since this is your First time on a Smart phone, here's few links you can read.
Welcome to your S3
Galaxy S3 Resource Bible
Hope this helps.
Please read ALL our sticky threads before doing anything to your device!
Sent from my SGH-T999 using Tapatalk
Thanks for the info. OK from your comments and the links you provided, I gather that any ROM that is a TouchWiz based ROM will still contain WiFi calling. Is that correct? So theoretically I could load one of these ROMs and still be good to go. I have a couple more questions though.
- I've seen a few references to "stock" ROMs. Does the term stock refer to the base Android build (so there is only one of these per release of Android), or does it refer to the software that came with each phone (so there is one per phone)? If it is the latter then would I be able to load the TMobile stock ROM if I did not like the custom ROM I chose?
- Also curious about TouchWiz in terms of Android architecture, which I am still learning about. I was under the impression this is some kind of loader or launcher specific to Samsung. I did not realize it would inherently contain Wifi calling. Does this layer also provide for the face buttons of the S3? What is TouchWiz specifically - a layer that sits on top of base Android? Trying to understand how this layer fits into the grand scheme, and are there comparable layers created by other manufacturers?
In any case, I guess I'm not getting AOSP or CM anytime soon. The TouchWiz ROMs are less-known so I am less inclined to chance it. At the very least I could root and get rid of some of these apps.
Thanks!
STOCK = base Android build from that Device's Manufacturer. So there's only one per Android Release.
Yes you can revert back to T-Mo Version if you don't like custom Roms.
(Small verbiage correction. We call Flashing a Rom not "Loading" a rom. This is to distinguish from system firmware such as Bootloader and Recovery.)
Touchwiz is a framework, that's specific to Samsung. Read here for more on Touchwiz and rest of your questions. It doesn't contain Wi-Fi calling but T-mo's feature of Wi-Fi calling needs to have this framework on your phone to work. There are other T-mo features such as Caller Name ID that needs this framework as well. What do you mean by Face buttons ? Face recognition ?
I had a question to tack on to OP's question, since it seems relevant here.
Ive noticed through looking at the "bible" stickied post that there seem to be 3 major types of roms: CM-based roms (roms that took CM10 code for the GS3 and used it to achieve AOSP compatibility, then rolled their own features), Rootbox based roms (dont know what this is or what it does), and Stock based roms.
Right now, I wanted to try out a Stock rom, as from my understanding, a Stock rom is one in which the developer starts with a stock firmware image from samsung, does things such as root, deodex, zipalign, debloat, etc, and then releases. The advantage of the stock rom, from my understanding, is that it is incredibly stable (assuming no kernel tweaks and similar) compared to the bugs we may experience on roms that are CM based.
I'm experiencing issues with CM roms that are not deal breakers by any means, but definitely make me want to look for greener (less buggy) pastures.
Is there a more up-to date version of the stock rom list? Is there a good way to search for stock-based roms?
shrimants said:
I had a question to tack on to OP's question, since it seems relevant here.
Ive noticed through looking at the "bible" stickied post that there seem to be 3 major types of roms: CM-based roms (roms that took CM10 code for the GS3 and used it to achieve AOSP compatibility, then rolled their own features), Rootbox based roms (dont know what this is or what it does), and Stock based roms.
Right now, I wanted to try out a Stock rom, as from my understanding, a Stock rom is one in which the developer starts with a stock firmware image from samsung, does things such as root, deodex, zipalign, debloat, etc, and then releases. The advantage of the stock rom, from my understanding, is that it is incredibly stable (assuming no kernel tweaks and similar) compared to the bugs we may experience on roms that are CM based.
I'm experiencing issues with CM roms that are not deal breakers by any means, but definitely make me want to look for greener (less buggy) pastures.
Is there a more up-to date version of the stock rom list? Is there a good way to search for stock-based roms?
Click to expand...
Click to collapse
All of the stock Touchwiz based roms are in Android Development, so start there. A dead giveaway is if a build number is in the title. For example if you see UVDMD5, or just MD5 in the title, it is based on the latest official release. Anything older is buried by now. We do have a couple of 4.3 leaked builds. UVUEMJ4 and UVUEMJC. MJC is the newest. Anyway, there is almost always a clue in the title. But if you are not sure, just open and look over the OP and screenshots.
Ill try to PM the OP of the list to see if he plans on updating it. I would not expect him to until after our next official release though, which is right around the corner. TBH, aside from a few roms, it should be pretty well up to date.
No I meant the lower left and lower right buttons on the face of the phone, the ones that light up on either side of the Home button.
OK so a custom TouchWiz ROM then may or may not contain the T-Mobile feature of Wifi Calling, since it is again a layer on top of TouchWiz? Just trying to make sure, because that is the single feature I am worried about retaining.
Thanks for the help!
Perseus71 said:
What do you mean by Face buttons ? Face recognition ?
Click to expand...
Click to collapse
squiddog said:
No I meant the lower left and lower right buttons on the face of the phone, the ones that light up on either side of the Home button.
Click to expand...
Click to collapse
What is your specific question regarding those lighted buttons? Do you want to remap them to make them do something other than what is intended or do you simply want to know if they work as advertised.
squiddog said:
OK so a custom TouchWiz ROM then may or may not contain the T-Mobile feature of Wifi Calling, since it is again a layer on top of TouchWiz? Just trying to make sure, because that is the single feature I am worried about retaining.
Thanks for the help!
Click to expand...
Click to collapse
Think of TWiz along the same lines as your KF. The Kindle (and Nook for that matter) uses Android as its base. Then it is skinned with features that Amazon (or B&N) think that you would like, overlay their own launchers, custom applications, locked bootloader ... Touchwiz is the very same thing. It is Samsung's version of what you have on your KF. An Android base with manufacturer's preferential skin and extra "goodies". Sense (HTC) and the now defunct Blur (Motorola) are other examples of this.
If you want Wifi Calling, then you should have no problem with any of the Touchwiz ROMs that are out there. Please note that Wifi Calling is not and will never be working on any AOSP ROMs.
***************
What I suggest is that your Root your phone, install a custom recovery, make sure that you back up your IMEI if you plan on going to and fro TWiz and AOSP. Before you flash anything, boot into your custom recovery and make a Nandroid backup of your ROM as it is right here and now. Then copy* that off your phone and put a copy on your PC. I say copy because you will want to leave one on your phone and one on your PC as a last resort backup (I still have mine from the ICS days). Then flash a ROM. Check it out for a few days. Not your cup of tea? Flash another. If something goes horribly wrong or you don't like some of the features of X ROM, then just restore your Nandroid that you made and you are right back where you started.
Yes I just noticed that the S3 had these buttons and many other phones do not. Therefore there is probably a TouchWiz requirement to get these buttons to work as advertised. The question is sort of moot now anyway - as I want a TouchWiz ROM.
Woody said:
What is your specific question regarding those lighted buttons? Do you want to remap them to make them do something other than what is intended or do you simply want to know if they work as advertised.
Click to expand...
Click to collapse
squiddog said:
Yes I just noticed that the S3 had these buttons and many other phones do not. Therefore there is probably a TouchWiz requirement to get these buttons to work as advertised. The question is sort of moot now anyway - as I want a TouchWiz ROM.
Click to expand...
Click to collapse
Yes I am aware you have decided to stick with Touchwiz roms. Just so you know, these two buttons work just fine in AOSP as well. In fact, on AOSP you have an option of assigning additional actions to Long Pressing of these two.
Hi,
I am a custom rom fan and use them in most of my devices. But with my Note 8.0 I only use original Samsung based rom.
because I don't want to lose Samsung features like S-Pen etc.
What I wonder is, with a custom rom ;
- is the s-pen supported ?
- is there an alternative to Samsung AllshareCast support ? (in standards this is miracast support. Do the custom roms support miracast ?)
- What would I miss from Samsung features if I use custom rom ?
Thanks.
The s-pen works and is very functional on custom roms however you need to find the right software to go in tandem
S note is only compatible with touchwiz based roms and Imo is the best but actual pens functionality and sensitivity is as sensitive on any custom rom
Sent from my GT-N5110 using Tapatalk
thnaks for the fast reply.
So you mean S-Pen works but S-note (app) does not work. That's good news because I don't use S-note.
But for example, I can use Adobe Photoshop with S-Pen ?
What else I miss with custom rom ?
and what about screen mirroring ? (miracast)
mrmrmrmr said:
thnaks for the fast reply.
So you mean S-Pen works but S-note (app) does not work. That's good news because I don't use S-note.
But for example, I can use Adobe Photoshop with S-Pen ?
What else I miss with custom rom ?
Click to expand...
Click to collapse
You may of misunderstood what he replied. Just to clarify....if the custom rom is based on Touchwiz then SNote will work fine otherwise it in most cases won't.
If the custom rom is based on Touchwiz you should actually gain more functionality and not lose any. AOSP roms will vary on what is working and what is not.
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
mrmrmrmr said:
and what about screen mirroring ? (miracast)
Click to expand...
Click to collapse
If I am not mistaken I believe that is confirmed working on civato's latest rom.
A little clarity:
There are ROMs based on the official Samsung ROMs, and they generally support all of the same features as stock but without bloatware and with additional features. Civato's excellent ROMs are a great example; they perform better, have more features (particularly kernel-based), allow the user to select which bloatware to install, and generally are wonderful. Consider it stock ROM fixed up. I have used them for nearly a year and can recommend them highly. This means you get S-Note, and Allcast I believe at this point. There have also been other apps that have been ported from other Samsung devices to this ROM.
Other ROMs are based on AOSP (Android Open Source Project) and do not include the Samsung-specific software. No TouchWiz, S-Note, or any app that depends on the Samsung APIs in their stock ROM. The Photoshop app that is shipped for Samsung crashes immediately on my OmniROM and I had to uninstall - I guess that it is calling a Samsung API. So now, with Omni-ROM I will be dealing exclusively with the world of generic apps, which is not a problem. The stylus works out of the box. To have an app launch when the stylus is removed it is necessary to add a non-free app from the store. This will also enable other features of the pen. There are stylus-supporting note programs (e.g. Papyrus) which work just fine. Most apps using a stylus should work (e.g. Sketchbook) unless they were written using the Samsung APIs, in which case that should be obvious in the store as they will be Samsung-only apps. Edit: if you like to use the stylus for general text entry then you will need to get an app for that as well; they are available - but the neat way that the Samsung keyboard can switch to stylus input is lost.
I have no knowledge of the Allcast issue, other than noting that there are apps available. DLNA is certainly available through any number of apps for any ROM.
You will find a good source of ROM info on this thread: http://forum.xda-developers.com/showthread.php?t=2630650
mrmrmrmr said:
- is there an alternative to Samsung AllshareCast support ? (in standards this is miracast support. Do the custom roms support miracast ?)
Click to expand...
Click to collapse
Both AllshareCast (Miracast) and Chromecast screen casting work fine on the most recent @civato ROM's (FlexNote 3.0 and FlexBurst 1.0). This app and the official app are required for Chromecast screen casting.
ramjet73
Hi,
I would like to make some clarification to my question. By "custom rom" I meant "non-Touchwiz based" rom. Of course, Samsung/Touchwiz based roms do support everything related to Samsung APIs.
So my question is;
with a non-Samsung based rom, shall I be able to use S-Pen with 3rd party apps ? (like Adobe Photoshop - not the one distributed with Samsung devices but the commercial Store version)
Also does miracast work with them ? (not DLNA , real screen mirroring)
Thanks.
Yes you can use your stylus. Miracast depends on Rom kernel development. Due the fact that this is included in Stock Samsung Kernel Source maybe not working...
That is a problem of all Samsung devices, lack of Source code...
Ok. Allshare Cast is Samsung feature but AOSP based roms do have Miracast support , correct ?
mrmrmrmr said:
Hi,
I would like to make some clarification to my question. By "custom rom" I meant "non-Touchwiz based" rom. Of course, Samsung/Touchwiz based roms do support everything related to Samsung APIs.
Click to expand...
Click to collapse
That's not necessarily true.
Some custom ROM's based on Samsung stock break things that work on the official ROM by using a different kernel, modifying the framework or implementing alternate versions of Samsung components from other devices. You need to check the OP and read through the thread to determine if any stock features are broken or missing.
It is definitely harder to mimic all the features of the stock TouchWiz firmware on ROM's compiled from AOSP source. If you plan to use one of those ROM's you really need to verify that the features you use/need are available and can expect to add several third party apps to get anything close to stock sPen support.
Here's a similar thread from last October and this post should help with fleshing out Spen support for AOSP ROM's even though it was written for the Note 3.
mrmrmrmr said:
Ok. Allshare Cast is Samsung feature but AOSP based roms do have Miracast support , correct ?
Click to expand...
Click to collapse
Allshare Cast is just Samsung's name for Miracast but it is still certified by the WiFi Alliance so it should be compatible. From the Wikipedia article on Miracast:
On 29 October 2012, Google announced that Android version 4.2 (updated version of Jelly Bean) will support the Miracast wireless display standard, and by default will have integrated features for it.[8] As of January 8, 2013, the LG Nexus 4 and Sony's Xperia Z, ZL, T and V officially support the function,[9][10] as does HTC One, Motorola in their Droid Maxx & Ultra flagships, and Samsung in its Galaxy S III and Galaxy Note II under the moniker AllShare Cast. The Galaxy S4 uses Samsung Link for its implementation.[11] In October 2013, BlackBerry released its 10.2.1 update to the existing line of BlackBerry 10 devices, which brings Miracast and Wi-Fi Direct support to the Z30,Z10,Q10 and Q5 models.
Click to expand...
Click to collapse
Chromecast screen casting is different and obviously requires a Chromecast device. I have done both successfully on the stock ROM and the latest versions from @civato but don't expect either to work on AOSP based ROM's at this point. They do work with the M10 snapshot for CM11 on my Nexus 4 but the Note 8.0 is not a Nexus device and I think those functions are highly dependent on the kernel used.
If you want all the features of the Note 8.0 working then you should stay with something close to the stock ROM. It will take a lot of time, effort and some money for apps just to get away from TouchWiz interface.
ramjet73
paying for 3rd party apps is not an issue if there are apps supporting S-pen.
I would stick with Samsung ROM if I believed Samsung will support this device anymore. But I doubt Samsung will release Android L to it.
So , I should turn to non-Touchwiz rom at some point. (I like the idea of 8 inch note device, and Samsung doesn't release a 2014 edition replacement)
2 things important for me on the Note device:
- S-Pen usability with 3rd party apps (I understand that non-Samsung roms support S-Pen)
- Screen mirroring (miracast should work if the rom is based on AOSP)
Any advice for a good non-Touchwiz rom ?
mrmrmrmr said:
- Screen mirroring (miracast should work if the rom is based on AOSP)
Any advice for a good non-Touchwiz rom ?
Click to expand...
Click to collapse
"Should" and "does" are two different things.
Out of curiosity, I loaded the M10 snapshot (the latest) for CM11, just to see if it supports screen casting for Miracast and/or Chromecast. The answer is "no" and it doesn't even appear in the display options for settings even though the M10 release for my Nexus 4 works fine with both.
The moral of the story is don't expect much better support in the future from the AOSP ROM makers. CyanogenMod will probably release an L (CM12) version since the N51xx is an officially supported device but don't expect it to support all the features of the Note 8.0 that the stock ROM does.
For a ROM recommendation, I'm planning to stay with the enhanced stock versions from @civato.
ramjet73
I appreciate your confusion on the stylus support, so let's talk about that. First off, the stylus is not unique to Samsung. Most if not all ROMs will provide the status of the raw stylus data (location, pressure, button, storage slot) to applications. Programs written to access the stylus at this level should work on any device that has the (Wacom?) stylus, Samsung or not. The PS Touch in the store should work fine on AOSP - the one I tested last night was a freebie tied to the Samsung ROM and didn't work on Omni-ROM (no surprise there). The fly in the ointment is that Samsung includes a library of stylus functions in their ROM which makes it easier to develop apps for use with a stylus, and which will lock the apps to Samsung devices (the APIs are Samsung-specific). Any app using those APIs will not work on AOSP ROMs. It is easy to tell the difference in the Store because those apps will be for Samsung-only; if it works on non-Samsung devices it is a good bet it will work with open ROMs.
In addition to the stylus software library, Samsung includes software to do things when the stylus is removed from storage or touches hot-spots, a keyboard option to use the stylus and handwriting recognition to create text input in any program, and stylus-enabled programs like S-note that can also convert your scribblings to text with varying levels of success - YMMV. These functions can all be added back into AOSP ROMs with programs from the store, at a modest price. Of course they will be a little different but the functionality will be there.
My recommendation would be to go with Civato's latest ROM (FlexBurst) for now, assuming you are using your stylus a lot and enjoy the Samsung implementation. Civato has added into the ROM support for aircommand, which is available on other Samsung devices but not stock for the Note 8. Also, there are newer versions of S-note available. Samsung (and thus FlexBurst) is currently at 4.4.2, while Omni-ROM is at 4.4.4; I don't see the small lag as anything important at this stage. Once Samsung stops supporting it there will be time to convert to AOSP. In any event once your Note is rooted and TWRP Recovery installed it is a simple matter to make a Nandroid and Titanium backup before installing a new ROM to try out; if you don't like it then wipe and reinstall - not a big deal. The only downside is that you will break your warranty if you have a KitKat bootloader (required for Civato's latest as well as Samsung's latest).
Hope this helps,
Greg
Hello everyone,
I recently bought a Tab S 8.4 and I do have it rooted along with a custom recovery but I'm still running the stock Lollipop Samsung ROM with Touchwiz. Here is my question: If I were to flash a non-Samsung ROM like IronROM or CM12 or anything based on AOSP, what are the Samsung features I would be losing?
Here's what I can tell so far:
Fingerprint Reader
Multi-Window
Touchwiz Overlay
Hancom Office Software
S-Voice? Unsure
Peel Smart Remote? Unsure
Toolbox
Quick Connect
Will I lose Power Saving and Ultra Saving Modes? Unsure
Guest mode/Private mode
Knox? Unsure what this does
Thank you.
Bumping this in case anyone has any insight they could share with me, thank you.
IronROM is a Touchwiz 5.0.2 ROM, not AOSP. Since you have custom recovery isntalled, you should try flashing AOSP ROMs to experience the difference yourself. Perhaps you'll become a flashaholic like many of us :victory: . A Marshmallow ROM is available. I tried several TW and AOSP ROMs on various devices, and I decided I prefer TW.
HKSpeed said:
IronROM is a Touchwiz 5.0.2 ROM, not AOSP. Since you have custom recovery isntalled, you should try flashing AOSP ROMs to experience the difference yourself. Perhaps you'll become a flashaholic like many of us :victory: . A Marshmallow ROM is available. I tried several TW and AOSP ROMs on various devices, and I decided I prefer TW.
Click to expand...
Click to collapse
Unfortunately, I now consider myself to be a reformed flashaholic I was hoping to avoid flashing several ROMs since it's a time-consuming process.
I did read up on some ROMs and might move over to IronROM since it keeps some of the Samsung features that might be useful. I'll end up deleting/freezing others that I don't want I suppose.
Thanks.
Personally, the only thing that keep me from using an AOSP Rom is Split Window, something that I use a lot.
You should consider if there is some TouchWiz feature that you can't live without, I consider most of it crapware.
Dont forget to run the Wanam LP Xposed module. It adds some customizations to TW.
Thanks all. I think multi-window and fingerprint reader are enough to keep me on the TouchWiz. I'll switch to IronRom and with Xposed that should do the trick, especially if I disable a lot of other Samsung bloat. Thanks again!
One major factor to me is that aosp does not support exfat. In this day and age and the size of media files that's a killer.
Also let's put something straight. TW like any other gui such as sense is just an enhanced interface.
It does provide many useful features. Samsungs problem is its insistence on bogging it down with unnecessary bloat, also knox should be optional.
TW can be just as efficient as aosp or cm.
On the tab A they included very little bloat and it runs very well.
The tab S has quite powerful hardware and should fly, which it does when all the chaff is removed.
ashyx said:
One major factor to me is that aosp does not support exfat. In this day and age and the size of media files that's a killer.
Also let's put something straight. TW like any other gui such as sense is just an enhanced interface.
It does provide many useful features. Samsungs problem is its insistence on bogging it down with unnecessary bloat, also knox should be optional.
TW can be just as efficient as aosp or cm.
On the tab A they included very little bloat and it runs very well.
The tab S has quite powerful hardware and should fly, which it does when all the chaff is removed.
Click to expand...
Click to collapse
Oh I had no idea about the lack of exfat support! That settles it then, I'm sticking with TW for sure and will switch to IronROM since it adds a few things and also enables the use of Xposed due to being deodexed etc. I can definitely disable the other bloat I don't need, in fact I have done that already on my current stock 5.0.2 ROM as well.
I am a serial Nexus user and the last 10 or so of my devices have all been Nexus, so TouchWiz is taking some getting used to. It does add some useful features and it's easy enough to get rid of what you don't want/need.
Thanks again everyone, much appreciated.
the7thson said:
Thanks all. I think multi-window and fingerprint reader are enough to keep me on the TouchWiz. I'll switch to IronRom and with Xposed that should do the trick, especially if I disable a lot of other Samsung bloat. Thanks again!
Click to expand...
Click to collapse
Cm13 does suport fingerprint sensor and multi Window (not 4 Windows, or mini Windows) but fingerprint isnt working right now.
Peel does work with aosp.
S voice is crap and Google search (even cortana beta) is far better.
Toolbox can be used by using an app called Toolbox (play store it, there are 5 i think)
So, you will only lose (and miss) ultra power saving Mode, because cm13 (even xposed modules have) has Its own saving Mode called doze
Knox is a security Mode to protect your info. (i never use it)
Guest/private Mode, are cm since cm12 and of course on cm 13 too
Soundcamp, the music workstation from Samsung, does not work on AOSP but is OK on IronRom.
BraianV said:
Cm13 does suport fingerprint sensor and multi Window (not 4 Windows, or mini Windows) but fingerprint isnt working right now.
Peel does work with aosp.
S voice is crap and Google search (even cortana beta) is far better.
Toolbox can be used by using an app called Toolbox (play store it, there are 5 i think)
So, you will only lose (and miss) ultra power saving Mode, because cm13 (even xposed modules have) has Its own saving Mode called doze
Knox is a security Mode to protect your info. (i never use it)
Guest/private Mode, are cm since cm12 and of course on cm 13 too
Click to expand...
Click to collapse
Finger print will never work for this device on an AOSP ROM. The sensor is a proprietary Samsung device, they will not release the source code for it. Regardless of the native support for fingerprint sensors in MM, it is impossible to build support for the Samsung sensors into an AOSP ROM without the source code.
Because English is not good, the followingis the machine translation.
I come from china. My equipment is Lemon3, that is, k32c36. You can use VIBE k5 plus rom.
XDA is a very good community, where the best resources and developers. This forum third party rom I have installed, are very smooth, thanks so many developers to provide so many rom! I like these roms, until now, the bug has been very little, but still there. My current area is promoting VOLTE, and my k32c36 itself is to support VOLTE, XDA forum these roms seem to support VOLTE is not very good, there is a feature is to open the VOLTE after opening the mobile data connection VOLTE will be disconnected , Until you re-switch it, there is the proposed in the status bar to add VOLTE icon, because there is no icon we can not see whether it is working. I do not know if this is a bug, or is it a different problem for the operator. Theme sent here, want to get answers, thank you!
As for now no 7.1 roms support volte properly. All 7.1 roms have toggle issue. Better use stock rom or miui lollipop rom for stable volte.
MIUI is bloated, but it does support VOLTEbetter. Really good looking forward to these 7.1 ROM can solve this problem as soon as possible.
Am sorry to say but this problem can't be solved. Until we Indian get a stock mm update with volte but thanks to lenovo they won't give us the updated ?
Okay, I'm reverting back to my G3 after using Android N on my Nexus 6 for the past half-a-year, so I'm debating between Fulmics or something Nougat-flavored (RR, Lineage, crDroid, AICP, maybe Beanstalk?)
My priorities look like:
Ability to pass SafetyNet
Ability to enable tethering
High quality Camera (maybe built from G3 Stock?)
Stable
Well supported / vetted
Runs smooth
Can handle Pokemon GO well
Good battery life
Useful multitasking (like Android N's multi-screen & switching controls)
Ability to reply from notifications menu
Smooth, streamlined quick-setting toggles (esp. for tethering, wifi, and flashlight)
Other bells and whistles are fun (Now On Tap, etc.) but not super necessary
The reason I'm leaning towards Fulmics, in spite of it's Marshmallow flavor, is I remember the stock G3 Camera being something exclusive to stock-based ROMs... and from what I gather, that would mean anything built from Nougat would *not* have access to that Camera, right? Do other ROMs still have good Cameras? I remember the G3 being quite finicky in that regard...
That said, I really like some of the Nougat additions I've gotten used to. Notably, I like being able to reply to messages straight from the notifications menu, I like the streamlined style of the toggles, and while I believe Fulmics can do this I like the double-tap-to-switch-apps feature and multi-window feature of the task switcher
I also will need whatever I go with to pass SafetyNet – which it seems any of the ones I listed can so long as I configured Magisk right?