View Single Post
Posts: 3,296 | Thanked: 4,325 times | Joined on May 2011 @ Poland
#4
I've started working on the OnePlus3 port: https://github.com/mer-hybris/hybris-boot/pull/111
Let's see how far I'll go

I'm basing on this image: cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-oneplus3.zip

Checklist:
  • [DONE] Build hybris-hal
  • [DONE] Fix kernel configuration
  • [DONE] Package Android HAL
  • [DONE] Build the SFOS rootfs
  • Test the image
Download link: http://students.mimuw.edu.pl/~marmis....10-marmistrz/
The signature was made with a key with the following ID: 0176AC20960B730A30ADBE545D9E4935F8CAE33F

Current state: boots.
* but the Sailfish UI crashes
* the 192.168.2.0/24 connectivity doesn't work, current findings: (log from #sailfishos-porters)
Code:
<marmistrz> I found the reason I have problems with connectivity on my OnePlus 3
<marmistrz> https://pastebin.com/1Sg23qbT
<marmistrz> the rndis0 interface is constantly registered and unregistered by the kernel - this looks like some conflicting/missing configuration option
<marmistrz> the dwc3 and RMNET messages are red in the journal, so errors
<marmistrz> And the only thing that is mentioned in the qcom init files about rndis0 is: write /sys/class/net/rndis0/queues/rx-0/rps_cpus ${sys.usb.rps_mask}, commenting it out doesn't change anything
How to get logs?
1. Enable
Code:
Storage=persistent
in /etc/systemd/journald.conf or create the directory /var/log/journal
2. After you force shutdown SFOS, you'll find the logs in
/data/.stowaways/sailfishos/var/log/journal
3. copy onto your computer, open with journalctl
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2017-08-22 at 18:25.
 

The Following 15 Users Say Thank You to marmistrz For This Useful Post: