Android

Asus ROG Phone shows up on a retail website for $1320 USD. Ship date late Oct

Android - Wed, 09/19/2018 - 17:06

Saw an earlier post saying its $875 for the base package, up to $1800 for the special edition. The listed price at this website is at $1320, wonder if its a mid-range package with accessories

http://www.gearbest.com/cell-phones/pp_009985657800.html

submitted by /u/iMaJia3000
[link] [comments]

Any profiles with python?

Tasker: Total Automation for Android - Wed, 09/19/2018 - 16:19

Hi, I am good with python and I have intermediate knowledge in Tasker. I was wondering if are there any good profiles combining Tasker and python for practical needs. There are few websites which tell about running python scripts on Tasker, but I couldn't find any with practically useful profile (with my initial search)

I am looking forward to learn more with profiles

submitted by /u/Pogolden
[link] [comments]

My Galaxy S7 Edge exploded last night.

Android - Wed, 09/19/2018 - 15:32

Pictures: https://imgur.com/a/0EtwkRU

I had it in my back pocket before taking it out to take a picture, but it froze and shut down. After trying and failing to turn it back on for a minute or so, I put it down on my countertop and figured I'll just try again later. Literally no more than a couple seconds after putting it down the whole thing spontaneously went up in flames. I had a couple nearby towels catch fire too, thought my kitchen was gonna burn down for a moment.

I took the phone to Samsung's local customer service this morning and was told nothing can be done since I bought it two years ago and it's no longer under warranty. I'm glad I'm safe and all I lost was the phone considering how close I came to getting severe burns, but I'm pretty bummed. This was an expensive phone that I expected to last me longer, and certainly didn't expect to almost start a fire at my place.

I contacted them on twitter, but I don't really expect anything considering how bad customer service is in Morocco. I loved my S7E and my previous Galaxy phones, but I think I'm kinda done with Samsung after this.

e: a word

submitted by /u/rokhana
[link] [comments]

Android Emulator 27.3.9: 'WHvGetCapability failed. hr=0x00000000 whpx_cap.HypervisorPresent? 0'

Developing Android Apps - Wed, 09/19/2018 - 15:12

Windows 10, on VS 15.8.4 with Android Emulator 27.3.9

Attempting to run the following command:

.\Emulator -avd Android_Accelerated_X86_Oreo -partition-size 512 -verbose -show-kernel

Gives the following error:

Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release. emulator: Checking whether Windows Hypervisor Platform (WHPX) is available. emulator: WinHvPlatform.dll found. Looking for WHvGetCapability... emulator: WHvGetCapability found. Querying WHPX capabilities... emulator: WHvGetCapability failed. hr=0x00000000 whpx_cap.HypervisorPresent? 0 emulator: WHPX is either not available or not installed. emulator: CPU Acceleration: DISABLED emulator: CPU Acceleration status: HAXM is not installed on this machine emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable. CPU acceleration status: HAXM is not installed on this machine

Hyper-V and Windows Hypervisor Platform are installed and working... Running (gcim Win32_ComputerSystem).HypervisorPresent returns True.

Here is the complete log:

emulator: Android emulator version 27.3.9.0 (build_id 4899998) (CL:e7b1c928a596dd490b990f4532055950f1409e49) emulator: Found AVD name 'Android_Accelerated_X86_Oreo' emulator: Found AVD target architecture: x86 emulator: argv[0]: 'C:\Program Files (x86)\Android\android-sdk\emulator\emulator.exe'; program directory: 'C:\Program Files (x86)\Android\android-sdk\emulator' emulator: Found directory: C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\ emulator: Probing for C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu-64: file exists emulator: Auto-config: -engine qemu2 (based on configuration) emulator: Found directory: C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\ emulator: emuDirName: 'C:\Program Files (x86)\Android\android-sdk\emulator' emulator: Found directory: C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\ emulator: Probing for C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu-64: file exists emulator: try dir C:\Program Files (x86)\Android\android-sdk\emulator emulator: Trying emulator path 'C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe' emulator: Found target-specific 64-bit emulator binary: C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe emulator: Adding library search path: 'C:\Program Files (x86)\Android\android-sdk\emulator/lib64' emulator: Adding library search path: 'C:\Program Files (x86)\Android\android-sdk\emulator/lib64/gles_swiftshader' emulator: Adding library search path: 'C:\Program Files (x86)\Android\android-sdk\emulator/lib64/gles_angle' emulator: Adding library search path: 'C:\Program Files (x86)\Android\android-sdk\emulator/lib64/gles_angle9' emulator: Adding library search path: 'C:\Program Files (x86)\Android\android-sdk\emulator/lib64/gles_angle11' emulator: Adding library search path for Qt: 'C:\Program Files (x86)\Android\android-sdk\emulator\lib64\qt\lib' emulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=C:\Program Files (x86)\Android\android-sdk\emulator\lib64\qt\plugins emulator: Setting Qt to use software OpenGL: QT_OPENGL=software emulator: Quoted param: ["C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe"] emulator: Quoted param: [-avd] emulator: Quoted param: [Android_Accelerated_X86_Oreo] emulator: Quoted param: [-partition-size] emulator: Quoted param: [512] emulator: Quoted param: [-verbose] emulator: Running :C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe emulator: qemu backend: argv[00] = ""C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe"" emulator: qemu backend: argv[01] = "-avd" emulator: qemu backend: argv[02] = "Android_Accelerated_X86_Oreo" emulator: qemu backend: argv[03] = "-partition-size" emulator: qemu backend: argv[04] = "512" emulator: qemu backend: argv[05] = "-verbose" emulator: Concatenated backend parameters: '"C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe"' -avd Android_Accelerated_X86_Oreo -partition-size 512 -verbose emulator: WARNING: Crash service did not start emulator: Android virtual device file at: C:\Users\rcarson.adm\.android\avd\Android_Accelerated_X86_Oreo.ini emulator: virtual device content at C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd emulator: virtual device config file: C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/config.ini emulator: using core hw config path: C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/hardware-qemu.ini emulator: using snapshot lock path: C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/snapshot.lock emulator: Found AVD target API level: 27 emulator: Read property file at C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/build.prop emulator: No boot.prop property file found. emulator: 'magic' skin format detected: 768x1280 emulator: autoconfig: -skin 768x1280 emulator: autoconfig: -skindir (null) emulator: autoconfig: -kernel C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/kernel-ranchu-64 emulator: Target arch = 'x86' emulator: Auto-config: -qemu -cpu qemu32 emulator: Auto-detect: Kernel image requires new device naming scheme. emulator: Auto-detect: Kernel does not support YAFFS2 partitions. emulator: autoconfig: -ramdisk C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/ramdisk.img emulator: Using initial system image: C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/system.img emulator: Using initial vendor image: C:\Program Files (x86)\Android\android-sdk/system-images\android-27\google_apis\x86\/vendor.img emulator: autoconfig: -data C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata-qemu.img emulator: autoconfig: -initdata C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/userdata.img emulator: autoconfig: -cache C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/cache.img emulator: autoconfig: -sdcard C:\Users\rcarson.adm\.android\avd\Android_Accelerated_x86_Oreo.avd/sdcard.img emulator: Increasing RAM size to 1024MB emulator: VM heap size 64MB is below hardware specified minimum of 256MB,setting it to that value emulator: System image is read only emulator: Found 4 DNS servers: 192.168.0.72 8.8.8.8 fec0:0:0:ffff::1 fec0:0:0:ffff::2 emulator: found magic skin width=768 height=1280 bpp=16 Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release. emulator: Checking whether Windows Hypervisor Platform (WHPX) is available. emulator: WinHvPlatform.dll found. Looking for WHvGetCapability... emulator: WHvGetCapability found. Querying WHPX capabilities... emulator: WHvGetCapability failed. hr=0x00000000 whpx_cap.HypervisorPresent? 0 emulator: WHPX is either not available or not installed. emulator: CPU Acceleration: DISABLED emulator: CPU Acceleration status: HAXM is not installed on this machine emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable. CPU acceleration status: HAXM is not installed on this machine submitted by /u/rscarson
[link] [comments]
Categories: Android, Linux

Trying To Auto Send WiFi Password To Anyone Which Texts "WiFi"

Tasker: Total Automation for Android - Wed, 09/19/2018 - 14:20

If someone texts me "WiFi" for me to automatically reply with the name and password to that same person.

How would I do this?

submitted by /u/Yoshiezibz
[link] [comments]

Multiple Radiogroup in Android.

Developing Android Apps - Wed, 09/19/2018 - 13:25

I have 2 radiogroups in my layout. Each of the radiogroup has a number of radio buttons. I have a button with set Enabled property(false). How will I be able to check if both radiogroups are checked so I can change my button property set Enabled to true?

submitted by /u/themavencoder
[link] [comments]
Categories: Android, Linux

Steal admob ads ID

Developing Android Apps - Wed, 09/19/2018 - 13:17

Hello everyone,

I have a question. If somebody decompile my code and take ads ID. Then, if that person self click on live ads in debug mode, what will happen? will my admob will be ban because of self click? Please let me know.

Thank you

submitted by /u/MBugOnYou
[link] [comments]
Categories: Android, Linux

Once Google releases RCS support on android messages, the android platform will be a much higher threat to apple.

Android - Wed, 09/19/2018 - 12:59

Thinking about when Google will finally release rcs for Android messages made me do more research to find out that Google and Samsung are doing a collaboration for the project. Meaning when it's released, the other majority of the population that uses Apple devices will find themselves on the other side of the spectrum. Google's messaging platform is currently one of it's largest downsides (in my opinion) and with the update, the playing field will be easily leveled.

I'm kind of excited :)

submitted by /u/dlmobs
[link] [comments]

How do you handle a backend that doesn't immediately reflect changes pushed to it?

Developing Android Apps - Wed, 09/19/2018 - 12:55

The basic issue I'm facing is that the backend supporting my app can't guarantee that changes I send up will be reflected in subsequent calls to retrieve that data for some time (milliseconds-seconds range.) For example if I add a comment to a post and then retrieve the list of posts immediately after the add comment call returns, I can't expect the new comment to be reflected in the data.

I've talked with our backend engineer about this as it's obviously less than ideal but have been told there's nothing that can be reasonably done on the backend. I suggested that any call which modifies backend data not return to the client until all relevant tables have been updated but apparently that approach wouldn't work well with our architecture because the functionality to update some of the tables is asynchronous and implementing callbacks would be difficult - the update tasks are intended to be fire and forget as I understand.

If you've faced similar issues before how have you handled them? Are there any good articles which discuss this problem?

My initial thought would be to locally cache any data we send up to the server, add a timestamp and then consider that data to be 'fresher' than what I get back from the API for some set amount of time. I don't like this approach as it adds complexity to my code and feels a bit hacky but I don't see any other options. Any suggestions?

Edit: It's a relatively complex app so updating the tables on the backend is non-trivial (I think the tables in question are quick-lookup tables but I'm not a backend guy so excuse any misunderstandings.)

submitted by /u/MikeAnDev
[link] [comments]
Categories: Android, Linux

Pages