I'm using the 7.1.2 firmware.
Background location update is enabled in the plist.
iBeacon Region monitoring is working fine even when app is in background.
I was thinking region monitoring was automatically restarted after a phone reboot.
In my case, nothing appends after the reboot (I have wait 20 minutes)...
Related
I have a Retina screen MacBook Pro with a 15.6" 4K external monitor attached. I've discovered the resolution of the Citrix session is terrible unless I set the (MacOS) display resolution to 3840x2160, in which case the session resolution is perfect.
The trouble is at this setting, the resolution outside of the session, in MacOS is tiny - I usually have it set to scaled slightly larger. Without the external screen attached, the situation is the same with the default native display resolution resulting in very poor quality in the session.
Is there any solution where both the Citrix session and MacOS both look good?
defaults write com.citrix.receiver.nomas EnableHighDPI -bool YES
I have a Retina screen MacBook Pro with a 15.6" 4K external monitor attached.
According to Citrix they don't have a solution yet.
Prerequisites
To try out on individual MacBooks without enabling for the entire organization/store or if you do not want to whitelist LaunchDarkly on your internal network, you can run the following command in macOS Terminal
defaults write com.citrix.receiver.nomas EnableHighDPI -bool YES
Limitations
Supported devices: MacBook, MacBook Pro. Devices not supported: Mac mini, iMacs, Mac Pro.
No Multi monitor support. This feature will not work if you have connected a secondary monitor. Even if you don't use the secondary monitor with the Citrix Workspace app, simply connecting it will cause this feature to not be available. This feature works only when you use a single monitor for your device.
Source: https://support.citrix.com/article/CTX270704/citrix-workspace-app-for-macos-and-retina-displays
I tried it on my M1 Mac. After I disconnected the Thunderbolt dock with all peripherals the running session changed the resolution by itself to higher DPI. As soon as I connected an external monitor I was back to 1080p.
I am developing an app in Xamarin Forms which will show thing live position of the user on a map and all the users having the app can track other users movement.
Right now the app is working fine in android. But in the iOS foreground, android background it stops after some time. It is not at all running in ios background when I put the app in the background it stops showing the location and stops fully.
Please share some idea to keep the app live in background and foreground mode for the whole day.
Generally speaking, mobile OSs will stop your apps, when they are in the background for some time. How strict the OSs are depends on the OS and the version. iOS has "always" been very strict about it, Android has been a bit more loose in older versions, but is quite restrictive in newer versions. Anyway, getting the location in background is quite a common use case and OSs are providing you options to do it nevertheless, if you ask them politely.
iOS
As of iOS 11, there is a distinction between updating the location when in use and when in background. The user can choose which one to grant and you'll have to handle it appropriately.
According to this guide you'll have to add the NSLocationAlways key to your Info.plist to contimue getting the location when in background.
Android
From the Android developer guide
In an effort to reduce power consumption, Android 8.0 (API level 26) limits how frequently background apps can retrieve the user's current location. Apps can receive location updates only a few times each hour.
Anyway
The system distinguishes between foreground and background apps.
An app is considered to be in the foreground if any of the following is true:
It has a visible activity, whether the activity is started or paused.
It has a foreground service.
...
According to this, you can create a foreground service, see here more about it
For this reason, foreground services must show a status bar notification with a priority of PRIORITY_LOW or higher, which helps ensure that the user is aware of what your app is doing.
So if you are starting a foreground service that is shown in notification bar, you should be able to retrieve updates, even if your apps main Activity is not in foreground.
I set my tango down for a couple of months while busy with other things. I charged it for a bit, turned it on and saw the red battery icon. I charged it overnight and saw the green battery symbol. I clicked the power button The splash screen came up, said it was installing updates and screen turned off. That evening I tried to turn it on and it wouldn't do anything. Next morning it turned on - splash screen - white screen, off. Now it doesn't do anything at all. I've tried - volume button and power, both volume buttons...nothing. Has anyone else had this problem? Any ideas? Thanks.
On the below instruction. it only diagnose your device for hardware and BSP level problem. Tango Core and Apps related is not included.
To diagnose your device problem. First we need reset your device.
Hard Reset device
Press your device power key for around 8-10 secs.
sometimes you will see the backlight of screen is off.
Diagnose what is going on on your tango devices
2.1 Check basic bootloader function.
Plug in device with a charging usb cables.
2.1.1 if your device is out of power.
It will show red battery icon. or green icon which you device still enough battery to boot it up.
2.1.2 if your device is not any icon pop up.
Try 1 step again. or
switch different Usb cables and chargers or charging docks.
If it still doesn't work.It is possible a hardware issues now. you may need to contact project-tango-help#google.com
2.1.3 if you do see the battery icon, but without charging icon on it.
That mean something wrong with your charging cable or devices. Switch different charger and cables. if problem still exists. you may need to contact project-tango-help#google.com
2.2 Check the Software side of the devices
if you can see the icon in 2.1.1, that is good.
Normally on Green icon, you can boot up your device.
2.2.1 after the icon is gone, press the power key are 1-3 secs, device will boot up.
you will see the tango icon and the rolling tango icon as part of booting process.
if you get stuck at this two process forever. it means that there is some problem on booting image on android. please go to section 2.3.
if you can see the Android UI without problem. you are fine.keep a eye on your battery. if it show 50% on charging full. and some weird condition. you may need to contact project-tango-help#google.com for more details.
2.3 Recovery your device by android recovery mode.
if you android system can't boot up successfully, Recovery your device is needed. Remember it will wipe out all your data,and cache. so try to backup your data if possible.
2.3.1 If you device can access by ADB, try : adb reboot recovery
or try below steps:
{ make sure device is off,
press the power key with volume Up and Down key at the same time for around 2-3 seconds, till you see Bootloader menus
you will see
{
Continue
Fastboot protocol
Recovery mode
Reboot
Power off
Force Recovery
}
by using volume Up and Down, and power key you can select the item.
select "Recovery mode"
2.3.2: now you are at Tango android recovery mode.
it will show
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
Using Volume down key for moving, and power key for selecting.
The same step as normal Android recovery step.
1. wipe cache partition
2. wipe data/factory reset
then select reboot system now.
Waiting device to boot up.
2.3.3, If your device is still not good. Google didn't provide the tango image for customer fastbooting the device. you had to contact project-tango-help#google.com for next step.
I have made an app with live tile for windows phone 8. The tile is programmed to refresh every 30 seconds. When the run the app in the emulator or when I deploy the app in my cell (Lumia 920) the tile works fine. But surprisingly when I downloaded the same app from the market and run it on the same device the tile doesn't update.
I did quite a bit of research on this problem and found that a similar problem is observed by many other people which can be found here.
Kindly tell me what is going wrong.
Extra Info : I have tried resizing the tile, pin and unpin the tile and hard reset. I have also tried changing the refresh period (initially the refresh period was 5 seconds). I have also checked that the background task is allowed for the app.
Thanks,
Apurva Pathak
Background agents have certain limitations, as listed below.
Background tasks can minimally be run every 30 minutes. There is a debug-only API to run them more regularly, but this is not available for released apps.
Some low power devices do not support background agents
Background tasks are limited by number on each device and can be enabled or disabled from application settings.
They do not work when power saver mode is activated.
As Mahantesh correctly pointed out your tiles work when you deploy the application because the ScheduledActionService.LaunchForTest() is allowed to run for a 60 seconds period for debugging and testing purposes ONLY.
Therefore this method cannot be called and it wont work with a time limit less than 30 minutes if the application is published to the market and users download it from there.
Since I updated to OSX Lion I got a strange issue.
I am used to never shut down my Mac, I simply put it in hibernate / sleep mode.
But since the update to Lion the mac just starts up at random times.
Day and Night I can hear the CD-Drive sound when it wakes up.
The screen does not even go on, it stays black but the as soon as you hit any key the monitor just turns on.
This is really annoying as it sometimes wakes you up at night when you MAC is booting up.
I could not find a similar issue reported yet.
Thanks
Sebastian
Given the RTC (Alarm) wake reason, ensure Wake for network activity is turned off. See the last comment in the thread at https://discussions.apple.com/thread/3247367?start=0&tstart=0
Also ensure you have not scheduled wake. See http://osxdaily.com/2010/07/17/why-mac-wakes-from-sleep/
Launch the Terminal and type the following at the command line:
syslog |grep -i "Wake reason"
OHC: stands for Open Host Controller, is usually USB or Firewire. If you see OHC1 or OHC2 it is almost certainly an external USB keyboard or mouse that has woken up the machine.
EHC: standing for Enhanced Host Controller, is another USB interface, but can also be wireless devices and bluetooth since they are also on the USB bus of a Mac.
USB: a USB device woke the machine up
LID0: this is literally the lid of your MacBook or MacBook Pro, when you open the lid the machine wakes up from sleep.
PWRB: PWRB stands for Power Button, which is the physical power button on your Mac
RTC: Real Time Clock Alarm, is generally from wake-on-demand services like when you schedule sleep and wake on a Mac via the Energy Saver control panel. It can also be from launchd setting, user applications, backups, and other scheduled events.
Hope this fixes your problem.