Porting to Samsung Galaxy Note 4 SM-N910P
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
@doniks looking through the lineage repo, it doesnt look like my device is an official device, the repo from what I can tell only goes to cm13,
Ah ok. Maybe there is some other android port. What about this:
https://forum.xda-developers.com/note-4-tmobile/development/rom-cmremix-rom-v2-5-12-23-14-t2981479
https://github.com/CMRemix?utf8=✓&tab=repositories&q=trlte&type=&language=
but I do understand what your suggesting. Make sure DirtyRect is enabled everywhere, try make again, if I give up or just cant get code ro compile try a different repo and see if that works. I think Ill have to just try building cm/lineage for my device and to from there, I have a suspicion that will compile fine cause the errors Im seeing according to the default.xml file are from the ubports repo of android_hardware_qcom_display-caf
That's probably it indeed! I remotely remember some conversation about ubports vs caf somewhere. But I can't find it.
@mariogrip , @bshah do you guys have any advice for the good man here?
-
@doniks thank you for the links, I checked those repos for my device and they only go to 13 as well. I have put this on the back burner before I get the urge to grab my biggest heaviest hammer, and teach this system to fly (prob why I never became a full fledged coder) I will keep checking in here and try solutions that are offered (or get whatever info is needed) though. I am also learning to code in my spare time as well, so that eventually I might understand whats supposed to be happening with this DirtyRect better than the comments in the cpp files.
-
So an update, I decided to coetely delete everything and repo sync again, Im back to the original error I got when it was compiling with the dirtyRect errors, Im doing research to see if I can figure anything out, but so far nothing of major note, aside from a old ubuntu touch git repo for galaxy phones, Im trying to get that to sync with my local manifest, but no luck so far, Ill keep trying and if it works Ill post again, if not Ill update this one with the errors and likely start working towards Halium.
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
a old ubuntu touch git repo for galaxy phones
links?
-
@doniks its just the display-caf, media-caf, and audio-caf portions, and I have yet to get my system to actually retrieve them, but heres the link
https://github.com/Ubuntu-Touch-GalaxyS?tab=repositories
So far the dirtyRect issue Im running into seems to be just with ubports version of display-caf, none of the other repos Ive looked at seem to have any mention of it which makes things a little more complicated for me, but who knows, if I can get this repo to download the files maybe it will actually compile for once, Ill try again when I get home, I also made a thread on XDA-Developers, hoping someone else is trying this or even has an idea on how to progress through, only time will tell.
#=== Edit ===#
I took a crack at porting Halium, I get the same dirtyRect error there as I do with ubports, I am starting to wonder if the dirtyRect is something linux based, which would explain why I havent seen it in any Android repos. I also havent seen anything for qcom's *-caf repos that goes over cm 11 on android which is just adding to my confusion at this point. There is a wip repo that I came across but that doesnt have dirtyRect in it either. So at this point Im just confused about the whole qcom *-caf repos in general. I am gonna try just manually adding the galaxy repos I came across, but I dont expect much to happen with that as its for the phablet 4.4.2 r1 build (which I understand to be deprecaded now) Im all ears if anyone can either help me make heads or tails of the caf repos or has anything I can try to get the code to fully compile. Thanks
#=== Edit 2 ===#
So I manually copied the display-caf repo I came across for galaxy phones, no luck there either. Guess Im going back to the drawing board with dirtyRect and display-caf, I did manage to get the nexus 4 version from the old cannocal guide to compile, however I dont own a nexus 4 so I cant try it to see if it works. I at least know I can compile the nexus 4 version, now I should try it with ubports and see if I het similar results to old porting guide, that at least will narrow down my issue regardless of result.
-
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. 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 decided to ignore that error just to see if the kernel at least boots (TWRP warns theres no OS if I reboot at this point) and to my shock and amazment, after a couple mins I could actually follow the debug info and telnet in. I had to change a couple things in the kernel config according to diagnosis.log and init.log which Ive done already, but still get that space error when I run halium-install. Anyone out there run into this? If so, tips to tey and move from a working kernel to at least a working gui?
-
@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! -
@doniks I got Halium 7.1 to build, 5.1 kept giving me the dirtyRect error so I decided against trying to compile that. I actually just found the thread you linked, google is such a pain cause it keeps searching for helium despite me typing halium. I checked the respective files on my system, I did like you had mentioned in that post and deleted the same file and ran make systemimage gave me a file that matches the size of my boardconfig.mk size. I will try flashing again when I get home, ssh can only do soo much when your not in front of the computer your sshed too lol
-
@tigerpro said in Porting to Samsung Galaxy Note 4 SM-N910P:
google is such a pain cause it keeps searching for helium
You could give the alternatives a go.
This one is quite good:
https://duckduckgo.com/ -
@hans1977se yea I just usually default to google cause its what I use, duckduckgo is my fallback, someday I wont have to google Halium errors anymore lol
-
@tigerpro yeah i know, i'm far worse with habits than i think i should be.
-
@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
-
@tigerpro probably so in many cases.
I hope this works out for you. It would be quite nice with some Samsung phones running Ubuntu i think.
-
@hans1977se thats my sentiment exactly. Dont get me wrong Android is nice and all, but it leaves alot to be desired for an OS, I have a working kernel (hybris-boot.img) so far, just gotta figure out the rest to make it all work now. Keep an eye out for a possible resolution to Halium, Im so close I can taste it lol
-
Ok, this is weird, I did make systemimage earlier, file size matched at that time, now its 250-ish MB when it should be 300+, think I might have to just use the mkext4 program manually, Im doing make systemimage again just in case something happened when I wasnt looking, but if I have the same issue then I dunno, maybe try a different drive for the code compiling shrugs this is turning into a scooby doo mystery haha
-
@tigerpro There are a lot of good things in Android, but i think it's not really for technical people who likes it better somewhere nicer off the mainstream.
Also i find it wrong to have someone constantly trying to watch you, 24/7, to find out how to make the most money out of your life.
-
@hans1977se well the monitoring is easily fixed via VPN, I myself use one whenever Im using a site with sensitive info, an ad blocker like Ad Away works really well too for the ads, I just want something different cause honestly, Im not a big fan of the current mobile OS offerings, anyways, getting slightly OT, if the make systemimage messes up again, Ill use mkext4 (or whatever the command is)
-
@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 I think it is a very complex thing to get the complete view of, but what i wanted to say is that i think it's conceptually wrong to constantly track people to get the most money out of you (or in any other way they might do or be doing in the future). You might forget to use your VPN or did not think it was necessary to use it at a particular time, and once they have your information they have it and once they have it their policy could change or a hacker can get hold of it.
Who knows what will happen, but this is one reason why i'm here and hope that your port as well as other people's ports will be successful and make Ubuntu wider available.
-
@doniks said in Porting to Samsung Galaxy Note 4 SM-N910P:
@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?
@doniks I did do that step, its a bit confusing on which partitions they want cause I used all of the others to try and figure out a pattern, then decided to just put them all in there, Ill post the full section I added when I get a chance.
#=== EDIT ===#
@doniks this is the stuff I added to fix mountpoints, im not sure whats needed and what isnt, but I think I have it entered correctly
"trltespr")
sed -i
-e 's block/platform/msm_sdcc.1/by-name/aboot mmcblk0p7 '
-e 's block/platform/msm_sdcc.1/by-name/apnhlos mmcblk0p1 '
-e 's block/platform/msm_sdcc.1/by-name/boot mmcblk0p17 '
-e 's block/platform/msm_sdcc.1/by-name/cache mmcblk0p25 '
-e 's block/platform/msm_sdcc.1/by-name/carrier mmcblk0p26 '
-e 's block/platform/msm_sdcc.1/by-name/dbi mmcblk0p5 '
-e 's block/platform/msm_sdcc.1/by-name/ddr mmcblk0p6 '
-e 's block/platform/msm_sdcc.1/by-name/efs mmcblk0p13 '
-e 's block/platform/msm_sdcc.1/by-name/fota mmcblk0p19 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs1 mmcblk0p14 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs2 mmcblk0p15 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 mmcblk0p10 '
-e 's block/platform/msm_sdcc.1/by-name/mdm1m9kefsc mmcblk0p16 '
-e 's block/platform/msm_sdcc.1/by-name/misc mmcblk0p20 '
-e 's block/platform/msm_sdcc.1/by-name/modem mmcblk0p2 '
-e 's block/platform/msm_sdcc.1/by-name/pad mmcblk0p11 '
-e 's block/platform/msm_sdcc.1/by-name/param mmcblk0p12 '
-e 's block/platform/msm_sdcc.1/by-name/persdata mmcblk0p23 '
-e 's block/platform/msm_sdcc.1/by-name/persist mmcblk0p22 '
-e 's block/platform/msm_sdcc.1/by-name/recovery mmcblk0p18 '
-e 's block/platform/msm_sdcc.1/by-name/rpm mmcblk0p8 '
-e 's block/platform/msm_sdcc.1/by-name/sbl1 mmcblk0p3 '
-e 's block/platform/msm_sdcc.1/by-name/sbl1bak mmcblk0p4 '
-e 's block/platform/msm_sdcc.1/by-name/ssd mmcblk0p21 '
-e 's block/platform/msm_sdcc.1/by-name/system mmcblk0p24 '
-e 's block/platform/msm_sdcc.1/by-name/tz mmcblk0p9 '
-e 's block/platform/msm_sdcc.1/by-name/userdata mmcblk0p27 '
"$@"
;;Let me know if I should change any of this