Hello!
Did anybody allready found the way to integrate updates of system apps into rom? On 5.0.1 you have just simply copy app and lib folder from /data/app to /system/app, but it seems that this isn't work any more.
Any working solution is appreciated.
Regards, Zagor
@rootSU, @_MetalHead_, @Elluel, @jd1639, ..., maybe?
5.1 hasn't even been released for my device yet
I have a connected issue.
I cannot convert apps to system apps as it says there isn't enough space in \system. It worked fine on 5.0.1 so what they done???
mcnob said:
I have a connected issue.
I cannot convert apps to system apps as it says there isn't enough space in \system. It worked fine on 5.0.1 so what they done???
Click to expand...
Click to collapse
It's not about the space. You can get it by removing some unnecessary apps. The problem is, that if you integrate an app, system somehow woudn't recognize it anymore.
zagorteney said:
It's not about the space. You can get it by removing some unnecessary apps. The problem is, that if you integrate an app, system somehow woudn't recognize it anymore.
Click to expand...
Click to collapse
Sorry zagorteney, I haven't tried to do what you're asking.
Sent from my Nexus 5 using XDA Free mobile app
I'm still on 5.0.2 as I haven't merged 5.1 into my source yet.
I'm on 4.4.4 still so I can't really help you. Sorry.
What apps are you trying to integrate? Some app's lib files sometimes need to be on the /system/lib folder in order for them to work. 5.1 is also ODEX'ed.
I had issues doing it also. Didn't care enough to dig into it. Not a big deal, just execute the APK to update.
happiness4u said:
What apps are you trying to integrate? Some app's lib files sometimes need to be on the /system/lib folder in order for them to work. 5.1 is also ODEX'ed.
Click to expand...
Click to collapse
I'm trying to integrate all updated Google apps. About lib's files you mentioned: it was on 4.4.4, that you have to exctract apps and copy apk to /system/app and corresponding libs to /system/lib. You have also to give them correct permissions. Actually, you have to be carefull and copy libs from PrebuiltGsmCore (or Google Play Services, if you like) last one. Otherwise you got force closes.
On 5.0.1 it was much easier. You just have to move apk and Lib folder from /data/app/ to /system/app or /system/priv-app. Permissions is allready ok. Cleaned dalvik (ART) cache and voila. You have integrated system apps (no need to have them on phone two times).
On 5.1 there are some strange things, that I can't figure it out. For example: if you move updated apk to /system/app it's somehow not installed anymore. I try do all possible ways, one of attempt succeeded, but when I try to do exactly the same with another one, it fails.
Also, I think, that actually problem with Xposed is somehow related to this behavior.
Sorry I'm mentionig you folks again, but because you are profs, you can maybe use this info also on Xposed thread.
@rootSU, @jd1639, @Elluel, @_MetalHead_ -know that you are stuck in stone age, but anyway , @Aerowinder, @Primokorn
zagorteney said:
know that you are stuck in stone age, but anyway
Click to expand...
Click to collapse
Not my fault google decided to update the crappy Nexus 5 before the mega Nexus 6
rootSU said:
Not my fault google decided to update the crappy Nexus 5 before the mega Nexus 6
Click to expand...
Click to collapse
Come on. Now Nexus 5 is crappy. You show-off.
zagorteney said:
Come on. Now Nexus 5 is crappy. You show-off.
Click to expand...
Click to collapse
Mine was ,yes. Severe endfire / noise cancellation issues once lollipop dropped I couldn't make a call without editing the build.prop. Which means I cannot even sell the device to get money. Very annoyed.
rootSU said:
Mine was ,yes. Severe endfire / noise cancellation issues once lollipop dropped I couldn't make a call without editing the build.prop. Which means I cannot even sell the device to get money. Very annoyed.
Click to expand...
Click to collapse
But, this is not lollipop related. It must be something with hardware.
Likewise. Still on 5.0.2 atm. I can tell you that much.
zagorteney said:
But, this is not lollipop related. It must be something with hardware.
Click to expand...
Click to collapse
It's Nexus 5 related, hence my statement "crappy Nexus 5"
zagorteney said:
Also, I think, that actually problem with Xposed is somehow related to this behavior.
Sorry I'm mentionig you folks again, but because you are profs, you can maybe use this info also on Xposed thread.
Click to expand...
Click to collapse
Not sure why Xposed is relevant. Xposed involves so much more possible things that could break.
Elluel said:
Not sure why Xposed is relevant. Xposed involves so much more possible things that could break.
Click to expand...
Click to collapse
Of course you are wright. But till 5.1 Ive never noticed such a "strange" behavior of android system.
So this is just my humble opinion.
P.S. Further conclusions: You can simply make any other app as system one, but still no with updates.
@rootSU
Any news on this, now that you have got 5.1 too?
Related
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
EDIT: I know that there are other posts describing how to do this but I found that they either didn't work for me or involved more complex steps. I'm sharing this because i found it to be easier and completely successful.
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
stearic said:
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Click to expand...
Click to collapse
thanks, but i knew that. i dont think you can just download it, as i did that and it didnt work so well. i know there are other methods, but those are sketchy and involve flashing a new recovery (the all in one installer). this is a more clean way that i got it to work.
just trying to share my experience
also this does not involve flashing anything
Nope, i changed the build.prop file, rebooted and it showed up in the market. Installed it and it works perfectly. The method i mentioned did say you to flash stuff, but that's with the touchwiz based roms. But it also does say pretty much do what you have said as well.
Insufficient privleges
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
GSHARPE3 said:
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
Click to expand...
Click to collapse
Yeah I got the same error, running rooted stock.
crazymadbaby said:
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Doesn't work.
It tells me i'm an unsupported device.
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
Yeah that just means you need to flash the Touchwiz libs zip file that's floating around the forums, then Wallet will work. I have the .zip file here: https://www.dropbox.com/s/lp7qj8odmhobwtu/D2VZW-Wallet-TW-JB-R81.zip
bogedy said:
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
Click to expand...
Click to collapse
Can I change these values in build.prop back after google wallet is working, or no?
not for stock samsung
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
this is for cm 10/10.1
specialkcf said:
Can I change these values in build.prop back after google wallet is working, or no?
Click to expand...
Click to collapse
nope, but why would you need to? it basically makes it so that you able to get through any barriers verizon put in your way for any app
Device not Ready
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
krmtdfrg said:
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
Click to expand...
Click to collapse
sorry i didnt see this. if its still an issue, which im assuming its not, more details please?
I've been holding off on unlocking my TF700 because I'm afraid of losing DRM, but I
don't really know what the effect will be.
I've been reading this forum for a few months, and I've seen a few bits, but
I'm hoping that people here can add to this.
Apps that lose ability to play HD videos as a result of unlock-caused DRM loss:
Google Play
Apps that lose ability to play HD, but there's a workaround:
Hulu+
Apps that are reportedly not negatively affected by unlock-caused DRM loss:
Netflix
Apps that I use that I'm hoping won't be affected by unlocking
HBO Go
Time-Warner Cable customer video/tv app
Can anyone provide any details on which other apps are affected/not affected
by this?
I am just getting started with the Infinity myself - flashing CROMI as i type, actually.
On flashing, CROMI does give the option to fix DRM specifically for the Hulu+ app. I can't say from personal experience whether it works, though I imagine that it would have come up in the threads if it did not.
bruinhoo said:
I am just getting started with the Infinity myself - flashing CROMI as i type, actually.
On flashing, CROMI does give the option to fix DRM specifically for the Hulu+ app. I can't say from personal experience whether it works, though I imagine that it would have come up in the threads if it did not.
Click to expand...
Click to collapse
He's interested in "HBO Go and Time-Warner Cable customer video/tv app'", CROMI will only works for Hulu+, Netflix and Google Play Movies(SD only, no HD). Since I don't HBO or Time-Warner Cable I can't test them.
Everyone, feel free to post about apps I didn't mention -- apps that depend on DRM that get broken by unlocking, apps that you might worry about that aren't affected. Even if I'm not interested, I'm sure others will find it useful, and it would be great if this thread turned into an exhaustive source of information on the subject, as there does not appear to be any other place with the info all in one place.
buhohitr said:
CROMI will only works for Hulu+, Netflix and Google Play Movies(SD only, no HD).
Click to expand...
Click to collapse
buhohitr: Does "SD only, no HD" apply to all three of Hulu+, Netflix and Google Play, or just Google Play?
bsammon said:
Everyone, feel free to post about apps I didn't mention -- apps that depend on DRM that get broken by unlocking, apps that you might worry about that aren't affected. Even if I'm not interested, I'm sure others will find it useful, and it would be great if this thread turned into an exhaustive source of information on the subject, as there does not appear to be any other place with the info all in one place.
buhohitr: Does "SD only, no HD" apply to all three of Hulu+, Netflix and Google Play, or just Google Play?
Click to expand...
Click to collapse
Just Google play. Everything else I mentioned worked as expected.
buhohitr said:
Just Google play. Everything else I mentioned worked as expected.
Click to expand...
Click to collapse
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
bsammon said:
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
Click to expand...
Click to collapse
No that's not correct. When you install CROMI, and during the installation, just select Hulu+. After boot up, you just go to the market and download Hulu+ and it will work as normal.
bsammon said:
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
Click to expand...
Click to collapse
As Buhohitr says that was a previous way of using it. We figured out how to get the full market app working on CROMI a few versions back so now you just choose the option from the installer and it puts the correct files in place.
sbdags said:
As Buhohitr says that was a previous way of using it. We figured out how to get the full market app working on CROMI a few versions back so now you just choose the option from the installer and it puts the correct files in place.
Click to expand...
Click to collapse
What if you don't use CROMI? Is there a workaround that applies to other ROMs or (if you're weird enough) a stock ROM?
bsammon said:
What if you don't use CROMI? Is there a workaround that applies to other ROMs or (if you're weird enough) a stock ROM?
Click to expand...
Click to collapse
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
buhohitr said:
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
Click to expand...
Click to collapse
Where do we find this library file that needs to be named lib.org? There are no files under /system/vendor, only directories.
lunatic_fringe said:
Where do we find this library file that needs to be named lib.org? There are no files under /system/vendor, only directories.
Click to expand...
Click to collapse
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
sbdags said:
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
Click to expand...
Click to collapse
Thank you, I misunderstood. Does a symlink suffice to allow both to function? I don't use google play often but it would be good to know.
buhohitr said:
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
Click to expand...
Click to collapse
I had interpreted this as saying "lib.org" was for Hulu+
sbdags said:
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
Click to expand...
Click to collapse
But this is saying that "lib" is for Hulu+.
Which is it?
bsammon said:
I had interpreted this as saying "lib.org" was for Hulu+
But this is saying that "lib" is for Hulu+.
Which is it?
Click to expand...
Click to collapse
lib is for hulu+ and lib.org is for Google play movies. After you made the change, you will need to reboot the device. Sorry for the confusion.
HBOgo on Comcast works. I found that flixter / Ultraviolet don't work. Do I just not realize that my tf700 isn't playing back the Google play movies in HD?
buhohitr said:
lib is for hulu+ and lib.org is for Google play movies. After you made the change, you will need to reboot the device. Sorry for the confusion.
Click to expand...
Click to collapse
Okay... didn't have access to my TF700 for a few days. Now that I do, I'm checking on this.
My ICS .26 stock install has "/system/vendor/lib/", but no "/system/vendor/lib.org/" .
So, if I unlock this, the stock system should still work with Hulu+, but I'd need to symlink /system/vendor/lib/ to /system/vendor/lib.org/ to get Google Play working as well? (but only in SD?)
bsammon said:
Okay... didn't have access to my TF700 for a few days. Now that I do, I'm checking on this.
My ICS .26 stock install has "/system/vendor/lib/", but no "/system/vendor/lib.org/" .
So, if I unlock this, the stock system should still work with Hulu+, but I'd need to symlink /system/vendor/lib/ to /system/vendor/lib.org/ to get Google Play working as well? (but only in SD?)
Click to expand...
Click to collapse
Not sure you can have them working at the same time. Google play doesn't like seeing the lib folder...... Hence you rename it you effectively hide the files inside.
I think there is still nobody who tested if making a backup of the DRM key before unlocking and restoring it afterwards leads to success.
In case anyone wants to try: The partition to backup and restore is /dev/block/mmcblk0p6. You must save its contents before unlocking (e.g. with dd) and then restore it.
_that said:
I think there is still nobody who tested if making a backup of the DRM key before unlocking and restoring it afterwards leads to success.
In case anyone wants to try: The partition to backup and restore is /dev/block/mmcblk0p6. You must save its contents before unlocking (e.g. with dd) and then restore it.
Click to expand...
Click to collapse
Hmm... tried this:
Code:
[email protected]:/ $ mkdir /mnt/sdcard/backups/
[email protected]:/ $ dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/backups/mmcblk0p6.bak
/dev/block/mmcblk0p6: cannot open for read: Permission denied
do I need to be rooted to do this, or did I get it wrong in some other way?
Also, I'm not sure how to verify that this worked, as I don't currently have any DRMed content that I use. I would need a pointer to a (preferably free and HD) known-DRM content that I could verify this with.
Hey guys, I was wondering if anyone knew how long it normally took for google app update rollouts. Apparently version 3.4 of google search came out last Wed. When I look at the app in the play store it says the last update was on May 2nd. What's weird is when I scroll down it says that the update is 3.3 (which is what I have). Also, when I look at reviews, the ones from May 2nd show up as "old version". I tried this on my N5, N7 2013, and on my sister's N7 2012, and all three devices are the same. The N5 and N7 2013 are on the same account and the older N7 is on a different one. I'm using gravity box to change the dpi of my navigation keys on my N5, and I heard sometimes play store messes up when you do that, but seeing as the problem occurs on my non-rooted tablets it can't be that. Anyone else not getting the update?
I used to have that problem with some apps and I'd have to go to Android Police or other external source. But as far as GAPPS are concerned, I'd look at the 0day PA GAPPS thread
1. You won't be monitoring for a new update
2. You have the latest of every Google App
The Nexus 5 advocate (Team Inferno)
TheLastSidekick said:
I used to have that problem with some apps and I'd have to go to Android Police or other external source. But as far as GAPPS are concerned, I'd look at the 0day PA GAPPS thread
1. You won't be monitoring for a new update
2. You have the latest of every Google App
The Nexus 5 advocate (Team Inferno)
Click to expand...
Click to collapse
So even though I have use the stock ROM I should overwrite the GAPPS with those?
You can. All you're essentially doing is overwriting the current GAPPS on your phone located in system/app and system/priv-app with the one from the package. I've done it a few times. Stock and a few aosp ROMs. As always, with anything I'd always make a nandroid better safe than sorry.
Assuming you're only after one app, Android Police releases leaked Google Apps as soon as they have them. Just Google search your title of this thread and Android Police.
The Nexus 5 advocate (Team Inferno)
TheLastSidekick said:
You can. All you're essentially doing is overwriting the current GAPPS on your phone located in system/app and system/priv-app with the one from the package. I've done it a few times. Stock and a few aosp ROMs. As always, with anything I'd always make a nandroid better safe than sorry.
Assuming you're only after one app, Android Police releases leaked Google Apps as soon as they have them. Just Google search your title of this thread and Android Police.
The Nexus 5 advocate (Team Inferno)
Click to expand...
Click to collapse
Got it, thanks a lot. I was just curious why it wasn't updating itself on three different devices almost a week after it was rolled out. What I also find weird is, after updating using the android police link, in the play store it still shows 3.3 as latest.
PsychDrummer said:
Got it, thanks a lot. I was just curious why it wasn't updating itself on three different devices almost a week after it was rolled out. What I also find weird is, after updating using the android police link, in the play store it still shows 3.3 as latest.
Click to expand...
Click to collapse
You may need to delete it manually either use a root Uninstaller or Root file Explorer and hunt down the Velvet.apk in system/app or system/priv-app (I can't remember which of the two and delete it and try installing) then try reinstalling the Android Police one. Should work, if not try wiping caches and rebooting.
The Nexus 5 advocate (Team Inferno)
TheLastSidekick said:
You may need to delete it manually either use a root Uninstaller or Root file Explorer and hunt down the Velvet.apk in system/app or system/priv-app (I can't remember which of the two and delete it and try installing) then try reinstalling the Android Police one. Should work, if not try wiping caches and rebooting.
The Nexus 5 advocate (Team Inferno)
Click to expand...
Click to collapse
Wiping cache for play store or google search?
Edit: Hmm, I cleared the data/cache for play store and cache for google search and rebooted still nothing. I guess it's fine though. Hopefully once the next update comes it will fix itself.
PsychDrummer said:
Wiping cache for play store or google search?
Edit: Hmm, I cleared the data/cache for play store and cache for google search and rebooted still nothing. I guess it's fine though. Hopefully once the next update comes it will fix itself.
Click to expand...
Click to collapse
I meant through recovery. However, I did get a Google Search update today. Maybe that was it?
TheLastSidekick said:
I meant through recovery. However, I did get a Google Search update today. Maybe that was it?
Click to expand...
Click to collapse
Yeah, I did as well. Now it's showing everything correctly. Btw, I saw that my thread was moved. I read that app and accessory related questions go in the app and accessory forums, respectively. Was I wrong? If so I'll make sure to put all questions in the Q/A section.
PsychDrummer said:
Yeah, I did as well. Now it's showing everything correctly. Btw, I saw that my thread was moved. I read that app and accessory related questions go in the app and accessory forums, respectively. Was I wrong? If so I'll make sure to put all questions in the Q/A section.
Click to expand...
Click to collapse
I'm not the moderation team, but coming from rules if I understand them correctly all questions about apps/devices pertaining to the device your using goes under the Q&A forum of your device.Glad to see that the official Google app push corrected the information for you. The app may have been installed, but because it wasn't officially pushed to Google Play yet, you weren't seeing the correct version.
After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.
I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.
RoomTenONine said:
I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.
Click to expand...
Click to collapse
I've had this problem. Did a search with Google and it seems others are having this issue. Hopefully Google will have an update to fix.
Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk
nikon120 said:
Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Code 505 is a permissions code. This typically means that the APK file already exists in your /data/app folder. You'll need to locate the APK files in question in the /data/app folder and remove them. You will need root to perform this action.
You came across this problem because you didn't do a wipe of your userdata partition when you jumped from Kitkat to Lollipop. I encountered the same issue because of that reason. I just ended up wiping and starting fresh as my phone hadn't been wiped since I got the device last November.
Click to expand...
Click to collapse
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder
PMamba said:
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder
Click to expand...
Click to collapse
I spent an hour combing through Google group threads trying to get a real answer to this outstanding question. I was perplexed that only two applications of mine refused to install due to this error. The consensus was that the APK file was still there, or some remnants of data related to the application remained on the device that the Play Store service didn't like.
I ended up wiping my device twice:
Once by flashing both the userdata.img and cache.img files, which ended up giving me the storage issue bug on Lollipop. (Showing 16GB instead of 32GB)
Second by performing a factory reset from within the booted OS, which resolved the storage issue.
After that, everything was good to go. Have yet to encounter this error code again.
PMamba said:
After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.
Click to expand...
Click to collapse
I just had to click install again after the error and it worked for me. It was a PITA.
sigh, I've had this issue with terminal emulator
C:\>adb install Term.apk
3966 KB/s (515876 bytes in 0.127s)
pkg: /data/local/tmp/Term.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=jackpal.androidterm.permission
.PREPEND_TO_PATH pkg=com.jrummy.liberty.toolbox]
Click to expand...
Click to collapse
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment
bleets said:
sigh, I've had this issue with terminal emulator
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment
Click to expand...
Click to collapse
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.
PMamba said:
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.
Click to expand...
Click to collapse
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that
bleets said:
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that
Click to expand...
Click to collapse
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.
PMamba said:
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.
Click to expand...
Click to collapse
https://code.google.com/p/android-developer-preview/issues/detail?id=1668
hopefully it'll get sorted...
You'd have thought people testing would have installed enough apps to come across it and if google knew about it in october why not fix it
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
How I solved it
In bootloader mode I flash from the factory image userdata and cache, then I wipe Dalvik, data and cache in TWRP after the first boot I skip the setup just too full factory data reset, in the second boot, I set up everything normal, but instead of restoring from previous devices I set it up as a new device, then I manually download the app that was giving the error, it installed without a problem.
I know is a little too much for an app, but it works for me.
onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
Exactly.
Thank you very much for the tip.
onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently
Jleeblanch said:
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently
Click to expand...
Click to collapse
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.
rootSU said:
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.
Click to expand...
Click to collapse
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk
mattie_49 said:
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I know, that's why you can't install jackpal terminal emulator if you have ROM toolbox installed as it uses the same permissions.
Although you should read up yourself because if you did, you'd know the terminal emulator in rom toolbox force closes on lollipop on the nexus 5.
I understand this is a old thread but I fixed it a way that wasn't mentioned in this thread. Just thought I'd share for anyone googling this issue and finding this. What I did was go into the guest account and uninstall the app that was causing the issue such as snapchat. The way I caused it in the first place was installing snapchat on aptoide which installed it on both my account and the guest account and I decided I didn't want snapchat anymore so I uninstalled it but it was still there on the guest account which caused the error 505 whenever I tried to reinstall snapchat.
Disclaimer: I am not responsible for your actions with your device. You are doing this at your own risk.
Do Moto and Moto Camera force close in the latest nightlies of LineageOS? I have the fix.
Get into TWRP and mount /system/
Then go to /system/framework/
You will see some .jar files starting with "com.motorola.XXX". Just remove them (ONLY THE com.motorola FILES).
Restart your device and it will work.
If Moto Camera doesn't record, uninstall current Moto Camera and flash the camera from here. Thanks to @Alberto97. It installs the camera as a system app and it configures permissions.
If for some reason you erase the wrong file and LineageOS doesn't work, just reinstall the build.
If you have some force closes of something called "Motorola Settings" or similar, just uninstall it with a system app uninstaller.
If it works for you, please tell me in this thread. Thanks to @dimusa .
Just wondering, does this stock camera mod (this is Moto camera btw) work on LOS nightlies or does it need the edits you've mentioned? https://forum.xda-developers.com/moto-g4-plus/themes/stock-camera-t3540473
echo92 said:
Just wondering, does this stock camera mod (this is Moto camera btw) work on LOS nightlies or does it need the edits you've mentioned? https://forum.xda-developers.com/moto-g4-plus/themes/stock-camera-t3540473
Click to expand...
Click to collapse
i can confirm that it is not working in LOS
I will test this modification and comment the results
echo92 said:
Just wondering, does this stock camera mod (this is Moto camera btw) work on LOS nightlies or does it need the edits you've mentioned? https://forum.xda-developers.com/moto-g4-plus/themes/stock-camera-t3540473
Click to expand...
Click to collapse
I haven't tried it, sorry.
Works perfect with latest beanstalk 7.1.1 rom. Flashlight and panorama no issues! Thanks for this guide.
Big thanks to you I was searching for this only.
Working great on my xt1643 night lies 14.1
I want to ask something that if I get back to stock os by using adb , anything will happen to phone? As I have deleted all com.motorala.*** jar files
sumit2021 said:
Big thanks to you I was searching for this only.
Working great on my xt1643 night lies 14.1
I want to ask something that if I get back to stock os by using adb , anything will happen to phone? As I have deleted all com.motorala.*** jar files
Click to expand...
Click to collapse
You won't have any problem changing the ROM or getting back to stock because you are only removing some files from LineageOS/AOSP (and similar ROM) which makes some camera apps not working.
I got back to stock to try some kernels and I didn't have any problem.
Hey man thanks alot for this worked like a charm ??
EvilHowl said:
You won't have any problem changing the ROM or getting back to stock because you are only removing some files from LineageOS/AOSP (and similar ROM) which makes some camera apps not working.
I got back to stock to try some kernels and I didn't have any problem.
Click to expand...
Click to collapse
Many apps also not working which worked on nougat. Do you have solution for this too? They are too force closing
sumit2021 said:
Many apps also not working which worked on nougat. Do you have solution for this too? They are too force closing
Click to expand...
Click to collapse
Which apps don't work? Do they force close?
EvilHowl said:
Which apps don't work? Do they force close?
Click to expand...
Click to collapse
Score hero
Game hacker
And there were some more I don't remember I just uninstalled them
I think that deleting those moto files affects the focusing methods - originally done with both laser focus and phase detect auto-focus (PDAF).
The "normal" focus in Lineage/Cyanogen is contrast-detection, the weakest method (and power intensive).
SoNic67 said:
I think that deleting those moto files affects the focusing methods - originally done with both laser focus and phase detect auto-focus (PDAF).
The "normal" focus in Lineage/Cyanogen is contrast-detection, the weakest method (and power intensive).
Click to expand...
Click to collapse
I also felt some changes in the focus after deleting that files
Sorry I am new to twrp...i followed the steps..i mounted the system from twrp recovery..but how to delete those files can anyone tell me.. Thanks ..
@EvilHowl Yup, it works perfectly on AOSP-CAF ROM after deleting those jar files but I can not change the default storage target to SD card. Any help??
Can I delete the files from within ES File Explorer or it has to be through TWRP Mount?
Edit: yes it can be done and the moto camera works.
I am getting the Moto Settings force close, but a system uninstaller shows two Moto Settings apps, which do I uninstall?
[email protected] said:
Sorry I am new to twrp...i followed the steps..i mounted the system from twrp recovery..but how to delete those files can anyone tell me.. Thanks ..
Click to expand...
Click to collapse
Use the filemanager in twrp
[email protected] said:
Sorry I am new to twrp...i followed the steps..i mounted the system from twrp recovery..but how to delete those files can anyone tell me.. Thanks ..
Click to expand...
Click to collapse
You can use root xplorer for delete the files too
runt said:
I am getting the Moto Settings force close, but a system uninstaller shows two Moto Settings apps, which do I uninstall?
Click to expand...
Click to collapse
I am in the same situation. There are two Moto Settings and don't know which one to uninstall. If they are not needed, what do those files do?