yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] xz3c:
Hey! I've got the exact same issue. My Z3C is rooted, and I'm running Lollipop 5.0.2. If I reboot my phone, it acts just as if there was no SD-card inserted. And just like you, I cannot manually "mount" it, I need to take it out and then reinsert it again.

And just like you, I have searched the web far and wide for a solution but nothing has helped.

Number 1 doesn't work.

Number 2 doesn't work.

as for number 3, I need to ask a question about this one: if I would use PC Companion to "repair" the firmware, as you suggest; would this really work when the phone is rooted?

I hope there's someone out there who might have an idea about a solution for this..
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Geeks Empire:
yup but you will lose ur root access by installing fresh firmware by Repairing option in PCC

:good:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] xz3c:
Yeah Ok, thanks. So that's really not an option then, because I would really like to keep root.

Now, a question for OP:

What firmware, exactly, are you using on your phone? I mean, which version and from where is the FTF-file? I'm wondering if the firmware version and / or region could be the cause of this problem... trying to narrow it down here...
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Rafaru:
Hello , did you manage to solve this issue please ??? I have the same problem after updting my Z1C to lollipop , I used Generric DE pre-root with dual recover , phone only mounts SD if taken out and reinserted but if reboot it does not show althought I can acces through root browser

Thanks
[Xperia Z3 Compact Q&A, Help & Troubleshooting] grockstar:
Exactly the same issue here. After a reboot, the SD card doesn't show up in Settings->Storage or in MTP sessions (nor - I think - in apps such as Album/Music).

But it is always fully accessible from the file system, e.g. using Root Browser/ES.

The card is correctly recognised when I remove and re-insert it.

It's not a great problem as I try not to reboot my phone very often. For reference I'm using a rooted Russian .726. FW.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Sadman Khan:
Funny how rooted phones are facing this
[Xperia Z3 Compact Q&A, Help & Troubleshooting] chris5s:
Same issue here, using rooted .28 LL FW.

Peace.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Rafaru:
The main problem to me is that i can not use recovery , i changed to italian pre rooted and samevissue as with german
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Revontheus:
I suggest downgrading to .93 Firmware ( KK ) then flashing Global .28 ( Lollipop ) firmware using Flashtool.

But it's highly unlikely it would be a software problem as most users don't experience this but are also rooted with Locked bootloaders. Maybe its the SD Card?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Rafaru:
Hi , i have a z1 compact , i had the same sd with kk and no issue , i have tried 3 different lollipops , all of them rooted and sam issue on all , i have downgraded and no problem at all , it only happens in lollipop , also sd works on other devices , must be a software problem , maybe becauss rooted , i do not know
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Revontheus:
I flashed a pre-rooted Lollipop made with PRF Creator via Recovery coming from FW .93 ( kk ) and no problem on my end It must be a software issue on some Kitkat releases
[Xperia Z3 Compact Q&A, Help & Troubleshooting] luizlee86:
What's the sdcard brand you are using?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Rafaru:
Hi , I have 2 , I was using a new samsung evo 32gb and thought it was damaged and bought a sandisk 32gb , both same issue and both work on other devices also on mine with kk , issue only happens in lollipop
[Xperia Z3 Compact Q&A, Help & Troubleshooting] luizlee86:
Both are the same class? It may look like a stupid question... but I had another problem and the issue was the brand. Maybe the class could be a problem?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Rafaru:
Samsung micro SDHC evo 32 gb class 10 and SanDisk Ultra micro SDHC 32gb class 10 , the only issue is they do not ppear as mounted nor you can see them on pc unless you take them out and insert again , but both play the music and i can see the pictures on them but as they dissapear when you reboot the phone I can not use recovery , I can even with root browser I can see files on them
[Xperia Z3 Compact Q&A, Help & Troubleshooting] cheahcl:
Oops forgot to update this thread.

Anyways I gave up looking for solutions until the phone refused to sleep AT ALL. I went ahead and reflashed KitKat and went through the whole procedure again.

The problem magically disappeared and has been fine ever since. Still rooted and lollipop.:good:
[Xperia Z3 Compact Q&A, Help & Troubleshooting] bossarts:
Exact same probleme here with my rooted z3 compact .726 and 64GB microSD card.

I replaced by new card, reformat many times, still same situation.

Card is always visible in totalcommander but not in the system.

It happen yesterday when i started the camera app for taking a picture. It worked for many weeks before without problem. Strange! [emoji43]
[Xperia Z3 Compact Q&A, Help & Troubleshooting] GeoI777:
To everyone who is still having this problem, I suggest flashing the newest NUT recovery 2.8.15, the installer version, since probablly you can't acces recovery. I've been struggling with this SD card issue myself until yesterday, when I tried the new recovery. The card is properly recognized now after reboot, recovery working normal.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Silverhydra:
It has fixed my z2 rooted with king root.

Thank you very much!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Silverhydra:
After a few days, the problem has occurred again :(
[Xperia Z3 Compact Q&A, Help & Troubleshooting] GeoI777:
Hmm... Sorry to hear that. Maybe the next recovery vers. will fix the problem for your phone too. My Z3C was having this issue and besides the recovery, I tried everything I could find to fix it. Since only upgrading the recovery worked, I suspect it was the problem. Wait for a new one and good luck!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] DimitarPavlov:
Some problem here.

By now I was using 2GB Kingston - I bought 32MB Kingston - nothing. The card is visible - but cannot copy anything on it.

Full FAT32 format it under windows - doesnt help. I mean under WIndows it is working fine, I try it on one old HTC - working - but on my brand new Xperia Z3 for 500 quid - not working :(

Very disappointed
[Xperia Z3 Compact Q&A, Help & Troubleshooting] kailly:
Same problem here.

Are there any news on this topic?

It's the year 2015 and we are not able to mount a SD card *omg*

I really need that extra space of my sd card. Is downgrading to KK an option?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] evildog1:
my phone appear as damaged SDcard and asj me to reformat it. please help. my SDcard is 2 days old
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Norup58:
Not having the issue myself ... but maybe something to try from this thread: http://xdaforums.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
[Xperia Z3 Compact Q&A, Help & Troubleshooting] evildog1:
i already solved the problem. Open SuperSU app -> settings and disable "Mount namespace separation"
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Twenga Dev.:
Hoi, I have the same plrobleem, AND i doe the same evertime on my rooted Z3
[Xperia Z3 Compact Q&A, Help & Troubleshooting] iamhari1234:
I had the same problem. what I tried, according to this http://xdaforums.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749 was to reinstall the recoveries by installer mode. And it was solved.
[AT&T Samsung Galaxy S 5] Trilback:
I have a friend who has a At&t Galaxy S5. He updated to lolipop and gets blocks on his lock screen, any ideas??
[AT&T Samsung Galaxy S 5] Waiting4MyAndroid:
Have him wipe cache from stock recovery. If that does not fix it, then do a factory data reset.
[T-Mobile Samsung Galaxy S II SGH-T989] R77:
I locate the network I sign in but it gives an error

Got the error: Server Error

Connection refused

I even reverted my ROM to it's previous state but no luck.

I used to connect just fine I even asked others and they said they have no problems.

I guess its my phone that has the problem what should I do?
[Android Q&A, Help & Troubleshooting] vbrennan:
Hi

Im new and cant seem to find anything, Anyone know a good app or software to tell me if my phone is being spy on? like if my x wife put something on it or my messages being forward?

Thnaks

Vince
[Android Q&A, Help & Troubleshooting] vbrennan:
Anyone??
[Android Q&A, Help & Troubleshooting] Pareshratan:
Interesting!!!!!
[Android Q&A, Help & Troubleshooting] jerbear294:
Android apps can't hide themselves the way you describe, but as a precaution you could install Clean Master and CM Security.
[Samsung Gear VR] shadowcliffs:
I bought Gear VR for Note 4 based on positive review, but after using it for two nights, I decide to send it back due to low resolution. Here's my illustration of how resolution is archived and my thought on it:

Movie watching experience: Low resolution ruins it. It's bad to watch anything on a 480p screen at a size of 200". Plus No DTS/AC3 support, no smb support in Oculus cinema.

Kodi supports DTS or AC3, but it also reveals that the field of view from Gear VR only covers part of Note 4's screen. See my illustration in attachment. The header, footer as well as 4 corners are not covered, which means that only central part of a movie is viewable.

Ideally, 720p (1280x720) resolution for each eye can be achieved from Note 4's 2560x1440 screen if the rectangle of half screen inscribed in the the field of view like some cardboard does. But the way Samsung's implementation of it's Gear VR makes it unable to fully take advantage of Note 4's screen. The best movie resolution that Gear VR can archive is 972x546. I understand that Samsung's take is good for VR for there is no unilluminated area within it's field of view.

I wish Samsung would come up with a new product that allow the rectangle of half screen inscribed in the field of view instead of the other way around. I think this can be archived by another set of lenes with less multiply factors than current ones. Even at 720p, the screen doesn't need to be 200". 150" would suits the pixel better.

When it comes to VR, Samsung Gear VR also suffers from low resolution. Plus 360 degree video makes me dizzy. I downloaded and watched almost all 360 degree video from youtube but I'm not impressed enough. The people figures are larger than real life. Everyone looks like giants in these videos. Among videos, I prefer those taken from a steady position. First person action view just makes me dizzy. I think it's due to my brain can't process it when the vr scene is moving around but my head is not.

360 degree picture is quite a pleasure to view though.
[Samsung Gear VR] anurajnr:
Sold mine to a colleague due to the exact same reasons
[Samsung Gear VR] Toss3:
Not questioning the validity pic you put up, but can I ask how you came to the conclusion that it only uses 972x546 pixels of the screen? Is it official information, or did you measure it somehow?
[Samsung Gear VR] shadowcliffs:
That's based on my calculation given my understanding of how it works (as illustrated) is correct. Samsung claims the resolution for each eye is 1440x1280, which is misleading IMO. Same reason as explained in the illustration.
[Samsung Gear VR] Toss3:
Just put my N4 in my Gear VR holding my thumb to the proximity sensor, so that I could see observe the screen when connected and they are not using a completely square image - it looks more like this (except there's a gap in the middle):

It also doesn't the entire width available, but it looks like it's using more than what you have in your picture. The gap between the images is about 4mm and the gap between the image and the sides is about half that (2mm). The top and bottom gaps are about 5mm. So it's definitely using more than 720 pixels for the height, but less than 1280 pixels for the width.

EDIT: I measured it using a tape measure (not any exact numbers, but more accurate than those I came up with).

So based on these measurements the screen would use about 1190 pixels at its widest point, and 1240 pixels at its highest.
[Samsung Gear VR] Nickoz:
The graph shows the best scenario, where movie screen fills your entire FOV. But this is not comfortable for most viewers, and you are likely to "sit back" a little. Since you're looking through the same matrix of pixels, you are then effectively losing screen resolution, going somewhere to 480p like OP mentioned.

What's also sad, when we reach the Holy Grail of 4K (with Note 5), the movie screen would still be only 1460x820.

If you want best experience with 2D HD content, you're better off moving your chair closer to a TV than strapping Gear onto your head.
[Samsung Gear VR] Toss3:
Actually just tried to measure the screen in the cinema mode, and came up with ≈ 45mm. The screen width is 125mm, which means that half that would be 62,5mm, which would give us an approximate horizontal resolution of 45/62,5*1280 = 921pixels. Pretty much explains everything right there. Even with a 4k screen the horizontal resolution in a comfortable mode would only be 1382 px.

The screen height (screen is not a perfect rectangle) at its highest point is ≈25mm. So with a screen height of 70mm that gives us a vertical resolution of 25/70*1440≈514px.

So based on my measurements the resolution you get is pretty much 921x514 (screen is not a perfect rectangle) at the widest and highest parts.
[Samsung Gear VR] shadowcliffs:
When it comes to watching movies, the screen will be cropped to the aspect ratio of close to 1.78:1, that's how I estimated it at an effective resolution of 972x546 (the biggest 1.78:1 rectangle inscribed in the FOV circle).

You just showed that the actual FOV is not exactly a circle. Now the question is, is the actual FOV inscribed in the theoretical FOV, or the other way around. I guess a way to find out is to look through gear vr at a picture with measurement markers.

And again, in best scenario the effective movie-watching-resolution based on Note 4 screen is 720p (1280x720) considering the aspect ratio of 1.78:1. This best scenario is achieved when the rectangle of half screen (1440*1280) inscribed in the FOV. This is the case in my Chinese version of Google cardboard where the movie screen is smaller (equal to 150" from 10 feet away, more or less) and the pixel is less obvious. So the difference of this Chinese version of Google cardboard vs Samsung Gear VR is like 150" 720p screen vs 200" 5xxp screen.

Not sure about the original Google cardboard for I don't have one.
[Samsung Gear VR] shadowcliffs:
In theory (if my theory is not faulted), to be 1080p movie ready for each eye, the width of the half screen needs to be 1920, which equal to 3840 in whole screen. The height is already more than enough (1440 available, 1080 needed). So the resolution needed from the phone screen is 3840x(1080 to 2160, the former may make the phone too long, but who knows right? The latter will keep the same aspect ratio as Note 4).
[Samsung Gear VR] shadowcliffs:
Can the lenses on gear vr be replaced so that it will make the screen through it smaller, for watching movie's sake?
[Samsung Gear VR] hashcheck:
I love mine as a great start to mobile VR and i have watch lots of films via oculus cinema. Can't wait for note 5 and new gear vr but perfect start samsung
[Samsung Gear VR] shadowcliffs:
Here I'm mainly talking about movie-watching ecperience. The experience is ymmv. For a guy used to watch movie on a 120" projector screen, or a 60" 3D Samsung TV, gear vr experience is unbearable, while Chinese version Google cardboard is very impressive except for it's build is not goog enough.
[Samsung Gear VR] Toss3:
I have a 120" movie screen (only 1080p though), and I personally don't find the experience "unbearable", just not as good. Still think it beats watching the movie on just your phone though or laptop.
[Samsung Gear VR] hashcheck:
Totally agree Toss3 :)
[Samsung Gear VR] shadowcliffs:
Right, I realized that unbearable is too much of a word. I meant to say that I still prefer to watch movies on 120" projector screen or 60" LED TV over current gear vr. It's a pity because gear vr would have done better. I'm impressed with it's build and the quality of lens, but the lens is not of the correct multiply factor for watching movies.
[Samsung Gear VR] hashcheck:
The gearvr resolution actually gets better overtime as you start not noticing the screen door effect the more you use it. Sure it's not perfect but heaps better then the oculus rift dk2. I'm can't wait for note 5 version
[Samsung Gear VR] rushless:
Average viewable res is 540p. Void mode shows more content at about 640p since no VR graphics (depending on video format).

I prefer Void due to more of the video res shown, can view laying down and at least 30% more battery life.
[Moto G Android Development] MetalPhoenix45:
This thread is for people who didn't come across my kernel...

http://xdaforums.com/moto-g/orig-development/kernel-smoothgkernel-v1-t3080408
[Moto G Android Development] Niropa:
No need for 2 threads though
[Moto G Android Development] MetalPhoenix45:
Sorry...

My work: SmoothGKernel for the Moto G, and remember always hit the thanks button if anyone helped.
[Moto G Android Development] gregbradley:
There is absolutely no need to create another thread in case anyone 'misses' your original thread. Even more so to create a non-dev thread in the dev section

Thread closed
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] sfgsr1:
Hello,

I just received a phone that I purchased off Swappa, the seller stated that the phone was not rooted and when I turned it on it had a safe strap screen before it booted into a factory reset of 4.4.2. I want to know how I can remove safestrap without bricking my phone. I have no idea where to start. It's safestrap version 3.72. If i need to flash and reinstall android I would like to update to 5.0.

Thank you all for the help
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] norbarb:
Here : http://xdaforums.com/showthread.php?p=59666956

Or here : http://xdaforums.com/showthread.php?p=59818274

Notes from Note 4
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] sfgsr1:
Thank you for the quick response, would I use the stock rom or the rooted rom? I want to return to 100% stock.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] norbarb:
If you want to be 100% stock use stock rom not rooted.
[Upgrading, Modifying and Unlocking] TireIron431:
Hey guy's,

Hopefully This is in the right place. Please assist in anyway you possibly can. This phone is not a brick, but it might aswell be. I have tried literally every kind of reset unbrick guide I can find for the past 2 months, and nothing works.

From what I can tell it is a driver issue, but even installing the meta mediatek preloader, and drivers does not seem to work. I have tried a fresh install of windows 8.1, windows 7, and xp. nothing works. I can not install the adb drivers for this device, because the phone will not even boot into recover. Recovery is corupted or something. I do have an mtkdroidtools backup, but can not flash it with sp flash because it always gives the error "THIS IS A SECURE BASEBAND CHIP PLEASE LOAD AUTHENICATION FILE". I've worked with kirito9 which was a big help in understanding a few things, but we could not get it sorted. I will stop talking now, and post something useful.

BTW:mobile upgrade tool s does not work either. I get terminal read failure.

As of now im on windows 8.1 with drivers installed. I have posted a couple of videos to show whats going on. Hopefully they will help. I can post some logs, but I honestly dont know which ones you would want, I have a lot of them, and have tried so many things I dont know where to begin again. In the zip file there is 2 videos, and the original mtk.log.

I forgot to mention that, this all started when I wanted to root, and install a custom recovery. I believe I used the guide on here but cant remember seeing as it was a while ago. Also the phone does not vibrate at all. Like I said I have a backup, but I dont remember much about it I dont know how reliable it is, and if I read back with sp flash or not. I believe I had to right? idk. thanks in advance.

https://drive.google.com/file/d/0B_DyVUIoGhqBSXlhbkNhdVNCR1k/view?usp=sharing
[Upgrading, Modifying and Unlocking] TireIron431:
Wow I cant believe nobody has run into this problem. That or you guy's are just busy which I totally understand.. I'm just really frustrated. I think I am going to try to return it to t-mobile. You gotta know when your defeated, and this is it. This phone has been a nightmare.... I just hate giving up. I broke it, and I wanted to fix it.

Anyway if this was in the wrong lace to post please let me know. thanks.
[Upgrading, Modifying and Unlocking] TireIron431:
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.

Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
[Upgrading, Modifying and Unlocking] heavy_metal_man:
Hey man, I cant really help with unbricking it. Mediatek chips are not my strong point but i just wanted to say logically if the recovery is corrputed and the rom is corrupted and the bootloader is not playing ball then unless the chips have a write counter/modification check then you should be okay I reckon.

Good luck though :)
[Upgrading, Modifying and Unlocking] TireIron431:
I still have it because I wanted to at least make it boot ok, but to no avail. I got the replacement and made a good back up with mtk droid, but I still get the error.

The phone is an Identical copy of my last one, and still no go. I even tried to flash it with the new phone, I get the same error. so I guess im a monkey, and cant do it right. If it's doing the same thing with the new phone as it is with the bricked one, than its me right?

I did notice that I cant create a scatter file with the create scatter button(its greyed out) I can only make one through the firmware.info.

This is the phone info from both phones.

Hardware : MT6581

Model : ALCATEL ONE TOUCH 4037T

Build number : ALPS.KK1.MP1.V2.10

Build date UTC : 20140918-073410

Android v : 4.4.2

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/09/18 15:26

Kernel v : 3.4.67 (android-bld@aclgcl-ubnt164) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 8 10:47:59 CST 2014

Uboot build v : ----- should be root shell

LCD Driver IC : 0-nt35512_dsi_vdo_tdt_lcm_drv

From what I have read this is actually a 6572 chip. Is this correct? I was just thinking that maybe droid tools wasn't reading it right, or backing it up right. Droid tools creats a 6582 scatter file, but my phone says 6581, and I saw 6572. Which one is it? I cant find or make a 6581, so I do not know what to do. I have tried both phones with all of the different drivers, with the different scatters, and I always get error 5000 secure baseband chip.
[Upgrading, Modifying and Unlocking] danymt87:
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.

I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.

Thanks from the start.