screen-not-initializing on Device_Phone didn’t get imei, And try to put on button then it works. How to fix it problem?
yusufcihan
August 5, 2019, 8:20am
#2
What will you do with IMEI?
for detection that device is already regsitered
vknow360
August 5, 2019, 8:54am
#4
First your question is not clear.
Asking questions
To improve the chance of getting help on the forum please follow these recommendations when posting a question:
Do your homework first
Search for similar questions/answers on the forum. Try forum search and also Google your problem.
Try to solve the problem yourself, and describe what you have tried. It is much more rewarding to help someone who has tried himself first.
Post in the right categorie, post only once and do not steal topics
Make sure that you post your question …
Peter
August 5, 2019, 8:56am
#6
Apps are doing things during screen initializing. So put it in a timerblock that executes say half a second after app is launched and see if it works. If it works you can then try to lower the time interval.
1 Like
vknow360
August 5, 2019, 9:09am
#7
It will not work on Screen Initialization.
Peter
August 5, 2019, 9:13am
#8
The timer enabled block in screen1 should say true
1 Like
Fabio
August 5, 2019, 9:32am
#9
This could be an option to do the same:
Introduction. My first Extension.
This extension obtains the unique AndroidID, without any permissions. Obtaining the IEMI number, or the users name can have significant privacy concerns. This extension obtains a unique value from the device, that can only be changed when the device is reset to factory defaults.
This is a great way to track individual devices, without knowing who they are, or asking for scary permissions. This helps for GDPR and other type compliance.
A use case is you wan…
