I have VEGAn-Tab 5.1.1 (Froyo ROM) installed and when playing (or accessing) files on a microSD card it mysteriously deletes all the files in the folder. Is there another Froyo custom ROM (I need true hardware acceleration) that DOES NOT have the deleting file problem like VEGAn-Tab?
Thanks in advance
DiGiTY said:
I have VEGAn-Tab 5.1.1 (Froyo ROM) installed and when playing (or accessing) files on a microSD card it mysteriously deletes all the files in the folder. Is there another Froyo custom ROM (I need true hardware acceleration) that DOES NOT have the deleting file problem like VEGAn-Tab?
Thanks in advance
Click to expand...
Click to collapse
Yes, ALL OF THEM, as long as you have an empty file called .nomedia in the root of the card...(use notepad++ to create a file don't enter any text into it, and save it to the SD card as .nomedia)
google "Gtablet for Dummies" And read everythign you can, he cover's just about everything you need to know about our finicky device.
edit: you can also use root explorer to creat the file directly on the device
you gotta be ishing me! that's the fix!?!!
Any ideas why .nomedia is needed?
DiGiTY said:
you gotta be ishing me! that's the fix!?!!
Click to expand...
Click to collapse
always has been...has always worked fine for me on BC, Vegantab 5.1.1, Calk/Clem. Of course, I took it a step farther and put the file in the root, and evey subdirectory as well...It takes up no space, so why the hell not, right?
thank goodness its just video files
DiGiTY said:
thank goodness its just video files
Click to expand...
Click to collapse
oh, it will delete audio files too...not all the time, but it's possible
Related
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
irus said:
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
Click to expand...
Click to collapse
You could try using a provxml file operation instead? Not sure if initflashfiles generally is happy about copying from a removable storage device such as the sd slot (just a guess), since in your Athena it is a fixed disk it may behave differently??
Another thing you could try is to do the copy operation as a stage of the customization process, use an xml file in there?? Perhaps the SD bus driver is not loaded until after initflashfiles has completed since really it has to run that before alot of other operations on first boot?
irus said:
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
Click to expand...
Click to collapse
I'd use CPY1/CPY2 in a UC script
Code:
CPY1:\storage card\pim.vol
CPY2:\pim.vol
CPY1:\storage card\eT9Rudb.Rdb
CPY2:\Windows\eT9Rudb.Rdb
CPY1:\storage card\eT9Cdb.Cdb
CPY2:\Windows\eT9Cdb.Cdb
mrvanx said:
You could try using a provxml file operation instead? Not sure if initflashfiles generally is happy about copying from a removable storage device such as the sd slot (just a guess), since in your Athena it is a fixed disk it may behave differently??
Another thing you could try is to do the copy operation as a stage of the customization process, use an xml file in there?? Perhaps the SD bus driver is not loaded until after initflashfiles has completed since really it has to run that before alot of other operations on first boot?
Click to expand...
Click to collapse
i will try this if all else fails but i would like it to be from the initflashfiles.dat but what you say makes sense.... thanks
andret said:
I'd use CPY1/CPY2 in a UC script
Code:
CPY1:\storage card\pim.vol
CPY2:\pim.vol
CPY1:\storage card\eT9Rudb.Rdb
CPY2:\Windows\eT9Rudb.Rdb
CPY1:\storage card\eT9Cdb.Cdb
CPY2:\Windows\eT9Cdb.Cdb
Click to expand...
Click to collapse
i thought about doing this but i read somewhere that sdautorun does not like spaces in the files path.... thanks for the info
ok so i tried using the cpy1/cpy2 and it actully worked however it did not copy over the pim.vol so i tried to copy it over manually and it let me but after i did that i could no longer press on contacts, calender, or get to the phone pad any thoughts?
I think you'll probably need to close down any process actively using the pim database before copying it over, it's probably open when you're overwriting it and getting corrupted..
Da_G said:
I think you'll probably need to close down any process actively using the pim database before copying it over, it's probably open when you're overwriting it and getting corrupted..
Click to expand...
Click to collapse
i changed the reg values to my documents then changed them back, i am kindof thinking that htc may have set this up a little differently on the TP which is why i am having so much trouble but thats is only my guess
ok so im thinking part of the problem is that the pim.vol file is working with some other file for contacts, here is why: i copied the pim.vol file from my rom renamed it pim.vol_ put it into my rom and flashed it, of course i put Directory("\Windows"):-File("pim.vol","\Windows\pim.vol_") into the initflashfiles.dat file and still not contacts. so i have no idea why this does not work any thoughts. thanks
This Avatar.apk is for those who have upgraded to Froyo with an unofficial build that doesn't include a working Avatar app, but desire a working Avatar.apk that launches the DRM protected copy of the movie included with the phone.
Some caveats/disclaimers: I don't own a Vibrant; I have an i9000 Galaxy S and a Nexus One. I don't plan on providing much support for this, but it shouldn't need it. All the usual "I am not responsible for damage to your phone" disclaimers apply; if you don't know how to use adb and don't have root, go find out how in the appropriate FAQs.
Back story: My friend owns a Vibrant and hated it (slow/laggy). I thought upgrading it to a Froyo build would make him happy, so I did with Team Whiskey's Onyx version (very slick, better than the best ROM I have on i9000 IMHO). He was disappointed that the Avatar shortcut/app on the desktop disappeared, so I pulled the apk from a 2.1 build and pushed it to the phone, but it didn't work.
A little investigation showed that the apk file has an xml resource that is hard-coded to look for the encrypted/drm copy of the movie in the path "/sdcard/sd/movie/AVATAR.dcf", but the Froyo builds mount the external card as "/sdcard/external_sd/" so the app doesn't work.
All I did here was edit the xml file to the correct path, repacked the apk, signed it, pushed it to the phone with adb to /system/app. The apk was then available to add as a desktop shortcut again, and it opens the movie as expected.
The file won't install like a regular apk (at least it wouldn't for me), it must be pushed to /system/app to work - use this command:
adb push <your path>/Avatar.apk /system/app
You could also probably download the apk and copy it over to /system/app with Root Explorer or any other file manager that lets you write to /system/app.
I have only tested this with Team Whiskey's Onyx build and by pushing via adb. I can't test any other ROM since I don't own a Vibrant.
I know a lot of people consider the Avatar.apk to be bloatware and ask how to remove it, but I see a lot of people asking for it back because it's convenient and a great show-off feature on the phone for non-Galaxy S owners.
Additional disclaimers: I did quite a bit of searching here on XDA for an apk that took this approach and didn't find one. If it's already out there, I apologize for this post and can link to it. All I found was an apk that requires you to have a non-encrypted mp4 copy of the movie. I also found a lot of bad information about you could use the original 2.1 version if you just de-odexed it and other stuff like that. Again, this will ONLY work on a 2.2 Froyo ROM because of the change in mounting path of the external sdcard.
credit/thanks to Brut.all for his apktool and to jessetbenton for his Mac-friendly android auto signing applet.
Edit: I only modded the English language part of the apk, it may not work properly if you're using a different language.
Here's the apk, enjoy:
Wow, that first post is a lot of words for such a simple posted apk! LOL. I just wanted to make sure to cover all the bases for any criticisms I might be getting.
Thanks dude, I kept trying to install the old avatar.apk, and when I tried opening avatar, it kept giving me "file not found"
Oh, btw works on Eugene's Macnut R12
You could also just make a folder named "sd" on the sd card, and move the Movie folder there. Works just fine for me.
pablizzo said:
You could also just make a folder named "sd" on the sd card, and move the Movie folder there. Works just fine for me.
Click to expand...
Click to collapse
Yes, but then you lose that 1gb of space on your internal sdcard.
I'd have gone for a symlink approach instead, but the internal card is plain old FAT32 and doesn't support them.
Or just use the stock froyo Avatar.apk? Lol. Worked for me...
distortedloop said:
Yes, but then you lose that 1gb of space on your internal sdcard.
I'd have gone for a symlink approach instead, but the internal card is plain old FAT32 and doesn't support them.
Click to expand...
Click to collapse
1 out of ~13gb is fine with me
rk0 said:
Or just use the stock froyo Avatar.apk? Lol. Worked for me...
Click to expand...
Click to collapse
Ah, that's good. Where'd you get it? I thought there wasn't a Vibrant specific Froyo yet - all I see on samfirmware.com are 2.1 builds. Like I said, I'm not a Vibrant owner, so don't really keep up with its developments.
Thanks for posting that.
pablizzo said:
1 out of ~13gb is fine with me
Click to expand...
Click to collapse
Yeah, to each his own.
My internal 16gb on the i9000 is almost full (nandroid backups, media, etc), and I have an external 16gb that's more than half full. I prefer to keep large media files on the external, obviously YMMV.
Glad you had a solution that works for you.
Nice thanks
Been looking all over this...thanks
Sent from my XDA app cuz I'm stalking your mom....
distortedloop said:
Ah, that's good. Where'd you get it? I thought there wasn't a Vibrant specific Froyo yet - all I see on samfirmware.com are 2.1 builds. Like I said, I'm not a Vibrant owner, so don't really keep up with its developments.
Thanks for posting that.
Click to expand...
Click to collapse
Deodexed JK2 Rom.
rk0 said:
Deodexed JK2 Rom.
Click to expand...
Click to collapse
Thanks for the response.
I wish someone had answered any one of the dozens of posts I read where people were complaining or asking about this with that info. Would have saved me the trouble here.
Actually, it worked out well for me anyways. I have a couple of apps with the same problem where I really want to force them to use the external card instead of the internal. Now I've learned an approach I can use to "fix" or mod those apps. I wish app developers would let you specify a preferred working directory - hard coded paths aren't usually a good idea in my opinion.
At any rate, based on the number of views of the thread, and over 140 downloads between my version and yours, seems like a lot of people didn't know about this, and we've given them a working solution. That's a good thing in my opinion.
can u make this work from terminal?
Please help me to get Avatar working !
Iam on Darky's 10.2 ROM(GB 2.3.4), bullet kernel & KB5 modem.
and the movie is at the same folder structure since, my phone came stock.
I tried:
1.) I cleared drm content and drm protected content & restarted my phone two times- then downloaded the app from http://forum.xda-developers.com/showthread.php?t=774078 but it won't install.
2.) I used the Android customisation suite from http://forum.xda-developers.com/showthread.php?t=894794 and created a zip with just the avatar.apk , cleaned dalvik cache, and the installed the zip from CWM, still the application just clicked, but no response/error message whatsoever.
3.) I downloaded a terminal emulator & tried to push the apk from this thread and I get adb:not found.
Please guide me, what needs to be done, as I haven't seen the movie [email protected]!
Great work I know this has been a huge issue for many many people ...I no longer have avatar on my phone but I sure missed the launcher at one time back when I first flashed my phone
Shortbus-Driver said:
Great work I know this has been a huge issue for many many people ...I no longer have avatar on my phone but I sure missed the launcher at one time back when I first flashed my phone
Click to expand...
Click to collapse
Buddy, I haven't been able to get it working, thru any of these methods!
I guess, I might have been doing something wrong in ADB Push. But I even tried with a Root File Explorer and replacing the Default Application that i had flashed using zip generated by Android Customization Tool(ACS) , with one provided in the two links(one of them, gives application not installed,probably the bigger in size one, and so installed the other one, thereby replacing the default that I talked above). but for no good.
Avatar, still doesn't work. Please help, guys!!
We have done the internal GPS hardware mods and want to see if we can activate the GPS module. We know we need to replace the default libgps.so with the Adam version. (obtained from http://forum.xda-developers.com/showpost.php?p=14111386&postcount=207 )
We have VEGAN-Tab installed with Super User and Root Explorer installed.
When we try to copy and paste the necessary libgps.so from the external SD card to over write /replace the default one located in system/lib we get a warning saying the file is read only. Attempts to change the permissions of the original with Root Explorer fail.
Are we noobs to think that the original file can be replaced with simple cut and paste actions?
Are we missing some basic step?
TIA
Gwyn
gwynethgh said:
Are we noobs to think that the original file can be replaced with simple cut and paste actions?
Are we missing some basic step?
Click to expand...
Click to collapse
Flash the new Froyo version I just added.
rajeevvp said:
Flash the new Froyo version I just added.
Click to expand...
Click to collapse
Thanx so much. We will try this soon.
Neutrino is my first custom ROM, and I love it!
I'd really like to enable TTS, and I'm not sure what I need to do. There was a multiupload link for the languages / tts .zip in the Neutrino thread, but it is now down. I see that people have had issues with it - although I understand that they've resolved it manually by copying over various files from CM7.
I'm at a loss, however, of where to obtain these files or which files are needed specifically.
I'd really like to get this done ASAP as I'm going on a road trip tomorrow, and really need my GPS functional! Does anyone have a .zip to flash to make this work, or is anyone able to me a rundown of what files to copy over?
Thank you so much!
- Andy
P.S. This would be posted in the Neutrino thread except as I am new XDA won't let me post in the Develpment Forum :-/
- Andy
For some reason he doesn't have it posted anymore, I have an early test one he made for me that I will post for you later(I use it still)
sent from my Atrix via XDA premium
Notorious544d responded, telling me what files I needed to copy over
But, what you should do is download CM7 and copy the following files in their respective folders:
/system/app --> PicoTTS.apk, ttsservice.apk
/system/lib --> libttspico.so, libttssynthproxy.so
/system/tts --> Copy whole TTS folder and place in system and set 644 (rw-r--r--) permissions to be safe.
Click to expand...
Click to collapse
The only thing is I don't know how to copy these over exactly. Where do I put them / how do I put them? There's no system folder on the SD card, so I take it I have to flash them? How do I do that exactly?
Nevermind - I figured out how to push the files up using adb after remounting as root
TTS works fine now!
phnord said:
Notorious544d responded, telling me what files I needed to copy over
The only thing is I don't know how to copy these over exactly. Where do I put them / how do I put them? There's no system folder on the SD card, so I take it I have to flash them? How do I do that exactly?
Click to expand...
Click to collapse
you would use ROOT explorer to do this look at the folders (outside the sdcard ) for the /system folder
Sent from my MB860 using Tapatalk
So I repartitioned my media and storage drives yesterday, and although I did have a few problems (post #156-158) I finally managed to repartition and proceeded mounting the drives in 1.4.1 rooted B&N. Also checked if they worked via usb to computer which they did. I then decided that I wanted to try cm7 today and installed it flawlessly. Only problem is that now my newly resized 10GB internal media partition don't show up. So tried installing the;
[CM7][GB] Soft-mod RibbonICS ROM by veronica, but still no change.
In the storage settings i've tried to mount the
Additional storage/mnt/sdcard/_internalSD but doesen't work and thats probably also just the folder I created myself as instructed in the soft-mod.
So yeah I'm wondering if I can only use the extended media part in stock rooted B&N or if its got to do with the problems I had with the process. Or mayb I just need to mount the media drive somewhere?
Please help
Went into adb-shell in CWM and checked via the p command if the media drive was there which is was
(looked like this: 10 1611MB 11.6GB 9989MB fat32 media msftres)...so it really should work.....shouldn't it?
Edit: actually the above is not entirely correct: I have found my media partition in the file browser now but its just not really accessible it seems. Is it just not mounted or what?
Included in the soft-mod for cm7 is also an application called multi-mount sd lite which should help with this but it force-closes on me even after i fix permissions need help with this..
nook tablet cm7 can not access internall sd
Hi
I loaded cm7 onto my nook tablet 16g internal SD using your latest Zip and it worked like a charm. Thank everybody.
only problem I have is that I can't access the internal SD from my windows computer. It accesses the external one fine but not the internal one.
can download app into internal via web and brows around it.
It doesn't seem to be mounted for external USB access.
Can anyone help with this?
Thanks Martyn
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.
EDIT: by "mine" I mean my copy of Celtic's.
OOPS!
Sorry. My reply above was to kingtechmartyn, not the OP domiel...didn't mean to hijack the thread.
Very sorry.
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244<br />
<br />
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.<br />
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.<br />
<br />
EDIT: by "mine" I mean my copy of Celtic's.
Click to expand...
Click to collapse
Just remember when changing build.prop to always make a backup of the original so if you want to revert you can.
Sent from my Nook Tablet using xda premium
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
for an edit of build.prop, be sure to use the correct edit tool which places a 'line feed' at the eol and not a 'carriage return and line feed'.
hth.
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
Normal
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
you are right, normally a backup is automatically created. But, I have seen a lot of requests since November when we started messing with this device of people making mistakes and not having a backup. So it is always a good idea to copy and then save to the sd card just in case.
Sent from my Nook Tablet using xda premium
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
build prop differences
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Cubanluke88 said:
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
Click to expand...
Click to collapse
exactly, if more people would do this there might be fewer issues due to being able to restore if there is a oops moment.
Sent from my Nook Tablet using xda premium
Hi Bernardicus
Thanks heaps you are a champion!
I don't even know how to get terminal into su yet so you zip was a god send.
Now I have to work out how to enlarge the 1g of memory, i must admit it's very fulfilling modifying my Nook, looking forward to be proficient enough to return the favors from you all.
RhinoNelson said:
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Click to expand...
Click to collapse
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
bernardicus said:
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
Click to expand...
Click to collapse
I'm running Veronica's NT_CM7_Ribbon_ICS_v2.1 and I have the same problem. I replaced her vold.fstab with the Team B version and edited her build.prop. Now I can mount the Internal SD on my computer. Thanks for the help.