yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sabianadmin:
I am thinking about setting up a nightly automated build of sailfish for G-Nex. This will help with driving development & allow me to make contributions to the codebase and enable community interaction with these changes. This might include making low level optimisations to the kernel, peeling away layers of android related redundancy from the CM base, the inclusion of binary blobs instead of open source components, bug fixes to the sailfish portion of things and patches (such as double tap to wake etc). I'll also see if i cant get the store working ( ;) )

Does any kind soul want to put together a sailfish build thread with a run through of how you churn out a flashable build using beidl's Github repo?

This might also take the pressure off of beidl to do a release every time he makes a change.
[Samsung Galaxy Nexus] sledges:
Give a go with http://github.com/dmt4/sfa-mer
[Samsung Galaxy Nexus] sabianadmin:
Thank you! Starting to set up now, can this be built on Mac? or will i have to vm Ubuntu and build from there?
[Samsung Galaxy Nexus] sledges:
Linux only:) Also contact [MENTION=4559082]vakkov[/MENTION] on IRC, he's been baking latest images
[Samsung Galaxy Nexus] sabianadmin:
Excellent setting that up now and yes i shall contact him, is he building for the Galaxy Nexus or just baking generic images?
[Samsung Galaxy Nexus] stronger12:
New Whatsapp Client for SailfishOS

Has anybody else tried the new inofficial whatsapp client "whatsup"?

On my Galaxy Nexus it crashes while loading.
[Samsung Galaxy Nexus] sabianadmin:
Sailfish Kickstart

Hi guys, are there any cooks or developers here willing to get the nightly server set up with me? Eager to get it working and get developing ASAP.
[Samsung Galaxy Nexus] mudnightoil:
Dunno how much experience or knowledge you have of Sailfish, but one of the reasons why focus has shifted to the Nexus 5 / Oneplus / other newer phones from the Galaxy Nexus and Nexus 4 builds (which were initially much more advanced) is that the OS has serious problems with only 1GB of RAM. It needs 2GB really. This wasn't true initially. But it certainly is now, and it's likely to get worse in the long run.

Just a heads up before you potentially spend a lot of time and effort on this.
[Samsung Galaxy Nexus] sabianadmin:
But wait... Doesn't the Jolla phone only have 1 gigabyte of addressable memory?

Don't have much in the way of Sailfish expertise. Should have enough of an understanding of QML & C++ / Qt though.

I've seen wonders performed on lesser devices with Android 4.0 to 5.1 so i think with a bit of work performance can be increased substantially.
[Samsung Galaxy Nexus] mudnightoil:
Correct, it's been a big issue since they updated the Qt version and some other libraries. Subsequent updates were supposed to 'improve' it, but it's just made it worse. All apps except phone app just suddenly close ... and it happens ALL THE TIME. You can reduce the sensitivity of the OOM killer using command line, but there's still no way to stop it suddenly closing everything once it's triggered. Even minimising sensitivity it happens pretty much every time I use a browser when a couple of other apps are open.

The supposed efficiency and low footprint of Sailfish was always a bit of a myth, but in terms of RAM usage / management it's way, way worse than any other mobile OS now.

I'd strongly recommend you target a device or devices with 2GB of RAM or more.
[Samsung Galaxy Nexus] sabianadmin:
But surly this is just an issue with OOM groupings and the configuration rather than any major inherit issue with Sailfish. From what i can tell, the Sailfish ports are making heavy use the Android kernel and user-space components sans the elements which require Dalvik? Is the latest Qt release that much of a hog that it trumps Dalvik / ART on memory usage?
[Samsung Galaxy Nexus] mudnightoil:
It would appear so, or at least Jolla's implementation. Never had these issues prior, even with heavy usage of Android apps on Alien Dalvik.

Early access release that went out today changed the sensitivity of the OOM app killer. It's now much more difficult to trigger, however the device slows down REALLY quickly instead of just closing all the apps immediately; as was the behaviour when the early access for the Qt update release was put out, prompting them to institute an app killer. Having a couple of active browser windows open with a couple of other apps open = tons of dropped frames, UI jitter, slowdown etc.

AFAIK Jolla have finished optimising memory usage post Qt update, or did so 2 updates ago. There won't be any major improvement or reversion to previous status quo (less memory usage). No-one's reported any OOM issues at all on the Nexus 5 port, hence why I'd recommend focusing on porting to 2GB+ devices.
[Samsung Galaxy Nexus] sledges:
Hi sabianadmin, here's a script to build an image with one line. Examining it and playing around is another way to learn the build process, also suitable for your nightly builds. It hasn't been tested on maguro, but nexus5 and sony xperia z have successful builds! So you'll be pioneering and please submit patches! :)

Here's a ready line which -should- work for maguro, if I didn't forget anything:) Have a lot of fun!

git clone https://github.com/sledges/sfa-mer -b maguro

cd sfa-mer

./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-16-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-16-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.2.17 -extraname my1 -jobs 4 -dhdrepo "http://repo.merproject.org/obs/home:/vakkov:/branches:/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_latest_armv7hl/" -mwrepo "http://repo.merproject.org/obs/home:/vakkov:/branches:/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_latest_armv7hl/" -target update11

Big thanks to dmt4, alin, and oleid for putting together and evolving this sfa-mer script!
[Samsung Galaxy Nexus] sabianadmin:
Hey sledges, thanks very much for the guide, i'll fork it on my GitHub page, kick off a build in work and report back tonight. One thing I was thinking about is dehydrating apps when they enter the background and whitelisting services using the Audio & File Transfer API, Similar to how iOS 6 did it back in the day. Would this be a plausible way of dealing with the auto-kill-cascade that seems to be an issue for devices with more humble memory quotients?

We need to short this memory issue out, 1gb is more than enough for a mobile device, lunacy that the low watermark has now become 2 gig. Software > Hardware.

Also i'll make an attempt to back-port the 1.9 GPU drivers at some point as they seem to be a big step up.
[Samsung Galaxy Nexus] mudnightoil:
Well, good luck, re: doing something about the RAM issues. If you have expertise in this field, maybe [MENTION=3234690]sledges[/MENTION] can put you in contact with the people at Jolla who are responsible for working on it. Personally I don't understand why it should be way more RAM hungry than iOS / Android / WP / BB10 / Tizen / UP / FFOS etc, but it seems like Jolla have settled on it.
[Samsung Galaxy Nexus] sabianadmin:
./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-16-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-16-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.2.17 -extraname my1 -jobs 4 -dhdrepo "http://repo.merproject.org/obs/home:/vakkov:/branches:/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_latest_armv7hl/" -mwrepo "http://repo.merproject.org/obs/home:/vakkov:/branches:/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_latest_armv7hl/" -target update11

Gives me a ssu-kickstarts-droid not found issue, as i on the wrong branch?
[Samsung Galaxy Nexus] dobby3698:
Getting the alpha2

Does anyone have the file for the alpha 2 and if they could, could they put it in google drive or dropbox so i can please download it, i may kick the tyres and learn how to help it out. maybe provide a link from my drive permanently
[Samsung Galaxy Nexus] mugna91:
Follow the guide on wiki page. You'll find download link (thanks to [MENTION=6169060]stronger12[/MENTION]): https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_maguro
[Samsung Galaxy Nexus] sabianadmin:
Have you run this script of late? Are the repo references in the script up to date? Its complaining about ssu-kicksrtarts-droid no being found in the repos...
[Samsung Galaxy Nexus] sledges:
Hi! If you grep the build system for ssu-kickstarts-droid, you will eventually find out that vakkov forgot to add droid-hal-configs to his repo (because he never used this script build system). Now I added that package to the official repo that it's also designated for proper use. Here is the new command:

./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-16-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-16-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.2.17 -extraname my1 -jobs 4 -dhdrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -mwrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -target update11

Enjoy!
[Samsung Galaxy Nexus] sabianadmin:
Thanks for the updates! Is it possible that mic (Image creation util) was also excluded? Currently getting:

Error <creator>: URLGrabber error: https://releases.jolla.com/jolla-apps/1.1.2.17/armv7hl/repodata/repomd.xml

* Info: copy image

cp: cannot stat `sfa-maguro-1.1.2.17-my1-201504201533/sailfishos-maguro-release-1.1.2.17-my1-201504201533.zip': No such file or directory

!! command failed at Mon Apr 20 15:33:08 UTC 2015, dying...

!! command failed at Mon Apr 20 15:33:08 UTC 2015, dying...

* left mer chroot

When running the script with your arguments
[Samsung Galaxy Nexus] sledges:
You found one more left-over. To fix it, you need to add:

cp $INSTALL_ROOT/etc/sailfish-release $IMG_OUT_DIR

to the %post --nochroot section of your final .ks file
[Samsung Galaxy Nexus] sabianadmin:
Should this modification be made in the build-img script? the a.ks seems to be auto-generated at run time so any changes made there will be overwritten.
[Samsung Galaxy Nexus] sledges:
Correct, this error will go away in near future (will be included into auto-generation of .ks within its native package), but for now feel free to modify the build script to automatically fix the last version of .ks during build process (just like where it adds custom packages to the image, such as jolla-calendar)
[Samsung Galaxy Nexus] sabianadmin:
Hmmm interestingly the line you suggested adding to the build script seems to already exist on line 127 of 'build-img.sh', are we sure this is whats missing? or am i missing something?
[Samsung Galaxy Nexus] sledges:
That means .zip creation is failing for another reason. Pastebin logs please :)
[Samsung Galaxy Nexus] sabianadmin:
Console Output

Here is the full console output for the build http://pastebin.com/PugN8EFL

Are there specific log contents you want along with this?
[Samsung Galaxy Nexus] sledges:
Thank you for the log, due to which I finally I found the real cause:

Error <creator>: URLGrabber error: https://releases.jolla.com/jolla-apps/1.1.2.17/armv7hl/repodata/repomd.xml

Should be fixed with this:

./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-16-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-16-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.2.16 -extraname my1 -jobs 4 -dhdrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -mwrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -target update11
[Samsung Galaxy Nexus] sabianadmin:
There now seems to be a circular dependency: http://pastebin.com/SJYiJJD7

Im doing a clean build and re-running to see if it was just a carryover issue.

EDIT: Yep did a build from scratch, same result. Seems one of the dependencies is missing "jolla-devicelock-plugin-encpartition" which is required by "jolla-hw-adaptation-maguro-0.0.6-201408251020.noarch"
[Samsung Galaxy Nexus] sledges:
Thank you, fixed that: https://github.com/mer-hybris/droid-hal-device/commit/58697e1f74f5894b1607d8e19e9e50beab6f3dbb

You'll need to re-run the build
[Samsung Galaxy Nexus] sabianadmin:
I know the change has been committed to the repo but is this change live? Deleted everything and cloned the branch and ran the script and I am still seeing the same issue regarding that specific dependency. Hahah sorry I'm starting to play QA here!
[Samsung Galaxy Nexus] sledges:
:D yea kind of, and I like it! Just check what physical file you have there, it should be live if you updated enough from scratch (repo sync would help): $ANDROID_ROOT/rpm/patterns/maguro/jolla-hw-adaptation-maguro.yaml
[Samsung Galaxy Nexus] sabianadmin:
I cleaned everything that the script pulls down and removed the actual cloned source also, checked it out again and then ran the script. Same result, does the repo reference the wrong dependency?
[Samsung Galaxy Nexus] sledges:
grep devicelock $ANDROID_ROOT/rpm/patterns/maguro/jolla-hw-adaptation-maguro.yaml
[Samsung Galaxy Nexus] sabianadmin:
http://pastebin.com/gZidinsd

The devicelock is listed there as "jolla-devicelock-plugin-encsfa"

EDIT: Is this a caching issue of some sort? Because that reflects the change you made in your commit...
[Samsung Galaxy Nexus] sledges:
The script build system that you are using is intended for nightlies - nuke the whole thing, and rebuild again clean.

It is possible to build incrementally, but one needs to know about how HADK works. If there's a pattern change, the whole sequence from chapter 7 needs to be re-done
[Samsung Galaxy Nexus] sabianadmin:
Nuking everthing should just be a case of removing the sfa-mer and mer-work dirs, bin dir, a files and thats it right? Does anything get cached in a .something folder which is hidden?

.scratchbox2 seems to be housing cached stuff on each fresh run of the script. I've cleared that and the build and I am re running it again.
[Samsung Galaxy Nexus] sabianadmin:
Ran it again, no dice. Where are these patterns being generated from? Clearly that dependency is specified in the repo as its auto generated xml that reference it?
[Samsung Galaxy Nexus] sledges:
You are correct, patterns on OBS repo are overriding our local ones. I'll ask vakkov to reupload them with correct pattern.

in the meantime, brace yourself for full rebuild (leave it for night). this is triggered when you remove all parameters with http://repo.. in them (dhdrepo and mwrepo, iirc)

have fun!
[Samsung Galaxy Nexus] sabianadmin:
Okay perfect! Let me know when thats updated repo side and ill re-run the build locally!
[Samsung Galaxy Nexus] sledges:
We misunderstood sorry: you can re-run build already now, by removing those params. the build will be way lengthier, let's see whether your build finishes first or vakkov updates RPMs :D
[Samsung Galaxy Nexus] sabianadmin:
Currently on the bus on the way to the office, once there ill kick off a build :) Gimme 10 mins ;)
[Samsung Galaxy Nexus] sabianadmin:
Ran a fullbuild sans arguments and it didn't go to well, loads of permissions issues even when running sudo because home wasn't specified, I've re-done it with the the device version and the paths set and i'll check back in with the result
[Samsung Galaxy Nexus] sledges:
Is this what you tried (if not, please do):

./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-16-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-16-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.2.16 -extraname my1 -jobs 4 -target update11
[Samsung Galaxy Nexus] sabianadmin:
Yep I've been trying with those arguments and still seeing the dependency error, let me know when he changes the repo and I'm not great at waiting so i will look for a way to modify the manifest with the incorrect dep referenced at run time :P
[Samsung Galaxy Nexus] sledges:
Something -fishy- going on :D Could you paste the whole (or as much as you can reach, after it fails) big output (to pastebin) of that fullbuild command above that I sent you? Pls nuke all ouput directories beforehand
[Samsung Galaxy Nexus] sabianadmin:
I'll nuke everything and try again and pastebin the output :)
[Samsung Galaxy Nexus] sledges:
Thanks!

BTW, the maintainer has uploaded new RPMs. When this has finished building, you can try fullbuild command line again
[Samsung Galaxy Nexus] sabianadmin:
No problem! My connection is awful today so its still downloading the sdks and environments (untaring the last of them as we speak) ill check back when its done! :)
[Samsung Galaxy Nexus] sabianadmin:
New Build In a Couple Hours

Okay that built successfully and I now have it running on my device, camera still isn't working and still a bit of stuttering when scrolling (GPU Drivers, does this use the CM10 kernel? Can we update the drivers used? Or is this down to surface flinger?) but everything else is significantly improved, the keyboard is much much better. Uploading now and will have it live in a couple hours for others to test. Proof of this seen in the screen cap below. Big thanks [MENTION=3234690]sledges[/MENTION] for his tireless support and to the Jolla repo maintainers!

EDIT: Ignore my thumb, I broke it kickboxing a few years back... looks like a foot.
[Samsung Galaxy Nexus] sledges:
Great job! For my next trick:

./fullbuild.sh -mer-root $HOME/sfa-mer-work/maguro/mer-apr-24-t1 -android-root $HOME/sfa-mer-work/maguro/ubu-apr-24-t1 -branch hybris-10.1 -device maguro -vendor samsung -dest $HOME/sfa-mer-work/maguro-deploy/ -sfrelease 1.1.4.28 -extraname my1 -jobs 4 -dhdrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -mwrepo "http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/maguro/sailfishos_1.1.2.16_armv7hl/" -target update11

This will produce the bleeding edge image of the still hot update, only for brave hearts ;)
[Samsung Galaxy Nexus] sabianadmin:
WOW okay! Stable(ish) & Bleeding edge nightlies it is! I'll get building this now! Upload for the existing version is at 82%, will you update the page with that and I'll start a new thread for the .4 nightlies?
[Samsung Galaxy Nexus] sledges:
I'll get a hold of [MENTION=1740472]beidl[/MENTION] (OP) to update the page. He and vakkov are the original porters, and only vakkov is active at the moment (he uploaded the RPMs).

BTW, vakkov would appreciate if you pinged him in our IRC channel (#sailfishos-porters) to talk about GPU and such.
[Samsung Galaxy Nexus] sabianadmin:
New Build Released [Test Build]

For willing testers: https://www.androidfilehost.com/?fid=96042739161892475 Flash that over CM10.1.2

[MENTION=3234690]sledges[/MENTION] No problem I will ping him in the morning, heading to sleep now. I've a few questions as to some of the ins and outs of how the Hardware Adaptation stuff works for him anyway :)

Thanks!
[Samsung Galaxy Nexus] sledges:
Updated this page: https://wiki.merproject.org/wiki/Adaptations/libhybris (and link to maguro)

Thanks for your time! sleep 28800 time:)
[Samsung Galaxy Nexus] sabianadmin:
Successful .4 build

Okay built that with the latest version specified and that works fine, I'll upload it once I get on a more stable internet connection in an hour or so.

I need to pop onto the IRC and figure out how we can tackle the poor performance issues. Also do we know why the Jolla store doesn't work? Whenever i try to install packages from the terminal over SSH and enter my user details it continuously prompts me to re-authenticate without any warnings or errors. When I do so through the Jolla Store app it returns some generic "Something went wrong type message".

EDIT: New bleeding edge 1.1.4 build https://www.androidfilehost.com/?fid=96042739161892737
[Samsung Galaxy Nexus] sledges:
Awesome! Have you got twitter/g+ handles so we could advertise these nightlies?

Jolla Store works only on selected devices, and acceptance of new devices has been halted until Jolla Tablet is out, apologies
[Samsung Galaxy Nexus] sabianadmin:
I'll have to set all of that up, sabianadmin is a handle (and email address) i haven't used since 2009 and I have my own business so this and that need to be separate ;)

I must get digging into the sailfish code and the maguro specific stuff, no point there being a nightly if nothing changes ;)

P.S I built a version of .4 with obs and store enabled, is there any point uploading this?
[Samsung Galaxy Nexus] sledges:
Twitter sabianadmin handle returns not found ;)

You indeed do!

No, it won't give you store access as per earlier message of mine. Though sideloading warehouse (openrepos app) would give you many 3rd party apps (less QA though, but better than none!)
[Samsung Galaxy Nexus] freesoftwareman:
Is wifi working good with maguro with emmc bug?
[Samsung Galaxy Nexus] sabianadmin:
Try and see.
[Samsung Galaxy Nexus] markitosd:
Flash on top of CM10.1.2?
[Samsung Galaxy Nexus] sabianadmin:
Yup same as the 1.1.2.16 build (I have my own thread surrounding these nightlies by the way, check the general section of our subforum)
[Samsung Galaxy Nexus] dobby3698:
Bugs Ive found

Hi all just gave this a spin for 20mins

A few bugs:

keyboard crashes and doesnt open numbers

GSM sims in Australia dont work?

Backgrounds are black?
[Samsung Galaxy Nexus] ffsinit:
About GSM sims:

There is a bug in OFONO, someone have to fix it. You can track progress in nemo bugzilla (cant post links, google for "[maguro][i9300] ofono unable to read/write from SIM " .

For now, temporary fix:

systemctl restart ofono

in root terminal. Should work until reboot.
[Samsung Galaxy Nexus] apollus:
To the OP or any other devs that have worked on this: Are there any plans for building/releasing an update of this running the latest version of Sailfish, OS 1.1.7.24 "Björnträsket" ?
[Samsung Galaxy Nexus] F0x123:
Hi,

I am looking for a new ROM for my Galaxy Nexus and I like the Jolly phone thus I thought I could try Jolly on my old but still good in shape GN. Would you recommend using Jolly on that hardware? Is the camera still not working? Other important issues, stability?

Thank you in advance
[Samsung Galaxy Nexus] bamtan2:
I would not recommend sailfishOS because judging from this thread it is not finished or actively developed. any 4.2/4.3/4.4/5.1 rom should be better :P
[Samsung Galaxy Nexus] F0x123:
Ok, that's a pity. I like the Sailfish UI and concept. Which ROM would you recommend for my GNEX? The stock ROM is getting slower and slower. The launcher often restarts which takes several seconds. The new ROM should be fast and secure and all hardware features should work (GPS, camera, buttons, etc.)
[Samsung Galaxy Nexus] playitlouder:
[MENTION=1740472]beidl[/MENTION] Do you still have the CyanogenMod 10.1.3 Rom backuped somewhere?
[Samsung Galaxy Nexus] Samuelgames:
Good news are coming

It's unbelievable how smooth the experience is for the Galaxy Nexus, baseband problems need to be solved (help is appreciated!) and there should be a build available soon
[Samsung Galaxy Nexus] Galaxyninja66:
Share the sources and or build, this is the only thing keeping me from buying a Galaxy Nexus today. I love the Gnexus and would kill to finally be able to rock one today. The only thing keeping me from doing so is the lack of a stable Sailfish OS build, let alone a 2.x build.

Edit: how stable is the 1.1.4 build?
[Samsung Galaxy Nexus] Galaxyninja66:
I also noticed the lack of BT mac address, which means most likely broken or half-functional Bluetooth, this has a ton of patches for people to try, at leaast for SD CPUs, the Gnexus has an OMAP though so I don't know... as far as baseband, please ellaborate, I know that ofono and RIL usually need a ton of patching for every phone and almost never work out of box. Have you built gstreamer and audioflinger for video and phone calls? how do the sensors work? I need to know EVERYTHING.
[Samsung Galaxy Nexus] awandroid89:
Legend will rise again... looking forward for this....