I've noticed the Android emulator from Android Studio at MacOS 12.6 changes time to some random one. For example it's 16:11 now but emulator shows time 15:16. If I set time to correct one manually it's changed back to wrong one after some time without emulator being suspended or rebooted.
I tried to turn off all automatic time and zone detection but it didn't help too. Also I'm not sure why wouldn't emulator synchronise time if automatic sync is on.
It seems to be a long lasting bug in emulator. The issue https://issuetracker.google.com/issues/257097404 is created in Google's bug tracker
Related
Here are my PC Specs
Acer Aspire 5
Intel Core i3-8145U 2.1GHz with Turbo Boost up to 3.9GHz
RAM: 4GB DDR4
SSD: Kingston SUV500M8120G
OS: Windows 10
So I watched flutter tutorials...
I tried to do it with Android Studio... I installed it in hdd...
So I didn't care too much about the ram usage and the lag...
Two or three days ago, when the emulator was running, the machine suddenly froze...
After waiting for half an hour, I tried to get the task manager but it didn't, so I turned it off with the power button...
After that, I googled and said that it is difficult to run an emulator with my pc specs...
So I used my phone that day and connected it with a data cable...
Anyway, since the day of that freeze, the lap is slower than before...
The file explorer and also After pressing the windows key, it takes a while to open...
What is the reason for this???
I use Eset Internet Security...
I did a full scan of it and nothing...
I also tried the chkdsk command on all three partitions and there is no problem...
When I used Angular before, I used Webstrom...
It's not that bad as android studio, it wasn't slow...
Should I reset the pc???
There is no big case because only the software are uninstalled.....
Or should I install the android studio on the ssd...
The problem I have is that even after closing the android studio, it lags...
Even after restarting the PC, it is the same
Tell me some solution guys, it's a big help...
It is necessary to have good about of ram, 16 GB is good, less 8 GB might feel laggy.
Android studio consume more than Visual Studio Code. I will suggest you to switch on VS Code, and upgrading your component, increase the ram. Resetting Pc won't help that much. Try to kill every background process, just use vs-code. If you like to build for android use real device.
As for learning, you can try on dart.dev
Issue: The build hangs with "iPhone is busy: making Apple Watch ready for development"
Further facts:
iOS 14.8
iPhone 8
watchOS 7.6.2
Xcode 13
Apple Watch Series 3 + Cellular (42mm)
Does anyone know a solution for that issue?
Many of the developers have the same issue:
https://developer.apple.com/forums/thread/691452
I have been struggling with this for some time now. If you don't need the Apple Watch, instead of turning it off completely, you can also turn on airplane mode if configured correctly.
On your watch, go to Settings App → Airplane Mode. Make sure that both WIFI and Bluetooth switches are turned off!
When the bluetooth switch is turned on, a connection will still be established even if your watch is in airplane mode AND bluetooth is turned off on the phone from Control Center. It took me some time to figure this out...
Update: The Bluetooth setting seems to turn itself on again after some time! No idea why... 🤷🏼♂️ Keep that in mind and check the setting again if flight mode does not fix your issue.
Using Flutter?
When running flutter doctor, it will give you a clear hint, that your watch is causing the issue.
When trying to build your app e.g. from Android Studio, you might instead find these messages in your log:
The requested device could not be found because no available devices matched the request.
Available destinations for the "dev" scheme:
[list of devices]
Could not build the precompiled application for the device.
Building a deployable iOS app requires a selected Development Team with a Provisioning Profile. Please ensure that a Development Team is selected by:
[instructions how to set the development team]
Ineligible destinations for the "dev" scheme:
[list of devices]
I put these messages here for people googling them. If you have an Apple Watch, then run flutter doctor to check if this is the root cause.
This is what works for me:
Turn off the Bluetooth from settings in your iPhone from Settings -> Bluetooth (Don't turn it off from the control center)
Quit Xcode
Launch it again
Build and Run
The solution is:
Waiting for 5-20 mins
Let your iPhone and Apple Watch on
I think all answers are overlooked, you don't need 5-20 mins if you let it finish the preparing process, it'll take just a few minutes, 5 mins top..
But regarding fixing this with an upgrade, that's not the case, and I would love to see it fixed, or offered with an option to exclude watch from the dev purpose unless really needed.
I facing this issue too. This is because the latest xcode only support until iOS 15.2 sdk, but my phone's iOS version is 15.3. Thus, xcode is downloading the iOS 15.3 sdk from your phone that's why takes time (I knew the message is not saying that)
However, I do some testing and it works for me.
Get the iOS 15.3 sdk (is 10BG!!!) from my friend xcode's Devices Support iOS folder /Users/XXX/Library/Developer/Xcode/iOS DeviceSupport and paste it to yours one.
Downloading the iphone OS device support file from https://github.com/filsv/iPhoneOSDeviceSupport/blob/0e8ef7bc51b982304ed3258454f88ae2d5615ac7/15.3.zip unzip it and paste it in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
Restart Xcode.
Build success without waiting.
Origin From: https://developer.apple.com/forums/thread/691452?answerId=704424022#704424022
The Apple Watch configuration takes around 5 minutes. It's way better to postpone everything and let it run for 5 minutes then the other workarounds - such as disconnecting your watch, turning on/off your iphone, etc
In my case:
If my Apple Watch is turned on - then from Xcode I'm still able build and run the app just fine.
But when I'm using Flutter - it fails.
flutter devices shows my iphone as "Busy".
As soon as I turn off the Apple Watch, and then disconnect and reconnect the iPhone USB cable - all is good.
Since it's one of the earliest Apple Watch modules, the latest WatchOS that I can install is v6.3, although the latest available is WatchOS v8.x.
I suppose this issue doesn't occur with the latest WatchOS.
(I'm using iOS v15.2)
This still happens from time to time. The solution that has worked for me every time is to reboot the phone
Make sure you're running a version of Xcode that supports the SDK versions of your iOS/watchOS device. If you've recently updated either OS versions, you may need a matching Xcode update for this to work properly.
The real solution is:
If you don't need the apple watch you can just power off the Apple Watch and unplug/plug the iPhone. That's a quick fix. No need to unpair the watch no need to wait 5 - 20 mins
According to this post, this issue is fixed with an upgrade to iOS 15.0.2 / watchOS 8.0.1: https://developer.apple.com/forums/thread/691452
I'm running into an issue where my iMac, with over 100G free, gets Disk Full Error after running Flutter for an hour or so.
When I reboot I get dozens folders in my Trash "Recovered Files" that are around 2G each.
The issue is actually described fairly well here (with screenshots): https://github.com/flutter/flutter/issues/56270
However, the moderator closed every comment as "off topic" (seems like several people are having this problem). So I figured it may be a good idea to bring this here to see if anyone else has found a solution for this?
I'm running VSCode and when I run Flutter Doctor I'm 100% compliant. Using the latest Flutter/Dart/MacOS/Xcode/Android Studio versions. I am primarily building my Flutter app to macOS platform (desktop).
I tried the suggestions in the above issue post and none of these worked for me (re-installing cocoa pods, re-installing Xcode, re-installing Android Studio).
I actually ran into this issue about a week ago. The comment linked to had put me on the right track, where they mentioned it only happens when they have an iOS device attached to their machine.
If you see something like this error in your VSCode output log when launching your app, then it's likely the same issue.
Failed _shouldMakeReadyForDevelopment
If you have a device attached and it's locked, I believe something in the Flutter env attempts a connection over and over causing these files to fill up.
However, this happened to me once even when I didn't attach a device and I found out it was because I had "wirelessly" attached a device in Xcode when I was doing iOS development for another project. So just sitting at my desk with my iPhone nearby was enough to cause it to try to connect over and over again, even if it wasn't attached.
I removed my iPhone from Xcode's wireless device list and that seems to fix it.
Can confirm, running flutter with an attached ios device eats disk space.
This is happening to myself and another developer on my team. I lost 200 GB of disk space yesterday. It's a frustrating productivity killer.
I am using the latest flutter
flutter doctor reports everything as fine
xcrun --find simctl is fine
Using Android studio 3.6.3
Latest patched Catalina 10.15.4
This morning I opened the Android Studio IDE with an android device and an ios device connected. I opened a get info window on my hard drive and left it open. Then I did nothing but watch the info window. No builds or anything. Over the course of a couple minutes, I watched 7 GB disappear.
I shut down the IDE and the loss stopped. I reopened the IDE with only the android device attached. I waited and watched for a few minutes. No loss of disk space.
Then I reopened the IDE with just an ipad attached and the losses started again. Then I unplugged the ipad and left the IDE open and the losses stopped.
Same here but happens also when just running Android Emulator.
This needs to be fixed A.S.A.P - its a dealbreaker!
When the problem happens and the disk runs full, my system slows down so much I can hardly do a thing. To free up disk space and get operational again quickly, there's two options:
Restart. Then the cache files are either deleted or end up in "Recovered Files" in Trash, as described by #william-t, from where you can delete them.
Directly delete the cache files in "TemporaryItems" (for me that's below /private/var/folders/bc/gw57z9dn4rn2v6df7306k9sh0000gn/T)
I know this is not a solution to the root cause of the issue, and it still helps a lot, as long as there's no true fix...
I am still confused about whether my device is properly updated, or whether Leibnitz has a problem, or something else is wrong ?
Yesterday r4ravi2008, who appears to be a Tango dev said:
Apologies, that you are experiencing problems. Is this still
happening? I am asking this because, there was a bit of leeway in
timing between when the TangoCore was updated on PlayStore and when
the OTA went out (which can potentially cause this issue, if OTA and
TangoCore are mismatched). I just want to make sure that you are are
updated on both TangoCore and OTA before diagnosing it. Also, make
sure you have permissions for camera in the android manifestl.
Could you please clarify with actual version numbers how one can tell if that mismatch is indeed the case. For example, in my device under Settings->About Tablet it says:
Kernel Verison
3.10.24-gcde7bc7
Tango#Atap #1
Fri Mar 20 10:12:09 GMT 2015
Build Number
KOT49H.150320
Next, under About in the Project Tango Explorer it says:
App Version 1.11
Tango Service Version 1.11
Is this combination of OTA Tango Core/Firmware/Kernel/whatever correct? If so, then the Tango Explorer keeps loosing pose data every few seconds
and eventually crashes; either, my device is broken, Tango Explorer has a problem or Leibnitz has a problem.
If the above is not the correct combination, then how can I fix it? In previous posts some people said that going back to factory reset and updating everything fixed the problem; others say it didn't? Please include in the answer what I am supposed to see in the above text fields so that I can be certain that my device is in the right state. Thank you.
I received my tablet on Wednesday the 22nd. I jumped right in without downloading everything in the proper order. I tried to download the core before updating the tablet. Then after updating the tablet it refused to let me download the proper version of the core. Every demo I tried would track for 2-5 seconds and then suddenly crash. Restarting the apps would say that the service was unavailable, and restarting the tablet would give me another few seconds of tracking before suddenly crashing again.
So on Thursday the 23rd I did a factory reset. Updated the tablet first through system preferences. After that I downloaded the core through the play store. Then downloaded explorer and several demos. Everything works fantastically and I haven't had a crash since.
These are the versions I have:
Kernel Version
3.10.24-g36a1dd3
Tango#Atap #1
Tue Apr 14 11:34:37 BST 2015
Build number
KOT49H.150414
Project Tango Explorer
App version 1.11
Tango service version 1.11
Hope that helps!
I am working on API LEVEL 17 supporting back upto 8. I have some network task to perform that I am doing from seperate AsyncTask class. Now the problem is that whenever I try to launch the application on emulator first time will be fine, but from 2nd onwards my emulator response is slower and gets more slower on successive launch. after 4-5 launch It installs the app but never starts the activity. Then I have to restart the emulator and it also need a startup after 4-5 launch.
I have seen in logcat skipped ### screens!!! UI thread might be doing to much work right from the starting of emulator.
Can anyone tell me what could be going wrong? Thanks in advance!!!
Regards,
Sourabh
Your system configuration is less for android api 17 version your app work properly in api level 8 to 10, so you can set api level 8 to 10.
Surely process of Emulator starting is slow, as lots of threads and process starts-off when emulator starts. Still for better start timing you can download Intel atom emulator from Android SDK Manager, its also available for android api version 17, Also there is option of choosing Snapshot for emulator, which takes less time for start-off.