So, Guys and Gals, as we all know, Motoroal just dropped their Lollipop Bomb after ages in our LOVED MOTO X (Still in Brazil though), which is expected to hit our INDIAN MARKET(XT1052) by a couple of weeks maximum stretched to a month.
But some of our good friends in here had already posted threads about how to side load 5.1 using TWRP backup.
* (http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594) *
So if you can't skip the beat to get ur hands on to the new one, do visit the thread to a wonderfull explanation and procedure.
*I myslef will be going on with in by this evening*
So, all said and linked, the following lists the known issues and doubts about upgrading/downgrading back and so on. (Gathered by going through all the threads realted to LP 5.1)
*It will really helpfull if you add on your issues and doubts in this one place so to help each other in resolving the said and please do mention your X's Model No. *
My device : XT1052(INDIA),KK 4.4.4(stock ROM),bootloader unlocked,Recovery Twrp, Xposed Installed.
Doubts :
1. When can we expect the OTA to push in India.?
2. If and when we officially receive the OTA, what shoud I need to do, for the installation process.? (As heard without stock recovery, OTA doesn't get installed)
3. Can We go back to my stock 4.4.4(If have it twrp backed up) if we don't like or the side-load LP 5.1 or it causes any issues.?
Now for the Issues read around :
1. The speakerphone bug, will it be bugging XT1052(or any other model) if we use your method.?
2. The network switching issues.? will it be also may bug XT1052(or any other model).?
3. "Android is updating" on every boot, is this also an issue..?
[update] 24/4/15
After installing from the backup and using for alomost half a day, some things got cleared and some bugs are found , as follows :
*All this bugs are for the model XT1052(europe/asia)*
1. The speakerphone bug is persitent (not gets activated when clicked during call, but does work when first placed call in speaker phone mode. both issues are vice-versa for speaker phone and ear piece)
2. Android updating and network switching is not present on my phone.
3. [New Bug] the corrective text suggestion while typing words blink misses while showing the suggestions.
Rest, still happy with my X(not ex)
rohitdna said:
So, Guys and Gals, as we all know, Motoroal just dropped their Lollipop Bomb after ages in our LOVED MOTO X (Still in Brazil though), which is expected to hit our INDIAN MARKET(XT1052) by a couple of weeks maximum stretched to a month.
But some of our good friends in here had already posted threads about how to side load 5.1 using TWRP backup.
* (http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594) *
So if you can't skip the beat to get ur hands on to the new one, do visit the thread to a wonderfull explanation and procedure.
*I myslef will be going on with in by this evening*
So, all said and linked, the following lists the known issues and doubts about upgrading/downgrading back and so on. (Gathered by going through all the threads realted to LP 5.1)
*It will really helpfull if you add on your issues and doubts in this one place so to help each other in resolving the said and please do mention your X's Model No. *
My device : XT1052(INDIA),KK 4.4.4(stock ROM),bootloader unlocked,Recovery Twrp, Xposed Installed.
Doubts :
1. When can we expect the OTA to push in India.?
2. If and when we officially receive the OTA, what shoud I need to do, for the installation process.? (As heard without stock recovery, OTA doesn't get installed)
3. Can We go back to my stock 4.4.4(If have it twrp backed up) if we don't like or the side-load LP 5.1 or it causes any issues.?
Now for the Issues read around :
1. The speakerphone bug, will it be bugging XT1052(or any other model) if we use your method.?
2. The network switching issues.? will it be also may bug XT1052(or any other model).?
3. "Android is updating" on every boot, is this also an issue..?
Rest, still happy with my X(not ex)
Click to expand...
Click to collapse
Have you found a solution to the "Android is starting..." on every boot yet?
I don't have the issue of andorid is updating on booting, but the speakerphone thing is I guess the only bug I found in 4hrs of my usage...
Can any one help me with this.?
rohitdna said:
I don't have the issue of andorid is updating on booting, but the speakerphone thing is I guess the only bug I found in 4hrs of my usage...
Can any one help me with this.?
Click to expand...
Click to collapse
yup speaker phone bug is present no fix till now... also i realized that the proximity sensor is always on even when the phone is in sleep ( this was there in kitkat also for the active display to show up when you reach near the phone) however it does nothing. also i saw the screenshot of the 2014 moto x moto assist services it has an option to enable the active display to light up, this option is missing in the moto x 2013 moto assist
jcrahul said:
yup speaker phone bug is present no fix till now... also i realized that the proximity sensor is always on even when the phone is in sleep ( this was there in kitkat also for the active display to show up when you reach near the phone) however it does nothing. also i saw the screenshot of the 2014 moto x moto assist services it has an option to enable the active display to light up, this option is missing in the moto x 2013 moto assist
Click to expand...
Click to collapse
proximity sensor thing might be hardware dependant, cause I heard moto x 2014 have more than one proximity sensor.. other than that, found one more bug.. on the text correction part, whenever a word is misspelled , the corrective suggestions option doesn't show up, i mean to say, it blink misses..
rohitdna said:
proximity sensor thing might be hardware dependant, cause I heard moto x 2014 have more than one proximity sensor.. other than that, found one more bug.. on the text correction part, whenever a word is misspelled , the corrective suggestions option doesn't show up, i mean to say, it blink misses..
Click to expand...
Click to collapse
the 2014 moto x has 4 proximity sensors to be exact, one on each edge so that the phone can sense when you are reaching from any direction, this was an upgrade when compared to 2013 moto x
rohitdna;60297566
[update said:
24/4/15
After installing from the backup and using for alomost half a day, some things got cleared and some bugs are found , as follows :
*All this bugs are for the model XT1052(europe/asia)*
1. The speakerphone bug is persitent (not gets activated when clicked during call, but does work when first placed call in speaker phone mode. both issues are vice-versa for speaker phone and ear piece)
2. Android updating and network switching is not present on my phone.
3. [New Bug] the corrective text suggestion while typing words blink misses while showing the suggestions.
Rest, still happy with my X(not ex)
Click to expand...
Click to collapse
clear data or clear cache for the dialler app it fixed the loud speaker bug or the speaker phone bug is resolved. i used clear data. hope it helps u all.
princeflash said:
clear data or clear cache for the dialler app it fixed the loud speaker bug or the speaker phone bug is resolved. i used clear data. hope it helps u all.
Click to expand...
Click to collapse
Thanks..
But I returned to my old KK 4.4.4 using the TWRP backup I made before going with LP 5.1
Will wait for the Official OTA to arrive in my region.
I will be waiting too for official 5.1.Most of the phones don't get even 4.4...
rohitdna said:
proximity sensor thing might be hardware dependant, cause I heard moto x 2014 have more than one proximity sensor.. other than that, found one more bug.. on the text correction part, whenever a word is misspelled , the corrective suggestions option doesn't show up, i mean to say, it blink misses..
Click to expand...
Click to collapse
I get the proximity sensor work one time in soak test, and sure that is software problem.(but in this time , I can't add google a/c)
I use backup method upgrade to 5.1 and also not work.
I go back to 4.4.4 for my TWRP backup and also not work.
BUT when I restart sometimes(3-4), I got message "Uninstall Motorola Sensor Services" , after uninstall and restart, it work again.
P.S. I check the setting > APP info > Motorola Sensor Services, the version is not same in 4.4.4 or 5.1.
4.4.4 1.63.1
5.1. 1.64.3
updated my moto x xt1052 from 4.4.4 to 5.1
-bug loudspeaker already present, also if i wipe data of dialer app
-sensor doesn't work to awake display when the device is in standby
- with game Clash of Clans i see some video issues on some menu, for example some icon flickering...
toroloco73 said:
updated my moto x xt1052 from 4.4.4 to 5.1
-bug loudspeaker already present, also if i wipe data of dialer app
-sensor doesn't work to awake display when the device is in standby
- with game Clash of Clans i see some video issues on some menu, for example some icon flickering...
Click to expand...
Click to collapse
yes even i have some screen tearing when playing COC
Hello guys,
I've recently bought this phone Motorola Moto g4 Plus and everything was fine. Until 1 day I cloned my old phone's apps into new one.
I had Sony's TrackID, which I use to search for tracks that were playing on radio. Even in this phone it worked great with external speakers. But when I plugged in earphones, it couldn't recognize a single track. Instead it popped up an error stating that it cannot hear any audio.
Since then I've tried Shazam, SoundHound, etc. These apps work great through my speakers. But fail every time when I plug in my earphones. Same error pops up saying there's no audio. Hoping for a solution from XDA.
Thanks in advance!
P.S. - I've tried reinstalling all the apps (Shazam, SoundHound). My phone's running on latest android build, Marshmallow 6.0.1
My phone is not rooted. I don't want to root it as I already use a rooted phone.
Have you get it fixed? I've been having the same issue
Flashing the very first 6.0.0 (MDA89D).
In my ventures this last week or so, after dealing with the Battery issue (15-30% power off range) and having my speakerphone mysteriously stop working (It was as if I hit mute to the person on the other end) I have been doing all the research and tinkering I could think of to see if these were indeed hardware or software issues with our 6P.
So in my venture, It may be that 7.1.1 fixed the battery issue for me, as after 3 full rundowns over the past few days, I was able to run down to 3% and then 1% 2 times before shutdown which is immensely better than shutdown anywhere from at best 13% to ~25-30% at worst when you're trying to use your phone through the day.
This was done by running the Mountain app to put a load on the device while I do other things. Once I see it hit 15% I allow it to turn on Battery Saver and watch as it ticks down to 1-0% and goes into Shutdown.
Not sure how truly comprehensive this test is, but so far, it is pretty incredible to have such an improvement over what many of us have been experiencing with our battery life being a cointoss through the day.
I only had 7.1.1 flashed as a fresh image straight from google, TWRP 3.0.2-3 and SuperSU 2.78 SR5 for Root for this test. No Google Account connected or anything else syncing or updated that would touch the battery or run in the background.
Now for my Speakerphone issue. I cannot recall exactly when the issue happened, but since I have been running PN since literally the day I got my Nexus, somewhere in that time, with a lot of dirty flashing from one MM update to the next, messing with Kernels, and overall going quite a while between clean flashes until I finally did one for the move to 7.0, I lost my Speakerphone Mic and only the sound for speakerphone was coming out of the bottom speaker. After testing my Refurb replacement and now my "fixed" original 6P, sound for the speakerphone is supposed to use both Speakers when everything is working normally.
The test for this was easy to do with the Skype Test Call. Just call it and turning on Speakerphone would either work, it records my voice and plays it back, or when it wasn't working, it would just end quickly telling me it doesn't hear anything (and the audio only comes through the bottom speaker).
So TL/DR and plainly, my recommendation if you haven't already done so, and you are having similar interesting and semi baffling issues such as these, try flashing the oldest Image available for our 6P as I did (Directly from google, I just did the Flash-all.bat file as it was included with the minimal ADP terminal on Windows 8.1) and let it do its thing. Once I was in the original MM build, I just skipped my way to my homescreen, downloaded Skype from apkmirror, and logged into that to do the test. Boom! After the test was a success, I downloaded the 7.1.1 image, flash-all.bad'ed that and did the same skip to test.... And Boom! Speakerphone Continues to work normally.
Now to test the battery side by side with both devices to see how bad my old one has degraded if it indeed has done so... or if 7.1.1 has indeed fixed that as well.
Like the title says, hotword detection used to work great, but in recent months seems to have gotten broken. I'd say it only works 30-40% of the time, where it used to be 90-95%. Even when it does detect the hotword, it will frequently fail to do anything. It will make the sound acknowledging that it is listening, but nothing will come up on the screen.
I've attempted to retrain/delete the voice model, tried reflashing the stock image. I'm trying to determine if it's something specific to my phone, or if this is a wider issue with the current build of Android. Based on how it fails to do anything, I'm suspecting this is a software issue rather than a hardware issue.
I'm down for any suggestions. This is a feature I use a ton, and would love to get it working again.
On a side note, I used to be able to long press the phone button on my wired headphones to activate the okay Google feature, but around the same time this stopped working, I lost the ability to do that. Anyone know why?
Hello, kinda new here...at least I haven't posted since my Xperia Play. However I own an Xperia XZ2 (H8276) Android 9, 64GB. I'm having two issues, one if which is one that seems to plaque Sony phones.
1). The Microphone for Xperia Diagnostics / Testing doesn't work during the test. Which it used to. However the microphone during calls via loudspeaker work. Google is touch and go. However, the in-call mic doesn't always work. Sometimes it'll work when I call. Sometimes it'll work when someone calls me. Then it doesn't. Almost seems random. I've tried uninstalling apps, app permissions, restore, app updates, etc etc. And it's a pain. I've even tried stupid things like disable Goggle Assistant, turn Bluetooth off prior, etc etc. IDK if it matters but I do have my Sony SmartWatch 2 paired to it (I assume at all times), and also a PC, PS3 Earpiece, X 2 speakers, ontop of the watch. However they're not always connected.
2). I cannot get the Sony Messaging (Xperia) base app to install now. It won't show up on Google play, and some APKs (whether upgraded or downgraded version) will either just say "not installed" or will keep crashing. It'll even give the "Not Responding" Window however it's only up for 1/100 a second. Not fast enough to select "App Info" or "Close App". Tho one time It did allow it and did nothing but continously crashing.
3). I also cannot find how to backup my device either via Xperia Companion (PC/Mobile). You used to be able to hook it up, select restore and it'll save a (X) GB .dll file. However upon clicking on the link it says something like "Android 10 users click here as there's a new method". Even tho I don't have an Android 10, it's Android 9, and the link take you to their site, and only has 5 phones listed (Xperia 1, and all the newest ones thereafter).
IDK whether this was the right place to ask however I don't know where else to ask as no one seems to know not even Sony themselves. Not to mention from my personal experience this forum site seems to have the most intelligent in-depth knowledgeable ppl around. So hopefully someone can help especially with the mic thing. I don't wanna have to use an Earpiece or Headphones to make private calls... It's a pain.