yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] AgathosAnthropos:
Howdy. I managed to get 17 (and 17.1) to build but am having issues with bringup. Feel free to see what I've done at

https://github.com/AgathosAnthropos/android_device_motorola_clark/

I'm having issues updating for system-as-root which it sounds like all Android 10 devices have to have and hopefully you're more capable than me for updating.
[X Style (Pure) Android Development] randomblame:
I spent the morning on the phone with the guy who donated his old pure to me, got it unlocked finally woot so I have a device that works now lol. 17 builds Just got it flashed and it's stuck on boot animation

here's my git as well https://github.com/randomblame/android_device_motorola_clark/commits/lineage-17.0
[X Style (Pure) Android Development] randomblame:
definitely hanging on audio policy

*and now keymaster / gatekeeper for modem as well as camera provider

*some sort of linker issue with apex
[X Style (Pure) Android Development] kb8no:
New system for 16 (as I read it)? Could you throw us a bone? Woof. Woof.
[X Style (Pure) Android Development] randomblame:
new hardware for compiling android lol I have a 10 core 20 thread xeon proliant gen 8 in the laundry room with 128gb of ecc ram networked via 10gig fiber optics and sfp+ to my new desktop with a ryzen 9 3900x and 32gb of ddr4 and a 1tb pcie 4.0 nvme drive :D [IMG="desktop"]https://pbs.twimg.com/media/ENyYTU9UUAERty2?format=jpg&name=small[/IMG]

Need another of these nvme drives and another 32gb kit on the desktop and I'll be able to ditch the proliant
[X Style (Pure) Android Development] kb8no:
I will have to Google about 50% of the words in your post to unravel more of it. [emoji53] But I get the big picture without Google. And, a picture is worth 1000 words. [emoji16] I'm thinking this means it doesn't take long to compile a measly Android ROM with a laundry like that. [emoji6]

So a new LOS 16 build would be a tasty bone. [emoji2960]
[X Style (Pure) Android Development] randomblame:
I'll pull 16 and try to put that together
[X Style (Pure) Android Development] Timmmmaaahh!:
I think I'm in love [emoji7]

Edit: is that a Corsair ICUE 220T RGB Airflow?

Wrapped with delicious Fajita [emoji896]
[X Style (Pure) Android Development] randomblame:
yes it is :D brand new build still breaking her in. I like this case but it's a little on the small side for me if it was just a bit longer so I could have a 360mm radiator on top and a bit deeper for cable management on the back side it would be perfect.
[X Style (Pure) Android Development] randomblame:
new build of lineage 16.0

https://www.androidfilehost.com/?fid=4349826312261700035
[X Style (Pure) Android Development] B4oE:
Nice! Great job! Any bugs that we need to know about? Would this be considered stable enough to use as a daily driver?
[X Style (Pure) Android Development] kb8no:
Dirty flashed fine.

Slow boot with "Process System isn't responding" error unchanged. Still takes > 2 minutes to settle down and get data. Crash on closing tether still present. No Netflix.

Seems snappier.
[X Style (Pure) Android Development] randomblame:
I swear with every new version I hate android more and more. why must they break everything good?
[X Style (Pure) Android Development] AgathosAnthropos:
Which "features" in particular in 10?
[X Style (Pure) Android Development] kb8no:
Regarding Netflix, with lots of trial and error I found that this file on androidapksfree.com works fine.

com.netflix.mediaclient_v6.26.1-build-15-31696-31696_Android-5.0.apk

This is apparently the last v6 build. Nothing from v7 worked at all.
[X Style (Pure) Android Development] randomblame:
trying to get /firmware mounted correctly that's what's holding up the boot process at the moment.
[X Style (Pure) Android Development] ccic2491:
Have you tried magisk? I'm using that and Netflix is working fine on my phone.
[X Style (Pure) Android Development] kb8no:
Of course. Do a Netflix search on the forum for this January. Are you using this ROM? So what version of Netflix are you using? It is blocked in Play store with this ROM.
[X Style (Pure) Android Development] ccic2491:
I'm using the latest version of this ROM (20200113) and I have Netflix 7.39.0.
[X Style (Pure) Android Development] kb8no:
So I am using the same ROM. Latest Magisk. Passes SaftyNet. PlayStore does not show me Netflix so cannot even download it. I have same configuration on 3 different phones and no Netflix. So what do you think the deal is?
[X Style (Pure) Android Development] ccic2491:
I'm not sure......I had that problem with my old Moto g3 but I downloaded apkpure and installed it that way.
[X Style (Pure) Android Development] kb8no:
So, did you install your Netflix from the play store?

---------- Post added at 02:00 PM ---------- Previous post was at 01:00 PM ----------

Have you actually played a movie? Try it.
[X Style (Pure) Android Development] ccic2491:
I did install it from the play store and it plays movies just fine, I'm watching the Aaron Hernandez thing right now.
[X Style (Pure) Android Development] kb8no:
Dirty flash or clean flash of ROM?
[X Style (Pure) Android Development] ccic2491:
Clean flash right after I changed the battery, restored the phone and updated to the last update Motorola ever did.
[X Style (Pure) Android Development] kb8no:
This is weird. So I have several of these phones. I went to the only one that I clean flashed and only added Gmail and Chrome. I think I cleared cache and data in Play Store too. Netflix was there in Play Store. Installed, came up, and played movie as you described.

Other phones were dirty flashed from Dec ROM. Could not find Netflix in PlayStore. Able to side load v6 and worked. Hummm...

So uninstalled Netflix, cleared PlayStore cache and data, and BAM, I could find Netflix and install it. Netfix started up, It would play the trailers, but error message when I tried to run a movie.

Then I tried to get back to v6 and now that is broke. Hummm

So Netflix is always the last thing I install. So at least for now, the moral of the story seems to be if you love Netflix, you need a clean flash of 0113 randomblame ROM, install Majisk, load Netflix first thing, and might need to clear PlayStore.

But for sure Netflix latest version can work on clean flash 0113 ROM. I wonder if [MENTION=1776875]randomblame[/MENTION] can shed some light on what is really happening here.
[X Style (Pure) Android Development] kb8no:
I confirmed and repeated now on two phones that Netflix from PlayStore installs AND plays movies on LOS 16 randomblame build 0113 at least under the following conditions:

Clean flash ROM (wipe everything except ext SD)

OpenGapps nano latest

Magisk 20.3

This exercise illustrates the axiom that a clean flash is the gold standard and a dirty flash is a risk particularly in the early development stages.

Thanks to [MENTION=4672472]ccic2491[/MENTION]
[X Style (Pure) Android Development] lautaro589:
Hello in the new update is the camera already smoothly and correctly?
[X Style (Pure) Android Development] B4oE:
Help: I am running Android Nougat and I have modem version 2.6-00149, according to TWRP 3.3.1-0. However, while trying to flash the newest build, TWRP says that I cannot since I need to have modem version 2.6-00185 or newer. I already factory reset my device. So that did nothing.
[X Style (Pure) Android Development] kb8no:
You do not give us enough information. Are you using stock Nougat or Lineage Nougat?
[X Style (Pure) Android Development] B4oE:
I am running stock Android Nougat on my Moto X. The bootloader is unlocked and I have TWRP 3.3.1-0 as my recovery. I have never installed LineageOS 16.0 on this device.
[X Style (Pure) Android Development] kb8no:
"trying to install the newest build". You certainly mean newest build of LOS 16 from randomblame a few posts back? I would flash a clean stock nougat and get it running. That will replace TWRP. Then fastboot TWRP and boot into it. Then tell TWRP that it can change system. Then flash LOS 16 and nano open gapps together. Then boot LOS 16.
[X Style (Pure) Android Development] lautaro589:
hello I have problems to run the camera in third-party applications, it starts but it does not take the images, when I try it it drowns and I have to close the application

Ex: intagram, whatsapp
[X Style (Pure) Android Development] tigger360:
As far as I know, this is a known bug. I haven't been able to take a picture in 3rd party apps ever since I started using this rom. It would be cool if it were fixed, but I believe the dev is focusing on getting Android 10 working.
[X Style (Pure) Android Development] kb8no:
I thought third party apps used screen shots and not the camera, hence the workaround back in the day when the camera didn't work was to use these screen shots from these apps as a third rate camera. I never use these apps except to try it once back then and the screen shot thing indeed worked.
[X Style (Pure) Android Development] tigger360:
Yeah, i remember that but I wasn't using the ROM at the time. I got it after the camera fix and I have never been able to get the camera working in 3rd party apps. Even after my recent clean install to get Netflix working.
[X Style (Pure) Android Development] redwoodie:
Netflix Playstore cache clearing

I found this to be mostly true. However, after I cleared the Play Store cache and data, my Google cloud backup of apps seems to have taken a powder, and my apps won't auto-restore. My preference would be to let Google re-install my apps versus some futzing around with Netflix.

Worse, my Titanium Backup of apps from immediately before the reflash won't restore either--the apps on the SD card all have a line through them in the restore interface. *sigh*
[X Style (Pure) Android Development] kb8no:
You are confusing me or you are confused. To make Netflix work you must do a clean flash of randomblame LOS16. You cannot get around it. To do this then you wipe everything except Ext SD. When you clean flash ROM then you have also a clean Play Store. No need to clear Play Store because it is already clear. Clear Play Store was only used by me experimenting with dirty flash of randomblame ROM to see if I could get around a clean flash. As you read in my post, it did not work. I don't want to reinstall all my apps any more than you do.

If you clean flash randomblame from scratch, you are on your own trying to use Google or Titanium to salvage your apps on your new shiny clean flash. A true clean flash has all clean new installs of your apps and settings. I stopped using Titanium for this reason long time ago. I never used Google. So we are going through all this trouble just to use Netflix, or, like me, just to prove I can make it work. It is my hobby.

But if randomblame were ever to drop us a gift of a new build after going through all the hassle, odds are a dirty flash would be fine. But the dev's never promise, they just say it probably will work and clean flash of it doesn't.

If you are bound and determined, I would do a clean flash and install Netflix. Don't mess with Play Store. Prove to yourself it will play a movie. Then experiment with Google or Titanium to install your old apps and settings making sure you don't overwrite Netflix with a corrupted version. See if it works and let us know.
[X Style (Pure) Android Development] redwoodie:
I did exactly that--total wipe and clean flash of the latest LOS16 build. It had an earlier build LOS16 on it before I wiped. You're saying install Netflix via downloaded APK? In this case Netflix installed from play store and works. I would just like to get the apps reinstalled without doing it manually. I have 2 stock X4s with same collection of apps, maybe I should factory reset and copy form other phone?

Wish this was as easy as importing a backed up software list in Linux.
[X Style (Pure) Android Development] kb8no:
Yes. It is a pain! Yep, install Netflix from PlayStore on your new clean flash and it works for you as it should. So you fixed Netflix which is the only app I found that that did not tolerate a dirty flash. Now you are in a better place because there was some subtile incompatibility from old ROM to new randomblame ROM.

Now how to easily get your old apps is easy. It does not take long to just install them. The real issue is all the settings, apps and ROM, that is the killer. It is my understanding that it problematic doing this across different ROM's and hardware. If you want to figure it out, I'd make a backup of your clean ROM with Netflix. If you break it you can start over more easily with a restore. Otherwise, bite the bullet.
[X Style (Pure) Android Development] redwoodie:
Is it worth trying any of the apps that purport to transfer apps, settings etc. between phones?

The restore via Google backup is usually pretty good, it's unfortunate there doesn't seem to be any way to initiate it besides factory reset.
[X Style (Pure) Android Development] kb8no:
I'd like to know too! Maybe someone smarter than us will pipe up. I know nothing about Google backup but I flash so many phones I can't see how it could do it right if it was always the whole thing.

Back in the day Titanium was cool and you cold pick an choose. But still it had to be the same ROM. Then it got obsoleted.

I gave up. A clean flash will take days of tweeking. When the ROM has rapid new builds I just put on the necessities. When it is slow gradually add and tweak until I get it right. This has been a generally slow forum and right now too quiet. I got randomblame build clean flashed and just how I want it. It has quirks but it is a reliable phone now.
[X Style (Pure) Android Development] redwoodie:
Restoring apps after wipe and flash

I tried a few of the app backup/restore apps in the Playstore and no love there. All I tried have broken parts and stuff that just doesn't work. Some can't mount or write to USB OTG (even when the system does), which is seriously dumb given there are devices out there with no SD slot. The last one I gave up on couldn't manage to upload even half the selected apps to Drive, then you had to download the apps again to new device and then install...most didn't download, some selected for install failed while others not selected were installed. After swapping SD card with the backup to new device, had to install apps one at a time requiring 2 tap confirmations for each...and 1/3 of them failed with "Unknown", "App Not Installed" or "Problem parsing package" messages. You can do it faster and easier just downloading everything from Play Store again one at a time! I often wonder if the devs on some Play Store apps ever try using them?

By comparison, Google Backup is pretty good, and much faster (still takes a day or so to restore 150+ apps, it manages to restore about 90% of them or better). But I've had problems with it too, and apparently it can only be initiated immediately following a factory reset/new flash and data wipe/new device.

Anyway, got Clark pretty well tweaked and liking the latest build. Thanks to Randomblame and everyone who contributed.
[X Style (Pure) Android Development] kb8no:
Thanks for your hard work and confirming my belief system. Sigh.

This is a nice, usable ROM. It's all I use and I enjoy it. Wish it could get a little love and fix a few annoying things but better than previous!
[X Style (Pure) Android Development] lautaro589:
Any link of lineageOS 17 denies its test phase?
[X Style (Pure) Android Development] xda_maddogdean:
Thanks to everyone for ALL the hardwork. I've finished downloading everything (including the stock firmware... just in case)

Any advice for root? SuperSU or Magisk? Pros or cons of each?

Thanks in advance,

Cheers,

MadDogDean
[X Style (Pure) Android Development] tigger360:
I use Magisk. Haven't had a problem with it. It allows you to use apps that need your phone to pass SafetyNet.
[X Style (Pure) Android Development] xda_maddogdean:
Hey all, been a rough night with all sorts of ADB driver issues on the pc. Got it all sorted and rolling smooth :)

But....

what version of TWRP is everyone using with this? I've tried flashing 3.1.1, 3.2.3, 3.3.1, and everything *looks* finished, but when I reboot into recovery I get the dead Androind and "No command". Obviously the TWRP isn't getting in there somehow (even though it says it is in fastboot)

https://www.dropbox.com/s/ztvjojymix1l37d/twrp flash.jpg?dl=0

[IMG="TRWP flash"]https://www.dropbox.com/s/ztvjojymix1l37d/twrp%20flash.jpg?dl=0[/IMG]

Thoughts? Cheers

---------- Post added at 08:16 AM ---------- Previous post was at 08:03 AM ----------

Got it. found the answer on this thread https://xdaforums.com/moto-x-play/help/bootloader-slotrecovery-t3436406

When you finish the flash DO NOT reboot, use the volume buttons and go directly into Recovery. Problem solved!!:good::laugh:
[X Style (Pure) Android Development] lautaro589:
Hi, is there an update where the camera works?
[X Style (Pure) Android Development] xda_maddogdean:
I'm running this ROM and the camera is working fine. It only works (or so it seems) with the stock camera. Open Camera *appeared* to work, but it never actually saves the photo....

The stock Camera doesn't have as many bells & whistles as 3rd part Cam apps, but to make real photos I use a real camera :p

Cheers

PS. This has been my daily driver for several weeks and there are no real complaints :good:
[X Style (Pure) Android Development] kb8no:
Use the latest build from the OP, 2020-01-13 build of randomblame. You MUST be coming from a good working stock Nougat base to have good Nougat firmware or this ROM will not work correctly.

Do a complete wipe of everything except extSD before you flash the ROM. Use Gapps nano and and the flash will install our hacked LineageOS stock camera, a real camera and the only camera that works. If you use larger gapps it overwrites the working camera with Google camera which does not work. Don't bother to try other cameras.

Be aware that photos taken in portrait are stored sideways and use gallery to rotate them if you care. Landscape photos are stored properly if you take the shot with button on the right.

There is a delayed boot problem with this ROM that randomblame and others have not been able to fix. When you boot this ROM it can't connect to data correctly right away. Let it sit for a few minutes while it figures out what to do. This takes about 2 minutes and if you are observant you can tell when it is done and ready for you.

Tether works but does a soft reboot when you shut the tether off. Annoying but you can live with it. Nobody has been able to fix this either.

And here is something nobody has mentioned before and requires using this ROM for some time to start noticing. If you run this ROM for a few weeks it starts to get more and more laggy. I now reboot it once a week or so to keep it fresh.

That's it. Great ROM.
[X Style (Pure) Android Development] tj90241:
Perfect ROM... except for voice calling! When "LTE" is set to my preferred network, I'm unable to receive incoming calls (though I can make outgoing ones fine). When I kick it down to "3G", I can receive calls, but depending on the area I'm in and how strong the 3G signal is... the phone sometimes falls back to EDGE and then phone quality becomes so bad that I need to hang up.

This is on T-Mobile in the US. With the stock ROM, voice calling was perfect.

If anyone has any tips, I'd love to hear them. I like the ROM so much that I'll probably learn to make do, but this ROM might not be a daily driver for everyone if voice calling is hit/miss.

EDIT: Found the "WCDMA only" option in the #*#*4636*#*# menu, which seems to have locked the modem to UMTS voice/HSPA data... crossing my fingers! Turning off "VoLTE Provisioned" does not work (it simply turns itself back on); so I'm guessing the above issue is due to the fact VoLTE is not working on with this ROM and T-Mobile right now.

EDIT 2: Can't post links yet, but look at LineageOS/issues/android/issues/745 ... seems to be an issue with LOS 16+. Locking the phone to WCDMA when you need voice calling is a workaround.
[X Style (Pure) Android Development] kb8no:
Stock ROM was Nougat, yes? Did you check APN? Sometimes it gets corrupted and/or does not import SIM info properly. I have had that happen. You need to pick correct APN. Don't use TMo so not sure of correct APN. Are you letting it sit for a few minutes after boot?
[X Style (Pure) Android Development] tj90241:
Yes, flashed from latest OTA Nougat and compared baseband to what others here have reported (09R, IIRC).

My fast.t-mobile.com APN (data) is correct, as LTE for data/browsing/etc. works spectacularly well. Funny you mention it -- I don't even have the "2 minute hang" issue at boot that you reference -- the modem is ready to rumble the moment I put in my pin code after a full phone reboot.

I think have the correct APN for T-Mobile (IMS). I'll look into that; information online seems sparse. Can anyone confirm that VoLTE/IMS actually works for this ROM? I certainly don't expect it to and have not spent much effort looking into that.

The GitLab bug I linked is super relevant here: LOS15/16 + T-Mobile US (both together) don't work well when VoLTE is not provisioned. When there's an incoming call, the modem remains at LTE instead of kicking down to 3G, so neither side hears each other and eventually it just hangs up. It's smart enough to drop to 3G before you initiate a call, though, so outbound calls are fine.

EDGE connectivity in my area is not good enough for voice calling, but HSPA+ is. At the same time, this ROM seems overly eager to jump the modem from 3G to 2G for me. I'm guessing some RSSI thresholds could use some fine tuning somewhere?

Anyways, to summarize: locking the modem to WCDMA when you both have T-Mobile US and need reliable voice calling seems to work just dandy. Switch back to LTE when you are done with the voice calling and you have all the benefits of LTE data again... just hopefully nobody decides to call you! :laugh:
[X Style (Pure) Android Development] kb8no:
[MENTION=5794081]Tj90[/MENTION]421 Where is the VOLTE setting where you enable / disable it? I can't find it.
[X Style (Pure) Android Development] xda_maddogdean:
Hey all, anyone having a problem with their battery?

Running this ROM as a daily driver for a couple of weeks with no major issues. My battery (about 6 months old) was perfect until 2 days ago, when it dropped to 4% overnight WHILE charging and will not go any higher. I've plugged it on slow charging from laptop, original Samsung charger, high speed QC3.0 charger but nothing changes - it just sits at 4%. Tried rebooting, turning off, removing battery for 10 minutes, etc, but no change. I've ordered a replacement battery (should be here in a few days) but will keep trying.

What do you think if I dirty flash the ROM? Do I need to reflash GAPPS as well?

Cheers
[X Style (Pure) Android Development] R77:
I did a clean wipe and flashed the ROM it booted up just fine. I then charged it since it had low battery then I flashed the new version of magisk 20.3 it booted on the Moto white screen. It turned off and it just became a boot loop. I have the nougat firmware that I flashed a coupe of years ago. The twrp version 3.1.1-0 any help?