I am having some trouble getting a custom wallpaper to be the default via auto-provisioning. The logs show the phone properly setting the user.ini value, but it is not actually applied.
Here is the entry from my common config file:
#Configure the phone background.
#If you set the custom image (new.png) as phone backgroup, the value is: phone_setting.backgrounds = Config:new.png
#If you set the system image (pictures(01).png) as phone backgroup, the value is: phone_setting.backgrounds = Resource:pictures(01).png
phone_setting.backgrounds = Config:newfslogo_white_t32.png
Here is the log from the phone:
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :276 ] IFO ***** Upgrade CFG File *****
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :301 ] DEB Open File [/phone/config/user.ini]
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :327 ] DEB --- Set [PhoneSetting::BackGrounds] Value [Config:newfslogo_white_t32.png]
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :327 ] DEB --- Set [PhoneSetting::ScreensaverTime] Value [0]
Aug 22 22:11:18 autop[373]: [./src/autoParser.cpp :823 ] IFO ***** END [CHANGED] *****
Despite apparently setting the wallpaper, it is still using the default. Exported config file:
[ PhoneSetting ]
BackLight = 8
UnusedBackLight = 1
BacklightTime = 60
BackGrounds = Resource:pictures (01).png
ScreensaverTime = 0
The actual image file is stored on the phone, and available to manually set as the background. Also, I am able to modify the user.ini file to have the "Config:newfslogo_white_t32.png" line, and upon re-uploading the config to the phone, the correct background appears.
Just realized there is a related thread here:
http://forum.yealink.com/forum/showthrea...212&page=1
And the "solution" on that thread did work -- rebooting the phone after it has received this config will show the proper wallpaper. This appears to be an order of operations issue. After a reboot, the user.ini files shows the proper line as well. So, it seems that the phone is loading the config into memory before setting the value somehow(though other values such as the screensaver timeout seem to apply right away).
I can live with this, but would prefer not having to re-boot a second time. When remotely provisioning phones, it would be nice to have the phone display properly on first boot for a better end user experience.
Edit: This may not be resolved...second time around, the phone is no longer taking the wallpaper setting, so it doesn't appear to be consistent.
Here is the entry from my common config file:
#Configure the phone background.
#If you set the custom image (new.png) as phone backgroup, the value is: phone_setting.backgrounds = Config:new.png
#If you set the system image (pictures(01).png) as phone backgroup, the value is: phone_setting.backgrounds = Resource:pictures(01).png
phone_setting.backgrounds = Config:newfslogo_white_t32.png
Here is the log from the phone:
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :276 ] IFO ***** Upgrade CFG File *****
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :301 ] DEB Open File [/phone/config/user.ini]
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :327 ] DEB --- Set [PhoneSetting::BackGrounds] Value [Config:newfslogo_white_t32.png]
Aug 22 22:11:18 autop[373]: [./src/fileUpgrader.cpp :327 ] DEB --- Set [PhoneSetting::ScreensaverTime] Value [0]
Aug 22 22:11:18 autop[373]: [./src/autoParser.cpp :823 ] IFO ***** END [CHANGED] *****
Despite apparently setting the wallpaper, it is still using the default. Exported config file:
[ PhoneSetting ]
BackLight = 8
UnusedBackLight = 1
BacklightTime = 60
BackGrounds = Resource:pictures (01).png
ScreensaverTime = 0
The actual image file is stored on the phone, and available to manually set as the background. Also, I am able to modify the user.ini file to have the "Config:newfslogo_white_t32.png" line, and upon re-uploading the config to the phone, the correct background appears.
Just realized there is a related thread here:
http://forum.yealink.com/forum/showthrea...212&page=1
And the "solution" on that thread did work -- rebooting the phone after it has received this config will show the proper wallpaper. This appears to be an order of operations issue. After a reboot, the user.ini files shows the proper line as well. So, it seems that the phone is loading the config into memory before setting the value somehow(though other values such as the screensaver timeout seem to apply right away).
I can live with this, but would prefer not having to re-boot a second time. When remotely provisioning phones, it would be nice to have the phone display properly on first boot for a better end user experience.
Edit: This may not be resolved...second time around, the phone is no longer taking the wallpaper setting, so it doesn't appear to be consistent.