yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] delaya73:
Check TWRP version.

All files Firmware download from a shared (like official) resource, not my.

Tell me what kind of phone you have? I will make a firmware mirror and give you a link.
[OnePlus 3 & 3T Cross Device Development] suolrihm:
TWRP is the latest 3.2.1-0 official release.

I use the regular OnePlus 3
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi.

Sailfish OS updated (my42), see first page.

- Use OBS

- Use Over-the-Air updates (OTA)
[OnePlus 3 & 3T Cross Device Development] Actura:
OBS? Is it Open Build Service?

Will try this again later. Finally we got OTA support!
[OnePlus 3 & 3T Cross Device Development] delaya73:
Yes.
[OnePlus 3 & 3T Cross Device Development] ASHU3003:
Can I know changlog?
[OnePlus 3 & 3T Cross Device Development] Actura:
That's the changelog

1. Using Open Build Service (OBS)

2. Added OTA Support
[OnePlus 3 & 3T Cross Device Development] ASHU3003:
Thanks
[OnePlus 3 & 3T Cross Device Development] cesanaboia:
Any way to run sailfish os and oreo in multirom?
[OnePlus 3 & 3T Cross Device Development] Actura:
Haven't experimented on that. Would be interested though as i am on omni8.1.

There is one tutorial on Mido sf os port thread for multirom, but maybe it won't work on our device. Dunno.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
I don't know it right, but oreo needs other firmeware files, than nougat. Sailfish OS uses Lineage OS 14.1 HAL and needs/uses the same firmware. I think, that is why multiboot with Lineage OS 14.1 is working and it won't work with Lineage OS 15.1.

---------- Post added at 10:14 AM ---------- Previous post was at 10:09 AM ----------

@delaya73: do you have some progress on "bt not working" research? That is something I am missing atm.
[OnePlus 3 & 3T Cross Device Development] cesanaboia:
Oreo multirom works with Sailfish Os on primary and NitrogenOS 1/8/2018 on secondary. Newer version of NOS won't boot.

----------------

Update: all versions of NitrogenOS works replacing boot.img from 1/8/2018 build to newer versions.

Download boot.img here , flash after NOS. https://mega.nz/#!41M1XL4L!3-Ky65JpoT0QE-elOk_XsqNMqADaTP2c8GDvpSVZdP0
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi all.

Report on the work done ;) (there was little time):

1. Doubletap working (after new build).

2. Vibration should work after a new build.

3. Bluetooth init command hci_qcomm_init see mac address, how to tie it with SFOS yet I do not know, reserch.

I can not make a new build. Something developers broke (at the moment, the dependencies of packages ...). I understand and wait...

While you do not need to update. I'll let you know when everything is ready.
[OnePlus 3 & 3T Cross Device Development] sttal00:
Great work, I've been waiting for this for a while.

Installed on my op3 with multirom and it works fine.

So far the detected problems on my part:

Bluetooth(wont work at all)

Vibration(even after the service restart it won't vibrate on calls)

Camera(shutter lags, app lags changing between camera modes, lags on start and stop recording)

Fingerprint(wont work at all)

I installed warehouse and storeman and both work.

Something that would be great after the bugs are fixed is SFdroid for this cm14.1.

The things i miss the most daily is bluetooth and fingerprint unlock(for the car) and something like Waze.

Could find client for twitter, instagram, feedly, and some others that i use daily.

The YTplayer doesn't show recomendations and lags on playback(dont know if it is rom related or a buggy app)
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi all.

Tested! (Working)

1. Doubletap +

2. Vibration +

At the weekend we are updated! ;)

!!! While you do not need to update. I'll let you know when everything is ready.

Will update: LOS (a lot of changes) and SFOS.
[OnePlus 3 & 3T Cross Device Development] PikkuKisuli:
Double boot for sailfish and android?

first of all thanks for this work of yours, i loved my old Jolla and its great to see that i can experience its software on my 3T now!

Im new to all this but your steps were easy to follow. However id like to install sailfish os as a secondary boot option, and i found this: https://xdaforums.com/crossdevice-d...ualboot-dualbootpatcher-simpler-dual-t3297414

I wondered what steps id need to do to make Sailfish work with that? is there any special steps id need to take/leave out?

i understand that this isnt problem or thing related to your work and if you dont want to address this its understandable.

thanks, PikkuKisuli
[OnePlus 3 & 3T Cross Device Development] sttal00:
Regarding multirom you have the instructions here https://xdaforums.com/general/help/howto-multirom-lineageos-14-1-t3730717

Also if you have doubts about which version of multirom to download (as the post can be a bit confusing) it is on the second post the version with the following line:"Update 08/07 by BitOBSessiOn"

The only step that I found misleading is when installing the SailfishOS (instructions on the beginning of this thread) if you have multirom be carefull not to format data(Step 5 and 6) as it may remove Multirom also. Please do back it up first because I don't know if it is strictly necessary to format it, but then again best case would be backup(at least /data/media) -> format(Step 5 and 6 of multirom) -> restore the backup from the pc. Remember to read others experience and keep sailfish as primary.
[OnePlus 3 & 3T Cross Device Development] Xpsp332:
Not boot for my device. Im clear cache,datasystem and change cache,data to ext4. Flash firmware/lineage and latest build sailifish OS reboot to system and boot loop for logo OnePlus why?
[OnePlus 3 & 3T Cross Device Development] delaya73:
Read the instruction, do everything in steps.

3. Wipe -> Advanced Wipe -> Select: Dalvik/ART Cache, Cache, Data, System.

Swipe to Wipe.

4. Select Cache into Advanced Wipe -> push Repair or Change File System -> push Change File System -> select EXT4 (if different). I.e. partition Cache format in ext4 fs.

5. Wipe -> Format Data -> write - yes -> Enter

6. Select Data into Advanced Wipe -> push Repair or Change File System -> push Change File System -> select EXT4. Format in ext4 fs.
[OnePlus 3 & 3T Cross Device Development] Nsdik:
Is this rom is bug free
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi all.

You can upgrade. ( version --dup)

1. Vibration working after restart service (research).

$ devel-su

# systemctl-user restart ngfd.service

2. Doubletap working

Instruction on/off doubletap (default disabled):

$ devel-su

# zypper in mce-tools

Having doubletap detection enabled can cause the device to have problems

with suspending.

Default to doubletap-wakeup=never.

Users can still opt-in via executing:

mcetool --set-doubletap-wakeup=proximity

link: https://github.com/mer-hybris/droid...7d03c29#diff-26ebed8329afb22089032eae5badd04d

3. LineageOS build later. First page I'll edit how the new IOS building will be ready. :)
[OnePlus 3 & 3T Cross Device Development] dr_root85:
Can it after update support android apps ?? :confused:
[OnePlus 3 & 3T Cross Device Development] Actura:
No.

Also, it is not mentioned in the change log.

Wait for the anbox development to mature.

[MENTION=5199715]delaya73[/MENTION]

Which one is the correct one,

Edit: okay, this is the one. Spasiba pal!

Default (Disabled)
[B]mcetool[/B] --set-doubletap-wakeup=never

Enable w/ proximity detection
[B]mcetool[/B] --set-doubletap-wakeup=proximity

No, don't use it as your daily driver if you can't live without android.
[OnePlus 3 & 3T Cross Device Development] delaya73:
Newer version of NOS won't boot - because install new kernel. I think so.

Right:

Default (Disabled)

mcetool --set-doubletap-wakeup=never

Enable w/ proximity detection

mcetool --set-doubletap-wakeup=proximity
[OnePlus 3 & 3T Cross Device Development] sfoslino:
If you have mcetool installed, you can do many other things (be careful).

Let the Phone show the clock if you put it out of your pocket or let your hand float over the proximity sensor type:

mcetool --set-low-power-mode=enabled

if you don't like it, set it back to disabled.
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
any update ? ota?
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi all.

Updated LineageOS.
[OnePlus 3 & 3T Cross Device Development] delaya73:
By bluetooth

MSM8996 BLUETOOTH/FM QCA6174A Bluetooth 4.1

hci_uart,

BOARD_HAS_QCA_BT_ROME,

Rome bt chip! :(

It will be necessary to patch bluez and rfkill.

Some information is, but its a little.

I do not see a ready solution.

links:

http://www.merproject.org/logs/#sailfishos-porters/#sailfishos-porters.2017-10-22.log.html

https://portland.source.codeaurora..../Automotive/3rdparty/fsl3-10/Release_1_12_23/

https://git.merproject.org/mgrover/bluez

At the moment bluetooth sees other devices, but it does not work correctly.
[OnePlus 3 & 3T Cross Device Development] weigeloveu:
could use android app now？
[OnePlus 3 & 3T Cross Device Development] Diddy0312:
Nooo :( in the Moment not..we must live without AndroidApps..it´s sad. Maybe "Anbox" is the future....... I love Sailfish OS but without AndroidApps ( OP3t) i don´t use it for Daily.

Let´s hope :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] syedyasin:
what is the status of anbox ? can we install anbox in sailfish ?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Currently in Alpha
[OnePlus 3 & 3T Cross Device Development] Diddy0312:
No, not in the Moment... but i think in future is this the best way!!

See this page it´s very interesting: https://anbox.io/

Greats...
[OnePlus 3 & 3T Cross Device Development] syedyasin:
yes, true..it's the future.. anbox is replacement of sfdroid.. but was trying to know the status, like we can start using it or not yet. just got to know that it is in alpha stage. we might need to wait some more time. we can stop using Android, but it will be very slow process.. like first we will stop android then slowly we will give up android apps.. because most of the people who use android, it's because of the app's.. let's hopes for the best, and stability of anbox.. :) :good:
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
any update ?
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hi all.

Now i rebuilding kernel (the new bluetooth stack). Not sure what will work!

On the new version, planned a transition to the next weekend.
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
thanks , kindly keep posting new updates even they are small one. :)
[OnePlus 3 & 3T Cross Device Development] Veestaai:
where's the latest download link(Of so many links in OP)
[OnePlus 3 & 3T Cross Device Development] delaya73:
link: lineage-14.1-20180227-UNOFFICIAL-oneplus3.zip (chapter 8) (Be sure to install. Diffirent from officiall LOS!)

md5: 01de803e8a65028bb91445533d2c5ff3

link: sailfishos-oneplus3-release-2.1.3.7-my42.zip (chapter 9)

md5: ab8193393653f159641850260fb79a1f
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
any update on vibration fix ?
[OnePlus 3 & 3T Cross Device Development] Waspoeder:
wow thanks m8 gonna test it this afternoon

i want to test a nice os for oneplus 3
[OnePlus 3 & 3T Cross Device Development] delaya73:
use fix

link: https://xdaforums.com/showpost.php?p=75373858&postcount=107
[OnePlus 3 & 3T Cross Device Development] Waspoeder:
The firmware zip for oneplus 3 is corrupted and i can’t install it

Anyone else has the same problem ?

Or has a noncorrupted zip file ?
[OnePlus 3 & 3T Cross Device Development] Veestaai:
any update on bluetooth fix?
[OnePlus 3 & 3T Cross Device Development] delaya73:
fix
[OnePlus 3 & 3T Cross Device Development] delaya73:
See irc channel on freenode.net #sailfishos-porters on date 21.03.2018 (history)

link: http://www.merproject.org/logs/#sailfishos-porters/#sailfishos-porters.2018-03-21.log.html

Until everything is bad.
[OnePlus 3 & 3T Cross Device Development] delaya73:
talk.maemo.org

See also talk on talk.maemo.org.

link: https://talk.maemo.org/showthread.php?t=100117
[OnePlus 3 & 3T Cross Device Development] delaya73:
Check MD5 sums!

Most likely the problem is in TWRP
[OnePlus 3 & 3T Cross Device Development] Waspoeder:
Silly me :)

Everything works great

Nice job man
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
Kindly Give update

this is not a permanent solution, kindly provide one update
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
the open beta for oneplus 3 you have provided is a corrupted 5kb file
[OnePlus 3 & 3T Cross Device Development] delaya73:
What specifically does not work?
[OnePlus 3 & 3T Cross Device Development] Waspoeder:
I had that same problem

But in the end i needed the 3t firmware
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
There are 3 total problems-

1. the oepn beta firmware file you have uploaded for oneplus 3 is of only 5kb and it is not working,so i downloaded it from another website.

2. In TWRP i was not able to send data via pc, so i had to use push command to send all files.

3. In this Sailfish OS there is no way you can install android apk or any android market. neither its store supports android support.
[OnePlus 3 & 3T Cross Device Development] suolrihm:
You can also use the Firware+Modem file by jamal (ExperienceOS) or extract them on your own, i had no issues with both ways.

Never had this because i always use adb push, sorry.

Already know but that's not really an issue because SailfishOS is simply not Android. If you want this Support on SFOS, wait or contribute to Anbox, which aims for Android App Support on SailfishOS Ports.
[OnePlus 3 & 3T Cross Device Development] dr.pythagora:
I have tried sailfish os with my nexus 5, several times.

Sailfish is nice os, but I dont think it is a daily device yet.

The problems are:

- poor battery life

- poor native apps, for example phone and contact apps are at very mediocre level

- fonts are ridiculously small; and there is not other choce

- multimedia apps are missing; whatsapp, viber, skype need native apps, not simulated from android because they will use battery too much.
[OnePlus 3 & 3T Cross Device Development] delaya73:
Update firmwares

Update firmwares.

OP3: Open Beta 22 firmware+modem to Open Beta 24 firmware+modem

See page one.

Not tested. Should work. :)
[OnePlus 3 & 3T Cross Device Development] sfoslino:
For the OP3 the Open Beta 24 is the last firmware for android 7 (nougat / los 14.1),

the Open Beta 25 is the first and Open Beta 32 is the newest for android 8 (oreo / los 15.1).

take a look: https://jamal2367.com/downloads/?dir=OnePlus 3/Firmware + Modems

I think I will stay with the one, that is recommended for lineageOS 14.1 official build: https://xdaforums.com/showpost.php?p=69535222&postcount=3

and wait until someone has testet the new versions.

Where comes your information from?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Last time i try'd SFOS, battery life was fine for me but on OP3. With Native Apps, i guess it depends on you. For example the Contact Apps. I want to see my contacts, not more not less. But maybe i miss understand what you mean. Font size is okay for me, but again that's a thing depending on you as a user. It's kinda sad that there there is still a lack of official, native apps like WhatsApp, sure but that's not the Problem of the OS, it's a problem for users and the should make noise so the devs can't overhear them. I used SFOS for several days and was pleased
[OnePlus 3 & 3T Cross Device Development] delaya73:
I just took the latest firmware.

I ask to give information (link) about the recommended firmware for LOS 14.1. I do not spend a lot of time on this.
[OnePlus 3 & 3T Cross Device Development] delaya73:
Thx. Fix it.

OP3: Open Beta 22 firmware+modem to Open Beta 24 firmware+modem

OP3T: Revert to Open Beta 19 firmware+modem

Where can I find information on OP3T last recommended firmware for LOS 14.1?
[OnePlus 3 & 3T Cross Device Development] breitseite85:
work salifish os as secondary rom with multirom?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
It seems to work, you can find more informations to it in this thread, but i wouldn't recommend you trying MultiRom if you also want to use a more recent (Android Oreo) ROM because of possible issues due to different Firmware+Modem versions
[OnePlus 3 & 3T Cross Device Development] sfoslino:
The same link, I posted already:

https://xdaforums.com/showpost.php?p=69535222&postcount=3

cite:

Latest Firmware files for oneplus3/oneplus3t -5.7.2017-

Make a nandroid backup before you proceed

Flash the following files using the latest official twrp to avoid any recovery related issues.

Make sure to do a clean flash if your rom requires an updated firmware.

Don't ever flash an oneplus3 firmware on oneplus3t or an oneplus3t firmware on oneplus3.

Oneplus3

...

2-Falsh OnePlus3_OpenBeta19-FIRMWARE+MODEM-flashable.zip.

...

Oneplus3t

...

2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.

...
[OnePlus 3 & 3T Cross Device Development] Diddy0312:
Oneplus3t

Instructions only for oneplus3t!

1-clean flash is recommended.

2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.

3-Flash the latest laos nightly

4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.

5-Wipe Dalvik/cache and reboot.[/QUOTE]

Heyyy....for me are the things for OP3t important.....you are saying under Point 4- optional:gapps arm64 7.1...........mean's this that we can have Goo** Play on SfOS??

I'm sry. if i understood this wrong??

Greats and Thank youuuu!!!!
[OnePlus 3 & 3T Cross Device Development] sfoslino:
No! I said nothing. I say: only flash the firmware file, recommended by OP.

It was a cite from the link I posted and should answer the question from delaya73 about the recommended firmware version for the official lineageOS. It was the description what to flash for the official lineageOS installation ONLY!

SFOS needs the unofficial lineageOS installion only to use the lineageOS drivers (HAL ). Read about libhybris.
[OnePlus 3 & 3T Cross Device Development] delaya73:
Sailfish OS ver. 2.1.4.14 (Lapuanjoki) (Not OBS)

Sailfish OS ver. 2.1.4.14 (Lapuanjoki) (Not OBS) (my58)

sailfishos-oneplus3-release-2.1.4.13-my58.zip

sailfishos-oneplus3-release-2.1.4.13-my58.zip.md5sum

Not OBS! Local build.

OBS version will be ready by the end of the week.

All early bugs are present.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
wow,very nice. Thank you.
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
thanks, changelog please, and what is OBS?
[Samsung Galaxy J1 Guides, News, & Discussion] DragonFire1024:
I have found a way to root the Samsung Galaxy J1 (SM-J100VPP, Verizon) without needing to flash modified, rooted firmware using ODIN. I do not know if this unlocks the bootloader. Maybe someone can reply with an answer.

1. Make sure ADB/USB debugging is turned on. Settings > about phone > tap on 'build number' seven times to enable developer options.

2. Tap back button once and tap developer options. Make sure the box next to 'USB Debugging' has a check mark.

3. Plug your phone into your PC and open up an ADB window.

4. Download and install the Hidden Menus APK attached to this post, located at the bottom of the thread. (If using ADB to install, place the APK in your ADB folder and open an ADB command window and type: adb install HiddenMenus.apk)

5. Open the Hidden Menus app and scroll until you see 'Rlz Debug UI' and tap on it.

6. Where it says 'OEM Mode', make sure 'on' is selected (tap the circle next to OEM Mode to turn it on).

7. Go to my Google Drive, download and install 'android_root.exe'. This will install an older version of KingoRoot onto your PC.

8. Open KingoRoot for PC and connect your phone to the PC.

9. At the very bottom, left corner of the KingoRoot for PC window, make sure to UNCHECK the box that says 'install recommended app'.

10. Click on root and let KingoRoot root your phone.

Replace KingoRoot with SuperSU

I don't like one-click-root apps. I don't trust them. So whenever possible, I try to find methods to install SuperSU. Below is a guide to replace KingoRoot with SuperSU. The method in this thread works and only consists of a few steps. First you'll need to go to the KingoRoot homepage and download the APK for Android and install it. Then follow the steps below:

1. Delete/Uninstall Kingouser, but keep Kingoroot. DON'T reboot your device

3. Install SuperSU apk from flashable zip v2.79 (APK provided by me, attached at the bottom of this thread).

4. Launch it, press "continue" and "normal" wait until the update is successful. (You might have to close the SuperSU app and reopen it to complete this step).

5. Reboot and uninstall Kingoroot.

Thanks everyone. I really love this little phone!
[Samsung Galaxy J1 Guides, News, & Discussion] mofugggz:
ok, so all that has happened here IS. you happened to have a samsung galaxy j1 sm-j100vpp verizon prepaid phone that happened to NEVER be updated to the unpatchable 5.1.1 and you rooted the existing firmware that we all have to downgrade to, to be able to root. And to answer your question about the boot loader.... NO, flashing or MODIFYING the firmware has nothing to do with the boot partition.

BUT. the super su replacement has caught my eye and is how i found this post. I will check the work and report back. this would be a huge step forward in creating a 32 bit custom twrp as the chipset in this phone only supports 32 bit and is why twrp (cwm similar etc....) does not work on this device. i have noticed another samsung device that has "alot" of the same chipsets but still supports 64 bit and has a promising twrp I may be able to compile as a 32 bit only recovery img. after that. its smooth sailing.
[Eee Pad Transformer Q&A, Help & Troubleshooting] bruisah:
Hi folks,

I have a rooted TF101 that I've assigned a very important role - to act as a WiFi connected serial console to my Linux server (idea being that, if my server has no IP connectivity, I can still remotely access it by connecting through my TF101).

The set up is pretty simple:

- Rooted TF101 (KatKiss 5.1.1_030c) with keyboard dock :)

- Dropbear SSH daemon running (clean and tight bot of software!)

- Busybody (provides 'microcom' terminal emulation amongst other things)

- USB to RS232 Serial cable connecting to the serial port on my server

The TF101 is docked, and the USB->RS232 Serial cable is via the USB port in the keyboard dock.

It all works rather well - boot messages are streamed to the serial terminal as well as the standard Linux virtual one, and the boot process finishes with a login prompt on the serial terminal. Great!

The problem is this:

If the TF101 is *not* connected to the power supply, the keyboard Dock eventually goes to sleep, and the serial port is not available. The only way to wake it up, is to physically open the 'lid' and everything is available once again. Not exactly conducive to remote access!

This is not an issue if the TF101 is connected to the power supply, but I want to be able to switch the power supply on or off as needed in order to not ruin the batteries by having them constantly connected to the charger long-term (the easy method will be via a standard mains timer, but I'm also considering getting the TF101 to control the power supply and charge itself when the batteries drop below a set threshold)...

So, the question is: is there a method to wake the keyboard dock remotely (i.e. from the command line)?

I expect that there is, I just haven't been able to find out how... :(

[Additional: For some reason, there is no option to keep the keyboard dock awake under "Settings->Dock->Dock Power Mode - WakeUp tablet with key press" - The 'Dock Power Mode' section is simply not there - no idea why. Also no idea if this would resolve the issue or not...]

Looking forward to some handy solutions! :)
[Nexus 5X Q&A, Help & Troubleshooting] cesar67:
Don't see how to enable NFC in settings, Android beam not present either.

Running 8.1 with magisk and Franco kernel.