Hey there, I was looking for a way to remove the "No SIM Card" notification (which appears for who dont insert a SIM... duh)... so i found a way to hide it by replacing a line in build.prop
(First you need to have root access and an app that can access system/build.prop in rw mode)
so the line you find by default is ro.config.tima=1
for me, it worked to remove this line and replace with the following ro.config.donot_nosim= true
This is not my own work, and im just sharing with xda, because i never found this in here (except just removing the icon, which does nothing on s5)
Source: answered by the user mag1071983 at http://android.stackexchange.com/.../remove-no-sim-card-in-phone-message
good info! thanks for sharing!!
hi,
is tehere any way to remove sim inserted alert?
Related
Hello!
Recently allowed the phone to update itself over the air - Android update (28th Dec 2010). After it did it's stuff, I now have a Triangle in the top of the screen /!\ as a notification "SIM card changed" - Tap here to change your settings"
If I tap here... I get a warning:
Code:
You have insterted a new SIM card.
Your phone will change the
following settings according to
your SIM card: bookmarks
shortcuts, wallpaper, ringtones,
language selections, and input
settings. Are you sure you want
replace these settings on your
phone?
YES. No, later. NO
What the hell??? I havn't touched the SIM card, just updated the OS to 2.2.1 (I think that what the update did).
Cheers for any insight. e.g. Should I select YES or NO to the above request?
Andy
hi there
s.memo keeps Crashing I am on a stock Rom
2.6.35.7-N7000XXKJ4-CL641703
[email protected] #2
I bought it from amazon.de, i am in UK
basically if i try to launch s memo directly via shortcut on home screen (finger or stylus) i get
A blank screen for a few seconds or so then i
Get a force close dialog saying s memo has stopped
Working (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly....
I can create an s memo widget on the home screen
And if i tap on this it launches what i assume is s memo and i can draw etc and save etc, this then turns the widget into mini version of whatever i drew/wrote but if i tap on the saved widget i get the force close dialog, i am able to click the widget "+" icon on the newly saved widget and i can work on a new s memo doc, but after saving.... Force close etc.
I have completely wiped phone factory reset etc and nothing installed no joy. Any help would be much appreciated. Could not find any info googling relevant terms.
Thanks
s memo crashing
Try this to solve the problem:
1. Find /data/system/packages.xml with Root Explorer.
2. Make a backup of packages.xml right away in the same folder in case we mess anything up any need to restore it later
3. Copy packages.xml onto the root of your internal or external storage
4. Plug your device into your computer and copy packages.xml from the root of your storage over to your computer
5. Open the packages.xml on your computer with your editor of choice - I use Wordpad
6. Search for the string. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044">
7. then, you need to put/add this: enabled="1" at the last line before the ">" sign. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044" enabled="1">
Do this work?I have not rooted my phone but will do it just to solve this problem!
no that doesnt work
man I hope someone find a fix for this!!
I updated my firmware to the latest open Europe one and the problem stop! So the best to solve this problem is to.flash a new firmware!
Pure vida guys!
Sent from my GT-N7000 using xda premium
I was following this thread and I used the application to find the db to add back mobile data to the toggles, but whenever I go to settings.db it tells me something about code 14 error and I cant edit the database to get the toggle back, does anyone know why this happens or if there is another method
http://forum.xda-developers.com/showthread.php?p=43042030#post43042030
Hello K3 Note users!
So, about 5 months ago I discovered that my back and menu keys were not working. I tried rebooting the device, pulling the battery out, changing the ROM and I even opened the phone up, to see, if every wire was connected properly....but the problem wasn't to be found. I also tried to get some support from the Lenovo's website, but I ended up getting none.
Eventually I found a workaround, that does not fix the problem itself, but it makes the phone usable again.
The solution is easy and it has already been written before:
1) Flash a custom ROM.
2) Make sure that you have ROOT.
3) Download a file manager, that can make use of the root rights.
4) Go to /system/build.prop
5) Add the line: "qemu.hw.mainkeys=0" to the very end of the file.
6) Reboot and voila!
However, I found that some apps refused to work with the nav bar and some vital content of those apps got hidden by the buttons.
I managed to found a fix for this problem. It can be solved with a wonderful Xposed module titled "Hideable Nav Bar".
The plugin will create a little down arrow on the left of the nav bar. This will let you to hide the bar whenever you want/need to. When the bar is hidden, then bringing it back is as easy as swiping up a bit from the bottom of the screen.
(I won't give you the steps on how to install Xposed, because it has already been described in the general thread.)
Anyway if you have installed Xposed, then you want to go to "Download" and search for this module. After that you should install the module, activate it and then reboot your phone. :good:
I hope this post was helpful to some K3 Note users and if it did help you, then don't forget to press the "Thanks" button too!
Hello, Just a small hack that allows me to use the VoLTE that my provider points out is "only available on handsets purchased directly from them" (SFR in France). This got me thinking ==> If VoLTE works on their handsets and not mine then :
a) The carrier infrastructure supports VoLTE
b) The sim cards must be provisioned correctly
c) The difference would therefore be in the telephone configuration ==> I'm thinking build.prop config in their "special firmware"​
So looking through various forums - I came across the following:
https://forums.oneplus.com/threads/root-working-volte-on-stock-oxygen-3-1-0.480128/, https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613 and https://source.android.com/devices/tech/config/carrier (to help understand what IMS is all about)
Here's what I added to the end of my build.prop [you will need root for this]:
Code:
#VoLTE - force the IMS into VoLTE provisioned mode on.
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
If you don't want to do that directly in the build.prop you can do this directly from a debug shell
Code:
adb shell
$ su
# setprop persist.dbg.ims_volte_enable 1
# setprop persist.dbg.volte_avail_ovr 1
# reboot
Please note that this did indeed allow me to make/receive calls and use 4G at the same time.
I also see "HD 4G" logo appear to the left of my signal bars.
When I look at my phone config (dial *#*#4636#*#*) I see VoLTE as provisioned.
I think that these lines force the phone to use VoLTE - the risk is that this might break your 4G - you have been warned. I don't guarantee that this works for you.
Can an administrator place this in the https://forum.xda-developers.com/mi-a2/how-to forum please ?
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
if yuou don't have root you can use *#*#86583#*#* . tested working on sfr too.
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
duxxyuk said:
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
Click to expand...
Click to collapse
VoWifi how? Whats the code?
I've got these lines on the back of my build.prop but it doesn't appear to work for me:
Code:
#WiFi calling
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1
rober788 said:
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
Click to expand...
Click to collapse
How does a temporary root work? I can't find anything with Google.
Magisk module VoEnableer maybe the best chois.
Thanks for sharing.. it also works on mi a2 lite
Thanks, It works