Alphabet is not anymore a startup company, and they cannot afford to lose money. Now they have institutional investors profit oriented with decision votes. I do not understand their strategy with the HW, cause they were not successful in the past also. But if they want to be successful I would expect to have chinese market in view. Anyway, I don’t care about google, they can fail/succeed…their problem.
Well then, I can tell you that
- Spotify is a (almost) 20 year company, not a startup.
- pixel sales are good. They don’t sell a few dozen devices, they sell millions.
But if you want to think there there is a conspiracy behind it or that they do gods work, feel free.
I have nothing to add on that
I’ll just leave this here. Anyone thinking they know how internet-based companies make money, and believing users matter to them should read it:
Based on what I read here and in other threads, it is a time-consuming and difficult path to port Sailfish to unsupported devices and get it running. Even for the experienced ones.
Will it be easier to accomplish this on a Xperia 1 mark vi than on a Samsung device?
Sorry if this is a stupid question from a non-developer n00b
Sony has the advantage that they provide AOSP with drivers in their open devices program. As far as I understand this is a good starting point
I wished Sailfish was ported on a more sustainable device instead of every two years on another one. On Gigaset’s e.g. Their phones can be opened on the back, inside parts are screwed to fix them. Gigaset sells spare batteries. The phones are sturdy and have a good size. These phones are mid range, not high end. By community members a port has been made (Piggz) yet it would be nice if this became official.
Yes I agree, in general I like the Xperias, but I prefer bigger devices. C2 is no option fir me, no OLED no buy.
Pixel phones have disadvantages that many here won’t like: they are Google’s and they don’t have a mini jack nor a card slot. If you want to listen you need Google’s bluetooth earbuds. Complete with location tracking.
I have tried install Sony AOSP multiple times on Debian and Ubuntu and always install fails at some point. Device is Xperia 10 lll.
Have you been using USB2 or USB3 ports to connect the phone? It is known issue that the flashing can fail if you are not using USB2 port or USB2-hub in the USB3 port when flashing.
Both USB ports tried and many different cables too.
I’ve been thinking if my computer is too ancient: Intel© Core™ i5-4670K CPU @ 3.40GHz × 4, memory 32 GiB.
But were the ports USB2 or USB3? If they both were USB3, maybe there is a setting in BIOS to change them to work in USB2-mode or use USB2-hub in the middle.
At least on Windows side years ago, when I flashed my Xperia 10, I used my old i5-2500K powered computer and had zero problems, when using USB2-port.
I meant both USB ports tried that I have plugged phone to USB3 port and USB2 port. I also tried phone plugged on USB hub which is only USB2 hub.
Then I’m out of ideas what could have caused your tries to fail, but I’m still pretty confident your old CPU wasn’t the reason. If you ever need to flash your phone (again) in the future and run into any problems, don’t hesitate to post on the forum, so smarter people than me can help you troubleshoot and guide you through the issues.
Thank you for your thoughts. I will try flashing AOSP some day. Maybe I will have assembled a new computer by then.
Was the trouble with building the flash image from the sources or the flashing process?
Flashing is described well on the Sony website
I did everything according to Sony’s instructions. The flashing process always crashed at some point. While searching for answers to the problems, I discovered that I am certainly not the only one having problems.
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/guides/aosp-build-instructions
That is strange based on my limited experience.
Building the images prior to flashing was always the hurdle for me and where I crashed.
But flashing did work always on my 20 years old Dell machine running Debian.
Yesterday in other thread about flashing problems I saw a possible fix, that I remember seeing before, but had completely forgot it, so I couldn’t suggest it in my earlier replies.
You should test @direc85’s trick for turning off the autosuspend
for USB and see, if the flashing works after that:
This and some other “tricks” for flashing successfully are documented for long at