Database Info

N 8000 ICS mobile network turning off automatically when screen off

Hi there. I just bought an N8000 and whenever I turn off screen the mobile network turns off and shows a circle with a slash in the middle. The device is on ICS 4.0.4. Whenever the screen is turned off no incoming calls can be received. Its product code is GT-N8000ZWAAFR. I have done 5 or 6 factory resets but the result is the same. Also, no incoming calls can be received when screen is off. If I am in the middle of a call and the screen shuts off, the line gets disconnected. I have also tested with two other SIM cards from different providers (all of whom have great reception in my area) but the same result.
I have checked the device update on my note 10.1 but still no updates either from OTA or Kies. I have scoured the internet and xda forums for similar problems to no avail. I checked out samir_a's guide to reinstall to a different region stock rom (I'm thinking Germany) but I'm confused whether I'll be able to receive OTA updates (some posts say I won't) as it will no longer match my region code, and I don't plan on manually flashing ever again.
Please please please help.

same problem
kreml0n said:
Hi there. I just bought an N8000 and whenever I turn off screen the mobile network turns off and shows a circle with a slash in the middle. The device is on ICS 4.0.4. Whenever the screen is turned off no incoming calls can be received. Its product code is GT-N8000ZWAAFR. I have done 5 or 6 factory resets but the result is the same. Also, no incoming calls can be received when screen is off. If I am in the middle of a call and the screen shuts off, the line gets disconnected. I have also tested with two other SIM cards from different providers (all of whom have great reception in my area) but the same result.
I have checked the device update on my note 10.1 but still no updates either from OTA or Kies. I have scoured the internet and xda forums for similar problems to no avail. I checked out samir_a's guide to reinstall to a different region stock rom (I'm thinking Germany) but I'm confused whether I'll be able to receive OTA updates (some posts say I won't) as it will no longer match my region code, and I don't plan on manually flashing ever again.
Please please please help.
Click to expand...
Click to collapse
same problem , when I downgrade from 4.1.2 to 4.0.4 the only solution that i have found is to update to jelly bean it will resolve this problem

hossam sokkary said:
same problem , when I downgrade from 4.1.2 to 4.0.4 the only solution that i have found is to update to jelly bean it will resolve this problem
Click to expand...
Click to collapse
Thanks for the reply.
Well I had warranty so didn't want to mess with it further. I took it back to the store and they gave me a new one. They however found the problem to be quite weird.
Also the previous one had a AFR CSC code, which I checked on sammobile to be still stuck on ICS 4.0.4 .. The replacement I got also had ICS 4.0.4 on it with CSC code COA (which is Romania ). I checked OTA after getting home but showed no updates (I selected Romania as my country when it asked for my location). On connecting it to Kies it found an update. I let it finish it's job and voila JB 4.1.2. \
I couldn't be happier.:laugh:

[Q][issue][P3100][no phone audio] Any way to change region or baseband in a ROM?

# Thanks first to ketut.kumajaya. This is not intended as a complaint against him or his amazing contributions, but need to find a solution and I hope this could also help others in the same situation.
I have a P3100 using ketut.kumajaya's Samsung-based ROM. He states states that it is based on P3100ZSDMD1, region BRI rebranded as XSE - whatever "rebranding" means.
Anyway, with this ROM initially I got zero phone audio in either direction - I couldn't hear anything once the call connected and the other party couldn't hear me. I noticed that this setup defaults to a different set of APNs - somehow I wind up with Fido's (my carrier) LTE APNs. I changed these manually to the original APNs that worked in another ROM - comprising fido-core-appl1.apn and internet.fido.ca - and I could finally hear the call, but the other party still can't hear me and to date this is where I am stuck.
I think my no-audio problem has something to do with the baseband radio or region used. One giveaway sign is that this ROM downloads a different set of APNs (LTE ones!) from my mobile carrier than CM does. I don't know anything about "rebranding" referred-to in the OP of ketut's thread, but maybe this broke something? CM10.1, which uses P3100XXLE3, works fine. Is there any way to change the region and/or baseband, either through a prop. setting, script or manually swapping baseband files from another ROM from http://samsung-updates.com/device/?id=GT-P3100?
If anyone knows how I can fix this while retaining ketut's awesome ROM, I would greatly appreciate it. Since the P3100 was never marketed by any carrier in Canada, there is no phone radio specifically for Fido/Rogers' networks in Canada, therefore the only recourse seems to be to use one from a different region that is "most compatible."
Any help would be greatly appreciated. I give "thanks" generously.

Couldn't find Mobile Network Type

Hello, Recently I have bought an Unlocked At&T LG G3 The seller told me that the phone has a bad IMEI But it's unlocked to be used interntionally. When I received it, It's working fine, except the data network speed trough EDGE is too slow. As yo can see on the screenshot below I couldn't find the option to change the network type. and I'm stuck at "E" which mean EDGE.
http://s14.postimg.org/8r7vs0x27/Quick_Memo_2015_09_09_11_41_43_1.png
The phone's model is LG-D850 and it's running android 4.4.2 KitKat. it has no IMEI when I dial *#06# it shows IMEI: 0-05 on Settings/about phone/Status... it says IMEI: 0

Anyone here to help?

First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them

youngunix said:
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
Click to expand...
Click to collapse
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?

AminhoVic said:
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
Click to expand...
Click to collapse
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.

youngunix said:
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
Click to expand...
Click to collapse
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?

AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
Click to expand...
Click to collapse
I get the same error if I use a third party dialer app (i.e., Dialer) until I tried the stock phone app.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
I haven't flashed any custom ROMs on my LG, but from experience, each device somehow reacts differently to custom ROMs. For instance, I've flashed my S.G. Note (i717) over 30 times and some ROMs were stable at first then started having issues with them.
The best advice I can give you, is to pick a ROM from the list you posted and check the comments to see if it is stable or too many users have issues with it.

AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
Ever think that it does not have the correct bands for your carrier?

Service Mode Not Supported- AQG5 UK Update Galaxy S8+ G955F

I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code •#0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?

bump

bump, come on people someone must have some info

have you tried *#2263# ??

It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect

esjames said:
have you tried *#2263# ??
Click to expand...
Click to collapse
that is for the snapdragon version, i have the international exynos version and the *#2683662# code used to work but after the update it now says unsupported

bluheart said:
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
Click to expand...
Click to collapse
possibly yes, im not sure which soc the indian version has whether its snapdragon or exynos but if its exynos then seems samsung have disbaled it after a recent update for whatever reason

After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.

Bryan48765 said:
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Click to expand...
Click to collapse
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
With regards to the CSC's, i can only comment on the XEU CSC which is part of the OXM multi csc and the one my phone is on and on that it says not supported for the code.
I haven't checked on root, don't really want to root my device

hamzahshakeel said:
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
Click to expand...
Click to collapse
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?

Bryan48765 said:
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Click to expand...
Click to collapse
i tried the logcat using the filters you provided (i.e. RILS, RILD etc) and yes it does bring back logs relating to those services however its not enough, all it outlines is when i type the code and monitor the logs subsequnt to the typing of the code the log just shows it trying to open the process associated with the menu, it doesnt show what it tries to do in between me sending the code and the response coming back so comparing that with a working code log will bring back nothing of note
however having said that i did try the full system wide log which was a bit teidous given it logs everything so going through it and pinpointing the relevant piece of log was a bit hard, i will attempt to log again using my s8+ and another samsung phone for which the same code works on and then post it here

try install phone info . this programm has all codes inside

Guys, the same in brazil. Since the begining of the year I've tried to activate 256QAM+MIMO 4x4 in my sumsung galaxy s8 using *#2683662# and by now it doen't work as return the message "not supported". Do you guys has reached some progress on it?

Seems they changed something inside the CP (modem.bin) and disabled the code. Flashing back the AQF7 - CP file will get back the code, but don't know the effect.

Yes I also noticed this a couple months back and made my own thread on it. So far there has been no progress except to flash a previous older update

Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.

no_name_no said:
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
Click to expand...
Click to collapse
Ive tried this but not work
Enviado desde mi SM-G935F mediante Tapatalk

hamzahshakeel said:
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code #0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
Click to expand...
Click to collapse
Unfortunately starting with Android v8.x.x (Oreo), test codes sent to the RilServiceModeApp via android_secret_code://<code> even by root are being denied.
If the test menu *#2263# or *#2683662# or *#2766338378# doesn't work with your current sim card, then try the following.
Find a couple of other active or inactive sim cards (can be another local carrier or from abroad), let the phone reboot and reconfigure its CSC while on the blue bootup screen, then try the code again, since test codes are CSC specific. It's a hit and miss affair, so be persistent.
If your phone is rooted, you can try these methods one at a time.
After each step, reboot the phone and try the test codes *#2263# or *#2683662# or *#2766338378#.
1. Using Shortcut Master (free version) from the PlayStore, tap on the menu, Secret Code Explorer, scroll down to 2263 or 2683662 or 2766338378 (or Menu > Search for "band"), tap on Launch0.
2. On combination firmware edit the file /efs/carrier/HiddenMenu and /efs/FactoryApp/keystr to be "ON", which will persists even after flashing back to stock firmware.
3. Copy the <CSC>_keystrings.dat from system/etc to root/etc and set permissions to 0744.
4. Try replacing the /system/priv-app/ModemServiceMode/ModemServiceMode.apk=com.sec.android.RilServiceModeApp from a previous Android version which had the codes working, and set the permissions to 0744.
5. Flash an earlier radio (CP) which had the codes working, if the current bootloader allows it to be downgraded.
This last method works on all Samsung models/firmwares without root, but requires a special test cable, which is only available for micro-USB ports at this time.
If you can find a similar cable with a USB-C connector, then it should work just fine. By the way, using an micro to C adapter does not work.
The following is only for phones with a micro-USB port, nonetheless it makes an interesting way to enable the hidden test menus.
You can actually enable most test codes (including RIL test codes which fail to execute on Oreo of newer even while rooted, such as *#2263# band change, *#2683662 lab test mode, and *#2766338378# engineering test menu, etc) on pretty much any model/firmware/region by simply plugging in a test cable into the phone (the other end doesn't have to be plugged in anywhere, it's just the built in resistor which enables test mode/FactoryMode).
It's important to follow the next steps exactly in this order: Open the dialer, exit the dialer with the Back key (not the Home button!), reopen the dialer and now it should accept most test codes.
These cheap test cables can be found on Ebay or AliExpress, just search for "Samsung 523K uart cable" or "Samsung 619K uart cable". Some come as a combo where you can simply switch the resistor values via a switch, but you must try both values, since only one or the other will work on certain models/firmwares/regions.
I've been using this method successfully for many years (currently on my Samsung S7 with the latest 2019 firmware), unfortunately these test cables are only available for micro-USB connectors, so it won't work on the newer USB-C phones even with an adapter (because it doesn't extend the resistor lines, only the data lines). If anyone finds a solution for USB-C, please post a message here.

Galaxy S7 Oreo update problems so far

So, I updated my S7 G930F to Oreo with the official UK BTU firmware, flashed with Odin CSC (Not CSC_Home), and after it booted i went into recovery and wiped. So far I've been having a couple of issues with the update. Stuff like:
-WiFi issues. A ! icon appears next to the WiFi icon every few minutes and I don't get internet again until i wait a few minutes or turn the WiFi off and on.
-Noticeably worse battery life than in Nougat, it's quite a bit worse, I wouldn't call it battery drain but it's lasting at least 30 minutes/1 hour of onscreen time less.
-Graphical glitches. In games there's some weird artifacts that are just annoying, i understand this isn't a big deal and will probably be fixed but I just wanted to point it out.
Performance has been ok, about the same as Nougat or a bit better.
That's been my experience with the update so far, i'd like to know your experiences or if anyone has had any similar issues because the WiFi problem really is being a deal breaker for me.

Galileo said:
So, I updated my S7 G930F to Oreo with the official UK BTU firmware, flashed with Odin CSC (Not CSC_Home), and after it booted i went into recovery and wiped. So far I've been having a couple of issues with the update. Stuff like:
-WiFi issues. A ! icon appears next to the WiFi icon every few minutes and I don't get internet again until i wait a few minutes or turn the WiFi off and on.
-Noticeably worse battery life than in Nougat, it's quite a bit worse, I wouldn't call it battery drain but it's lasting at least 30 minutes/1 hour of onscreen time less.
-Graphical glitches. In games there's some weird artifacts that are just annoying, i understand this isn't a big deal and will probably be fixed but I just wanted to point it out.
Performance has been ok, about the same as Nougat or a bit better.
That's been my experience with the update so far, i'd like to know your experiences or if anyone has had any similar issues because the WiFi problem really is being a deal breaker for me.
Click to expand...
Click to collapse
WiFi: Check you don't have WiFi > Advanced > Switch to mobile data enabled, or it will try switching to data whenever it thinks the wifi signal is lower than it wants, this option has never worked well even since my S5 days
This is not a BTU 8.0 firmware issue as I do not suffer from it and have the exact same phone and firmware
Check your router too, maybe reset that, or at least power cycle it, check DHCP lease and remove the phones entry, allow the router to assign it another IP, or set in the router a static IP for the phone based on MAC address to ensure it is not handing out an IP assigned to another device causing a conflict and losing your phones WiFi connection
Battery Life: I am experiencing way better battery life, possibly due to factory resetting and not having a huge amount of apps installed, but I have gone from sometimes not even 4 hours SoT to easily over 6 hours, I did use a Package Disabler to disable a lot of bloatware / system apps that used to cause battery drain on Nougat (no root needed)
Graphical glitches: I don't really game on my phone, but the few I have tried have run fine, PUBG and a couple of casino slot games, but I have heard others complaining of graphical glitches gaming under Oreo, I would assume the games need updating for the new OS version, or the OS needs some tweaking, either way like you say no doubt that will be fixed in the coming weeks / months

I'm having Bluetooth issues when connected to my ford radio, the phone and radio says it's connected but it is not coming through the cars speakers or the phone speaker (not all the time but often) and I have to press the Bluetooth button on the phone during a call and then the loudspeaker button to hear the caller.
Also if I use the Samsung audio switch thing from the notification bar and use phone audio which I like to use for TomTom or other navigation, then none of my calls are also routed through Bluetooth, on Nougat it all worked great, phone speaker for navigation and car speakers for calls, it's really annoying that it's not working.
Everything else is great, performance is really snappy, battery life is amazing on mine which is almost 2 years old.
Sent from my SM-G930F using Tapatalk

Hi.
I have a galaxy S7 international (dual SIM). I'm having issues with calls. People try calling me and they can't reach me. Or sometimes I can't make calls. ( As soon as I dial the number, it hangs up ) I'm wondering if it has to do with CSC . Any suggestions?

*Detection* said:
WiFi: Check you don't have WiFi > Advanced > Switch to mobile data enabled, or it will try switching to data whenever it thinks the wifi signal is lower than it wants, this option has never worked well even since my S5 days
This is not a BTU 8.0 firmware issue as I do not suffer from it and have the exact same phone and firmware
Check your router too, maybe reset that, or at least power cycle it, check DHCP lease and remove the phones entry, allow the router to assign it another IP, or set in the router a static IP for the phone based on MAC address to ensure it is not handing out an IP assigned to another device causing a conflict and losing your phones WiFi connection
Battery Life: I am experiencing way better battery life, possibly due to factory resetting and not having a huge amount of apps installed, but I have gone from sometimes not even 4 hours SoT to easily over 6 hours, I did use a Package Disabler to disable a lot of bloatware / system apps that used to cause battery drain on Nougat (no root needed)
Graphical glitches: I don't really game on my phone, but the few I have tried have run fine, PUBG and a couple of casino slot games, but I have heard others complaining of graphical glitches gaming under Oreo, I would assume the games need updating for the new OS version, or the OS needs some tweaking, either way like you say no doubt that will be fixed in the coming weeks / months
Click to expand...
Click to collapse
Which bloatware/system apps did you disable?
Would be good to make a list to help others to increase battery life.

baboo17 said:
Which bloatware/system apps did you disable?
Would be good to make a list to help others to increase battery life.
Click to expand...
Click to collapse
There's lists all over the S7 forums, pretty sure there is even a dedicated thread or two too
My list:
Save as disabledpackages.xml and import into package disabler pro
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.monotype.android.font.rosemary</string>
<string>com.skype.raider</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.google.android.googlequicksearchbox</string>
<string>com.oculus.systemdriver</string>
<string>com.samsung.android.app.withtv</string>
<string>com.samsung.android.hmt.vrshell</string>
<string>com.sec.android.app.safetyassurance</string>
<string>com.samsung.android.hmt.vrsystem</string>
<string>com.oculus.browser</string>
<string>com.samsung.android.app.vrsetupwizard</string>
<string>com.sec.android.easyMover.Agent</string>
<string>com.wsomacp</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.intelligenceservice2</string>
<string>com.microsoft.office.excel</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.dsi.ant.service.socket</string>
<string>com.microsoft.skydrive</string>
<string>com.oculus.vrshell</string>
<string>com.sec.kidsplat.phone</string>
<string>de.axelspringer.yana.zeropage</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.drivelink.stub</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.android.egg</string>
<string>com.android.mms</string>
<string>com.android.nfc</string>
<string>com.oculus.horizon</string>
<string>com.microsoft.office.onenote</string>
<string>com.google.android.gm</string>
<string>com.samsunguk.mygalaxy</string>
<string>com.android.calendar</string>
<string>com.samsung.fresco.logging</string>
<string>com.android.sharedstoragebackup</string>
<string>com.facebook.services</string>
<string>com.android.printspooler</string>
<string>com.samsung.android.hmt.vrsvc</string>
<string>com.samsung.storyservice</string>
<string>com.android.dreams.basic</string>
<string>com.sec.app.samsungprintservice</string>
<string>com.sec.android.omc</string>
<string>com.samsung.knox.securefolder</string>
<string>com.samsung.android.game.gametools</string>
<string>bluepin_app.cont.lego</string>
<string>com.google.android.apps.docs</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.microsoft.office.word</string>
<string>com.sec.android.inputmethod</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.microsoft.office.powerpoint</string>
<string>com.sec.enterprise.knox.myknoxsetupwizard</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.app.vrsetupwizardstub</string>
<string>com.android.chrome</string>
<string>com.samsung.android.sm</string>
<string>com.sec.kidsplat.kidsgallery</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.google.android.videos</string>
<string>com.dsi.ant.server</string>
<string>com.sec.android.app.myfiles</string>
<string>com.google.android.feedback</string>
<string>com.sec.kidsplat.camera</string>
<string>com.google.android.apps.photos</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.oculus.home</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.facebook.system</string>
<string>com.samsung.android.oneconnect</string>
<string>com.oculus.systemactivities</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.google.android.backuptransport</string>
<string>com.sec.android.app.kidsapps</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.android.spay</string>
<string>com.sec.android.emergencylauncher</string>
<string>com.sec.android.easyMover</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.enhance.gameservice</string>
<string>com.google.android.talk</string>
<string>com.oculus.mediaplayer</string>
<string>com.sec.svoice.lang.de_DE</string>
<string>com.sec.svoice.lang.en_US</string>
<string>com.sec.svoice.lang.es_ES</string>
<string>com.sec.svoice.lang.fr_FR</string>
<string>com.sec.svoice.lang.it_IT</string>
<string>com.sec.svoice.lang.ru_RU</string>
<string>com.samsung.android.app.appsedge</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.knox.switcher</string>
<string>com.sec.kidsplat.media.videoplayer</string>
<string>com.sec.android.widgetapp.webmanual</string>
<string>com.oculus.vrshell.home</string>
<string>com.samsung.android.coreapps</string>
<string>com.samsung.android.app.vr.input.service</string>
</disabledPackages>
</importExportSetting>

No real problems so far!

After flashing oreo with oxa csc, caller id has disappeared, So by receiving a spam call I do not see smart call.

joker950 said:
After flashing oreo with oxa csc, caller id has disappeared, So by receiving a spam call I do not see smart call.
Click to expand...
Click to collapse
Phone app > top right 3 dots menu > settings > Caller ID and Spam protection

*Detection* said:
Phone app > top right 3 dots menu > settings > Caller ID and Spam protection
Click to expand...
Click to collapse
I just said that the option has disappeared ...
In the call settings menu there is no longer the option to activate / deactivate caller id.
I think it's a problem of aligning the csc, i flashed oxa csc

joker950 said:
I just said that the option has disappeared ...
In the call settings menu there is no longer the option to activate / deactivate caller id.
I think it's a problem of aligning the csc, i flashed oxa csc
Click to expand...
Click to collapse
No you didn't, you said CallerID was missing, not that the menu itself was gone, some settings have moved from settings into the individual app settings in Oreo such as message notification sounds etc
I'm running the exact same firmware and CallerID is still there

*Detection* said:
No you didn't, you said CallerID was missing, not that the menu itself was gone, some settings have moved from settings into the individual app settings in Oreo such as message notification sounds etc
I'm running the exact same firmware and CallerID is still there
Click to expand...
Click to collapse
Sorry bro, I was not too precise.
However, I put the screen so you can see what options appear to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

joker950 said:
Sorry bro, I was not too precise.
However, I put the screen so you can see what options appear to me.
View attachment 4502490
View attachment 4502489
Click to expand...
Click to collapse
It should be under Ringtones & Keypad tones
Not sure then, my CSC is XEU running this firmware

*Detection* said:
It should be under Ringtones & Keypad tones
Not sure then, my CSC is XEU running this firmware
Click to expand...
Click to collapse
Exactly, I think the problem is precisely the CSC...
I think my problem is that when I flashed BTU firmware I left my sim card inside the phone, so on reboot the CSC was not aligned correctly.
There is a way to change CSC without wipe?

joker950 said:
Exactly, I think the problem is precisely the CSC...
I think my problem is that when I flashed BTU firmware I left my sim card inside the phone, so on reboot the CSC was not aligned correctly.
There is a way to change CSC without wipe?
Click to expand...
Click to collapse
What do you mean "Aligned properly"?
You don't need to remove your SIM when changing CSCs, I didn't, but XEU is included in BTU which is Multi-CSC, so it defaults to flashing XEU because that's my phones original CSC
CSC controls certain calling features such as VoLTE, and when you get OTA updates, I have no clue if BTU supports that feature but I don't see why not if XEU does (also UK firmware), maybe build.prop can enable it, but you would need root
Other than that, install TrueCaller to get a similar feature working
https://play.google.com/store/apps/details?id=com.truecaller
No way to change CSC without wiping unless that CSC is included in your current CSC but can't remember the process, trying to change between CSCs when they are both included in the same Multi-CSC proved impossible for me, trying to get BTU CSC from XEU, apparently flashing a different region not in your CSC first works but didn't have any success

*Detection* said:
What do you mean "Aligned properly"?
You don't need to remove your SIM when changing CSCs, I didn't, but XEU is included in BTU which is Multi-CSC, so it defaults to flashing XEU because that's my phones original CSC
CSC controls certain calling features such as VoLTE, and when you get OTA updates, I have no clue if BTU supports that feature but I don't see why not if XEU does (also UK firmware), maybe build.prop can enable it, but you would need root
Other than that, install TrueCaller to get a similar feature working
https://play.google.com/store/apps/details?id=com.truecaller
No way to change CSC without wiping unless that CSC is included in your current CSC but can't remember the process, trying to change between CSCs when they are both included in the same Multi-CSC proved impossible for me, trying to get BTU CSC from XEU, apparently flashing a different region not in your CSC first works but didn't have any success
Click to expand...
Click to collapse
Then I can not understand what the problem may be...
I had read somewhere here on the forum that leaving the sim card inside the phone on the first reboot after flash would align the CSC with the sim region, at least that's what I read...
If OXA CSC is Multi-CSC it should maintain the previous csc, so for me my previous CSC was PHN, but now as you can see in the screen i posted my csc is OXA. There is a way I can see which csc I really have?

joker950 said:
Then I can not understand what the problem may be...
I had read somewhere here on the forum that leaving the sim card inside the phone on the first reboot after flash would align the CSC with the sim region, at least that's what I read...
If OXA CSC is Multi-CSC it should maintain the previous csc, so for me my previous CSC was PHN, but now as you can see in the screen i posted my csc is OXA. There is a way I can see which csc I really have?
Click to expand...
Click to collapse
It will only retain your original CSC if it is included in that Multi-CSC, grab Samsung Phone INFO from the play store to check which CSCs it contains
Mine says: BTU, CPW, DBT, ITV, KOR, NEE, XEF, XEO, XEU
Never tested the SIM card theory, would be handy if that worked but I've never seen it mentioned anywhere else, always that you must flash a single CSC from a region not included in the firmware you want to flash CSC, then you can flash that multi-CSC and get BTU or whatever you're wanting

*Detection* said:
It will only retain your original CSC if it is included in that Multi-CSC, grab Samsung Phone INFO from the play store to check which CSCs it contains
Mine says: BTU, CPW, DBT, ITV, KOR, NEE, XEF, XEO, XEU
Never tested the SIM card theory, would be handy if that worked but I've never seen it mentioned anywhere else, always that you must flash a single CSC from a region not included in the firmware you want to flash CSC, then you can flash that multi-CSC and get BTU or whatever you're wanting
Click to expand...
Click to collapse
Also the csc is BTU, so it's changed compared to before I had PHN.
I start thinking that smart call is not available in the UK...

*Detection* said:
WiFi:
Battery Life: I am experiencing way better battery life, possibly due to factory resetting and not having a huge amount of apps installed, but I have gone from sometimes not even 4 hours SoT to easily over 6 hours, I did use a Package Disabler to disable a lot of bloatware / system apps that used to cause battery drain on Nougat (no root needed)
Click to expand...
Click to collapse
Wow. I never got 4 hours SOT on my s7 since it was brand new. Let alone 6.
Today seems like a fairly good day and I'm at 1.5 hours with 30% left.
Oreo is certainly a little worse than nougat though in terms of battery. Otherwise I like it.

joker950 said:
Also the csc is BTU, so it's changed compared to before I had PHN.
I start thinking that smart call is not available in the UK...
View attachment 4502670
Click to expand...
Click to collapse
Yep, OXA is not a CSC
I'm in the UK and have been using it for as long as I've had the phone and the firmware supported it, works fine in the UK
Carrier probably determines if you can use it or not, as with WiFi calling