I'm running Vegan 1.5.1 with VTL Launcher.
Twice now, on boot, I've had all the widgets come up as "Problem Loading Widget". Once this happens, nothing I've tried gets them to automatically load, including restarting VTL, rebooting, restoring, etc. I ended up having to delete and recreate all the widgets, which is very annoying.
Any ideas why this is happening, how to prevent and/or fix it after it does?
A clue? I recreated the Widgets, one by one. I noticed that after adding some of them, one of the old "problem" ones would duplicate the new widget I just created. Hrm...
TarheelGrad1998 said:
Twice now, on boot, I've had all the widgets come up as "Problem Loading Widget". Once this happens, nothing I've tried gets them to automatically load, including restarting VTL, rebooting, restoring, etc. I ended up having to delete and recreate all the widgets, which is very annoying.
Any ideas why this is happening, how to prevent and/or fix it after it does?
Click to expand...
Click to collapse
No, no, and, yes--I think I know how to fix it.
I get the same problem, sometimes, after I "Wipe Dalvik Cache"/"wipe cache partition" in ClockworkMod. After looking around, I found out that the widget list is stored in /data/system/appwidgets.xml, and that this file, occasionally, for some reason, gets reset to defaults.
Just copy your /data/system/appwidgets.xml elsewhere for safekeeping, then restore it when you have problems.
TarheelGrad1998 said:
A clue? I recreated the Widgets, one by one. I noticed that after adding some of them, one of the old "problem" ones would duplicate the new widget I just created. Hrm...
Click to expand...
Click to collapse
That sounds like the Google backup/restore magic in progress. It surprised me too. I upgraded from CyanogenMod 7.0.2 to 7.0.3 and I'd fully expected to re-install all my old apps and widgets after I'd upgraded. I left the gTab on for a few hours and my apps (which I'd moved onto the SD card) started automagically installing themselves one by one.
I'm happy, but, also mildly disturbed that this sort of thing happens behind my back.
Thanks a lot for the reply.
I could save/restore that file, but...I can't find that file at that path. Is it somewhere else under VTL?
TarheelGrad1998 said:
I could save/restore that file, but...I can't find that file at that path. Is it somewhere else under VTL?
Click to expand...
Click to collapse
That, in fact, might be the cause of your problem. As far as I can tell, the appwidgets.xml file is created by Android--ie. it's not Launcher specific. (I'm using ADWLauncher EX, btw.)
Try these steps:
1. Do a "Fix permissions" using ClockworkMod or by typing the following commands in a Terminal:
Code:
$ su
# /system/bin/fix_permissions
2. Reboot the gTab and add all your widgets back to desktop. This should create a /data/system/appwidgets.xml file.
3. Copy the file safely away somewhere.
4. Reboot the gTab and see if the widgets still load.
I get this randomly as well, it appears to be a crap shoot for me everytime i turn my GTAB on. Its usually all are not working and get "Problem loading widget" or all is fine..I too will give this a try soon as i can and update.
My ROM is CM7 stable
rajeevvp said:
That, in fact, might be the cause of your problem. As far as I can tell, the appwidgets.xml file is created by Android--ie. it's not Launcher specific. (I'm using ADWLauncher EX, btw.)
Try these steps:
1. Do a "Fix permissions" using ClockworkMod or by typing the following commands in a Terminal:
Code:
$ su
# /system/bin/fix_permissions
2. Reboot the gTab and add all your widgets back to desktop. This should create a /data/system/appwidgets.xml file.
3. Copy the file safely away somewhere.
4. Reboot the gTab and see if the widgets still load.
Click to expand...
Click to collapse
I tried those steps. It happened again today, so I did "Fix permissions" in CWM, rebooted, removed and added the Widgets again...but I still don't see that file.
Do you need something like Root Explorer to see it?
I moved VTL to system apps with root explorer and fixed permissions. Once I did that I have not experienced this problem again.
Also, does anyone experience this while only having one launcher installed? It might not have been just moving VTL to system apps it could have been deletion of the stock launcher as well. Could be that multiple launchers are causing the .XML file to be reset.
Just a thought.
TarheelGrad1998 said:
I tried those steps. It happened again today, so I did "Fix permissions" in CWM, rebooted, removed and added the Widgets again...but I still don't see that file.
Do you need something like Root Explorer to see it?
Click to expand...
Click to collapse
Yeah, it might be a File Manager thing. I rarely use any of them so I can't say if it's case here for sure. Try this:
Code:
$ /system/xbin/ls -ld /data/system
drwxrwxr-x 8 1000 1000 1024 Jun 14 22:28 /data/system
$ /system/xbin/ls -l /data/system
total 203
-rw-rw---- 1 1000 1000 24576 Jun 14 08:47 accounts.db
-rw------- 1 1000 1000 1071 Jun 14 05:42 appwidgets.xml
-rw------- 1 1000 1000 11504 Jun 14 22:28 batterystats.bin
-rw------- 1 1000 1000 291 May 17 15:51 called_pre_boots.dat
-rw------- 1 1000 1000 191 May 17 15:51 device_policies.xml
drwx------ 2 1000 1000 12288 Jun 14 22:43 dropbox
-rw------- 1 1000 1000 4096 Jun 14 20:28 entropy.dat
-rw-rw-r-- 1 1000 1000 6261 Jun 14 05:42 packages.list
-rw-rw-r-- 1 1000 1000 121707 Jun 14 05:42 packages.xml
-rw------- 1 1000 1000 11737 Jun 12 20:00 profiles.xml
drwxrwx--x 2 1000 1000 1024 Jun 14 04:41 registered_services
drwxrwx--x 2 1000 1000 1024 Jun 13 00:33 shared_prefs
drwx------ 2 1000 1000 1024 Jun 14 05:11 sync
drwx------ 2 1000 1000 1024 May 17 15:51 throttle
-rw-rw-r-- 1 1000 1000 143 Jun 13 07:43 uiderrors.txt
drwx------ 2 1000 1000 1024 Jun 14 22:10 usagestats
-rw------- 1 1000 1000 173 Jun 14 06:43 wallpaper_info.xml
That is (roughly) how the output should look. Verify that /data/system has the same owner and group and the same permissions. The same for the files inside /data/system. If you ran the fix_permissions command in my previous post (or used CWM to do it), it would have set the permissions to what you see above (roughly that is--it sets some idiotic permissions to a lot of the files for no good reason).
If you don't want/like to use the command line, then Root Explorer is what's usually suggested.
Ah, I downloaded Terminal Emulator, and I can see the file there. Though, I can't copy it, due to permissions.
Shame that it appears Titanium Media sync can't see the file.
Anyway, thanks for the help. I'm still a newb.
TarheelGrad1998 said:
Ah, I downloaded Terminal Emulator, and I can see the file there. Though, I can't copy it, due to permissions.
Click to expand...
Click to collapse
You will need the Superuser app from Market, too, if you don't already have it.
Code:
$ su [I] Become superuser[/I].
# cat /data/system/appwidgets.xml [I]Check the file first.[/I]
# cp /data/system/appwidgets.xml /mnt/sdcard/.
Check the size of the appwidgets.xml file and its contents first before you save it. If the file is a lot smaller than ~1000 bytes, or, if its contents, as displayed by the cat command, seems suspiciously thin, or, look like binary junk, then you have a problem file and you shouldn't copy it. To restore the file (you must have busybox installed--use something like Busybox Installer from Market):
Code:
$ su
# install -o 1000 -g 1000 -m 600 /mnt/sdcard/tmp/appwidgets.xml /data/system/appwidgets.xml
Here's my appwidgets.xml file:
Code:
$ su
# cat /data/system/appwidgets.xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<gs>
<p pkg="com.google.android.apps.genie.geniewidget" cl="com.google.android.apps.genie.geniewidget.miniwidget.MiniWidgetProvider" />
<p pkg="com.android.music" cl="com.android.music.MediaAppWidgetProvider4x2" />
<p pkg="com.cyanogenmod.cmparts" cl="com.cyanogenmod.cmparts.provider.RenderFXWidgetProvider" />
<p pkg="com.curvefish.widgets.bluetoothonoff" cl="com.curvefish.widgets.bluetoothonoff.Bluetooth" />
<p pkg="org.zooper.acw" cl="org.zooper.acwlib.ACWProvider" />
<p pkg="com.jasoncalhoun.android.systeminfowidget" cl="com.jasoncalhoun.android.systeminfowidget.SystemInfoWidget" />
<p pkg="com.curvefish.widgets.wifionoff.donate" cl="com.curvefish.widgets.wifionoff.donate.Widget" />
<h pkg="org.adwfreak.launcher" id="400" />
<g id="1" h="0" p="3" />
<g id="2" h="0" p="6" />
<g id="3" h="0" p="0" />
<g id="4" h="0" p="4" />
<g id="5" h="0" p="4" />
<g id="6" h="0" p="0" />
<g id="7" h="0" p="5" />
<g id="8" h="0" p="1" />
<g id="b" h="0" p="2" />
<g id="f" h="0" p="2" />
<g id="11" h="0" />
</gs>
Mantara said:
I moved VTL to system apps with root explorer and fixed permissions. Once I did that I have not experienced this problem again.
Also, does anyone experience this while only having one launcher installed? It might not have been just moving VTL to system apps it could have been deletion of the stock launcher as well. Could be that multiple launchers are causing the .XML file to be reset.
Just a thought.
Click to expand...
Click to collapse
I'm on ADW Ex and I uninstalled the free ADW that comes with CM7, so I only have one launcher and I'm still getting the problem occasionally, so I don't think it's caused by having multiple launchers installed. That could be causing it too, but if so, it's not the only cause. I'll try moving it to /system/app, then fix permissions and see if that fixes it. It might take a while to find out, though, since the problem occurs so sporadically. Thanks for the tip!
Just in case people would like to try this, but don't know how to do it:
1) Get Root Explorer, it's well worth the money; you need a file manager that can browse all the root folders and change permissions. I use it all the time to do this sort of thing. (You can also do this using ADB, but that's more complicated)
2) Open Root Explorer and navigate to /data/app and locate the apk of the launcher you're using (I'm on ADW Ex, so mine was "org.adwfreak.launcher-1.apk"). Long press the file and select "Move".
3) Navigate to /system/app. Press the "Mount R/W" button in the upper left corner then hit "Paste".
4) Fix Permissions. You can do this in a terminal app (I used Terminal Emulator, which comes with CM7) or you can reboot into clockwork mod and do it from there. If you're doing it with a terminal app, the code is:
$ su
# /system/bin/fix_permissions
(the $ and # are added automatically)
You're done and this problem is hopefully fixed (fingers crossed). Thanks Mantara!
I just booted up my gtab and all the widgets said "Problem Loading Widget", so I guess moving the launcher to /system/app doesn't fix the problem (at least for me on ADW Ex). Oh well, it was a good idea.
Sorry to hear that. I have not had it happen with vtl launcher since I did this. I was actually wondering the other day if you had got this sorted out.
Mantara said:
Sorry to hear that. I have not had it happen with vtl launcher since I did this. I was actually wondering the other day if you had got this sorted out.
Click to expand...
Click to collapse
Thanks! It's not a big deal. It only happens once in a while and it only takes a minute or two to remove and replace all the widgets, so it's really only a minor inconvenience. I'm sure the issue will be resolved when I flash a newer version of CM7 or switch to one of the HC ROMs.
raphenucleus said:
I just booted up my gtab and all the widgets said "Problem Loading Widget", so I guess moving the launcher to /system/app doesn't fix the problem (at least for me on ADW Ex). Oh well, it was a good idea.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking of doing that, but it sounds not worth it.
I haven't had it happen again since doing the fix permissions. But like you, I'm not convinced yet. Sometimes it goes weeks. I had it happen every couple of days when I started this thread.
"Fix permissions" fixed it for some of my widgets. A couple of them though, still showed "Problem loading gadget".
Here's what I did:
I rebooted in recovery, cleared cache and dalvik cache, I ran "Fix permissions", then rebooted, re-created widgets on the workspaces, and then rebooted again to test. It was ok. I'll re-create the couple of widgets that did not load, and go over it again.
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
I did it again. One of the two widgets that were still not loading loaded this time. So did the ones that loaded successfully the previous time. The other one though, disappeared completely.
I guess I have no choice but to go over it again...
lots of people ask... how do you port roms... so here you go... I hope now the thread is started the people posting can help each other as I have other projects working on... Maybe someone learning will help me later with my other roms
lot of chatter of people saying that the structure of my rom is from other x10 so for you all to see I give you basic instructions (that I ported and posted first with almost everything working) so here is all the basics on getting a bootable miui rom for beginners.. first download the formels newest release.
then download a stable gingerbread 2.3.3 version that is compatible with the files. ( I always use the great z and j for sources).
the next step is to get the formels rom ready by deleting the boot image and the data folder. Next step is to go to the etc folder and delete firmware folder... also delete ap2sd init script from the init folder)
then go to lib folder and delete hw and modules.
now it is time to add files. I know the miui files pretty good now so the list has shortened greatly.
now use your stable gb rom source to replace the folders I had you delet above
you may have to change other files depending on the rom i.e. bluetooth/dhcpd and others.
to start in the etc folder you need to add
apns-conf
dbus
dualmic
gps
hosts
hw-config
init.bt
init.gold
init.local
mediaprofiles
mke2fs
profile
resolve
sensors
sysctl
vold
now to the lib folder all files start with lib
cm
dll
dsm
dss
gsl
miscta
oem-rapi
pbmilb
qmi
diag
mmgsdilib
nv
onrpc
queue
ril-qc-1
wms
auth
sdi-exp
wmsts
mmipl
oemcamera
mmjpeg
there are other files but I think that is enough to get bootscreen... if not let me know and I will list the other misc ones.
now the bin files
akmd2
am
bmgr
bmiloader
chargemon
charger
compache
eeprom
fixpermisions
gdbserver
handlecompache
hciqcomminit
ime
input
monkey
pm
port-bridge
qmuxd
recevent
svc
sysinit
updatemiscta
wlanmac
wlantool
wmiconfig
Any dev, or semi-dev can start work this.
COURTESY: http://android.modaco.com/content/s...aco-com/341986/how-to-port-miui/#entry1737792
manju991 said:
lots of people ask... how do you port roms... so here you go... I hope now the thread is started the people posting can help each other as I have other projects working on... Maybe someone learning will help me later with my other roms
lot of chatter of people saying that the structure of my rom is from other x10 so for you all to see I give you basic instructions (that I ported and posted first with almost everything working) so here is all the basics on getting a bootable miui rom for beginners.. first download the formels newest release.
then download a stable gingerbread 2.3.3 version that is compatible with the files. ( I always use the great z and j for sources).
the next step is to get the formels rom ready by deleting the boot image and the data folder. Next step is to go to the etc folder and delete firmware folder... also delete ap2sd init script from the init folder)
then go to lib folder and delete hw and modules.
now it is time to add files. I know the miui files pretty good now so the list has shortened greatly.
now use your stable gb rom source to replace the folders I had you delet above
you may have to change other files depending on the rom i.e. bluetooth/dhcpd and others.
to start in the etc folder you need to add
apns-conf
dbus
dualmic
gps
hosts
hw-config
init.bt
init.gold
init.local
mediaprofiles
mke2fs
profile
resolve
sensors
sysctl
vold
now to the lib folder all files start with lib
cm
dll
dsm
dss
gsl
miscta
oem-rapi
pbmilb
qmi
diag
mmgsdilib
nv
onrpc
queue
ril-qc-1
wms
auth
sdi-exp
wmsts
mmipl
oemcamera
mmjpeg
there are other files but I think that is enough to get bootscreen... if not let me know and I will list the other misc ones.
now the bin files
akmd2
am
bmgr
bmiloader
chargemon
charger
compache
eeprom
fixpermisions
gdbserver
handlecompache
hciqcomminit
ime
input
monkey
pm
port-bridge
qmuxd
recevent
svc
sysinit
updatemiscta
wlanmac
wlantool
wmiconfig
Any dev, or semi-dev can start work this.
COURTESY: http://android.modaco.com/content/s...aco-com/341986/how-to-port-miui/#entry1737792
Click to expand...
Click to collapse
nice dude,some 1 start with it?
Could this guide still be used for porting nowadays?
Anyway, thanks for this usefull information
so it's works ?
This is a very useful guide , thank you.
Hlo guys,
Please help me to fix sound bug after porting rom in spreadtrum sc7731 kitkat 4 .4.2
here is the guide which i used...
from /system/bin
phoneserver
netd
tc
wpa_supplicant
from /system/lib
hw(whole folder)
modules(whole folder)
egl(whole folder)
libhardware.so
libhardware_legacy.so
libctest.so
libdiskconfig.so
lisensorservice.so
from /system/etc
bluetooth(whole folder)
dhcpcd(whole folder)
firmware(whole folder)
wifi(whole folder)
handheld_core_hardware.xml (from permissions)
platform.xml(from permissions)
from from /system
vendor(whole folder)
usr(whole folder)
Further asking Spreadtrum developers i tried their method too to fix bug here what i did
★Bin
(folder)
tinymix
★etc
(folder)
audio_effects.conf
audio_hw.xml
audio_para
audio_policy.con
tiny_hw.xml
★Lib (folder)
libaudio-resampler.s*o
libaudioeffect_jni.s*o
libaudioflinger.so
libaudiopolicy.so
libaudiopreprocessin*g.so
libaudioutils.so
libtinyalsa.so
libtinyxml.so
libwebrtc_audio_prep*rocessing.so
lib> soundfx
(sub-folder)
libaudiopreprocessin*g.so
libbundlewrapper.so
libdownmix.so
libeffectproxy.so
libldnhncr.so
libreverbwrapper.so
libswdap-mod.so
libvisualizer.so
I took logcat too via alogcat android application(before trying this guide i hope it will help)
Please help guys!! We really need all the help w can get here . . .
No support
https://forum.xda-developers.com/android/general/kitkat-rooting-to-roms-t3560777/post71153851
Try the porting method here
have u replaced whole soundfx folder????
@ki said:
have u replaced whole soundfx folder????
Click to expand...
Click to collapse
yes
In my search to find a way to disable the fixed bootanimation on my X96 I not only found the solution but also some nice "feature".
A normal bootanimation comes as a bootanimation.zip and usually without sound.
A video boot is a MP4 file with sound and all
To enable video boot a line in the build.prop needs to be edited/added:
service.bootvideo=1 this enables the bootvideo, service.bootvideo=0 makes use of the normal bootanimation.zip, same for not having this line.
The actual bootvideo is as said a MP4 file named bootvideo and is located in the etc folder of the system partition - if not you need to make one
Any resolution the box supports can be used here but for obvious reasons it should be only as long as the actual boot might take.
There should be a file bootplayer inside the /system/bin folder - this is used to play the video.
In case it still won't work with all the above files you need to add a service in the init.amlogic.rc file of your kernel.
Code:
service bootvideo /system/bin/bootplayer /system/etc/bootvideo
class main
user root
group system
disabled
oneshot
I tested and confirmed it works with basically any MP4 video on my X96 but assume it should work the same way on all 3.14 kernels.
Another option, you can do so
Code:
#service bootvideo /system/bin/bootplayer /system/etc/bootvideo
service bootvideo /system/bin/bootvideoplay.sh
class main
user root
group system
disabled
oneshot
and place to /system/bin/bootvideoplay.sh with this
Code:
#!/system/bin/sh
MARK=/data/media/0/Download/bootvideo
if [ -f $MARK ]; then
bootplayer /data/media/0/Download/bootvideo
else
bootplayer /system/etc/bootvideo
fi
If there is a file /data/media/0/Download/bootvideo (internal sdcard) , will be play this video
Nice one!
Did not even consider using a check in the init file - will keep that in mind for sure
Checked the way with the script but no matter what I try it simply shows no video at all.
But works fine by just using the medi folder instead of ETC, SDCARD won't work either.
For the SD it makes no difference is SDCARD is used for the path or the direct mountpoint.
Seems the bootplayer is a bit restricted if it does not run directly as a service.
But can't be bothered too much as I only use one video anyway LOL
Still image
There is a way to remove the X96 image as the first image? I changed the video all ok, but the image before bootvideo remains the same. What is tha file that I need to change? Thanks a lot!!!
That would be the bootlogo, flash a new one or use an app tp change it.
I only exchange them together with the firmware and so far did not bother otherwise.
Downunder35m said:
That would be the bootlogo, flash a new one or use an app tp change it.
I only exchange them together with the firmware and so far did not bother otherwise.
Click to expand...
Click to collapse
I searched all the bins for the bootlogo file, but I can't find it. Do you know in wich bin it is located?
No bin, inside the bootloader partition
Downunder35m said:
No bin, inside the bootloader partition
Click to expand...
Click to collapse
Hi, friend. Thanks for your reply. I'm a bit newbie. How can I access the bootloader partition and access its contents?
Downunder35m said:
In my search to find a way to disable the fixed bootanimation on my X96 I not only found the solution but also some nice "feature".
A normal bootanimation comes as a bootanimation.zip and usually without sound.
A video boot is a MP4 file with sound and all
To enable video boot a line in the build.prop needs to be edited/added:
service.bootvideo=1 this enables the bootvideo, service.bootvideo=0 makes use of the normal bootanimation.zip, same for not having this line.
The actual bootvideo is as said a MP4 file named bootvideo and is located in the etc folder of the system partition - if not you need to make one
Any resolution the box supports can be used here but for obvious reasons it should be only as long as the actual boot might take.
There should be a file bootplayer inside the /system/bin folder - this is used to play the video.
In case it still won't work with all the above files you need to add a service in the init.amlogic.rc file of your kernel.
Code:
service bootvideo /system/bin/bootplayer /system/etc/bootvideo
class main
user root
group system
disabled
oneshot
I tested and confirmed it works with basically any MP4 video on my X96 but assume it should work the same way on all 3.14 kernels.
Click to expand...
Click to collapse
Hello,
I set the 1 in the build.prop, added the line to the init.amlogic.rc and put my mp4 intro video and your attached files to the places. 1. Reboot -> I become your x96 bootvideo. I deleted the bootvideo file from your attached files and I dont become a bootvideo. Whats wrong? My bootvideo.mp4 is already in the system/etc/
getting permission error
unfortunately, I am getting permission issue. I have verified that I am root and write permission to root. I am using X96mini Amlogic Box . any help?
p281:/ # whoami
root
p281:/ # cp /sdcard/virtukiosk-video-v1.mp4 /system/etc/bootvideo1
cp: /system/etc/bootvideo1: Read-only file system
1|p281:/ # ls -ld /system/etc/bootvideo
-rw-r--r-- 1 root root 9149031 2017-10-09 09:31 /system/etc/bootvideo
p281:/ # ls -ld /system/etc
drwxr-xr-x 13 root root 4096 2017-10-09 09:48 /system/etc
p281:/ # ls -ld /system
drwxr-xr-x 20 root root 4096 2018-01-04 17:49 /system
p281:/ #
Thank you! works perfectly.
I just edit the build.prop seems it was there (bootvideo and bootplayer) already in my MXIII S802 box.
@ nigam214
Try to use EZ Explorer or any Root explorer for easy File transfer.