Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
The rate limiter was an intentional introduction in Jelly Bean (4.1) and the settings can not be altered by users. Device manufacturers have the ability to alter this limit in their firmware, but they have to balance heavy texters against protecting users against malicious premium rate SMS sending applications.
You may wish to contact your device manufacturer to see if they can raise the limit in their firmware.
You may wish to contact your device manufacturer to see if they can raise the limit in their firmware.
bo...@google.com
OK, just as information I'm a Galaxy Nexus user therefore writing this here instead anywhere else.
However the 'protection' mechanism is plain wrong - instead of dealing with malicious software in the market end-users are 'punished' with such limitations ruining the, otherwise great, experience of using Android. Also it won't help with such limitations because any malicious software can be aware of such restrictions thus pacing the rate of sending premium texts to avoid being noticed by the user (until the bill comes or one runs out of credit on pre-paid) and even if Google set this to hilarious 1 text per hour user still could not be aware that anything is wrong because noone is keeping track of their texting timing.
Bottomline - such restriction won't help nor solve the problem but can only be highly annoying to regular users.
However the 'protection' mechanism is plain wrong - instead of dealing with malicious software in the market end-users are 'punished' with such limitations ruining the, otherwise great, experience of using Android. Also it won't help with such limitations because any malicious software can be aware of such restrictions thus pacing the rate of sending premium texts to avoid being noticed by the user (until the bill comes or one runs out of credit on pre-paid) and even if Google set this to hilarious 1 text per hour user still could not be aware that anything is wrong because noone is keeping track of their texting timing.
Bottomline - such restriction won't help nor solve the problem but can only be highly annoying to regular users.
yo...@gmail.com
Completely agree with wojek.k. Terrible user-experience. I have unlimited texts so why would I care if I've been sending a lot of text messages. Soon we'll have to answer security questions to send a text message...
lf...@google.com
Ive gotten it a few times now and it's very irritating. Im part of the text generation and friends and I trigger off text messages like crazy, especially with those that aren't on G+. How am I suppose to text someone I like (wink) only to get cockblocked from Android itself. #fail
yo...@gmail.com
That is probably the worst "feature" I've ever seen on a phone. Why would a phone EVER limit its usage for anything? I pay for unlimited texting and I pay for my phone, why should I have to deal with this? No other phone, including the iPhone, has such a stupid limit. Clearly this does nothing to prevent spam. Please, AT LEAST let the end-user decide if they want that limit or not. It's just stupid.
[Deleted User] <[Deleted User]>
I believe that the this feature should be an option allowing users to either limit or not limit their number of texts. In my opinion that would be the best for of action. But if it is not possible to remove/bypass it, can you tell us how to remove it in our custom roms.
vh...@google.com
I agree with others here. This is a HORRIBLE implementation. I'm not even a heavy texter, but occasionally I WILL send out eg. a party invite to a group of friends, easily passing the limit of "allowed" messages (especially since a long message will count as 2-6 messages all by itself times perhaps 10 invites.
If this was at least user-definabale (like the "allow non-market apps to install" option, that would be one thing. You'd "protect" the non-savvy users, while allowing me and others to keep using our phone as we want to, but making it hard-coded like this is EXTREMELY annoying. And yes - I too have a Galaxy Nexus so I can't "talk to my carrier" - I got it precisely because I wanted the full android experience - not to get friggen told how I can't use my own phone by it.
If this was at least user-definabale (like the "allow non-market apps to install" option, that would be one thing. You'd "protect" the non-savvy users, while allowing me and others to keep using our phone as we want to, but making it hard-coded like this is EXTREMELY annoying. And yes - I too have a Galaxy Nexus so I can't "talk to my carrier" - I got it precisely because I wanted the full android experience - not to get friggen told how I can't use my own phone by it.
zy...@google.com
I called Samsung Canada about this issue and their response is that it's not something they can fix and only google can fix it. Super annoying.
vh...@google.com
Well I fixed the problem on my device but requires cwm. Basically it overwrites the limit Google has to 500 texts an hour per app
zy...@google.com
vh...@google.com
Could you share the solution? Still - it's temporary and doesnt' really solve anything, but it would be nice to don't have to deal with it for the moment...
vh...@google.com
Unfortunatelly mentioned fix doesn't seem to work (for me at least)... and this 'feautre' just cause slight problem because message wasn't sent and the dialog appeared and was dismissed because I didn't click 'allow' (and clicking any other place dismiss any dialog in android)...
vh...@google.com
This "feature" really is absolutely insane. I can't believe it. If you're going to have something like this hard coded then it CAN'T be a flat rate to fit hundreds of thousands of different users! At the very least it should be a learned average, unique to each device, based on THE USER'S personal rate of texting. Even if this was implemented through the service provider based on past billing information (average texts per month, overages, unlimited data plans), that would be a great improvement.
But of course, like everyone else has said, most importantly.. IT NEEDS AN "OFF" SETTING
But of course, like everyone else has said, most importantly.. IT NEEDS AN "OFF" SETTING
vk...@gmail.com
Really bad user experience. :-(
ja...@gmail.com
Wow.Didn't expect such daft compulsory restrictions from Android.
di...@gmail.com
I don't expect this to get sorted. Which upsets me. Mainly because my girlfriend just got the message and I'll get the blame for recommending her the Nexus 4.
yo...@gmail.com
I agree with other posters, this is a terrible user experience. There should at least be an option to INCREASE the limit of SMS messages you can send without getting this warning message. I have unlimited text messaging and i'm constantly annoyed by this warning message that pops up. Please fix this!
pa...@gmail.com
I found a couple places that deal with this issue.
http://forum.xda-developers.com/showthread.php?t=1831289
http://forum.xda-developers.com/showthread.php?p=35244366
http://digiex.net/guides-reviews/guides-tutorials/mobile-devices/9546-how-remove-android-sms-limit-gingerbread.html
I haven't tested any of these myself, but if I do, it'll be the last one designed for Gingerbread.
I haven't tested any of these myself, but if I do, it'll be the last one designed for Gingerbread.
of...@mikemitterer.at
I tried to send a number of messages to my friends wishing them a Happy New Year. Mindful of how the Networks crash around midnight, I therefore did this at 7pm, some FIVE hours early.
It was a complete and utter waste of time, as only around lunchtime the NEXT DAY, New Year's Day, did I for some reason only THEN start seeing these Sending Warning pop up acknowledgments.
What a disaster, especially as my messages to the hundreds of friends alluded to why I was sending the message so EARLY. A message they only actually got on New Year's Day afternoon, much LATER than those sent from users of any other device...
That utterly reined what I hoped to achieve, and really put a bug downer on my New Year.
I could say I suppose I see why they have introduced this feature, and then say that the problem is one of getting the balanced and limit correct, and that they are a million miles apart here, but in truth, I can accept it at all an ANY level...
Ive used Android since the original G1... If it's never been a real problem for anyone all this long time, how does it now justify a change that DOES however, negatively impacts so many. And that's putting it mildly...
Disgusting...
It was a complete and utter waste of time, as only around lunchtime the NEXT DAY, New Year's Day, did I for some reason only THEN start seeing these Sending Warning pop up acknowledgments.
What a disaster, especially as my messages to the hundreds of friends alluded to why I was sending the message so EARLY. A message they only actually got on New Year's Day afternoon, much LATER than those sent from users of any other device...
That utterly reined what I hoped to achieve, and really put a bug downer on my New Year.
I could say I suppose I see why they have introduced this feature, and then say that the problem is one of getting the balanced and limit correct, and that they are a million miles apart here, but in truth, I can accept it at all an ANY level...
Ive used Android since the original G1... If it's never been a real problem for anyone all this long time, how does it now justify a change that DOES however, negatively impacts so many. And that's putting it mildly...
Disgusting...
to...@gmail.com
CAN'T, not *can* in my previous post. "I CAN'T accept it at all...."
be...@gmail.com
Agreed. Completely horrible user experience.
bo...@gmail.com
I just got this message for the first time after receiving my Nexus 4 yesterday. Unbelievable that this has been added. Really annoying and it's a bit disappointing that the limit can't be tweaked.
al...@gmail.com
I thought android was an open handset alliance project!
ht...@gmail.com
This issue has been raised by my girlfriend on her nexus 4 and by myself, it is ridiculous please make it an in-app setting.
em...@gmail.com
I think it's a good idea but further tweaking is needed, such as allowing a silence period of 15 minutes before triggering another prompt
b....@gmail.com
If you install a 3rd party messaging app then you don't have to worry about it
ar...@nolimitdevelopment.com
It is an operating system message, so even with 3rd party messenger apps this occurs. The problem is within android not the messenger app
d....@gmail.com
Exactly - only the message will change to "X is sending a large amount of messages" (substitute X with with app name)
di...@gmail.com
Well I use gosmspro and the message warning stops
lu...@gmail.com
[Comment deleted]
cl...@gmail.com
Make sure you disable the stock messaging app
al...@gmail.com
[Comment deleted]
of...@mikemitterer.at
@31 you are right - if you disable stock messaging app the error is gone!
di...@android.com
Thank you thank you.
di...@android.com
You are using nexus 4 right? How are you liking it?
jo...@gmail.com
i dont have rooted phone how to disable stock messaging app? thanks
si...@southwales.ac.uk
Friends,
Just go to your application screen through settings and clear the cache for the messaging app. This makes the popup go away :)
Just go to your application screen through settings and clear the cache for the messaging app. This makes the popup go away :)
ko...@gmail.com
Is there any way to automate this?
AGL
AGL
ke...@gmail.com
It would be Really Nice if the user could at least __temporarily__ increase the limit for some particular duration: Say increase from 30 to 300 for, say the next 48 hours. It's Really Annoying since you must Stop Everything just contend with the pop-up and you have to do this over and over. Give the user the flexibility to at least temporarily over-ride this "feature".
sc...@gmail.com
Yes! I routinely need to send a message to 44 people in an a emergency situation, and need to click "YES" 34 times. This is just plain STUPID.
ke...@gmail.com
I'd like to add my voice to this. This feature is REALLY ANNOYING and the fact that I have no control over it on my phone is more annoying still. Put the limit in place if you must but give the user the ability to control it. Epic fail, IMHO.
je...@gmail.com
i just picked up a nexus 4 for the purpose of mas texting my 200 plus students any changes to class etc. My old HTC inspire did it fine, but now my "fancy NEXUS 4" wont?
cr...@gmail.com
I'm in a similar situation to a few people here. I recommended the Nexus 4 to my girlfriend and now I am getting the blame for a supremely irritating pop-up that seems to have been implemented to fix a problem that doesn't exist.
I find it ridiculous that I am now going to have to void her warranty by rooting her phone just to get rid of this thing. What the shit, Google?
I find it ridiculous that I am now going to have to void her warranty by rooting her phone just to get rid of this thing. What the shit, Google?
gw...@gmail.com
when google is going to fix this limit issue..??
[Deleted User] <[Deleted User]>
how do you fix it
l....@gmail.com
Does anyone know if this has been fixed in KitKat?
es...@gmail.com
Has anyone tried a third party SMS client such as Textra SMS? I've heard that it has no group messaging limits; however I have nowhere near enough contacts to test it out with. I know that it may be a pain to not be able to use the stock messaging app; however, that's probably the only way to fix it until we find out whether Hangouts SMS has the same limitations.
ke...@gmail.com
Textra has the same problem. Tge limit is something built into Android Jelly Bean.
yo...@gmail.com
Oh, OK. I didn't know it was actually a built in problem. Oh well, hopefully Google changed it in 4.4, and if they didn't, that's a big bummer.
ju...@gmail.com
Google when are you going to fix this problem? Such a stupid decision. The whole point of android is having flexibility and understanding a user is intelligent enough to make a decision in whether this is what they want to use.
At least have the ability available for those of us to change it. Search on google and you will find many people have the same problem.
At least have the ability available for those of us to change it. Search on google and you will find many people have the same problem.
ro...@gmail.com
Jesus, just remove or give us the opportunity to change the Sms sending limit...
zy...@google.com
yeah. . . .change this feature. . . .or give us the power to change it
jo...@gmail.com
Yes, please remove this feature
[Deleted User] <[Deleted User]>
Get rid of this shit
cb...@gmail.com
Follow up: this one if the main reasons I've abandoned Android (after four devices) for a Blackberry. My smartphone is an essential communication tool. If it can't
mw...@gmail.com
I'm with everyone else. This is a horrible implementation of this "feature". This crap won't stop anything. Besides, if there were a malicious program sending repeated texts that triggered this, wouldn't this just make it impossible to do anything about? A message repeatedly popping up asking if I give it permissions to send? Who has this problem anyway? I install all kinds of random crap from the market and have never had a single app attempt to send a text. I understand that doesn't mean that it doesn't happen but I'm just saying this is a terrible solution to a very minute problem.
You should at least have a whitelist or something available. The default texting app is giving me this message... What genius came up with this as a solution?!
You should at least have a whitelist or something available. The default texting app is giving me this message... What genius came up with this as a solution?!
pe...@unarin.com
We are users AND customers, not children... implement the feature by all means but allow the grown ups to control it and turn it off if they wish... this isn't Apple for gods sake!
God bless the Nanny state
God bless the Nanny state
se...@janzen.it
So other than switching to an IPhone, wtf am I suppose to do? I just got a brand new phone, I have been with Verizon since my first phone 20 years ago...and they didnt even try to explain it, or try to help me. They just said they apologize and I should try to not send as many txts. I have sent 40 txts...I sent a few on my lunch break, and the phone started prompting me every message...even when I turned it off, it did the same thing. I dont understand, on my previous 5 smartphones or however many I have never seen this.
ma...@gmail.com
This is a very annoying and useless 'feature'. The whole point of Android was to give more freedom, but something as basic as SMS being restricted somehow makes sense to the Android devs! Without even giving a choice?!
Another bad, bad decision. Seems to be a trend with Google as of late, this.
Another bad, bad decision. Seems to be a trend with Google as of late, this.
[Deleted User] <[Deleted User]>
This is still occurring for the Galaxy Nexus.
ma...@gmail.com
I solved this issue. I bought an iPhone. Never happens anymore :-D
ed...@gmail.com
Why this is marked as obsolete?
jc...@gmail.com
this is not obslolete please change the status
fa...@gmail.com
Agreed, this is not obselete!
ma...@gmail.com
What a stupid "feature"!!! So, the "write, send and forget" was the golden age? I can't text anymore while in the subway! And you know what? The same sh*t happens with Hangouts : "unable to send, tap to retry"!
What's next? Gmail?
What's next? Gmail?
ma...@gmail.com
yo...@gmail.com
Docker actually runs on VirtualBox. So it is really one thing. It is really VirtualBox and Emulator that are incompatible.
jk...@google.com
Thats not entirely true. Modern Docker for MacOS uses a component called
HyperKit [1] to talk to the CPU hypervisor through MacOS native APIs
(Hypervisor.Framework [2]). Even in this scenario, Android Emulator and
Docker are incompatible and cannot be used at the same time.
[1]https://github.com/docker/hyperkit
[2]https://developer.apple.com/reference/hypervisor
failed on Mac when trying to restore vcpu state
https://code.google.com/p/android/issues/detail?id=197915
Docker actually runs on VirtualBox. So it is really one thing. It is really
VirtualBox and Emulator that are incompatible.
HyperKit [1] to talk to the CPU hypervisor through MacOS native APIs
(Hypervisor.Framework [2]). Even in this scenario, Android Emulator and
Docker are incompatible and cannot be used at the same time.
[1]
[2]
failed on Mac when trying to restore vcpu state
Docker actually runs on VirtualBox. So it is really one thing. It is really
VirtualBox and Emulator that are incompatible.
of...@mikemitterer.at
I know we should not ask questions here but we have 2017 now and it's not possible to run Android-Emulator and Docker in parallel on the same machine (on Mac). This is MORE than annoying! Everything is dockerized these days which is great but I have to use real devices to test my Android app!! Do you just ignore developers using a Mac??
fe...@gmail.com
So, yea.. I can't work on Android on my Mac because I use Docker. Great.
lf...@gmail.com
Virtualbox 5.1.14
Android Studio 2.2.3
Tested with latest updates on all SDK / HAXM etc, and it still doesn't work.
Android Studio 2.2.3
Tested with latest updates on all SDK / HAXM etc, and it still doesn't work.
lf...@gmail.com
Just to note that if i change to a non-x86 device image, the emulator runs fine (albeit horribly slow).
But this may be because it's actually not using the HAXM thing.
But this may be because it's actually not using the HAXM thing.
yi...@googlemail.com
Same Issue here on Mac pro 2016 using HAXM and Docker for Mac(CE) with docker HyperKit (based on apple Hypervisor framework).
Dear Google Android Emulator Team:
how about build an offical docker image for Android? Android ist built on linux kernel and docker runs on linux kernel. That seems plausible to me. Developers will love it. And Linux Community will be grateful for your contribution to linux kernal and will love it too. Please do it and let us make the linux great again.
Dear Google Android Emulator Team:
how about build an offical docker image for Android? Android ist built on linux kernel and docker runs on linux kernel. That seems plausible to me. Developers will love it. And Linux Community will be grateful for your contribution to linux kernal and will love it too. Please do it and let us make the linux great again.
ju...@gmail.com
[Comment deleted]
di...@gmail.com
Virtualbox and VMWare Fusion can run together without problem. VMWare Fusion and AVD has no problem. Only Virtualbox and AVD has problem.
sh...@gmail.com
Has anyone tried working around this by running qemu in docker and X-windows on mac?
ma...@gmail.com
I just quit docker and it worked.
qa...@gmail.com
stop Docker for Mac worked for me.
qa...@gmail.com
[Comment deleted]
ub...@gmail.com
The latest HAXM update was offered to me in Android Studio 2.4 Preview 3 today and it seems to run fine together with the latest Android Emulator, the latest MacOS, Docker 1.13.0, and the latest VirtualBox.
hu...@google.com
Re #94: Yes, after updating to HAXM 6.1.1 (thanks for Intel), you are able to run Android Emulator with Docker and VirtualBox.
zy...@google.com
Considering the bug fixed: HAXM 6.1.1 (available as a part of Android Studio or on Intel website at https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager ) is designed to coexist with Docker/VirtualBox/HVF hypervisors on Mac OS
m....@agendrix.com
Important note, taken on Intel's website:
The SDK Manager will download the installer to the "extras" directory, under the main SDK directory. Even though the SDK manager says "Installed" it actually means that the Intel HAXM executable was downloaded. You will still need to run the installer from the "extras" directory to finish installation.
After installing 6.1.1, I can finally run the emulator alongside my vagrant box. YAY!
The SDK Manager will download the installer to the "extras" directory, under the main SDK directory. Even though the SDK manager says "Installed" it actually means that the Intel HAXM executable was downloaded. You will still need to run the installer from the "extras" directory to finish installation.
After installing 6.1.1, I can finally run the emulator alongside my vagrant box. YAY!
de...@gmail.com
The emulator now works with vagrant as well as with docker! Christmas came in April this year!
And yes, as mentioned in #97, I needed to run the installer from `extras/intel` directory manually.
And yes, as mentioned in #97, I needed to run the installer from `extras/intel` directory manually.
wk...@gmail.com
Hi. As of now (2017-APR-06) I've been running the latest OSX, latest Android Studio 2.3.1 from April 1. Its SDK manager said HAXM 6.1.1 should be installed. I tried spinning 1 VirtualBox VM and Android emulator afterwards:
~/Library/Android/sdk/tools]$ ./emulator @Nexus_5X_API_22
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync HAX vcpu contextInternal error: Initial hax sync failed
So whatever shipped with Android Studio didn't help me. I went to Intel's website and I've installed HAXM 6.1.1 again, by hand. This time it worked. I can run Android x86 emulator with vagrant VM.
Darwin wkoszek_laptop 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
~/Library/Android/sdk/tools]$ ./emulator @Nexus_5X_API_22
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync HAX vcpu contextInternal error: Initial hax sync failed
So whatever shipped with Android Studio didn't help me. I went to Intel's website and I've installed HAXM 6.1.1 again, by hand. This time it worked. I can run Android x86 emulator with vagrant VM.
Darwin wkoszek_laptop 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
st...@gmail.com
Hi! As it was said in #99, SDK manager does not install HAXM correctly.
After updating HAXM 6.0.1 was still installed (for my upgrade case). I checked it by running a following command:
$ANDROID_HOME/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh -v
6.0.1
I had to reinstall HAXM manually:
sudo $ANDROID_HOME/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh
After that the emulator and docker run both at the same time! \o/
After updating HAXM 6.0.1 was still installed (for my upgrade case). I checked it by running a following command:
$ANDROID_HOME/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh -v
6.0.1
I had to reinstall HAXM manually:
sudo $ANDROID_HOME/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh
After that the emulator and docker run both at the same time! \o/
ma...@gmail.com
I have been unable to start the Emulator recently on Mac OS X 10.12.4, and found that HAXM strangely wasn't installed anymore in the SDK Manager. So I chose to install it from the SDK Manager and it completed, but still the emulator would not start with Docker installed/running. I then downloaded HAXM 6.1.2 from the Intel site and installed it manually and then even with Docker running it would start.
te...@andypiper.com
Just to add my $0.02 here. There are two problems on OSX:
1. Haxm reports a conflict with virtualbox when in actual fact the conflict may be with another hypervisor (e.g. docker very common now).
2. Haxm is installed incorrectly by android sdk. I suspect the problem may be that it needs sudo permissions which it does not have and silently ignores. If I install manually (6.2.1) with sudo all is good and the error goes away even with docker running.
1. Haxm reports a conflict with virtualbox when in actual fact the conflict may be with another hypervisor (e.g. docker very common now).
2. Haxm is installed incorrectly by android sdk. I suspect the problem may be that it needs sudo permissions which it does not have and silently ignores. If I install manually (6.2.1) with sudo all is good and the error goes away even with docker running.
Description
Host Operating System: Mac
Steps to Reproduce Bug:
1. Run the qemu2-based emulator for a while
2. ???
3. It crashes with the following stack:
Thread 4
0x00000001062640a0 (libQt5Core.5.dylib + 0x000230a0 ) __ZNK14QMessageLogger7warningEPKcz
0x0000000106454998 (libQt5Core.5.dylib + 0x00213998 ) __ZN14QObjectPrivateD2Ev
0x000000010645488e (libQt5Core.5.dylib + 0x0021388e ) __ZN14QObjectPrivateD0Ev
0x0000000106456576 (libQt5Core.5.dylib + 0x00215576 ) __ZN7QObjectD2Ev
0x0000000105d27acf (libQt5Gui.5.dylib + 0x0008bacf ) __ZN8QPMCacheD2Ev
0x0000000105d2799d (libQt5Gui.5.dylib + 0x0008b99d ) __ZN8QPMCacheD0Ev
0x0000000105d29a65 (libQt5Gui.5.dylib + 0x0008da65 ) __ZZN12_GLOBAL__N_114Q_QGS_pm_cache13innerFunctionEvEN7CleanupD1Ev
0x00007fff9743046a (libsystem_c.dylib + 0x0005f46a ) __cxa_finalize_ranges
0x00007fff9743076e (libsystem_c.dylib + 0x0005f76e ) exit
0x00000001046306d5 (qemu-system-i386 + 0x0011f6d5 ) _hax_sync_vcpus
0x00000001045775ea (qemu-system-i386 + 0x000665ea ) _run_qemu_main
0x00000001046347ea (qemu-system-i386 + 0x001237ea ) __ZL20enter_qemu_main_loopiPPc
0x0000000106276811 (libQt5Core.5.dylib + 0x00035811 ) __ZN14QThreadPrivate5startEPv
0x00007fff982e2c12 (libsystem_pthread.dylib + 0x00003c12 ) _pthread_body
0x00007fff982e2b8f (libsystem_pthread.dylib + 0x00003b8f ) _pthread_start
0x00007fff982e0374 (libsystem_pthread.dylib + 0x00001374 ) thread_start
0x00000001062766bf (libQt5Core.5.dylib + 0x000356bf ) __ZN14QThreadPrivate21createEventDispatcherEP11QThreadData
>>> 0x0011f6d5 ) _hax_sync_vcpus
This is the function which has no other choice but to exit if hax ioctl() fails
The crash itself happens deep in Qt code, but the reason is this failed HAX call which results in exit() and the following bad things