yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Questions & Answers] xdataibai:
I will try that. Previously I tried adb reboot disemmswp, and also from twrp terminal reboot disemmcwp, they didn't work.
[ZTE Axon 7 Questions & Answers] xdataibai:
Tried that, ifont works Now.but /system/etc/hosts does not work, I can change it , after reboot, it is reverted back.
[Google Pixel 2 XL Questions & Answers] BFSilva:
Hi,

Since one of the last youtube app updates I'm unable to use zoom-to-fill pinch gesture in youtube videos!

The only temporary fix I found is to clear data from the app. After that it will work as long as the app stays open in memory. After it closes the issue returns with no way to pinch to zoom in videos!

Does anyone have the same issue? Does anyone know a fix?

Thanks
[Google Pixel 2 XL Questions & Answers] sn0warmy:
Working fine for me on the latest version of Youtube. No issues.
[Google Pixel 2 XL Questions & Answers] BFSilva:
I've managed a fix!

1. Deactivate Youtube app.

2. Downgrade to version 12.49.55 (from apk mirror for exemple)

3. Launch youtube and test pinch to zoom, it should be working fine

4. Update youtube app to the latest version through the play store

That's it. It works just fine now!
[Android Q&A, Help & Troubleshooting] Esgariot:
Hi everyone,

I'd like to build Resurrection Remix ROM for unsupported device (unofficial build). So I followed some tutorials, synced some repos and got stuck on this part:

when building for treltexx it says

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/treltexx/lineage.mk]]: "device/samsung/trelte-common/device-common.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/treltexx/lineage.mk]]: "device/samsung/trelte-common/device-common.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/treltexx/lineage.mk]]: "device/samsung/trelte-common/device-common.mk" does not exist. Stop.
Device treltexx not found. Attempting to retrieve device repository from lineageos Github (http://github.com/LineageOS).
Found repository: android_device_samsung_treltexx
Default revision: cm-14.1
Checking branch info
Default revision cm-14.1 not found in android_device_samsung_treltexx. Bailing.
Branches found:
cm-12.1
cm-13.0-precommon
cm-13.0
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/treltexx/lineage.mk]]: "device/samsung/trelte-common/device-common.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/samsung/treltexx/lineage.mk]]: "device/samsung/trelte-common/device-common.mk" does not exist. Stop.

** Don't have a product spec for: 'lineage_treltexx'
** Do you have the right repo manifest?

despite my local_manifest.xml looking like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="githubRemote" fetch="https://github.com/" />
<project name="bonuzzz/android_device_samsung_treltexx" path="device/samsung/treltexx" remote="githubRemote" revision="cm-14.1" />
</manifest>

but this setting is not being picked up. So I tried to remove existing android_device_samsung_treltexx reference by adding

<remove-project name="LineageOS/android_device_samsung_treltexx"/>

but it results in error saying that there is no entry for "LineageOS/android_device_samsung_treltexx", which is true, because it's not present in default manifest.xml

I get that it tries to look for branch cm-14.1 in LineageOS/android_device_samsung_treltexx repo and that branch does not exist.

So my question is how to tell breakfast to look for cm-14.1 branch of device in other project entry - one from my roomservice.xml/local_manifest.xml?

Or how to delete reference to LineageOS/android_device_samsung_treltexx?

EDIT

Looks like there are other problems with missing references in my build method, will need to fix them before coming back to this.
[Nexus 6P General] yodabug:
I'm not sure if this is even allowed here but, I can't use the phone for phone calls AND 1 other "over the air service" such as GPS or WIFI hotspot or even wifi - if I do the calls get broken up with the poor audio routing of the blue tooth adapter--it's almost like the phone doesn't have enough resources to run cell phone call AND GPS or cell phone call AND blue tooth music or cell phone call AND wifi/hotspot service....any eon one service used at one time works flawlessly but with a cell phone you want to use ALL the wireless services at once and have them work.

AND, the phone shuts itself off when it's in my pocket and charge to 95-100%?? I miss phone calls from work all the time, I am constantly checking the phone to make sure it is still turn on. What a pain the behind.

I call Google - so sorry it's Huawei's problem, I call Huawei - so sorry its Googles problem. In the meantime I bought this phone from google and it worked well for 1.5(purchased 06-16-2016) years (besides the shutdown issue) then poof gone - it is now a piece of crap - 3 months outside of the one year warranty and I need a new phone!

So, my question to these two companies ( and I know they have lurkers in these forums all the time - that's why I am posting this here after speaking with BOTH of them) is: How in all honesty can you expect me and every single person I talk to about this to ever purchase another phone from either one of you?

Because I do talk, to everyone who will listen, about this; I see a LOT of people everyday, different jobs sites all over eastern Ontario. I tell them that as a technician for the past 30 years and knowing how technology works and also knowing that BOTH of these companies are probably to blame each in their own way and that NEITHER of these companies are thinking about their customers on this issue and only about their own bottom line I couldn't possibly recommend either one of them for anything.

Without exception these people I meet ask me which brand they think I SHOULD buy. I tell them this: "If you want a phone that just works and you aren't a customizer get an iPhone. If you are a customizer get a Razer Phone, an LG if you want cheap or a Samsung, Samsung being my preferred choice - but whatever you do, DO NOT buy a google phone or any phone made by Huawei because BOTH of these companies have proven to not be trust worthy, over this debacle, to their customers and if this is the case now then why would you think any future incidents of this nature would be any different?

Good bye to Google and Huawei, hello to Samsung again.

Thanks for letting me rant/rage here.
[Nexus 6P General] aserate:
I have to say, I'm also disappointed on my nexus 6p. One day it just went nuts, shutdown itself and then bam! bootloop occurred and from that day on I can't install roms including stock, yes including stock, without applying a 4-core mod (forces my device to use only 4-cores to work and boot). Some say it's a hardware failure or something, idk. And even before that i have been having issues with my battery, i only get 4h sot average. I cant believe i spent so much for this crap. Dont get me wrong though, i love this camera very much and the stock google experience (and custom roms) but everything else is sh*t. So yeah, +1 for this "dissatisfaction"
[Nexus 6P General] undeadking:
Well I have no idea what carrier you use but if I was you I'd "accidentally drop" or "lose" my phone and file an insurance claim- I know Verizon told me if I end up breaking or losing my 6p they would either give me a Pixel 2 or 2XL so maybe that's something to look into?
[Nexus 6P General] 400ixl:
Personal experience is the complete opposite. Phone was nearly 2 years old (1 year warranty in the UK) and started shutting down. Online chat with Google and confirmed I had done the basic fault fixes like factory reset and they immediately send out a refurb to replace it.

They had no legal requirement to do so but also did this for a lot of people who bought their phone through the play store. Its more complex if it was bought through a carrier as the warranty / contract is then with the carrier or Huawei and those experiences appear to be less straight forward.

Everyone has different experiences, I wouldn't touch Samsung with a barge pole due to personal problems I had with them and the number of faults our organisation has with their phones. Had an LG phone that had the reboot issue and they wouldn't do anything as it was outside of the 12 month warranty.

Warranties have an end date that you sign up to, they may give a goodwill gesture outside of this, or you can fight them to say the fault was inherent.

What have you done to diagnose the issue on your phone?

It could be as simple as the battery needs replacing. It can have all sorts of symptoms including shutting down or failing services when there is high demand and a power spike which the dying battery can't provide. Have you run something like Accubattery to check the battery state?
[Nexus 6P General] tharweb:
I'm in the UK. I bought mine from Playstore but the warranty card states the handset had a 2 year warranty?

I agree with you on LG though. I bought two LG G4's. One had the well documented bootloop within warranty and they repaired it. The second started to bootloop two weeks out of warranty...LG didn't want to know.
[Nexus 6P General] PratikP:
Had the same issue. The phone was practically useless for calls due to its secondary mic issue. The battery aged really well for me, though

When I contacted Google - they were pretty responsive. I really appreciate Google for this. After a year they had no obligation to even entertain me. But that's about it - they gave me standard replies like factory reset - to which I laughed. Rooting and disabling the secondary mic would have probably solved the issue but then the payment options would'nt have worked for me. Google had acknowledged the mic and the battery issue in North America but here in India they went the factory reset route. I shared the bug id as well. Nothing helped. They asked me to visit the Huawei service center. They changed mic - issue still persisted - asked me to contact Google.

I eventually got myself a Samsung N8. Had been with Google for 3 generations. The Pixel 2 XL couldn't convince me this time. Customer lost.
[Moto G 2015 Android Development] Subinsmani:
CHANGELOG

28/03/2018

Source Updated

21/03/2018

Merge all-new OSS commit from Alberto

Initial Release

Remaining bug

Camcorder

Selinux status permissive
[Moto G 2015 Android Development] Subinsmani:
Screenshots

Reserved
[Moto G 2015 Android Development] Subinsmani:
Reserved
[Moto G 2015 Android Development] web_charles:
4G does not work
[Moto G 2015 Android Development] Subinsmani:
Are u asking or report the bug..

For me 4G is working without any issue..
[Moto G 2015 Android Development] web_charles:
Asking. Because I saw it in the pictures, so I thought it was not working.
[Moto G 2015 Android Development] Subinsmani:
Nah nah.. Thats old pic.....

Rom bug us posted on changelog section...
[Moto G 2015 Android Development] rahul9999:
Nice work.

I think Camcorder is working partially in Footage & modded Gcam, so please mention that

Here is a link of modded Gcam - https://drive.google.com/file/d/1TfgC1EGUZvqtlMwZqsJSfpMmzgNdxNei/view

Note : - Only 720p video recording is working, so as after you installed change video recording quality to 720p to avoid any FC
[Moto G 2015 Android Development] teensheet:
Does LTE works ? Because the community said that It worked in the pixelexperience ROM but it didn't work for me so I just want to confirm. Thanks
[Moto G 2015 Android Development] rahul9999:
Working
[Moto G 2015 Android Development] kvijaya:
Guys atleast give the dev *thanks* if not donation stuffs...which courage/makes mood to dev for maintaining rom and keep alive our osprey for some time?...#rip eng
[Moto G 2015 Android Development] web_charles:
for me it also did not work, was it something we did wrong?
[Moto G 2015 Android Development] usuario1515:
Man, try check the APN, in some ROMs doesn't find automatically depending on your SIM Card. in pixel experience for example I need to put APN manually every Time I do a Clean Flash. I don't know if this issue is happening only in my device.
[Moto G 2015 Android Development] web_charles:
It worked, all right!

Thank you very much.
[Moto G 2015 Android Development] ralpzN:
flashing the gapps gives me bootloop and reboot to the twrp
[Moto G 2015 Android Development] Rizz11:
Is there a way to turn off data activity?
[Moto G 2015 Android Development] sudeeptodutta:
First of all, a big thank you to the developers who've invested their valuable time for keeping osprey devices exciting to use. I've some questions to ask. Apologies if certain questions were not supposed to be asked.

- How is the ROM general? Is it stable enough for daily driver usage? How is the battery life ?

- Are there any known issues that any one of the users experienced so far?

- Will this ROM receive OTA updates? Does unofficial / offical stages affect the usage of the ROM?

Thank you
[Moto G 2015 Android Development] iamiliyax:
Couldn't open the above given rom link...plz update the link
[Moto G 2015 Android Development] Oscarworld343:
dude

i can´t install magisik
[Moto G 2015 Android Development] Subinsmani:
Rom source has issue... So many bug will u got... So Happy with the bug..
[Moto G 2015 Android Development] mr.robot1996:
[

link dropped please go back up
[Moto G 2015 Android Development] mudayaa:
No link available
[Moto G 2015 Android Development] Subinsmani:
New build is up. so happy flashing...
[Moto G 2015 Android Development] web_charles:
I'm from Brazil, I love your rom. Thank you!
[Moto G 2015 Android Development] teensheet:
I am experiencing frequent back to back restarts on its own and I can not seem to stop it.
[Moto G 2015 Android Development] Subinsmani:
Please if u provide me a log then it will very helpfull
[Moto G 2015 Android Development] teensheet:
First : these restarts occur randomly so I cannot pinpoint exactly when it will happen again. But a trend I noticed was that this occurred only when my battery percentage dropped below 20 and multi tasking.

Second : I do not know how to take logs, sorry xP. But If you can guide me on how to. I will try my best to get the logs of time when this happens.

Thank you for your hard work dev. Cheers!
[Moto G 2015 Android Development] Ashok1111:
[MENTION=7868666]Subinsmani[/MENTION].... Can you build DoT os for merlin too?... It will be great if its possible....;)
[Moto G 2015 Android Development] UnJosesinacento:
muchas gracias amigo, me estoy descargando la rom para probar, espero todo salga bien.
[Moto G 2015 Android Development] Subinsmani:
First u plug ur phone to pc.. and open adb the simply write adb logcat..

Remember u have to do this during bootloop...

If u want record the log logcat > bootloop.txt

Then post it here...
[Moto G 2015 Android Development] teensheet:
Okay so just to be clear, when my phone starts 'bootlooping', I connect it to my pc and use the adb commands. How do I stop 'taking' the logcat?

UPDATE : This bootlooping occurred yesterday night when i was using Youtube for 1+ hour.
[Moto G 2015 Android Development] Subinsmani:
To stop logcat ctrl + c..
[Moto G 2015 Android Development] web_charles:
I've been using ROM for a few days, and they sometimes reboot from nowhere, is this normal?
[Moto G 2015 Android Development] teensheet:
Hey, sorry couldn't get back at you with the logs as I am currently out of station. But the frequency of the restarts has somehow reduced quite significantly for me.
[Moto G 2015 Android Development] iamiliyax:
Link not found error is shown
[Moto G 2015 Android Development] rahul9999:
https://drive.google.com/file/d/1TfgC1EGUZvqtlMwZqsJSfpMmzgNdxNei/view
[Moto G 2015 Android Development] amalpeter:
Is it only for g3

Is it only for moto g3 or it work for others
[Moto G 2015 Android Development] stonny20:
Which phone are you using? This ROM is for Moto g 2015, Osprey model.
[Moto G 2015 Android Development] amalpeter:
I have two phones to be tested

one is honor 4x and other is micromax q414 .

But in the honor 4x I couldn't unlock the boot loader it will not be unlocked because the unlocking page has been deleted. So could you help me with the q414
[Moto G 2015 Android Development] stonny20:
You can find your respective phone forum and request help there, if there is support for your phone. And add a new thread in respective Q&A section about your problem.
[Moto G 2015 Android Development] amalpeter:
There is a thread

There is a thread on these both phones but they are not active
[Mogul, XV6800 ROM Development] madman34:
Greetings all,

Well here it is as promised, the fix for the dreaded audio adapter not working after upgradeio flash was of ROM. First of all, I upgraded my ROM and radio to DCD's newest 3.0.0 and radio, which fixed my SelectRadio issue where it dropped out, and looked at the RNC and discovered that it was as I suspected a timer value in the radio ROM was tweaked wrong causing the BER to run away and make the PPP session reinitialize very quickly or go dormant all together, but new radio fixed it. Still we had the audio adapter broken after upgrade issue, so here it is and how to fix it:

First, there is no 'electronics that you have to have' in the adapter as advertised. The problem was that a pin is wired differently in the ones that exibit the problem. The fix is as simple as clipping a wire ! Yep, thats right. Ok, with the connector of the adapter pointed at you, the curved part down, you will notice there are 6 pins on the lower edge. Numbered 1 thru 6 from left to right, pin 1 is unused, 2 is the tip of the 3.5mm jack, 3is unused, 4 & 5 are audio ground (sleve), 6 is the ring on the connector. On the stock adapter and the pigtail sound only adapters that do work properly this is how it is. The ones that mess up are a little different in that pin 1 is shorted to 4 & 5 which did not make a difference before, but really seems to upset any ROM based on 6.1. All you have to do is GENTLY cut the adapter and clip the wire going to pin 1 and all is good, no loss of any functio, it even still powers/charges as this is done by pins 1 & 5 on the top row. A tiny odity is that on some adapters the tip and ring are reversed resulting in left and right channels being reversed, but you can fix or ignore that at your leisure. ENJOY !!!!!!!!!!!!

P.S. Maybe a mod would make this easy to find or sticky it ??? I bet many people are wrestling with this easy to fix issue, I know it bugged the stew out of me til I just sat down and figured it out. Thanks for looking at my rant and being patient as I took a long time to follow thru with my promise.
[Mogul, XV6800 ROM Development] MIK1200:
I've read what you posted in both of the adapter threads, and just want to confirm. I have the adapter shown in this link:

http://www.semsons.com/2miusband3st.html

Your fix works on this adapter? I wonder if there is a way to just remove pin 1 from the adapter without having to cut it open. How did you reseal the molded plastic (I assume some sort of glue). Thanks!
[Mogul, XV6800 ROM Development] madman34:
Thats the one

Thats the one I am talking about and i was thinking you might just be able to pull the pin but i was worried about damaging the connector.
[Mogul, XV6800 ROM Development] fachex:
Confirm

This fix works also with the HTC adapter that comes with the device.

Don't cut open the adapter, try to cut the pin 1 from outside in.

Thanks!
[Mogul, XV6800 ROM Development] Otter:
Pretty ghetto fix....

But I'll have to try it later, because rigging up 2 adapter and having to plug them in, in a certain order is really sucking.
[Mogul, XV6800 ROM Development] rschell:
Maybe this could be a Wiki topic :)
[Mogul, XV6800 ROM Development] mshnayde:
I can't believe this

First of all thank you for saving everyone on this forum money, because now we don't have to buy adapters to try and figure this out.

I spent months without being able to use the adapter and finally broke down and downgraded to the original 2.17 ROM.

Now, I can finally use the adapter again and can't believe that it was so simple all along.

I can't thank you enough.

This modification of the adapter works - I just confirmed it.

:p

Michael
[Mogul, XV6800 ROM Development] scheel78:
this is great. I now have garmin mobile gps, all my bluetooth devices working, and at last music through my headphones. life is good.
[Mogul, XV6800 ROM Development] cochran242:
This will be great if I can get it to work. How are you guys removing pin-1? Are you opening the adapter or are you removing from the connector? If your removing from the connector, what are you using?
[Mogul, XV6800 ROM Development] vincemash:
I took an exacto knife and bent pin 1 up and tried to bend it to get it to break to no avail, so I just bent it up as much as possible and pushed it into the connector hoping it would not short out any other wires, got lucky cause it works now, thanks for the tutorial
[Mogul, XV6800 ROM Development] blue6800user:
OMG!

:eek:THANK YOU SO MUCH!:eek: I just figured it was worth trying this before buying a new one. I used a thread ripper to move pin one around till it was not aligned correctly then i just plugged it into my phone hoping it would break the pin. But it didnt, it bent it way far into the adapter. I thought i was screwed ... but i plugged it in and it works now! THANKS AGAIN!

you are the awesome!:D
[Mogul, XV6800 ROM Development] sputnik:
pics?

Can anyone post pics of their "modded" adapter? I'm not new to soldering, but I am new to cutting open a molded rubber piece like this...
[Mogul, XV6800 ROM Development] x10dude:
Ditto. Can someone post a diagram or picture so we know exactly which one is pin 1.
[Mogul, XV6800 ROM Development] drew826:
This is based off reading madman34's post. I *THINK* this is what you should see when you look at the jack on the PPC6800 and the connector on the audio adapter. Can anyone verify this?

PPC6800
_______________
| |
| 4 3 2 1 |
| 6 5 4 3 2 1 |
|______________/

USB/Audio Adapter
_______________
| |
| 1 2 3 4 |=====|===== to USB*: 1) +5V DC, 2) Data-, 3) Data+, 4) Ground
| 1 2 3 4 5 6 |=====|===== to Headphone**: 1) Unused***, 2) Tip (Left Channel****),
\______________| 3) Unused, 4) & 5) Sleeve (GND),
6) Ring (Right Channel****)

* [URL="http://pinouts.ws/usb-pinout.html"]http://pinouts.ws/usb-pinout.html[/URL] (the 4th physical pin is unused,
and therefore not labeled in these diagrams)
** Based entirely off madman34's research. I have not verified any of this.
*** On non-working adapters, this pin is shorted to 4 & 5. If your adapter does not work,
disconnect the wire leading to the pin or bend the pin back so that it does not make
contact in the jack.
**** Left & Right Channels might be swapped on some adapters.
[Mogul, XV6800 ROM Development] madman34:
Thanks for running with this

The diagram is spot on and I think pin 3 might be the microphone line, but have not tested this yet.
[Mogul, XV6800 ROM Development] drew826:
If that's the case, then I'd assume that pin 1 would be microphone ground. Are there any audio adapters that also provide microphone input? If so, maybe we should warn people not to cut pin 1 if they plan on using the microphone.

Or maybe it's possible that all of the non-working adapters were built to include microphone support, which for some reason isn't working.
[Mogul, XV6800 ROM Development] Otter:
It works!

Thanks!

I didn't get the pin to come out...But I guess it's bent back somewhere...

I used a sewing needle and then used that other adapter that came with the phone to crush it.
[Mogul, XV6800 ROM Development] jrebeiro:
Are you people screwing with the port on your phone or the connector on the adapter? I personally would NEVER mess with my phone to get some adapter working.
[Mogul, XV6800 ROM Development] vincemash:
we are only talking about messing with the adapter's, not the phone......my adapter cost only $4 so I didn't have much at risk here
[Mogul, XV6800 ROM Development] madman34:
You DID NOT do that did you?

Otter, the way you put that it sounds like you did mess with the pin on the phone. Please say that we read this wrong as I meant only to alter the cheap adapter and never the phone.