OTA and kernel mismatch - google-project-tango

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!

Related

Failed to start remote service on device problem in xcode

I create a flutter app and now I'm trying to run it through XCode on my real iPhone, but after the installation finishes, I face the following problem:
Also with I trying to run the application on my real phone, after clicking on the application icon, I face a white screen appears, and then the application closes directly.
Catalina 10.15.3
IOS 14.2
XCODE 11.7
Also I was make a trust to app in phone
Does anyone know the reason for this problem?
This problem maybe because of two reasons:
First: Xcode 11.7 doesn't have support files for iOS 14 you can download it from here https://github.com/filsv/iPhoneOSDeviceSupport
Second: I have this problem now and I couldn't fix it.. but I have iPhone with iOS 14.2 and iPad with iOS 14 so the problem was just on the iPhone but after I updated the iPad with iOS 14.2 it happened with it.. so the problem maybe because of the iOS 14.2 so we have to wait for the update or because of the Xcode 11 version and we have to download the Xcode 12 version..
I hope we can find a solution quickly...
make sure to have the latest system update on your target device and the latest Xcode version as well. The error should disappear.
Best,
Ralf
I have fixed the problem by using the above solution but it has happened again. So, I have followed these instructions and fixed again:
https://stackoverflow.com/a/61665031/6586109
A good first place to look is Window > Devices & Simulators in xCode, then find the details for your device. There may be error information here that helps you find the fault.
Restarting devices and installing updates seem to fix this problem for a lot of people.
For me, there was a red notice in the device window about connection to the device and it turned out to be the cable that was at fault.
This was an official Apple cable, just a few months old, and still works fine for charging and data transfer; and I've been using it with xCode without problems for a couple of months. It seems to be possible for Apple cables to develop some tiny physical fault that seemingly only xCode is sensitive to.
Using a different cable worked first time for me.
There seem to be a few variations on the exact error message with the same root causes varying depending on exactly what xCode was trying to do at the exact moment it failed: I'm on xCode 12 and for me it was:
Failed to start remote service on device
Failed to start remote service com.apple.installation_proxy on device

On Starting mac and running xcode simulator Consume around 500MB Internet Data

For Past 4 week i observer when i run my Xcode application on simulator on first time simulator launch it consume around 500MB internet data.
This is not project specific issue. Every time when i shutdown and start the mac and run Xcode as soon as simulator open it will consume same amount of Data.
Can any one help me What is the issue?? or any background service run??
Xcode version: 11.6 (11E708)
simulator: 13.6
OSX: 10.15.6
Please help me unnecessary every time my Internet Data is consume i have to fix this
This issue is still persist after updating to xcode 11.7
Thanks For #Rado for suggesting the https://apple.stackexchange.com/.
After posting the question on https://apple.stackexchange.com/ i fond the answer.
Orginal Answer: Xcode simulator constantly download something
Answer:
rename the file com.apple.nsurlsessiond(Dont delete) in
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/UserEventPlugins/com.apple.nsurlsessiond.plugin/
to something -com.apple.nsurlsessiond
and also the file nsurlsessiond(Dont delete) in
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/
to something -nsurlsessiond
Apps with admob works perfectly also no problem with safari
If you don't need an internet connection for testing you application, you could simply disable the network.
You could run wireshark and see what it is actually doing, or at least see where it is connecting to.
I used tripmode firewall don't give simulator internet access only give when you need it.
Works fine but when you forget to turn it off and start the simulator next time, you feel horrible :(

Flutter - Disk Full Error - A Document Being Saved by xcdevice

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...

Game App cannot run in Genymotion

I am having trouble loading a game app on genymotion. The game is Star Wars Force Collection. I can load the game, get the splash screens, then it crashes.
I have done some research before I posted here. The possible problems found in the genymotion logcat file:
There was a line noting Google services was out of date, "Google Play services out of date. Requires 4030500 but found 3225136"
Fatal signal 11 (SIGSEGV) at 0x00000364 (code=1), thread 1796 (RefQueueWorker#)
W/NetworkManagementSocketTagger( 280): setKernelCountSet(10040, 1) failed with errno -1
Some have pointed out ARM Translator problem and OpenGL.
Then again I'm really not sure the problem, and I want to post the logcat file here but I don't know how to attach it.
For problem 1, I have seen other thread here that may have fixed it with code, I'm not savvy enough for that and my Google is not updating itself.
That's about it. A few details about genymotion and the VM. I am running the latest version of genymotion and virtualbox. I am using the downloaded Custom image 4.3 as provided by Genymotion. I flashed the ARM Translation v1.1. I flashed the Gapps onto it, (I tried a higher version of Gapps to try and solve the problem, but that just made it crash) and then Star Wars Force Collection, most up to date version.
Also, worth noting that the app was running fine for v2.++, until an update to v3.++ made the game crash. I updated my graphics drivers to try and mend any graphics issues.
So there it is, any suggestions will be appreciated.

Upgraded ZTE Open from 1.0 to 1.2 - Stuck in reboot loop

I own a ZTE Open, UK edition. I tried upgrading from 1.0 to 1.2 following these instructions.
https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/comment-page-1/#comments
The update I installed came from ZTE themselves, and was not a custom, or third-party ROM.
The upgrade worked smoothly and had no errors, and I was prompted to reboot my device. Since then it has been in a reboot loop.
I've tried entering recovery mode and restoring to factory settings, but nothing worked. Likewise, I've tried wiping the cache from recovery mode, but with no success.
Any help would be much appreciated.
EDIT: Also worth adding that I cannot access the phone via ADB or Fastboot.
I had a similar problem when I tried to update to 1.2 using the same tutorial
(I have the US model).
The problem seems to be jumping from 1.0 to 1.2. You need to load 1.1 first, then 1.2.
The solution for me was to download both of the ZTE Official 1.1 updates linked on the
ZTE Open device page for my region (on the mozilla developer website under the heading "Upgrading Firefox OS" linked below).
Do not change the downloaded files names, just unzip them both and put both .zip files on the root of an sd card and reboot into recovery.
You should be able to flash one of the two files using the install update choice, the other will give an error (I can't read the full filenames on the phone so I'm not sure which one actually worked for me, that is why I say just try both.)
After flashing you should clear cache, wipe data and reboot.
If all goes well you should have a fresh factory load of 1.1 on you phone and you can now follow that tutorial to upgrade to the developer preview of 1.2.
If your recovery won't flash either of the official EU 1.1 updates you may have some how replaced your stock EU firmware with a stock US firmware, one update will say signature verification error and the other one will give another longer error 7 something or other. I replaced my US firmware with an EU firmware (v1.0) without realizing it and thought my phone was totally bricked because I couldn't get any US 1.1 firmware to flash and I couldn't get to fastboot or adb to manually flash a build (I loaded EU 1.0 version then used fastboot to flash a 1.4 build that wouldn't boot). The solution to that problem was to load an official EU 1.1 .zip from recovery and then load the US 1.2 developer preview from fastboot which replaces the EU recovery and let me flash an official US 1.1 .zip build.
Try not to mix and match firmwares from different regions, the Open doesn't seem to like that.
I was able to get the ZTE preview of 1.2 to work but it has a nasty bug with the notification bar so I went back to the official 1.1 build so you may want to stay at 1.1. If you do load 1.2, the key to using the notification bar is to tap and hold above the screen and slowly "roll" your finger onto the bar until you can pull it down (that might not make much sense now but if you get 1.2 loaded you will understand).
Hope that helps.
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN
When upgrading to V1.1 before attempting to upgrade further, I might be able to explain why #Foo observed that only one of the two ZTE files worked (ZTE file links: European, US - each has two files). I didn't hit the reboot loop, but I was unable to install what looked like the right file.
The reason is that there are two links for upgrading to V1.1.0B02 - one link is labeled "(for V1.0)" and the other is labeled "(for V1.1)". This really tripped me up as I was scanning the list for 1.1 and jumping over the (right) file labeled for 1.0.
Very clearly, if you are upgrading from 1.0, then you need the "V1.1.0B02(for V1.0)" version. Just downloading both and trying each one may be easiest, but it vexed me to not understand this.
If you pick the wrong one, I found the error message (E:signature verification failed) to be very unhelpful after booting into recovery and attempt to flash from the SD card.

Resources