Database Users

having problems downgrading my Razr M back to ICS

hey guys i'm having issues downgrading my Razr M back to ICS. I did read through alot of threads, I downloaded RSD Lite 6.1.4 then i downloaded the software for Razr M ICS. I then followed the instructions and opened up the XML file and deleted the GETVAR line and OEM line. but it just gives me an error when i try to flash the file, can somone tell me what i'm doing wrong?
I got this file US|Verizon|4.0.4|Blur_Version.77.111.10.XT907.Verizon.en.US
it came out as VZW_XT907_4.0.4-7.7.1Q-144_SMQ_S1-36-10_CFC.xml after i unzipped it.
then i went and edit VZW_XT907_4.0.4-7.7.1Q-144_SMQ_S1-36-10_CFC.xml to delete the GETVAR line
I then loaded it into RSD to try to flash, it says failed and now the phoen is stuck in AP fastboot because it had a flash failure.
can somone tell me what i did wrong? do i need to rezip it into a SBF file?
edit: so i reflashed the 4.1.2 file on there and now it turns back on. but can somone tell me how to take it back to 4.0.4? here is the XML file i edited if anyone is interested
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SM_VZW_CFC" />
<software_version version="scorpion_mini-user 4.0.4 7.7.1Q-144_SMQ_S136-10 20 release-keysSM_BP_1139.000.32.12P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="164ABBBEDFC1A113F5A1890DD63C0A93" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="169C16EE30F086C084EFB239741E9775" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="2A98236BC098E74D9EE9CBBC6049FB2C" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="112950A3D7962D7E8E0A1B115DC0E796" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="16C5ED30D233CE9BDB8D271DE163C38A" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="567676B28DF3B060A443FEADA9C5C783" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="ADCDB8732B367F57B1975B447A9AA2AC" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="45429E3985203D3A1E7334C09BD237C7" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0B28FEFE8D9FCF02B6F92A582D5D7A07" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="boot" filename="boot.img" MD5="C75BBEA9B6879CDFBE95A2801C6A0CE0" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="5F2DA0989ED59E2508716DCA88011746" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="3C96F96D399B4AAAC7C9A7222FEF05F2" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
</steps>
</flashing>

The undisputed easiest way is Matt's utility 1.2
You need to be in AP fast boot and it will flash the latest stock ota from Verizon which is not ICS. I'm afraid to say once you go jellybean, no more ICS. Seriously though the utility is a one stop shop to restore, root, unlock boot loader, and flash a recovery.
Sent from my XT907 using Xparent Cyan Tapatalk 2

bmplekan said:
The undisputed easiest way is Matt's utility 1.2
You need to be in AP fast boot and it will flash the latest stock ota from Verizon which is not ICS. I'm afraid to say once you go jellybean, no more ICS. Seriously though the utility is a one stop shop to restore, root, unlock boot loader, and flash a recovery.
Sent from my XT907 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
O once i am at JB i cant downgrade to ICS? damn okay thanks

If your boot loader is locked, you can't go back. If you unlock your boot loader, you can use the FXZ files to go back.

RikRong said:
If your boot loader is locked, you can't go back. If you unlock your boot loader, you can use the FXZ files to go back.
Click to expand...
Click to collapse
so if i get the Bootloader unlocked, i can go back to 4.0.4 even though its on JB?
So i got SU and BL unlocked on JB, i'm searching for FXZ files and its not talked about much. I saw the bat utility, and i also have the SBF file. can you give me a little more direction please.
thanks

TELL ME HOW... lol
truwrxtacy said:
so if i get the Bootloader unlocked, i can go back to 4.0.4 even though its on JB?
So i got SU and BL unlocked on JB, i'm searching for FXZ files and its not talked about much. I saw the bat utility, and i also have the SBF file. can you give me a little more direction please.
thanks
Click to expand...
Click to collapse
you've unlocked??? please inform me as to how? i'm completely stumped. i have root access and everything in the latest 4.1.2 OTA and i can't unlock. no suprise, the phone isnt eligible for a motorola tool unlock using their site...

It's not possible with the latest 4.1.2 OTA, but with some earlier it was.

[Q] how to add permissions to android manifest?

Hey guys,
First timer here made a small test app recently, then i realized that wen u install the apk the permissions were not shown even though i wrote them in the manifest following the permissions guide in android.developer.com... i would like some help with this, a video tutorial will do great but screenshots guide will do fine aswell.
thanks in advance guys

Do it like this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
... >
<uses-sdk
... />
[COLOR="Blue"]<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />[/COLOR]
<application
... >
<activity
... >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<!-- Your other components -->
</application>
</manifest>
However, some permissions won't be shown as they are development or system permissions which cannot be granted to normal apps.
Which one are you talking about?

Mocolocoroco said:
Hey guys,
First timer here made a small test app recently, then i realized that wen u install the apk the permissions were not shown even though i wrote them in the manifest following the permissions guide in android.developer.com... i would like some help with this, a video tutorial will do great but screenshots guide will do fine aswell.
thanks in advance guys
Click to expand...
Click to collapse
if you are using eclipse as die you may use the "Manifest" Editor which can easy generate your manifest and your permissions.
If you are using Android Studio with latest SDK then there is an Auto completing.
If you want to add permissions be carefulll. some devices will not be able to download your app.
Use use-feature and disable required if you still want the app listed in playstore for devices which has (for example) no Bluetooth or camera
Here is an example of one of my apps.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="de.seiboldsoft.myapp
android:versionCode="10"
android:versionName="1">
<uses-sdk
android:minSdkVersion="11"
android:targetSdkVersion="17" />
<permission
android:name="de.seiboldsoft.myapp.permission.C2D_MESSAGE"
androidrotectionLevel="signature" />
<uses-feature
android:name="android.hardware.camera.autofocus"
android:required="false" />
<uses-feature
android:name="android.hardware.camera.flash"
android:required="false" />
<uses-feature android:name="android.hardware.location" />
<uses-feature
android:name="android.hardware.location.gps"
android:required="false" />
<uses-feature
android:name="android.hardware.microphone"
android:required="false" />
<uses-feature
android:name="android.hardware.camera"
android:required="false" />
<uses-feature
android:name="android.hardware.telephony"
android:required="false" />
<uses-feature
android:name="android.hardware.bluetooth"
android:required="false" />
<uses-feature
android:name="android.hardware.touchscreen"
android:required="false" />
<uses-feature
android:name="android.hardware.wifi"
android:required="false" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.ACTION_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.DISABLE_KEYGUARD" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.WRITE_SMS" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
<uses-permission android:name="android.permission.PROCESS_OUTGOING_CALLS" />
<uses-permission android:name="android.permission.BATTERY_STATS" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.KILL_BACKGROUND_PROCESSES" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="de.seiboldsoft.theftspy.permission.C2D_MESSAGE" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.READ_CALL_LOG" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.INSTALL_PACKAGES" />
<uses-permission android:name="android.permission.DELETE_PACKAGES" />
<uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="com.android.vending.BILLING" />
<uses-permission android:name="android.permission.MANAGE_ACCOUNTS" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="com.android.vending.BILLING" />
<uses-permission android:name="android.permission.USE_CREDENTIALS" />
<uses-permission android:name="android.permission.ACCESS_SUPERUSER" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.UPDATE_DEVICE_STATS" />
<uses-permission android:name="android.permission.BIND_ACCESSIBILITY_SERVICE" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/myapp"
android:largeHeap="true"
android:logo="@drawable/ic_launcher"
android:launchMode="singleTop"
android:theme="@android:style/Theme.Black">
<receiver
android:name="com.google.android.gcm.GCMBroadcastReceiver"
androidermission="com.google.android.c2dm.permission.SEND">
<intent-filter>
<action android:name="com.google.android.c2dm.intent.RECEIVE" />
<action android:name="com.google.android.c2dm.intent.REGISTRATION" />
<category android:name="de.seiboldsoft.myapp" />
</intent-filter>
</receiver>
<activity
android:name=".activities.StartAcitvity"
android:configChanges="orientation|keyboardHidden|screenSize"
android:label="@string/myapp"
android:launchMode="singleInstance"
android:theme="@style/Theme.Transparent">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<service android:name="GCMIntentService" />
<activity android:name=".modules.AlarmActivity"></activity>
<service
android:name="AndroidService"
android:exported="false"
android:label="@string/myapp" />
<service android:name=".modules.ModulCamera" />
<!-- cropped lots of stuff -->
</application>
</manifest>

thanks
but do any of these permissions listed show on screen wen the user tries to install m apk?

Mocolocoroco said:
but do any of these permissions listed show on screen wen the user tries to install m apk?
Click to expand...
Click to collapse
Most permissions are shown when the app is installed. However, not all are shown.
Which one do you have problems with?

i tried this for starters
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT"/>
<android.permission-group.ACCESSIBILITY_FEATURES />
and none of them seem to appear wen i install,any suggestions?

Mocolocoroco said:
i tried this for starters
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT"/>
<android.permission-group.ACCESSIBILITY_FEATURES />
and none of them seem to appear wen i install,any suggestions?
Click to expand...
Click to collapse
Maybe you put them into the wrong place of the XML. Could you please provide more of the file?
(You can delete all Activities except one if you want to. But please let one tag of each kind stay there so that we see whether it is in the right place or not. )

<uses-sdk
....
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT"/>
<android.permission-group.ACCESSIBILITY_FEATURES />
<application
...
<activity
<intent-filter>
</activity>
</application>
</manifest>

Mocolocoroco said:
<uses-sdk
....
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.FLASHLIGHT"/>
<android.permission-group.ACCESSIBILITY_FEATURES />
<application
...
<activity
<intent-filter>
</activity>
</application>
</manifest>
Click to expand...
Click to collapse
You've got a <manifest> tag at the beginning, too, right?
Are you able to install the app?
The only thing left which I can offer is that you send one of us your project and we will check it.
You can remove all stuff that is not related to this. And then we will try.
Everything else is difficult. You know, we're not sitting next to you.

yea i hav the <manifest open and yes im able to install the app aswell....and how will i send u the manifest file? or do u want the apk?

Mocolocoroco said:
yea i hav the <manifest open and yes im able to install the app aswell....and how will i send u the manifest file? or do u want the apk?
Click to expand...
Click to collapse
Well, with the apk I can check whether I see the permissions.
With the manifest I can try it out myself.
You can upload it to dropbox or something like that and send me the download link via PM.

alrite it will take awhile cause ill hav to make a dropbox account...shall i upload the manifest file in a word or how do i send the manifest to you?

Mocolocoroco said:
alrite it will take awhile cause ill hav to make a dropbox account...shall i upload the manifest file in a word or how do i send the manifest to you?
Click to expand...
Click to collapse
Just upload the xml.
If you want it to be accessible for everyone, you can also post it as an attachement on XDA.
I'll wait.

the xml file is not getting uploaded ill just pm u the dropbox links now

Mocolocoroco said:
the xml file is not getting uploaded ill just pm u the dropbox links now
Click to expand...
Click to collapse
Thanks. Got your PM and the file. You can delete the apk if you want to.

OK. Tested the manifest you sent to me.
To do that I created a new project and replaced the manifest. I installed it on an emulator and went to the settings. This is what I see for the app:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will test it on a real device now.

On the device I see the permissions, too.
Should I send you the project files?

yea if u cud send them that would be great...and how do i use them to change my current project???

Mocolocoroco said:
yea if u cud send them that would be great...and how do i use them to change my current project???
Click to expand...
Click to collapse
My test project.
I don't know how much this will help you. Could you please post a screenshot of your directory structure (or send it to me via PM)?
Maybe that is the problem.

what do you mean by the directory structure? as in the package explorer?

[Q] [DEV]Where is the AppOps in custom ROMs of kitkat?

Kitkat has included a more powerful AppOps, which could even limit background wakeups of apps selected by users, while many bugs seen from 4.3 have been solved too.
Developers, by deleting the reference and setting the enable status to true, the best privacy protector could be back online.
https://android.googlesource.com/pl...ttings/+/android-4.4_r1.1/AndroidManifest.xml
line801~819
Code:
<!--
<activity android:name="Settings$AppOpsSummaryActivity"
android:label="@string/app_ops_settings"
android:taskAffinity=""
android:excludeFromRecents="true"
android:enabled="false">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<action android:name="android.settings.APP_OPS_SETTINGS" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.VOICE_LAUNCH" />
<category android:name="com.android.settings.SHORTCUT" />
</intent-filter>
<meta-data android:name="com.android.settings.FRAGMENT_CLASS"
android:value="com.android.settings.applications.AppOpsSummary" />
<meta-data android:name="com.android.settings.TOP_LEVEL_HEADER_ID"
android:resource="@id/application_settings" />
</activity>
-->

Is it possible to enable this part on an already installed custom ROM? In my case I'm using KITKALO but AppOps are not (yet?) enabled.

excelari said:
Is it possible to enable this part on an already installed custom ROM? In my case I'm using KITKALO but AppOps are not (yet?) enabled.
Click to expand...
Click to collapse
Need re-building the rom.

here's a workaround:
http://forum.xda-developers.com/showthread.php?t=2540233

[Q] Issues after updating to .15 (NOT root or BL related)

My wife had a water mishap with her G2 which made it unusable. I flashed the .15 update on an old RAZR M for her to use. The bootloader was unlocked prior to the update. She doesn't care about being rooted or anything, just wants a phone to use. After flashing the update the entire phone is all wonky.
First off, a message pops up saying the UIDs are inconsistent and the data partition should be wiped or the device will be unstable.
Then, all sorts of apps start "stopping" with error message after message.
The Play store won't even open in order to update apps.
Any ideas how to solve this??

Where did you get the .15?... It kinda sounds like a bad flash... I would re download and flash it again... Maybe (as its unlocked) modify the XML of .10 flash it give it a run if all is good and you/she wants the .15 flash it.. Or wipe the partitions manually and flash them... Idk the fastboot commands but I can look for the thread where they are posted if that is the route that is needed to resolve the issue
We cannot teach people anything; we can only help them discover it within themselves.

dbreezy187 said:
Where did you get the .15?... It kinda sounds like a bad flash... I would re download and flash it again... Maybe (as its unlocked) modify the XML of .10 flash it give it a run if all is good and you/she wants the .15 flash it.. Or wipe the partitions manually and flash them... Idk the fastboot commands but I can look for the thread where they are posted if that is the route that is needed to resolve the issue
Click to expand...
Click to collapse
I got the .15 file from somewhere here, at least the links were from somewhere here. I'll re-download and try flashing again.
Since it was previously unlocked is it actually possible to fool it into flashing .10 and re-rooting? It's not that important really but I'd really prefer to root it for her and at least get rid of the bloat.
The most important thing is to actually get it to work properly.

Since your unlocked you have your freedom still. Don't like kk? You can go back to jb 4.1.2. Root on even .15 is as easy as flashing a recovery in fastboot and flashing su zip. As for your issues. They don't sound like the normal kk issues. I agree with dbreezy187 try a reflash

thewraith420 said:
Since your unlocked you have your freedom still. Don't like kk? You can go back to jb 4.1.2. Root on even .15 is as easy as flashing a recovery in fastboot and flashing su zip. As for your issues. They don't sound like the normal kk issues. I agree with dbreezy187 try a reflash
Click to expand...
Click to collapse
I didn't think you could go back to anything once you've flashed .15?!?
Are you saying I can start all over since I was unlocked prior to flashing .15?

chucklehead said:
I didn't think you could go back to anything once you've flashed .15?!?
Are you saying I can start all over since I was unlocked prior to flashing .15?
Click to expand...
Click to collapse
I believe you can yes... I've read a few posts from people that went from .10 all the way down to ICS so I would think the same method could be used... Just modify the XML of the firmware your flashing remove the get_ver line and you should be good to flash it
We cannot teach people anything; we can only help them discover it within themselves.

dbreezy187 said:
I believe you can yes... I've read a few posts from people that went from .10 all the way down to ICS so I would think the same method could be used... Just modify the XML of the firmware your flashing remove the get_ver line and you should be good to flash it.
Click to expand...
Click to collapse
I don't see such a line in the xml file of any of the firmwares I've downloaded:
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VZW_XT907_CFC" />
<software_version version="smq_vzw-user 4.4.2 KDA20.62-10.1 10 release-keysSM_BP_101031.042.32.86P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="B06997B2407D87205454D47A4DE2CA77" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="9EBD6FB39A7DDBD3DD8BB0F0E7B4E612" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="B3D58C0A21BAA8DEAC238B6002ABB59E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="6ACFA1DA4F8FF45341D7C2EC40C733F7" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="974770FC264C73E429B716F1832A8C38" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="56CC3781D10C94A342F5262560EFEFDB" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="42661F0BBF0DB568369F9337324F7BEC" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="boot" filename="boot.img" MD5="B59DF3268823BCE19DF80409C036645D" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="2FD6AB345BBE5B6C99DE1B5CE1D56F2C" />
<step operation="flash" partition="system" filename="system.img" MD5="1362E5D51CA3D71089F9B48A836624C9" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>

Its the getvar line I'm sorry
We cannot teach people anything; we can only help them discover it within themselves.

Device not supported for meizu mx5

Device model Meizu MX5
OS version (android version 5.0.1)
I have that device, and i get error device is not supporting when i download app from store and try to launch the application.
https://play.google.com/store/apps/details?id=com.netvariant.banknizwa
Possible to know some reasons? and why?

The manifest
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_USER_DICTIONARY" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.READ_USER_DICTIONARY" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-feature
android:name="android.hardware.location.gps"
android:required="false" />
<uses-feature
android:name="android.hardware.location.network"
android:required="false" />
<uses-feature
android:name="android.hardware.wifi"
android:required="false" />
<uses-feature
android:name="android.hardware.location"
android:required="false" />
<uses-feature
android:name="android.hardware.screen.portrait"
android:required="false" />
<uses-feature
android:name="android.hardware.telephony"
android:required="false" />
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="22" />
<uses-feature
android:glEsVersion="0x00020000"
android:required="true" />

An xposed module disable device check on playstore just apply this module ;D

How would you do that?