Database Develop

[Q] Reboot needed before stuff on SD card appears?

This sounds weird - but whenever I transfer information to the SD Card it doesn't become visible until I reboot the N1. Any directory changes, new files / deleted files don't become visible until a I reboot, even though they are visible from the PC. Anyone got any ideas why?
I use the SD-Share/SD-Split app from the marketplace to allow me to use Co-Pilot Live at the same time as reading the SD card as a mounted USB device in the car.. (the file changes aren't visible from ASTRO, Bluetooth file manager or eFile file managers)
Am I doing anything wrong? Is this normal behaviour? (I use the latest enom ROM)
Graham

Your SD-share app is causing this effect, I believe.

[Bounty] $125 if someone can make me a Nookie Froyo SD image that works with 16gb

I am absolutely pulling my hair out here. I have 3 16GB sd cards - 2 16gb ridata class 6, and one patriot class 4.
No matter what I do, I cannot get any of them to work with Froyo. ONLY my 16gb cards fail - I have various other 4 and 8gb cards floating around that work 100% fine.
With this image, I can boot the first time, run the makepart.sh command (which gives a "too many cylinders on disk error), and reboot fine again. When I go to finish formatting the SD card partition using formatpart.sh, it completes the process but never reboots - it just gets stuck on the Android... text in the bottom corner of the screen.
http://forum.xda-developers.com/showthread.php?t=922324
With these images, both 6.6 and 5.9, I can boot initially just fine but the sd card is only seen as 884mb. When I expand the partition to take up the rest of the free space (about 14gb) using EASEUS partition manager, I can boot fine next time but get literally hundreds of force closes to the point where I can't do anything. I've tried everything - creating new partitions as both logical and primary, resizing existing partitions, formatting from terminal and windows 7 x64, etc, etc.
http://forum.xda-developers.com/showthread.php?t=883175
So I've had it. If someone can make me a flashable and bootable SD card image (preferably 6.6, but 5.9 works too) that simply works with the 16GB cards (so I can actually utilize the extra space) and includes the below I will paypal them $125.
-Google Apps
-Market
-Camera and Voice apps removed
-Dropbox added
-Mount/System added (if the app does not take up the full screen force close it once)
-Nook Reader
-Phone and TelephonyProvider removed
-SetupWizard renamed (Can't get it to work. Go into Setting>Accounts & sync to add gmail account after your wireless has been setup)
-Flash installed and updated
-Default Launcher removed
-Zeam added
-Button Savior
-Angry Birds
-Astro File Manager
-Gingerbread keyboard
I basically want a version of the customized Nookie, but with Angry birds, astro, and button savior instead of softkeys (I can't stand softkeys).
To clarify, it only has to work with 16GB cards to get the $125. If it can work with 4 and/or 8GB size cards too, I'll add another $50.
Thanks for looking.

$500 if someone can de-expand my snookie "wife" from 16GB to 2GB and isolate her to sit in her fixed emcc and cook me up some gingerbread. lol. and yes i have used the search function already.

Edit: I did my own research and came to this, I did not create it but I read that some people are using it on 16gb SD cards and it works perfectly. So I decided to put it here.
Updated 2/6 new version! Pandora, YouTube, MP3's all play now. Flash might work w/o choppiness now too(?) - let us know.
Installing Nookie Froyo custom Android 2.2 ROM to boot off of an SD card:
The first thing you're going to need is a micro-SD card:
*at least 2GB in size
*at least 4GB is recommended, in order to have several GB's of storage on the SD Card partition (what Android reads as actual SD card storage)
*Class 6 or 10 is preferred
*Class 4 may be fine, 2 will likely be slow
Be aware that some companies claim to be offering a higher-class card than they really are (as there's no independent third-party that monitors the Class specification). So researching the brand you're considering is recommended.
You'll also need an SD card reader
If you have an Android phone, you may also be able to use it by placing the SD in your phone, selecting Mount as USB Drive on your phone, and proceeding from there.
First, download the latest version of Nookie
Unzip the .gz file (Winrar, 7zip, etc. Should work for that) so that you have an .img file that you're working with.
If you're on a PC, you're going to want to get a program called Win32DiskImager.
If you're on a Mac or Linux machine, you'll want dd.
Connect the SD card to your computer.
For PC Users:
open Win32DiskImager, select (using the button with the dots) the image file for Nookie that you downloaded, then select the drive of your SD Card (be very careful you're choosing your SD Card drive and not another!), then choose Write Image. *After a few minutes, you're all done!
For Mac Users (instructions credit nookdevs.com)
Open a terminal window.
Find which drive the sd card is mapped to: type in the terminal this:
diskutil list
Be very careful to identify the SD card and not your hard disk. Be VERY careful.
Now unmount that drive typing this:
diskutil unmountDisk /dev/disk#
(My computer is was disk2 replace # with your number.)
The computer should say:*Unmount of all volumes on disk was successful
dd if=NameOfNookieFroYoImage of=/dev/disk# bs=1m
Again, replace # with the number of your card. Everything needed should copy right over to the card.
RUNNING NOOKIE:
Simply insert your Nookie Froyo SD card into your nook and power on. As long as your SD card is in your NOOKcolor when you power it on or reboot, it will boot into Nookie Froyo. Everything that would normally be on an Android phone or tablet's internal memory (plus what would normally be on an SD card) is all going to be on your SD (this is why we recommended a card of 4GB or more).
One of the first things you'll notice is that there aren't any Google apps installed. You'll need to do this yourself (I would have loved to include them, but there are legalities, yadda yadda...).
ADB Installation of Google Apps:
1. You'll need to have adb (Android Debug Bridge) installed on your computer. This link explains in relatively easy terms how to get this going . . .http://forum.xda-developers.com/showthread.php?t=502010
Basically, you'll want to install the Android SDK and become familiar with the location of the directory it was installed in.
If you want to make it easy, move the 'Tools' directory (inside the SDK directory) onto c:/ . . . (or whatever your main hard drive's letter is) then, to get there, you'll simply type cd c:/tools
2. Having installed the SDK for adb access to your nook, now download the google apps files, and unzip the file so that it extracts the folder called 'system' into the 'Tools' directory in the SDK folder you downloaded.
3. Now you'll open a command prompt in Windows (start menu>run>type 'cmd') and navigate to the correct folder (cd [folder directory's path]). On Mac, this would be done via Terminal.
4. Now, with your NOOKcolor connected to your computer's USB port, type the following (of course, hit enter after each line):
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push [here, enter the path to your SDK tools folder]\system system/
adb reboot
5. Now your NC will reboot. When it boots, you'll have Market, Gmail, Google Maps, and many more Google apps.
* If you're getting a "device not found" error when running adb, first, reboot your Nook and your computer and see if it changes.
If that fails, download and unzip this file, open install.exe, and follow the on-screen prompts (this will install drivers so your computer will recognize the nook).
If that doesn't work, try opening the Super User app on your nook and then issuing the commands.
If that still doesn't work, refer to the steps in this thread, repeating if necessary.
One of the first things to do:
Before you start, one of the most important things to remember with the current version of nookie is to turn the screen off/on (do this each time you boot your nook). There's some serious touchscreen lag by default, and this is the very simple solution to make it go away. Nothing fancy, just put the screen to sleep for a sec, and when you turn it back on, it'll be plenty responsive.
Click to expand...
Click to collapse
Here is a comment a user posted regarding the 16gb SD cards
I bought a class 10 16GB from Wintek, a brand I've never heard of and not only was the card unbearably slow -- so massive lag a points, it ended up corrupting itself... Anyways, I put in a 16 GB class 4 Kingston I have and not only is it faster than the supposed class 10 -- rarely any lag, I've not had any problems.
Click to expand...
Click to collapse
Source: (all credit for creating the rom)
Android Central
Edit 2: Since you also wanted to delete any signs of cell phone options, use this theme.
http://forum.xda-developers.com/showthread.php?t=944278
Hope this helps

So... since someone did end up "fixing" your problem, although not directly in response to your thread, are they going to get a nice surprise?

Chirp....Chirp....Chirp....Chirp...
(Just Kiding)

"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.

khaytsus said:
"computerpro", have you looked to see if the FAT is FAT16 or FAT32? Pretty sure a 14G FAT16 isn't going to fly.
Click to expand...
Click to collapse
It's Fat32. I'll try that solution posted above when I get home from class, but brian said he is working on an update that should work with all cards and it should be out today. What's weird is that I can even boot with a 10GB partition with 4gb unallocated space. IT's just once I get up in the 12-14gb partition size range when things start corrupting themselves. And again, what's weird is that this happens across different brand and class cards. They are not defective. I am convinced it has something to do with the too many cylinder error I get while running makepart.sh
We shall see!

[Q] Redirect files downloaded from NookColor web browser to SD Card

I used auto-nooter 3.0.0 to root my NookColor, now the browser is no longer restricted to file downloads. Now when I try to download a 16mb file from the web browser it says I don't have enough room. That's fine, but there's no menu in the browser for me to change the destination folder where these downloaded files are to be stored. Is there some settings file I can hack to redirect from the standard /media/My Files/Downloads to some other location on my SD card?
I know there are other free browsers on Android Market that I can download and use but I rather not have to go through that route.
I don't mind hacking some files to make this change. Is there any ideas?

I would also like to know if this is possible. I would like my downloads to go to the SD card instead of the internal memory. Is there a setting somewhere that I am not seeing to do this?

[Q] Cannot download files to internal SD in Mass Storage mode.

I'm running stock Android 2.2 and just rooted my phone yesterday. Since rooting my phone, I've had the following issues:
Cannot create a new folder on internal SD card ("The file '<%1 NULL:NameDest>' is too large for the destination file system") from computer while in mass storage mode (I can in media player mode)
Cannot copy/move files to internal SD card while in mass storage mode (I can in media player mode)
Cannot download from browser to phone using computer (I tried downloading an apk file from xda but it just kept trying to download.
Cannot download from mobile phone browser ("Cannot download. The content is not supported on the phone")
That's all I can think of for now, but you get the idea. I think it might have to do with the fact that I didn't unmount the internal SD card before rooting my phone (I don't think there's a way, but perhaps I rushed).
Is there any way I can fix this? Thanks in advance
Edit: It only affects the internal SD card. I put an external SD into it and it works fine.

I've been having pretty much the same issue since day one with this phone. While in Mass Storage, I cannot transfer files onto my phone. I can create/delete folders in the file tree though.
I would greatly appreciate any information you folks can come up with.

I have the same issues on a china-phone running 4.4.2 , is there any solution to this?
Also apart from these, but i think is due to the same bigger problem, i have some random issues with the gallery: it fails to load some images and it crashes.
Bluetooth transfer fails due to storage issues, yet i have some gbs free (internal or phone), and the files are just mbs.
I cannot copy some files from my phone to my pc, it keeps showing some errors (which appear to be due to FAT-FAT32 format, but in reallty i have no clue).
My phone is rooted, but it seems like i have no rights over the storage control... and that makes me real sad.
Any suggestions?

Sucore said:
I have the same issues on a china-phone running 4.4.2 , is there any solution to this?
Also apart from these, but i think is due to the same bigger problem, i have some random issues with the gallery: it fails to load some images and it crashes.
Bluetooth transfer fails due to storage issues, yet i have some gbs free (internal or phone), and the files are just mbs.
I cannot copy some files from my phone to my pc, it keeps showing some errors (which appear to be due to FAT-FAT32 format, but in reallty i have no clue).
My phone is rooted, but it seems like i have no rights over the storage control... and that makes me real sad.
Any suggestions?
Click to expand...
Click to collapse
It's hard to help/support a phone we don't know about. What device do you have exactly? Which root did you use? Also, FAT32 isn't supported by quite a few devices, I would suggest using a different format.

I have an Mpie t6s, which i believe is kinda new cause i haven't been able to find anything on the net.
I have failed to create a backup due to "task ended with error" from MTKDroidtools, and i was trying to find a rom that works. I couldn't.
So now, i have it with the rom of a similar model, mpie 909t, but the problems remain.
I have sort-of realized that the gallery issue was created because i didn't ejected the drive from My Computer (yea, it has Mass Storage, and MTP, and camera mode when i connect it to PC.
I read that 4.4.2 and mass storage are not compatible, and it came to me.
I rooted it with iRoot that was the only that worked.
I removed all the Chinese &(@$^ but i kept iRoot's Superuser because i thought that with SuperSU all the problems where returning (that was before i realized the issue with mass storage and safe remove).

BWolf56 said:
It's hard to help/support a phone we don't know about. What device do you have exactly? Which root did you use? Also, FAT32 isn't supported by quite a few devices, I would suggest using a different format.
Click to expand...
Click to collapse
So i came to realise that the internal sd is 69MB (after i repartitioned it and made 2.5gb the interal for apks), so i think this is the main problem!
Formating via windows showed me that size, at first i thought it was something wrong (everywhere else in win the size was 29 GB) but now i manage to deal with that.
Prefer that than an always crashing phone.
ExtSD to the rescue!

Oreo & SD Cards

There appears to be a problem moving files about on the SD Card when running under Oreo. It seems you can write to the card from say the camera or from the phone storage but moving or copying a file from the SD Card to another location on the SD Card doesn't work.
My mate with a different branded phone has the same issue so its not the Nokia 8, it is Oreo, anyone know of a fix?

Same issue here. Nokia TA-1004 updated to Oreo. SD Card has issues. Any files you copy to the SD card will have the file written physically, but with a read error on the destination file. The file will appear as zero bytes. But a simple restart will fix this.
Hope Nokia will fix this soon...
Edit: a restart will fix the files appearing correctly, but the issue still remains.

djunk said:
Same issue here. Nokia TA-1004 updated to Oreo. SD Card has issues. Any files you copy to the SD card will have the file written physically, but with a read error on the destination file. The file will appear as zero bytes. But a simple restart will fix this.
Hope Nokia will fix this soon...
Click to expand...
Click to collapse
I can confirm this issue as well.
Tried total Commander and solid Explorer with same result - zero byte file
BTW factory reset does nothing as I have done it straight after updating to oreo (from recovery menu)

So, there's a way.
Use the default file manager, Files app. Copying and moving works well, from Internal to External memory and within also. I found the Files app rather basic, but it does work.
No zero bytes issue.
Just clear Files' app data and cache.
Works for me.
For 3rd party apps, we should wait for an update for the apps itself. I reinstalled File Manager + and X-plore, the issue is still present for these apps.
Maybe other file managers might work.

djunk said:
So, there's a way.
Use the default file manager, Files app. Copying and moving works well, from Internal to External memory and within also. I found the Files app rather basic, but it does work.
No zero bytes issue.
Just clear Files' app data and cache.
Works for me.
For 3rd party apps, we should wait for an update for the apps itself. I reinstalled File Manager + and X-plore, the issue is still present for these apps.
Maybe other file managers might work.
Click to expand...
Click to collapse
I didn't know that the Nokia 8 comes equipped with a file manager app, is it made by Google? Can I find it on the play store please?

Yes, Nokia has its own file manager. No, its not made by Google and its not available in Playstore either.
Its called "Files" app, v8.0, because its Oreo maybe.
If you're using a 3rd party launcher, maybe it won't appear in your app list. Use the default launcher.
Or go to Settings -> Storage -> Internal Storage -> Files.
If you have an SD card, tap on the SD card in the storage settings to open the Files app.
Its integrated in the OS, can't be disabled, and I also can't find a way to extract its apk.
Hope you find it...

djunk said:
Yes, Nokia has its own file manager. No, its not made by Google and its not available in Playstore either.
Its called "Files" app, v8.0, because its Oreo maybe.
If you're using a 3rd party launcher, maybe it won't appear in your app list. Use the default launcher.
Or go to Settings -> Storage -> Internal Storage -> Files.
If you have an SD card, tap on the SD card in the storage settings to open the Files app.
Its integrated in the OS, can't be disabled, and I also can't find a way to extract its apk.
Hope you find it...
Click to expand...
Click to collapse
Thanks a lot

It isn't a Nokia problem BTW, my mate is running Oreo (although not a final release) in his Galaxy S7 Edge and it has the same issue.

djunk said:
So, there's a way.
Use the default file manager, Files app. Copying and moving works well, from Internal to External memory and within also. I found the Files app rather basic, but it does work.
Click to expand...
Click to collapse
I just tired moving 2 files from the system to the SD Card using the default file manager and both files were lost.

MrBelter said:
I just tired moving 2 files from the system to the SD Card using the default file manager and both files were lost.
Click to expand...
Click to collapse
Remove and try reading the memory card on a computer, see if your files are there.
Clean data and cache for the Files app, and try again.
Can you try with another card for a chance.
Am using a Maxell class10 16gb card.
I hope this issue isn't related to card speeds or capacity.
I didn't try other cards though.
And other file managers still has the issue.

djunk said:
Remove and try reading the memory card on a computer, see if your files are there.
Clean data and cache for the Files app, and try again.
Can you try with another card for a chance.
Am using a Maxell class10 16gb card.
I hope this issue isn't related to card speeds or capacity.
I didn't try other cards though.
And other file managers still has the issue.
Click to expand...
Click to collapse
It doesn't matter if the files are lost it was just to see if the default file explorer works correctly and it doesn't.
I am using a 64GB SanDisk Extreme Pro with 95MB/ reads and 90MB/s writes, i'd say that is a card that is up to the job. That said i don't think this is a anything to do with the cards people are using, i'd hazard a guess at Google changing how Android handles the files on an SD card in Oreo.

Well, seems we have to use the internal storage till Google makes this right...

Or the app makers work it out

At least X-plore works all right, Total Commander does have the problem as described.

No one seems to be updating any apps, i am wondering if Google borked it totally.

Well Google wouldn't care since they don't use SD cards on their devices. For me none of the 3rd party file managers work. Either we wait for Nokia to fix it or the app developers.

Also i discovered something else which is with the camera... If i choose to save the pictures on the SD when taking pictures, and press to see the photo from inside the camera app after i taken it, it wont open it.
It shows it as a small thumbnail that the photo was taken. Even if i go to the Photos to find the picture is not there. This only occurs when using the Nokia camera app and having selected to save on SD.
If i use a different camera app like the Google camera, or select from the Nokia camera app to save on the internal storage i don't have this issue.
I don't if that matters but im using a Samsung EVO Plus 64GB microSD

Paladin987 said:
Also i discovered something else which is with the camera... If i choose to save the pictures on the SD when taking pictures, and press to see the photo from inside the camera app after i taken it, it wont open it.
It shows it as a small thumbnail that the photo was taken. Even if i go to the Photos to find the picture is not there. This only occurs when using the Nokia camera app and having selected to save on SD.
If i use a different camera app like the Google camera, or select from the Nokia camera app to save on the internal storage i don't have this issue.
I don't if that matters but im using a Samsung EVO Plus 64GB microSD
Click to expand...
Click to collapse
Try clearing the Cache Data for the stock camera app. On mine it works without issues, saving to Internal or SD card. I use a 16GB card though..

djunk said:
Try clearing the Cache Data for the stock camera app. On mine it works without issues, saving to Internal or SD card. I use a 16GB card though..
Click to expand...
Click to collapse
Never crossed my mind to clear the cache, did and works now.
The weird thing is, that i talked to the support about this and they told me that the camera app doesn't have permissions to manage the SD storage so it won't work

SD card problems seem to be fixed in today's update