I have seen meany forums ignore this one please help.
Device is T-mobile note 4
Rooted - I am using cyanogen mod - (trltexx) trltetmo does not work for my device.
( cm-12.1-20150808-NIGHTLY-trltexx.zip )
I get an MD5 error? but it installs anyway
There is no cellular service.
Everything works except my sim card. It wont detect it and my APN settings page says.
"APN settings are not available for this user"
Things I tried repeatedly as suggested by google searches
I tried each one with a clean rom install
1. - manually input APN settings (it wont save them)
2. - Reboot 5 times
3. - Remove the sim card before first boot
4. - Use wifi first to "warm up network"
5.- Wait 3 days for cellular tower to send me signal
6. - Wait 5 min
7. - Try a different rom (same problem with apn settings)
8. - let phone cool down with full battery
9. - Dial *#*#4636#*#* turn off radio?
10. - cry
I remember back when I had an HTC evo 4G everything was so simple...
I installed ROMs like crazy with no errors.
can anyone help me get my cellular service working?
Hi, i got the xiomi mi 5 like 4 days ago and i have had some issues
List:
1-Apps get kill in the background way to fast (1 min)
2-Can't i uninstall google apps
3-Notification don't show on the lockscreen
4-Why the f do i have to do a double finger gesture to expand notification
5-miui fails to change between 2g,3g and 4g
6- Settings that i change globaly in the security app then need to be change in everyapp
I really like the phone, it's super fast and good made but those miui things are really annoying for me now i have try cm13 and the one thing that kill me was that the recent app button was set to menu and you couldn't change it. It was the same for mokee and slimrom :/
Is there a rom that can help me with the "problems" i have?
∆ Sorry if my english is not the best.
Backup your phone first !!!
you can try flashing this to restore your Xiaomi keys or if you want to do it manually,...
Make sure you grant root access to your file manager.
open file manager or ES Explorer or any other root file manager in phone and go to
Code:
system/usr/keylayout/
open the file "synaptics_dsx.kl" in any text editor
edit the following
Code:
key 139 APP_SWITCH VIRTUAL
key 158 BACK VIRTUAL
save & set permission as follow
Code:
S R W X
OWNER [] [x] [x] []
GROUP [] [x] [] []
OTHERS [] [x] [] []
Reboot...
chiragkrishna said:
Backup your phone first !!!
you can try flashing this to restore your Xiaomi keys or if you want to do it manually,...
Make sure you grant root access to your file manager.
open file manager or ES Explorer or any other root file manager in phone and go to
Code:
system/usr/keylayout/
open the file "synaptics_dsx.kl" in any text editor
edit the following
Code:
key 139 APP_SWITCH VIRTUAL
key 158 BACK VIRTUAL
save & set permission as follow
Code:
S R W X
OWNER [] [x] [x] []
GROUP [] [x] [] []
OTHERS [] [x] [] []
Reboot...
Click to expand...
Click to collapse
I'll try it once i get home, thank for replying :fingers-crossed:
it didn't work :c buttons stay the same
I really wasn't a fan either. I installed Resurrection Remix and am now 95% happy with that!
hi,
i've got a problem that occurs with all the rom i've tried (omni, cm and resurrection).
i set the network as wcdma only, but when i turn off and on the phone it changes automatically on wcdma preferred.
can it be solved ?
Thanks !
edit:
i've tried to modify the lines in the build.prop that cahange the network setting, but these lines there aren't
ro.telephony.default_network=xx
Hi,
my Huawei P9 (EVA-L19, Android 6.0 / EMUI 4.1.1, root) is playing with me :/
With SIM #1 I have no access to the menu "caller id" in phone > settings > advanced/additional > caller ID (show my number / hide my number / operator default settings), because the menu is greyed out.
If I put the same SIM #1 in the other device (Samsung Galaxy S5, Android 4.4.2, root) I have access to this menu.
If I put a SIM #2 (other operator) in my P9, menu "caller id" is active.
And so:
P9 + SIM #1 = menu is not active / greyed out
SGS5 + SIM #1 = OK
P9 + SIM #2 = OK
SGS5 + SIM #2 = OK
There are no restrictions like CLIR on the SIM #1. I have tried everything (change the settings, make a call, save the settings, again change the cards between the devices) - no results...
I think, booth SIM-Cards are ok (not damaged), booth devices are working fine as well, so I would like to use some "magic codes" or find a new "hidden option" to activate this menu for the SIM #1, before I try factory reset and setup the device again...
Any ideas?
TIA
t.
PS
My P9 is a dual sim, but I use olny one SIM + SD-Card
Hi All,
TLDR:
- LineageOS 16, Dual-SIM
- Deactivated second sim in the settings
- Updated to LOS 17.1
- SIM is still deactivated, no button to enable
- Looking for ways to remove SIM card settings
before upgrading from LineageOS 16 to 17.1, I had my second sim card disabled via the general slider (it's my business sim, and I was on vacation). This slider feature now seems to be gone in LOS 17 but the sim is still in a disabled state, meaning LOS is not even asking me for a pin on boot, instead I receive a message saying "Adroid System" / "There's an internal problem with your device. Contact your manufacturer for details". I can still see the sim in the settings (which actually freeze if I try to change carrier settings), and the sim is visible in the top bar with zero reception and the "x". I can still use the sim card in other phones, but the OP3T seems to have memorized the sim card settings somewhere, regardless of which sim slot I use. My solution would have been to delete the per-sim settings, that LOS seems to be storing somewhere, but I have no idea where they could be located.
Any pointers or other ideas would be much appreciated. Thanks!
Same issue here:
System:
- Hardware: OnePlus 3T
- Firmware: 9.0.3
- Recovery: TWRP 3.3.1-1
- Software: LineageOS April 25, 2020
Symptom:
Dual SIM issue: SIM1 (in slot1) works as expected. SIM2 (in slot2) never connects to its network. I use SIM1 mainly for calls, SIM2 mainly for data.
Tried:
- to update firmware to 9.0.6, no change
- to swap SIM1 and SIM2, SIM1 still works in slot2, SIM2 does not work even in slot1, no change
- to remove SIM1 and keep only SIM2 (slot1 or slot2), no change.
- to use different bands GSM/WCDMA only for SIM1 (was GSM/WCDMA/LTE) and LTE only for SIM2 (was GSM/WCDMA/LTE), no change
Hints:
- when I installed LOS17.1, SIM2 was probably locked (I only unlock it when I used mobile data)
- at boot, only PIN1 is asked, not PIN2
- in SIM2's menu, choosing "Advanced > Access point names" crashes `Settings`.
- when SIM1 is not inserted, only SIM2, the `Mobile data` icon in `Quick tiles` does nothing
I looked in this XDA thread dedicated to LineageOS 17.0/17.1 on OnePlus 3/3T, and found several messages complaining about SIM cards not being detected. The problem seems different and the solution suggested is outdated, since the line is now already in `init.qcom.rc`.
The most similar issue is this thread, I cross posted in reddit. I searched gerrit for `dual sim` in the lineage-17.0 and lineage-17.1 branches as well `sim` in the oneplus_oneplus3 tag, without success.
Any idea?
Summary: `/data/system/radio` seems to be broken. Should be replaced with the same directory from a clean install. This breaks PIN auth, which means that
`/data/system/locksettings.db` has to be removed as well, and the PIN reconfigured.
Steps:
0. reboot in TWRP
1. backup broken `data` partition
2. wipe data partition
3. adb sideload `lineage-17.1-20200423-nightly-oneplus3-signed.zip` and `open_gapps-arm64-10.0-nano-20200516.zip`
4. reboot in system
5. make sure that both SIM cards are unlocked and working
6. reboot in TWRP
7. backup working `data` partition (or copy `/data/system/radio` somewhere)
8. restore broken `data` partition
9. move `/data/system/radio` to `/data/system/radio_broken`
10. put instead `/data/system/radio` extracted at step 7, either by gunzip/untar backup, or from the "somewhere" you selected
11. delete `/data/system/locksettings.db`
12. reboot into system
13. unlock both SIM cards
14. set a PIN
Done
why are the devs unable to solve that with an update or flashable zip?
Notor1ouS- said:
why are the devs unable to solve that with an update or flashable zip?
Click to expand...
Click to collapse
Clean flashing on major version bumps will always avoid this issue in the very first place. In my opinion there are much more important topics for a dev to focus on then getting dirty upgrading major versions fool-proof as long as clean flashing works flawlessly and fool-proof.
i disagree on that. a competent dev should be able to do that.
but that's going nowhere anyway, so I'm out.
Notor1ouS- said:
i disagree on that. a competent dev should be able to do that.
but that's going nowhere anyway, so I'm out.
Click to expand...
Click to collapse
If you have the competences and the knowledge to fix issues from dirty upgrading, go ahead, dirty upgrade and fix the issues.
If you don't have the competences and the knowledge to fix issues from dirty upgrading, go ahead and clean flash as recommended on major version bumbs.
If you don't have the competences and the knowledge to fix issues from dirty upgrading and you are resistent to recommendations, blaming the devs as incompetent will polish your ego but don't fix the issue.
For a community driven open source project, you can easily push a fix instead of blaming the devs as incompetent!
Be a user - not a customer.