@tager18 do you see any useful logs in .cache/upstart/ ? (I think that's the path)

@tager18 Did you use YOUR public key? You know you can't use the literal wget command from @guru's book right? Because that would not be YOUR public key.

If you are not sure what I'm talking about, then I'd suggest you delete the .ssh folder on your phone and recreate it following these steps:

https://askubuntu.com/questions/348714/how-can-i-access-my-ubuntu-phone-over-ssh/599041#599041

@guru Maybe you want to consider changing the instructions in your book. I kinda understand what you MEAN, but I think it would be more helpful for people if the instructions where LITERALLY copy/paste -able. And that would mean adb. DO include the tip that there ARE alternatives to adb, like uploading it to someones own webserver and then wget the key on the phone, but, that should be a more advanced tip further down, better explained and not as prominent. Also I do remember that I also needed more/other chmod/chown commands than in your book. The instructions on askubuntu that you do link to seem pretty foolproof to me (with -R and with chmod)

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

ok so I just played around with the system.img file, if I run "mka systemimage" and try to mount it, it fails saying invalid partition type,

I think the android system.img is some unusual image format. Read the halium-install script. There you see how they transform it into something else!

if I run the make_ext4fs command on it, i can then mount it, but it is empty, (kind of expected as make_ext4fs is a ext4 format tool)

Well, yeah. It is expected to be empty afterwards.

and trying it the way the script has it doesnt work either, so now I think I have it narrowed down to the system.img file being corrupted or not compiling right.

I could imagine that an incomplete, or corrupt, or even an absent system.img might all lead to a rebooting device. Do you know how far the boot process goes for you so far? Does it enter the rootfs. Do you have telnet access? ssh? Which ip? Can you watch the usb serial number? What values does it go through?

I can't make much sense of your kmesg above. Maybe it is only the "late" part of the boot process after it has switched to the rootfs. If that is the case you can check my thread for how to NOT start the lxc container with the system.img. just as a stepping stone in debugging problems in that container

@doniks was this the issue you were experiencing with TWRP 3.1.1? if so I might be SOL from here cause my device only has 3.1.0 or 3.1.1 according to the TWRP website.

No I don't think you need to worry here. You only need twrp to have ANY recovery that allows you to adb in. You can probably use any other recovery you can dig up on xda for your device. I think my problem was just that the other version wouldn't install or something.

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

@doniks I was using the Sailfish HADK to figure that out, I forget what the actual command was, but I did "adb shell" then another command which output that info, I copy and pasted from my terminal into the fix mountpoints file then formatted it to the correct format for the file.

Ok

I tried to manually adb push the system.img to the same destination the script was (/data based on my understanding) which worked,

Hang on. So you DO have a system.img file? I thought make systemimage fails?! (Can you still post that error?)

but that juat makes my phone boot loop so I think I might be missing something, I looked at the kmesg file as well, the last entry it had was "booting linux" but thats also not happening otherwise I would be posting files lol

Maybe post the whole kmesg. Boot loop could be all kinds of other problems.

@tigerpro ok. How did you decide which partition number to put where, eg., how did you decide to pick 17, 24 and 27 for boot, system and userdata? What are the partition sizes? Whats the content of your board config file? What is the exact error message you get?

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

@hans1977se arent we all? I am gonna keep searching if this flash attempt fails, I have a feeling my issue might be halium-install trying to copy the image to the wrong partition cause I tried flashing it with TWRP just out of curiosity, and it says the image is bigger than the partition (which explains the out of space) and TWRP only offers boot or recovery when I select the file, but since I just recompiled the system image it might have resolved itself, wont know until I get home to try it

That reminds me. Did you do this step?

https://docs.halium.org/en/latest/porting/index.html#include-your-device-in-fixup-mountpoints-script

What changes did you make to that script?

@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:

So I have made progress, I managed to find an un-official lineageOS repo for my phone, using that and a little trial and error I managed to get Halium to compile.

Niice! Which version?

I follow the halium porting guide, but when I get to the part that tells me to run the halium-install script, I keep getting an error saying that it "cant write 217 blocks, out of space?" Or something along those lines, not in front of my computer atm,

I remember there was another ubports forum conversation about a similar error message. Something about partition size settings ... I can't remember whether it was actually resolved, but see whether you can find that. Maybe it helps.

EDIT: found it
https://forums.ubports.com/topic/481/porting-to-motorola-moto-g-2013-lte
It seems it was related to the filesystem it was being built on. Weird!

@thepeter

http://docsubportscom.readthedocs.io/en/latest/userguide/dailyuse/libertine.html

@Josué said in OTA 3 suggestions: your wanted features:

what do you think about this? =)
https://www.youtube.com/watch?v=3FYbtyweMs8

Looks good!

@hans1977se said in [BQ E5 vegetahd] Change of grid units, scaling?:

@doniks said in [BQ E5 vegetahd] Change of grid units, scaling?:

Well, the "cfg file" syle configurability is there already, right?!

Yes, but it is apparently in the read-only part of the fs, and the suggestion is that it can live in /home/phablet for anyone who wants to change the default.

https://askubuntu.com/a/846751 :

gsettings set com.canonical.Unity8 usage-mode Windowed
gsettings set com.canonical.Unity8 usage-mode Staged

This is what I meant with "cfg file" style. It's not a literal file, but I think executing a single commandline is about the same complexity as changing a file. So it is not in the read-only part of the fs. Also I guess it shows that there can be as many gui's as people like to implement. tweak tool does have it!

PS: I believe there is a third setting like Auto, Automatic ... as well.