I've had the Nexus 5X for over a year, and purchased a USB to USB-C 64GB memory stick when I first got it, this has always worked flawlessly and been picked up in recovery, and and android versions I've run. Though recently in recovery it just shows as no free space and you can't select it, and in android in ES File Manager it constantly appears and disappears every second (in picture).
The drive works fine in my laptop with the USB-A end, I've tried a second unit and it's exactly the same so I know it's the phone. The phone charges fine and I can connect the phone to laptop with a cable and transfer files. Would OTG use different pins to charging and file transfer by cable?
Has anyone had similar? Or any ideas to try?
This is what i've got https://www.kingston.com/en/usb/personal_business/dtduo3c
{
"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"
}
Thought i'd update for completeness. I wiped everything including internal storage, and flashed latest radio / recovery / vendor / latest pure nexus + gapps. And something in that lot fixed it as it's working fine again now! :good:
loakyj said:
Thought i'd update for completeness. I wiped everything including internal storage, and flashed latest radio / recovery / vendor / latest pure nexus + gapps. And something in that lot fixed it as it's working fine again now! :good:
Click to expand...
Click to collapse
I experienced something similar recently and I think ES file explorer has something to do with it. But you did say you cleaned and wiped the phone, so could be another issue. For me I found that i had to go through a certain cleaning function in ES, or the files would be kept in a kind of Recycle Bin. Once I cleaned that out i had my space back. However, I don't have the same Type-C OTG, but that fixed my issue.
Related
So i am having a problem with my internal storage. These numbers aren't adding up and I am being told I am low on storage. Is there anyway to fix this without doing a reset? ES file explorer doesn't seem to enforce that I am low on space so i can't see the problem.
{
"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"
}
Before it completes loading, it looks like this, so the bar jumps.
Same for me.
Removing almost everything does not solve the "Internal storage is full, please delete some files." bug.
I still cannot
dowload from the Play Store
update anything
take any photo
etc
I tryed to empty every app cache but it was useless.
Try wiping your dalvik
And what ROM are you on, ICS ?
sent from your future.
If you have GPS enabled, s0ome of us have a bug where the AGPS data keeps updating continually which fills the memory. You need to go to data/gps and clear out that folder if this is your issue. You'll see a ton of .txt files there, they can be deleted without worry. I leave my GPS disabled due to this and only enable it when needed.
Thanks for the answers.
My A100 is rooted. It is running ICS build number Acer_AV041_A100_1.037.00_WW_GEN1
Unfortunately, wiping dalvik did not change anything.
Although I use GPS a lot, there is nothing in /data. The folder /data/gps doesn't even exist.
[EDIT] It looks like I'm a noob ! It was that gps log problem.
/data was empty when I looked into it with File Manager. I went into recovery mode (I had TWRP installed). Then I could see a lot of thing in /data. I did a rm *.txt in gps folder and rebooted.
Everything is OK now. Thanks b1lk1.
I guess you've read this a million times here: "Apple User switched to Android = completely lost"
This forum is fantastic, but I gotta say its SO big with so much information, I find I've spent an hour or more just trying to find the right information, and even then I feel lost.
I recently tried Slim-t0lte, but I used the wrong ROM which was the N7100 when I have a GT- N7105 device. Lost all ability to make and receive calls and worst of all I lost my 64GB MicroSD card. Photo's, music, files the lot - gone!
That was a couple of days ago and since then I've done a lot of reading and have somewhat rectified the situation.
I am now using Slim-t0lte-4.2.2.build.7.2-WEEKLY and its working great, ie. I can make and receive calls at least, and I had to go and buy a new 64GB MicroSD which set me back $70 dollars. Formatted the new SD card to Fat32 using GuiFormat and the device now see's my new 64GB drive which is great.
But here I am now with everything done and I am completely lost as to how to use this ROM. In the image below is the phone set up how I thought it would look when I loaded the ROM. But it doesn't look anything like that, so I had a play around in settings and I've got the Time, Weather up on the lock screen, but nothing else.
{
"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"
}
Also I downloaded Universal_SlimBean_theme_lockscreen_blue_bubble, Universal_SlimBean_theme_power_widgets_ics_blue, Universal_SlimBean_theme_powermenu_ics_blue and Universal_SlimBean_theme_settings_ics_blue. I installed them all through CWM but I can't find a way to load them so I can see how how they look.
My question (after all the background info above) is there a how to, a video or something which shows the features of SlimBean that a novice user like me can watch so I can begin to navigate this great looking ROM and access its features?
Thx
Has anyone tried this cable or one like it that lets you charge and use usb port at the same time and lets you use a powered hard drive? Please post a link to any that have been tested working.
Thanks
http://www.ebay.com/itm/USB-Cable-With-Host-OTG-Adapter-Cable-For-Samsung-Galaxy-Note-10-1-N8000-N8010-/321165636304?pt=US_Tablet_eReader_Chargers_Sync_Cables&hash=item4ac6f6b2d0
{
"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"
}
Hello.
As you will read here http://forum.xda-developers.com/showthread.php?t=2303902 ,it's just a question of pins connecting + somes resistors.
It must work.
I will build my own maybe tomorrow for my Note 10.1 ,then report the result.
Doesn't work :crying:
I try many things for useless, i also try to change ROM for Cyanogen 10.2 ,same result.
When i plug power supply to pin 7 & 8 ,the Tab unmount the USB host by itself.
Samsara69 said:
Doesn't work :crying:
I try many things for useless, i also try to change ROM for Cyanogen 10.2 ,same result.
When i plug power supply to pin 7 & 8 ,the Tab unmount the USB host by itself.
Click to expand...
Click to collapse
Samsara, in the post from the Tab7.0 forum, they said that the adapter would unmount and then remount the USB host. Did yours not remount the host after it unmounted it?
Hello.
They talk about Paragon HFS app, this app give you choice for mount/unmount NTFS drive only if the drive is accepted by the Tab.
In the Tab, there's no choice, it's look like no drive plugged.
My solution :good:
http://forum.xda-developers.com/showthread.php?t=2424007
Hello, I've had my 32gb since Jan 10 and I have some questions. Is this normal for an IPS display? It seems fpse won't see my 64gb USB stick. Works fine when ROMs are in internal. Is there some way to tell fpse to check external storage? Would Google play movies and ota work if I'm rooted? Came from Toshiba Thrive which is ancient now.
{
"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"
}
Sent from my SPH-L710 using Tapatalk
anyone?
Kenny301 said:
anyone?
Click to expand...
Click to collapse
Ok, so, as far as I know, there's a problem with FLO devices that can't read USB Sticks via OTG Cables.
There's 2 ways to make USB devices work:
1. BUY the app "Nexus Media Importer" from Google Play (and when I say buy I mean you can't hack it, it verifies its' licence with the server, no matter how you patch it)
OR
2. Root your device and install "StickMount" (https://play.google.com/store/apps/details?id=eu.chainfire.stickmount). It will mount your USB Drive and create a new folder in "Internal Memory/sda1/blablabla".
Hope this helped!
If it's just a matter of what dragancia sad, then it's very easy if you use StickMount. External storage gets mounted under /sdcard/usbStorage, and most apps should be able to access. I've never used fpse and can't tell you if needs files to be in a specific directory, like the Kindle app does. Nor have I ever used Nexus Media Importer.
Hi,
I have this M8 as a "testing phone" and I have changed roms time to time testing new android versions etc. In past months I have tested few roms, mainly android 11 and 10 versions. Found some things on them that didn't liked so I installed GPE MM back yesterday and them suddenly realized that camera won't work. I mean it won't start at all, it just says as in that picture. When I factory reset/wiped and installed new, not Sense, rom that whole cam app isn't even visible on app list in drawer or in desktop. But it can be found via settings/apps. And while I try to open it for example via gallery it says something like "can't connect to camera".
Then I wiped again and installed back that original MM rom and that camera icon exists again but it won't start but says still like in picture.
So do I have a situation that some camera chip etc or mainboard has suddenly failed without any reason or could this be software problem anymore since that cam won't do anything or even start with any rom?
I haven't dropped the phone or opened for a long time, I haven't even taken much pics with that m8 so it's quite weird thing. I have done factory reset while changing the rom and sometimes wiped cache, dalvik/art cache and data partitions. Twrp version is 3.3.1-3 it matters.
{
"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"
}
Try installing the camera application itself, this is how I got the camera to work