[Q] All Widgets display "Problem Loading Widget" - G Tablet Q&A, Help & Troubleshooting

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...

Related

[Project] Incoming MMS Picture Size Fix

Hey all, this would probably be only interesting to those who are receiving 2kb, 160x120 MMS messages. Using TMO-USA as an example, the X10 received large MMS images with 1.6, but I'm guessing it doesn't recognize the uaprofile of 2.1 and now are getting tiny mms images. This could also help others on other networks that have the same problem.
Cyanogenmod has an option to switch the profile. Someone else on XDA has posted some of the changes, and those can be found here.
I'm thinking that since I don't think we can compile a new mms.apk, maybe it's possible to edit the current mms.apk with the uaprofile from a different phone (probably the t717/equinox for the tmo users)? Hopefully it's not encrypted or anything either...
So off I go into root explorer and I can't find any mms.apk in my x10. hmm, so i adb shell into it and still no mms.apk. I can't get too far if I can't find the mms application, lol.
so does anyone know what SE uses for mms? or if I'm just simply not seeing it?
obviously, i'm new to working with android, i'll pick up more as time goes on thanks for any help!
Bah! Just in case anyone else looks, I think I found it... sigh.
I searched through the /data/data/ folder and found a reference to 'ericssson' (part of what would be the normal uaprofile text) in com.sonyericsson.converstations_preferences.xml... converstations, eh? makes sense... and yes, there's a converstations.apk
so far i've unzipped it and found 'mms_config.xml' that has max file size and dimensions... but i think this might be only for outgoing mms...
I could be wrong, but isn't it conversations.apk
EDIT: nevermind, looks like you already found it lol
Curious
Thanks for trying to work on it. I would love to have a fix to these small picture messages on T-mo US. But is it possible that the small picture sizes have something to do with T-mo's services somehow???
motibbs96 said:
Thanks for trying to work on it. I would love to have a fix to these small picture messages on T-mo US. But is it possible that the small picture sizes have something to do with T-mo's services somehow???
Click to expand...
Click to collapse
It was working fine with 1.6 but when the X10 jumped up to 2.1, mms images were small. So to me, that means that the tmobile no longer recognizes the phone and it goes automatically downsizing all incoming images.
What I'm not sure is if TMO checks the url of the phone's uaprof or if it just looks at the url and just checks it against their own database. I'm thinking the latter.
Another thought might be if TMO just looks at the specs that the phone gives. The reason for this last question is because X10 1.6 had a max size of 640x480 (not sure if this was receiving or sending) at 1 meg (tmo only handles 300k max). with X10 2.1, it states a max size of 1600x1200 and a max size of 1 meg. Maybe it thinks 1600x1200 is too big and it hits some trigger on TMO's side to only send the fallback size (160x120)
I would recommend emailing customer service (and for anyone else having the same issue with their respective provider) and seeing if they can add the uaprof of the x10i (url) to their database. I know this UAprof is from the v24 update. I'm not sure if it's any different for the DT update or the first 2.1 update. It's not a permanent solution but it's all we have for now.
I thought I'd also post an update, in case if anyone has any thoughts on what I might be doing wrong or helpful tips.
I searched the entire system directory for any text within the files that might relate to uaprof or udp or anything like that. Nothing. I think in 'normal' Android builds have a mm_property.conf file where we can change the uaprof info. So for now, I'm concentrating on converstations.apk and that specific file isn't located there (or anywhere). SE has to store this info somewhere so I think it's in a different conf file. But for the hell of it, I did a hex search for anything that might be related to uaprof (just in case a text search missed something). Again, nothing.
SE encrypted converstations.apk. So if it's in there somewhere, we have to decrypt it first. I'm looking into and reading on decrypting and repackaging the apk. Seems easy enough - I just need to learn a little more.
APN Settings
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username: (leave this blank)
Password: (leave this blank)
Server: (leave this blank)
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0 (don't know if this is important)
MCC: 310
MNC: 260
APN Type: (leave this blank)
To create APN settings for your Xperia.
1. Go to 'Settings'
2. Select 'Wireless & networks'
3. Browse down to 'Mobile networks'
4. Browse down to 'Access Point Names'
5. Click the Menu (Left) button
6. Select 'New APN'
7. Key in the detail relating to your provider or carrier
8. Then press the radio button to select it
9. Save settings, reboot phone.
To test your network dial the following on your phone dial keypad to get into test mode: *#*#4636#*#*
Thanks for the help, but the issue isn't an APN setting. Just for giggles, I went ahead and changed the default APN settings to this and can confirm that it still receives small images.
So far I've decompiled the apk but haven't found the settings I need to change
Alright. So I've *properly* decompiled the apk (I'm working on the newest X10i build, v435). It references the UXprof url from framework-res.apk. I found where the url is in that file and changed it to the url for the Tmobile G2 (just to see if that change will work). Unfortunately, I need to recompile framework-res.apk and from everything I've read, it's recommended not to do that.
I'll keep on reading to see if I can do it, but has anyone recompiled framework-res.apk for the x10?
totalundone said:
Alright. So I've *properly* decompiled the apk (I'm working on the newest X10i build, v435). It references the UXprof url from framework-res.apk. I found where the url is in that file and changed it to the url for the Tmobile G2 (just to see if that change will work). Unfortunately, I need to recompile framework-res.apk and from everything I've read, it's recommended not to do that.
I'll keep on reading to see if I can do it, but has anyone recompiled framework-res.apk for the x10?
Click to expand...
Click to collapse
I've dealt with framework-res.apk before. It was just to add the Super Circle Battery, but I can tell you what works.
Compiling the APK seems to encrypt the XML files one by one. If you change any of the resources (like adding images), then you also need to compile a new resources.asrc. Fortunately, since it's a system file, you don't need to sign the APK.
Check this thread for lots of good info on modifying framework-res.apk (thanks to _calum_ and MrRusch):
http://forum.xda-developers.com/showthread.php?t=834806
Important points:
- The XML files and resources.asrc need to be compiled.
- The APK doesn't need to be signed.
- You can compile the XML and resources.asrc with APK Manager, then extract them from the "unsigned" APK it creates, and then reinsert them into a copy of the original APK using WinRAR (or your favorite zip tool).
- Compression should be set to "store" (a.k.a. no compression).
Be sure to have a backup copy of your original framework-res.apk. It's best to leave a copy on your SD card somewhere.
Be careful when replacing framework-res.apk. Copying it with Root Explorer isn't a good idea. I think the permissions get screwed up or something, and you don't have time to change it because it reboots right away. It's better to copy it onto your SD card and use the dd command through ADB.
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
Click to expand...
Click to collapse
If you mess up, then you may not be able to boot the phone. Don't panic. ADB is still available even when it hasn't booted yet, so just use dd to replace it with your old one.
wow, i never would've thought the picture sizes had to do with my phone. hope you find a fix for this!
Thanks Grospolina! That info should help me a lot.
I actually tried to use root explorer at first... LOL. Stuck at the SE screen and I thought I bricked the phone but found out that my USB port on the monitor has quit working... Wasted a couple hours there. Sigh, lol.
I was using apktool since it's supposed to be framework-res.apk friendly but it kept on compressing the apk. I tried to adb push the file but it kept on saying I didn't have permissions. So I ended up using xrecovery to 'restore' the file in update.zip. I did a test mms but it was still small so I went ahead an cleared the davlik cache. I checked the file size of the modified framework-res.apk but either clearing the cache brought the original apk back or xrecovery update didn't work because the file size was the same as the original (apktools shrunk it down to nearly half).
anyways, I'll try it with that adb line.
There is one issue though. If I open up the original framework-res.apk file in 7zip, the file I need to edit doesn't appear. I'll try this but am not sure what to do if the xml file I need to replace doesn't appear.
bah, i can't ever get adb to replace a file. it always says that it's not writeable and then when i get su permission set, some other error happens. I'll figure it out... still reading... typical adb newbie issue, haha.
I don't have enough time right now (or in the next day) to keep on working on this but if anyone on tmobile usa with an xperia x10 wants to give it a shot, I've linked the apk below. The only change I've done so far is change a couple lines in style.xml. I'm not sure this is it for sure, but I can't rule it out yet.
sorry not trying to be rude or nething but i think you should say that this post is about the picture size...cuz a lot of times iv noticed that when you flash it erases your apn settings which is what you need to receive mms messeges in in the first place... just a thought
No offense taken!
I edited the title to reflect that it's to fix incoming picture mms size.
I hope you don't take offense, but this ISN'T an APN settings issue. I explained it several times earlier and it's been brought up before. It's a problem that been mitigated with custom roms because they have the ability to change their uaprof to something the network recognizes.
Several networks, one of which includes TMobile USA, default to a MMS picture size of 160x120 if it doesn't recognize the phone. This project's intention is to change the default uaprof in order for Tmobile USA (and eventually any other providers) to a uaprof of a supported handset.
mms - framework-res.apk - custom
I was totally on the wrong track with APN settings. Admit I saw MMS and jumped the gun without searching on anything. Had just been through all the baseband compatibility issues and APN setting seemed related
http://forum.xda-developers.com/showthread.php?t=830102 - theeedy - good job working with the settings on the Semc Camera Application, related in the compression of images taken by the default camera.
http://forum.xda-developers.com/attachment.php?attachmentid=355818&d=1278461264
This is MMS.apk - it's an interesting modification, couldn't find it easily within my phone.. decompiling it broke with Unknown Resources, which of course is referencing - /system/framework/framework-res.apk
I think it's related to someone's custom Framework-res.apk and used the default Android MMS app for ease of modifications. I'd say that could be the way to go about this and using the Android SDK in Eclipse or Netbeans is probably the right track.. not APN settings... sheesh! - Grospolina is on the money
package="com.android.mms"
Here are permission sections - might make sense..
Code:
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.RECEIVE_MMS" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.WRITE_SMS" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_DRM" />
<uses-permission android:name="com.sonyericsson.android.permission.SEMC_BACKUP_SERVICE" />
<uses-permission android:name="com.sonyericsson.android.permission.SEMC_CUSTOM_SETTINGS" />
<uses-permission android:name="android.permission.RECEIVE_WAP_PUSH" />
<uses-permission android:name="com.android.mms.wap.permission.READ_PUSH" />
<uses-permission android:name="com.android.mms.wap.permission.WRITE_PUSH" />
<permission android:name="com.android.mms.wap.permission.READ_PUSH" android:protectionLevel="signatureOrSystem" />
<permission android:name="com.android.mms.wap.permission.WRITE_PUSH" android:protectionLevel="signatureOrSystem" />
Now your creating your own Framework-res, you need to know the parts that your looking for and what to do with them.. roughly..
Code:
<service android:name="MmsService" android:permission="com.sonyericsson.android.permission.SEMC_CUSTOM_SETTINGS">
<intent-filter>
<action android:name="com.android.mms.MMS_CUSTOM" />
<action android:name="com.android.mms.MMS_SERVICE" />
</intent-filter>
</service>
From here you can define the properties that you need in the RES layout.. you need something along the lines of this in a file called - image_attachment_view.xml - which would define the image properties you are discussing.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<com.android.mms.ui.ImageAttachmentView android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/image_attachment_view" android:background="@drawable/attachment_editor_bg" android:paddingRight="5.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content"
xmlns:android="http://schemas.android.com/apk/res/android">
<ImageView android:id="@id/image_content" android:layout_width="fill_parent" android:layout_height="150.0dip" android:layout_weight="1.0" />
<LinearLayout android:orientation="vertical" android:layout_width="wrap_content" android:layout_height="wrap_content">
<Button android:id="@id/view_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/view" style="\?android:attr/buttonStyleSmall" />
<Button android:id="@id/replace_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/replace" style="\?android:attr/buttonStyleSmall" />
<Button android:id="@id/remove_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/remove" style="\?android:attr/buttonStyleSmall" />
</LinearLayout>
</com.android.mms.ui.ImageAttachmentView>
EDIT: There are also some better MMS applications out there.. before reinventing the wheel perhaps a bit of window shopping?
No problem! Thanks for the info MrHassell. I enjoy reading your posts (chop full of interesting info, haha)
I'll definitely look into your tips there! SE mucked around with the messaging and they don't use mms.apk but conversations.apk. After decompiling conversations.apk, it references outside of converstions.apk (I'm 95% sure of that) for the uaprof. This (I think) makes sense in that the system needs to tell the network its uaprof.
Other MMS applications depend on this system uaprof to receive images and they too, receive small images. Custom roms get around this because they allow changing the uaprof. However, since SE changed the location of some of the interesting strings, I haven't been able to use AOSP or anything like that as a template to find the strings specifically.
I could use a custom rom, but I'm waiting until a stable, feature filled one is available without having to download X, Y, and Z to get features to work. I like messing with my phone but don't want to mess around with an entire rom (yet, I already did that with a Samsung i7500, lol).
So far, the interesting lines (2) is in framework-res.apk. /res/values/strings.xml
>> <string name="config_useragentprofile_url">http://wap.sonyericsson.com/UAprof/%R202.xml</string> (something like this) and h ttp://wap.sonyericsson.com/UAprof/%R101.xml
Which I changed to
>> <string name="config_useragentprofile_url">http://www.htcmms.com.tw/Android/TMO/Hero/ua-profile.xml</string>
Which is the uaprof for the Tmobile G2.
And just for background...
How I think this all works (if anyone works for tmobile usa and knows, please correct me!)
Phone connects to the network OR when the phone receives an MMS
Advertises it's uaprof capabilities to the network
Network looks at the url and either:
goes to the url and assigns those capbilities to that registered phone
or
looks at the url and looks for that url in a local database. Network finds info and assigns MMS values OR doesn't find it and assigns default 160x120 values. Doesn't go to the internet to find those values.
The X10 worked under 1.6. Why? It was rumored to come to the USA and 1.6 would have had the uaprof on their database for testing reasons. 2.1 comes and TMobile USA has already decided not to carry it so they don't add the new url to their database.
totalundone said:
bah, i can't ever get adb to replace a file. it always says that it's not writeable and then when i get su permission set, some other error happens. I'll figure it out... still reading... typical adb newbie issue, haha.
Click to expand...
Click to collapse
The /system directory is read-only by default. You need to mount it as read/write:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
If that doesn't work, you could try this:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
exit
exit
Click to expand...
Click to collapse
Also, don't forget to check your phone for a "SuperUser" popup and allow it. In the SuperUser app, this shows up as "Unknown".
Thanks again Grospolina!
Evidently I didn't have it approved by superuser. I thought I did... but forgot that I lost it when I had to reflash a few days ago.
I tried the new framework-res.apk. It didn't crash my phone and it was the new size! unfortunately incoming mms photo sizes are still 160x120 max.
Well... I guess I need to get back to searching ...
just want to say thank you for looking into this. i really want to have the mms picture issues worked out.
thanks again

[FREE MOBILE][FreeWifi_secure][WIFI][EAP-SIM] HOWTO

Hi,
In France, the 4th Mobile Operator, FREE, is launching a wifi access for mobile phone. This access is relayed by all the Adsl Box from FREE ADSL.
The SSID of this Wifi Access is "FreeWifi_secure" and it is protect by WPA EAP-SIM.
FREE is solding some android phones with the ability to configure EAP-SIM but they do not share the changes they made it on their Roms.
I use an EVO 3D GSM with KingIceCobra3D 1.2. And i found a simple method to connect to this wifi.
In the file:
/data/misc/wifi/wpa_supplicant.conf
Code:
adb shell cat /data/misc/wifi/wpa_supplicant.conf
ctrl_interface=wlan0
update_config=1
device_type=10-0050F204-4
config_methods="push_button keypad"
[COLOR="Red"]network={
ssid="FreeWifi_secure"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
priority=5
}
[/COLOR]
Add theses Lines in red
Carefull to preserve the rigths of this file after the modification
1) Get the File and rename it to wpa_supplicant.conf
2)
Code:
adp push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
adb shell chown 1000:1010 /data/misc/wifi/wpa_supplicant.conf
adb shell chmod 660 /data/misc/wifi/wpa_supplicant.conf
adb shell ls -l /data/misc/wifi/wpa_supplicant.conf
-rw-rw---- 1 1000 1010 272 May 17 09:10 /data/misc/wifi/wpa_supplicant.conf
adb shell cat /data/misc/wifi/wpa_supplicant.conf
ctrl_interface=wlan0
update_config=1
device_type=10-0050F204-4
config_methods="push_button keypad"
network={
ssid="FreeWifi_secure"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
priority=5
}
FXJumper.
Just checked on mwakious3Drom 4.0 ... works great
remerciements?
tuxstang said:
Just checked on mwakious3Drom 4.0 ... works great
Click to expand...
Click to collapse
I would like +1 on my "thank meter" and you will my first fan ;-)
merci,
fx
Hi Fxjumper,
I'm really interesting in your solution.
I don't find data/misc ...
Can I create it or have I to use a specific file manager.
I have tried with "file manager" and "file expert"
Thanks for your help
Optimus 2X - CM7 Temasek Kang -104
mgl2 said:
Hi Fxjumper,
I'm really interesting in your solution.
I don't find data/misc ...
Can I create it or have I to use a specific file manager.
I have tried with "file manager" and "file expert"
Thanks for your help
Optimus 2X - CM7 Temasek Kang -104
Click to expand...
Click to collapse
Use a root file browser. Root Explorer. Also, be sure to mount it as RW (advanced options)
Thank u for your help.
a) All right : I put the wpa_supplicant.conf into my phone but now i can't activate wifi due to an error
b) what the second code is for ? (what have i to do with this code ?)
thx
Edit : a) it's Ok now after editing the file : i don't have to replace the initial text but to add the red text from fxjumper (i'm an idiot cause that's what he said )
The B) point isn't resolve : what is the code for and when have i to put it inside ?
Hello,
The second code is an example to install the wpa_supplicant.conf file. This replaces your ssid configured.
Your solution is preferable, because you do not remove your existing configuration but add the SSID "FreeWifi_secure".
Sincerely,
fxjumper said:
Hello,
The second code is an example to install the wpa_supplicant.conf file. This replaces your ssid configured.
Your solution is preferable, because you do not remove your existing configuration but add the SSID "FreeWifi_secure".
Sincerely,
Click to expand...
Click to collapse
It works for you????
I did it and it can t connect to the network but it s trying now...
Any idea?
Precisions
(Google traduction --- sorry)
After a few questions in Private Message, here is a method from a blank file and edit it.
i) file format (dos or unix encode)
ii) to file permissions
This is how I propose to proceed
1) recovering the file on the computer
2) we change
3) upload it on the mobile
4) we check the consistency of the file (right)
------------------------
It is left
------------------------
1) I assume the phone is Rooted
we will save the file wpa_supplicant.conf that derail and recreate one:
Code:
adb shell
cd /data/misc/wifi
cp-a wpa_supplicant.conf wpa_supplicant.conf.sav
rm wpa_supplicant.conf
exit
Switch OFF/ON the wifi
Copy the file on the computer
pull adb shell /data/misc/wifi/wpa_supplicant.conf wpa_supplicant.conf
2) To modify the file I suggest you use notepad++
http://download.tuxfamily.org/notepa....Installer.exe
Edit the file, and add at the end
network = {
ssid = "FreeWifi_secure"
key_mgmt = WPA-EAP IEEE8021X
eap = SIM
priority = 5
}
save
3) is the upload
Code:
adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf.new
4) It checks the credentials and the owner and the old file
Code:
adb shell
cd /data/misc/wifi/
ls -l wpa_supplicant.conf
----> -rw-rw ---- 1 1000 1010 185 May 20 5:31 p.m. wpa_supplicant.conf
We crush our file
Code:
cat wpa_supplicant.conf.new > wpa_supplicant.conf
This should solve our problem of right and permissions
we check again:
Code:
ls -l wpa_supplicant.conf
----> -rw-rw ---- 1 1000 1010 185 May 20 5:31 p.m. wpa_supplicant.conf
Sincerely,
Another way, as we most use a custom rooted rom, is to use a rooted filemanager.
For exemple, i use ES File Explorer, set so it accesses /data RW, then edit the file with ES's editor. No need to set back file's permissions.
tuxstang said:
Another way, as we most use a custom rooted rom, is to use a rooted filemanager.
For exemple, i use ES File Explorer, set so it accesses /data RW, then edit the file with ES's editor. No need to set back file's permissions.
Click to expand...
Click to collapse
And it works for you??????
I did it and it can t connect....
Who have it working?????? and what did you do????
B_e_n said:
And it works for you??????
I did it and it can t connect....
Who have it working?????? and what did you do????
Click to expand...
Click to collapse
Hello B_E_N,
In private message, you said you are using a motorola milestone xt720 under cronosx 2.3.7, a cyanogen mod 7 customized.
Now i sent you a patch with /system/framework/com.orange.authentication.simcard.jar
We are waiting your test ...
Sincerely,
CM9 nightlies + SGS
Hello,
I just tried this modification, but cannot find a way to make it work...even though I doublecheck both the permission and the content of the file
For information, I'm running CM9 nightlies for my Samsung Galaxy S.
Until now it doesn't work for me ... even with rom toolbox. Permissions and owners are checked and ok.
Next try : via adb & androisd sdk.
o2x - cm7 - FREE
One more thing : no more error message but wifi try to connect without result ...
o2x - cm7 - FREE
B_e_n said:
And it works for you??????
I did it and it can t connect....
Who have it working?????? and what did you do????
Click to expand...
Click to collapse
Here's how i proceede from ground up on my EVO 3D, with Mwakious, Predator and KingCobra ICS roms.
1/ go in settings and select FreeWifi_secure
2/ set a lock PIN as requested
3/ switch off WiFi
4/ open ES File Explorer
5/ check "Up to Root", "Root Explorer" and "Mount FileSystem" in ES File Explorer settings
6/ navigate to /data/misc/wifi
7/ edit wpa_supplicant.conf
8/ save
9/ switch on WiFi and select FreeWifi_secure
10/ unset lock PIN
Hope it helps.
it was that easy?????
should work on all rooted phone so
works like a charm on my evo
Don't work with my phone...
How do you change owners parameters with ES explorer ?
Regards.
o2x - cm7 - FREE
Hi,
maybe you can use an alternate method on post #11 in
http://forum.xda-developers.com/showthread.php?t=1639437&page=2
what's your phone by the way ?
I'm using CM7.2 on a Nexus One.
I edited the file with ES Explorer, saved, activated wifi...
But doesn't work... It tries to connect but fails.

Moving system apk from stock 4.0 to CM 11

Hi,
I got CM 11 running on my devices (Nexus Q) and want to add some system apk from the stock factory images and need some help. I mounted the factory image and copied TungstenLEDService.apk from /system/app to my computer and tried to install it over adb. This is what I have done so far.
Code:
adb install TungstenLEDService.apk
but it fails with INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Ok fine, its a system apk, so I did the following.
I enabled root over adb on developer settings on the device and from the terminal I did
Code:
adb push TungstenLEDService.apk /sdcard/
adb shell
su
mount -o rw,remount -t ext4 /system
cp /sdcard/TungstenLEDService.apk /system/app/
And then I set the permission with Solid Explorer filemanager to -rw-r--r-- on TungstenLEDService.apk and rebooted. From logcat I got this error
Code:
Package com.google.tungsten.ledservice has no signatures that match those in shared user android.uid.system; ignoring!
What to do next? Do I need to resign the apk? How do I do that? I have not modified the apk in any way and the CM 11 build is from this xda thread: http://forum.xda-developers.com/showthread.php?t=2596910
mannberg said:
Hi,
I got CM 11 running on my devices (Nexus Q) and want to add some system apk from the stock factory images and need some help. I mounted the factory image and copied TungstenLEDService.apk from /system/app to my computer and tried to install it over adb. This is what I have done so far.
Code:
adb install TungstenLEDService.apk
but it fails with INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Ok fine, its a system apk, so I did the following.
I enabled root over adb on developer settings on the device and from the terminal I did
Code:
adb push TungstenLEDService.apk /sdcard/
adb shell
su
mount -o rw,remount -t ext4 /system
cp /sdcard/TungstenLEDService.apk /system/app/
And then I set the permission with Solid Explorer filemanager to -rw-r--r-- on TungstenLEDService.apk and rebooted. From logcat I got this error
Code:
Package com.google.tungsten.ledservice has no signatures that match those in shared user android.uid.system; ignoring!
What to do next? Do I need to resign the apk? How do I do that? I have not modified the apk in any way and the CM 11 build is from this xda thread: http://forum.xda-developers.com/showthread.php?t=2596910
Click to expand...
Click to collapse
3 things that are probably causing issues.
1) it's a signed factory apk, and is looking for a factory rom to work on. You can try re-signing it using basic "test" signature. Also, make sure the apk is "deodexed".
2) Just incompatible with version 4.4 KitKat. In this case, you would probably have to re-write a lot of code.
3) Decompile and check the Android Manifest for anything unusual. Also, while decompiled, check all the folders for the last error message you posted. Might be a clue in there.
Moscow Desire said:
1) it's a signed factory apk, and is looking for a factory rom to work on. You can try re-signing it using basic "test" signature. Also, make sure the apk is "deodexed".
Click to expand...
Click to collapse
How do I deodex the apk / odex files? Any good and easy guides out there? Im a neewbie. Tell me like I'm 4 years old The apk / odex files is from android version 4.0.4
Signing with test signature, do you mean something like this
Code:
jarsigner -keystore ~/.android/debug.keystore -storepass android -keypass android TungstenLEDService.apk androiddebugkey
after the apk is deodoxed?
Moscow Desire said:
2) Just incompatible with version 4.4 KitKat. In this case, you would probably have to re-write a lot of code.
Click to expand...
Click to collapse
I hope not.
Moscow Desire said:
3) Decompile and check the Android Manifest for anything unusual. Also, while decompiled, check all the folders for the last error message you posted. Might be a clue in there.
Click to expand...
Click to collapse
I didnt see anything special in the Manifest, it looks like the one I posted below. Do I need to change android:versionCode and android:versionName?
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:versionCode="15" android:versionName="4.0.4-403218" package="com.google.tungsten.ledservice"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.BROADCAST_STICKY" />
<application android:label="Tungsten LED Service">
<service android:name=".LEDService" android:exported="true">
<intent-filter>
<action android:name="com.google.tungsten.LedService" />
</intent-filter>
</service>
<receiver android:name="BootReceiver">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
</intent-filter>
</receiver>
<service android:name="com.google.tungsten.ledservice.TungstenLedContainer" android:enabled="true" android:exported="true">
<intent-filter>
<action android:name="com.android.athome.START_SERVICE" />
</intent-filter>
<meta-data android:name="com.android.athome.service" android:resource="@xml/connector_info" />
</service>
</application>
</manifest>
mannberg said:
How do I deodex the apk / odex files? Any good and easy guides out there? Im a neewbie. Tell me like I'm 4 years old The apk / odex files is from android version 4.0.4
Click to expand...
Click to collapse
Ha! Can't do that mate. Have to work!
Now, here is what I use for pretty much all my needs when it comes to working with apks and other things.
http://forum.xda-developers.com/showthread.php?t=1619473
They have a pretty good support here at XDA, and also their own website. This saves you having to find all these apktools and such for decompiling, deodexing and stuff, which is a real pain. I use it under Win 7. Might have to install the latest version of Microsoft.net though.
First thing, is make sure your apk is deodexed or not. If it's not, you will see an odex file with the same name in your system folder of your old 4.0.4 files. If it's not, you'll need to deodex it before decompiling. If there's not an odex file, then you can go straight to decompiling. Then, you can look in all the folders and such. Then recompile it back, using the test keys for signing.
As with the manifest, it's possible you need to change the android versions. But the message you had, seems to be looking for something signed specifically for that 4.0.4. Probably a factory signed framework or systemUI.
CM uses unsigned files, or files signed using random testkeys.
You can also check XDA University about porting apps to KitKat. Lots of these folks do this, and port to other devices, so hopefully somebody there can tell you more. Or check the General Android Application Development forums.
MD
I dedoxed the apk and odex files. Changed the manifest and removed the sharedUserId and rebuilt the apk, signed with a test key. Then I copied the the apk to /system/app. So far everything is fine.
I tried to launch the service (tungsten.ledservice) with
Code:
adb shell am startservice -n com.google.tungsten.ledservice/.TungstenLedContainer
and when I check ps in adb shell I see a process called com.google.tungsten.ledservice. But nothing happens when I change the volyme. It should change the leds on the Nexus Q. I checked adb logcat and found this in the log.
Code:
D/AndroidRuntime( 2626):
D/AndroidRuntime( 2626): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 2626): CheckJNI is OFF
D/dalvikvm( 2626): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 2626): Added shared lib libjavacore.so 0x0
D/dalvikvm( 2626): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 2626): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 2626): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
E/cutils-trace( 2626): Error opening trace file: No such file or directory (2)
D/dalvikvm( 2626): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
E/memtrack( 2626): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 2626): failed to load memtrack module: -2
D/AndroidRuntime( 2626): Calling main entry com.android.commands.am.Am
D/AndroidRuntime( 2626): Shutting down VM
This service use some library from /system/lib/, libled_service_jni.so and libtungsten_led.so. I guess some changes were made to the jni stuff between android 4.0.4 and 4.4. Is this fixable? Is it the java code that fails or the compiled c librarys?

[Q] How do I get media_rw folder to be read write accessible?

I have a rooted Galaxy S3 running 4.4.2 kitkat and been trying to do what I thought be simple thing and get the media_rw folder to be read write accessible.
I can do it using Root Browser as my file manager and change the permissions and it work until phone is rebooted the the permissions revert back to what they were.
I read too many threads on cures and a lot have to do with editing the platform.xml file which has been done and checked with one of the apps use to check it. I tried writing a bootup script to set permission on every boot using ROM Manager but that did not work either.
So I figure I would ask here to find out from the informed people here as to why this has this been such a pain to get working or what I am hoping is someone set me straight and tells me how to fix the problem.
Any comments on making permissions stick using android work or even why it wont work would help. I am not familiar with linux based systems just windows.
Just giving this thread a bump as per the rules to get it unburied here.
https://play.google.com/store/apps/details?id=nextapp.sdfix
https://play.google.com/store/apps/details?id=jrummy.sdfix
http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521
es0tericcha0s said:
https://play.google.com/store/apps/details?id=nextapp.sdfix
https://play.google.com/store/apps/details?id=jrummy.sdfix
http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521
Click to expand...
Click to collapse
I had tried 2 of the fixes before just tried the xposed one and still have the same problem.
The only problem I been having is to use Titanium Backup "Protect This Backup" option as I am getting operation failed when I use it.
The workaround for me was to change media_rw folder to 777 permissions which I did by using Root Browser.
The problem with that was once I rebooted the phone the permission are reset and cant access folder anymore.
I needed use this path to make Protect This Backup work /mnt/media_rw/extSDCard/TitaniumBackup
If there another path I can use that be fine too.
Make Titanium a /system/app and reboot. That should allow you to do that, I think...
es0tericcha0s said:
Make Titanium a /system/app and reboot. That should allow you to do that, I think...
Click to expand...
Click to collapse
I did that I made TB a system app and rebooted.
I could not access media_rw folder and tried protect the bacckup with /storage/extSdCard/TitaniumBackup path same result operation failed when I tried it.
Grab you system/etc/permissions/ platform.xml edit with notepad ++ or any text editor. Make sure your permissions looks like this for the sdcard:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Should fix your problem
lacoursiere18 said:
Grab you system/etc/permissions/ platform.xml edit with notepad ++ or any text editor. Make sure your permissions looks like this for the sdcard:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Should fix your problem
Click to expand...
Click to collapse
I been working backwards on this thread just trying to get rw permissions for media_rw folder I have read and tried a lot of things unsuccessfully to work and here is my edited platform.xml file to examine and you can tell me if my edits were wrong but I think there are good.
lacoursiere18 said:
Grab you system/etc/permissions/ platform.xml edit with notepad ++ or any text editor. Make sure your permissions looks like this for the sdcard:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Should fix your problem
Click to expand...
Click to collapse
I am kinda new to android and linux permission so how does adding <group gid="media_rw" /> to the platform.xml file change things?
Does it change the media_rw/ folder to make it R/W?
techmanc said:
I am kinda new to android and linux permission so how does adding <group gid="media_rw" /> to the platform.xml file change things?
Does it change the media_rw/ folder to make it R/W?
Click to expand...
Click to collapse
Correct. You have to reboot your phone after you apply these changes as well..
EDIT:
https://www.dropbox.com/s/n9lcyu7b2vnym3q/platform.zip
You forgot to add READ_MEDIA_STORAGE
lacoursiere18 said:
Correct. You have to reboot your phone after you apply these changes as well..
EDIT:
https://www.dropbox.com/s/n9lcyu7b2vnym3q/platform.zip
You forgot to add READ_MEDIA_STORAGE
Click to expand...
Click to collapse
I installed your platform.xml file you uploaded it had like 10 more lines than my file hoping it would work but I am getting a lot programs crashing now. I can replace file with the one I was using no problem but any idea why this platform.xml file not working?
It looks like its not seeing my SD card now just internal card
I just reinstalled my backup as the platform.xml was not working and was getting a lot apps to crash. I was able to restore my original platform.xml but still was having same problems with apps popping error messages. The 3 apps I used showed my phone should be working right but I cant access the media_rw folder using Titanium Backup to path it to /mnt/media_rw/extSDCard/TitaniumBackup which was only way I could get Protect This Backup feature to work. I am assuming that Titanium Backup is the problem but still cant get it to work.
Maybe someone has a Galaxy S3 4.4.2 than can post there platform.xml if there's is working with this problem.
So where nothing has worked its hard to see how the changes were supposed to work. Would it allow me to access the media_rw folder by changing its permissions or how does it work. I can do anything else with my phone and apps so not sure if its the problem or TB. Any insight would be helpful as I still learning how android OS works. Also have nandroid of phone so I can revert back it needed.
https://play.google.com/store/apps/d...=nextapp.sdfix
https://play.google.com/store/apps/d...d=jrummy.sdfix
http://forum.xda-developers.com/xpos...orage-t2693521
techmanc said:
I just reinstalled my backup as the platform.xml was not working and was getting a lot apps to crash. I was able to restore my original platform.xml but still was having same problems with apps popping error messages. The 3 apps I used showed my phone should be working right but I cant access the media_rw folder using Titanium Backup to path it to /mnt/media_rw/extSDCard/TitaniumBackup which was only way I could get Protect This Backup feature to work. I am assuming that Titanium Backup is the problem but still cant get it to work.
Maybe someone has a Galaxy S3 4.4.2 than can post there platform.xml if there's is working with this problem.
So where nothing has worked its hard to see how the changes were supposed to work. Would it allow me to access the media_rw folder by changing its permissions or how does it work. I can do anything else with my phone and apps so not sure if its the problem or TB. Any insight would be helpful as I still learning how android OS works. Also have nandroid of phone so I can revert back it needed.
https://play.google.com/store/apps/d...=nextapp.sdfix
https://play.google.com/store/apps/d...d=jrummy.sdfix
http://forum.xda-developers.com/xpos...orage-t2693521
Click to expand...
Click to collapse
Have you tried an app called FolderMount? You might want to give that one a go. It requires a reboot after the changes are detected and changed..
lacoursiere18 said:
Have you tried an app called FolderMount? You might want to give that one a go. It requires a reboot after the changes are detected and changed..
Click to expand...
Click to collapse
I tried it said it had to patch to fix something which seemed to work but when I tried to path it to use it you need to start from path /storage/emulated/0 so could not even get to media_rw folder to add to path to so I assuming with this app you cant go to the root folder to setup a folder to move. I hope I explained this right.
Anyone out there thats using Titanium Backup which was only way I could get Protect This Backup feature to work running 4.4.2 kitkat os and how did they get it to work?
techmanc said:
I tried it said it had to patch to fix something which seemed to work but when I tried to path it to use it you need to start from path /storage/emulated/0 so could not even get to media_rw folder to add to path to so I assuming with this app you cant go to the root folder to setup a folder to move. I hope I explained this right.
Anyone out there thats using Titanium Backup which was only way I could get Protect This Backup feature to work running 4.4.2 kitkat os and how did they get it to work?
Click to expand...
Click to collapse
Did reboot after it patched? If not do so then try the TB feature
lacoursiere18 said:
Did reboot after it patched? If not do so then try the TB feature
Click to expand...
Click to collapse
Did not work.
The path I am using with TB as my Backup folder location is when I cant access media_rw folder due to permissions is
/storage/extSdCard/TitaniumBackup and everything in TB is working except Protect This Backup.
Now I just gave RW permissions to media_rw folder and use this path in TB folder location to
/mnt/media_rw/extSdCard/TitaniumBackup
and I can protect and unprotect files with TB but I have to manually set the permissons to media_rw folder none of the tweaks have done that.
One of the thread I was looking at suggested to use a script to add permissions on bootup but did not work for me either.
I know I am being thick headed about making this work just irks me when I cant find the solution....
Here is the other threads link.......
Titanium Backup "Protect This Backup" fails
http://forum.xda-developers.com/showthread.php?p=54701863
added couple screenshots of using TB
Any way to add a script to add RW permissions to the media_rw folder when booting the phone so folder can be accessed?

Video bootanimation on Amlogic boxes

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.

Categories

Resources