yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] UltraMagnus0001:
Let me clarify because my previous statement is a little confusing.

I flashed the zip using flashfire. Flashfire automatically extracted the files and selected everything except data. Flashfire also selected su install. At the install, there was a warning about io error and it will wait 3 minutes to reboot in order for me to see the warning. After a reboot my screen was blank so I connected my HDMI to the TV directly to see it stuck on th nVidia logo. I tried rebooting with no luck. This is when I decided to try flashing everything manually using Minimal ADB, by placing all the files except data (because I didn't want to wipe my data) and flashing everything one by one. I could not flash vendor, because it wouldn't let me or I don't know the right way. I followed the command for each file from nVidia's website. Since that didn't work I just ran the included batch file and factory reset the Shield. Everything is good now, but flashfire would be extremely convenient in the future and I'm still confused as to what I did wrong. Was there an option to pick my installation drive that I missed?
[Shield Android TV General] jionny:
was the zip installed on your internal because if it was on external that may be the problem also did you use flashfire version 0.73?
[Shield Android TV General] ShadowsDemise:
Is anyone else not able to download the 6.1 developer image directly from nvidia's website? Whenever I try to download the developer image it says I need to be a member of the developer program even though I already am in the developer program.
[Shield Android TV General] jionny:
same here, so I downloaded the developer image from softpedia flashed with absolutely no problems

got it from here http://drivers.softpedia.com/get/gam...re-6-1-0.shtml
[Shield Android TV General] UltraMagnus0001:
Yep. 0.73. I had it on the root of internal shared to my pc
[Shield Android TV General] ShadowsDemise:
I downloaded the image from softpedia but when I would select "Flash Zip or OTA" the zip file wouldn't show up even though I was in the folder that it was in.
[Shield Android TV General] jionny:
been there done that you have to pick flash firmware not ota and make sure screen orientation is off if you have that installed so you can see all of flashfire
[Shield Android TV General] jionny:
Did you get it sorted out?
[Shield Android TV General] UltraMagnus0001:
Well I don't know what happened exactly, but I did a full reset and I'm now in the middle of restoring everything , as in settings etc. Gonna just use my laptop in the future, with minimal adb worked in the past. except for having to put twrp to flash supersu.
[Shield Android TV General] nahsha:
Guys, any 6.1 flashable via twrp?
[Shield Android TV General] jionny:
you can flash it via twrp or flashfire your choice
[Shield Android TV General] nahsha:
I tried the zip posted earlier, got invalid zip. Which zip is good for 2015 shield nonpro? Thx
[Shield Android TV General] jionny:
go to softpedia if you cant download from nvidia and look for 2015 nvidia shield tv 16gb 6.1 developer image
[Shield Android TV General] nahsha:
Interesting, it's the one from softpedia that fails to install from twrp.
[Shield Android TV General] jionny:
is it 1.2gb? can you not install with flashfire? is it the developer image?
[Shield Android TV General] nahsha:
Yeah 1.2. I tried with flash fire, didn't seem to work. Do I just click on the + and select zip / ROM and flash ? Or any other specific options?
[Shield Android TV General] jionny:
you click the + then click flash firmware, everything but data will be checked then hit flash
[Shield Android TV General] dk1keith:
Used this method to update my Shield TV Pro 2017. Worked great. Kept all my apps and games, and root.

thanks much for this.
[Shield Android TV General] unsatgoua:
Not sure why you guys are trying to update this way. Rooted you can't ota, best way is to download the consumer(not dev) 6.0 and flash back to stock(you'll keep all your apps and config but lose root). Then ota and follow the instructions at:

http://nvidiashieldzone.com

Been doing this since 5.0, no need for dev edition, there's no benefit.
[Shield Android TV General] jionny:
That is a matter of choice, I personally prefer the developer image, to stay rooted which for me definitely has its benefits but to each his own
[Shield Android TV General] sammarbella:
I flashed the newest firmware dev as soon it was "freed" over older version since 5.0 (rooted, unlocked, TWRPed).

I agree flashing a stock OTA over a rooted firmware is a nonsense even if it works after a few loops.

What is the benefit to flash a stock small OTA update instead of a full firmware dev for a user already using root?

Reset configs and loose root to simply be able to flash a small OTA update instead of waiting around 2 weeks to get the full updated dev firmware with root meanwhile other ppl act as guinea pigs enjoying the usual bugs?

If you don't get benefit from root then stay stock 100% always. :D
[Shield Android TV General] unsatgoua:
My way I'm on 6.1 rooted on day one, no lost settings and configs. I don't like to wait. The dev ver does nothing more than rooted stock does, unless there's an advantage you can school me on. I looked up the rooted dev ver when it was first released and you still needed to root like I'm doing after the ota's.

---------- Post added at 09:40 AM ---------- Previous post was at 09:39 AM ----------

If I'm wrong school me.
[Shield Android TV General] jionny:
You do not need to root the dev version it is pre rooted, just flash with flashfire its that simple, your way while I m not knocking it adds more steps. Once again its a personal choice not a right or wrong choice
[Shield Android TV General] dk1keith:
can I use this same method with Flashfire to flash 6.1 but check data to wipe all app data and install a clean 6.1?
[Shield Android TV General] jionny:
yes
[Shield Android TV General] jionny:
Hope everyone enjoyed, this download will no longer be hosted after tomorrow morning
[Shield Android TV General] Silenus21:
Hey do you have or can you host the 2015 16gb 6.1 dev image too?

I can't download from Nvidia anymore. Asking me to be a dev.
[Shield Android TV General] jionny:
Sorry I do not have that version
[Shield Android TV General] sammarbella:
I'll upload it to Mega in a couple of hours.
[Shield Android TV General] Silenus21:
Can I flash the normal 6.1 version over my dev rooted 6.0 through fastboot?

Or I should wait for the dev 6.1?

I already downloaded the normal 6.1.

It's getting kinda tiring having to manually flash dev versions everytime there is an update because it can't do ota and flashfire doesn't seem to flash it neither.
[Shield Android TV General] jionny:
Flashfire flashes it fine, look at all the other posts, I flashed with flashfire(make sure its version 0.73) with no problems you just click the + button then flash firmware and then leave everything but data clicked if you dont want to lose your data, all in all takes 5 min
[Shield Android TV General] sammarbella:
Why do you want to flash normal firmware on top of an already rooted one?

Non full OTAs can't be flashed over rooted firmwares.

I uploaded the 6.1 DEV firmware for

Shied TV 2015 16 GB

(nv-recovery-image-shield-atv-6.1.0-dev_rooted.zip) here:

https://mega.nz/#!VZ4FBB4L!gYWZadJ-zEjR4ShD7p9jPQX32kVdOlSq00YpL7Gebi4

You can flash this one over your rooted 6.0 Shield TV 2015 16 GB using FlashFire 0.73 as jionny explained.
[Shield Android TV General] jionny:
Developer image Nvidia Shield TV Pro 6.1

https://mega.nz/#!YGpU2SjJ!aQqOj8bqVfgiWAR_OeVWdCiqWpI6tc0sJ7SVoOQkDzc
[Shield Android TV General] iRushaad:
Hi, can anyone show me instruction to flash this? just received my first Nvidia Shield Pro :D
[Shield Android TV General] jionny:
download 6.1 developer image to your internal drive on the shield, download flashfire 0.73( search xda for it) open flashfire, hit the + button, click flash firmware, in flashfire everything should be clicked to flash except data, click flash and 5 minutes later you are good
[Shield Android TV General] dk1keith:
+1

worked great for my shield pro 2017. And for those that may be having problems with their shield like apps force closing etc. I also used this method but checked data to do a clean install of 6.1 and get rid of apps that may have been causing problems. Really made my shield run better and stopped all force closing of apps to include Leanback Launcher.
[Galaxy S I9000 General] (°_o):
Currently on hold due to working on Nougat first.

I've got a booting or should I say bootlooping build of Lineage 15.0 for I9000. (galaxysmtd)

I've had to use crazy hacks like adb binary from 7.1 in ramdisk.

Just to get `adb logcat` working.

For now it's stuck at bootlogo. I've attached the logcat here.

I'm looking into it to figure out what needs to be done.

Sources:

manifests and patches I've used.

https://github.com/galaxys1-resurrected/local_manifests

https://github.com/galaxys1-resurrected/android_patches

Kernel:

https://github.com/galaxys1-resurrected/android_kernel_samsung_aries

Device Tree:

https://github.com/galaxys1-resurrected/android_device_samsung_aries-common

https://github.com/galaxys1-resurrected/android_device_samsung_galaxysmtd

Thanks:

[MENTION=2222292]rINanDO[/MENTION] for backporting kernel side of things to 3.0

[MENTION=5414656]xc-racer99[/MENTION] and [MENTION=6794010]Coldwindofnowhere[/MENTION] for getting the device upto android 7.1

And all others who had worked from beginning till now on this device.
[Galaxy S I9000 General] a1shakes:
Is there anyone still working on this?

I was curious if anyone this was still being developed? I'm totally newbie in the android scene but have some knowledge of operating systems and am interested in resurrecting my i9000.

I went through the logs and a couple of things jumped out:

1) Surface flinger returning non zero exit status because it needs OpenGL ES v2.0 or greater. I believe i9000's GPU PowerVR SGX540 supports OpenGL ES 2.0, so this issue could be solved.

2) Media extractor crash: /system/bin/mediaextractor: libminijail[1291]: prctl(PR_SET_NO_NEW_PRIVS): Invalid argument, whatever the heck it means.

3) activity_recognition HAL is deprecated, so ActivityRecognitionHardware class's init does not do anything.

For 3 , I got to android_hardware_location_ActivityRecognitionHardware.cpp's source where it comments out activity_recognition.h with the following comment:

// #include <hardware/activity_recognition.h>
// The activity recognition HAL is being deprecated. This means -
// i) Android framework code shall not depend on activity recognition
// being provided through the activity_recognition.h interface.
// ii) activity recognition HAL will not be binderized as the other HALs.

I believe more work has been done since this post based on git commits lasting upto Nov'17. Would be great if someone could post logs for an updated build. I feel that android oreo with go optimizations would be a really good fit for i9000 and uphold this device's legendary support. I mean a device running from eclair all the way to oreo would be amazing.

Even if this might not work out, I would like to thank [MENTION=5916159](°_o)[/MENTION], [MENTION=5414656]xc-racer99[/MENTION] , [MENTION=6794010]Coldwindofnowhere[/MENTION] and [MENTION=2222292]rINanDO[/MENTION] for bringing i9000 upto nougat. I believe even i9000's nexus sibling nexus s does not have a working nougat rom.
[Galaxy S I9000 General] xc-racer99:
Unfortunately, no one is really actively working on Oreo. As you've found out, it's an issue with the graphics drivers that is holding everything back. No device (that I've found) that uses a PowerVR graphics chip (we use the PowerVR SGX 540) has working graphics drivers on Oreo. There were rumours that someone had found newer working blobs, but weren't able to release them publicly due to intellectual property laws that they were trying to figure out (but this was months ago).

Our GPU does support sufficient enough OpenGL, but only using BGRA8888 as opposed to RGBA8888. BGRA hasn't officially been supported in Android since ~4.2, but there's been a hack used to make things work. Come Oreo, things have changed and the hack no longer applies cleanly. However, I think the really issue is that the gralloc blobs was extended by PowerVR (see https://github.com/xc-racer99/andro...6.0/exynos3/s5pc110/include/hal_public.h#L119) but with the binderized HALs/VNDK/other low-level Oreo changes something has broken. I had a go at trying to work around things, but failed too.

There are a few ways I can think of getting working graphics:

1) Someone finds some updated blobs for the PowerVR SGX 540 for ARM (I've found x86 ones, but they don't work for obvious reasons)

2) Someone hacks around the source code so that the blobs work - but I'm not sure if it's PowerVR "extension" of the gralloc interface that is causing issues or not...

3) We simply use software rendering, but this would be so slow with our ancient CPU that I haven't bothered to try

4) We work on porting a newer kernel so we have the Samsung DRM kernel driver, use the Linux PowerVR blobs coupled with drm_gralloc/drm_hwcomposer and maybe a wrapper like https://github.com/TexasInstruments/dri3wsegl and somehow cobble together working support :)

In terms of the mediaextractor crash, that's due to the kernel missing seccomp support. There's a whole bunch of different backports, some more successful than others. Due to our ancient kernel, backporting is no longer very easy...

If we could somehow get the graphics drivers working, we'd have a pretty good base as there are free implementations of all HALs/drivers except for GPS and TV-Out (and, of course, graphics....).
[Galaxy S I9000 General] nailyk:
Are you really working on porting oreo on the i9000?

How do you deal with the small amount of ram?

Are you using the 'low end device' oreo feature?
[Galaxy S I9000 General] xc-racer99:
No, no one (that I know of) is actively working on Oreo for the first-gen Galaxy S devices. There were attempts, the kernel got in good enough shape that everything wasn't immediately crashing, but due to the graphics driver issues described a couple posts ago nobody has managed to get a fully booting build.
[Galaxy S I9000 General] nailyk:
Thanks for fast anwser. Yes, the graphic driver problem exist on another of my exynos device.

Anyway I wasn't able to boot the 7.1 (not able to boot something else than 2.3.6 :D)

Will attempt to see that post you are talking about but am probably not smart enough to deal with graphics drivers ;)

Thanks for your time.
[Galaxy S I9000 General] xc-racer99:
If you're serious about trying to mess with graphics drivers, it might be interesting to check out the blobs from https://www.renesas.com/pt-br/produ...ion-boards/renesas-starter-kit-for-rzg1e.html as it's an ARM-based device with the SGX540. It's possible that they're new enough to not run into the same issues as the older blobs (but equally possible that even the kernel part is closed source). The binary blobs are only semi-SoC specific as I've managed to use the OMAP blobs with only having hardware decoding being broken.
[Galaxy S I9000 General] alirezaamini11:
Is it for real???

I9000 !!:D
[Galaxy S I9000 General] MYEUHD:
Apparently, some new SGX540 and SGX544 DDK blobs for OMAP4 have appeared:

https://gerrit.unlegacy-android.org/#/c/Unlegacy-Android/proprietary_vendor_ti/+/10525/

https://gerrit.unlegacy-android.org/#/q/topic:omap-ddk-1.14+(status:open+OR+status:merged

In fact, (Barnes and Noble's) hummingburd and ovation are both based on SGX544 and have gotten an Oreo ROM (using the new blobs).

https://xdaforums.com/showpost.php?p=77526206&postcount=2490
[Galaxy S I9000 General] rusiu559:
Use android go it will be better.
[Galaxy S I9000 General] xc-racer99:
Yep, I've seen the blobs, they've been there for awhile now. Just haven't had a chance to run a build with the blobs to see if they work. It's on my to-do list when I find the time :)
[Galaxy S I9000 General] xc-racer99:
Alright, I've had a chance to look at the blobs now. I have a build, but unfortunately it looks as if we need to adjust our hwcomposer as well :( We use a relatively old hwc 1.0 but the new gralloc blob doesn't appear to keep the framebuffer open which is a requirement for a hwcomposer this old. There is a prebuilt blob that is used by omap4 devices but it doesn't work on s5pc110 due to the fact that it uses some DSS stuff which is OMAP-specific. Still plenty of work to do, without even trying to figure out all the Oreo/Pie changes (I'm testing on KitKat as that's the build environment I have setup right now).
[Galaxy S I9000 General] MYEUHD:
We need a newer hwc anyway, as Pie requires at least hwc 1.3:

As a reference, the galaxy S3's hwc was updated from 1.0 to 1.4: Thread

hardware/samsung
[Galaxy S I9000 General] xc-racer99:
Was unaware of the fact. Are you volunteering to make the patches? :D

I've uploaded my changes to https://github.com/xc-racer99/proprietary_vendor_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_hardware_samsung/tree/ddk-1.14 https://github.com/xc-racer99/android_kernel_samsung_aries/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd/tree/ddk-1.14 https://github.com/xc-racer99/android_device_samsung_aries-common/tree/ddk-1.14 but I think this might be the last I work on this as I don't really have the motivation to work on it anymore. Note the patches are against a custom version of Unlegacy Android 4.4 so you'll need to cherry pick the changes to your ROM of choice if desired.

The changes build, the EGL appears to initialize, but I always get

E/libEGL ( 471): validate_display:254 error 3008 (EGL_BAD_DISPLAY)

And in dmesg:

[ 8.509291] init: computing context for service '/system/vendor/bin/pvrsrvinit'
[ 8.509601] init: starting 'pvrsrvinit'
...
[ 8.601890] PVR_K: UM DDK-(4081762) and KM DDK-(4081762) match. [ OK ]
...
[ 8.765955] init: process 'pvrsrvinit', pid 99 exited
...
[ 55.560021] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.563491] PVR_K:(Error): PVRSyncIOCTLCreate: Failed to find unused fd (-24)
[ 55.597577] s3cfb s3cfb: [fb0] video memory released

Whether the issue is in the HWC or the gralloc blob that we've stolen from OMAP, I have no idea.
[Galaxy S I9000 General] MYEUHD:
Will try to do my best!

BTW, do I really need jdk-7 to compile kitkat? or does it simply work with jdk-8??
[Galaxy S I9000 General] xc-racer99:
You really do need jdk-7... I used the "reference implementation" available at http://jdk.java.net/java-se-ri/7 and made sure the java executables were in the PATH before the java I actually have installed.

Note that my Unlegacy Android trees will not work for the i9000 (well, they might, but you'd need to install u-boot as well at a bare minimum...)
[Galaxy S I9000 General] The_Pacific_gamer:
It's kinda Insane that people are trying to get an 8 year phone to run oreo
[Galaxy S I9000 General] MYEUHD:
[MENTION=5414656]xc-racer99[/MENTION] Do you still have the AOSP 7.1 source code on your computer?
[Galaxy S I9000 General] xc-racer99:
I've got the .repo folder, but don't have the individual files expanded as I don't have the disk space :D Could run a repo sync and look at things but don't have the disk space for a full build.
[Galaxy S I9000 General] darixtorento1:
its kinda insane that people are still using this phone.
[General Topics] JustusIV:
I am thinking of installing a sony explod MEX BT2500 in my ride so i can stream via bluetooth some audio. I have heard these head units have crappy sound but i can buy it for 110 bucks as opposed to some other brands available that are like 400. Does anyone have any opinion this or any other head unit i should buy?

thanks

JustusIV
[Sony Xperia XZ Premium Questions & Answers] baster72:
since update to oreo i have this message "apps running in the background" and i cant rid of it i try anything long press on it and switch off of any app who running in the background switch off in the app it self the only way to not showing it in "importance" put it on low that mean "no sound or visual interruption" but when i pull the statusbar its always there.

do everyone have this bug??please help :(
[Sony Xperia XZ Premium Questions & Answers] karrouma:
me to
[Sony Xperia XZ Premium Questions & Answers] denkem:
It is not bug, it is Oreo feature. You can get rid of it by downloading some apps, I am using AutoNotification. And here is a video: Youtube.

Dont forget to change "running in the background" for your language (I am using czech language so I had to write it in czech). Hope it helps.
[Sony Xperia XZ Premium Questions & Answers] Sebi673:
Yup, been using it for all the annoying status infos.

And for all of you lazy ones that only want that specific notification gone, there's actually an app for that haha. https://play.google.com/store/apps/details?id=com.iboalali.sysnotifsnooze
[Sony Xperia XZ Premium Questions & Answers] baster72:
ty very much it work finally it's gone :)
[Sony Xperia XZ Premium Questions & Answers] jaseman:
But why in the world do we need to install another stupid app, that will also be running in the background and using battery and other resources, to stop a stupid notification that we have apps running in the background using battery and other resources???? WHo lost their mind here and decided that this notification is a good idea??? Why can it not be toggled off if we do not want it??? I am getting really tired of the constant stupidity of Android!
[Galaxy S I9000 Q&A, Help & Troubleshooting] rhythm07:
Im not sure why but when starting phone, Samsung Logo shows white color then turns pink. See attached photos.

things I've tried so far:

-search through google but no one seems to have this issue, even the xda forums(if i overlook any thread my bad [emoji24] pls let me know)

-flashed other roms suchs as lineage, crom, omni, etc.

-restored my nandroid backup i think it was gingerbread

-tried the color thingy on accessibility it doesnt work

pls can anyone help me?! i dont wanna throw my i9000 [emoji30] [emoji22] [emoji24]

View attachment 4319206View attachment 4319207

View attachment 4319208View attachment 4319209View attachment 4319210
[Galaxy S I9000 Q&A, Help & Troubleshooting] rhythm07:
The only way I was able to fix this is by reverting back to stock rom gingerbread 2.3.6 jvu.

Im not sure why flashing custom roms put the screen back to pinkish/inverted color, so I decided to leave at stock rom 2.3.6 gingerbread jvu.
[Galaxy S I9000 Q&A, Help & Troubleshooting] (°_o):
I was playing with color setting and noticed pinkish screen happens when you totally remove the green channel..

So i guess it's issue with color format..
[LG L Bello Questions & Answers] davidwilson83:
Please view this thread in a browser or follow this link:

Moderator Contact List
[LG L Bello Guides, News, & Discussion] davidwilson83:
Please view this thread in a browser or follow this link:

Moderator Contact List
[LG L Bello Guides, News, & Discussion] davidwilson83:
Please view this thread in a browser or follow this link:

A message from the moderators - All users please read
[Xiaomi Redmi 3s Questions & Answers] tejjoshii:
I recently came across this bug. I noticed it when I tried to play injustice 2.

I don't exactly know when this problem originated but for about 2 weeks I am using different updates (Latest changed version) of ViperOS by dineshthangavel47.

Once I restart the phone the obb folder turns into a file with no extension and size is 0kb. It happens after about 10 minutes.

Then I have to restart the phone again to be able to do anything.

First I thought it might be happening because of the format of data partition changed to f2fs from ext4. So I formatted everything back to ext4. I clean flashed the latest version of rom too..

I use magisk zip for rooting.

Has anyone else faced this bug? :confused:

Any kind of help is appreciated. :)
[Xiaomi Redmi 3s Questions & Answers] wasimsiwan007:
Sm thing was happening with me when i tried to move obb data to folder.

U need to download obb frm game like 3,4 mb then rename ur old data to new data name nd move it obb.

It's worked for me