I recently used nomone resolution changer to change me tablet resolution with 1920*1080 220dpi. Upon restarting one day all of a sudden i get com.android.systemui and com.android.phone crash. I have usb debugging on but the problem is rsa keys. It has not been confirmed and i cannot since these crash notifications wont go away so i cant use adb shell.
i have used ro.adb.secure=0 ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.sys.usb.config=adb
but does not work.
Do you know which file saves the actual resolution, not build.prop. I mean which file does wm density reset and size reset change?
I have cwm and i can access recovery and download mode Its a samsung galaxy note 10.1 2014 edition
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Related
Hi Guys,
I have a HTC Desire with Defrost 6.1 + Data2SD.
However whenever I connect it to USB it always has USB debugging turned on, I can turn this on and it will work as normal until I reboot then it will be turned on again and I have to turn it off.
Why does it do this? Can I turn it off permanently (not totally remove it just have it set to off by default when I reboot) ?
Many thanks,
Stephen
I'd imagine that, with most other AOSP/CM-built ROM's, it has the following set in the default.prop file (contained in the boot image with the kernel)
ro.debuggable=1
persist.service.adb.enable=1
Both helps to debug/test/check ROM's when they are made, as devs/users can get straight into adb from boot of a freshly wiped & installed ROM to either view logcat output or fiddle about to resolve & sort out any issues which may be present after each release.
Hmmm ok so how can I disable this?
I have tried editing the file in the root of the phone but it seems to get overwritten, I'm guessing this is from the file contained in the boot image like you said.
Please bear with me, I'm new to android.
Hi, I have recently followed a guide to install S Voice on the GNex, In the tutorial, I had to do this "Fix" which apparently changes what apps and my PC identify the phone as, (Link has the full info.) Anyways, after I did that, it worked, but I noticed when I connect to my computer, it identifies it as a the GT-I9300. I ignored it because I knew why it was doing that. Later, I decided to delete the S Voice app because I wasn't using it, so I went ahead and uninstalled it and then reset the build.prop file from "GT-I9300" to "Galaxy Nexus" (IM SORRY, I THINK Galaxy Nexus ISNT the original string, can anyone tell me the original strings? ) Which was the original value for both lines ( ro.product.model and ro.product.device ) I rebooted and left it. I recently installed AirDroid and when I logged on, it showed an image of the S III for my device, instead of showing the GNexus. I know it probably doesn't affect performance, but I just don't like it! Anyone have the solution? I know that resetting to factory settings will probably fix it, but are there any better solutions?
LINK TO THE FIX I DID : http://forum.xda-developers.com/showthread.php?t=1664785
Image of airdroid dashboard : http://imgur.com/pKiIe
IF ANYONE HAS A SOLUTION PLEASE REPLY!
I would suggest backing up all your apps and data, then reflashing your ROM. But if you just want to change the build.prop, I'll include the device specific lines.
ro.product.model=Galaxy Nexus
ro.product.brand=Google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
C0dy said:
I would suggest backing up all your apps and data, then reflashing your ROM. But if you just want to change the build.prop, I'll include the device specific lines.
ro.product.model=Galaxy Nexus
ro.product.brand=Google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
Click to expand...
Click to collapse
Tried it, unfortunately didn't help! I I've also noticed that Google Play behaves the same way! It says I'm using a GT-I9300... I don't understand why, there is NO mention of GT-I9300 on that file!
Hi all,
I've a samsung S4 mini (i9195) and I want to boot the device when it's plugged to charger
I tried many solution I've found like change the playlpm file but it simply does not work.
So I've decide to modify the kernel. Has someone change on the kernel to do this?
At this moment i'm trying to change the code in file /init/main.c but it does not work
Someone can help me?
Any solutions (I9295 and playlpm-script not working either)
Hi
I'm also looking solution for the same problem. I have Samsung Galaxy S4 active (international version I9295) and I have tried several different solutions to fix this. I have already tried following solutions:
- playlpm basic editing (as seen on many, many tutorials)
- playlpm including chmod changes and SU additions
- correct chmod and chown settings to playlpm
- 3rd party apps (which of most do the same as I have done by had)
When using shellscript above (playlpm), phone (when plugged into AC or USB when off), shows blank battery icon, shows it for 5-10 secs and then goes blank, and repeats whole sequence again and again.
What I what considered is that somehow reboot mode itself calls playlpm again, so it is stuck in low power mode bootloop, but this is just guessing game.
Anyone with helping solution? I really would like to get my S4 A to boot on charge.
On new Sansumg devices the file isn't playlpm. The new name is only lpm.
Try this and tell us if you have success.
I was trying to change my G3 resolution to 1080p ( someone will ask what is the benefit form G3 with 1080p and why i didnt buy a phone with 1080p > answer : i dont care about resolution its not noticeable the only thing thats really matter is the PPI so if its 2K or FHD i dont care iam still have 530+ pixel)
back to my Q
I am not rooted ( and i dont want to ) & using ADB SHELL to make the changes
using this commands :
adb shell wm size 1080x1920 ( Resolution )
adb shell wm density 400 (DPI)
now the problems as you know i have to restart to make everything adopt the new R & D
G3 stock apps stop working on anything less than 530 DPI so i am using G2 lollipop stock apps now. thats a problem solved
PROBLEM NUMBER 2 & THE WORST ONE
after rebooting the phone i can hear the phone booting sound & i can hear the voice when unlocking lock screen but i am stuck at LG boot screen
2 times after opening a GAME the screen works again i dont know why xD
what i did is to enter this command : adb shell wm size reset ( which reset the resolution to stock but i still have the low DPI )
after entering this command without rebooting the screen comes back and the logo gone
so i reentered this command : adb shell wm size 1080x1920 & now the screen works but the apps are not looking good ( need restart )
so i need some one to help me to avoid ( skip) LG logo ( boot screen ) which i did by like 2 times
Solution - Root so you can use xposed mods to fix dpi in specific apps
I need help getting SmartThings working with LineageOS.
Short Version:
I have LineageOS 17.1 installed on a Tab S (SM-T700)
When I launch the SmartThings app it crashes
I've tried changing the build.prop
I've tried installing some Samsung account APK files
Long version:
I have two of the original Samsung Tab S (SM-T700) tablets that I bought new to use as controllers for my smart home. I have lots of smart home stuff, but I mostly control it all with SmartThings. The tablets are perfect for my needs: Thin and light in the perfect size, however they are now so old that the new version of SmartThings no longer works with the newest available stock Android, nor does Sonos, rendering them basically useless.
In an effort to revive them for their original use, I flashed one over to LineageOS. It works fine, however SmartThings crashes as soon as you get to the login.
I have read that this is caused because SmartThings looks at the build.prop, sees that this is a Samsung tablet, and then looks for the stock Samsung account management APKs.
First I tried changing the build.prop file. I rooted the device with Magisk. I then navigated to the /system folder and found the build.prop file. I opened it with a text editor. This thread https://forum.xda-developers.com/t/smartthings-crash-on-lineageos-with-samsung-tablet.4109423/ said to change
ro.product.brand=samsung to ro.product.brand=google
and
ro.product.manufacturer=samsung to ro.product.manufacturer=google
However, those exact lines don't exist in my build.prop. The closest I could find were ro.product.system.brand and ro.product.system.manufacturer. I assumed they were basically the same and changed those. When I saved the file, and opened it again, it had reverted back from google to samsung. So I copied the file to another folder and tried again. Saved the changes and they stay. However, if I copy back to /system, they revert to samsung. The only way I could get it to stick was to delete the original build.prop and THEN copy it back, but when I do that, and I reboot, the tablet hangs at the startup animation.
Clearly I am doing something wrong with changing the build.prop file. Can someone please explain this to me with step by step instructions?
I also saw this thread:
Getting Smartthings to work when you have debloated or used another rom
Hi, Just wanted to let you guys know how I got the Smartthings app to work on my S20 FE (Also my older Samsung devices) Some of the debloat guides/scripts remove either 1 or 2 packages required for Smartthings to work on Samsung devices. The...
forum.xda-developers.com
This says I just need to get
com.samsung.android.easysetup
com.samsung.android.beaconmanager
Installed and everything should work. I hunted down a couple APKs of those packages, but even after I installed them SmartThings refuses to load. Maybe I didn't have the correct version? Does anybody have a link to the exact files I should install to get this to work?
It seems like there are a couple of work arounds that will get me up an running again, but I can't seem to get anything to work. Please help!