Related
Hiya,
due to my brother not having the luck of having Froyo on his phone I took a look at it and hacked the newst YouTube app to work with Eclair. I had to remove two calls and add android.util.base64 which was introduced with Froyo. However, it should work flawlessly. If you encounter any problems, feel free to post here along with a little description and if possible a logcat dump of the exception.
Download:
http://ul.to/emt639
Old Download:
- http://ul.to/kxu37d
- http://www.mediafire.com/?5bdc88opu6qt9nz
You have to remove the default YouTube app before you can install this one over.
Using ADB Shell this should just work:
adb remount
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
then you can just install it over using the package manager or with adb (adb install YouTube_signed.apk).
Hope this helps, enjoy the re-designed Youtube app!
Tested. Work well on Floyo 1.01. Great work.
Just tested it, and it works on eclair.
btw, is it possible to port the froyo gmail app to eclair?
EDIT: after further testing, it force closes. the process used to get to a force close was i logged in to my youtube account, exited the app, opened skyfire (it forced closed, perhaps of youtube. however i am not sure), reopened the youtube app but it forced close. i reverted back to the older youtube (stock) and repeated the process above, and no force closes in skyfire or youtube
t2k269 said:
Tested. Work well on Floyo 1.01. Great work.
Click to expand...
Click to collapse
Why not,it`s a Froyo 2.2 ROM so you can use the original too
http://www.appbrain.com/app/youtube/com.google.android.youtube
thanks alot it works in 2.1 in spica ..
How did you decompile the original apk? If i may ask...
It worked for me at the first start, but then it gives me force closes every time I try to start it. I restarted my phone, tried to reinstall the app, but nothing helped. Anybody has the same problem?
I can only use the app again if I go to Settings/Applications and delete cache and data from YouTube. Is there any way to avoid deleting these all the time? FC mainly occurs after I login to my account. Thanks
Updated it
http://ul.to/emt639
Changed a API call that would require Froyo. Should work better now.
Works great. Cheers!
rolle3k said:
Updated it
Changed a API call that would require Froyo. Should work better now.
Click to expand...
Click to collapse
Thank you rolle3k for your work. I just tried the fixed version, but it still gives force closes when I am logged onto my account. The problem might be around logging in to an account, because when I'm not logged on, it works.
sempi601 said:
Thank you rolle3k for your work. I just tried the fixed version, but it still gives force closes when I am logged onto my account. The problem might be around logging in to an account, because when I'm not logged on, it works.
Click to expand...
Click to collapse
Thanks for the suggestions. I'll check that out.
this app is awesome!!!!! .. smoother than ever!! ... thanks mate...
Not sure if this is just me but it doesn't open now, I just get an instant FC no matter how or where I open the app from. Any ideas?
Yep, it seems logging into your account breaks it.
Installed it on HTC Gratia Froyo port, works great
I just got into the setting, applications, manage applications, found it and uninstalled it, then installed the new one, and it works great...
Ganii said:
Why not,it`s a Froyo 2.2 ROM so you can use the original too
http://www.appbrain.com/app/youtube/com.google.android.youtube
Click to expand...
Click to collapse
Really... haha, didn't pay attention to update of YouTube app. Removed and use the original one. Thanks for your info.
Yeah, its the same
hello all,
i removed youtube and tried to install this but it gives error as "application not installed". by the way i'm using cronos froyo 1.4.2. any idea?
Hi, I have a problem with that app.
Yesterday I've installed it and worked fine until evening.
Now I got an error everytime I try to open it... I try to restart the device (many times), but nothing's happened.
My Hero got "Tegro 2.1 (Slide Espresso port) [ROM]", any suggestion?
Edit:
I have uninstalled and reinstalled the apk: now it works! I don't know why but it works!
It FCes if i try to start application again after logging in...;/
rolle3k said:
Thanks for the suggestions. I'll check that out.
Click to expand...
Click to collapse
Hello rolle3k! Have you found anything that is causing the Force Close? It is definitely doing this when logged in.
Since then I am using YouTube without logging in and it works great so far. However, it would be great to have the ability to log in without deleting data/cache every time I want to use YouTube.
Could you help us? With that option this app would be awesome. Thanks
I'm running CM7 #211 and yesterday my SUperuser app decided to RANDOMLY auto update itself. I didnt even know you could download the superuser app from the Market. Now all my apps are force closing. I uninstalled the update but my ROM is still F'd force closing on everything. I've tried clearing both caches and fixing permissions and it's still messed up. Any ideas? HOW DO I GET SUPERUSER TO NOT AUTO UPDATE?
I wiped my phone and restored to a backup last week and everything seems fine for the moment.... I just need to figure out how to force the market not to auto update any of my apps.
Since froyo rolled out, you have an option in the market to auto update. The part that sucks is this is within each app so if you have thirty apps, then you have to go into all thirty apps in the market and de-select the auto update option.
And yes, SU has been available for some months in the market as well as in XDA.
cowman4000 said:
I'm running CM7 #211 and yesterday my SUperuser app decided to RANDOMLY auto update itself. I didnt even know you could download the superuser app from the Market. Now all my apps are force closing. I uninstalled the update but my ROM is still F'd force closing on everything. I've tried clearing both caches and fixing permissions and it's still messed up. Any ideas? HOW DO I GET SUPERUSER TO NOT AUTO UPDATE?
Click to expand...
Click to collapse
im running CM7 nightly 211 with the newest SU and it works just fine. if you go to the SU app and update the binary it will fix all the FC.
The latest night will have the updated binary and SU in the zip.
Update the binary? Is that done from within the superuser app?
cowman4000 said:
Update the binary? Is that done from within the superuser app?
Click to expand...
Click to collapse
yep go to the app. click menu button then preferences.
at the bottom you will see "tap to check for updates"
that way you can enjoy the new app and have the new binary's. without breaking CM7
Thanks I'll try that.
In TB you can disassociate apps from the market which is very handy so those you don't ever want to update such as themed or custom.
SlimSnoopOS said:
Since froyo rolled out, you have an option in the market to auto update. The part that sucks is this is within each app so if you have thirty apps, then you have to go into all thirty apps in the market and de-select the auto update option.
And yes, SU has been available for some months in the market as well as in XDA.
Click to expand...
Click to collapse
My superuser app was also auto-updated contrary to my will, i feel raped
First i need to say that everything in the update went fine, updated superuser app and binary are up and working OK.
But regarding what you said, i have eclair 2.1 and so i have the old Market 2.3.6. I also have the option "Allow automatic updating" present in all of my apps, so i can use it or not, it is up to me.
BUT the problem is that in Superuser app this option is not available. See pics:
ttp://i297.photobucket.com/albums/mm203/lanosalf/2011-10-7-14-46-19.jpg
ttp://i297.photobucket.com/albums/mm203/lanosalf/2011-10-7-14-46-45.jpg
PS:
Add the "h" to "ttp" to get "http" and complete image link.
The XDA forum board don't let me put images, it says"to prevent spam new users cant post links..." or something That's okay but, in my opinion, links inserted in between [image] should be permitted.
EDIT: ALL OK NOW. When version 3.04 appear in Market, it also appears the option "Allow automatic updating", so know i can uncheck it if i want, and i did...
BenHolliday said:
In TB you can disassociate apps from the market which is very handy so those you don't ever want to update such as themed or custom.
Click to expand...
Click to collapse
On my phone superuser doesn't show up in titanium backup. While other system apps show up in red. If anyone knows a way to make superuser show up in titanium please post it.
Guys, stop freaking out about the SU update. Just do like Synisterwolf said. You'll be fine.
Getting constant f/c on mine, even get them after clicking to update the binary.
Looking over the reviews for SU in the Market many are running into this problem with the latest update.
I had no issues with the update in CM7 but updating past SU app 3.0.2 and binary v2.3.2 running McSense 2.4 was a whole 'nother story. Basically locked down every root permissions app on my phone. Was able to nandroid back to 3.0.2 and disable updating in the market for that ROM. I'll just ignore the nag until the next update.
daj
BTW how are more people not talkign about this? Just about every review across many different roms and phones says the same thing:
http://www.appbrain.com/app/superuser/com.noshufou.android.su
I have no idea if this will help anyone with the SU program or not, or what effects it might have on certain roms.
So after hearing about the force closing on SU I grabbed my phone which I had just updated the binarys on the other day, and today installed a SU update. FC's all over the place as been described. No way to uninstall it from the market, (didn't try the main applications app) so I went to my astro program and from there I was able to uninstall it....well not the entire thing I guess but just the latest updates.
I can now enter back into it without it FC on me. I went to market and made sure auto update was now off and didn't update it when prompted as you open the app.
Seems to work now but I honestly never use it per se unless it prompts me to grant SU permissions when doing something else, so ymmv if doing as I did.
Just thought I'd put it out there in case it helped some folks.
Updated the app to 3.0.5. As long as I don't update the binary past 2.3.2, I'm good running McSense 2.4.
daj
wildstang83 said:
Guys, stop freaking out about the SU update. Just do like Synisterwolf said. You'll be fine.
Click to expand...
Click to collapse
It's very likely that you won't. For me, 3.0.4 worked for the most part, but it never worked with adbWireless. I updated to 3.0.5 and started getting very frequent force closes. Superuser 3 is not ready for prime time. I'm back to superuser 2.3.6.3 su binary 2.3.2 and will stay there for a while.
Ok people this will fix the FC on superuser 3.0.5 with binary 3.0!!!!!
1. Go setting/application/manage applications and clear data on superuser
2. Go to market and install update
3. open superuser and preferences change automatic response to "allow"
The list will not show apps but log will and the first time the app accesses little lag but no FC.
Not sure if you already installed 3.0.5 if will fix... Can try clearing data and then change automatic response.
Tanks RL.
I read something like that lastt night and changing it to "allow" fixed the f/c for me.
But this whole thing is so stupid. So many times someone takes something that is perfectly fine and updates it till it is broken. If it's not broke don't fix it. Especially something as important as this.
rlacrossjr said:
Ok people this will fix the FC on superuser 3.0.5 with binary 3.0!!!!!
1. Go setting/application/manage applications and clear data on superuser
2. Go to market and install update
3. open superuser and preferences change automatic response to "allow"
The list will not show apps but log will and the first time the app accesses little lag but no FC.
Not sure if you already installed 3.0.5 if will fix... Can try clearing data and then change automatic response.
Click to expand...
Click to collapse
Tried again using this except I uninstalled all updates first. Everything looked OK at first but I started getting FCs when opening TiBU. Cleared data for both SU and TiBU and tried again and it worked fine but as I started opening other root apps, the FCs came back. YMMV
daj
Hello, first of all I'd like to apologise if this is not the correct forum to ask about this.
Essentially, I have CM12 on my i9195, it worked perfectly fine for a period of time, but for some reason I am unable to install 3rd-party (non-play store) apps.
I am running the newest (20150206) nightly, and I have unknown sources enabled.
Furthermore, I've already done my fair share of googling, and no I am not using any kind of screen filter app, and I have sufficient memory.
Whenever I attempt to install an apk, it just comes up with 'app not installed' - nothing more.
I have also attempted to install through the terminal (using pm install /storage/emulated/0/Download/app.apk), which resulted in 'Failure [INSTALL_FAILED_DEXOPT]'.
I am completely new to any sort of android related things, so I have no clue how to solve this.
I'd be grateful if someone was able to help me out here.
Cheers
What app were you trying to install.
Usually the error occurs when the package name of the app u are trying to install is same as a preinstalled system app.
I was attempting to install a modded version of Snapchat (without installing any other version of it before).
Only thing that I came up with was moving the apk to its folder in system/app/.
However, the error comes up with with any other app as well, and to say the least moving the apps each time and changing the permissions is slightly inconvenient.
MedzikPL said:
I was attempting to install a modded version of Snapchat (without installing any other version of it before).
Only thing that I came up with was moving the apk to its folder in system/app/.
However, the error comes up with with any other app as well, and to say the least moving the apps each time and changing the permissions is slightly inconvenient.
Click to expand...
Click to collapse
Try recovery and clearing cache and dalvik. Then when you boot up do nothing but make sure allow unknown sources is ticked, then go to filemanager and just install?
There could also be a problem with the modded snapchat version. Try redowning and older or newer version to see if that works.
Cheers,
Sora.
SORAnoDYStopia said:
Try recovery and clearing cache and dalvik. Then when you boot up do nothing but make sure allow unknown sources is ticked, then go to filemanager and just install?
There could also be a problem with the modded snapchat version. Try redowning and older or newer version to see if that works.
Cheers,
Sora.
Click to expand...
Click to collapse
I really hoped it wouldn't come to that, but I did to a full format, which did not help at all.
It is an issue with not only snapchat, but all of the 3rd apps I tried to install.
I guess it might just be an issue with the ART runtime or something, and for now I'll just be converting essential 3rd parties to system apps.
@MedzikPL Did you try to install those apks on other roms. To see if they are working there. That points towards cm12. Which nightly are you running. I will flash cm12 today and i will try to reproduce the problem you are facing. Also give me link to snapchat download.
Very strange. Well I'm on latest nightly and all my 3rd party apps install fine. Can't be runtime. Please post a link to the nodded Snapchat and I will give it a go.
Sora.
SORAnoDYStopia said:
Very strange. Well I'm on latest nightly and all my 3rd party apps install fine. Can't be runtime. Please post a link to the nodded Snapchat and I will give it a go.
Sora.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/apps-games/app-mod-snapmod-modified-snapchat-apk-t3006522
This is the mod, but as I said earlier I am generally unable to install non play store apps through the built-in installer.
Simultaneously, I did manage to get them to work by putting them in /system/app/ though, and they run just fine as I can tell.
After 20150208-NIGHTLY I am able to install apps, thread is for closure
MedzikPL said:
After 20150208-NIGHTLY I am able to install apps, thread is for closure
Click to expand...
Click to collapse
Glad its fixed.
Sora.
Hi i have samsung galaxy j5 oof it has android lollipop whenever i try to install any modded apk like asphalt 8 airbone or any other it start inatalling but after few second it say app not installed.i have even rooted my phone
Hi Mi A1 Device Holders,
I was curious of Google Floating Dialler on my device running Android O. So tried a modded APK from one of the threads. However I couldn't install the mod on to my device when it was in Beta stage. After several attempts.
Now Google have released a new version v17 in which the floating bubble dialer is enabled by default. You may refer to the below link.
https://www.xda-developers.com/enable-google-dialer-floating-bubble-2/.
So I wanted to try it again and went to Playstore and it doesn't allow me to download. Tried downloading and installing from Apkmirror. However I couldn't install it.
But I managed to install it with a small tweak.
Here is the Guide:
1. Hold the Phone app Icon and Click App Info
2. Scroll down to Option Phone App. If it is showing YES, you will not be able to install the new app. So you need to change it NO.
Note: You will not be able to do it without another Dialler app installed on your phone. For this, I installed TrueCaller App and then changed it. You may try with other dialer apps.
3. Install the latest app downloaded from ApkMirror or the one attached below.
4. Again, hold the Phone app Icon and Click App Info and shift the Phone App from True Caller(in my case) to Phone app.
5. You are done.
Enjoy :good:
Hit a thanks if you like it
P.S:
I was using v16 which got automatically updated from Playstore from the previous version. On top of that I installed the V17. My device is not rooted and using stock os...and I find absolutely no issues or lag or whatsoever
well in my case i just installed it and it worked voilaa.... Thanks for link
Thanks for the APK. I was able to install but now I can't search for contacts using T9 dialer. I now need to manually tap the search bar on the top and type in the letters.
Even manually searching is really slow and delayed.
Any fix for this?
Edit: The problem goes away if I roll back to the default Phone app, but comes back once I reinstall the above Apk.
What's going on here?
Leong428 said:
Edit: The problem goes away if I roll back to the default Phone app, but comes back once I reinstall the above Apk.
What's going on here?
Click to expand...
Click to collapse
It's working fine with me.. I find no such issues. You may try clearing the cache/data of the app. See if it helps.
kamireddybhargav said:
It's working fine with me.. I find no such issues. You may try clearing the cache/data of the app. See if it helps.
Click to expand...
Click to collapse
I tried that but it didn't help. Any other ideas?
I figured out the issue! For some reason Google Phone v17 did not work well with Contacts v2.4.
T9 dialling was very slow to search the contacts (10-15 seconds).
I tried everything from reviewing permissions, clearing cache, removing accounts etc. But nothing worked.
Finally I decided to manually check apkmirror and update the Contacts app to v2.5 and presto! Reduced lag when using T9 dialling!!
There is still an ever so slight lag compared to when I roll back to the v13 Google Phone, but it's much more usable now. Hope this helps!
Leong428 said:
I figured out the issue! For some reason Google Phone v17 did not work well with Contacts v2.4.
T9 dialling was very slow to search the contacts (10-15 seconds).
I tried everything from reviewing permissions, clearing cache, removing accounts etc. But nothing worked.
Finally I decided to manually check apkmirror and update the Contacts app to v2.5 and presto! Reduced lag when using T9 dialling!!
There is still an ever so slight lag compared to when I roll back to the v13 Google Phone, but it's much more usable now. Hope this helps!
Click to expand...
Click to collapse
i tried this on my redmi note 4, but when i make a call, history is not logged in new phone app, only in the old one. any suggestions? i hate these gapps [emoji14]
Sent from my Redmi Note 4 using Tapatalk
Have you tried setting the new phone app as the default and disabled the old one?
I was using v16 on January stable build and all was fine then i downloaded apk of v17 from apk mirror and it was also working fine aftert that i changed my rom to new February beta and now after installing v17 when i open phone app a popup appears everytime with a message that this app is not compatible and calls may not work correctly. Even though app was working fine but that popup was irritating me so i modded my phones build prop to pixel xl 2 and now Phone app is compatible with my Mi A1 and i can see it in play store aswell ??????
I was using v16 which got automatically updated from Playstore from the previous version. On top of that I installed the V17 and I find absolutely no issues or lag without build prop changes. Moreover, my device is not rooted for your info...
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks