Related
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
Found this answer deep in a Jolla thread and it worked like a charm, so I thought I would bring it to light for anyone trying to enable/fix these features on their Nexus 5 running Sailfish OS:
All credit to @5pik3
Download the newest version on your Jolla device here: https://openrepos.net/content/basil/warehouse-sailfishos
Go to terminal (or dev SSH access)
Acquire root permissions with
Code:
devel-su
Type in the password from the developer options panel in the settings app
Now execute this code, line by line
Code:
ssu dr home
ssu dr adaptation0
zypper refresh
If you get a prompt here, type yes (you may have to do it 2 times)
Code:
pkcon install-local /home/nemo/Downloads/harbour-warehouse-[version].armv7hl.rpm
(Replace '[version]' with the version you are installing)
Code:
pkcon install store-client jolla-xt9 jolla-xt9-cp
And that is it! Jolla store should work, Warehouse should be installed, and after a reboot, you will have keyboard predictions!
OP:
5pik3 said:
If you want to install warehouse app download from here https://openrepos.net/content/basil/warehouse-sailfishos
Now open your terminal app or use the ssh access.
You need to have root permissions with 'devel-su'. Enter your password (the one in the developper options in the settings app).
Now you have to disable some repos : enter 'ssu dr home' and 'ssu dr adaptation0'.
Try a litle 'zypper refresh' and you will see no more authentication errors
And you can install the warehouse app with 'pkcon install-local /home/nemo/Downloads/harbour-warehouse-0.3-20.armv7hl.rpm'
And finally you type 'pkcon install store-client jolla-xt9 jolla-xt9-cp'
You can now have the keyboard prediction's and have both warehouse and jolla store to work
Click to expand...
Click to collapse
pkcon install store works fine on nexus 7 grouper but installing things from within the store gives an error to me
same issue with nexus7
Having same problem using sailfishos-grouper-release-1.0.8.19-alpha1.zip on nexus 7 grouper.
Any tips?
help
why i can't type the password on terminal??
chandradcp said:
why i can't type the password on terminal??
Click to expand...
Click to collapse
You are typing it in, it is just not showing up (this is a security feature for every linux distro). So, type the password in (even though it is not showing up) and hit enter, it will work.
vman411gamer said:
You are typing it in, it is just not showing up (this is a security feature for every linux distro). So, type the password in (even though it is not showing up) and hit enter, it will work.
Click to expand...
Click to collapse
thx... it works:good:
Fresh installs of Sailfish OS 2.0.5.6 give an error when running the final command.
Code:
[[email protected] Downloads]# pkcon install store-client jolla-xt9 jolla-xt9-cp
Command failed: This tool could not find any available package: could not find jolla-xt9
Any idea how to fix this?
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...
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
Having my favourite distro on my pocket is very exciting so thank you very much...
I have to carry only a development lamp server so using a pacman tip I revert to a base, base-devel system removing everything about xorg and DE.
Now I connect using ssh but I've noticed that the tablet screen is simply blank: no tty, no text console.
There is a way to have a text only console at boot to make a login (may be using an usb keyboard) when device is not connected?
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.
This is stackexchange issue I raised on this issue :
<a href="http://android.stackexchange.com/questions/171241/wifi-hotspot-timeout-setting-gone-in-nougat-7-0-7-1-but-timeout-has-not">
Wifi HotSpot timeout setting gone in Nougat 7.0 , 7.1, but timeout has not</a>; .
(answered only by myself).
I have observed, on receipt of my new AGM A8 QualComm 410 MSM8916 Android 7.0 phone , that the Wifi-HotSpot keeps timing out
after 2-5 mins . I am trying to connect my Linux 4.10 x86_64 host, using its iwlwifi driver, and wpa_supplicant + ISC dhclient, and it
does connect fine, for 2-3 minutes, but then the android phone (default DHCP router) stops responding to ping requests, and the
link is dead , until I bring the device down on the linux host & kill & respawn wpa_supplicant & dhclient . The script I use to do this
is attached. One weird thing is that even though the Android device stops responding to pings, it may still be passing pings through
to the WAN internet , so my script has to trying pinging an actual internet address like www.kernel.org (one of the few public IP
addresses left that respond to ICMP).
This is really nasty of Android Nougat, especially as the previous Android version I used on my old phone (4.2.2)
had a Wifi-HotSpot Timeout Options Settings dialog , which let you specify inactivity timeouts .
So I had to develop this complicated workaround where my 'network' init.d script does
PID_FILE=/run/wlan_ping_monitor.pid daemon /etc/init.d/wlan_ping_monitor.sh
which keeps the link alive.
I really need to root this phone, so I can install my own /etc/hosts file / ISC BIND9, fix this issue in /etc/default.hostapd.conf settings,
and maybe try to fix hostapd , & be able to view logs .
Any advice on how to create a custom recovery for this phone ? latest TWRP & CyanogenModROMs do not support it.
It looks similar to the WileyFox Swift , for which there is a lineageos 14.1 build . Should I try this ?
I am focusing on trying to build android & android_bootable_recovery and android_rooting_tools gitweb gits, & then build AOSP
& TWRP & a recovery ROM - any advice gratefully received.
This is linux kernel bug : https://bugzilla.kernel.org/show_bug.cgi?id=194931
and stackexchange issue: http://android.stackexchange.com/qu...ng-gone-in-nougat-7-0-7-1-but-timeout-has-not
The kernel could be responding better to the empty data frame sent by Nougat hostapd on ap_max_inactivity=300 timeout.
Also wpa_supplicant should be detecting the link has gone dead & re-initializing .
BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net
Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi
Hi retiredtab,
I ready to try this rom
Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).
@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.
I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi
Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.
Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.
Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.
The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.
I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi
@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.
bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.
@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.
Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.
Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L
bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.
Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.
Ooh i want really like to test!