• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

How to resize active screen area / change height of screen?

I can't imagine you can do this without root: it's changing the way the display system works, so if Samsung haven't provided the option you'll surely need to be able to grant something system privileges in order to make that change, and that's what root does.

Thanks for your reply

If you know of a way to do this with root, is there any chance the permissions can be granted with ADB commands, as I know this works for some apps that require root.

Tablet not responding

I can now confirm that following the proceedure in the video above fixed the issue I had with the unresponsive Samsung Galaxy Tab A (2016) T580 (10.1 inch).

I disconnected the battery ribbon cable, disconnected the screen ribbon cable, reconnected the screen ribbon cable then reconnected the battery ribbon cable. My original idea of simply disconnectingthe battery and reconnecting it to "break a software loop" did now work. I have no idea why it is necessary to do both cables. Something to do with how the screen ribbon cable is seated, perhaps. Perhaps somebody with more tech know how than me can explain what is going on. All I know is my tablet is now talking to me agaon.
NICE!!!!!!!!!!!!!

thanx for posting your solution......you are braver then i am. i would have never attempted to open things up like that.

Help Installing USB Ethernet Adapter drivers

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>Prepare to build the driver, you need the Linux kernel sources installed on the</li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>build machine, and make sure that the version of the running kernel must match</li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>the installed kernel sources</li>
</ul>

Apps How to debug USB OTG application?

The adb command has a tcpip mode. I've used it and it works, but when I plug the USB OTG device in I stop getting logcat output. Maybe I'm doing it wrong, but maybe you can figure it out.

Code:
(base) puff@rockyraccoon:~/$ adb devices
List of devices attached
015629628541c1c8    device

(base) puff@rockyraccoon:~/$ adb tcpip 5555
restarting in TCP mode port: 5555
(base) puff@rockyraccoon:~/$ adb connect 192.168.66.27
connected to 192.168.66.27:5555
(base) puff@rockyraccoon:~/$ adb devices
List of devices attached
192.168.66.27:5555    device
015629628541c1c8    device

USB comms between Tablet and Ubuntu PC Exception

I'm still learning about this myself, but to use USB you need to make a permission popup happen and the user has to grant permission. Everything I've read so far says there's no way to skip that. Since you're seeing a SecurityException, my guess is that's what you're running into.

To make this happen, you need to set up the app configuration right, and in your code you have to create an Intent that asks for "com.android.example.USB_PERMISSION", call UsbManager.requestPermission() with it, and have a BroadcastReceiver ready to receive the permission response and use it to set up the USB connection.

See these links:
https://stackoverflow.com/questions/12388914/usb-device-access-pop-up-suppression
https://developer.android.com/guide/topics/connectivity/usb/accessory.html

If you've managed to figure this out since you posted this question, I'd appreciate some advice.

Android-x86 Installation

I install it on a Laptop, but on a VM.

They have instructions to run Android-x86 inside VirtualBox:
https://www.android-x86.org/documentation/virtualbox.html


If you're using VMware I found this:
Issues
VMware
You have to change your virtual disk type to be IDE because the default type in VMware is SCSI, and Android-x86 kernel is not configured to support SCSI. You can follow these steps:

  1. Create a virtual machine.
  2. Edit virtual machine settings after the virtual machine created.
  3. Choose the hard disk and remove it.
  4. Add a hard disk to create a new virtual disk, then you can choose IDE as your virtual disk type.
  5. When finished, you can install android-x86 normally.

Nagging issue with Multiple tablets

I've written an Android app for data logging temp and humidity from sensors in the house, via wifi and and Arduino. I'm currently running the app on three tablets;

LG LGLK430
Samsung SM-T110
ACER B3-A40

The app itself runs fine on all three devices, that is, until the screen savers kick in, or if I rotate the screen.

Once I rotate the screen, or awaken the device from the screensaver, the app acts as if it is restarting and the plotted data returns to its init values.

Does anyone know how to get around this issue?

Regarding the screensaver, I've done everything that I can to prevent the screen savers from activating.

I've tried using the following recommended code in the manifest file;

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.a_steve_app3">
mlns:tools="http://schemas.android.com/tools">

<uses-permission android:name="android.permission.WRITE_SETTINGS"
tools:ignore="ProtectedPermissions"/>


and the following in the main activity file;

android.provider.Settings.System.putInt(getContentResolver(), Settings.System.SCREEN_OFF_TIMEOUT,21600*1000);


Also, I've gone to file-settings-editor-inspections-'Using system app permissions' and unchecked the box.


When I do all of this, the code compiles fine but I still get the following error when running the app;

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.a_steve_app3/com.example.a_steve_app3.MainActivity}: java.lang.SecurityException: com.example.a_steve_app3 was not granted this permission: android.permission.WRITE_SETTINGS.

thoughts anyone?

Steve

Does this point to a permission setting on the devices? I've gone through the settings on all three devices looking for permissions options.

Corrupted SD Card backhanded Android Firmware

I've seen something similar happen before, although not on my s9, where a failing SD card caused the phone to misbehave and removing it made the phone work normally again. 5 years is an eternity for an SD card in a phone and you're lucky it lasted that long without a total data-robbing failure. I recently replaced the card in my S9, which was maybe a couple of years old, because it was getting cranky about saving new files which is a sure sign of impending failure.

Interesting, yeah I know the SD card is pushing it's lifespan hard, but it seems to have all the data there. I haven't noticed any issues since that message and the system failure, but nonetheless. The data kept on it was just pictures from devices generations ago, simply a convenient way to externally store and transfer data. Glad it's fixed, just never heard of it.

Filter

Back
Top Bottom