i'm a newbie and i'd like to work on a custom cyanogen 6 for my G1.
the problem i'd like to expose you is about a barebone system:
following the wiki
- i remove all unecessaries apps from /system/apps
- re-write signature of the CM
- flash it on my dev
what should i do if i'd like to modify an .apk??
for example:
if in my barebone CM i remove LatinIME.apk and LatinImeTutorial.apk, whenever i reboot my device an error popup display 'till i go to /setting/Lang&Keyboard/ and i disable Android Keyboard.
the system popup error is " Error loading com.android.inputmethod.latin "
how can i avoid system check for com.android.inputmethod.latin at startup?
is it possible to modify setting.apk and simply delete the related menu voice??
if yes how can i do?
if no what should i do to solve this problem?
Related
when i wanted to make my backround setting to be transparent... i search a tutorial on how to transparent all black backround and i do it in my own risk.. i edit a code in framework to make my settings backround transparent, then i follow the tutorial when it done,, click or tap the m/o to m/w and reboot.. after rebooting and try to see the difference .. i open the settings and "wuala" its says settings is "unfortunately settings has been stop" same as with the other apps like root explorer, video player, calculator etc. "has been stop" or error to launch.. i reset my phone nothing happens.. all my apps back to normal and delete the other apps.. but nothing happens.. can you help me ?? i do not have CWM or TWRM.. i also try to connect via pc but i can't activate the usb debugging due to setting has stop.. please their other way to solve ? please help .. im begging.... Sorry for my english thanks for advance
Without knowing what device you have and based on the info you gave here's my advice.
Try other root file managers to replace the nodded settings apk with the original and fix permissions, then reboot.
If you have tried all root file managers with no luck you may need to flash a custom recovery like twrp and use the built in file manager to do this, then use the fix permission option in twrp
One thing that was brought to my attention was whether you properly compiled the apk. Here's the link to the apk tool with instructions on how to properly use it.
http://forum.xda-developers.com/general/xda-university/guide-to-apk-t2924108
Installed frameworks(was throwing error before), decompiled systemui, made edits(even tried without making edits), compiled, signed, zipaligned but its not working.
I also tried to update the original apk with winrar(compression level = store),
After I reboot, there is no wallpaper, no status & navigation bar, and systemui is not working.
Device is mediatek, running Kitkat, is there any more info required?
Please help me...
Link to apps :
SystemUI.apk : ge.tt/1Yg8aJQ2/v/0
mediatek-res.apk : ge.tt/5AwWYJQ2/v/0
framework-res.apk(not required) : ge.tt/3LjNYJQ2/v/0
Hello,
Have the following problem whenever I install Xpose Framework and then start cell phone, the apps are indeed all optimized but then comes the error message - unfortunately system ui was terminated - have everything up to date and no longer know what to do .
have sdk23.arm85 framework used
system 23.5.A.0.575 android 6.0.1
Lollipop 5.1 suddenly at every startup: "android is starting, starting apps"
Wiko Rainbow Jam, Lollipop 5.1 stock rom, root access enabled.
Few days ago I installed HEBF: http://forum.xda-developers.com/and...ebf-tweaking-battery-saver-optimizer-t3401341 (please keep in mind that I'm not saying that this app is the culprit of my trouble, so this discussion is not a rant)
Inside HEBF I activated some of the options for saving battery and to improve a little bit the user experience, then, to do a comparison, to see which effectives improvements I could get with this app, I uninstalled HEBF: I clicked on "reset" inside HEBF, I deactivated all the options, I cleared the data and cache (and I made sure that the scripts inside init.d were deleted), and then I uninstalled the app: at the next reboot, now, every time, before to see the home of the launcher, Android is showing a window which tell "android is starting, starting apps": this message will appear for about 5 - 6 seconds, then my phone is able to operate as usual, without any issues.
I contacted the friendly developer of this app, asking him if HEBF maybe left some file or setting on the file system: the developer told me to check at the build.prop file, because such window "android is starting, starting apps", in his opinion, could be related to the "ART fix" option of HEBF, but looking at my build.prop, the
"dalvik.vm.dex2oat-filter=interpret-only"
"dalvik.vm.image-dex2oat-filter=speed"
entries are no longer present in my build.prop file (its content is avaliable here: http://txt.do/583iw)
I checked everything: using a root startup manager I see that nothing of strange is loaded at startup: I used SD Maid to check for leftovers, I used grep to search for the artfix option in every file on my system (by using "dex2oat" as keyword), I wiped the app cache and the dalvik cache by booting inside TWRP recovery, but the "android is starting, starting apps" message is still present at every boot. I'm looking for hints and clues, to get rid of such message. I suspect that maybe there could be some other entry inside some setting file?
Many thanks.
EDIT: I forget to mention the fact that I booted Lollipop in safe mode, but the message was still present.
The Parse Error in Android devices is one of the oldest and most common error faced by Android users. The error usually pops up when one tries to install an app on his Android phone. The message appears "Parse Error: There was a problem parsing the package". It turns out to be "the application cannot be installed on your phone due to an issue with the parsing.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Causes of the Parse error in Android.
Before we proceed to the fixes, let’s see what can cause this error. There are several known causes today. The parse error occurs while installing an Android app on your phone. But, the causes can be different.
Making changes to the app’s manifest file (for example, changing the Android OS version).
Damaged or partially downloaded apk file.
Not enough permission to download or install third-party apps from unknown sources.(very rare)
Your Android smartphone OS version or the hardware of your smartphone is not compatible with the app.
Your device security system is blocking a third-party app installation.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Method 1: Allow Apps Installation from Unknown Sources
For the security reasons, the Android smartphone bans you to install third-party apps and software from all sources apart from the Google Play Store. Installing third-party apps from unknown sources can harm your Android phone.
So, if you are trying to install an .apk file, you may face the "Parse Error: There was a problem parsing the package". To fix this and bypass the ban, you should allow app installation from the unknown sources. There is an option in your phone security settings.
1)Go to “Settings”;
2)Then “Privacy”;
3)Find “Unknown Sources” and check the corresponding box. If your are prompted to confirm, tap OK.
4)Go back to the folder where you have the .apk located. Tap on it and install the app.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Method 2: Enable USB Debugging
Enabling USB debugging isn’t really necessary for installing Android apps using the .apk file. Nevertheless some users report that enabling the USB debugging fixed this issue.
To enable USB debugging, you need to enable Developer Option in your Android phone. In doing so, follow next steps:
Go to “Settings”;
Find “About phone” option;
Scroll down to “Build Number”. Tap seven times on it. After 7th tapping you hopefully see a “You are now a developer” message on the screen;
Go back to “Settings”, scroll down to “Developer Options”;
Tap on USB debugging and enable it
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Method 3: Disable Antivirus
The parse error can also occur if your security application is blocking the installation. Most of the Antivirus try to block the installation of the applications that may look untrusted or suspicious. So, if you are trying to install an .apk file, the chance of getting the error is that your Antivirus app is blocking the .apk file and preventing the suspicious installation. Try to disable the Antivirus temporarily and install the .apk file. If your guess is right, you should be able to install the .apk file without receiving any parse error in Android.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Method 4: Damaged or Partially Downloaded .APK File
A damaged .apk file might also be cause of the phrase. Try to download a new apk and install it. See if this can fix the issue. Besides, make sure you download the complete file. In doing so, it is enough to compare the size of prompting and downloaded file. Sometimes, you may partially download a .apk file and face "Parse Error" while installing it.
****************************************************END OF THE ARTICLE***********************************************