I have given my phone to repairing service to change the case and glass for new ones. After 2 weeks + I got my phone back. Everything was cool except the fact that my speaker(the one from which you hear the caller) stopped working; so I came back again to this service and gave them back my phone. They were fixing it in connection with guarantee. After 1 week or so I got it back. Speaker worked at the service. Then I have pushed Lineage OS update from 20 of June and speaker stopped working again....
I plan going to service yet again tomorrow. Until then I hope somebody will answer in this thread.
My phone details are as follows:
Device: SM-A520F
Android version: 7.1.2
Lineage OS version: 14.-20180620-a5y17lte
Lineage OS API Level: Guava (7)
Android security patch level June 5, 2018
Baseband version: A520FXXU2BQIE
Kernel version:
3.18.14-g406953af719
[email protected] #1
Wed Jun 20 00:09:49 UTC 2018
Build date: Wed JUn 20 00:06:21 UTC 2018
Build number: lineage_a5y17lte-userdebug 7.1..2 NJH47F 20180620 dev-keys
SELinux status: Enforcing
binpx said:
I have given my phone to repairing service to change the case and glass for new ones. After 2 weeks + I got my phone back. Everything was cool except the fact that my speaker(the one from which you hear the caller) stopped working; so I came back again to this service and gave them back my phone. They were fixing it in connection with guarantee. After 1 week or so I got it back. Speaker worked at the service. Then I have pushed Lineage OS update from 20 of June and speaker stopped working again....
I plan going to service yet again tomorrow. Until then I hope somebody will answer in this thread.
My phone details are as follows:
Device: SM-A520F
Android version: 7.1.2
Lineage OS version: 14.-20180620-a5y17lte
Lineage OS API Level: Guava (7)
Android security patch level June 5, 2018
Baseband version: A520FXXU2BQIE
Kernel version:
3.18.14-g406953af719
[email protected] #1
Wed Jun 20 00:09:49 UTC 2018
Build date: Wed JUn 20 00:06:21 UTC 2018
Build number: lineage_a5y17lte-userdebug 7.1..2 NJH47F 20180620 dev-keys
SELinux status: Enforcing
Click to expand...
Click to collapse
Yeah, i installed AOSP extended yesterday, first few hours everything was fine and afterwards i noticed that there is no sound coming at all, i already tried some things but nothing seems to work.
We have the very same phone, the problem might be something caused by getting a custom rom itself.
Related
Phone: LG G3 (Europe) d855
System: CyanogenMod Android 6.0.1 Marshmellow
(TWRP 3.0 + ROOT USER and a GAPPs pack)
PROBLEM: the phone boots every time i want to make a call.
I will add dome screenshots.
Please help!
And thanks.
**** ****, doesn't let me post images, i will write it instead.
Model: LG-D855
Android Version: 6.0.1
CyanogenMod Version: 13.0-20160524-NIGHTLY-d855
API lvl on CyanofenMod: Fig (6)
Android Patch Security lvl: May 1, 2016
Base Version: MPSS.DI.2.0.1.c1.13.2-00002-M8974AAAAANPZM-1
Core Version: 3.4.0-CM-g4afd674
[email protected] #1
Mon May 23 19:41:02 PDT 2016
Compilation Date: Mon May 23 19:36:49 PDT 2016
Compilation Number: cm_d855-userdebug 6.0.1 MOB30J 0dec70d4bc test-keys
SELinux State: Obligatory
Hello, I would know because my Samsung j3 2016 smJ320FN, after I have completed the root, he is firm on the logo, it appears and it disappears but he remains always on the logo, Thank you very very much
information:
Android version : 5.1.1
Baseband version: J320FNXXU0AQC6
Kernel version: 3.10.65-10519280
[email protected] #2
Mon Feb 27 20:36:15 KST 2017
Build number: LMY47V.J320FNXXU0AQB3
SE for android status: Enforcing
SEPF_SM-J320FN_5.1.1_0072
Mon Feb 27 20:51:45 2017
Ono Minori said:
Hello, I would know because my Samsung j3 2016 smJ320FN, after I have completed the root, he is firm on the logo, it appears and it disappears but he remains always on the logo, Thank you very very much
information:
Android version : 5.1.1
Baseband version: J320FNXXU0AQC6
Kernel version: 3.10.65-10519280
[email protected] #2
Mon Feb 27 20:36:15 KST 2017
Build number: LMY47V.J320FNXXU0AQB3
SE for android status: Enforcing
SEPF_SM-J320FN_5.1.1_0072
Mon Feb 27 20:51:45 2017
Click to expand...
Click to collapse
You need to flash supersu v2.79SR3 to get root access without bootloop.
Flash Stock ROM via SmartSwitch and try with v2.79
Anyone have any problems that popped up?
On my phone, So far so good. Not noticing anything that isn't working right.
Only had to update 19 apps from the playstore.
I'm using AT&T for my carrier.
One UI version
1.0
Android version
9
Baseband version
G965U1UEU3CSA8
Kernel version
4.9.112-15119402
#2 Tue Jan 15 20:11:43 KST 2019
Build number
PPR1.180610.011.G965U1UE3CSA8
Knox version
Knox 3.2.1
Knox API level 27
TIMA4.0.0
You really made a op about this... Wheres the issue?
PoochyXXX
FastEddieR said:
Anyone have any problems that popped up?
On my phone, So far so good. Not noticing anything that isn't working right.
Only had to update 19 apps from the playstore.
I'm using AT&T for my carrier.
One UI version
1.0
Android version
9
Baseband version
G965U1UEU3CSA8
Kernel version
4.9.112-15119402
#2 Tue Jan 15 20:11:43 KST 2019
Build number
PPR1.180610.011.G965U1UE3CSA8
Knox version
Knox 3.2.1
Knox API level 27
TIMA4.0.0
Click to expand...
Click to collapse
I just got mine today. So far, so good. I guess the silver lining for being last is that everyone else has already tested it on everything.
Hey guys, I'm trying to flash SM-G960U1 (Unlocked Samsung S9) so I can get Wi-Fi calling enabled but with Odin I keep getting stuck at SetupConnection and after a while it says <OSM> All threads completed. (succeed 0 / failed 1). However adb and everything else works; Samsung Smart switch can go and communicate with the device. I've also tried several different versions of Odin (3.13.1 PatchD, 3.14.1 PatchD and the unpatched 3.14.1 from SamMobile) Anyone know why Im having such trouble getting odin to flash firmware?? The phone's running Android 10 and has the May security update; and my carrier is AT&T
I have SM-G960U too, looking for VoLTE. my firmware details :
PDA/AP Version: G960USQU3BRJ5
CSC Version: G960UOYN3BRJ5
MODEM/CP Version: G960USQU3BRJ5
Android version: 8.0.0
Samsung Experience version: 9.0
Baseband version: G960USQU3BRJ5
Kernel version: 496514537311 dpiasWDG4718 #1 Mon Oct 15 18:43:57 KST 2018
Build number: R16NW.G960USQU3BRJ5
SE for Android status: Enforcing SEPF_SM-G9600_8.0.0_0017 Mon Oct 15 18:53:03 2018
Knox version:
Knox 3.1
Knox API level 25
TIMA 4.0.0
Service provider SW ver.:
SAOMC_SM-G960U_OYN_AIO_00_0060 4135324133583398
AIO/XAA/AIO
Security software version:
MDF 3.1 Release 2
WLAN V1.0 Release 1
VPN PP MOD v2.1 Release 1.1
ASKS 11:45 Release 180123
FIPS Boringssl V12
FIPS SKC v1.9
FIPS SCrypto v2.2
SMR Oct-2018 Release 1
Android security patch level: October 1 2018
Hello all,
The last updated I received on my AT&T Note 4 was the August 1, 2017 Android security patch level, which was probably around September-October of 2017 (obviously I don't remember).
But, mid-morning Nov 12, 2020 I started receiving notifications that a software update was available. I just ignored them, thinking it was some kind of bug. But when I woke up the morning of Nov 13, 2020 I found that my phone had restarted after installing the update. It was waiting on my boot password, and after typing that in it went through the normal "optimizing apps" screen that appears after a system update.
Here is the information from the "About device" page:
Device name
SAMSUNG-SM-N910A
Model number
SAMSUNG-SM-N910A
Android version
6.0.1
Android security patch level
August 1, 2017
Baseband version
N910AUCU2ETI2
Kernel version
3.10.40-8932341
[email protected] #1
Mon Sep 14 16:23:37 KST 2020
Build number
MMB29M.N910AUCU2ETI2
Security Enhancements for Android status
Enforcing
SEPF_SECMOBILE_6.0.1_0029
Mon Sep 14 16:28:02 2020
Security software version
MDF v2.0 Release 6
VPN v1.4 Release 6.1
ASKS v1.2 Release 161011
KNOX version
KNOX 2.6
Standard SDK 5.6.0
Premium SDK 2.6.0
Customization SDK 2.6.0
Container 2.6.0
CEP 2.0.1
Enterprise Billing 1.2.0
OTP 2.6.0
SE for Android 2.4.0
SSO 2.5.0
Shared Devices 2.6.0
TIMA 3.2.003
VPN 2.2.5
So it looks like somebody (Samsung?) in Korea (KST is Korea Standard Time) compiled the Linux kernel on Mon, Sep 14 2020 4:23 pm and pushed out an update. Anybody have any further information?
AT&T has an information page on the update here (I included spaces in the URL which you'll have to remove manually due to forum not letting me post links):
<AT&T Base URL> / device-support/ article/ wireless/ KM1126949/ Samsung/ GalaxyNote4N910A
But there's no information other than the release date was Nov. 10, 2020. Android version is still 6.0.1 (same as last update), and the Security patch level is still August 1, 2017 (same as last update).
The kernel version in this update is 3.10.40-8932341, same as the kernel version from the July 21, 2017 AT&T update, but the compile date of this kernel is Mon Sep 14. So I don't know if Samsung/AT&T applied some patches without bumping the kernel version, or if they just recompiled the kernel for fun.
erichritz said:
AT&T has an information page on the update here (I included spaces in the URL which you'll have to remove manually due to forum not letting me post links):
<AT&T Base URL> / device-support/ article/ wireless/ KM1126949/ Samsung/ GalaxyNote4N910A
But there's no information other than the release date was Nov. 10, 2020. Android version is still 6.0.1 (same as last update), and the Security patch level is still August 1, 2017 (same as last update).
The kernel version in this update is 3.10.40-8932341, same as the kernel version from the July 21, 2017 AT&T update, but the compile date of this kernel is Mon Sep 14. So I don't know if Samsung/AT&T applied some patches without bumping the kernel version, or if they just recompiled the kernel for fun.
Click to expand...
Click to collapse
The information page link is https://www.att.com/device-support/article/wireless/KM1126949/Samsung/GalaxyNote4N910A
It says that the change is to implement a "Network conflict fix".
The build number and baseband version have been updated:
Build number: MMB29M.N910AUCU2ETI (was MMB29M.N910AUCS2EQH1 )
Baseband version: N910AUCU2ETI2 (was N910AUCS2EQH1)
I haven't updated and I haven't noticed any network issues. I'm using a data only SIM from AT&T MVNO FreedomPop which doesn't get updates. I'll probably use an at&t SIM to update in a few days if no one reports any issues with the update.
I took the update around the middle of December (three weeks ago). I haven't noticed any issues or any visual operational changes at all.
`