wallpaper path | developer.brewmp.com wallpaper path | developer.brewmp.com

Developer

wallpaper path

Forums:

Hi all,

I'm looking for some information about the path to use to store a wallpaper on the various handset.

The information on the "Knowledge base" isn't useful at all, it is plainly wrong, stating we need to use "Shared" for pre-3.1.3 phones and "fs:/~0x0102e5fc/" for post-3.1.4 phones, whereas in the real world, the LG8100 (2.1) needs to use "fs:/~0x0102e5fc/" for example (oh and by the way you need to put in the mif a dependency on a class that's documented nowhere).

The device spec are not consistent either in giving the right information.

So, basically we ended up having NSTL to test every phone we have with various possible paths, and we have most of the phones working, but we still have some left, that failed with all the paths we tried, and some of those phones are not available (yet, or not anymore) at verizon for us to try more possibilities.

So does anyone happen to know were to store wallpapers on the following phones ?
- Samsung A890 (the spec suggests "Shared", but if we store the wallpaper there it doesn't appear in MyPix)
- Samsung U710
- Nokia 6245
- LG 8600
- LG 9400
- Kyocera 323
- Casio Gz'One

Thanks for any useful info.

I have a similar problem with the Samsung A930. I have an image file I need to show up in MyPix. The spec says the shared media directory is /brew/16453/lk/mp but I haven't been able to get my file in that directory. Have you gotten this to work? What is the mif dependency you mentioned? If possible, can you post any code snippets? Any help is appreciated.

I have a similar problem with the Samsung A930. I have an image file I need to show up in MyPix. The spec says the shared media directory is /brew/16453/lk/mp but I haven't been able to get my file in that directory. Have you gotten this to work? What is the mif dependency you mentioned? If possible, can you post any code snippets? Any help is appreciated.

fs:/~0x0102e5fc/ is the directory you need to use on the A930. To use that path, you need to add a dependency to the class ID 0x0102e82d in th mif. Good luck...

fs:/~0x0102e5fc/ is the directory you need to use on the A930. To use that path, you need to add a dependency to the class ID 0x0102e82d in th mif. Good luck...

Thanks for the reply. I got that working. I would have never figured that out before reading your post since the documentation states that this way is for 3.1.4 and up and I'm using a 2.1 device. Anyway, I got the picture saved to /brew/16452/mp/ but it still does not show up in MyPix on the phone. This sounds similar to what you're seeing in the Samsung A890. If you've tried the A930, did you have a similar problem? Any idea what I'm missing? Thanks.

Thanks for the reply. I got that working. I would have never figured that out before reading your post since the documentation states that this way is for 3.1.4 and up and I'm using a 2.1 device. Anyway, I got the picture saved to /brew/16452/mp/ but it still does not show up in MyPix on the phone. This sounds similar to what you're seeing in the Samsung A890. If you've tried the A930, did you have a similar problem? Any idea what I'm missing? Thanks.

Does anyone have an insight as to what the wallpaper path is for the Casio Hitachi GzOne type-S?

Does anyone have an insight as to what the wallpaper path is for the Casio Hitachi GzOne type-S?

Hi,
Even I m facing the same prob. isnt a interface available(like IRingerManager for Ringtone) which can internally find wallpaper path.
thanx in advance..
Suppi.

Hi,
Even I m facing the same prob. isnt a interface available(like IRingerManager for Ringtone) which can internally find wallpaper path.
thanx in advance..
Suppi.

The plot thickens.
From what I can tell this device requires a protected MCF BID to be included in the mif.
AEEGROUPID_MCF_PICTURE.BID
This needs to be included in the dependencies tab on the mif. You'll find it in the /inc directory of your sdk.
Here is the associated macro call:
fs:/~0x0102382c/
Now once this has been accomplished it still has problems. It will save to what appears to be the proper directory:
brew/mod/10888
The phone's native UI does not enumerate these files for wallpapers.
Here is where it gets fun.
Using the QPST I can see proper path (saved a wallpaper to it by hand):
brew/10888
So it looks like the phones implementation of the MCF (media control file) is wanged. Would love to be wrong about this.
Software information:
V9210E43
BREW version:
3.1.4.32
Any word on the QComm side? Would certainly appreciate the help. :confused:

The plot thickens.
From what I can tell this device requires a protected MCF BID to be included in the mif.
AEEGROUPID_MCF_PICTURE.BID
This needs to be included in the dependencies tab on the mif. You'll find it in the /inc directory of your sdk.
Here is the associated macro call:
fs:/~0x0102382c/
Now once this has been accomplished it still has problems. It will save to what appears to be the proper directory:
brew/mod/10888
The phone's native UI does not enumerate these files for wallpapers.
Here is where it gets fun.
Using the QPST I can see proper path (saved a wallpaper to it by hand):
brew/10888
So it looks like the phones implementation of the MCF (media control file) is wanged. Would love to be wrong about this.
Software information:
V9210E43
BREW version:
3.1.4.32
Any word on the QComm side? Would certainly appreciate the help. :confused:

I had this same problem with the GzOne Type-S. I contacted the technical contact at UT Starcom and he gave me access to bigvault.com to download a firmware update (V9210M01). My image directory is fs:/~0x0102382c/. This corrected the issue...sort of. Here is my email to him and then his reply:
"Thx, I am able to run my application now and save wallpapers to the correct directory (/brew/mod/10888). However, the wallpapers do not show up in My Pictures until I power off the phone and power it back on. The same is true if I put any other pictures on the phone using App Loader. If I take a picture using the camera it shows up under My Pictures immediately. Is this a known issue?"
his reply:
"This is not an issue at all. From the information the manufacturer released to me that is exactly how they designed the SW to work. It's similar to installing PC application that requires the user to reboot the PC."
I can't understand how this could be acceptable. I am quite certain that NSTL would not pass my application because of this. Any thoughts?

I had this same problem with the GzOne Type-S. I contacted the technical contact at UT Starcom and he gave me access to bigvault.com to download a firmware update (V9210M01). My image directory is fs:/~0x0102382c/. This corrected the issue...sort of. Here is my email to him and then his reply:
"Thx, I am able to run my application now and save wallpapers to the correct directory (/brew/mod/10888). However, the wallpapers do not show up in My Pictures until I power off the phone and power it back on. The same is true if I put any other pictures on the phone using App Loader. If I take a picture using the camera it shows up under My Pictures immediately. Is this a known issue?"
his reply:
"This is not an issue at all. From the information the manufacturer released to me that is exactly how they designed the SW to work. It's similar to installing PC application that requires the user to reboot the PC."
I can't understand how this could be acceptable. I am quite certain that NSTL would not pass my application because of this. Any thoughts?

You could be getting into the same issue we are seeing in some of the models. To ensure integrity, we download a wallpaper in our application directory then move it to the wallpaper directory. If we move it using IFILEMGR_Rename, on some models it doesn't get picked up until next reboot, but if we copy it (open, read/write, close) then delete the original, it gets properly picked up.
HTH...

You could be getting into the same issue we are seeing in some of the models. To ensure integrity, we download a wallpaper in our application directory then move it to the wallpaper directory. If we move it using IFILEMGR_Rename, on some models it doesn't get picked up until next reboot, but if we copy it (open, read/write, close) then delete the original, it gets properly picked up.
HTH...

I took the suggestion in a previous post and instead of saving my wallpaper image directly into the correct wallpaper directory (/brew/mod/10888 on the GzOne Type-S) I am saving it into my application directory and copying it into the wallpaper directory. However, the image is not showing up in "My Pictures" until I reboot the phone. I believe that this is a problem with this device and was wondering if anyone else is encountering the same issue with it?

I took the suggestion in a previous post and instead of saving my wallpaper image directly into the correct wallpaper directory (/brew/mod/10888 on the GzOne Type-S) I am saving it into my application directory and copying it into the wallpaper directory. However, the image is not showing up in "My Pictures" until I reboot the phone. I believe that this is a problem with this device and was wondering if anyone else is encountering the same issue with it?

My application just failed NSTL because the wallpaper that was just downloaded was not available under My Pictures until after the phone was rebooted. I even included the copy from an email from the manufacturer stating that it is supposed to work this way. I don't know who to solve this problem and we just wasted $700!

My application just failed NSTL because the wallpaper that was just downloaded was not available under My Pictures until after the phone was rebooted. I even included the copy from an email from the manufacturer stating that it is supposed to work this way. I don't know who to solve this problem and we just wasted $700!

You should contact NSTL Support.

You should contact NSTL Support.

Because they're OH so helpful these days, especially when it comes to disputes with failure reports.
Max, I know you're not necessarily the person who directly deals with NSTL, but is there someone (anyone?!) you know of
that a developer can contact with regards to complaints about them?

Because they're OH so helpful these days, especially when it comes to disputes with failure reports.
Max, I know you're not necessarily the person who directly deals with NSTL, but is there someone (anyone?!) you know of
that a developer can contact with regards to complaints about them?

Well, you can try Dev Relations.
If there's already a known issue published against the device, you can just go through NSTL Support. If there's no known issue published for the issue, I'd recommend opening up support requests with both QIS and NSTL support. Any time you're trying to make an argument with NSTL, it helps if you have evidence in your favor (all other apps on the device exhibit the same behavior, known issue filed, etc.).

Well, you can try Dev Relations.
If there's already a known issue published against the device, you can just go through NSTL Support. If there's no known issue published for the issue, I'd recommend opening up support requests with both QIS and NSTL support. Any time you're trying to make an argument with NSTL, it helps if you have evidence in your favor (all other apps on the device exhibit the same behavior, known issue filed, etc.).

Was anyone ever able to resolve this issue with having to power-cycle the handset before the wallpapers appear in the gallery?
Thanks

Was anyone ever able to resolve this issue with having to power-cycle the handset before the wallpapers appear in the gallery?
Thanks