Nougat 7.1.1 on Moto x 2013 - Moto X Q&A

A simple question for everybody interested in this old, but still special phone. It looks like Nougat 7.1.1 can't boot on Ghost: why is it so difficult? It boots on almost every phone, so what's the problem? Technical impossibility due to the peculiarity of the hardware, or lack of developers? Maybe this isn't such an interesting question, but here it is...

Lack of developers, I must say, but that's not the right place to ask this.

I immagined... but tell me, please, where's the right place? I really don't know. . Anyhow, it isn't so important... All the best
Ok, I've seen!

stefanowall said:
I immagined... but tell me, please, where's the right place? I really don't know. . Anyhow, it isn't so important... All the best
Ok, I've seen!
Click to expand...
Click to collapse
Why do you need 7.1.1? There are well working 7.0 builds. There is no difference between 7.0 and 7.1, it's just patches/bug fixes for the Nexus/Pixel line.

liveroy said:
Why do you need 7.1.1? There are well working 7.0 builds. There is no difference between 7.0 and 7.1, it's just patches/bug fixes for the Nexus/Pixel line.
Click to expand...
Click to collapse
Well, I don't "need" 7.1 Nougat, I simply thought that it could resolve the issues present in 7.0 builds... I've tried them all and they aren't well working, absolutely! Can you suggest one, personally tried by you, maybe?

XPE is working more or less. Infact almost no device has completely working CM14.1. So should suffice even if you don't like em. I know they got problems with mic on 3rd party apps and the camera is a bit tricky to get it working, but that's what you signed up for, by going custom, ya know?

liveroy said:
XPE is working more or less. Infact almost no device has completely working CM14.1. So should suffice even if you don't like em. I know they got problems with mic on 3rd party apps and the camera is a bit tricky to get it working, but that's what you signed up for, by going custom, ya know?
Click to expand...
Click to collapse
I already tried it, camera works sometimes and microphone doesn't at all... for these reasons, I'm waiting for a working romcalmly waiting...

same here bro.
Last somewhat stable xpe built is 1011. Using Footej Camera and Easy Flashlight as third party app and opengapps 7.0 pico and GooglePixelExperience-flashable-V2 as complementary flashing. But unable to use Mic in VoIP calls.

mochi579 said:
same here bro.
Last somewhat stable xpe built is 1011. Using Footej Camera and Easy Flashlight as third party app and opengapps 7.0 pico and GooglePixelExperience-flashable-V2 as complementary flashing. But unable to use Mic in VoIP calls.
Click to expand...
Click to collapse
Good to know ...even if this solution can't satisfy me any more. My heart is bleeding (so to speak :laugh when I realize that almost all versions of Moto G, and even Moto E, have their magnificent Nougat on board, when poor, noble Moto X lays in despair...?

Related

Android Auto doesnt work!

So I guess im super lucky and finally got Android Auto in my Sonata 2015 but it doesnt work with The Verizon Lg G3.... Its one of three phones that it doesnt work for supposedly... Im wondering if there is some kind of workaround? There has to be!? Ive tried multiple roms and options but cant seem to figure out how to get it to work for my device! If anyone can help me out that would be amazing! :laugh:
Badouken said:
Verizon Lg G3.... Its one of three phones that it doesnt work for supposedly...
Click to expand...
Click to collapse
Just FYI, it would be "1 of 3 of the MOST POPULAR new phones" running stock Lollipop+ that Google has tested.
I'm sure there is a huge list of less popular phones that aren't working, but Google has only done positive/negative testing on the most popular. Fragmentation is a problem for Google too.
Maybe that will make you feel slightly less bad.
Sorry I don't have an answer for your actual question.
mikereidis said:
Just FYI, it would be "1 of 3 of the MOST POPULAR new phones" running stock Lollipop+ that Google has tested.
I'm sure there is a huge list of less popular phones that aren't working, but Google has only done positive/negative testing on the most popular. Fragmentation is a problem for Google too.
Maybe that will make you feel slightly less bad.
Sorry I don't have an answer for your actual question.
Click to expand...
Click to collapse
yeah that's true but as far as Im aware if it has lollipop it should work regardless and if someone doesn't have lollipop I doubt they would have android auto. Its just annoying because every other variant of this phone works with android auto and it seems like something someone on XDA could fix before Verizon gives out an update... which would be months from now if that! Guess I just have to wait or buy a new phone which im too cheap to do!
Or flash cyanogen 12? (Not 12.1) the last 12 official build works fine.
Badouken said:
So I guess im super lucky and finally got Android Auto in my Sonata 2015 but it doesnt work with The Verizon Lg G3.... Its one of three phones that it doesnt work for supposedly... Im wondering if there is some kind of workaround? There has to be!? Ive tried multiple roms and options but cant seem to figure out how to get it to work for my device! If anyone can help me out that would be amazing! [emoji23]
Click to expand...
Click to collapse
This is why I'm not on Verizon, and why I don't buy phones with heavily OEM modified Android. You risk it not working with the latest and greatest that Google puts out.
I have always stuck with Nexus (or recently) Motorola devices. As much as I liked the G3 (and the G4 even more), I want to play with all things Android, so better to stay with vanilla Android as much as possible.
Solutions Etcetera said:
This is why I'm not on Verizon, and why I don't buy phones with heavily OEM modified Android. You risk it not working with the latest and greatest that Google puts out.
I have always stuck with Nexus (or recently) Motorola devices. As much as I liked the G3 (and the G4 even more), I want to play with all things Android, so better to stay with vanilla Android as much as possible.
Click to expand...
Click to collapse
I always try and make my phones as vanilla android as possible. But I think Im just gonna buy a Nexus 6 and stick my sim into it for now and then sell my G3 on swappa. Ive never owned a Nexus phone before because I never had spare money but I have a new job (salary based finally!) So I think im gonna just treat myself, ive always wanted a Nexus phone as well!.
Happy Nexus Sixing!

Will Moto G2 get Android N?

HI everyone,
Is there any definite information available regarding whether the Moto G2 would get the Android N? Thanks for sharing any information about this.
I pray for stock 6.0.1 and security update
support lenovo says that the last tests but when asked which country he could not say
lying, but I hope I'm wrong
forget about stock N..
only custom..
I'll wait a few more weeks as nothing appears I install custom 5.1.1 or RR 5.7.3 based on M.
but on all 6 rom touch issuse is there from what I read
Android N will not be coming to our beloved Moto G2. It will come by CM or other custom rom.
I very doubt it. Titan didn't even got stock 6.0.1 yet. Perhaps CM could bring it, who knows.
Thanks for the replies everyone. Really appreciate it!
Oh well, I am kinda used to the Moto G2 as my second phone. It was quite cheap and is still quite fast and problem-free. So, I was curious (and hopeful) about whether there was any chance of it getting the upcoming Android.
Thanks again! :good:
I am waiting for android N ...lets hope we get it soon
Well, if Lenovo fixed the touch issues, it would make things easier. Anyways, one of CM13's devs for Titan said that it would be hard because stuff changed the camera and without proper source code, it would be hard to make it work. One can only hope.
I just had a chat with Motorola Customer Support. They said that they do not have any information right now as to which all phones will get Android N and by when would they get it.
No stock naugat.
I'm a moto g 2014 owner and i got the official 6.0 patch on my device, though i was a part of a soak test but i'm pretty sure it was released right after the soak ended back in February. chances of Android N on moto g 2nd gen are slim but it could happen.
any chance of custom n rom
josfr4ncisco said:
Well, if Lenovo fixed the touch issues, it would make things easier. Anyways, one of CM13's devs for Titan said that it would be hard because stuff changed the camera and without proper source code, it would be hard to make it work. One can only hope.
Click to expand...
Click to collapse
Why? The custom ROM's currently available are awesome and provide all that I need for now. If getting the latest version of Android becomes that important to me then I will upgrade my phone to one that supports it. But that's me.
pastorbob62 said:
Why? The custom ROM's currently available are awesome and provide all that I need for now. If getting the latest version of Android becomes that important to me then I will upgrade my phone to one that supports it. But that's me.
Click to expand...
Click to collapse
Seems like you don't experience the touch issues which are plaguing the MM ROMs for this device then. And I agree, I don't see a hurry for Nougat for me right now, Marshmallow would be good enough. And I would prefer to see this phone die on MM with a fixed touch drivers (pls Lenovo), rather than going to NG with lots of things broken, according to the devs.
josfr4ncisco said:
Seems like you don't experience the touch issues which are plaguing the MM ROMs for this device then. And I agree, I don't see a hurry for Nougat for me right now, Marshmallow would be good enough. And I would prefer to see this phone die on MM with a fixed touch drivers (pls Lenovo), rather than going to NG with lots of things broken, according to the devs.
Click to expand...
Click to collapse
No I don't have any touch issues. But my post may have been prophetic. Yesterday, my mobile data stopped working for no apparent reason. All of the usual suspects are properly set and on still, so it is definitely a hardware issue. I have no data unless I am connected through a WIFI AP. Really sucks since I cannot access the WIFI at my job with personal devices. And the company laptop is so restricted I can't really get any personal business done on my break times.
Bottom line - I ordered a Moto G 4th gen yesterday evening. Hopefully it will serve me as well as did the 2nd gen. I really gave it a thorough run for the two years I had it. We'll see how it compares.
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
EduardoClasheiro said:
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
Click to expand...
Click to collapse
For all of the hype I see about xposed, I have never had a pressing desire to install it. At least not where my needs lie.
EduardoClasheiro said:
Touch issues happen only if you have glass protecting screen on some ROMs but if you have i recommend cm13 and if you need more personalization put xposed and thats all
Click to expand...
Click to collapse
I don't use a glass screen protector :v
pastorbob62 said:
For all of the hype I see about xposed, I have never had a pressing desire to install it. At least not where my needs lie.
Click to expand...
Click to collapse
Xposed is about more personalization if you dont like or dont care about personalization it will be useless, personaly i dont use it ????
josfr4ncisco said:
I don't use a glass screen protector :v
Click to expand...
Click to collapse
I have issues here and think it is the problem ???? good to know dont is this, by the way cm 13 fixed my problemas ????
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
clive48 said:
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
Click to expand...
Click to collapse
moto g2 xt1068 is not a 4g device. but you can use reliance jio via their jio mifi device which is a portable wifi Hotspot device.

LineageOS on OP3T, everything works?

Hi
I'm new here. I recently got a Oneplus 3T (Midnight Black Edition). I am a huge fan of lineageOs. I was wondering if I flash los in Oneplus 3T, will everything work? I mean is there any known bug present?
Thanks for replying.
There was some bugs a year ago, but those have all been ironed out under the past year.
And the camera API problems can only be fixed by OnePlus, if only they would.
pitrus- said:
There was some bugs a year ago, but those have all been ironed out under the past year.
And the camera API problems can only be fixed by OnePlus, if only they would.
Click to expand...
Click to collapse
Sorry if this is a lame question, but the "camera API" problem as you mentioned means anything related to end user/ day-to-day camera usages? or this is more of a developer's headache? Simply asking if the camera will not work?
tushxda said:
Sorry if this is a lame question, but the "camera API" problem as you mentioned means anything related to end user/ day-to-day camera usages? or this is more of a developer's headache? Simply asking if the camera will not work?
Click to expand...
Click to collapse
Camera will work. I think stock LOS has alright camera. Sultan's camera work makes the quality match OP's camera software but it lacks features such as 1080p60 or 720p120. Not sure if you can get those features if you use 3rd party cameras or not. Paranoid Android uses a custom camera driver that they create that makes the quality really good, but I never used the ROM myself.

OnePlus 6T Android Q beta thoughts

Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
peanutpajamas said:
Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Click to expand...
Click to collapse
you can text if you send a screenshot or pic attached to it then the text goes through no matter what messaging app u use
bradhoschar said:
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
Click to expand...
Click to collapse
I thought that was just the links..
My thoughts are this sucks and op should be ashamed of themselves.they released a backport
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
superiscch said:
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
As the name suggests, this build of Android Q is best suited for developers and early adopters. As it is still in an early stage of development. That said, we do not recommend flashing this ROM if you have little to no experience in software development or flashing custom ROMs. Proceed at your own RISK!
Click to expand...
Click to collapse
superiscch said:
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
I think your right to a certain extent, but I also feel like lately OnePlus hasn't been doing what they have become known for, oneplus users want fast updates to try out the latest of Android.
this build while intended for development was made with very little thought, most other OEMs on the list actually made it useable, take essential for example, yes there are a few bugs but it can send a text and doesn't crash when you click on auto brightness. Even though it was for "devs".
OnePlus could have definitely done a better job at this, very dissatisfied.
SpasilliumNexus said:
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
Click to expand...
Click to collapse
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
fullofhell said:
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
Click to expand...
Click to collapse
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
If anyone want to see a video or a quick look than check this
https://youtu.be/Yhw6463pTPg
-snip-
PatrickLoewer said:
Has someone problems going back to custom roms?
I downgraded to the Pie Image linked in the OnePlus Android Q official post. This is working fine, i can boot and flash TWRP as well, but as soon as i install any room i go straight back to "Qualcom CrashDump Mode".
Tried the original fastboot partitions from "rom-stock-fastboot-roms-oneplus-6t" aswell, those are working fine for me as well. But soon as i flash any custom rom (tried 3 different ones) i go straight into the "Qualcom CrashDump Mode" (fastboot is no longer working after that so i have to use the MSM Tool to restore the phone).
Tried dirty flashing or a complete clean flash (wiping all partitions except Internal Storage) both result in the same Qualcom Crash screen.
Using the MSM Tool gets me a working Pie everytime, also using the original fastboot rooms works as well, it's only custom roms .... (tried with and without flashing magisk/opengapps)
Edit: International Version, no T-Mobile or McLaren Edition
Click to expand...
Click to collapse
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
fullofhell said:
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
Click to expand...
Click to collapse
Was not the problem, but the MSM Tool didn't worked with the version i had.
indian84 said:
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
Click to expand...
Click to collapse
Cute attempt at the assumption, but you're far from getting that one right. Try again.
SpasilliumNexus said:
Cute attempt at the assumption, but you're far from getting that one right. Try again.
Click to expand...
Click to collapse
Burnnnnn
fullofhell said:
--WoT--
Click to expand...
Click to collapse
No matter how buggy or broken they are, they are meant for developers to adapt software and hardware on them before final builds are out to the general public. Not for randoms to treat them as finals, as few here and a lot on the OP forums have done.
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Xpiatio said:
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Click to expand...
Click to collapse
Fairly sure you have to wipe and not choose "secure startup" (or similar) in the set up. That feature (encryption) is not working currently.
They could make a PRE-Alpha build, say DO NOT INSTALL THIS, and zillions of lDIOTS would download it because they want the latest update, no matter what, THEN, will get on here, OP's website and other places to complain about it.
It's like these clowns hanging out windows, rail cars and what not to get a selfie so they can get "likes"....lDIOTS

Whats the best choice for XZ3 right now? (April 2022)

Hello,
Without any doubt I can say that XZ Premium was my favorite phone, many mods, ports and ROMS. Changed it to OP 7Pro and Im also satisfied with XDA support but it wasnt enough so...
I bought XZ3 Dual 4/64 with A10 and 52.1.A.3.137 firmware. Read all possible topics here and Im totally confused what to do, could you help me out?
I dont really know should I unlock bootloader because I would like to have Sony Camera functions like 4K HDR etc.... but
I cant stand button navigation on stock, I would love to have gestures.
I dont need Sony audio enhancement because I mostly use V4A, what forces me to unlock BL and keep root.
I thought about SailfishOS but I need few android apps like messaging or banking app, cant live without it.
Thought about LineageOS but there are problems with crackling speaker, camera app, gcam not working, and I like sony stock apps but I dont mind using google apps instead, not a fan of lineage apps. Present magisk/hide is apprecatied.
Not a fan of A12- read that camera app is not working with a12, never flashed nor used A12.
No matter what I choose- there are downsides, so what will be the best choice?
Totally sad that XZ3 is not as supported as XZP, I would love to support XZ3 development but Im so underdeveloped that I only use whats given on xda ((
Have a great day!
Hello,
I'm at the same point as you. I'm a previous user of LineageOS on a Galaxy S7. That one had a lot of flaws but was still much, much better than anything that forces gapps on me, even though maybe the S7 version was the worst LineageOS ever. I also used it on S5 and S3. No LineageOS was perfect, but superior over all other ROMs I tried.
The thing that bothers me about the camera is: I can't find information about where the issue is after unlocking. People say it performs worse. But is it a driver thing you can't fix or is it just the Sony camera app? I get no answer here. If it's just the Sony camera app that is decapitated after unlocking, you should just get rid of this peace of crap and replace it with Open Camera. You can then switch to Camera 2 API and disable this awful edge enhancement and actually make good photos. The only downside is that Open Camera doesn't apply proper shutter time for very dark conditions automatically. 4k HDR also seems to work. But remember: I'm still on the original ROM and I don't know if anything will be different after unlocking. I would be thankful if someone could give any information about it.
You should be able to use almost any app on LineageOS. I use FDroid and Aurora as app managers. Some apps check for root or custom ROMs and refuse to work if they find it. I don't use any banking apps on Android. Maybe they do a root check. I can't tell you. You may use the web page of your bank instead. Telegram and Signal both work on LineageOS, I've never tried WhatsApp though.
What's the best option isn't an easy decision for the XZ3. There are always downsides on custom ROMs. The problem is that we can find almost no information on what exactly doesn't work as usual after unlocking, so we can't make our decision. I don't expect to find much help, if I encounter problems after unlocking.
I also spend hours and days trying to get information about all of this and didn't find what I need to know. The crackling speakers problem on LineageOS for example is new to me. Can you give me further information about it or provide a link? Have made any progress since your post here?

Categories

Resources