This is for: Samsung GT-I9300 (Android 4.1.2 Phone)
Context: We are mobile development consultants and one of a beta versions of the an app we did for client is crashing on client's devices. (It was delivered through Testflightapp but since the app immediately crashes before the testflight session begins, we don't see any debug logs or crash log via testflight)
We want our client to send us the logcat contents so we asked him to:
1) Turn on the Developer Options from Settings/About Phone/ and Touch 7 times on the "Build Number".
2) In Developer Options you will see "Take bug Report". Touch it and Touch Report and it will take some time to prepare the email. When the preparation is complete you will see a notification which will ask you to Share the Report.
He replied:
Looking in developer options and I don't see anything called "take bug report
We then actually checked the user manual of Samsung GT-i9300 Galaxy and it does not have the 'take bug report' feature.
Question: How can we access the logcat contents from the client's device without resorting to integrating a logging framework in the app ?
Dump state error log or adb
Hello,
I'm developing an application that uses an external usb webcam. Times before i used a galaxy S3 for testing and everything work ok. But i had to change the phone because need more power so im trying now with a LG G2 (D802) with android lollipop stock (rooted).
With this stock android 5.0.2 SELinux state is set to enforcing and have a lot of denials trying to use cameras. I tried to change state manually due devide is rooted with commands "su setenforcing 0" and "su system setenforcing 0". The first seems to do nothing and with the second i get an error: "Could not set enforcing status: Permission denied".
I tried also with selinuxmodechanger and get notification of the change but still getting denials.
I can't check actual status because can't found SELinux state in "about phone" like in others devices. But errors show a tag named permissive and has value 1. I think should be 0...
I attached a image of logcat with the error.
Any help i really appreciate.
Thanks.
I found that the problem is not related with SELinux state.
SELinux state is already permissive, but, i read on chainfire web that warnings about avc denials still appearing in logcat even when enforcing is disabled and are not blocking anything actually.
The problem seems to be a bug in usb libraries when using otg usb 1. I read on dmesg log that an allocation bandwith on usb bus for the camera is failling on initialization (Not enough bandwith to allocate altsetting 5 2048B/frame). So, i solve this problem using a usb 2.0 otg hub.
I think this can be helpful for someone.
thanks
Seems tasker just won't turn on the hotspot on these. Anyone get it to work?
The error seems to state that the user does not have android.permissions.TETHER_PRIVILIGED so I went ahead and decompiled modified the manifest and then recompiled. I then used pm grant to grant the permission only to be met with "Operation not allowed: java.lang.SecurityException: Permission android.permission.TETHER_PRIVILEGED is not a changeable permission type".
Anyone find a way to resolve this? The dev says it's a sprint thing but tmobile users report it too.
Thanks
Dave
I am T-Mobile and no dice
I have latest updates and it fails for me too.
Wifi Tether enabled failed
Action Wifi Tether failed
result stop task (error)
Error 1
Action finished exeD 1 action no 0 code 113 status Err next 0
Used this all the time on my old phone sucks that this does not work now.
Anyone else? Seems to also do it on oreo w/ the S8+
Hello XDA community,
Im a noobie when it comes to rooting, thats why i need help...
I deleted some files that i want to recover on my Samsung S7 Edge 2-3 years ago, this device has Android 7.0. (Never updated)
There is a lot of apps such as Disk Digger that offer you to recover every single file but the device must be rooted to access 100% on the internal memory.
Right now my Samsung S7 Edge is not rooted but i need to root to recover this files, so my question is, there is anyway of rooting without factory reset, or there is anyway of doing a fully backup of the internal memory of my device without touching the partitions so then i can try recovering my files later with this apps?
I hope someone can help me...
Regards
It's pretty disappointing that nobody ever responded to this considering how big is a community it is and how popular the S7 Edge was. I know this is pretty old and hopefully you were able to resolve this before this message but I'm going to respond to this just so you don't feel like your question wasn't acknowledged at all. I have an S7 Edge through Verizon which uses the Snapdragon processor. And I will find a link to post for you that although the method says it's discontinued I rooted my phone through this method and it works fine. The only reason that you would have to wipe your phone is if you're changing firmware as far as I know. I've rooted my phones and did not have to wipe them. I kept all the data and everything.
Before I lift this you are also asking about an application that you could use to back up your phone and that would be Samsung smart switch. It has a companion app for the desktop and it sinks to the phone and it'll make a backup of your data.
Now on to the root method all props and praise goes to the people that worked to give this to the people I'm not good at doing all this **** and I'm not meaning to step on any toes I'm just trying to help you since nobody did for two ****ing years.
To root
1. Download PrinceComsys Odin
Odin.Prince.Comsy.zip
drive.google.com
2. Download the engboot.
Engboot Download
Nougat_S7_Edge_EngBoot.tar.md5
drive.google.com
3 make sure you have adb and fastboot installed on your computer (goggle them)
4. Root file
Download the file below.
Nougat_S7_Root_2_82_All_Carriers_V2.zip | by jrkruse for Galaxy S7 Edge
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
BELOW IS THE ROOT AND MOD FOR THE PHONE!!!!!
Follow this method to root:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, unlock developer options by going into the phone settings scroll down to 'about phone' find the build number and tap on it repeatedly after several times it will unlock Developer Options then back out once and in your settings you should have a new option on the very bottom called developer options go into that and enable USB debugging and Disable Verify Apps Over USB.
Plug the phone into the computer and make sure you have adb and fastboot installed to this location
C:\Users\YOUR PROFILE\AppData\Local\Android\Sdk\platform-tools
go to that folder and inside it hold shift and right click then click on 'open command window here'
then in command prompt type
adb devices
then hit enter.
The computer should automaticly detect and run adb
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and hold shift and right click then click on 'open command window here'
In the command window type root.bat then press enter from your PC.
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
Give phone a few min to settle open developer options set animation scales .05 and others to .05
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
SOLUTIONS
Did you:
? Open Odin as Administrator?
? Try the Prince Comsy version?
? Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
? Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
? Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
============
Congratulations! You are ROOTED but you're not done
Follow these instructions next
On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on "Enable su during boot".
This option will ensure that startup scripts that are installed during this process get to do their job correctly.
Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and copy this file to your device:
S7_VOLTE_ICON_FIX_ALL_VARIANTS or S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
turn off auto update of time and date in your phone settings, then set your year to 2013,
Launch FlashFire app on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step.
Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Tweaks to Root
Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working,
VoLTE icon appearing, searching for service issues, MMS not working, unauthorized security nag notification, etc.):
Full notes on what this flashable update does:
Adds a rotate button to the native gallery app
.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
after you flash your stuff change the date back. and you're good.
I know this all seems like a lot and it seems very confusing but it's pretty easy if you just follow the directions this will not wipe your data. Please do research, read through the forms and just tried to get as much knowledge as you can before you go about doing this it's an easy process but it's better to go in with more knowledge, I hope this helps. If you have to reinstall the firmware make sure that you install CSC home so you don't lose your data
Hi, using a rooted moto g7. There are /dev/graphics/fb{0,1}. I can not read directly from either device. The error given is "no such file or directory" however the files show up in a directory listing, this means the driver developer chose a bad error code.
How am I supposed to use them, for example to take a screenshot?
I see the sys nodes for the two devices /sys/class /graphics/fb{0,1}. I looked at their properties there, and see that fb1 is a writeback panel. As I understand it this is the one I should attempt to request screen data from.
I've looked at the msm_fb driver in the Linux kernel source but it's still not clear to me what I should do.