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
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.
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
lakitu47 said:
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
Click to expand...
Click to collapse
I did it over adb yes, but on the newest release of fire OS (5.6)
wieli99 said:
I did it over adb yes, but on the newest release of fire OS (5.6)
Click to expand...
Click to collapse
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Sent from my Amazon KFGIWI using XDA Labs
lakitu47 said:
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Click to expand...
Click to collapse
It works for me in adb shell with
pm clear --user 0 com.amazon.kindle.kso
Well, I don't know if this will work with your exact tablet, but try this:
1. If you haven't already, get the Google Play store/services on your tablet
2. Download this app without the quotes: "https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en"
3. Follow on-screen instructions to grant tablet permission to edit secure settings (worked on 2 devices on 5.6)
BE CAREFUL WHAT YOU EDIT. If you change the wrong settings, your tablet can and probably bootloop or get bricked.
4. Go to the "secure" tab, scroll down to "limit_ad_tracking" and change value to 1
5. Go to "global" tab, scroll down to "LOCKSCREEN_AD_ENABLED" and change value to 0. Immediately reboot your device.
This was tested and worked on two HD 8 tablets on 5.6, with special offers manually disabled on 5.4. Since Amazon still thinks you are subscribed to special offers (ads), the notifications are hidden. This workaround actually makes the ads gone (hopefully), so the notifications will appear as soon as you turn on the screen, without a swipe down gesture.
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
do you have to have root for this? i did su and it said, " su not found."
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
Like that one eh? That was one of the first ones I found. Works without root too.
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
dondraper23 said:
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
Click to expand...
Click to collapse
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/hd8-hd10/help/root-required-completely-disable-enable-t3739257
I just had to do it again today because attempted to use Xposed and wound up getting in over my head and got caught in a bootloop, but at least I can reaffirm that this guide works
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
DragonFire1024 said:
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
I love all your posts- it's your guide I followed to disable the lockscreen. Unfortunately, Xposed is a bit much for a "noob" like me. I attempted to install it and got caught in a bootloop and had to do a factory reset. Considering what my dad uses it for, the negatives far outway the positives for me to bother with Xposed ever again
As you may noticed since last week google wants us, the custom rom users to manually register our android_id to the link https://www.google.com/android/uncertified/
It looks simple isn't it?
But there's a catch. Each google account can register up to 100 ids. So if you keep registering new ids after every clean install you'll more likely to hit that 100 ids limit soon. That's even worse for fhe rom developers as they may flash up to 20-30 roms a day.
I'm figuring out that in a different way though. The procedure I'm following is:
A. BEFORE ANYTHING
If you're doing this first time:
1) Copy this database from /data/data/com.google.android.gsf/databases/gservices.db
2.1) Open the database with a sql editor or from adb shell or a terminal emulator in sqlite3, see android_id with this sql command:
SELECT *
FROM main
WHERE name="android_id";
2.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "SELECT * FROM main WHERE name = \"android_id\";"'
3) Then save the value you're seeing to somewhere else, and register to your account at https://www.google.com/android/uncertified/
B. THEN FOR EVERY CLEAN INSTALL
1) Backups and wipes.
2) Flash rom (pt roms with vendors have the firmware included).
3) Flash gapps.
4) Optionally flash a custom kernel.
5) Reboot and configure your device.
6) Flash magisk, reboot.
THEN THIS PART IS IMPORTANT:
7.1) Again copy this database /data/data/com.google.android.gsf/databases/gservices.db and open in a sql editor (or with sqlite3 in terminal emulator, or adb shell) and execute this sql command:
UPDATE main
SET value=XXXXXXXXXXXXXXXXXXX
WHERE name="android_id";
7.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "UPDATE main SET value=XXXXXXXXXXXXXXXXXXX WHERE name = \"android_id\";"'
Note: XXXXXXXXXXXXXXXXXXX is your android_id as you've learned and registered to your account before (You can see the android_id s you've registered at the same google link).
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Deleted
Deleted
muff99 said:
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Click to expand...
Click to collapse
Yes that works too but this is the manual method for the gsf android_id. Wifi only devices doesn't have IMEI for example.
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
G4B33 said:
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
Click to expand...
Click to collapse
Yes so now we don't have to do that much of hacky-wacky stuff just to get gsf certified status anymore. #YayGoogle? ?
What if you don't do that?
seems not working. After rebooting, it went back to previous id
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
ccelik97 said:
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
Click to expand...
Click to collapse
I think the display will always stay on "not certified", but you are atill able to use the Google services (which unregistered custom ROM users are not any more, if I understood correctly).
This is just a guess on my side, I have not tested this (and I can't since I added all kinds of IDs to that registration page ...).
All in all the information flow from Google on this topic has been spectacularly bad, imho.
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
image45 said:
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
Click to expand...
Click to collapse
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
muff99 said:
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
Click to expand...
Click to collapse
Do I need to convert it or is that an accepted way to submit the information please?
If I try to resubmit it advises already registered.
Hello guys,
I recently built this setup to hold my nethunter:
Phone: Galaxy S7 Edge (exynos)
OS: LineageOS 14.1 (Nougat 7.1.2) UNOFFICIAL
Kernel: WirusMOD v14+svirusx
Compiled with the official nethunter installer tool for hero2lte-cm model.
Root: Magisk 21.4 > app v8.0.7
Everything seemed to be working fine, till I try initiating vncserver to test a GUI session.
Everytime i run KEX or vncserver by itself, it runs a session and causes a reboot just after creating a session.
Has anyone gone through that before?
Yep same here.... Can't find a solution anywhere.
Charlesincharg said:
Yep same here.... Can't find a solution anywhere.
Click to expand...
Click to collapse
It's such a weird behaviour, I did:
LineageOS nougat + kernel = vnc crash
LineageOS Pie + kernel = vnc crash
Currently on HavocOS + kernel and it is still crashing...
I'm not really sure if the pre installed vncserver came crashed or something or if it is a kernel behaviour.
I was thinking on rolling back to stock and trying it on stock, but I couldn't find a hero2lte stock on Android pie. I'll keep looking.
Everything else seems to be fine.
Here i got one solution. Hopefully will help your problem . I use tissot device with lineage os 17.1 and nethunter kernal from team-402.
I got same error with you. When setup and run under kex tab. My phone freeze and need to force reboot
This happen after i update and upgrade my nethunter system
ps: I not responsible if you bricked your own device. I here just to share with you what i discover to fix this problem
Fix:
-Open Root Manager that you use. Go to /data/local/nhsystem/kali-arm64/root/
-Delete ' .vnc' file in root directory or you can just remove from your terminal
-Open nethunter terminal. Run 'vncserver' and set up your password
-Open vnc app and just type 'localhost:5901'
-If you want open in other device, just type 'vncserver -localhost no'. And open vnc in other device. add new host and type 'nethuter ip:5901'
- to kill vnc server just type 'vncserver -kill'
# After almost 5 time try with defferent lineage os and methods. This one work for me.
33baleta said:
Hello guys,
I recently built this setup to hold my nethunter:
Phone: Galaxy S7 Edge (exynos)
OS: LineageOS 14.1 (Nougat 7.1.2) UNOFFICIAL
Kernel: WirusMOD v14+svirusx
Compiled with the official nethunter installer tool for hero2lte-cm model.
Root: Magisk 21.4 > app v8.0.7
Everything seemed to be working fine, till I try initiating vncserver to test a GUI session.
Everytime i run KEX or vncserver by itself, it runs a session and causes a reboot just after creating a session.
Has anyone gone through that before?
Click to expand...
Click to collapse
The error is related to tigervncserver install any other vnc server
Charlesincharg said:
Yep same here.... Can't find a solution anywhere.
Click to expand...
Click to collapse
The issue is regarding tigervncserver in the linux part install any other alternative
scriptkiddies123 said:
Here i got one solution. Hopefully will help your problem . I use tissot device with lineage os 17.1 and nethunter kernal from team-402.
I got same error with you. When setup and run under kex tab. My phone freeze and need to force reboot
This happen after i update and upgrade my nethunter system
ps: I not responsible if you bricked your own device. I here just to share with you what i discover to fix this problem
Fix:
-Open Root Manager that you use. Go to /data/local/nhsystem/kali-arm64/root/
-Delete ' .vnc' file in root directory or you can just remove from your terminal
-Open nethunter terminal. Run 'vncserver' and set up your password
-Open vnc app and just type 'localhost:5901'
-If you want open in other device, just type 'vncserver -localhost no'. And open vnc in other device. add new host and type 'nethuter ip:5901'
- to kill vnc server just type 'vncserver -kill'
# After almost 5 time try with defferent lineage os and methods. This one work for me.
Click to expand...
Click to collapse
Y did that aredy but issue is when you are using tigervncserver will test with other alternatives
scriptkiddies123 said:
Here i got one solution. Hopefully will help your problem . I use tissot device with lineage os 17.1 and nethunter kernal from team-402.
I got same error with you. When setup and run under kex tab. My phone freeze and need to force reboot
This happen after i update and upgrade my nethunter system
ps: I not responsible if you bricked your own device. I here just to share with you what i discover to fix this problem
Fix:
-Open Root Manager that you use. Go to /data/local/nhsystem/kali-arm64/root/
-Delete ' .vnc' file in root directory or you can just remove from your terminal
-Open nethunter terminal. Run 'vncserver' and set up your password
-Open vnc app and just type 'localhost:5901'
-If you want open in other device, just type 'vncserver -localhost no'. And open vnc in other device. add new host and type 'nethuter ip:5901'
- to kill vnc server just type 'vncserver -kill'
# After almost 5 time try with defferent lineage os and methods. This one work for me.
Click to expand...
Click to collapse
Has stopped the crashing issue for me now. My phone isn't restarting now.