[Fixed] System freeze after playing with "secondary monitor" in Developer options
Hey, I just played around in the developer options and wanted to find out what "second monitor" does.
As far as I remember I set it to 480p and the system froze immdediately.
Rebooting the device shows the bootloader but the animation will stop soon.
I am using LineageOS 14.1 on my Sam S3 mini.
I was able to connect via adb - may be I can fix the problem by myself if someone can tell me where these settings are stored.
Some research here and with google gave no useful results so I just asked here.
--- Edit:
I was able to fix the problem in file /data/system/users/0/settings_global.xml which is not were I expected it to be (Google told me different).
Related
Being bored, I thought thought that I might scrounge around my Atrix's filesystem, and I ran into some interesting databases. I listed the one's I've found, along with the settings I've messed with. I hope this isn't a repost
/data/system/accounts.db
-> accounts
Stores phone accounts
/data/data/com.android.providers.settings/databases/settings.db
-> secure
install_non_market_apps #Pics below, proof of it working
throttle_threshold_bytes
throttle_value_kbitsps #This is unconfirmed but I set the two throttle settings high, and it's maxed out at higher than what I was previously downloading and uploading at
-> system
Has a bunch of system sound location paths that can be manipulated
haptic_feedback_enabled #Sets tactile feedback in phone app (i think)
screen_brightness #Values do not go below 30 or above 230
/data/data/com.android.providers.telephony/databases/telephony.db
-> carriers
Stores an array of carrier info
/data/data/com.motorla.android.providers.settings/databases/settings.db
-> settings
software_update_alert #Guessing gets rid of the annoying persistent update message
double_tap #Path to your double-tap app!
Restart and enjoy #PS that if you mess with the settings in the settings menu, it will overwrite your changes
Post more databases and settings, if you guys have found any
It is a repost, but thanks for the effort.
I have been successfully using the Verizon FIOS remote control app to control my TV FIOS STB and it is much nicer to use than the standard IR remote.
To get it to work originally using a nightly (circa 128), I had to persuade the Nook that it had a phone number as this is registered against one set in the STB. I did this by going into Settings/Call Settings/Additional Settings. This gives a network or SIM card error but when OK'd allow me to manually enter a phone number which then worked fine and continued to work through many nightly updates.
Something has now changed (I am currently on nightly 200) as I find that I have to re-register the FIOS app almost daily to get it to work.
On checking I find that the Phone Number setting gets lost periodically and set back to Unknown and I have to manually enter it again.
Does anybody know whether CM7 behaviour has changed with respect to the storage of the Phone Number? I realise it would normally be on a SIM, but it does seem to stick around for quite a while on the Nook before getting lost.
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
dgibb2000 said:
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
Click to expand...
Click to collapse
I have made some progress investigating this but have not got a final solution yet.
First, I can set my phone number up even though it is not a phone. I go into Settings, Call Settings, Additional Settings. The screen blurs and brings up a dialog box saying Call settings Error - Network or SIM card error. If I OK that then I see 3 menu items. The first 2 are grayed out but the 3rd "My Phone Number" is enabled. I select that and can enter a Phone Number. Are you saying you get the error and then all 3 options are grayed out?
Once entered I can view the Phone number via Settings, About Tablet, Status.
So far so good. The phone number setting does not normally survive a reboot, and also typically reverts to Unknown after a couple of days even without a reboot.
I have traced the Phone number setting to be stored in com.android.phone_preferences.xml which is in /data/data/com.android.phone/shared_prefs
But when the Phone number disappears it doesn't disappear from this file so there is some more complex interaction with trying to read a non-existent SIM first. So far I have traced the code involved to MyPhoneNumber.java and MSISDNEditPreference.java which are in the CyanogenMod-android_packages_apps_Phone-5d2764c.
I am still working on understanding this to see if there is some work-around to make the setting stick better. Currently I just have to check the phone number manually and set it again when it disappears.
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
dgibb2000 said:
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
Click to expand...
Click to collapse
Yes. That is strange. All my settings in Call Settings are enabled even though most are inapplicable. I don't think I have done anything to explicitly enable them and I'm on a standard Nightly 240 with the updated SystemUI.apk which turns off the phone signal bars. But I've never had these greyed out with any nightly build before.
Anybody else comment on whether their whole Call settings are enabled / disabled?
There is also a setting in build.properties in the system folder with a key called
keyguard.no_require_sim
I think this may have effect on how the OS treats calls which access the SIM. On my system this is currently set to 1. I might try playing with other values like true, 0 to see what effect that has.
Another theory as to why your call settings may be greyed out is that it they may get disabled in airplane mode.
Now this could be an issue even if you have set and subsequently cleared airplane mode as I believe the airplane mode setting doesn't go away entirely and can cause problems.
There is a command line way of clearing this setting completely which I did once when I set airplane mode on. Search for something like airplane sqlite to find the instructions.
That was it. I was stuck in airplane mode, and must have been for a long time. I used Android Assistant to clear the setting and it worked. I'm able to set my number and use fios mobile remote now! Thanks for your help.
Where did you get that updated systemui.apk to clear the cell signal bars? Now that I got the airplane mode off I have the signal strength there for no reason.
I got the SystemUI.apk from here
http://forum.xda-developers.com/show...60542&page=547
I just replaced the one in system/app. If you overwrite then you might get status bar forced close but a system reboot will sort that out and I haven't had signal bars since.
I've now put this in a zip that I can use to install after any nightly update I do as I've now found there is a wifi patch to deal with any remaining SOD issues although I haven't had one of those for a long time now.
Hopefully this stuff will get put into the main build before too long.
Looks like your link got clipped. Getting a page not found error.
Also, do you have any instructions on how to put the .apk into a zip for re-install after you do an upgrade? I'm assuming its not as easy as just ziping the file up?
Updated link
http://forum.xda-developers.com/showthread.php?t=960542&page=547
Yes. It is as easy as zipping the file up, but you have to create a matching folder structure to determine where the file goes. So in the case of the SystemUI file you create a folder called system containing a folder called app, put the file in the app folder and zip it so that system is in the root of the zip.
Correction: I thought that zip method was working but it wasn't. I had manually put the files in anyway and that worked OK. Then I was testing the zip, but it was actually failing.You need to put the files in a zip with the meta-inf etc. I think this link gives instructions
http://alldroid.org/default.aspx?g=posts&t=855
No. That doesn't work either as it uses an older method of scripting no longer supported. Apparently it needs to use Edify scripting now. It looks like some people add files to the gapps package, but I'm not clear yet whether it has to be re-signed, and I don't particularly want to redo gapps just to do this minimal patch.
I think I now understand how to produce an update zip that works.
I first took a gapp zip and stripped out all the existing files under system leaving the meta-inf alone. I put in the patch files in the appropriate folders under system. I then modified the updater-script in the meta-inf tree to just mount system, run package_extract_dir("system", "/system"); and unmount system with changes to the ui_print
I then signed the zip using the win-sign utility available here
http://forum.xda-developers.com/showthread.php?t=629151&highlight=sign+zip+files
I tried this out by first updating to nightly 246 and then applying my patch containing the SystemUI and the wifi driver that fixes SOD and that seemed to work OK.
I recently retired my son's Galaxy Tab 2 (7") for a new SM-710 (updated OTA to 5.1.1). The old Tab 2 (running CM12) was setup in multi-user mode with him as a restricted user. It worked great - I could limit his access on an app by app basis, his data didn't cross-over into my data, he could log into services with his own account etc etc.
So I had intended to setup his new SM-710 the same way - me as the primary user, him as a restricted user. One HUGE problem - the Samsung (TouchWiz) version of Lollipop seems to be missing a critical menu item that is present on stock Lollipop devices. I can't find the "add users from lockscreen" option in the USER settings. On stock devices there is a menu button (top right) where this option is located. It is usually defaulted to unchecked, however on the Samsung version, the device behaves as if the option is checked, and yet there is no menu item to uncheck. This results in both the "GUEST" and "ADD USER" items appearing in the multi-user lockscreen menu when the device is locked. This is a problem for a multitude of reasons. My son could simply create a new user from the lockscreen and use that account to bypass all the restrictions I have placed on his account. Moreover, anyone else could do the same thing, making it impossible to secure the device.
I have tried a few fixes that I found here and elsewhere. All of them required me to root the device, none of them worked (build.prop edits, sql db edits etc). Happy to describe in detail what I tried, but didn't want to make the post any longer that it had to be). Has no one else noticed this problem/error/bug? Am I missing something obvious?
Any help / insight would be appreciated.
Have a look at Samsungs' "Kids Mode", available in the Galaxy Apps store. It is supposed to be their solution for handing your tablet or phone to your children. It requires a pin code to leave the Kids Mode. However, I suspect it is targeted at rather youngish kids.
My T815, which is still at 5.0.2, doesn't even have the options you describe. I'm a bit annoyed that Samsung has spent time disabling features that just come for free from Google.
The build.prop edit should have worked according to other threads. I'm not rooted, so I can't tell.
Hi,
I tried to find root cause, but unfortunately without success. Is there anybody, who using Tasker or another application for automatization of your phone without any issues?
My issue is, Tasker is still "delayed" - but same rules I used before on LG G3 (Android 6.0) - but now on P9 (DualSIM) didn't work.
I have task for Calendar Entry, where if I have appointment in my work calendar, during this time Sound mode is deactivated (only Vibrate).
Some suggestion? I tried white lists, etc. or another app with same bad behavior.
Thank you!
Well, I tried to deactivate power management app from Huawei over ADB and looks good now finally! Its workaround, but tasker now working very well as expected.
adb shell pm hide com.huawei.powergenie
Did you have "Run in Foreground" selected in Tasker's preferences?
My Tasker works fine with that selected, although I also have trusted the app in permissions manager, allowed it to auto launch & activated it as a device administrator in advanced settings/security.
Yeah, I tried every tip over Tasker or phone (EMUI settings) and only deactivate power management helps me.
I had the same problem with IFTTT. It worked perfectly with my LG G3, but was hopeless on the P9. No amount of white-listing or settings would work.
I even had the app in memory, with Google maps running, on GPS, screen on, and it still wouldn't trigger a location based profile.
I've had to revert to manually arming and dis-arming my home security system. Annoying.
I translate from spanish so I'm sorry if your phone shows menus with other name.
You must go to adjust > advanced adjusts > memory and store and at bottom of page "space clean". On new screen push on upper-right wheel, and now on last option "white list of memory clean". Finally look for your app and activate it.
If you don't include app here, clean system will close it on background and timers won't work. It solved my problems.
aidrabmol said:
I translate from spanish so I'm sorry if your phone shows menus with other name.
You must go to adjust > advanced adjusts > memory and store and at bottom of page "space clean". On new screen push on upper-right wheel, and now on last option "white list of memory clean". Finally look for your app and activate it.
If you don't include app here, clean system will close it on background and timers won't work. It solved my problems.
Click to expand...
Click to collapse
"Settings>Advanced settings>Memory & storage>Storage cleaner" and "Memory cleanup whitelist".
Using Agama, I can get an app to start following a reboot. However, I would like to start the App at every Startup. Does Automate or any other app let you do that?
carroamer said:
Using Agama, I can get an app to start following a reboot. However, I would like to start the App at every Startup. Does Automate or any other app let you do that?
Click to expand...
Click to collapse
Why would you need Tasker for that simple.
Settings, type in the Search Autostart and add your app to the list of apps to be started on every reboot.
You may also need to disable Battery Optimization for your app (to make sure it would still work in background when the phone sleeps with dark screen)
That should generally work for all Androids. I don't have Huawei P9 now for years, I remember that EMUI might have had specific Settings organization but there was also Autostart (or Auto start)...
zgfg said:
Why would you need Tasker for that simple.
Settings, type in the Search Autostart and add your app to the list of apps to be started on every reboot.
You may also need to disable Battery Optimization for your app (to make sure it would still work in background when the phone sleeps with dark screen)
That should generally work for all Androids. I don't have Huawei P9 now for years, I remember that EMUI might have had specific Settings organization but there was also Autostart (or Auto start)...
Click to expand...
Click to collapse
When I search 'Autostart' it produces 'No results'
carroamer said:
When I search 'Autostart' it produces 'No results'
Click to expand...
Click to collapse
I had P9 for three years (if you don't believe, you can find tons of my posts here back from 2017-2018)
Now, you have that phone, not me (I got rid of my last Huawei almost three years ago) - I cannot show you and I cannot look into the EMUI settings because I don't have the EMUI phone anymore
But I KNOW that there was a way in EMUI how to control which apps will be automatically started on boot - I know because I played with all that back in those years, II did need for many apps like AdAway, Find My Device and similar that required to be auto-started to operate correctly
Take your time and google and you'll find. Sorry, I tried to help you but I will no more waste my time on that. Huaweis are past time for me
And take your time, use your imagination, If not Autostart, google for EMUI startup manager or something similar to find the answer for your question on the Net
Hi -
I'm using Android Studio to build an Android app that runs on a CCwGT (Chromecast with GoogleTV). I've been able to setup developer mode, and I have sideloaded my APK. Initially it didn't show in the default launcher, but I fixed that by setting up the project for "Android TV" in Android Studio.
Anyway I have multiple APK's from various sources (e.g. VLC) and I have NO problem assigning VLC to the supervised kids accounts I have set up. The problem is that I cannot do it for my own sideloaded APK. I'm not sure if I am missing some sort of configuration in the Manifest.xml or something else. The application is simply not visible in the list of apps, therefore I am unable to select it.
Since I am not a professional Android developer I am struggling to find information on how to solve this. Can anybody shed some light on how this is supposed to work? Could it be related to topics like content filtering or perhaps family sharing? Any hints or tips into the right direction are very appreciated.
I haven't setup a ADB yet since I don't have a USB3 hub with passthrough.
Thank you in advance.
You don't need USB for ADB -- it runs over network.
adb connect ip.add.re.ss