Related
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
psbear532 said:
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
Click to expand...
Click to collapse
Use adb
Code:
adb install myapp.apk
ros87 said:
Use adb
Code:
adb install myapp.apk
Click to expand...
Click to collapse
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
psbear532,
You can use a file explorer program (astro, es explorer, etc), and choose the apk on sd and install it. Just remember to use nookcolortools and de-select and re-select the non-market app box.
I guess it would be easier - I haven't had luck with adb so far...
psbear532 said:
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
Click to expand...
Click to collapse
Assuming you've successfully rooted your NST:
1: Enable wifi on your NST and make a note of the IP address assigned to it.
2: Tell adb to connect to that IP
Code:
adb connect 10.0.0.2
That's it, if adb was able to connect you can now adb push or adb install all you want
---------- Post added at 01:41 AM ---------- Previous post was at 01:39 AM ----------
apeine said:
psbear532,
I guess it would be easier - I haven't had luck with adb so far...
Click to expand...
Click to collapse
Why?, apart from having to download and install the Android SDK, using adb should be straightforward unless you're trying to get it to connect to the NST trough usb.
Ros87,
Maybe that was my mistake. I've always tried using USB :S
apeine said:
Ros87,
Maybe that was my mistake. I've always tried using USB :S
Click to expand...
Click to collapse
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Thank you both so much! Ros87 I got it to work over wifi which I think is even better since now I don't even have to deal with the wire. apeine I didn't try your method since adb worked, but thanks for your time anyway.
ros87 said:
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Click to expand...
Click to collapse
So why don't you install linux on a separate partition?
How does one do this without an SD card? I will be getting one soon, but for now, can I just create a temporary folder on the home directory and install it from there? Does it automatically install to the apps directory?
Thanks!
EDIT: I just figured out how much you can browse with the computer. So...
The simplest method is to just copy the apps to an SD card, insert the card,browse to the .apk location,tap on the .apk file, you will be prompted with an screen asking if you want to proceed to install or just use the adb over wifi method as explained above
I use and app names Airdroid. It allows you to install apps remotely from your computer via wifi.
I have an "apk" folder in my UbuntuOne account, Dropbox should work too.
then i have the app for the service installed.
it works fine for me
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Did you use the "cd" command to change the directory to where the platform-tools folder is?
That's assuming you have the Android SDK and Java Dev Kit (JDK) installed already..
Sent from my Atrix HD via XDA-Developers application
pianoman102 said:
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Click to expand...
Click to collapse
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
pianoman102 said:
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
Click to expand...
Click to collapse
U're welcome
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
skeevydude said:
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
Click to expand...
Click to collapse
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
devilsking said:
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
Click to expand...
Click to collapse
Thanks.
That's what I thought it did. I was going to do something similar, but I couldn't remember if the correct folder was and I was just too lazy to do the research and find out. I was thinking System32, but its been so long that I couldn't remember.
UPDATE 27th November 2014
I have added an Xposed module for the clients below that will work around the issue with Google Play services 6.5
UPDATE 25th November 2014
Google have released Google Play services 6.5 which has strengthened security, effectively making this app useless (clients will be unable to connect). Until Google either loosen the security (which is unlikely to happen), or someone somehow were able to get a hold of the private keys from the chromecast/Android TV this app will no longer work and will no longer be updated.
Thank you all for your support!
Hi everyone! I've decided to finally release my modified Cast Receiver app from the ADT-1 for Android that will work on most devices (though not sure what the minimum api requirement is).
If you don't know what this is it's basically a chromecast receiver for your Android; I use it on my Android mini PC that's hooked up to my TV.
Downloads
Last updated Nov 05 2014.
Recovery install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiaU5WSWRxeC02Tzg
Signed
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiVDR1a1o0WFVSWjg
System install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiNFJGUE1acGZTeFE
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiOTRoanlyX19pVmc
If you are not rooted and can only install it as a regular apk, use the signed version. Note however that casting the screen from another Android device will not work due to a signature mismatch (Google Play Services checks the signatures of the app before allowing screencasting).
If you are rooted you should go for the recovery/system install option, as that will allow screencasting to work.
Xposed module for receiver
If you want to be able to use the system install version on devices older than KitKat you can use the following Xposed module:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiZEFrN1RqLTRFdkk
Xposed module for client
Version 6.5 and newer of Google Play services makes it impossible to connect to the receiver due to some added security. This Xposed module works around that:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiWG1tU3NfYWwwV00
Install
Recovery install
No special instructions needed, simply copy SYSTEM-CastReceiver.zip to the internal storage (or sdcard) on your device and flash it through your recovery (follow the instructions for your specific recovery).
Signed
Simply install the apk as you would with any apk, either through adb:
Code:
adb install -r AndroidMediaShell-signed.apk
or by installing it from your sdcard.
System install
You will need rooted adb for this to work correctly.
If you come from an old install, you can safely remove the old lib first:
Code:
adb remount && adb shell rm /system/lib/libmedia_shell_content_view.so
Once that's done, run:
Code:
adb remount && adb push libcast_shell_android.so /system/lib/ && adb shell chmod 0644 /system/lib/libcast_shell_android.so
adb remount && adb push AndroidMediaShell.apk /system/priv-app/ && adb shell chmod 0644 /system/priv-app/AndroidMediaShell.apk
(Change priv-app to app on devices older than 4.4)
Running
Amazon Fire TV
Because the Whisperplay app implements a DIAL protocol of its own on port 8008, which the Cast Receiver app also uses and that causes a conflict between the two apps.
To get the app running correctly you need to rename WhisperplayCore.apk:
Code:
adb shell mv /system/app/WhisperplayCore.apk /system/app/WhisperplayCore.apk.bak
once that's done, reboot and follow the instructions below.
For the receiver to start you can simply reboot provided you are using the system install. If you are using the signed version you need to run:
Code:
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n com.google.android.apps.mediashell/.AutoStartListener
After that it will run automatically in the background after each reboot, so you will be good to go!
Keep in mind that it might take a few minutes for the receiver to show up in the cast list, if it doesn't show after 10 minutes, try rebooting the device.
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
Supported Apps
Currently not every app is supported. The ones I've tried are:
YouTube - Working
Google Play Music - Working
Google Play Movies & TV - Working
Google+ - Working
Google Photos - Working
Screen Cast - Working (if you follow the instructions above)
Chrome for computer - Working
Netflix - NOT Working (I'm looking into this)
Plex - Working
Chrome for Android - Workinghttps://drive.google.com/file/d/0B4FOzj4b2EYiWVlDTWNGOEw3UTg/view?usp=sharing
Those are the ones I've tried, others may or may not work.
Whether the app will work may also depend on what device you are running the cast receiver on, as well as the region you are in.
FAQ
My device doesn't show up in the official Chromecast app
This is a known "problem" that also affects the ADT-1. There is nothing I can do about it in the Cast Receiver app, only Google can fix it by modifying the Chromecast app. Screen casting etc should work though, it's only the Devices screen that doesn't show any devices.
The receiver doesn't work on my Amazon Fire TV
Please read the instructions under the Running category.
I can't find the receiver device in the cast list
Give it a few minutes. If that doesn't work, try backing out of the app, and enter it again. If it still doesn't show, post a new reply to this thread with a log from logcat.
App X doesn't work
Get me a log when you try to initiate the connection, keeping in mind that some apps may be easier to fix than others. And some may be next to impossible due to them being regional.
How?
I've had some people ask how this was done, so I've written up a list of the changes and a brief summary here:
https://docs.google.com/document/d/1tXnjDdurdoJ4ufulzaqGpuaNpLLt6LGAUk22MO2jta4/edit?usp=sharing
You can get a patch of the smali changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiTHZBRGVUWmlSV1U/view?usp=sharing
And a bsdiff of the lib changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
The source code of the Xposed receiver module can be found here:
https://github.com/HomerSp/XposedCastReceiverFix
The source code of the Xposed client module can be found here:
https://github.com/HomerSp/XposedCastClientFix
And finally here is the code I used while testing the receiver, and writing the MediaDrm and JmDNS code:
https://github.com/HomerSp/CastTest
Changelog
Nov 05, 2014
* Fixed receiver not working while connected to ethernet (may be restricted to the Fire TV)
Oct 29, 2014
* Fixed app not working on API level 15 (tested by me on a real device).
* Disabled logging to file - this should significantly reduce the size of the data that's used by the app.
Oct 26, 2014
* Updated to new 5.0 preview from the ADT-1.
* Lowered API level to 15 on the signed version, keep in mind that this is untested by me. This also includes disabling some DRM API calls that were added in API level 18, so Play Movies will not work on API 17 or lower.
Oct 17, 2014
* Fixed receiver not always starting correctly due to device not being provisioned, thanks to @rkirmeier!
Oct 10, 2014
* First version!
Finally I would like to give out a big thank you to @death2all110 for doing extensive testing for me, as well as providing me with the system dump from the ADT-1. I couldn't have done this without him!
Enjoy!
Great! Works flawlessly on my Ouya (CM11). Run on boot via ScriptManager.
If you need help with Netflix you know where to find me!
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
krosk said:
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
Click to expand...
Click to collapse
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
@death2all110 I probably will, yes. It seems to be restricted to the US for now - I've tried hard-coding a proxy in the code, which makes it go further, but not far enough for it to work. I'll get back to you when I have something for you to test!
HomerSp said:
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
Click to expand...
Click to collapse
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
krosk said:
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
Click to expand...
Click to collapse
Of course, I completely misread your post. Sorry!
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
rkirmeier said:
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
Click to expand...
Click to collapse
What version of Google play services do you have installed on the sender device? Also, a logcat from the receiver would be useful.
astro128 said:
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Click to expand...
Click to collapse
I don't own a Nexus Q myself, so I won't be able to do any testing. The Q is running a full Android system, right? If it is, the receiver app most likely requires a later API version, or the Q doesn't support some of the features the cast receiver app requires to function.
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
rkirmeier said:
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
Click to expand...
Click to collapse
You can attach the logcat to your post, or use something like pastie.org or pastebin.com
Log attached to this post.
rkirmeier said:
Log attached to this post.
Click to expand...
Click to collapse
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
That is correct. I'll work on getting the log from my minix and tablet tonight as they both have the receiver installed and do the same thing.
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
Minix log attached...
Thanks!
rkirmeier said:
Minix log attached...
Thanks!
Click to expand...
Click to collapse
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
HomerSp said:
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
Click to expand...
Click to collapse
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
rkirmeier said:
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
Click to expand...
Click to collapse
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
HomerSp said:
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
Click to expand...
Click to collapse
I confirmed USB Debugging is enabled. Wouldn't this be required to even make the connection?
I have heard that disabling it can make Oreo ROMs faster. Also, can someone help me with screenshots of using those commands on a computer?? I don't know if I'm doing it right.
Basically, tell me everything bout it.
Regards
@m00nlighter can help, he seems to know bout thjs
Dude, just wait for the Pie ROMs to become mature.
Oreo ROMs for Titan were simply not on par with Nougat ones, and a debloated stock Marshmallow ROM with ZRAM disabled will beat both Nougat and Oreo ROMs in terms of performance and stability.
So for now it's either stock or Pie, Oreo is history.
But I want to use Oreo, they ain't that bad for me. Could you please help me??
Detailed instructions are below. Please don't ask for further explanations, this is as simple as I can make it.
It's somewhat complicated and requires adb access and root permissions, so you have to be rooted.
Moreover, you have to have some free space on /system partition (I'd say around 300 megabytes) because ALL packages (apps) will be recompiled, including system apps. As for the data partition, it is hard to tell, depends on what apps you have. I recommend starting with minimum required apps.
First, disable the JIT compiler
adb root
adb shell stop
adb shell setprop dalvik.vm.usejit false
adb shell start
Click to expand...
Click to collapse
Second, clear profile data and remove compiled code for all packages
adb root
adb shell cmd package compile --reset -a
Click to expand...
Click to collapse
Third, force compile all packages using "speed" compiler profile (AOT-compiles all methods in app code)
adb root
adb shell cmd package compile -m speed -f -a
Click to expand...
Click to collapse
And finally, add/edit the following two properties to system.prop:
dalvik.vm.usejit=false
Click to expand...
Click to collapse
This will permanently disable the JIT compiler.
pm.dexopt.install=everything
Click to expand...
Click to collapse
This will force AOT compilation for apps, including updates and new installs.
After that, reboot and enjoy your FAST Oreo ROM
Why JIT compiler should be disabled on old devices like Titan?
Read the excellent post by Farhan on Stack Overflow here:
https://stackoverflow.com/questions/40336455/difference-between-aot-and-jit-compiler-android#
Where did I get this info from?
Official Android docs. See
https://source.android.com/devices/tech/dalvik/configure
and
https://source.android.com/devices/tech/dalvik/jit-compiler
m00nlighter said:
Detailed instructions are below. Please don't ask for further explanations, this is as simple as I can make it.
It's somewhat complicated and requires adb access and root permissions, so you have to be rooted.
Moreover, you have to have some free space on /system partition (I'd say around 300 megabytes) because ALL packages (apps) will be recompiled, including system apps. As for the data partition, it is hard to tell, depends on what apps you have. I recommend starting with minimum required apps.
First, disable the JIT compiler
Second, clear profile data and remove compiled code for all packages
Third, force compile all packages using "speed" compiler profile (AOT-compiles all methods in app code)
And finally, add/edit the following two properties to system.prop:
This will permanently disable the JIT compiler.
This will force AOT compilation for apps, including updates and new installs.
After that, reboot and enjoy your FAST Oreo ROM
Why JIT compiler should be disabled on old devices like Titan?
Read the excellent post by Farhan on Stack Overflow here:
https://stackoverflow.com/questions/40336455/difference-between-aot-and-jit-compiler-android#
Where did I get this info from?
Official Android docs. See
https://source.android.com/devices/tech/dalvik/configure
and
https://source.android.com/devices/tech/dalvik/jit-compiler
Click to expand...
Click to collapse
Dude, one last question. What is the output of cmd after you type :
adb shell stop
CMKdaGreatest said:
Dude, one last question. What is the output of cmd after you type :
adb shell stop
Click to expand...
Click to collapse
There should be NO output. This command effectively stops the shell.
@m00nlighter
This is the result I'm getting. Please tell me if it is what it is supposed to be
Please answer my question, pleaseeee
If you can't see the pic,
The output to adb shell stop is something like this
"stop:must be root"
Am i doing something wrong?
CMKdaGreatest said:
@m00nlighter
This is the result I'm getting. Please tell me if it is what it is supposed to be
Please answer my question, pleaseeee
If you can't see the pic,
The output to adb shell stop is something like this
"stop:must be root"
Am i doing something wrong?
Click to expand...
Click to collapse
Yes you are doing something wrong. Please go learn how to work with adb, enough info is available, just google it.
Unfortunately I'm not able to work with adb very well. adb root command is failing I think, so adb shell stop is also failing.
Someone help me please @m00nlighter @sapo_joe @Oshmar @thedeadfish59
I use magisk as su. Is that a problem for this?
Hi all, my 9t pro is locked with no root and I usually update the Xiaomi apps by using apkmirror. I've never had any problem so far, until the latest Xiaomi weather app updates. The last working version on my phone was 12.1.0.9, and after installing any newer version I am unable to launch the app anymore, because it just shows "Can't use this app. It wasn't installed from the official source.".
I tried to go in the Manage app section where usually there should be a "Uninstall update" button for this, but in the Weather app it's grayed out and I don't really know what I can do to solve it. At this point, I don't really care to have the latest updates for this app I'd just like to restore to what it was. Has anyone see this problem before?
My weather app also has bug shows different location in default
Not got a fix but if you launch the Google app there's weather built-in. It's a little more intuitive than Xiaomi Weather and a good stopgap until it's fixed.
If you bring up the Google app, weather should be located beneath the search field. Tap it then switch tabs to get the full weather view. You can then open up the hamburger menu and at it to the homescreen.
droident said:
Not got a fix but if you launch the Google app there's weather built-in. It's a little more intuitive than Xiaomi Weather and a good stopgap until it's fixed.
If you bring up the Google app, weather should be located beneath the search field. Tap it then switch tabs to get the full weather view. You can then open up the hamburger menu and at it to the homescreen.
Click to expand...
Click to collapse
I installed a different weather app so finding a replacement wasn't a problem, but I really like the simplicity of the Xiaomi one, that's why I'd like to have it working again
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
tinhopvh said:
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
Click to expand...
Click to collapse
Bro I registered just to say thank you! I couldn't find a solution anywhere. You are a man of culture and I salute you, sir. But... I need the same command for music player. Is it something like
pm install -r -d /system/priv-app/Player/Player.apk ?
CyberCrai said:
Bro I registered just to say thank you! I couldn't find a solution anywhere. You are a man of culture and I salute you, sir. But... I need the same command for music player. Is it something like
pm install -r -d /system/priv-app/Player/Player.apk ?
Click to expand...
Click to collapse
This is for Mi Music :
adb shell pm install -r -d /system/priv-app/MiuiMusicGlobal/MiuiMusicGlobal.apk
C.T.E said:
This is for Mi Music :
adb shell pm install -r -d /system/priv-app/MiuiMusicGlobal/MiuiMusicGlobal.apk
Click to expand...
Click to collapse
Thank you!
tinhopvh said:
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
Click to expand...
Click to collapse
Thank you so much!!!...
tinhopvh said:
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
I am suffering from this bug from last 2 months. I also accidentally installed unauthorized apk update for Xiaomi Weather app. After that app stop running and suffered me alot from last 2 months, I am searching for this type of help up to now. It resloved my problem. Thanks for your help.
Click to expand...
Click to collapse
tinhopvh said:
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
Click to expand...
Click to collapse
Thanks a lot..
It resolved the issue in the poco f1..
I need another favour.. I have similar problem with miui fm radio and miui notes.. what adb command i have to use to reinstall their factory version..
Thanks in advance..
PrashanthG said:
Thanks a lot..
It resolved the issue in the poco f1..
I need another favour.. I have similar problem with miui fm radio and miui notes.. what adb command i have to use to reinstall their factory version..
Thanks in advance..
Click to expand...
Click to collapse
Same commands but the appropriate package names.
Try with com.miui fm and com.miui.notes
(and rather take care when debloating)
Hi it doesn't work for me. I've tried this and i got an error that says [INSTALL_FAILED_VERSION_DOWNGRADE] Uninstalling it via google play store also doesn't work. I don't know what to do. I don't want to use third party apps..
tinhopvh said:
Resolved after reinstalling the factory version with the command:
"adb shell pm install -r -d /system/priv-app/Weather/Weather.apk"
Using ADB.
I hope it helps you too.
Click to expand...
Click to collapse
Thank you! I've had the problem for months...