Frequently Asked Question - SFE devices

Frequently Asked Question - SFE devices - Sailfish General

Hi guys,
i've started a general Q&A thread for n4 and others. Everything related to sailfish and of course n4 can be posted here.
1. Which HW components are working?
A: take a look at the spreadsheet libhybris: https://wiki.merproject.org/wiki/Adaptations/libhybris
2. Can I run my android apps?
A: atm = no. due to licensing issues the dalvik runtime is not included in android ports. Join community efforts in this XDA thread. The jolla phone run android apps.
3. What about playing videos and music
A: new ports with gstreamer1.0 (Nexus 5) play MP3, MP4, H264 out-of-the-box.
Install gstreamer1.0-libav for more codecs.
For old gst0.10 ports:
MP3: install gst-fluendo-mp3-0.10.23-1.armv7hl.rpm via rpm -i fluendo
Video: Install gst streamer plugins and ultimate codec support. detailed instructions: http://forum.xda-developers.com/showpost.php?p=53552092&postcount=424
4. I'm able to install apps?
A: On Nexus 4 and Nexus 5 yes, soon on other devices too, always use Jolla Store for tested quality apps! Not there might still be scalability/stability issues on ported = non-official Sailfish OS devices.
As alternative and if you want to try many but NOT QUALITY-TESTED/POTENTIALLY DANGEROUS apps you can try Warehouse (openrepos.net):
* Navigate via your phone's browser to https://openrepos.net/content/basil/warehouse-sailfishos
* Download latest RPM
* In Terminal type `devel-su zypper in Downloads/harbour-warehouse*.rpm` and install
If you have Jolla Store also working on your ported device, you can install that app via UI instead of terminal:
* Ensure you have download at least one app from Jolla Store beforehand (which triggers `pkcon refresh`)
* Ensure Settings->System->Untrusted software is allowed
* Go to Settings->System->Transfers, click on downloaded file, and it will be installed
5. whatsapp?
A: Beware of WhatsApp temporary banning 3rd party app users. You can try WhatsUp: http://forum.xda-developers.com/showpost.php?p=60264278&postcount=137
Next Mitäkuuluu version is rumoured to be unbannable, lets all wayt
6. How to access the device?
A: Via ssh or sftp. Take a look on @Daycrawler thread: http://forum.xda-developers.com/jolla-sailfish/general/sailfish-android-devices-release-t2696409. He released the ea mail where everything is described.
7. How to install sailfish on my Android device ?
A: You will be able to install when an image is available. Check "Downloadable Image" column in https://wiki.merproject.org/wiki/Adaptations/libhybris .
Porting Sailfish OS by yourself is possible via following the HADK: https://sailfishos.org/hadk
For Nokia N9: http://wiki.maemo.org/Sailfish#Sailfish_Images
9. What about multirom?
A: MultiROM is supported on Nexus 4, Nexus 5, and OnePlus One (possibly Nexus 7 too)
10. Why I have to flash so much to get sailfish on my device?
mmmmmhhhh. Answer question by yourself and try
E.g. for Nexus 4 please do all steps you'll find in: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823 . It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't.
11. How to take a screenshot?
A1: Install screenshot app by lbt, from Jolla Store.
A2: do `zypper in lipstick-qt5-tools lipstick-qt5-tools-ui` - iconless Screenshot app will be among the App Grid
A3: This can be done on the phone via terminal and also on a remote SSH PC client.
grabscreen /home/nemo/Pictures/Test.png
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
The picture can be accessed in the Gallery or via a file manager (question #17 below).
12. How to get files from/to device, if USB Mass Storage mode or SD card are not available ?
A1: ssh + scp combo (windows[putty] & linux)
This combo is a set of linux standard tools. You can connect to the phone via secure socket shell from your pc and transfer files to your phone and vice versa.
A2: sftp + filezilla (windows & linux)
You can access the files via filezilla. You can transfer files like you're doing with an ftp server.
A3: Gnome Desktop Environment
The gnome filemanager nautilus has an build in option for accessing sftp / ssh servers or devices easily.
A4: WinSCP (windows)
To connect via these methods, enable developer mode, set a new password and take a look what ip you've get. Behind the wlan symbol. Then choose one of the above methods:
username = nemo
password = the one you entered in developer mode section
[ssh]= ssh [email protected]_ip
[filezilla] = sftp://device_ip
[nautilus] = select: Connect to server (on the left side) and enter: ssh://device_ip
13. How can I use the Backup app when there's no (working) SD Card?
A: Launch Settings->System->Backup to save all the settings you want to preserve
Perform
Code:
tar cf $HOME/backup.tar -C $HOME .vault
scp backup.tar onto your PC (other ways of how pull files, see FAQ #12 above)
Install new Sailfish OS.zip, put the tarball back onto device (say at $HOME), then perform:
HTML:
cd $HOME && tar xpf backup.tar
Go to Settings->System->Backup and restore your content from a chosen backup
14. How can I provide another radio.img only for Sailfish OS?
Put radio.img onto Sailfish OS rootfs somewhere safe.
Edit /lib/systemd/system/firmware.mount and replace "What=/dev/mmcblk0p1" with "What=/path/to/firmware.img"
Be careful with that and always do backup (i.e. comment the first What out )
15. How can I skip tutorial?
On first screen, tap on corners in sequence: top-left, top-right, bottom-right, bottom-left
16. How can I mount android's virtual sdcard partition (Nexus4,5) with all my goodies?
Try:
Code:
devel-su
mkdir /android
mount /dev/mmcblk0p28 /android
# virtual sdcard content is then available in /android/media/0/
# enable nemo user to read/write the contents (use file manager for those):
usermod -aG media_rw nemo
# And for media to be tracked:
ln -s /android/media/0/DCIM /home/nemo/Pictures/Android
ln -s /android/media/0/Music /home/nemo/Music/Android
ln -s /android/media/0/Movies /home/nemo/Videos/Android
# To make this permanent, update your /etc/fstab file by adding the following line at the end:
/dev/mmcblk0p28 /android ext4 rw,relatime,data 0 0
17. Filemanager?
Install File Browser by Kari from Jolla Store.
For root access add on https://openrepos.net/content/schturman/startasroot-file-browser (See question #4 on how to access openrepos via Warehouse app)
18. OTA?
Over-the-air updates are not straightforwardly supported (it's possible to hack around via ssu release 1.x.y.z and version --dup commands but not been tested and breakages might happen).
Just do backup and restore via a backed up file (question #13), and reflash new .zip (which will overwrite the whole Sailfish OS partition), then restore backup
--
This thread should be a collection for sailfish on devices and I will update frequently if news or tipps & tricks are available.

Reserved

Sorry if I'm asking in a wrong thread.but this information was missing from QA.
Are there any information about android apps running in ART instead of Dalvik on Nexus4, or even on Jolla?

Morderen said:
Sorry if I'm asking in a wrong thread.but this information was missing from QA.
Are there any information about android apps running in ART instead of Dalvik on Nexus4, or even on Jolla?
Click to expand...
Click to collapse
on jolla art isn't available or usable. Almost every app is running under art.Titanium Backup, Whatsapp and a hand full of other was critical. But they updatet theire apps and everything is working fine.

carepack said:
Hi guys,
No. Please do all steps you'll find in the ea mail. It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't. You will get this by flashing the google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
After this you have to flash a clean base. That's why you have to flash cm_10.1.3: http://get.cm/get/aWH
Now you've done the preperations and can flash sailfish.
Click to expand...
Click to collapse
Its not important to flash the factory image for the Nexus 4. All you need to do is flash the Radio from the 4.2.2. which can be available as a flashable zip for TWRP Recovery. The radio is called 0.48 availabe in one of the xda threads.
Thats what I did flashed this zip after I flashed CM 10.1.3 and EA2 worked as a charm. For reference my Nexus 4 was already on 4.4.3

DeepPurple15X said:
Its not important to flash the factory image for the Nexus 4. All you need to do is flash the Radio from the 4.2.2. which can be available as a flashable zip for TWRP Recovery. The radio is called 0.48 availabe in one of the xda threads.
Thats what I did flashed this zip after I flashed CM 10.1.3 and EA2 worked as a charm. For reference my Nexus 4 was already on 4.4.3
Click to expand...
Click to collapse
you're right. You have the choice. The important part is the right baseband / radio. But to keep it user friendly reading and simple I only described this way.

Looks like the next update is early june.
https://together.jolla.com/question/43464/next-os-update-in-early-june/
from
http://forum.xda-developers.com/nexus-4/general/sailfish-os-progress-nexus-4-t2667622/page36

i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?

misal6666 said:
i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?
Click to expand...
Click to collapse
If you have a file manger, like cargo dock, look for your file in download folder, simply click on it and you're done.
First be sure to have enabled, in settings,->system->untrusted software, otherwise you won't be able to install.
Inviato dal mio iPad utilizzando Tapatalk

misal6666 said:
i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?
Click to expand...
Click to collapse
quote from first post. hope it helps
a.) Download warehouse from opnrepos.net: https://openrepos.net/content/basil/...use-sailfishos
transfer it to you're device and install it via: rpm -i package
After that you'll be able to install apps from openrepo
Click to expand...
Click to collapse

hello.
usually i dont use camera,gps and Bluetooth in my daily life, so can i say that every thing else in nexus 4 is working

Sobaro said:
hello.
usually i dont use camera,gps and Bluetooth in my daily life, so can i say that every thing else in nexus 4 is working
Click to expand...
Click to collapse
How is the call quality? I thought the volume was still rather low.

Darakian said:
How is the call quality? I thought the volume was still rather low.
Click to expand...
Click to collapse
Yes, it is very in version 5, let's hopes we will good in version 7..
Sent from my Nexus 4 using XDA Premium 4 mobile app

Would it work on Optimus G?

Darakian said:
How is the call quality? I thought the volume was still rather low.
Click to expand...
Click to collapse
mailyaseen said:
Yes, it is very in version 5, let's hopes we will good in version 7..
Click to expand...
Click to collapse
I messaged Stskeeps on #SailfishOS IRC channel, this is what he said.
wait for next update; it fixes all that and more.
we had a bug in float vs integer valeus
Click to expand...
Click to collapse
Here are the logs for that day.

DeepPurple15X said:
I messaged Stskeeps on #SailfishOS IRC channel, this is what he said.
Here are the logs for that day.
Click to expand...
Click to collapse
I don't see that particular message in the logs, but it's good to hear none the less

I found this thought it would be useful to share and maybe add to the list
How to take a Screenshot on the Nexus?
Code:
su-devel
grabscreen /home/nemo/Pictures/Test.png
This can be done on the phone via terminal and also on a remote SSH PC client.
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
The picture can be accessed in the Gallery or via Filetug.
Code:
sleep 5 && grabscreen /home/nemo/Pictures/Test.png

DeepPurple15X said:
I found this thought it would be useful to share and maybe add to the list
How to take a Screenshot on the Nexus?
Code:
su-devel
grabscreen /home/nemo/Pictures/Test.png
This can be done on the phone via terminal and also on a remote SSH PC client.
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
The picture can be accessed in the Gallery or via Filetug.
Code:
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
Click to expand...
Click to collapse
added to list! thx

updated the thread with new hints. ea3 is coming soon! The version is more fluidly on mako devices. The resulotion fits better the screen. Had problems with mitäkuuluu because can't open chats. Working codec support is now easier to activate. Have fun guys!

carepack said:
updated the thread with new hints. ea3 is coming soon! The version is more fluidly on mako devices. The resulotion fits better the screen. Had problems with mitäkuuluu because can't open chats. Working codec support is now easier to activate. Have fun guys!
Click to expand...
Click to collapse
For mitakuuluu u need to install location and positioning packages..
Install pkcon qt5-qtdeclarative-import-location
Install pkcon qt5-qtdeclarative-import-postioning
Sent from my Nexus 4 using XDA Premium 4 mobile app

Related

[unofficial][linux3.4][native][tarchive][multirom]ArchLinuxARM release for N7 2013

This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483

looks interesting will give it a crack and see how it goes

thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...

is there any way to rotate the screen as its really annoying having it in portrait all the time

Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation

Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?

Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!

hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work

daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!

updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!

computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me

It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.

castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?

Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )

Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something

castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working

Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...

Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?

Cool I will give it a try.

[Q&A] [ROM][29Jan][GNU/Linux] Sailfish OS (community port)

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
[ROM][29Jan][GNU/Linux] Sailfish OS (community port)
Click link here>> To jump to Development thread <<Click link here[/COLOR]
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
-----------------------------------------------------------------------------------------------
Hi guys,
i've started a general Q&A thread for n4 and others. Everything related to sailfish and of course n4 can be posted here.
1. Which HW components are working?
A: take a look at the spreadsheet libhybris: https://wiki.merproject.org/wiki/Adaptations/libhybris
2. Can I run my android apps?
A: atm = no. due to licensing issues the dalvik runtime is not included in android ports. Join community efforts in this XDA thread. The jolla phone run android apps.
3. What about playing videos and music
A: new ports with gstreamer1.0 (Nexus 5) play MP3, MP4, H264 out-of-box.
Install gstreamer1.0-libav for more codecs.
For old gst0.10 ports:
MP3: install gst-fluendo-mp3-0.10.23-1.armv7hl.rpm via rpm -i fluendo
Video: Install gst streamer plugins and ultimate codec support. detailed instructions: http://forum.xda-developers.com/showpost.php?p=53552092&postcount=424
4. I'm able to install apps?
A: On Nexus 4 and Nexus 5 yes. But expect glitches because Jolla Store is going under maintenance until Tablet comes out. Known issues:
* "Essential Apps from Jolla" is not visible. Find them one by one via Seach
* Newly added apps might not show up for SFE devices
Alternatively, try Warehouse (openrepos.net):
* Navigate via your phone's browser to https://openrepos.net/content/basil/warehouse-sailfishos
* Download latest RPM
* Either run devel-su pkcon refresh in terminal, or download at least one app from Jolla Store
* Ensure Settings->System->Untrusted software is allowed
* Go to Settings->System->Transfers, click on downloaded file, and it will be installed
5. whatsapp?
A: Beware of WhatsApp temporary banning 3rd party app users. You can try WhatsUp: http://forum.xda-developers.com/showpost.php?p=60264278&postcount=137
Next Mitäkuuluu version is rumoured to be unbannable, lets all wayt
6. How to access the device?
A: Via ssh or sftp. Take a look on @Daycrawler thread: http://forum.xda-developers.com/jolla-sailfish/general/sailfish-android-devices-release-t2696409. He released the ea mail where everything is described.
7. How to install sailfish on my device (other than n4)?
A: You will be able to install when an image is available. Check "Downloadable Image" column in https://wiki.merproject.org/wiki/Adaptations/libhybris .
Porting Sailfish OS by yourself is possible via following the HADK: https://sailfishos.org/hadk
For Nokia N9: http://wiki.maemo.org/Sailfish#Sailfish_Images
9. What about multirom?
A: MultiROM is supported on Nexus 4, Nexus 5, and OnePlus One (possible Nexus 7 too): Follow up: http://forum.xda-developers.com/jolla-sailfish/general/09-06-sailfishos-multirom-how-to-set-t2869096
10. Why I have to flash so much to get sailfish on my device?
mmmmmhhhh. Answer question by yourself and try
E.g. for Nexus 4 please do all steps you'll find in: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823 . It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't.
11. How to take a screenshot?
A: Install screenshot app by lbt, from Jolla Store.
A1: This can be done on the phone via terminal and also on a remote SSH PC client.
su-devel grabscreen /home/nemo/Pictures/Test.png
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
The picture can be accessed in the Gallery or via Filetug.
12. How to get files from/to device, because USB Mass Storage mode and SD card are not available ?
A1: ssh + scp combo (windows[putty] & linux)
This combo is a set of linux standard tools. You can connect to the phone via secure socket shell from your pc and transfer files to your phone and vice versa.
A2: sftp + filezilla (windows & linux)
You can access the files via filezilla. You can transfer files like you're doing with an ftp server.
A3: Gnome Desktop Environment
The gnome filemanager nautilus has an build in option for accessing sftp / ssh servers or devices easily.
A4: WinSCP (windows)
To connect via these methods, enable developer mode, set a new password and take a look what ip you've get. Behind the wlan symbol. Then choose one of the above methods:
username = nemo
password = the one you entered in developer mode section
[ssh]= ssh [email protected]_ip
[filezilla] = sftp://device_ip
[nautilus] = select: Connect to server (on the left side) and enter: ssh://device_ip
13. How can I use the Backup app when there's no (working) SD Card?
A: Launch Settings->System->Backup to save all the settings you want to preserve
Perform
Code:
tar cf $HOME/backup.tar -C $HOME .vault
scp backup.tar onto your PC (other ways of how pull files, see FAQ #12 above)
Install new Sailfish OS.zip, put the tarball back onto device (say at $HOME), then perform:
HTML:
cd $HOME && tar xpf backup.tar
Go to Settings->System->Backup and restore your content from a chosen backup
14. How can I provide another radio.img only for Sailfish OS?
Put radio.img onto Sailfish OS rootfs somewhere safe.
Edit /lib/systemd/system/firmware.mount and replace "What=/dev/mmcblk0p1" with "What=/path/to/firmware.img"
Be careful with that and always do backup (i.e. comment the first What out )
15. How can I skip tutorial?
On first screen, tap on corners in sequence: top-left, top-right, bottom-right, bottom-left
16. How can I mount android's virual sdcard partition (Nexus4,5) with all my goodies?
Try:
Code:
devel-su
mkdir /android
mount /dev/mmcblk0p28 /android
# User data is then available in /android/media/0/
# You can update your fstab file by adding the following line at the end:
/dev/mmcblk0p28 /android ext4 rw,relatime,data 0 0
# And for media to be tracked:
ln -s /android/media/0 /home/nemo/android_sdcard
17. Filemanager?
Install File Browser by Kari from Jolla Store.
For root access add on https://openrepos.net/content/schturman/startasroot-file-browser (See question #4 on how to access openrepos via Warehouse app)
This thread should be a collection for sailfish on devices and I will update frequently if news or tipps & tricks are available.
-----------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP

Arabic Keyboard
Is there a way to enable Arabic keyboard layout in SailfishOS?

Upgrade Sailfish
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al jolla-camera jolla-camera-settings sensorfw-qt5 qt5-qtsensors-plugin-sensorfw
[Fix problem with adaptation0 after upgrade]
[[email protected] ~]$ devel-su zypper al ssu ssu-network-proxy-plugin ssu-vendor-data-jolla
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Your Nexus 4 should now run Sailfish 1.1.2.16!]

Niyoru said:
Today I am upgraded my Nexus 4 to Sailfish OS 1.1.2.16 and I don't noticed any (new) bugs. I done upgrade on fresh install of Sailfish OS 1.1.1.27 from that thread.
Below I will write procedures to successfull upgrade Sailfish from 1.1.1.27 to 1.1.2.16.
[Procedure to add locks - without that camera will not work after upgrade]
[[email protected] ~]$ devel-su zypper al qt5-qtmultimedia-plugin-mediaservice-gstcamerabin jolla-camera jolla-camera-settings nemo-qtmultimedia-plugins-gstvideotexturebackend sensorfw-qt5
[Change release version to 1.1.2.16]
[[email protected] ~]$ devel-su ssu re 1.1.2.16
[Refresh package list and install updates]
[[email protected] ~]$ devel-su zypper refresh
[[email protected] ~]$ devel-su zypper update
[Accept updates and wait. After update restart your phone]
[Disable repository adaptation0]
[[email protected] ~]$ devel-su ssu dr adaptation0
[Refreshing package list]
[[email protected] ~]$ devel-su zypper refresh
[Your Nexus 4 should now run Sailfish 1.1.2.16!]
Click to expand...
Click to collapse
Thank you for your instruction.. I just have one problem...
I get the below error message when trying to refresh the repositories. Even after doing "zypper clean -a".
"Retrieving repository 'adaptation0' metadata ---------------------------------------------------------------------------------[-]
Timeout exceeded when accessing 'http ://repo.merproject.org/ obs/sailfishos: /testing: /hw:/mako/sailfish_latest_armv7hl/repodata /repomd.xml'."
I'm running sailfish OS with Multirom.
I hope you can help me.
Kind regards,
Edit: I know what the problem is. I have to authenticate but I don't have any credentials. Is there a way how I can register for that repository? Many thanks

That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.

Niyoru said:
That repository probably don't exist for 1.1.2.16.
Try use devel-su ssu rr adaptation0 and devel-su ssu dr adaptation0.
I will try to stop the repo adaptation0 on 1.1.1.27. If I do this I will write here how to fix this repository.
Edit. adaptation0 is a repository for packages like droid-hal, what comunicate with hardware. Now you have installed these packages and Sailfish will work without this repository avaible. However I will try to fix it.
Thanks for feedback.
Click to expand...
Click to collapse
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works

btrdossantos said:
No, Thank YOU!
I did the update as you proposed, but the UI is not the same as the sailfish 2.0 Hammerhead version. It's probably because of the missing adaptation0 repo and the fact the official images aren't out there, yet.
Thank you for looking at the problem and your time! Let me know if it works
Click to expand...
Click to collapse
This will not look like Sailfish 2.0, becouse this is not Sailfish 2.0. This is Sailfish 1.1.2.16, you can read more about that release on Sailfish Website. (Sorry for no links, but I can't put any into post, becouse I have less than 10 posts :c)

sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)

dimon2242 said:
sailfish-weather is not found in jolla app store.
When i can get rpm package with weather?)
Click to expand...
Click to collapse
If you upgraded Sailfish to 1.1.2.16, you can use command "devel-su zypper install sailfish-weather".
This work for me

Niyoru said:
If you upgraded your Sailfish to 1.1.2.16, you can use just "devel-su zypper install sailfish-weather".
This work for me
Click to expand...
Click to collapse
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(

dimon2242 said:
What is about mp3 codec?
After installing flurence and bad-extras i can't play music(
Click to expand...
Click to collapse
In my phone this one work well: d-h.st/nkS8

Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi

carepack said:
Hi all,
we're working on the next official community release. Great you're figured out how to update. But be aware. If a bigger patchset is applied to the kernel this method won't work. But maybe one of you can help us out with a little information if you have upgraded the way from first post. If you open the messages app and looking at the background what do you see? Are there little quarters or or little diamonds?
Thx in advance!
ahoi
Click to expand...
Click to collapse
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4

Browser is closed if i play online music or youtube video!
Hope, what this will be fixed in next update!)

Niyoru said:
Definitely little quarters. However I think screenshot can say everythink and I attach one.
Thank you for your interest in this update solution.
I hope that you will be able to make stable build for Nexus 4
Click to expand...
Click to collapse
We're doin' our best :fingers-crossed:! Hope you enjoy the beloved sailfishos and thank you for sharing the information about quarters or not!
ahoi

Bug - Untrusted software installation
I am now running on v1.1.2.16 based on the tutorial provided in the thread (thanks Niyoru) and would like to report a bug.
I went into Setting -> System -> Untrusted software
and enabled "Allow untrusted software" option in there. However, I can't install any .rpm files. When I go back into settings, the setting is disabled. Not sure if this is caused by the upgrade or is also a problem in v1.1.1.27 as well in the Nexus 4 port.
The workaround was to go into terminal, do a devel-su and typing in:
zypper in package.rpm
Hope this helps...
PS. Looking forward to this build having the "Sailfish OS Updates" working instead of a manual upgrade process. Happy sailing! :fingers-crossed:

Installing sailfish via multirom with over kitkat primary rom
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?

Updated to v1.1.4.28 and all seems fine thus far...
Looks like latest update is screen resolution aware.
Sent from my Note 2 using Tapatalk...

mikerog said:
Hi. ive read all the posts i can find. Any pointers
Running up to date multirom on nexus 4 v31
Kitkat primary (beanstalk)
Lollipop secondary (Tamasek)
Downgraded kitkat radio from .98 to .84 to allow me to install sailfish
Downloaded Cm 10.1.3 and sailfish 1.1.2.16 beta 4
Installed both using sailfish "add rom" multirom option
All i get is bootloop after choosing sailfish from multirom list. Get to "google" screen and then it reboots back to multirom selection , Cant get past Google
Checked md5s, tried 4 or 5 times now
reread threads etc
Am i missing anything obvious..??
Any suggestions?
Click to expand...
Click to collapse
You got to use cm10.1.3 as primary ROM, too.
ajack2001my said:
Updated to v1.1.4.28 and all seems and fine thus far...
Looks like latest update is screen resolution aware.
Click to expand...
Click to collapse
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards

keenofhiphop said:
Did you update via OTA? Does it work now?
Hello, I'm buying a N4 today and am happy to join the community. I love Sailfish OS.
Regards
Click to expand...
Click to collapse
Yes, I update OTA using a combination of ssu and zypper commands... I guess it also helps that my account allows me to use early release software.

VRTV Free for Cardboard 3.0 open beta

Hi XDA! I'm the developer of VRTV, a video player for Cardboard. I'm running an open beta of my latest release, and I was hoping I could get some feedback here. Hope this doesn't count as me spamming. The app is free, with a banner ad, but there is a paid version available.
Anyway, here's a small description of the news in 3.0 beta:
Big news:
Uses libVLC backend, with support for replacing the decoding library.
Regular 2D video player UI.
Configurable bluetooth controls.
Smaller news:
Support for 220/270 degree panoramas.
Audio track selection.
Guess video config from filename.
Setting for phones/headset in reverse landscape configuration.
Like MX Player, I've disabled support for DTS/AC3, but you can build and load your own libvlcjni.so from the libvlc source code if you are not under the jurisdiction of software patents. To get the correct version I recommend using the same source as I used to build the version that's distributed with the app. Link below.
The other big new thing in 3.0 is that I've implemented a simple "normal" video player UI, so ideally you would get by with VRTV for all your videos and can set it as the default video player. Something that's been bugging me with VRTV for a while (and with most other players I believe). Uncheck "VR Player" to use the regular player.
I use the beta functionality in the Play Store, so to join, click the appropriate link below to join the beta with your Google account, then find VRTV in the Play Store to update to the beta.
https://play.google.com/apps/testing/se.chai.vrtv.free
https://play.google.com/apps/testing/se.chai.vrtv (requires buying/owning the paid version)
Follow the link below to get the source code for libvlc used in VRTV. Let me know if you would be willing to help me test loading a self-built library!
https://github.com/svenhenrik/vlc_vrtv_1.7.x
Any feedback is valuable, and if you have the ability to provide logs for crashers I will love you forever! Especially Nougat seems to be a bit troublesome, and I don't have a device to test with myself.

Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
- What settings do I have to change to enable AC3/DTS?
- Do I need the Android SDK or just the libraries mentioned at https://wiki.videolan.org/AndroidCompile/?
So I will just do a
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
sudo apt-get install automake ant autopoint cmake build-essential libtool \ patch pkg-config protobuf-compiler ragel subversion unzip git
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
./compile.sh --release -l -a armeabi-v7a
Copy the new libvlcjni.so to data/app/se.chai.vrtv-1/lib
?
Thank you for your help.

OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).

ColinMacLaren said:
OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).
Click to expand...
Click to collapse
Hi, so sorry for not checking in here sooner to help. Did you manage to get it all to compile? Let me know if you have more questions, I'll check a little more often
I'll update the patch later today with the new contrib links. I really should upgrade VLC since they released a new version recently, I used the one that was released when I started adding support.
I'll add the part about needing NDK r10e to the instructions, thanks!

ColinMacLaren said:
- What settings do I have to change to enable AC3/DTS?
Click to expand...
Click to collapse
Missed this part. You basically want to revert my changes relating to the a52 library. These are the modifications I've made:
- Make sure to use the last tested SHA of VLC instead of the latest checkout, to get some stability in what VRTV is using.
- Disable GPL, and fix building without GPL libraries (all changes relating to -lmad and -lpostproc
- Disable a52, in both the vlc build script and in the ffmpeg config.
The latter two are mixed and spread over two commits unfortunately so you can't just revert them.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/39bfc574661484f3d6e6f4371c1582aec57dbe35
Here you need to remove the --disable-a52 lines and add back the linker flag -la52 that was removed.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/961142382010ef3bb74028163cd66e11244d139a
Remove the --disable-decoder lines the patch added to vlc/contrib/src/ffmpeg/rules.mak
I think I might have had to add --enable-a52 to the compile script to get it to pick up the changes when rebuilding, try that if it doesn't download the a52 contrib lib or doesn't link.
By the way, the latest beta supports reading zip:ed libvlcjni.so files (make sure it's the only file in the archive).

Also gave this a shot. The developer still hasn't updated the source with new links to libraries, but I managed to get it to build and load after some tinkering.
If anyone else wants AC3/DTS support but can't build it themselves, PM me, new account so I can't post links.

Where do I put the zipped library and what are the naming restrictions?

ColinMacLaren said:
Where do I put the zipped library and what are the naming restrictions?
Click to expand...
Click to collapse
Haven't tried zip, but if you pick "load library" in the menu in VRTV you get a file browser so just put the file anywhere on the phone.

Instructions
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
Using;
Note 5 -Samsung Gear VR, streaming videos from Local NAS

sounds cool. will give it a try

Cool. Will give it a try

[WIP] Docker Build Steps
This isn't working but I thought I'd post anyone, I will edit when I figure out what I'm missing.
If you already have a build environment setup these steps may or may not be helpful, but here's what I did to build the library file with docker:
Code:
# Grab a docker image that's has the NDK and SDK install for you
docker pull dbndev/android-ndk-r12b-build-samples
# Grab the source for building VRTV's VLC Lib, and checkout the version before any changes were made
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
cd vlc_vrtv_1.7.x
git checkout 58181046e79112450a3362df7195cc35dd332096
# EDIT compile.sh, otherwise gradle don't download, the url changed, and redirect isn't caught. Note change xxxx to http, I can't post links with my account
# ORG: GRADLE_URL=xxxx://services.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
# NEW: GRADLE_URL=xxxx://downloads.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
docker run -it --rm -v $(pwd):/build_vlc -w /build_vlc dbndev/android-ndk-r12b-build-samples bash
# Install needed tools and setup the environment for building
apt-get update
apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
apt-get install automake ant autopoint cmake build-essential libtool patch pkg-config protobuf-compiler ragel subversion unzip git
export ANDROID_SDK=/opt/android-sdk-linux
export ANDROID_NDK=/opt/android-ndk-r12b
echo "r10 (64-bit)" > $ANDROID_NDK/RELEASE.TXT
./compile.sh --release -l -a armeabi-v7a
exit
There should now be a libvlcjni.so around xKB in the root of the vlc_vrtv_1.7.x directory, copy to android and enjoy audio!
Here's the error I'm having now, it looks like I'm trying to build a 32bit library on a 64bit OS, and looks like I need to set some other envs to get past this.
Code:
configure: error: in `/build_vlc/vlc/contrib/contrib-android-arm-linux-androideabi/fribidi':
configure: error: C compiler cannot create executables
See `config.log' for more details
../../contrib/src/fribidi/rules.mak:26: recipe for target '.fribidi' failed
make: *** [.fribidi] Error 77
contribs: make failed
Getting the same thing on mac when trying the following. Hope someone know's how to fix this issue.
Code:
------ NATIVE MAC ------
Download Android studio
Configure / SDK Manager / SDK Tools / NDK
Open the vlc_vrtv_1.7.x folder (maybe not needed who knows...)
echo "r10 (64-bit)" > $HOME/Library/Android/sdk/ndk-bundle/RELEASE.TXT
brew install automake ant cmake libtool patchutils pkg-config protobuf ragel subversion
ANDROID_SDK=$HOME/Library/Android/sdk ANDROID_NDK=$HOME/Library/Android/sdk/ndk-bundle ./compile.sh --release -l -a armeabi-v7a

Hi.
Also using the paid version and I really like the app, it's the best yet!
Two things I'd like to see and it would be even better:
1. support for web streams. Youtube, vimeo, etc.
2. automatic switch off for locked view when browsing your videos in app. It's impossible to click on the X when the image follows your head.
- Mik

Version 3.2 beta / vc61
Not sure what happened since last update, but the back button does not exit from VRTV back to anymore. The only way to exit player is through VR mode and clicking on the small X on top left side.
Also, Gear VR controls don't seem to work anymore.
Also there is a serious drift now.
Future function; a way to save settings or backup settings. I lost my config of my gamepad controls and can't get them back.
---------- Post added at 11:50 AM ---------- Previous post was at 11:37 AM ----------
ColinMacLaren said:
Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
Click to expand...
Click to collapse
An actual 64bit Android support would be cool, not sure if it would be needed if Hardware support works... just an idea that was triggered from above.

Hi. I am just a noob in this, but please help me. I love VRTV player, but I can't
in VR mode in cinema choose another video to play. Have to pull off my phone, go to another movie tapping it, then pull phone back and watch. very uncomfortable.

Wilsonb said:
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
Using;
Note 5 -Samsung Gear VR, streaming videos from Local NAS
Click to expand...
Click to collapse
Hi, can you explain how did you install VLC coded? Thanks.

--- deleted by user ---
Reason. This has been answered in the very first post of this thread.

I have a nexus 5X and I can't find a good setup to have a quality like in another app.
Trying to play with shader and opengl 3.0 or Vertex hq, but I can't reproduce a good image quality.
What do you suggest ?
Envoyé de mon Nexus 5X en utilisant Tapatalk

Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks

Wilsonb said:
Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks
Click to expand...
Click to collapse
What is your rendering settings plz ?
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk

[Guide] How to Enable Miracast for Pixel

Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.

Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel

jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.

sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).

jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.

Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.

Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs

spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.

Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin

Someone tries on Pixel 3? Thanks

It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !

this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....

marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?

EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.

marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!

OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.

Android 11- OneUI 3.0 (Beta 1,2 & 3) - Manual Update/SideLoad (N986U & N986U1) - [Guide]

********** ANNOUNCEMENT - Beta Enrollment without Banner (OPEN NOW - Nov 16,17) - Read More Here
INTRODUCTION - Hello all. Now Samsung wants us to go to Members app and keep looking for banner to sign up for Android 11, One UI 3 Beta . It went live October 27th, 10:20 PM EST, As fate would have it, i went to sleep early, i missed it and the banner refused to show up for me in the morning. Download was only showing up for people with unlocked variants on ATID firmware.
DISCLAIMER / NOTICE - Flashing is always risky. I am not responsible for anything that may happen to your device including but not limited to it turning against you, making you its slave and sucking you into the Matrix.
This post is a collection of wisdom, research and hard work of many people over many years across many forums and not just XDA. I will try to credit and link to their original posts.
TIP -Keep in Notice -This SHALL NOT Factory Reset Your Device or Format Data, it is still a good idea to Take Back Up - Just a Suggestion - Always have a latest Back Up
******** UPDATE - It seems ATT devices are getting wiped now if its CSC or the Sim remains to be tested.
i don't have ATT hence cant verify but in case you have an Unlocked device (N986U1) with ATT sim, then, removing sim and Changing the CSC to XAA/XAA/XAA before sideloading Beta is advisable.
PROBLEM STATEMENT - Missed the One UI 3.0, Android 11, Beta Sign up Banner in Members app or got the banner but didn't get the download and I really want it NOW.
Not sure if you want it now? - Find the BETA CHANGELOG HERE
GRAB YOURSELF A COFFEE / DRINK, because depending on where you at and how fast you/your internet speeds/your Machine is this may take anywhere between 7 to 45 MinsSOLUTION -
1. Pre-Requisites - Make sure Following Conditions are met before you start
You need a PC/Laptop along with your phone and USB Cable.
You need ADB installed, you can use ADB on Linux too - NOTE If your ADB Tools are not working, download my ADB Folder called platform-tools. Then extract it somewhere easy to remember/ find, like desktop
Remember the Location of the folder where you have ADB installed / Location of platform-tools- This is the location containing adb.exe file.
You may or may not need ADB/USB Drivers if any errors in ADB please Download Drivers from here and Install on your PC.
This following one step is relevant Only for flashing Beta 1
Use Odin to Flash Unlocked (SM-N986U1) ATID Firmware if you are not on that. Refer this thread to get your Firmware.
For changing Firmware from N986U to N986U1 and / or GUIDE TO FLASHING USING ODIN Refer This thread
______________________________________________________________________________________________________________________________________________________________
2. Now Download the relevant Beta File that you intend to flash - note that to Sideload Beta 2 you need to be on Beta 1 first. Mandotory Sequence = Beta 1>>Beta 2>>Beta 3 There is no skipping versions possible here.
BETA 1 (ZTGJ) Get the Beta1.zip file from here Thanks to @thatotherguy.. for the original zip.
BETA 2 (ZTK1) Get the Beta2.zip file from here
BETA 3 (ZTK9) Get the Beta3.zip file from here
______________________________________________________________________________________________________________________________________________________________
*************** Apply Update from SD card failed for me (Feel free to try that ) but here we will be using ADB Sideload Feature in Stock Recovery*************
HOW TO - Using ADB Sideload - Windows -The Process is Similar for Linux too
1. Copy the downloaded zip file to the ADB Folder (From Pre-Requisite step). ADB Folder is the folder containing ADB.exe it might be named differently for you (The one i have posted is called platform-tools)
2. Open Command Prompt Window as Admin.
3. Type in
Code:
cd Copy-paste the location of your ADB folder here
4. Connect the phone to the PC using USB Cable and Unlock it. Go to Developer Options and Switch on USB Debugging.
To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu
5. On your PC Type in Command Prompt
Code:
adb devices
6. Give Permission that appears on your phone and PC - I check the box Always Allow, you should do the same.
7. Now type the following and the phone will reboot to recovery.
Code:
adb reboot recovery
8. Once you see recovery on your phone Use Volume Keys to scroll down to Apply Update from ADB and press Power Button.
9. Now on your PC, Type the following in Command Prompt; this is just to be sure, it should show the device name with Sideload next to it.
Code:
adb devices
10. Type
Code:
adb sideload Beta1.zip
For Beta 2 use adb sideload beta2.zip Similarly For Beta 3 use adb sideload beta3.zip. Use whatever you have named the zip file. Most people use update.zip. The commands here are for the attached files in this post and their naming convention.
11. Wait for it to finish and Done
2nd (Second) BETA Is Out- How To Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Second Beta should be flashed After Beta 1. Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 1st Beta. Download the 2nd Beta (ZTK1) Zip File to flash Here Thanks to @hayabusa1300cc for the FOTA Link.
3rd (Third) BETA Is Out- Nov 16, 2020 Do this if you are not able to Enroll for Beta and or don't see update to download even after Enrolling
Third Beta should be flashed After Beta 1>>Beta 2. Third Beta (ZTK9) can not be flashed unless you have Second Beta (ZTK1). Second Beta (ZTK1) can not be flashed unless you have Beta 1 (ZTJG).
To flash follow the same instructions as above only this time the prerequisite is you have to be on the 2nd Beta. Download the 3rd Beta (ZTK9) Zip File to flash Here
OPTIONAL THINGS TO DO POST UPDATE
If you want to enable RCS (In the Native SMS app) and Native Video calling (This feature is on Tmobile) have a look at this thread.
Check out this Guide Service Mode and CSC Guide/Enable LTE/5G Bands and Services/5G Low Band on U1 by @mellojosh
TROUBLESHOOTINGSome people might run into "cant read update.zip" error for that we need to make ADB Large address aware. Follow the Steps Here I use the Advanced mode as it shows the true false flags. - This wont happen if you use the ADB Tools provided by me above under the Pre-requisites section.
************** FOR FUTURE BETA OTA Questions / Bugs - Observations and some more info - Go Here ********Please dont ask questions without reading.
QUESTIONS, HELP & SUPPORT ?? - See if I am Online here on this Live Chat
If it helped HIT THAT THANKS BUTTON, what are you waiting for ? Cheers !!

Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)

I get "adb: failed to read command: No error"

ekerbuddyeker said:
Suggest you rename the title for which device it's for as it's not for every snapdragon (right?)
Click to expand...
Click to collapse
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.

d_ganggreen said:
I get "adb: failed to read command: No error"
Click to expand...
Click to collapse
Use a different USB Cable. A good quality one preferably. Also try changing USB port.

Can i install this on sm n 9860 version and does google pay and samsung pay beta work?

warriorvibhu said:
Use a different USB Cable. A good quality one preferably. Also try changing USB port.
Click to expand...
Click to collapse
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.

d_ganggreen said:
Hmm, still getting same. Tried 3 cables including the one that came with the phone and both usb ports on my computer.
Click to expand...
Click to collapse
Are you on ATID Firmware?

warriorvibhu said:
Are you on ATID Firmware?
Click to expand...
Click to collapse
I am, I odin flashed it a few weeks ago.

1gorelo said:
Can i install this on sm n 9860 version and does google pay and samsung pay beta work?
Click to expand...
Click to collapse
Too early in the morning to go out and test that. This is Beta and i have already encountered some bugs. So you have to be up for that.
Good Lock wont work, gesture navigation is buggy, you can not even apply wallpapers from the Galaxy Themes app.
Wallpaper Service on the other hand is greatly improved. Fingerprint sensor is much faster.

d_ganggreen said:
I am, I odin flashed it a few weeks ago.
Click to expand...
Click to collapse
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.

warriorvibhu said:
My friend there are so many reasons why that error can happen. Sometimes you might have to change the ADB version. I am attaching the platform-tools i used. Extract this zip inside folder on desktop and try. If that doesnt work you might need to update ADb/Samsung drivers. Let us know if this works.
Click to expand...
Click to collapse
Thank you! Whatever it was, that worked. I am able to get it running with your tools. I am running it now.

CHANGELOG - Android 11_OneUI 3 Beta
************ Notice: This changelog is compiled from various different resources online, verification of these features rests with the users **********
Code:
[COLOR="SeaGreen"][CENTER]BETA CHANGELOG[/CENTER][/COLOR]
[B]Home screen[/B]
– Touch and hold an app to add an associated widget
– Turn the screen off by double-tapping on an empty are of the Home screen. You can turn this on in Settings > Advanced features > Motion and gestures.
Lock screen
– Dynamic Lock screen now has more categories, and you can select more than one.
– Lock screen widgets are improved.
[B]Contacts, Phone and Call Background[/B]
– Added the ability to edit multiple linked contacts at one time.
– Added an option to help you quickly delete duplicate contacts.
– Enhanced the search experience.
– Extended the storage period of the Trash bin from 15 to 30 days.
– Added the ability to customize the call screen with your own pictures and videos.
[B]Messages[/B]
– Created a Trash bin to store recently deleted messages.
– Call & Text on other devices
– Added the ability to turn Call & text on other devices on or off with Bixby Routines.
[B]Calendar[/B]
– Events with the same start time are now shown together in month and agenda view.
– Reorganized options for adding and editing events.
– Improved layout for full screen alerts.
[B]Reminder[/B]
– Improved layout for full screen alerts
[B]Camera[/B]
– Improved auto-focus and auto exposure functionality and usability.
– Improved stabilization when taking pictures of the moon at high zoom levels.
[B]Photo editor[/B]
– Added the ability to revert edited pictures back to their original versions.
[B]Bixby Routine[/B]
– Grouped preset routines help you get started quickly and learn how to build your own routines easily.
– You can now see what actions are reversed when a routine ends.
– New conditions have been added, such as a specific start time, the disconnection of a Bluetooth device or Wi-Fi network, a call from a specific number, and more.
– New actions have been added, including talking to Bixby and accessibility actions.
– You can add a customized icon for each routine and add routines to the Lock screen for quick access.
[B]Digital wellbeing and Parental controls[/B]
– Added trends to your weekly report. You can see how your usage has changed since the previous week and check your usage time for each feature.
– Added phone usage time while driving to the weekly report.
– Added a lock screen widget so you can check your screen time without unlocking your phone.
– Added separate profiles for personal and work modes so you can track your screen time separately.
[B]Internet[/B]
– Added ability to block websites from redirecting you when you tap the Back button.
– Added warnings and blocking options for websites that shot too many pop-ups or notifications.
– Rearranged menus to make things easier to find.
– Added several new add-ons, including one that translates websites.
– Added option hide the status bar for a more immersive browsing experience.
– Increased maximum number of open tabs to 99.
– Added ability to lock and reorder tabs.
– Improved design for tab bar which is now supported on all devices.
– Ended support for Samsung Internet edge panel.
[B]Quick panel[/B]
– See your conversations and media more conveniently in their own sections when you swipe down from the top of the screen.
[B]AOD[/B]
– Always On Display widgets are improved.
[B]Accessibility[/B]
– Get quick access to the most important accessibility settings during device setup.
– Get recommended accessibility features based on what you use.
– Set the Accessibility shortcut more easily in settings.
– Sound detectors now work with your SmartThings devices such as TVs and lights to give you more visible alerts when the doorbell rings or a baby is crying.
[B]Samsung Keyboard[/B]
– You can find the keyboard in settings more easily under General management in Settings, and the settings have been reorganized to put the most important ones first.
Samsung DeX
– You can now connect to supported TVs wirelessly.
– New touchpad multi-gestures let you change screen zoom and font size more easily.
Feel free to add anything else that you observe.

warriorvibhu said:
Wohooo Fingers Crossed. Did it finish ?
Click to expand...
Click to collapse
Yes it did, running 3.0 beta now!

warriorvibhu said:
I flashed on an Unlocked one so there is no way for me to tell if this can be flashed on N986U since so many people have flashed Unlocked firmware on the U devices using Odin (One confirmed guy flashed unlocked firmware on Verizon locked device and got the Beta banner) hence i think this will work for all Snapdragon devices. Give it a try and see. Just that before you try this make sure you are on ATID firmware.
Click to expand...
Click to collapse
I'm on n9860 which is a snapdragon. I'm not sure if it's the same. Anyone want to try?

My US unlocked stuck at 16% when sideloading? Is it normal?

jianansong said:
My US unlocked stuck at 16% when sideloading? Is it normal?
Click to expand...
Click to collapse
Since how long ?
Which step are you at?

warriorvibhu said:
Since how long ?
Which step are you at? (See Pics)
Click to expand...
Click to collapse
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.

jianansong said:
On my phone, it shows "Verifying updte package..."
On the adb, it shows serving update.zip 16%.
It has been there for at least 20 minutes... Do I need to cancel and restart?
I used the uploaded adb and the first link for update.zip.
Click to expand...
Click to collapse
Yes thats too long Cancel and restart, It took me 97.5 seconds to verify the package.
Your ADB is fine dont change that. For firmware you can try using the second link from google drive. do you meet the criteria Unlocked and on ATID ?

warriorvibhu said:
Yes thats too long. do you meet the criteria Unlocked and on ATID ?
Click to expand...
Click to collapse
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------
jianansong said:
Yes, mine is us unlocked and it's on ATID. Do you know how I could cancel it?
Click to expand...
Click to collapse
At the command line, I clicked "control + C" and surprisingly the progress number starts moving again, and now I am at 53% and it's still going...

Database Users

welcome