yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] edp17:
Hi,

Thanks.

I've checked that on my device. I could only select the resolution but not the frame per sec. When I selected 1080p, it was a few seconds waiting, then the device played the whole video to the end without any lag.

I've also checked resolution 720p which was not a problem either.
[Galaxy Note 4 General] edp17:
OTA from 4.4.0.68 to 4.4.0.72 is ready

devel-su
mask the following:
systemctl-user mask voicecall-ui-prestart.service
systemctl-user mask mission-control-5.service
systemctl-user mask booster-silica-media@.service
systemctl-user mask voicecall-manager.service
reboot
devel-su
cp /usr/bin/droid/wifi.conf /usr/bin/droid/wifi.conf.backup
if installed, unapply and remove all patches
if installed, uninstall patchmanager
if used, ssu dr mousetracker
if used, ssu dr chum
if used, ssu dr sailfishos-chum
ssu release 4.4.0.72
ssu ar adaptation-common https://releases.jolla.com/releases/4.4.0.72/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.4.0.72/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.4.0.72/
ssu ur
zypper ref
zypper dup --details
vi /usr/lib/systemd/system/dsme.service
set PrivateNetwork=true to PrivateNetwork=false
vi /usr/lib/systemd/system/systemd-hostnamed.service
remove or comment out PrivateNetwork=true
cp /usr/bin/droid/wifi.conf.backup /usr/bin/droid/wifi.conf
unmask the following:
systemctl-user unmask voicecall-ui-prestart.service
systemctl-user unmask mission-control-5.service
systemctl-user unmask booster-silica-media@.service
systemctl-user unmask voicecall-manager.service
reboot
[Galaxy Note 4 General] edp17:
If you OTA update to 4.4.0.72 on or after 07/12/2022, the following steps aren't necessary:

vi /usr/lib/systemd/system/dsme.service
set PrivateNetwork=true to PrivateNetwork=false
vi /usr/lib/systemd/system/systemd-hostnamed.service
remove or comment out PrivateNetwork=true

These are fixed in packages, so no longer need to do the change manually.
[Galaxy Note 4 General] edp17:
OTA from 4.4.0.xx to 4.5.0.18 is ready

Here are the steps I followed and the commands I executed

devel-su
mask the following: (just in case any of these triggers a reboot in the middle of OTA update)
systemctl-user mask voicecall-ui-prestart.service
systemctl-user mask mission-control-5.service
systemctl-user mask booster-silica-media@.service
systemctl-user mask voicecall-manager.service
reboot
devel-su
if installed, unapply and remove all patches
if installed, uninstall patchmanager
if used, ssu dr mousetracker
if used, ssu dr chum
if used, ssu dr sailfishos-chum
ssu release 4.5.0.18
ssu ar adaptation-common https://releases.jolla.com/releases/4.5.0.18/jolla-hw/adaptation-common/armv7hl/
ssu ar adaptation-community-common https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.18/
ssu ar adaptation-community-treltexx https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.18/
ssu ur
zypper ref
zypper dup --details
unmask the following:
systemctl-user unmask voicecall-ui-prestart.service
systemctl-user unmask mission-control-5.service
systemctl-user unmask booster-silica-media@.service
systemctl-user unmask voicecall-manager.service
reboot
[Galaxy Note 4 General] edp17:
I've also updated the zip file int the first post if someone want to install fresh.
[Galaxy Note 4 General] edp17:
OTA from 4.5.0.18 to 4.5.0.19 is ready

Here are the steps I followed and the commands I executed

devel-su
mask the following: (just in case any of these triggers a reboot in the middle of OTA update)
systemctl-user mask voicecall-ui-prestart.service
systemctl-user mask mission-control-5.service
systemctl-user mask booster-silica-media@.service
systemctl-user mask voicecall-manager.service
reboot
devel-su
if installed, unapply and remove all patches
if installed, uninstall patchmanager
if used, ssu dr mousetracker
if used, ssu dr chum
if used, ssu dr sailfishos-chum
ssu release 4.5.0.19
double check whether these three repos are pointing to the 4.5.0.19 version:
ssu lr
adaptation-common should be https://releases.jolla.com/releases/4.5.0.19/jolla-hw/adaptation-common/armv7hl/
adaptation-community-common should be https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.19/
adaptation-community-treltexx should be https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.19/
ssu ur
zypper ref
zypper dup --details
unmask the following:
systemctl-user unmask voicecall-ui-prestart.service
systemctl-user unmask mission-control-5.service
systemctl-user unmask booster-silica-media@.service
systemctl-user unmask voicecall-manager.service
reboot
[Galaxy Note 4 General] steve-marinos:
Hello @edp17

Will this port work on the note 4 exynos 3g variant?

edit:

flashed the sfos on samsung galaxy note 4 sm-910h and so far everything seems to work well, minus i did not insert my sim card, and probably never will.

thank you for the port.
[Galaxy Note 4 General] edp17:
Hello,

I thought the port would work on all exynos variants. (Although,, couldn't prove it because I only had an SM-N910C. :) )

And now, you have just proven that the port works well on an SM-910H variant. This confirms my theory. :)

Thanks for that, congrats and enjoy Sailfish on your Note 4!
[Galaxy Note 4 General] steve-marinos:
Thank you for your hard work, yeah so far so good, need a bit of a learning curve, same like experiencing any new OS.
[Galaxy Note 4 General] edp17:
You can join the community on Telegram. (https://t.me/+KeJKDDA60uU2M2Q0)
[Galaxy Note 4 General] asinnerm3:
@edp17

waydroid is not running for me, not sure why, what info do you need so i can help you diagnose the issue, maybe uninstall and fresh install, then init again!

thank you.
[Galaxy Note 4 General] edp17:
I remember, into the vendor.img I had to add a few *.so files from the LOS17.1 android base. I am not sure whether the n910c and 910h variants are using the same hardware and whether their drivers are the same. Probably these differences are causing the issue you are having. I am pretty sure if you copy the necessary libraries from a LOS17.1 android base of 910h into the vendor.img, that would sort out this problem.
[Galaxy Note 4 General] asinnerm3:
Frankly speaking and after thanking you on providing excellent support, am not too familiar in digging in the vendor.img (wouldn't know what to look at) and got me thinking, since you had to add some stuff from the LOS 17.1 why not base SFOS on LOS 17.1?

I know zero knowledge on porting/building Os so please excuse my ignorance if my question seem so.

On the bright side seems my variant is an unlucky one, I tried to flash LOS 18.1 on it and the install complaint about the variant i have even though the porter clearly state that the sm-n910H is compatible, so am not sure how bad my variant is or maybe it is messed up from a previous flash even though each time am flashing something new am doing a full wipe except my microsd.

Hope you continue your port for the Note4, if my variant was LTE compatible i would have not hesitate to daily drive it on SFOS.
[Galaxy Note 4 General] edp17:
I understand what I said sounds a complex task. Especially for those are not experienced in Linux. Otherwise, it is a simple mounting an image file with read & write and then copying some files from an extracted source into it. (I admit, there could be complications like I had when I did it, so at the end it could turn into a more complex task than a copy/paste exercise.:) )

I also understand users prefer to use a 'Ready for daily driver' device where everything just works. I think community ports are experiments and for those who likes tinkering their device and using linux on a handheld device without any restrictions. And more importantly, SFOS helps you to keep your data and privacy safe from giants (Google, Facebook, etc.)

Back to your question why I didn't use Los17.1 as the base under SFOS.

When I started porting SFOS to this device, there was no Waydroid, so I've chosen an android base I was familiar with while I was porting SFOS for other devices. That's why I picked Los14.1.

Later, when Waydroid came into picture I've managed to make that work on this device with that old base. Ultimately Waydroid requires a Halium base which's very first version is based on android 9. So, it was a miracle that I could make it work on that Los14.1 base (which is android 7.1.2 and being far-far away from the required minimum android 9). :)

So, got Waydroid working but during the process also introduced some problems and I thought that's because of the old base. Therefore, started from scracth and I ported SFOS to the Note 4 again, but this time with androd 10 base (Los 17.1). I hoped those problems would be fixed on the new port, but unfortunately, all the problems remained. Therefore, I ditched that Los17.1 work and returned to the original 14.1. Luckily, since that time I've managed to fix almost all problems, so they were not at all related to the android base. :)
[Galaxy Note 4 General] edp17:
OTA from 4.5.0.18 to 4.5.0.21 is ready

Here are the steps I followed and the commands I executed

devel-su
mask the following: (just in case any of these triggers a reboot in the middle of OTA update)
systemctl-user mask voicecall-ui-prestart.service
systemctl-user mask mission-control-5.service
systemctl-user mask booster-silica-media@.service
systemctl-user mask voicecall-manager.service
reboot
devel-su
if installed, unapply and remove all patches
if installed, uninstall patchmanager
if used, ssu dr mousetracker
if used, ssu dr chum
if used, ssu dr sailfishos-chum
ssu release 4.5.0.21
double check whether these three repos are pointing to the 4.5.0.21 version:
ssu lr
adaptation-common should be https://releases.jolla.com/releases/4.5.0.21/jolla-hw/adaptation-common/armv7hl/
adaptation-community-common should be https://repo.merproject.org/obs/nemo:/testing:/hw:/common/sailfishos_4.5.0.21/
adaptation-community-treltexx should be https://repo.merproject.org/obs/nemo:/testing:/hw:/samsung:/treltexx/sailfishos_4.5.0.21/
ssu ur
zypper ref
zypper dup --details
unmask the following:
systemctl-user unmask voicecall-ui-prestart.service
systemctl-user unmask mission-control-5.service
systemctl-user unmask booster-silica-media@.service
systemctl-user unmask voicecall-manager.service
reboot
[Galaxy Note 4 General] anjarys:
Hi, do you have samsung's flashable default boot screen?
[Galaxy Note 4 General] edp17:
Hi,

No I haven't but I did have the original screens and param.bin, so I created an updater for you:

Note4-Original-Boot-Logo-Restorer-FIXED_by_edp17.zip

Please let me know if it worked.
[Galaxy Note 4 General] anjarys:
Thank you. Appreciate it.

Got this error on twrp, as attached.
[Galaxy Note 4 General] edp17:
Ops, I've forgotten to update the script name. Sorry.

This should work: Note4-Original-Boot-Logo-Restorer-FIXED_by_edp17.zip
[Galaxy Note 4 General] anjarys:
Wow its working, bro. You're a life saver.
[Galaxy Note 4 General] edp17:
I am glad it helped. :)
[Galaxy Note 4 General] edp17:
I couldn't fix the LXC problem on recent releases, so, I've decided to go back to SFOS4.2.

Some fixes (wifi, netlistener flod, etc.) were included in newer releases, therefore, I've included them into the hybris-hal for 4.2. So, if you'd like to go back to 4.2 but you want wifi fixed, please flash this hybris-boot image into /boot partition. (hybris-boot-sfos42-08-wd-fixes_usbmoded-wifi-netlistener.img)
[Galaxy Note 4 General] geek_1405:
Hi there, I was wondering if anyone would know if this also woks with the galaxy note edge since it's the same phone under the hood
[Galaxy Note 4 General] tigerpro357:
If it's anything like the snapdragon variants it will not, my UT port worked.fine on the Note 4 SD variants, but it didn't work on the edge
[Samsung Galaxy S10 5G Questions & Answers] elesbb:
Did the Odin update and I forgot to flash the BL (didn't really care because I have done this in the past without issues) but when it rebooted it was stuck at the Samsung Galaxy S10 5G screen without any signs of booting (20 mins).

Used vol dwn + power to turn it off. Then tried to use vol dwn + bixby + pwr to get back to download and to flash the BL this time, however, nothing happens. It will not power on nor boot to download..

This is the first time on any Galaxy device I have had this happen. I do not know if the kernel tried to patch the BL partition, or what. But, I have no life in the phone. It is currently at a repair shop but they aren't having issues either.

If I were to repair it myself, I would JTAG flash the BL partition to get be back to download mode then use Odin to flash the firmware again. However, the repair company does not have one. I may also try a jig that I have used before to see if that works (Concerned with using the wrong jig for the wrong phone if that is a thing.. i do not know). I also don't own a JTAG/Riff box.

I do not mind purchasing a JTAG/Riff box, but I need to have the proper files to flash with the JTAG/Riff box - does anyone know where to get these?

Or does anyone have this capability willing to do it for me for a reasonable price?
[Samsung Galaxy S10 5G Questions & Answers] 0x0null:
I have the same problem, a dead s10 5g
[Samsung Galaxy S10 5G Questions & Answers] 0x0null:
Did yo get a fix?
[Samsung Galaxy S10 5G Questions & Answers] elesbb:
Nope. I had to get a new device, but kept the old one for parts (good thing cause my screen broke ha)
[Fire TV Q&A, Help & Troubleshooting] glitchbit:
I suppose the easier thing would be to hook up an echo in my room and tie alexa with a specific tv. In lieu of that I have started on this journey so I will share what I have.

1. Use the following and find the right eventX

getevent -lt /dev/input/eventX

2. press buttons on your remote until you find it.

3. Change the following code to your eventX

adb shell sendevent /dev/input/event4 4 4 786977

adb shell sendevent /dev/input/event4 1 217 1

adb shell sendevent /dev/input/event4 0 0 0

adb shell sendevent /dev/input/event4 4 4 786977

adb shell sendevent /dev/input/event4 1 217 0

adb shell sendevent /dev/input/event4 0 0 0

4. Watch Alexa activate for the specific and official remote, but very briefly.

You can keep it open for longer by delaying the 2nd half 3rd command onward. The other issue is that the actual mic is not activating on the controller - this may be by design, but if you press the button on the controller itself then the mic activates. I am not sure if the mic can be activated remotely or not on the official remote or how we'd route a 3rd party controller's mic output to start pushing into the correct socket/api or wherever it needs to go. If anyone has any ideas please post them here.

What probably needs to happen is that I need to figure out how to intercept the 3rd party controllers audio channel when the user holds down the mic button and assuming it activates and can listen and then pipe that through to whatever the expected audio recording /dev/ interface is located at. If we can wrap all of that up in a single button then awesome, if not then maybe a dedicated Alexa button and a separate button for recording the audio and then you end it by letting up on the actual record button or by pressing the dedicated Alexa button again as it is simply a toggle.
[Fire TV Q&A, Help & Troubleshooting] glitchbit:
A possible method for probing the location of the mic's audio stream. If we find this and loopback a 3rd party mic to the same location instead I am wonder if we might not end up with a functional Alexa mic on just about any 3rd party remote?

https://www.commandlinefu.com/commands/view/350/output-your-microphone-to-a-remote-computers-speaker
[Moto E5 Questions & Answers] buggatti:
Hello

I am about to give a moto e5 phone to my employee and want to know can I block the factory reset option so the employee cannot factory reset the phone

Thanks.
[Redmi Note 8 Questions & Answers] mjrifath:
Hi Guys,

I need to understand which MIUI custom ROM is best and Playstore certified among below.

1. MIUI MIX

2. MIUI HELLAS

3. MASIK

4. Pls Suggest

which have more features and optimization.

Thank you
[Mogul, XV6800 ROM Development] Inescapbl:
Great and wonderful gurus...I think I dug myself into it. I was hoping my first post here would one with better news...but alas I am calling on your help.

I own a Telus P4000 (TITA100) and was keen on trying out dcd's new ROM. I did the following in the following order and now I have some unfortunate results.

1. Upgraded bootloader to 2.40 using USB instructions here:

http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome

2. Thought 'what the heck' and tried upgrading to bootloader 2.47 using the microSD instructions at the same address.

3. Upgraded the Radio to 3.42.50.

4. A reboot brought me to the Telus screen so I thought I had done something wrong.

5. I reverted back to Radio version 1.40

6. I reverted the bootloader to 2.07 using the instructions here: http://wiki.xda-developers.com/index.php?pagename=TitanStockHome

7. I reflashed the stock Telus ROM.

8. Results are now that I cannot make any outgoing calls or data connections

(automated voice says I need to activate my phone) and my power key does not turn the device back on once it goes into 'hibernate' mode.

I am really hoping someone can help me out. I've been searching for hours to find the original Radio (1.32) and the original bootloader (1.04) so I can put things back to the way they were but I can't find anything.

Any help is well appreciated,

Ry

PS - Update - I tried the other method of reverting back to stock (via USB) and now the bootloader is 1.04 and the Radio is 1.32. BIG Steps in the right direction....

Okay...so most of the issues seem to have been resolved and I'll call Telus to re-activate my phone tomorrow but there is one remaining question:

Did I do anything wrong here and how can I continue on my quest to give this another whirl?

(I debated not posting at all...but I figure my conundrums may help someone else later)
[Mogul, XV6800 ROM Development] Inescapbl:
Extra info

For you Telus users...found the last link...programming. I completely forgot about this and thank goodness I stumbled across this link thus making me feel completely stupid but nonetheless satisfied....

http://taiu.wordpress.com/2008/02/06/updating-my-telus-p4000/

I think I'm going to bed now...
[Mogul, XV6800 ROM Development] kareeem:
I'm glad you got it to work. I just had to mention that I thought your title was vey clever :D
[Mogul, XV6800 ROM Development] nitro66215:
Keep in mind, at least on Verizon, when upgrading your radio from a non-GPS radio to a GPS radio, the phone will require re-authentication. The A-Key will have to be given by your provider. When I called, I basically told them I had to do a hard reset. The tech on the other end said that every time I do a hard reset, I need a new A-key. NOT!(idiot)... :D
[Mogul, XV6800 ROM Development] scrawnyb:
Actually, I've only needed a new A-Key once, and that was when I hard reset my device. However, when I got my phone, I upgraded the stuff before activating.

So yes, hard-resetting does (sometimes/always?) causes you to need a new A-Key.

And even then, I didn't call in; I did the whole online "activate another phone, then reactivate the 6800" trick to avoid dealing with terrible CS
[Mogul, XV6800 ROM Development] cleanser:
I don't know if this A-key thing is true anymore. On my original phone I had to do an A-Key update twice. And both times was when I upgraded the Radio. After a while I stopped having to do them.

Yesterday I got a replacement 6800 (old one had bad charging port). I activated it got it working, and immediately put on SPL 2.47, radio 3.5.42 and DCD 3.2.5 (in that order)

I DID NOT have to call verizon for an A-key update.
[Mogul, XV6800 ROM Development] belgarionr:
Also take a look at some P4000 instructions I posted here.

http://www.howardforums.com/showthread.php?t=1413430&page=1&pp=15
[Mogul, XV6800 ROM Development] unL33T:
I have never had a problem flashing my P4000 except for when I used a Sprint ROM to get an updated radio and let the customizations run. This made it so that I could not send text messages but everything else worked fine.

Here's how I fixed it:

- used the relocker to relock the phone and restore the original bootloader

- flash with stock Telus ROM

- change to 2.40 bootloader

- flash radio (didn't use the Sprint ROM this time, used SD card method instead)

- flash DCD ROM

- run Telus carrier cab

Since then I have updated to 2.47 bootloader, updated to DCD3.2.5, went to a lower version of the radio because I was having signal issues, and then just recently went to the latest radio version. I haven't had any problems other than that one I just mentioned above.

Even when you flash with DCD's ROMs the Telus splash screen will still come up as this is not overwritten by the ROM. This will only change if you use a flasher to change it or flash with another carrier's ROM (like Sprint for example).
[Mogul, XV6800 ROM Development] Keystone:
Without a major scew-up, you should not have had to activate your phone on Telus after unlocking and a ROM update. I've never such an issue nor anyone else I know.

Inescabl, in all of those steps you failed to say when and where you upgraded to a third party ROM.... Within the first two I already see a point of concern where you stated you unlocked to 2.40 and then your next step being, ''what the heck' and tried upgrading to bootloader 2.47 using the microSD instructions. How did you get into the OS? Were you still on the stock radio and ROM?? You then stated that you flashed to the latest radio, but of course a reboot would only bring you to be stuck on the Telus screen if you'd not bothered to also flash to an appropriate ROM.

From what you've described, you decided to go a bit your own way, and did not pay close enough attention to the stated steps and problem solving that I wrote in the Wiki.

I'm glad that it all worked out for you, but this should be a warning to others to not rush into things without first being clear upon what the Wiki's guides and troubleshooting offer.