yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] The-Saint2k:
Hello,

the next build is ready:

15.1 December 19
[Shield Tablet Android Development] Snah001:
No 14.1 build??
[Shield Tablet Android Development] debby_:
14.1 ?
[Shield Tablet Android Development] thelangosta:
14.1 has functioning hardware acceleration. So far that hasn't been fixed on newer builds.

Edit: I think I should have said hardware encoding
[Shield Tablet Android Development] The-Saint2k:
Hello,

unfortunately I can't build 14.1 at the moment. At the moment not all security fixes are closed, so they will not be considered when compiling. I check daily at https://www.lineageoslog.com/14.1 if there are any changes.

Sorry.
[Shield Tablet Android Development] The-Saint2k:
Hello, everybody,

finally all changes in sources for the December update are ready. So here now late but better than never :).

14.1 December
[Shield Tablet Android Development] SpRiNgToIfEl79:
No mirror download for 14.1 DEC package aviable? :(

Its working now...
[Shield Tablet Android Development] player594:
Mirrors are not working.

Seems to be working now.
[Shield Tablet Android Development] Snah001:
Thanks a lot.

Keep up the good work!!!
[Shield Tablet Android Development] seokol:
This is my first time using lineage os I've downloaded the 14.1 build and gapps on my pc what are the steps I need to take?

---------- Post added at 04:23 PM ---------- Previous post was at 04:18 PM ----------

Additionally is the shield tablet the same as the shield k1 as some websites have them separate.
[Shield Tablet Android Development] LukeSlovian:
Hi, there is an NVIDIA Shield TV console exactly this model P2897. I bought this console with a pre-installed version of Android 8 Oreo. Those who want to run LineageOS on this console do not care which version. Do I need to downgrade the firmware from Android to Nougat version 7 ? If I currently have Android 8 Oreo preinstalled - can I enter recovery mode and run the installation of a non-standard TWRP recovery-dedicated to this console from an img file ?
[Shield Tablet Android Development] turilo:
Ok so I purchased an original Nvidia Shield tablet, first gen. One with the stylus 16gb wifi. Not the K1 model.

It actually came with CyanogenMod version 13.0 build v5.1 by Temasek.

6.0.1 MM

Also has TWRP v3.0.0-0

Ive been out of the scene for a while, can I flash the 14.1 version here overtop of this build and flash the updated 3.3.1.0 TWRP?

Assuming I have to wipe system first of course.

Thanks to the op also for keeping this up to date for us. :good:

Also I keep hearing about this Nvidia pushing updates to brick the devices?
[Shield Tablet Android Development] turilo:
I'm getting error 7 flashing latest 14.1 on original nvidia shield using latest twrp 3.3.1.0.

Any ideas?
[Shield Tablet Android Development] silvershadow:
Cant help with your main question, but i can definately clear up the information regarding the bricks.

There were a bunch of original shield tablets that had a "defective" battery. Everyone that had a possibly effected model was able to request a replacement. Nvidia let us dispose of the old one ourselves rather than forcing us to return it to them.

Inorder to "ensure" we all stopped using our possibly dangerous old tablet..the "brick" update was pushed to all devices that had the serial number you submitted when performing the recall. If i was to reinstall stock on my "pyrotablet" right now without removing the updater, it would brick.

To combat this, people installed custom roms, or removed the tegra updater (cant remember exact name right now). There is a chance the unit you have was one of the "dangerous" units.

Ive had my recalled and replacement tablets for soo long now, that i dont even remember which one is which anymore. I run a modified stock without updater on one, and lineageos 14.1 on the other.
[Shield Tablet Android Development] RichBordoni:
Go to page 14. I posted a little guide there for installing LOS from scratch. The original SHIELD and the SHIELD K1 are different models but for the purposes of LOS they are the same.

Did you do a full wipe before flashing?

As far as I'm aware, you don't have to worry about downgrading the stock firmware as long as you do a full wipe before flashing LOS.

Not sure what you're asking here. Do you have TWRP installed or you want to install TWRP?
[Shield Tablet Android Development] SpRiNgToIfEl79:
LOS 14.1 Dec:

The Option "Disable absolute volume (Bluetooth)” in "Developer Options" will not working.

You can Switch it on, but no effect / the option is not be setted after closing the Developer Options...
[Shield Tablet Android Development] RichBordoni:
Hmmmm, can you post a screenshot or picture of the error?

Maybe try to wipe everything including recovery and re-flash TWRP, or delete the ROM files and re-download them (in case they got corrupted somehow) and try again.

If that doesn't work, it's a bit of a hassle but you could also try following the instructions here and re-flashing everything back to stock before installing TWRP and the ROM. (files here)

I have the same original SHIELD as you and that's exactly what I did. I previously had a much older version of LOS installed (and I think from a different developer) but I let the tablet sit for like a year or two without touching it. When I came back to it I didn't know what was going to be compatible with what so I decided to basically just start from scratch. I re-flashed everything back to stock, then installed the latest TWRP, then flashed LOS + GApps + root.

If even that doesn't help, then maybe try these instructions here: https://android-fix.com/android-errors/61-status-error-7-twrp.html

Also I remember reading at the beginning of the thread that some other people were having issues with Error 7. You may want to go back and read through and see if there's any information that can help.
[Shield Tablet Android Development] vrman:
I was able to flash TWRP and version 14.1 on a virgin LTE model without any issues. I did have to use the pico GApps package due to error 7 on the GApps stock package(Something related to storage space).

Reading thru the thread I didn't see any mention for a source to the Nvidia apps like Dabbler and Stylus launcher. Any direction or alternate apps for these?
[Shield Tablet Android Development] RichBordoni:
I had the same issue with storage space and had to do the same thing... though I don't remember what error number I got. I just remember it directly told me it couldn't flash the GApps because there wasn't enough space.
[Shield Tablet Android Development] RichBordoni:
Sorry for the double post, but can anyone tell me if their Bluetooth is working? No devices are showing up under Bluetooth for me.

(I tried to search this thread for 'bluetooth' but it doesn't seem to be working - it's saying there are 0 results which I know is wrong)
[Shield Tablet Android Development] Sir Daniel III:
I have working Bluetooth on LineageOS 14.1 October 23 Build
[Shield Tablet Android Development] RichBordoni:
Thanks. I'm on the Dec 23rd build and rooted. Can't get any Bluetooth devices to show up for pairing. Don't really want to do a wipe and clean flash but I'm not sure what could be causing this?
[Shield Tablet Android Development] Sir Daniel III:
Were you able to connect to Bluetooth before...? (Also forgot to mention that I'm rooted too). You think it's a software issue or hardware issue?
[Shield Tablet Android Development] RichBordoni:
I did a total wipe and flash a few builds back but I didn't have the occasion to turn on or try to use Bluetooth since then until yesterday. Before that I hadn't picked up the tablet for a year or two and it was on a much older and totally different build of LOS. I can't really remember specifically if Bluetooth was working back then or not.

Don't know if it's a hardware issue or not. If it was I feel like I would be getting more serious errors? All it's telling me is "No Bluetooth devices were found" after scanning for awhile while other devices that I have are able to see and pair just fine. Somebody a few posts up in the thread mentioned a setting pertaining to Bluetooth in Developer options wasn't working for him. Maybe that has something to do with it? Is anyone else on the latest build that can test to see if their Bluetooth is working?

Also, do you have the original SHIELD or the K1?
[Shield Tablet Android Development] Sir Daniel III:
I have the K1. You're on LOS 14.1 December 23rd build right? I can flash that ROM later to see if it works.
[Shield Tablet Android Development] RichBordoni:
Hmmm, I have the original model. Maybe that's why? Yes I'm on the Dec 23rd build. I didn't want to ask you to update in case your Bluetooth stopped working, but if you're OK with taking the risk I'm curious to see what the result is. :fingers-crossed:
[Shield Tablet Android Development] debby_:
Bluetooth works fine. Shield t - K1 here.

14.1 dec build

###+

Dev --> dis. abs. volume... Works
[Shield Tablet Android Development] TheToxicant:
Anybody have a link to the December build I can't seem to find it.

(Found it)
[Shield Tablet Android Development] 414isaiah:
Thanks so much for this, I have an original shield tab I would like to breathe some life into. I haven't rooted or flashed anything since my note 2 should be fun figuring it all out again haha... thanks!!!
[Shield Tablet Android Development] The-Saint2k:
there is again a current build for LineageOS 15.1. for 14.1 it currently looks quite bad. I'm also unsure how long there will be updates for 14.1, because Google officially doesn't release any adjustments for Android 7.1 anymore. But I hope that the diligent developers of LineageOS will continue.

LineageOS 15.1 Januar
[Shield Tablet Android Development] RichBordoni:
Can anyone with an original non-K1 tab on 14.1 report if Bluetooth is working for them?
[Shield Tablet Android Development] Sir Daniel III:
Yeah I'm sorry for the late response, but Bluetooth is working on my K1 on the December build. Might be an issue with the original model; I wouldn't know
[Shield Tablet Android Development] RichBordoni:
Np, thanks for checking anyway! :)
[Shield Tablet Android Development] x Revo:
It is working for me, latest build.
[Shield Tablet Android Development] RichBordoni:
Thanks for checking. Guess I'm going to do a backup and a full wipe and report back with my results.
[Shield Tablet Android Development] animeware:
The latest build 15.1 crashing for me too Wallpaper not responding and Nvidia Shield Geforce is not responding too...
[Shield Tablet Android Development] moviefirst:
I had this issue to when I flashed nano gapps, with pico gapps no crashing anymore. 15.1 is fine for me only standby battery drain is a bit high.

Thanks for the rom!
[Shield Tablet Android Development] RichBordoni:
Just did a full wipe, flashed the latest (Dec) build of 14.1 + su, and Bluetooth is now working! (It worked before I flashed root too. I was wondering if maybe that was the culprit.) Very weird - I had done a full wipe only 2-3 builds back. I guess one of the dirty flashes I did since then messed with the Bluetooth somehow?
[Shield Tablet Android Development] bigcletus:
Really liking the ROM, but I can't get Nvidia Games app to connect to Nvidia. Anyone had luck with this? Running 14.1 on Thanks.
[Shield Tablet Android Development] RichBordoni:
Just tested this and I'm having the same issue. Somebody else posted about this not working a few pages back also.
[Shield Tablet Android Development] Sir Daniel III:
I've never got it to work, ever.
[Shield Tablet Android Development] bigcletus:
it is a strange problem. I have Lineage OS 15.1 on my Nintendo Switch and it can login and connect just fine. The Shield Tablet is an official Nvidia device running the same software as my Switch and it cannot login.

It seems to be a network related problem perhaps? I have network monitor activity enabled, when I click on the news tab I can see network traffic in the status bar, but when selecting games or logging in through settings there is no traffic displaying. Its as if it not even attempting to make the connection.

Also, when I install the LOS rom on the Shield, during the initial setup wizard's google account info, I set up as new device but I never get a notification on any of my android devices that a new device has signed in. I saw a user report something similar to this on the Shield TV forums and he installed the LOS without gapps to resolve, but I tried that too without any luck.

Update: Ok, I installed LOS 15.1 to test Nvidia Games (was on LOS 14.1) and I can successfully login to Nvidia Games app just fine. Games are showing now and I can select them. Unfortunately, they don't ever run, I think that may be because 15.1 has issues? I wonder why I can login to Nvidia Games on 15.1 but not on 14.1. I also get the "new device sign-in notification setting up 15.1 that I am not getting on 14.1.

I am looking into the PMF router thing right now.
[Samsung Galaxy S10 Questions & Answers] Jannomag:
Hi guys,

on my trip to Ireland I missed a nice feature of my old Huawei P10 where I can set a mode for long exposure photography at daylight to make water look smooth (for example). Huawei made an extra mode for this including light burst and other nice features.

On the S10 I'm missing such a thing.

With the pro mode I can set the exposure time but the photos are getting way to bright.

Does someone know how to make such long exposure pictures with the S10?

Greetings,

Jannomag
[Samsung Galaxy S10 Questions & Answers] AHE_XDA:
[MENTION=6954776]Jannomag[/MENTION]

What you're trying to accomplish will require 'Pro' mode.

Click on the 'Galaxy S10+ - F-Stop & Exposure.jpg' screenshot I attached.

That should allow for longer exposure; anywhere from 1/24000 to 10 seconds.

The second screenshot, Galaxy S10+ - ISO.jpg, should assist if you're looking to introduce more/less light.

I don't find the Galaxy phones great for manual photography but, using the two settings together, you'll eventually find the right balance for you.
[Samsung Galaxy S10 Questions & Answers] Jannomag:
As I mentioned it above, the photos are getting overexposed. See the example I attached. I used f1.5 with 1/4 exposure.

As an example I also attached a picture made with my wife's Huawei P20 and it's silk water mode.
[Samsung Galaxy S10 Questions & Answers] AHE_XDA:
I'm giving to provide some insight and kindly step away from this discussion. :)

Every hardware vendor approaches digital imaging differently. Meaning just because Huawei achieves one effect; doesn't necessarily mean Samsung isn't able to and vice-versa.

To the best of my knowledge, Samsung doesn't have a 'silky water mode' but that doesn't mean it's impossible.

For example, here is a reference image taken from a Galaxy S8 (a device from 2 years ago):

https://i.redd.it/gmmnsuguop311.png

The user in question, kiosk123, used the Samsung camera app and manually set his ISO to 50 with a 2 second exposure.

With a tripod and a similar setting, I don't see why you wouldn't be able to do the same.

Here's a simple tutorial if you require more explanation:

https://www.youtube.com/watch?v=RpBwaB7I4EM
[Samsung Galaxy S10 Questions & Answers] Jannomag:
On night time or low light it's possible but on daylight, the photos are getting too bright. (Look at my Attachment, where I used ISO 50 and 1/4s shutter speed with f/1.5).

I think Huawei doesn't use the shutter speed for this effect. Instead they're using a series of pictures and merge them.

An app which does this would be also great, but I couldn't find any.
[Samsung Galaxy S10 Questions & Answers] pchetan2:
Did you try editing the picture after actual shot ? Shoot in Raw and edit using Photoshop for android or snapseed.

Manual Exposure control helps but is disbaled when using manual shutter speed after 1/10 and I dont think we can capture the effect you need
[Samsung Galaxy S10 Questions & Answers] Jannomag:
I tried to edit it, yes. But it's way too bright.

I'll try to shoot many pictures in burst mode and combine them manually on PC. It's a handy work but it should work
[Samsung Galaxy S10 Questions & Answers] redsmith:
Have you tried using f2.4? Maybe it can help bringing the exposure down a little bit. Also, make sure to shoot RAW and later dial down the exposure all you can in Lightroom.
[Samsung Galaxy S10 Questions & Answers] Jannomag:
With f2.4 it's even e bit brighter. Also with RAW it's too bright to get back every part of the image. Some parts are completely white.

It's sad that there's no different app or that Samsung doesn't support those nice features. I used them often on my holiday trips. Also the light trail feature is quiet nice because sometimes the picture gets also too bright when shooting in cities with near street lamps.

nvm...I have to deal with it, it's sad for a 800€ phone but everything else is good.
[Samsung Galaxy S10 Questions & Answers] Anoyyo:
You have to use ND filter to achieve the long exposure shot during daylight.
[Samsung Galaxy S10 Questions & Answers] migsims:
You're literally asking for something that doesn't work without an ND filter.

The whole point of LONG EXPOSURE is literally in the name.

You can't get "long exposure" without exposing the sensor to more and more light the longer the shutter is open.

Whatever huawei was doing isn't real long exposure during daylight because that is impossible without an ND filter over the lens.
[Samsung Galaxy S10 Questions & Answers] andyshandyman:
The p20 uses software to average multiple expdures so you could so it in bright daylight. It worked really well and wish I had something similar on my s20
[Android Stick & Console AMLogic based Computers] puradawid:
I am looking for two things:

- any ROM or uboot.bin for AML6726-MXL with EM_M62_V4.0 device (or any way to build that up)

- JTAG pins on EM_M62_V4.0 board, as there are many test pads but I can't find any schematic for their description

I have one bootlooped board and one that is bricked completely (probably because it had an attempt to install wrong AML uboot/ROM).

Anyone met that board and processor (it was years ago, probably) and want to share their findings? It looks like HTTP download server for openlinux.amlogic.com is down for years already. Appreciate any help!
[Android Q&A, Help & Troubleshooting] hydroponics_1:
I want to move /system /vendor /cache /data to microSD card by editing /vendor/etc/fstab.mt6765 and other files on /vendor.

modified /vendor/etc/fstab.mt6765

/dev/block/mmcblk1p2 / ext4 ro wait,recoveryonly

/dev/block/mmcblk1p3 /vendor ext4 ro wait,recoveryonly

/dev/block/mmcblk1p4 /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable

/dev/block/mmcblk1p5 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,reservedsize=128M,formattable

I have extracted vendor.img from OTA.zip and searched and replaced strings like

/dev/**/**/**/system with /dev/block/mmcblk1p2

and

/dev/**/**/**/data with /dev/block/mmcblk1p5.

I have unlocked the bootloader using

fastboot flashing unlock

.

I am not modifing /system. I will copy system.img from OTA.zip to sdcard using dd.

since I am not modifing /system I think it is safe. Is there possibility of issues with dm-verity?

Have I disabled dm-verity by unlocking the bootloader?

On an android-6 device with no /vendor partition I have moved /system /data /cache and /nvdata to sdcard by modifing boot.img.

But this android-9 device uses System-as-root ( /system is mounted at / ) and boot.img doesn't have fstab.** and .rc files. Some .rc files are in /system (mounted at / ) and other .rc files and fstab are in /vendor/etc/

Is it safe to flash modified vendor.img using

fastboot flash vendor vendor.img
[P3300, MDA Compact III ROM Development] chiqo:
Is there any greek roms with WM6.1? I searched a lot but nothing found.
[P3300, MDA Compact III ROM Development] nikkpap:
look you pm....
[P3300, MDA Compact III ROM Development] nikos2004dj:
and me iám interested about a Greek 6.1 rom

can you send me pm or you can tell here the answer pls ?
[P3300, MDA Compact III ROM Development] nikkpap:
nikos

i sent you my opinion....
[P3300, MDA Compact III ROM Development] chiqo:
I added a poll to this thread about donation. Please vote to this pole. :)
[P3300, MDA Compact III ROM Development] chiqo:
Note: the poll is for greek users
[Samsung Galaxy S7 Edge Questions and Answers] syednawaz:
what do you mean stuck? does it hang on TWRP logo and not moving? Or you want to install some other recovery or stock firmware.

Ps. if you are stock firmware, i hope its latest as you might have updated your bootloader or modem bec of some custom roms.
[Samsung Galaxy S10 Questions & Answers] lame.exe:
Hi guys,

I have a big issue with my S10, probably it's a deadlock...

Successfully rooted with magisk and installed TWRP as described in all the tutorials.

Had some issues with wifi concerning one router and debloated too many apps, so I decided to flash stock rom with TWRP and Magisk again.

Wiped /data and /system and flashed that prepatched AP of G973FXXU2ASF3 again by Odin.

Worked well, flashed multidisabler-g97x-1.2 via TWRP, wiped /data and rebooted to recovery.

Android started, all well and then let Magisk do it's job. It asked for a reboot and then I got locked.

The message "only official released binaries are allowed to be flashed" appeared after that reboot, so I tried to install AP again.

Also in download mode "only official released binaries are allowed to be flashed" appears now, KG state is "Prenormal" and OEM Lock says "OFF (U)".

I know i have to get to the system to skip the 7 days but accesing the system is my problem now.

I can install unmodified AP of G973FXXU2ASF3 but the boot fails.

I can also reach android recovery with options reboot system now, reboot to bootload, apply update from ADB etc.

And I can lock the bootloader in download mode, but I'm not sure to do that.

Thanks in advance if someone can tell what to do best.
[Samsung Galaxy S10 Questions & Answers] lame.exe:
Ok i managed it already by myself.

I locked the bootloaded by long pressing vol+ in download mode and locking the bootloader, so I could start the stock firmware.

Then I had to do the date trick by setting date 7 days in past, searching for update manually, putting date back to today, search again for update and oem lock was visible again in dev options.

Afterwards again to download mode, long pressing vol+ and unlocking bootloader one more.

Then I was able to flash AP with Magisk and TWRP again.

EDIT: The issue was that I didn't check if the OEM Unlock was greyed out in dev options, so the VaultKeeper didn't let me install the unofficial image in download mode as described by topjohnwu.
[LG Q6 Guides, News, & Discussion] tomc1:
Arrived OTA in the UK
[LG Q6 Guides, News, & Discussion] Urosz:
im still on july 2018 mwhen i check it says that there is no update
[Verizon Samsung Galaxy S8+ Questions & Answers] c_acton98:
All of a sudden the speaker automatically opens when I make or receive a call. So much for privacy. I DUCK DUCK GOED but no luck I found an old thread from 3 years ago. But it says a hard reset. Not my first option. Any ideas?