One shortcoming of 12T pro is slow file transfer speed, any suggestion?
Make sure that it's running USB3.
(Does it even have USB3? Type C connector is a guarantee of nothing.)
Check to see if there is a difference in writing to /sdcard vs. /data/local/tmp
There could be some slowdown due to sdcardfs or whatever is handling /sdcard.
If rooted, run dmesg to make sure that the USB is not thrashing.
Yes, because this phone used USB2.0.
USB2.0 is the characteristics of Xiaomi.
Dispossible said:
Yes, because this phone used USB2.0.
USB2.0 is the characteristics of Xiaomi.
Click to expand...
Click to collapse
Thats right. Usb 2.0 is so slow.
Renate said:
Make sure that it's running USB3.
(Does it even have USB3? Type C connector is a guarantee of nothing.)
Check to see if there is a difference in writing to /sdcard vs. /data/local/tmp
There could be some slowdown due to sdcardfs or whatever is handling /sdcard.
If rooted, run dmesg to make sure that the USB is not thrashing.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What should I look for?
That looks ominous, but Android is a never-ending crescendo of errors.
Note the time (1968), do another transfer and see if there are new errors.
Use WIFI to share files between pc and android for example X-plore app with WIFI 6 u can get 50MBps instead of 20MBps with USB
Personnaly it tryed to send a movie of 1.16go, it took 33 sec so not so slow, i was wondering because after sending back 70go of data last time it didnt took so long, im on 12t pro btw
Correct me if im wrong but 1160mo/33s = ~35mo/sec on a usb3.0 hub wich look pretty ok even if its not ssd speed
I sent on my usb 3.0 usb hdd and i had arround 91mo/sec ... it took 14 sec to send
Related
Hey Guys,
I am using a Samsung Galaxy S2 I-9100 Carrier T-Mobile Hungary; though this started back when I was using AT&T from the US
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am having the problem very similar to this post: http://forum.xda-developers.com/showthread.php?t=1317916&highlight=USB+does+-work
Though the poster has abandoned the question so I thought it wise to repost.
What I have seen:
When Plugging my device into any computer using any USB cable the result is the same.
If on - nothing happens; no notice on the PC and no charge on the phone. I have tried with debugging on/off, I have tried USB Mass storage mode no difference.
If off - It will turn on the phone and then the phone will show charging state though it will lose a charge and the PC will not say a device was plugged in. Also if phone is unplugged after it is on it will continue to say it is charging until a reboot.
If in Recovery Mode - Mounting any form of drive is not seen by the computer.
If in Download Mode - Device will say charging and drivers will attempt to install on the computer and I will see an unaccessible folder in "computer" that says "samsung i-9100"
I have just checked the web for updates and it says none found. To my limited understanding I am using a Stock ROM with an edited Kernel to give me root access.
I performed the update of the Kernel identically on both my and my fathers Identical phones and his has not had any problems. The only difference between the two is He is still on AT&T US; While I have moved to Hungary. But as I said the problem existed before that
If there is ANYTHING I can gather or forgot to submit that may offer some light to my problem please let me know.
Thank-You Very much for reading.
Regards,
Joshua Puckett
Fixed - I was using the cable that came with my Storm 2 BlackBerry; and tried after that a Cable I had bought at Radio Shack.
Once I tried the original Sammy cable it all worked;
Thanks to those who looked!
Hi guys.
Trying to hack my device and rewrite its bootloader to make a prototype for my project, but I'm new to this.
I already have root permission on ClockworkMod Android.
Initially I tried to reinstall OS to Android that I build from source code. But device hasn't got fastboot. So I decided to start from the bottom.
Current problem is that I have to locate UART on my device. Can't provide a photo of its board.
http:##s8.postimg.org#rqfzm4pdx#device.jpg
I read some articles about it and have prepared oscilograph and multimeter. But still, need some help.
Processor is AllWinner A13, have found its datasheet. UART RX and TX pins are 151 and 152, 125 and 124, 13 and 12, and I have no idea how to connect to it.
Could you give me some hints or useful links? Maybe some advice, please?
Thanks in advance.
Trying to analyze pins with mutimeter. Do I have to turn on the device?
Aaawwh, that's such an ugly board... (Compared to Oppo-7!)
Here's you pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need the correct USB-to-serial cable, like those offered by FTDI R232Vxxx models. But you have to know what voltage to use!
E:V:A said:
You need the correct USB-to-serial cable, like those offered by FTDI R232Vxxx models.
Click to expand...
Click to collapse
I've got this one too. I've borrowed it from someone, but I don't know how to use it yet.
E:V:A said:
But you have to know what voltage to use!
Click to expand...
Click to collapse
I found these four pins strange (in attachment), and checked it with multimeter. Pins from top to bottom 1, 2, 3, 4.
1-2: 3.25V,
1-3: 3.25V,
1-4: 3.25V.
What can I do to be sure than these are right pins before I start soldering?
^^ You don't solder anything. You only need GND attached + Rx to probe.
Those pins are probably not UART... No telling. What's on the backside?
E:V:A said:
What's on the backside?
Click to expand...
Click to collapse
:laugh:
Hi guys,
I just installed the CROMBi-kk Rom from the relative thread in my ASUS TF201:
http://forum.xda-developers.com/showthread.php?t=2773812
It's very fast and smooth...I confirm camera problems but this is minor problem for me: my camera is affected of "green screen" bug..
My problem is the USB OTG ADAPTER that I use to connect pen drive or other externals disks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With stock JB Rom the adapter above worked very well: I connected a 160Gb Hard Disk Drive without problems.
With this CROMBI-kk Rom the system not mount the external memory that connect with the adapter. In Settings-Memory I may see that the USB options are enabled (and when I pull out the adapter becames disabled) but "Install SD Card" command does nothing.
Is there a solution for this issue?
Thanks in advance
PS: I found others theads in this forum but not for my ASUS Prime
FYI
On Google Play I found an App to solve this issue...
It work well and with an helper is well integrated in the system
Look for "Usb otg" on the market
I have never had that particular problem, it had always recognised and auto-mounted any attached storage :/ could be a bad flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
I just flashed Crombi-kk and I have this problem. On stock 4.1.1 OTG cable worked great. Now I it doesn't . Chainfire Stickmount didn't help either.
update1:
When I connect thumb drive to the dock it is recognized and is working, but with cable not anymore, even though the thumb drive light is blinking so it must be bug in Crombi-kk. Everything else is great.
update2:
In order for USB thumb drive to work, you cann use
1. Total Commander with USB Stick Plugin-TC., or
2. Nexus USB OTG File Manager.
The other USB OTG apps didn't work including Chainfire's Stickmount. Hope I helped someone.
I hope in the future Combi-kk version that USB OTG will be corrected including slow transfer speed. Speed transfer is maybe 2-3 times slower than on stock JB.
I'd love to find a way to add a USB Mass Storage option when connecting the Lenovo TB-8703F to PC, to make the MicroSD accessible like a USB stick or hard drive. Has anyone successfully done it? Using MTP is far from ideal for my purposes.
You mean like this? If yes, I did nothing. I don't even have the drivers installed, only what windows installs on it's own.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is MTP. The drive cannot be seen by apps that require writing to a 'drive letter' with MTP. And copying and reading files is worse since it has to cache the file being read first. And I've had heaps of instances where the latest files wouldn't be visible with MTP unless the Android device was rebooted first. MTP is a total pain (for the way I work). Only advantage to me is making some of the internal storage accessible but I save everything important to MicroSD.
I can't see why USB Mass Storage is omitted since all the budget Lenovo tablets I have had experience with have it. They cost half what this tablet does. And I can even connect 2 tablets together and share files with nothing more complex than a $1 USB OTG cable from ebay connected to a Micro USB cable when in USB Mass Storage mode. All without a spyware brain-damaging wifi sharing app. I can do so much with USB Mass Storage.
Also MTP doesn't play well with older OSs without drivers. Less of an issue now than it once was but still not fun when you need it.
I have tried UMS Enabler https://forum.xda-developers.com/android/apps-games/app-universal-mass-storage-enabler-beta-t3240097 in my desperation but didn't have much luck.
comfortable said:
And I've had heaps of instances where the latest files wouldn't be visible with MTP unless the Android device was rebooted first.
Click to expand...
Click to collapse
uhhh this is the worst! I've lost so many files in the past...
I have a Redmi Note 10 4G (on MIUI 13.0.9 / Android 12) and I would like to decrease the resolution to get better battery life and performance. But looks, there's a “virtual notch” that is stretched as the resolution is decreased via ADB (using the platforms tools on PC).
There's some way to do it without this problem, or at least remove this “notch”?
With 1080×2400 (original resolution):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With 720×1600 (decreased resolution):
I think it's strange because on the others models, like Xiaomi 11T that looks very similar, doesn't have this problem:
Update: I'm on a custom rom actually and there's no “virtual notch” after decreasing screen resolution.By the way, the rounded corners are not 'updated' properly (they seem looks bigger and not matching the actual screen size). So use this following commands on ADB to fix it:
adb shell settings put secure sysui_rounded_size 0
adb shell settings put secure sysui_rounded_content_padding 5
I can test this for you on AOSP. Tell me the command.
Samir2298 said:
I can test this for you on AOSP. Tell me the command.
Click to expand...
Click to collapse
Thank you so much! It's adb shell wm size 720x1600 and to come back to original is adb shell wm size 1080x2400
Hey I just tested on GSI 720x1600. I see no virtual notch. Everything looks ok. I don't have another phone to show you pics but took some screenshots anyway.
Samir2298 said:
Hey I just tested on GSI 720x1600. I see no virtual notch. Everything looks ok. I don't have another phone to show you pics but took some screenshots anyway.
Click to expand...
Click to collapse
Interesting... It looks that's actually just MIUI being a little annoying. Thanks! I don't think there will be any easy way to fix this, so now I'm considering using some custom rom - just waiting to pass the 168 hours to unlock the bootloader.
Anyone found I solution for doing it in miui? I did custom rom a while back and half of it didn't work so it was pain to get back on miui. Now im hesitant for custom rom
How much impact did this have on battery life?