I brought 'Moto G24 Power' smartphone 2 days back. From day one it is overheating evening when I am doing basic tasks. I brought it from Flipkart online. There is no return, only repair from service center. Is there any heating problem with this model or is it an hardware issue? What should I do?

While downloading Android apps, sometimes I have seen apps for armeabi-v7a and x86 architecture. I read some references for armeabi-v7a and x86 architecture. However, at the end, I couldn't finalize which mobile processors and architectures belong to armeabi-v7a and which belong to x86. As per my knowledge, mobile processors commonly used in Android devices are Snapdragon (by Qualcomm), MediaTek, Exynos (by Samsung) and Kirin (by Huawei). Almost all brands explain specifications of a smartphone and almost all specifications say mobile processor is 64-bit or not. Should I conclude that 64-bit of mobile processors (Snapdragon, MediaTek, Exynos or Kirin) belong to ARM architecture? **EDIT:** To understand which SoC supports armeabi-v7a Android apk and which SoC supports x86 Android apk, I have gone through the specifications of MediaTek Helio X30 and Snapdragon 855. The specification of Helio X30 says, it supports dual-core ARM Cortex-A73 and quad-core ARM Cortex-A53 but ARM is not mentioned anywhere in the specification of Snapdragon 855. So should I conclude that Helio X30 will support armeabi-v7a Android apps and Snapdragon 855 will not support armeabi-v7a apps? Please clarify my confusions.

So I was wondering, I just got Iqoo (a Vivo brand) phone and it is supposed to have processor Snapdragon 778g. And now when I go to Settings>About Phone, I see the correct processor name. Ok? But the issue is that when I check my hardware info through any other third party app (and believe me, I have tried multiple apps) then name of the processor that I see is completely different..... Is this normal? For phones to have a different processor?? I need some guidance, so please help. Also check the attached images...... The info on GPU is as follows- Vendor: Qualcomm Renderer: Adreno (TM) 642L Maximum Frequency: 550 MHz Gracias

I have a 64bit android application with "minSdkVersion=20" (means it can be installed on Android 4.4 above). My question is: can this application be installed on Google Nexus6 with android 6 ( Marshmallow)?? Does Google Nexus 6 support 64bit apps at all?? Thanks.

I'm planning to buy a new android smartphone, and I've heard that while high processor clock speeds are good, they are also accompanied by high heating effects. Is there a way I can obtain the heat (in watt possibly) and the clock speed (in GHz) of the processor? (I'm quite new here, and I'm not really a very informed person when it comes to anything digital technology).

I am using CPU-Z to test basic things about the J7. It reports an Exynos Octa 7580, 8 cores, 8x ARM Cortex-A53 @ 1.5GHz, r0p3, 28 nm. At all times that I checked, only cores 0-3 are active, and cores 4-7 are stopped. Power saving is disabled. **Is there any way of activating all cores?** **Is there any way of at least seeing all of them active, for testing purposes?** I have found a few posts around (here and here ) mentioning that it may be the way the phone + OS kernel keep temperature in check, but I am not sure it applies to J7, and if so, how to circumvent it. **PS:** I find some times that my J7 is sluggish, so I wonder why would it have 4 processors idling if they could work (assuming the causes are processing several apps, which could be tackled by assigning different processors).

There are apps that can accomplish this task (e.g. "Kernel Adiutor" and others), however they in turn require other apps that can grant them root access to begin with, which is a lot of modification for this simple task. In any regular Linux desktop system, setting the governor at every boot would be accomplished by creating a script, for example in rc.local or a systemd-oneshot, that simply calls echo "" > /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor after each system start. What would be the Android equivalent of this solution? Is there any way to automatically set the CPU governor without installing any apps?

I wanted to purchase a 64-bit android smartphone. I looked at the processor used on the Galaxy A11. It is a 64-bit ARM Cortex-A53. And I bought this phone. Looks like I made a mistake. Android on the Galaxy A11 runs in 32-bit mode. Is it possible to switch the phone to 64-bit mode?

I am writing a script to test a large quantity of apks. Some run on x86 and some run on arm. Is there a way I can tell which apks are intended for which architecture? I have looked through the report on aapt badging with aapt dump badging application.apk. For some of the arm compatible versions I see native-code: 'armeabi-v7a' but not for all of them, and I don't see any indication of what architecture the x86 compatible apks run on. I have also tried using apktool to break apart the apk and examine the AndroidManifest.xml. I don't see anything pertaining to the chip architecture in it either. I'm looking for something on a linux platform. Any ideas?

I tried to compress my 1.6GB video in the Media Converter app by exporting it to mp4(h264,aac) on my OnePlus 3 as per https://www.quora.com/How-do-I-reduce-video-size-on-Android . However, approximately 75% of the way through the conversion (after about 30 minutes) my phone overheated and turned off (with the screen going black immediately and no shut-down procedure). I tried to turn it on in the normal way, but it would not turn on. After leaving it to cool for 5 minutes, I plugged it back into the charger and it immediately turned on automatically (displaying battery at 30%). I tried to compress the video a second time, this time putting my phone on an ice-pack to keep it cool and leaving it on charge. I touched and checked the front and back of the phone regularly to ensure it was remaining dry, was not cooling too much because of the ice pack, and was not overheating (it remained at something like 20 degrees C, approximately the same as the top of the ice pack, through most of the process - although the bottom of the ice pack remained cold). This time it turned off after 45 minutes, 1 minute before the conversion was due to complete. Immediately after it turned off I noticed a very small area near the speaker (I assume near the processor) was overly warm (though not hot). I assume the heat could not escape fast enough from the hot processor into the body of the phone. Maybe the internal thermometer was closer to the ice-pack than the processor and 'tricked' into thinking the processor was cool. Now my phone is not turning on, displaying anything on the screen, or vibrating, even after plugging it into the charger and unplugging it many times over the past 12 hours. What can I do to try and revive my phone?

I was searching weather a mobile processor be Overclocked or not so i came across an answer saying no because processor operates on PLL(phase locked loop) which if set to a particular frequency can't be changed. But i have heard about Android Overclocking with some custom kernels and rooted devices. So i need some expert opinion on this matter.

My searches on the web didn't provide suitable answers to these questions: 1) **Where is the baseband firmware stored?** My understanding is that this particular firmware is a RTOS built for the Baseband Processor (BP/CP). BP is part of a SoC, so it uses its own RAM and its own storage for the firmware. **Is the firmware really stored in another eMMC than the Android firmware ?** 2) **How does Android interact with the baseband firmware?** Again, my understanding (which may be incorrect) is that the BP communicates directly with the AP via a serial connection UART trough Radio Interface Layer (RIL). This RIL interact with Android telephony services. **When does the baseband firmware take action ?** 3) **When the modem/baseband/radio partition is used ?** It seems to me that it only contains the firmware. One thing I've found is that this partition isn't mounted during Android runtime. **Is it only mounted for modem firmware update ?**

Laptops have usually at most four cores, and dualcores are probably more common. I have recently switched from quadcore to dualcore and I can confirm there is a limited number of usecases for quadcore, even with CPU intensive tasks. On the other hands, at mobile phones, quadcores, hexacores and octacores seem to be common. Why? What tasks can utilize them? I understand that [big.LITTLE](https://en.wikipedia.org/wiki/ARM_big.LITTLE) can be a part of the answer. That is, the main benefit of so many cores is not the ability to use all of them simultaneously, but rather using a core with power consumption appropriate for the current workload. However, for example, the Snapdragon 625 has eight Cortex-A53 cores, which does not seem to be a case for big.LITTLE. Maybe the ARM architecture has a lower point of optimal performance per watt. That is, having a single core tuned for optimal performance per watt results in a lower performance on ARM than on Intel. So, more cores are used in order to deliver the performance. This is just a hypothesis. But even in this case, I don't see what workload can efficiently use, say, eight cores on a mobile phone. On laptops, I can imagine a few like full (non-incremental) compilation of a project. But on phones? * Games can be performance-hungry, but they usually require GPU performance rather than CPU, don't they? * Theoretically, multiple cores could speed up Android Lollipop/Marshmallow AOT compilation when installing or when upgrading (i.e., the phase “Optimizing apps 3/121”). I am, however, not sure if this can utilize multiple cores. As far as I remember the code, only one app is being compiled at a time, but maybe there is some parallelism within the compilation process itself. * Also Android 7+ could utilize multiple cores when compiling. But since it reportedly compiles when idle and charging, the benefit seems to be rather minimal. At least when one charges the phone overnight – I really don't care if it takes 30minutes or two hours in such a scenario.

Can we somehow connect mobile device with our pc and use pc's ram, cpu etc. on connected mobile device or is there maybe a powerful external ram and processors for mobile devices?

As the title says, do I need a smartphone with more RAM or one with a higher processor in order to load a big excel file faster ? For instance : Snapdragon 835 with 8GB RAM vs Snapdragon 845 with 6GB RAM, which is faster to load a big excel file ?

I was trying to create an Android emulator on my computer but the AVD Manager is telling me that my computer doesn't support a required feature for the "VT-x or SVM." My computer has a AMD A6-5350M processor with radeon graphics with 8GB of memory. I was wondering if there was any way to run an emulator with this configuration.

I'm using OS Monitor to look at CPU usage because I've noticed a drastic performance decrease lately. The app shows that system/xbin/sh is consuming anywhere from 10% to 70% of the CPU. This happens constantly, the process never stops appearing at the top of the list. I have a two questions: 1. What is system/xbin/sh? 2. What could be causing it to utilize so much of the CPU? 3. Is there a way to track which apps make calls to system/xbin/sh? More Info: - Android version: 4.1.2 - Phone: Motorola DROID RAZR MAXX HD - ROM: Droid Nexesque v3.8 (AOSP-based ROM) (through safestrap) - Rooted: yes - not running any anti-virus or the like adb shell top output: PID PR CPU% S #THR VSS RSS PCY UID Name 6214 0 97% R 1 182528K 92452K root /system/xbin/sh ... 6211 0 0% S 1 1428K 448K root /system/xbin/sh 6212 0 0% S 1 53500K 52596K root /system/xbin/sh ... adb shell ps output: USER PID PPID VSIZE RSS WCHAN PC NAME root 1 0 544 404 ffffffff 00000000 S /init ... root 6211 1 1428 448 ffffffff 00000000 S /system/xbin/sh root 6212 6211 53500 52596 ffffffff 00000000 S /system/xbin/sh root 6214 6212 293976 214156 ffffffff 00000000 R /system/xbin/sh ... cat /proc//cmdline output: "level 1" process: /system/xbin/sh /system/bin/debuggerd "level 2" process: /system/xbin/sh /system/etc/init.d.loader "level 3" process: /system/xbin/sh /system/etc/init.d.loader /system/etc/init.d.loader contents: #!/system/xbin/sh ############# ############# ############# # init.d.loader by puppet13th@xda # Version 0.7 19 June 2012 # to run script in background append .bgrun to script name # example : "myscript.bgrun" # ############# ############# ############# logfile=/data/init.d.loader.log loglength=65536 bgrunsign='.bgrun' if [ -f $logfile ] then log=cat $logfile currentloglength=length "$log" if [ $currentloglength -gt $loglength ] then rm -f $logfile fi fi echo " * date * init.d.loader start . . .">>$logfile echo " ">>$logfile if [ ! -d /system/etc/init.d ] then echo " creating init.d folder . . .">>$logfile mount -o remount rw /system >>$logfile 2>>$logfile if [ -f /system/etc/init.d ] then rm -f /system/etc/init.d >>$logfile 2>>$logfile fi mkdir /system/etc/init.d >>$logfile 2>>$logfile mount -o remount ro /system >>$logfile 2>>$logfile fi echo " ">>$logfile echo " i : running init.d scripts . . .">>$logfile for script in /system/etc/init.d/* do if [ -x $script ] then bgrun=grep $bgrunsign $script>/dev/null if [ $? = 0 ] then echo " - running $script in background . . .">>$logfile /system/xbin/sh $script & >>$logfile 2>>$logfile else echo " - running $script . . .">>$logfile /system/xbin/sh $script>>$logfile 2>>$logfile fi fi done echo " ">>$logfile echo " * date * init.d.loader end . . .">>$logfile echo " ">>$logfile /system/bin/debuggerd contents: #!/system/xbin/sh #init.d.loader /system/etc/init.d.loader /system/bin/debuggerd.bin Checking /data/local for things other tools might have left to "plug into init": There are four empty folders and a file named RootToolsMounts. /data/local/RootToolsMounts contents: rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdataorig /datamedia ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdataorig /ss ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc,discard 0 0 /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/block/platform/msm_sdcc.1/by-name/pds /pds ext3 rw,nosuid,noexec,relatime,barrier=0,data=writeback 0 0 /dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 /dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 Looking at /data/init.d.loader.log (~50 MB file), it is running the init.d scripts approximately every 10 seconds. I'm not too familiar with the underlying components of Android, so I'm not sure if this is a lot or not. The two scripts in /system/etc/init.d./ are init.d.loader.test and minfree. /data/init.d.loader.log contents: The log file is filled with these entries repeating every 10-12 seconds ... * Sun Feb 23 18:46:09 CST 2014 * init.d.loader start... i: running init.d scripts... - running /system/etc/init.d/init.d.loader.test... - running /system/etc/init.d/minfree... * Sun Feb 23 18:46:09 CST 2014 * init.d.loader end... * Sun Feb 23 18:46:20 CST 2014 * init.d.loader start... i: running init.d scripts... - running /system/etc/init.d/init.d.loader.test... - running /system/etc/init.d/minfree... * Sun Feb 23 18:46:20 CST 2014 * init.d.loader end... ... init.d.loader.test contents: #!/system/xbin/sh # init.d.loader tester # check /data/init.d.loader.test echo init.d.loader test >/data/init.d.loader.test minfree contents: #!/system/xbin/sh echo "2469,4938,6584,33756,36971,40186" > /sys/module/lowmemorykiller/parameters/minfree

Pokemon Go is releasing today but sadly I saw somewhere in the Internet stating that Niantic has claimed that the app is **not supported by devices with intel processor** (in my case asus zenfone 5). So I wonder why the **type of processor** will be one of the factors **determining whether the app is compatible for the device**. Any help is appreciated. =)

For example, if we're considering an quad-core processor, and if the speed given in the "specifications" is 1.8 GHz, does that meant that the combined speed of the entire set of 4 cores is 1.8 GHz, or that each of these four cores has a speed of 1.8GHz individually? In other words, if the printed spec is "quad-core 1.8 GHz", does that mean that there are 4 cores of speed 1.8 GHz?

I want to buy Moto G4 Plus phone but I am confused as they are giving us two configurations. 1) **3 GB RAM** with Snapdragon 617 **Octacore 1.5GHz** processor and 32 GB ROM 2) **4 GB RAM** with Snapdragon 617 **Octacore 1.5GHz** processor and 64 GB ROM As I searched it on Google everyone is saying that the combination of RAM and Processor always matters.High RAM and Lower processor or vice versa doesn't give us better performance. So my question is which configuration is better? why?