yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] ayyu3m:
i have kept a close look on this thread for a while. and my opinion is this thread be kept for sometime. not much has been expressed here by other members. but i see this is one of a kind thread in the elf forum. and it gives an opportunity to express concern and at the same time to show appreciation.

thankx kar200 and all others in this thread. lets work out any concerns we have over the elf forum in this single thread :D
[Touch GSM ROM Development] absorber786:
To post or not to post?

While i do agree, that the forum needs to be clean and its users repsecting the rules etc.... human nature as Noonski pointed out is laziness! so there will always be threads being opened. I think that most junior members will fall into this catergory (and this is NOT a dig at them but merely an observation :rolleyes:) but can be to a certain degree understandable/acceptable. Would you agree? If, however this is done by people who have been around for some time, then by all means close the thread and flame the user - they should know better.:)

As a thought, maybe some guidlines from the Mods here (Ameet and Noonski) re how long a 'repeated' thread will be kept open?

From a personal perspective, i have never needed to open a thread or even post that often specifically because i have always found what i needed from reading.... (which i kinda enjoy:confused::confused: silly me)
[Touch GSM ROM Development] Biffert:
I think for someone new to the scene and first coming here, it can be quite overwhelming. There is tons of information available, but where do you start? So from that perspective I can understand why someone would start a new thread. On the other hand, looking at myself when I first came here... all I did was dig through the piles of information just reading, not looking for something specific but just gathering as much info on any subject as I could.

As for the thread closing and modifying posts. The closing of threads depends on whats going on in the thread. Closing a thread on the first available answer can leave some users without a clue because the given answer wont work for them, and the cant reply on the thread to continue asking. Which can be a missed opportunity to add more useful data to the forums if someone has a different solution to the problem.

Modding the answer into the posters question can lead to some confusion if you ask me :) Only a mod has the uberpower to edit a users post, so if there is a mod nearby that had a good comment you have to look at your own posts, but you also have to look at the end of the thread to see if someone posted usefulness in case your post was not modified (hihi MODified :-P).
[Touch GSM ROM Development] Noonski:
I Am Cornelio, Need Dippy For My BungHole.

Where you been Biffert, enjoyed your vacation?

This has only happened on a specific Beta Thread ;)
[Touch GSM ROM Development] Biffert:
I know, but it was more of a big picture perspective on the matter :) Ive been reading the thread as well and saw the request for some opinions so I thought, why not :)
[Touch GSM ROM Development] Noonski:
I'm just to excited because i just ordered My Pro.

Gotta run Print and sign the contract.

But still Where you been?

Do tell or i'll fill it in myself:D
[Touch GSM ROM Development] Biffert:
Ive been finishing school and landed a job as a software engineer/consultant :) (And vacation ofcourse :P - Poland and Tsjech republic)

No Pro for me yet, still playing with my Touch (cant wait for the new Surface btw) and Kaiser :)

So its all good here ;)

Edit: Bit of topic here, sorry bout that.
[Touch GSM ROM Development] ayyu3m:
trashing threads too early create confusion!!!

EXACTLY!

even if an answer has been already given...a thread shudnt be closed so early. cos the user has to check and then give feedback on whether it has worked or not.

i respect the work of the mods...but somehow i cant fully support the idea of kabooming threads when a single answer or a re-directing link to an answer has been given. also note that, a new user tries to follow the thread he has created and which HAS the answers given mainly by other members....so when the user looks back...the help given or the helpful posts made in that thread is also missing. this creates confusion. and the end result....new threads too. at a point where closing a thread is justified is okay...but trashing a thread...wud and WILL only create confusion and misleading guidance. I hope this sentence is fully understood and looked into.

So, in my opinion, this does hinder what we are ALL here to do. To help out so called noobs!!!! This is finally what made me speak out here, cos i have witnessed a few cases, where some users has been lost into the advent of search button!

WHEW! Finally i hope i have shed some light on this debate too.

respect and peace to all members!
[Touch GSM ROM Development] Noonski:
This definitely goes for the Elf Rom Development thread now.

It's already good and cleaned.

I did notice that i do carry over the policy from a few other threads.

I'm all over the place, and at development a thread is fairly quickly moved if it does not belong there.

You should see how many reported posts come into my mailinbox.

The funny thing is that actually the hardcore cleaning stopped, just at the moment this thread got started.

So it now mostly is focused on going through old threads and going through their importance.

So for a while (and still) we have to be very straight forward.

Just look at the Diamond Forum with 845 Threads, and it's only been out for a short while. So over there there really is a now mercy policy that most mods agree on at the moment.

So the policy used there does not apply to the touch thread (not by a long shot).

A you can imagine how easily you start applying these rules.

I heard one user say "It's not a democracy here" in defense of the mods.

Truth is that it is a bit grayish on that matter, Most reported posts are submitted by users. (not the matter in ELF Forums).

So i can say that in the case of ELF forum i'll be mostly going through the very old posts and do some data compression if need be.
[Touch GSM ROM Development] Ameet:
WOW!! :D This thread is my one of the most frequently visited other than the Mod forums :)
[Touch GSM ROM Development] absorber786:
I asked this question elsewhere but maybe is more applicable here...

I refer you to the Dev and Hack section where there is a Q&A type sticky that assists in preventing unneccasary posts.

Will it work here in this forum as well? Do you think it will work here? Can I work here;)

This may assist the mods in the their objectives of keeping it clean etc...
[Touch GSM ROM Development] ayyu3m:
Aye Caramba! Hehe ;) Ameet how you doing buddy. Any new UC roms on the way? Been quite sometime i flashed my elf. Still enjoying SPC.

ps: keke, this is a good place to say HI also. correct??!! hehe
[Touch GSM ROM Development] ayyu3m:
good idea. looks like ur the man up for the job. how abt we work on a sticky like that. you compile the question and i wil compile the answers???

must not include Q&A from kokotas sticky. hehe :D

+ anyone else can join too
[Touch GSM ROM Development] absorber786:
Its not about me posting the questions.. it about users posting all questions in one place and other users giving the answers there...keeping it clean. I think where the work comes in is the admin in managing the Question linked to the answers...Just quickly looking through the unanswered questions in the dev and hack thread, it seems that there is already an exisitng thread where those questions may have been posted..

kokotas sticky is quite brilliant actually...i sometime amaze myself by actually reading the links and finding the answers without the need to create a new thread...i am guilty sometimes of piggy backing on existing threads though:o:o
[MTCD  Android Head Units Q&A] alma359:
Hello, i have a Xtrons model PBX79TRV PX5 and i recently installed the newest MCU version(MTCE_GS_V3.44) and Hal9k Mod v4 ROM. But now my bluetooth is not working correctly. I can Pair and start a call from the phonebook and also listen music with A2DP, but when i am in a call with someone I can not hear anything and they can not hear me. The microphone and audio output are not working. I tried to revert the MCU to the original version(I found 3.17.4), and I also tried all bluetooth drivers from the factory settings, but no success. :(

What can the problem be?

Here is information from my original software when i bought the device:

Model & hardware

PX5(1024x600)

Android Version

9

MCU Version

MTCE_GS_V3.17.3 Jun 21 2019 20:14:31

CPU

Octa-core Cortex-A53 @ 1.5G

Memory 3940 MB

Kernel version

4.4.167

#101 Fri Jun 28 14:37:48 CST 2019

Build number

rk3368-userdebug 9 PQ2A.190305.002.20190722.132319
[Motorola Edge + (2020) Questions & Answers] tjsamford:
Does anyone know if the Edge+ could be bought and used for non-Verizon service like TMobile?
[Motorola Edge + (2020) Questions & Answers] Koneesha:
Yes and No.

The Verizon version is locked to Verizon service for 30 days. It needs to be activated on Verizon otherwise it will never be unlocked.

The Verizon version also doesn't have band 71 which T-Mobile will be using mainly in the future. So the phone may work but it will start to be missing a critical band in a few months.
[Motorola Edge + (2020) Questions & Answers] pcmp:
I'm looking at options now and I see that the Global version has both bands 41 and 71. So, unless tmobile plays ****, the global version should work with tmobile. Mind you I'm not saying it's a good phone or anything. Just looking at options...
[Motorola Edge + (2020) Questions & Answers] SwarlosEstavez:
I have the international version and am running on T-Mobile. Band 71 works great. Absolutely love the phone.
[Motorola Edge + (2020) Questions & Answers] skritch:
I know this thread is a little old but according to the verizon website (here: https://www.verizon.com/smartphones/motorola-edge-plus/#specsHeading), the Edge plus supports band 71

"Network: 5G: mmWave band n260/n261 | 5G: sub-6GHz band n2/5/41/66/71/77/78 | 4G:LTE band 1/2/3/4/5/7/8/12/13/17/20/25/26/28/29/30/34/38/39/40/41/42/46/48/66/

71

"
[Motorola Edge + (2020) Questions & Answers] 5eroD4y:
did you ever get the Edge+ and use it on TMobile?
[Motorola Edge + (2020) Questions & Answers] nexendz:
I have the vzw edge+ on T-Mobile I wouldn't recommend it, data and everything is fine but if you rely on your phone for phone calls then it's doesn't work very well, phone has to drop from from lte down to g in order to make or receive calls and sometimes you won't get calls. If it had volte support or handled TMobile calls better it would be great. But from my experience if you mainly use data then you'll be fine but don't rely on making and receiving calls reliably.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Mutcholoko:
THIS IS AWESOME!

Seriously, you're doing gods work in this community. I'll flash it right now!

---------- Post added at 06:30 AM ---------- Previous post was at 05:37 AM ----------

OK, just flashed it and so far it is very fast! For some reason tho, the SIM card IS detected but I have "no service"... Tomorrow I'll try to remove and insert the SIM again to see if the problem solves, but I honestly don't think it will. I flashed this coming from ViperOS 6.6, and the signal was perfectly fine there. Anyways, this is a huge project and thanks again for keeping it up with the ROMs :)
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] omonra2004:
[IMG="xt1799-2"]https://yadi.sk/i/GTb-zrrxaymbsg[/IMG]

does not load after installing xt1799-2
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
Thanks :) As for the RIL, I noticed that on the first boot it says no service for a little while, I get signal shortly after the "finishing update" notification disappears. Aside from that, it works fine on my XT1794, so I can't reproduce the bug. Please flash this zip and send me a radio logcat (adb logcat -b radio). The zip will set a prop on boot (persist.vendor.radio.adb_log_on) to make libril output to the logcat. Also please start the logcat while booting because I need to know what's going on when the RIL is starting.

Sorry, but XT1799-2 is unsupported. It is like an entirely different device (montana_retcn, this ROM if for montana) and would require making a separate device tree, kernel etc. and a separate build just for it.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] omonra2004:
It is a pity that the device that you can still buy a new one is not engaged in anyone. I put the previous build LineageOS some even worked in addition to the front camera and NFC.:(
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
Nice work, I am going to test it, from our more known main Dev Jarl, I did find out this isn't treble tho

Maybe you should "Collab" in the future?
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] GivFNZ:
I'm using montana XT1792 and I can confirm that RIL is working, but I can't have mobile data access.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
Oh hey giv :)
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] GivFNZ:
Oh hey Rush :D
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
Lmfao
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
It definitely is treble, the ROM contains a vendor partition image (check the attached screenshot). It might not be fully working, we may need to tweak the VNDK or some other things in order to boot GSIs, probably move a bunch of vendor blobs around as well. And I'm pretty sure the new (well, it existed before but we didn't use it in Pie and earlier) /product partition will be an issue, since we don't have one and just put everything it's supposed to contain in /system. I have a (dumb?) idea though - use /cache, AFAIK it's only used for storing OTA packages on stock.

I forgot to test that, it is (or was) broken on my device too. I fixed it right now, so I'll try to get a new build uploaded soon.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Mutcholoko:
Do you have "no service"?

Also, I just checked and my IMEI is 0, but that was probably my fault. But it also doesn't make sense tho, I was on ViperOS 6.6 which is Android 9 and then flashed this right after. Shouldn't be considered as a downgrade.... I'll try to flash stock and then flash this again.

---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------

I have Montana too and I can't get data access too. Waiting for the build :)
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
The "no service" thing, is "normal" for now, new build later

About full custom ROMs

Make sure, that IF you dirty flash, to flash from Lineage 16

If you want to switch to this, do a [Bold]Clean Install[Bold/]

---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------

What is the theme/mod you used for that altered dark mode by the way?

---------- Post added at 02:28 PM ---------- Previous post was at 02:18 PM ----------

@Asd Monio

Currently video recording is broken on any tested app. Including the stock camera

---------- Post added at 03:06 PM ---------- Previous post was at 02:28 PM ----------

@AsDMonio

Did you ever have Google Play Problems btw?

(Some apps wouldn't display)

If so, how did you fix it?
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
New build is uploading now, should be up in an hour or so.

If the IMEI does not show up (0 is probably default) then I think the mobile data fix won't help you. What exact device model do you have (XT179x)? I had to try a few different sets of RIL blobs (libril and libqmi) to get it working on mine, so maybe yours needs a different one. Also, you can try to wipe the modemst1 and modemst2 partitions (make a backup just in case). I did that on my device somewhere along the way.

Swift Dark Substratum theme

It turns out the updated libqmi (or libril) I used to fix the RIL also broke thermal-engine, which in turn broke recording. I tested the camera when the RIL was still fully broken, so I had no idea. Will be fixed in the new build.

Nope, no Google Play problems here, and I never used that build. For this ROM, I used CodeZero's cedric device and vendor trees as base and those never had that problem.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Mutcholoko:
I have a XT1792, aka montana. I'll wait for your new build and see if it works. I'm guessing the problem ain't the rom itself, because now I flashed stock via Fastboot and my IMEI is non-existent there too... Anyways, thanks for your kindness
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
New build is up

lineage-17.1-20200813-UNOFFICIAL-montana.zip

Changelog:

* Updated netmgrd blobs
* Updated thermal-engine blobs
* ^ fixes camera

If there's no IMEI even on stock, then I'm like 90% sure there is something wrong either with the modem data in your /persist partition, or the modem cache (modemst1 and modemst2). Check that you have dhob.bin, dhob.bin.bak and shob.bin in /persist/rfs/msm/mpss. If not, then we can't do anything, but you may still be able to run the modem on whichever ROM works with the modem cache you currently have. If you do have those files, check the permissions, especially owner user and group. On my device it looks like this in adb shell:

montana:/ # ls -l /persist/rfs/msm/mpss/
total 96
drwx------ 2 vendor_rfs vendor_rfs 4096 2017-08-09 05:56 datablock
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin.bak
drwxrwx--x 2 vendor_rfs vendor_rfs 4096 1970-11-06 01:44 mot_rfs
-rw------- 1 vendor_rfs vendor_rfs 5 2020-08-13 18:31 server_check.txt
-rw------- 1 vendor_rfs vendor_rfs 43695 2017-09-01 09:38 shob.bin
montana:/ # id vendor_rfs
uid=2903(vendor_rfs) gid=2903(vendor_rfs) groups=2903(vendor_rfs), context=u:r:magisk:s0
montana:/ #

^ So if it doesn't say vendor_rfs vendor_rfs for those files you should run: chown 2903:2903 /persist/rfs/msm/mpss/{d,s}hob.bin*

If you have the files and setting permissions doesn't help on stock (Oreo, because Nougat had different user and group IDs), try wiping the modem cache in TWRP (adb shell or terminal):

# to backup to internal storage:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/data/media/0/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/data/media/0/modemst2.img
# to backup to external microSD:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2.img
# to wipe:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
deleted

Reason:

Turns out my carrier is an asshole and locked me out for not having filled up using a 5$ card :|
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
[MENTION=9876543]Some random[/MENTION] Actually, you're right, mobile data is broken for me as well again. It must be this thermal-engine messing with the new netmgrd (once again, I tested mobile data before fixing the camera with the broken thermal-engine). I've updated the posts, I'm going to find a version that works and update again soon.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] Rush:
Wait, but it works for my friend (Giv)

Tf

Wait do you have XT1794 too? (RetEU, Europe Model)
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] GivFNZ:
Camera crashes when I set to video mode. I didn't have problems with RIL anymore.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] JarlPenguin:
You actually don't need a separate /product partition, it infact causes more problems in GSIs than it solves
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
I have the exact same one, however I am running a slightly "exotic" firmware configuration - modem and fsg from the latest stock Oreo (MONTANA_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC) and the rest is from Nougat, either factory or whatever was the most recent when I bought it. I'll try to find blobs that work for me and everyone else, if I can't I'll try flashing the full firmware.

This is very strange, it's the exact opposite for me - the camera is fixed, I can record using the stock Lineage camera app but mobile data is not working at all (it did work before fixing the camera). Are you sure it doesn't work after you reopen the app? I've had a one-time crash every reboot on Pie using the Moto camera app.

That's nice, thanks for the info. What should we do with the blobs in product then? Move them to vendor?
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] JarlPenguin:
The actual proper place for them to reside is indeed /system/product, so they should stay there :)
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] AsD Monio:
I reverted to the same netmgr blobs as used on the Moto G5 and mobile data is working again for me, camera and recording as well. Another build incoming today / tomorrow.

But then if we flash a GSI it's going to completely replace the system image, so all of our blobs will be gone. There's stuff like, for example, qti-telephony-common in there and I'm pretty sure the RIL won't work properly without that. We can put stuff into /vendor and it's going to persist even if we erase the system image, the same would be true for a dedicated product partition, if we had one. So I think our options are:

move the blobs to vendor and make them work

re-purpose another partition as a product one and deal with the issues

or I guess we could create add-on packages to flash after installing a GSI

I'm leaning towards #2 if we can make it work, then we (hopefully) don't have buggy blobs and don't need special steps to flash a GSI either.
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] omonra2004:
How do I implement this?
[Moto G5S  ROMs, Kernels, Recoveries, & Other Devel] JarlPenguin:
qti-telephony-common is a system framework, so it should be included in GSIs. I'm pretty sure the only thing in /product is VoLTE-related things (which doesn't work on GSIs anyways). Also, /product was already designed to be able to interact only with system libs, so putting them in /vendor would only break them more.