|
Title: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on December 29, 2009, 02:22:51 PM Just wanted to let you guys know that it's in progress...I'm so tired of being chained to what the phone came with from the factory, so it's time to get it on.
I currently have been able to make a directory in the filesystem. It seems the structure, as far as where "Other Files" is, is /Media/Other Files. Here's a folder structure of what I have so far for / <!DOCTYPE folder-listing SYSTEM "obex-Folder-listing.dtd"> <folder-listing version="1.0"> <parent-folder /> <file name="RecMngr.bin" size="3145728" /> <file name="drm_bind_id.dat" size="16" /> <file name="VcuReg.bin" size="35596" /> <folder name="DM" /> <folder name="DRM" /> <folder name="Pso" /> <folder name="Pxo" /> <folder name="Media" /> <folder name="Obigo" /> <folder name="Modules" /> <folder name="testrw" /> </folder_listing> I'm pretty sure there's nothing higher up than t hat. If there is, it's completely shutoff, but I highly doubt that there's anything higher. The "testrw" folder was my test to see if we had write access to that folder, and sure enough write access is there for us. So we have read-access, write access...things are opening up. Time to find where the java apps are at so I can try deleting them to see what happens. Oh, and yes, these phones are capable of FOTA. I took a gif file off the phone that you would actually see on your phone if you were to do a FOTA update (which doesn't appear to be supported by ATT at this time). (http://img148.imageshack.us/img148/3416/fotasoftwareeng.gif) Here's a scary thing: /Obigo/brs/private_data.dat stores a file that lists every search term you've ever entered into the built-in browser. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on December 29, 2009, 06:28:09 PM Here's the att.pol file (may vary slightly from your phone):
Code: ################################################################################# #����: Security Policy ����� �Ľ��� �� �����Ǵ� ���� �ּ� ���� ('#', ';', '/') ################################################################################# //------------------------------ Network Policy ------------------------------ alias: HTTP_HTTPS javax.microedition.io.Connector.http, javax.microedition.io.Connector.https alias: SSL javax.microedition.io.Connector.ssl alias: Comm_Connectivity javax.microedition.io.Connector.comm alias: Datagram javax.microedition.io.Connector.datagram, javax.microedition.io.Connector.datagramreceiver alias: Socket javax.microedition.io.Connector.socket, javax.microedition.io.Connector.serversocket alias: SIP dummy alias: Push javax.microedition.io.PushRegistry //------------------------------ PIM Policy ------------------------------ alias: PIM javax.microedition.pim.ContactList.read, javax.microedition.pim.EventList.read, javax.microedition.pim.ToDoList.read, javax.microedition.pim.ContactList.write, javax.microedition.pim.EventList.write, javax.microedition.pim.ToDoList.write //------------------------------ File Policy ------------------------------ alias: FILE javax.microedition.io.Connector.file.read, javax.microedition.io.Connector.file.write //------------------------------ Message Policy ------------------------------ alias: SMS javax.microedition.io.Connector.sms, javax.wireless.messaging.sms.send, javax.wireless.messaging.sms.receive alias: CBS javax.microedition.io.Connector.cbs, javax.wireless.messaging.cbs.receive alias: MMS javax.microedition.io.Connector.mms, javax.wireless.messaging.mms.send, javax.wireless.messaging.mms.receive //------------------------------ Bluetooth Policy ------------------------------ alias: Bluetooth javax.microedition.io.Connector.bluetooth.client, javax.microedition.io.Connector.bluetooth.server, javax.microedition.io.Connector.obex.client, javax.microedition.io.Connector.obex.server //------------------------------ SIM Policy ------------------------------ alias: SIM dummy //------------------------------ Location Policy ------------------------------ alias: Location javax.microedition.location.Location, javax.microedition.location.Orientation, javax.microedition.location.ProximityListener, javax.microedition.location.LandmarkStore.read, javax.microedition.location.LandmarkStore.write, javax.microedition.location.LandmarkStore.category, javax.microedition.location.LandmarkStore.management //------------------------------ Record Control Policy ------------------------------ alias: Record_Control javax.microedition.content.ContentHandler, javax.microedition.media.control.RecordControl, javax.microedition.media.control.VideoControl.getSnapshot //------------------------------------------------------------------------------------ domain: C=US;O=Cingular Wireless, LLC;CN=Cingular Trusted Root CA type: operator allow: HTTP_HTTPS allow: Comm_Connectivity allow: SSL allow: Datagram allow: Socket allow: SIP allow: Push allow: PIM allow: FILE allow: SMS allow: CBS allow: MMS allow: Bluetooth allow: SIM allow: Location allow: Record_Control domain: C=US;O=Cingular Wireless, LLC;CN=Cingular Preferred Root CA type: operator blanket(oneshot): HTTP_HTTPS blanket(oneshot): Comm_Connectivity blanket(oneshot): SSL blanket(oneshot): Datagram blanket(oneshot): Socket blanket(oneshot): SIP blanket(oneshot): Push blanket(oneshot): PIM blanket(oneshot): FILE blanket(oneshot): SMS blanket(oneshot): CBS blanket(oneshot): MMS blanket(oneshot): Bluetooth blanket(oneshot): Record_Control domain: C=US;O=Unified Testing Initiative (UTI);CN=GeoTrust CA for UTI //type: 3rd-party session(oneshot): HTTP_HTTPS session(oneshot): SSL session(oneshot): Datagram session(oneshot): SMS session(oneshot): MMS session(oneshot): Comm_Connectivity session(oneshot): Bluetooth session(oneshot): Push session(oneshot): Record_Control domain: C=ZA;S=Western Cape;L=Cape Town;O=Thawte Consulting cc;OU=Certification Services Division;CN=Thawte Premium Server CA;E=premium-server@thawte.com //type: 3rd-party session(oneshot): HTTP_HTTPS session(oneshot): SSL session(oneshot): Datagram session(oneshot): SMS session(oneshot): MMS session(oneshot): Comm_Connectivity session(oneshot): Bluetooth session(oneshot): Push session(oneshot): Record_Control domain: C=US;O=VeriSign, Inc.;OU=Class 3 Public Primary Certification Authority //type: 3rd-party session(oneshot): HTTP_HTTPS session(oneshot): SSL session(oneshot): Datagram session(oneshot): SMS session(oneshot): MMS session(oneshot): Comm_Connectivity session(oneshot): Bluetooth session(oneshot): Push session(oneshot): Record_Control domain: C=KR;O=LG Electronics;CN=CA, LG Electronics for Trusted Domain //type: manufacture blanket(oneshot): HTTP_HTTPS blanket(oneshot): Comm_Connectivity blanket(oneshot): SSL blanket(oneshot): Datagram blanket(oneshot): Socket blanket(oneshot): SIP blanket(oneshot): Push allow: PIM allow: FILE session(oneshot): SMS session(oneshot): CBS session(oneshot): MMS blanket(oneshot): Bluetooth session: SIM oneshot: Location session(oneshot): Record_Control domain: C=KR;O=LG Electronics;CN=CA, LG Electronics for Developer type: operator allow: HTTP_HTTPS allow: Comm_Connectivity allow: SSL allow: Datagram allow: Socket allow: SIP allow: Push allow: PIM allow: FILE allow: SMS allow: CBS allow: MMS allow: Bluetooth allow: SIM allow: Location allow: Record_Control domain: untrusted oneshot: HTTP_HTTPS I'm going to modify it and let you know if I can get things to happen as far as not being bugged about data access EVERY DAMN CLICK. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on December 30, 2009, 06:10:11 PM Hopefully you've made more progress than I did?
I wouldn't overwrite the policy file... Oh yeah, BE VERY CAREFUL NOT TO DELETE ANYTHING as you can't put it back where it belongs - unless you've found a way to write files directly to a specific location without the phone moving it. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on December 30, 2009, 06:18:40 PM I ended up deleting the att.pol last night. No harmful effects have resulted. After reinstalling opera mini, I only get the data access nag once after I open up opera, and that's it. I can surf away with no more nags.
I'm currently working with the openobex group to hammer out some bugs, hopefully. I can mount the filesystem using FUSE, but there's a bug on the openobex side that'll need resolved first. https://sourceforge.net/projects/openobex/forums/forum/27861 Also, I'm going to pull the binary file that I _think_ is handling the obex requests on the phone, and try to decompile it to see if there's perhaps a special header that needs sent, or whatnot. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on December 30, 2009, 08:02:11 PM Ok, I'm seriously pissed now. This phone keeps track of EVERYTHING it seems. Messages that have long been deleted, are still stored in RecMngr.bin. I crapped myself when I saw seriously old text messages with corresponding phone numbers in it.
WHat the hell is this, big brother? Title: Re: Accessing filesystem using bluetooth and OBEX Post by: curlefry on December 31, 2009, 11:33:18 PM Ok, I'm seriously pissed now. This phone keeps track of EVERYTHING it seems. Messages that have long been deleted, are still stored in RecMngr.bin. I crapped myself when I saw seriously old text messages with corresponding phone numbers in it. WHat the hell is this, big brother? That really pisses me off, they only give us room for ~100 texts even though it's blatantly keeping them...thank you for your hard work Tonglebeak, I really appreciate it since I don't understand this phone mumbo-jumbo. :) Title: Re: Accessing filesystem using bluetooth and OBEX Post by: justin121994 on January 01, 2010, 06:59:48 PM ??? Thats really pissing me off that it saves all the texts.
Have you found a way to take off the limit for texts? Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 02, 2010, 10:33:52 AM Still working on it. As of now I'm waiting on a bugfix on openobex's side, so I can proceed further.
I've also found that RecMngr.bin has a list of every single URL I've ever visited using Obigo (the built-in browser). This phone ticks me off more and more. I've also tried accessing the filesystem with Virtual Sim enabled, but the phone completely refuses to do anything (response code of 43 from the phone, which means "Forbidden".) Not sure if there's a way to override that currently, will definitely work on it though. ANother possibility is modifying the headers sent using the obex protocol. If we absolutely cannot find a way around the phone's "best-guess file placement", then perhaps sending false headers will trick it into placing files where we want to. I am definitely going to work on that as well. Will keep everyone up to date. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Whoracle on January 02, 2010, 05:55:53 PM Great job mate :)
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: max13 on January 03, 2010, 05:24:02 PM Great job, I am glad to see that there is still hope.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Whoracle on January 12, 2010, 06:53:03 PM I ended up deleting the att.pol last night. No harmful effects have resulted. After reinstalling opera mini, I only get the data access nag once after I open up opera, and that's it. I can surf away with no more nags. I'm currently working with the openobex group to hammer out some bugs, hopefully. I can mount the filesystem using FUSE, but there's a bug on the openobex side that'll need resolved first. https://sourceforge.net/projects/openobex/forums/forum/27861 Also, I'm going to pull the binary file that I _think_ is handling the obex requests on the phone, and try to decompile it to see if there's perhaps a special header that needs sent, or whatnot. Tongle mate could you guide me on how you accessed the file system ? And how you deleted the policy file, I have a Rogers phone and it's restricting Java apps to be installed from the web browser only, and installed applications don't have access to any file on the phone / memory card. Cheers mate Title: Re: Accessing filesystem using bluetooth and OBEX Post by: «ammar» on January 12, 2010, 07:25:48 PM im just gonna say that u might not wanna do any of ur hacks with bluetooth connection
because some of the files u send might lose some information a long the way and ur connection might disable causing ur phone to be bricked Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Whoracle on January 12, 2010, 08:20:22 PM I just connected to my phone using OBEX Commander (Has a user-friendly interface, you might want to check it out). The phone connects successfully and drivers installs successfully, except it gets stuck on "Retrieving Folders" then it fails, and it disconnects.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: «ammar» on January 13, 2010, 01:23:23 PM if u guys hav a data cable then u can conenct ur phone to the data cable then install the lg usb modem driver
it might work then u guys might be able to try to connect to efs Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on January 13, 2010, 01:52:57 PM Note: Java application permissions are defined (and somehow stored) at install, so deleting the att.pol may not affect currently-installed applications, but I'm curious to know if you can install something new and if it works OK.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on January 13, 2010, 01:56:28 PM @ammar:
At least with the EMP modem driver that LG supplies (on the GR500 disc - and seems to be the only one that even recognizes the phone) and my AT&T-branded firmware, nothing will stay connected over USB except for the GPRS data connection. LG's EFS explorer gets disconnected shortly after connection, so I can't "get in." This happens even with bootmode enabled. Happy to hear results to the contrary... :) EDIT: Ahh, haven't checked out the driver Ammar referenced - will give it a shot when I get a chance. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: sumo on January 13, 2010, 08:46:19 PM Note: Java application permissions are defined (and somehow stored) at install, so deleting the att.pol may not affect currently-installed applications, but I'm curious to know if you can install something new and if it works OK. Well the att.pol is a set of permissions the phone needs to allow certain access points. So if you are missing that file, newly installed apps will not be able to access certain functions (I.E. A mini browser, such as Opera Mini, will not be able to access the connection point to allow to connect to the Internet, etc.). Now, to my knowledge, I have not heard of any major complications coming from removing it (Although if I remember right, it would brick the Vu if that file was not present). Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 14, 2010, 09:23:05 AM SOrry folks, I've been doing other things lately and haven't gone back to playing with the phone yet.
Note: Java application permissions are defined (and somehow stored) at install, so deleting the att.pol may not affect currently-installed applications, but I'm curious to know if you can install something new and if it works OK. That's what I did with Opera Mini. You'll get one "data charges blahblahblah" prompt per session, and that's it. Much much less irritating then getting that prompt every single time you send a request. Also, deleting the att.pol did not help with allowing java apps to access the filesystem...as far as I can tell. I tried to reinstall liteftp onto the phone, but it did not have read access. But there were some other things I was going to do and I never got to it. I've been too busy working on my website. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: «ammar» on January 14, 2010, 02:24:00 PM @bhiga
i am hoping the lg usb modem driver will work for u guys i believe it supports all the lg phones hence the name (lg usb modem driver) Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Whoracle on January 14, 2010, 07:56:49 PM @bhiga i am hoping the lg usb modem driver will work for u guys i believe it supports all the lg phones hence the name (lg usb modem driver) Installed it, what now ? What should I do ? (What software should I run etc.) @Tongle, could you guide us on how you accessed the file system ? I'm familiar with OBEX, so you probably won't have to detail it a lot. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 14, 2010, 08:19:09 PM I used obexftp.
Pair the phone with the computer using bluetooth, then I would issue commands, such as obexftp -c / -l, to list the contents. For some reason though, only 4 SETPATHs are successful before it fails, so I can't get into a 4th subfolder. NOt sure if this is the phone, or if it's a bug with openobex. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on January 14, 2010, 11:21:54 PM To get beyond 4 layers deep, you'll have to alternate forward slashes (/) with backslashes (\)
I found that trick in the comments of one of the early KU or KF series Sony Ericsson phones with regard to BlueSoleil 1.6 It might work for openobex, not sure. @Tonglebeak: Do the carrier-supplied applications still work OK? (IM, Yellow Pages, etc) I'm very worried that without the policy file any new carrier-signed downloads (like from MEdia Mall) won't get proper permissions. Also to verify, your carrier is AT&T, correct? @ammar: The USB modem drivers are phone-specific as the USB device itself has different identifiers. We already have a working LG modem driver for the GR500/Xenon from the LG PC Suite CD, so that's covered, though it seems cable connections differ in behavior between Rogers and AT&T firmwares. @sumo: Appreciate your attention and sharing your knowledge! The GR500/Xenon definitely has a main SWF-based interface, along with various PAF and PXO files that are mainly graphical in nature, as you say. I'll post a map of the AT&T firmware's filesystem here in a few... need to transfer the file to an accessible machine. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 15, 2010, 10:08:04 AM IM works, as does media net.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Whoracle on January 15, 2010, 04:21:14 PM Phone is paired.
obexftp -b -c / -l returns a connection error Am I missing something ? Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on January 16, 2010, 01:23:03 AM @Tonglebeak:
Interesting... Keep us updated, especially if you download/purchase a program that accesses Internet or GPS from MEdia Mall. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on January 31, 2010, 12:21:48 PM so how do you even access the files in the first place?
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 31, 2010, 10:52:18 PM Well, the new thing I've been working on is faking certificates. I have a signed midlet ready to roll, but for some reason the phone states "Authentication failed" :(
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Tonglebeak on January 31, 2010, 11:11:01 PM http://sandboxofstuff.com/MiniCommander.jad (http://sandboxofstuff.com/MiniCommander.jad)
http://sandboxofstuff.com/MiniCommander.jar (http://sandboxofstuff.com/MiniCommander.jar) Perhaps one of you can figure out why shit doesn't work. And I'm having a hell of a time getting my fake certificate onto the phone (can't download it for some gay reason). Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on February 13, 2010, 02:30:15 PM your jar file comes out as a zip :-[
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on February 23, 2010, 02:14:08 AM Technically JARs are Zip files. But specific MIME types are needed to do direct-to-phone download.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on March 11, 2010, 07:06:37 AM so what is this just a dead topic now??? >:( >:( >:(
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: Spyker on March 11, 2010, 09:37:52 PM do you wanna try doing this? takes time..
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on March 12, 2010, 07:08:08 AM actually i have been working, but what i was asking was why nobody was talking about it anymore. don't jump to conclusion next time.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on March 18, 2010, 05:36:21 PM Mainly I think most people are busy and don't have a spare phone + SIM to really dedicate to hard-core experimentation.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on March 18, 2010, 08:39:01 PM o well :-\ :-\ :-\
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on March 19, 2010, 01:19:41 AM I have a spare phone, but no SIM (and BOOTMODE access doesn't work without a SIM - that was 2 hours of headscratching...) maybe I can get one of those prepaid ones.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: kgb on March 19, 2010, 06:11:06 AM Just call you carrier and say that you have lost you old SIM and would like a new one. They should ship you one out. I have two extras here for Rogers. I'd ship you one down but your Xenon would need to be unlocked to work.
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: lotamaster on April 03, 2010, 05:48:57 AM yea...im not very good with this code and stuff. can somebody please tell me what i can do to view a deleted text message (in simple terms :P)
Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on April 03, 2010, 11:44:30 PM Just call you carrier and say that you have lost you old SIM and would like a new one. They should ship you one out. I have two extras here for Rogers. I'd ship you one down but your Xenon would need to be unlocked to work. Hmm... My Xenon is unlocked... Haven't bothered to call to get my backup (now primary) Xenon unlocked yet. I should do that.I was under the impression that carriers get mighty unhappy when they see two devices active on the network with the same whatever identifies your account on the SIM. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: PaulEinsig on April 07, 2010, 12:03:25 PM yea...im not very good with this code and stuff. can somebody please tell me what i can do to view a deleted text message (in simple terms :P) im not sure if you even can Title: Re: Accessing filesystem using bluetooth and OBEX Post by: liuht on May 08, 2010, 10:49:42 AM i deleted the att.pol file yesterday. Finally get ride of the annoying network access prompt. However, there are two unexpected things I noticed: first of all, media mall link doesn't work anymore, second, newly installed ebuddy can't access internet. It appears that the att.pol file is more than a set of security definitions.
For those who want to do the same, here is what I did: I downloaded a ubuntu live CD, boot computer into ubuntu, then insert bluetooth adapter and install obexftp (you can use 'sudo apt-get install obexftp' to install obexftp). Then you can use the following command to delete att.pol file. opexftp -b -c . -c Media -c Java -c cert -G att.pol Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on May 10, 2010, 12:16:07 PM Million dollar question now is...
Can you put the att.pol file back? Title: Re: Accessing filesystem using bluetooth and OBEX Post by: spillb on June 23, 2010, 03:00:57 PM I can get passed 4 layers if I use the -S switch. I'm using obexftp in ubuntu. Not sure if openobex has this switch.
i.e. 5 layers obexftp -b xx:xx:xx:xx:xx:xx -S -c ../Media/Obigo/ref/theme/2 -l Sending "../Media/Obigo/ref/theme/2"...|done Receiving "(null)".../<?xml version="1.0"?> <!DOCTYPE folder-listing SYSTEM "obex-Folder-listing.dtd"> <folder-listing version="1.0"> <parent-folder /> <file name="ls_Browser_softkey_forward.bmp" size="7076" /> <file name="Browser_softkey_favorite_dim.bmp" size="4196" /> <file name="tab_active2nd.bmp" size="30054" /> <file name="zoombar_out.bmp" size="1712" /> <file name="Browser_softkey_forward_p.bmp" size="4196" /> <file name="ls_Browser_softkey_back.bmp" size="7616" /> <file name="zoombar_in_p.bmp" size="1712" /> <file name="Browser_softkey_zoom.bmp" size="4736" /> <file name="zoombar_out_p.bmp" size="1712" /> <file name="Browser_softkey_refresh_p.bmp" size="4196" /> <file name="Browser_softkey_forward_dim.bmp" size="4196" /> <file name="Widgets_softkey_back.bmp" size="4536" /> <file name="ls_Browser_softkey_zoom_p.bmp" size="7796" /> <file name="Browser_softkey_refresh.bmp" size="4196" /> <file name="Browser_softkey_back.bmp" size="4736" /> <file name="zoombar_in.bmp" size="1712" /> <file name="zoombar_bg.bmp" size="21740" /> <file name="Browser_softkey_back_dim.bmp" size="4736" /> <file name="ls_Browser_softkey_refresh.bmp" size="7076" /> <file name="ls_Browser_softkey_stop_dim.bmp" size="7076" /> <file name="Browser_softkey_zoom_dim.bmp" size="4736" /> <file name="ls_Browser_softkey_zoom.bmp" size="7796" /> <file name="Browser_softkey_option.bmp" size="4536" /> <file name="ls_Browser_softkey_back_p.bmp" size="7616" /> <file name="ls_Browser_softkey_zoom_dim.bmp" size="7796" /> <file name="ls_Browser_softkey_favorite_p.bmp" size="7076" /> <file name="ls_tab_active1st3.bmp" size="54254" /> <file name="ls_tab_active1st.bmp" size="54254" /> <file name="Browser_softkey_close_p.bmp" size="9176" /> <file name="Browser_softkey_next_p.bmp" size="9176" /> <file name="browser_close_p.bmp" size="776" /> <file name="Browser_softkey_refresh_dim.bmp" size="4196" /> <file name="Widgets_softkey_back_p.bmp" size="4536" /> <file name="Browser_softkey_stop_dim.bmp" size="4196" /> <file name="Browser_softkey_close.bmp" size="9176" /> <file name="Browser_softkey_forward.bmp" size="4196" /> <file name="ls_tab_active2nd.bmp" size="54454" /> <file name="Browser_softkey_favorite_p.bmp" size="4196" /> <file name="ls_Browser_softkey_back_dim.bmp" size="7616" /> <file name="ls_Browser_softkey_stop_p.bmp" size="7076" /> <file name="Widgets_softkey_option_dim.bmp" size="4536" /> <file name="ls_tab_active2nd3.bmp" size="54454" /> <file name="Browser_softkey_prev_p.bmp" size="9176" /> <file name="Browser_softkey_next.bmp" size="9176" /> <file name="ls_Browser_softkey_refresh_dim.bmp" size="7076" /> <file name="Browser_softkey_option_dim.bmp" size="4536" /> <file name="ls_Browser_softkey_refresh_p.bmp" size="7076" /> <file name="zoombar_cursor.bmp" size="470" /> <file name="Browser_softkey_stop_p.bmp" size="4196" /> <file name="ls_Browser_softkey_option_dim.bmp" size="4536" /> <file name="Widgets_softkey_option.bmp" size="4536" /> <file name="ls_Widgets_title_bg.bmp" size="60056" /> <file name="ls_Browser_softkey_forward_p.bmp" size="7076" /> <file name="Widgets_title_bg.bmp" size="36056" /> <file name="Browser_softkey_prev.bmp" size="9176" /> <file name="ls_Browser_softkey_forward_dim.bmp" size="7076" /> <file name="Browser_softkey_option_p.bmp" size="4536" /> <file name="ls_Browser_softkey_bg.bmp" size="48056" /> <file name="ls_Browser_softkey_stop.bmp" size="7076" /> <file name="Browser_softkey_back_p.bmp" size="4736" /> <file name="ls_Browser_softkey_favorite.bmp" size="7076" /> <file name="tab_left_bg.bmp" size="6454" /> <file name="ls_Browser_softkey_option.bmp" size="4536" /> <file name="Widgets_softkey_option_p.bmp" size="4536" /> <file name="Browser_softkey_favorite.bmp" size="4196" /> <file name="Browser_softkey_bg.bmp" size="28854" /> <file name="ls_Browser_softkey_option_p.bmp" size="4536" /> <file name="Browser_progress_bar.bmp" size="132" /> <file name="browser_close.bmp" size="776" /> <file name="tab_active1st.bmp" size="30054" /> <file name="Browser_softkey_stop.bmp" size="4196" /> <file name="Browser_softkey_zoom_p.bmp" size="4736" /> <file name="ls_Browser_softkey_favorite_dim.bmp" size="7076" /> </folder_listing> Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on June 23, 2010, 03:54:24 PM Has anyone so far been able to successfully write (ie, the file writes and stays there) a file outside of /Media/Others and /Media/Other Files ?
If so, please provide how you managed it, thanks! Title: Re: Accessing filesystem using bluetooth and OBEX Post by: xPi on July 20, 2010, 06:07:00 AM tried out MiniCommander.jar
"This application read your personal planner information. Continue?" pressed OK 34 times, and it works! wow, its like midnight commander I was not able to get into Private there's a lot of .mid files in /temp/ 10 minutes of OK button mashing and 4 seconds of file copying later, I've got the midi files on the sdcard! its kinda bad to have the row of touch screen numbers right behind the OK button that I am mashing... the midi and wav files turn out to be from a game I was recently playing... ...this thing has to unpack the sound files to a temp directory to play them??? Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on July 20, 2010, 03:29:46 PM Sounds good so far...
Can you write the files to anywhere other than /temp or /card ? So far all the firmwares redirect incoming files to another folder, depending on its file type. Unknown file types get moved into Others or Other Files. Yes, Java apps have access to /temp to store files. :) Title: Re: Accessing filesystem using bluetooth and OBEX Post by: xPi on July 20, 2010, 04:17:11 PM copied /Card/a.txt to /Private/a.txt using MiniCommander
.. well that wasn't useful, reinstalling the app made a.txt disappear OBEX Commander on windows could not connect with Folder Browsing.. Title: Re: Accessing filesystem using bluetooth and OBEX Post by: bhiga on July 20, 2010, 05:19:39 PM /Private is for the app to store its data too, from what I can tell, persists only with application install, so it'd store preferences and the like.
|