Related
Ok guys. Flashed cm11 3 days ago and everything has been working great. Woke up this morning and i get no wifi signal. Wifi is on but it picks up no wifi signals. I am in a spot where there are 5 to 6 wifi always available and none are showing. Any guesss as to why I no longer receive wifi signals into my phone? I was hoping just maybe switching from dalvik to art would fix the solution but it did not. I am hoping this is just a simple fix. I guess i could just reflash cm11.
drivermcgee said:
Ok guys. Flashed cm11 3 days ago and everything has been working great. Woke up this morning and i get no wifi signal. Wifi is on but it picks up no wifi signals. I am in a spot where there are 5 to 6 wifi always available and none are showing. Any guesss as to why I no longer receive wifi signals into my phone? I was hoping just maybe switching from dalvik to art would fix the solution but it did not. I am hoping this is just a simple fix. I guess i could just reflash cm11.
Click to expand...
Click to collapse
reflashing cm11 did not fix issue. when refreshing wifi i get : WPS has failed error.......
Try updating your build. If that doesn't work then I would do a clean flash of a "Stable build".
Sent from my SCH-I535 using Tapatalk
lost root that was the issue
My issue was not the wifi it was i lost root updating to 11.0. I tried using super su to get my root back and when i did it caused me to lose wifi. It did not get my root back either. I can reflash with factory reset and get everythign working like it should, but root is gone. Flashing the newest super user does not fix the issue. I think my only option to get root is to go back to factory and re-root and then start from scratch.
drivermcgee said:
My issue was not the wifi it was i lost root updating to 11.0. I tried using super su to get my root back and when i did it caused me to lose wifi. It did not get my root back either. I can reflash with factory reset and get everythign working like it should, but root is gone. Flashing the newest super user does not fix the issue. I think my only option to get root is to go back to factory and re-root and then start from scratch.
Click to expand...
Click to collapse
Use this version. http://download.chainfire.eu/204
Sent from my SCH-I535 using Tapatalk
No wi-fi on sspence 11-23
I also lost Wi-Fi on sspencer10's 11-23 build. I am using ART. Restoring 11-21 build brought it back, but I am waiting for new build to try again.
WPS Failed
I've never had WiFi on CM 11 and did a clean wipe to fix it on an earlier nightly. Even the Snapshot build did not fix it for me.
Is there any fix out there?
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
Thats how it is every boot it has to pre compile the code for apps
Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?
stanc74 said:
Hmm...but in pre root form, this only happened the first time after selecting runtime. Now its happening every reboot! Is this supposed to be normal for a rooted phone?
Click to expand...
Click to collapse
I don't see that issue on my s2 skyrocket running 4.4 art. I'm not running art on my n5. I'm guessing it's an issue with the franko kernel, but that's just a guess
This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app
chill out guys, this is normal behavior when using ART.
This is not normal behavior at all on stock ROM. When you switch to ART, it only does the upgrade/compile thing on the first boot. Having it redo it after every reboot is probably a compatibility issue with the ROM you are running.
mdandashly said:
When you switch to ART, it only does the upgrade/compile thing on the first boot.
Click to expand...
Click to collapse
That's my recollection as well. It still is on stock ROM. But it looks like other people who have rooted are facing issues that might have arose from kernel or app issues.
I have already wiped cache and rebuilt dalvik fwiw. Also uninstalled titanium backup while no weird odex files are noted. Only Franco kernel left as last data point but I wanted to see if others faced this problem before taking the plunge to reinstall stock kernel
dorkythegreat said:
This happens to my N5 as well. Omni 12/01 nightly + Franco r14
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It does not happen on stock rooted for me either. I would suggest returning to stock rooted to use ART. According to Omni threads they are in nightlies so stuff is expected to be wrong.
Fwiw. I've flashed stock kernel, reflashed the patched libart.so (ie. Whatsapp compatibility fix) , reinstalled whatsapp. Still no joy.
Ah... from According to:
[url]https://code.google.com/p/android/issues/detail?id=61916
The problem is identified as an extra unbalance check between MonitorEnter / MonitorExit JVM instructions, which ART does and Dalvik doesn't. Some apps (such as Whatsapp) fail to have those balanced.
The fix will be probably fixed in AOSP sooner than later...
Sooo ... everybody relax and have a cup of tea (me included) :good:[/QUOTE]
stanc74 said:
Ah... from [URL="http://forum.xda-developers.com/showthread.php?p=47473296”]this thread about ART[/URL], this upgrading on every boot seems a known ART bug related to partially incompatible apps like whatsapp
Click to expand...
Click to collapse
Hmmm... sorry for the bad news but the problem discussed in that thread is unrelated with yours. We were discussing the (initial) whatsapp incompatibility.
BTW: Using ART here (Nexus 4), absolutely no problems now
it will depend on your apps. this is normal behavior. my n7 doesnt go through it, but my n4 does. they have different apps installed. my n5 goes yhrough it as well(but only 3 apps upgrading on a reboot). its fine if you want to freak out over it, but in reality it is normal.
I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...
stanc74 said:
I have 80 apps upgrading on reboot..and these are pretty standard apps.... This is quite a mysterious situation.
Good to know its happening. Perhaps next ota will address this...
Click to expand...
Click to collapse
my nexus 4 has 92 apps that upgrade after every reboot while on ART. 92 apps, out of 183 apps.
I’m using ART. Running Purity ROM with ElementalX. No long boot issue. I did have a long boot with apps optimization when I switched to ART the first time, but since then it boots normally and quickly.
Updated to 4.4.1. Had to flash stock boot and system IMG along the way. Updated, rooted and now it seems fine. Fast reboot with no data loss!
simms22 said:
chill out guys, this is normal behavior when using ART.
Click to expand...
Click to collapse
markdapimp said:
Thats how it is every boot it has to pre compile the code for apps
Click to expand...
Click to collapse
stanc74 said:
Having just rooted and unlocked boot loader, my N5 is giving the "android is upgrading" message for 80+ apps (half the usual) on EVERY reboot. This behaviour is only seen with ART runtime. Not with Dalvik. It was also not seen when on ART in stock form. Running Franco r14 kernel with stock rom. Any ideas?
Click to expand...
Click to collapse
i am running stock 4.4.2 on N5 with bootloader unlocked and after each reboot i face the same cache rebuilt thing (android is upgrading) for all the user applications i have. Is it normal for stock rom too? have you seen any one on stock who is having otherwise?
I have this problem on my sony xperia sp running cm11, but it is happening since 5 days. Maybe it is the new version of a custom kernel, or link2sd.
Nope it's not normal. What else have you installed or flashed?
Sent from my Nexus 5 using Tapatalk
Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
I bought a Nexus 5 used online. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was update it which put it to Adroid 5.1.1 LMY48B. When any update came out after that I would try to update it, but it would not work. I would download the update, which would then let me install it, but once it restarts to install it, it gives me the Adroid fella with an "Error" underneath. This has happened for every update and now even for Android 6.0.1. I have cleared the cache and wiped the phone entirely multiple times. It is not rooted or have any custom backup's or whatever. It is just unlocked.
I literally have tried everything and haven't a clue how to fix it. Is there any hope you guys could try and help me?
Have you tried flashing a stock Google ROM and then running the update? Note that you need to unlock the bootloader before you can flash a stock ROM.
Facing same issues here but my N5 is rooted and I've not installed any custom recovery...
Sent from my Nexus 5 using XDA Free mobile app
I don't think Google updates will install on a rooted system.
Yeah tats right but my phone didn't boot up with the stock version either ...stuck in bootloop
Sent from my Nexus 5 using XDA Free mobile app