I've not watched development like this before, mainly because i've only had my evo since august and things were already running for a while.
What I'm wondering though is what the usual time frame is from new version release to fully functional rom? Looks like we are getting close with only a few things missing at this point for ICS.
Thanks
It could still be a long time before we see a final build with everything working since the evo4g is not officially supported for ICS the devs are having to code and compile drivers from scratch, if you've ever written any kind of code from the ground up then you know how long it can take you run into unforeseen errors, problems with code, typos that need to be corrected etc.
Hi, I managed to build Cyanogenmod 11 for my device based on this guidehttp://wiki.cyanogenmod.org/w/Build_for_ks01lte#How_to_Build_CyanogenMod_.0Afor_Galaxy_S4_LTE-A_.28GT-I9506.29_.28codename:_ks01lte.29. The docs for porting omni seems to be really sparse and my device is an rather obscure model (GT-!9506). I am wondering what exact changes(other than the repos) do I have to make to the steps used to build Cyanogenmod in order to build Omni ?
Infinitelomeres said:
Hi, I managed to build Cyanogenmod 11 for my device based on this guidehttp://wiki.cyanogenmod.org/w/Build_for_ks01lte#How_to_Build_CyanogenMod_.0Afor_Galaxy_S4_LTE-A_.28GT-I9506.29_.28codename:_ks01lte.29. The docs for porting omni seems to be really sparse and my device is an rather obscure model (GT-!9506). I am wondering what exact changes(other than the repos) do I have to make to the steps used to build Cyanogenmod in order to build Omni ?
Click to expand...
Click to collapse
Depends on the device. Sometimes the device trees and kernel need very little modification.
In other cases, CM has commits buried in various places to handle "Samsungisms" (various odd quirks), some of which we may be missing for certain things to function.
On our wiki, we used to have some info highlighting specific things we did differently than CM, but many of those were handling "pure AOSP/CAF" vs CM's "hybrid AOSP/CAF" stuff for Qualcomms, and many of those issues disappeared in 5.0
Unfortunately much of the documentation never really got updated with 5.0 - 5.0 was a complete and total disaster/failure for us to be honest. We had a lot of team members tied up with other things/burned out for the entirety of the 5.0 cycle.
5.1 looks like it'll turn out much better but it's going to take some time for things to settle out.
In general, there's always a lot of trial and error for a device maintainer, which is partly why there aren't detailed step-by-step guides - it's partly that there is no way to write such a guide as each device is different, and partly because if someone has hope to maintain a device properly in the long run, they need the patience and investigative/troubleshooting skills to figure out a lot of this on their own.
In general, if you drop by on IRC when something goes wrong, people can try to give you pointers, but as i said - the beginning of the 5.1 cycle is going to be a time where lots of things break on occasion.
Hello,everyone!
I just got this superb-looking device,and I was wondering about something.
I see that the ability to root and install TWRP is present on the phone,but what about the source code and custom roms?
I am interested in the source code in order to try(a big emphasis on TRY) to get CM13 on this phone,but I do not know where to start. .-__-.
Can anyone point me the right way? I am a bit tired of having to test the living crap out of my phone and hard-brick it several times before actually getting somewhere(I just got it,don't want to blindly throw myself into anything because I am prone to killing my phones when I do so).
I am also asking this because I am used to seeing 2 same-looking things on new forums,not knowing which one is better.
Oh,and is there any "dangerous" thing one should avoid?
Hello everyone, I have recently started trying to port UBPorts (formerly Ubuntu Touch) to my trltespr, I get the code to start compiling but I keep hitting errors.
https://forums.ubports.com/topic/477/porting-to-samsung-galaxy-note-4-sm-n910p
Is the link, in case anyone wants to follow. I created this thread to see if anyone else is trying to do the same thing as well as serve as a general progress update. Im sorry if this is in the wrong spot, but seeing as UBPorts isnt exactly and android OS I wasnt sure where to put it. I know some people may ask why, the simple answer, Im tired of Android and want something different. I am also contemplating porting Halium, if anyone has any interest in helping with either port, or is currently trying and would like to consolidate their efforts with me, please let me know, Ill update this post as well as the thread I linked with updates on what Im doing and how its all going.
Thanks for Reading.
Sorry for the double post, but I managed to get Halium to compile, the kernel to boot, and thats about it so far, running into an issue with getting the rest on the phone, I can post the files and any info to get Halium working if anyone wants it, but that is gonna be when I have a working gui (features are a different story)
#== Edit ==#
Halum is booting into pre-boot, it is having trouble from there though. It mounts the images (system.img and rootfs.img) just fine in the pre-boot environment, however if I try to continue the boot process from there, the phone kicks me out, then refuses any new attempts to connect. I am working on getting my git repo synced with my local repos so anyone that wants to help can do so.
#=== Edit 2 ===#
I managed to get all the files on the phone, phone successfully gets to pre-boot environment and that is where everything falls apart, I'm trying to figure out the root cause of the issue, however its going to be slow going with the Holiday season apon us (those who celebrate at least) I will update when I have something to update with (hopefully a partially working port, but no promises)
Sorry for a third post, I hope mods are understanding since I haven't received any replies to this thread.
So Update since it's been awhile, I now have halium able to boot, I get ssh access and when I ssh in it says Ubuntu 16.04, that's the good news. The bad news now, I still get no GUI on the phone screen, and it appears to be a mount issue which I am working on. I can release the files I have now if anyone wants them, however I prefer to wait till I have a working GUI.
Poll Time,
Once I get ubports to boot and give me a GUI should I work on getting a Ubuntu dock setup working or try and port something like LuneOS, Plasma Mobile, or even sailfish to the note 4? Let me know your thoughts as well as any thoughts you have for ubports on a note 4.
Cheers
Do you try ubports / halium 7.1... Msybe with sources here: https://github.com/underscoremone/unified_android_device_samsung_trlte
Don't know, but maybe you get more support from community
I actually have made a lot of progress from my last post on here. I am actually in the telegram groups which have given me a lot of useful info, I am still trying to get the GUI working though. Thank you for the reply and keep an eye out for a update in the next few weeks (depending on my free time)
jasousa said:
Do you try ubports / halium 7.1... Msybe with sources here: https://github.com/underscoremone/unified_android_device_samsung_trlte
Don't know, but maybe you get more support from community
Click to expand...
Click to collapse
I'm in the same stage... trying get GUI. SSH is OK. My device is samsung galaxy J5 2016
Telegram, in fact, is the best place to get help, and the guys behind the ubports and halium are very good.
Regards
Sent from my SM-J510FN using Tapatalk
Update:
I have managed to get Ubuntu to boot and bring up SSH, still no GUI but the android container does start and stay running now. I have a list of things I can try from here to see if I can get a GUI that with any luck I can get working today (depending on RL) I am hoping to have this working and giving me a GUI by the U.S. Christmas holiday. I will post the files as they are now if anyone is interested.
Update Edit:
I finally got the Ubuntu Touch boot screen, It hangs there ATM which I will be working on shortly, I still have a long ways to go before I'd consider it "complete" but I hope it will be completed enough to use as a daily test platform, I could use people to help with testing if anyone is interested.
So Big Update:
I got past the boot screen, I now have a full GUI with working WiFi and working touchscreen. Not much else is working. I could definitely use people to test this distro, so if you are interested in using Ubuntu Touch on a Galaxy Note 4 PM me and I'll get you setup for testing. I only have a sprint variant of the note 4 but if you have a different variant it shouldn't take much to get that working as well.
So the list for anyone interested/curious
Working:
WiFi (doesn't auto-connect)
Touchscreen
GUI
File Access
USB networking
Not Working:
Cellular (ofono is having permission errors)
Bluetooth (haven't looked at yet)
S-Pen (kernel disables it for some reason)
Rotation (sensor values aren't seen)
Audio (haven't looked at yet)
Status Light (works with hybris-boot, not halium-boot)
Vibration/Haptic Feedback (works with hybris-boot, not halium-boot)
I'm sure I forgot something, but that's off the top of my head. I welcome anyone volunteering to help move items from not working to working, if not then I will eventually get there, but don't expect this to be a complete ROM until next year at the earliest.
tigerpro357 said:
So the list for anyone interested/curious
but don't expect this to be a complete ROM until next year at the earliest.
Click to expand...
Click to collapse
Does any other stylus respond as a Wacom device?
harrypotnik3 said:
Does any other stylus respond as a Wacom device?
Click to expand...
Click to collapse
Sorry for the delayed answer, I only have the S Pen so I cant say for sure.* The capacitive stylus' that you can buy basically anywhere do work though.* I haven't really had time to continue my work on this port, I have made some progress as I can get rotation to work, and there is a lot of things that work in the terminal however they don't carry over to the GUI for some reason.* I can release the files here if you want to try other stylus' and let me know what works for you.
Hello; I have an old Note 4, T-Mobile (US) variant that I'd like to do something interesting with and UBPorts seemed promising. Then I found your thread. How are things going with this project? I would love to test this for you on my device if you think it might be working. Thanks for the all the good work!
There is a T-Mobile port in progress already, there are a couple things left to resolve for this port as well, how would you like to get started?
Its always nice to se new things for our phones.
This one is really a breakthrough for the Note 4
Having a Ubuntu touch working on Note 4 is a whole new level in development in Android phones.
We are very lucky to have so charismatic devs among us, even better if they are working on our phones.
For that, we are thank full @tigerpro357, for what you are doing here.
I know its just the first steps, I know that these are just the beginning, but they are showing us what wonderful things we can expect in the future.
Thank you ,
KUDOS
post was doubled
I'm not really sure... I guess I'd just like to flash it on the phone and see what happens, what works and doesn't.
ccellist said:
Hello; I have an old Note 4, T-Mobile (US) variant that I'd like to do something interesting with and UBPorts seemed promising. Then I found your thread. How are things going with this project? I would love to test this for you on my device if you think it might be working. Thanks for the all the good work!
Click to expand...
Click to collapse
ccellist said:
I'm not really sure... I guess I'd just like to flash it on the phone and see what happens, what works and doesn't.
Click to expand...
Click to collapse
Ok, I can tell you whats currently not working, or working, I will advise you this is currently not ready to be a daily driven ROM, in call audio doesnt work, YT causes crashes, camera causes crashes (cause I havent finished applying the patch to my repos) theres a couple other things as well, I need to make a propper list for everything rather than go off memory
Thanks so much for the info. Not to worry, I wasn't planning on using it as a daily driver, I really just want to play around with it, kick the tires so to speak.
logosA said:
Its always nice to se new things for our phones.
This one is really a breakthrough for the Note 4
Having a Ubuntu touch working on Note 4 is a whole new level in development in Android phones.
We are very lucky to have so charismatic devs among us, even better if they are working on our phones.
For that, we are thank full @tigerpro357, for what you are doing here.
I know its just the first steps, I know that these are just the beginning, but they are showing us what wonderful things we can expect in the future.
Thank you ,
KUDOS
Click to expand...
Click to collapse
Very nice
UT on note4... You guys are amazing.
Sent from my SM-N915F using Tapatalk
Hi everyone,
This may be a rather naive and noobish question but I am curious if it is possible to "port" LG framework to be used under LOS 15.1 so that native LG apps (like their camera app) could run under LOS. And if so, what is GENERAL process for doing so?
I have a pretty strong Linux background (kernel, etc) but admittedly I am not too sure what people are really talking about when they say they are porting an app to work on another ROM or AOSP.
Does it mean figuring out which native libs an app depends on, and gathering them all up and putting them in the right place in the other ROM? I understand apps and probably even framework libs would likely have to be built against the correct android release to have a good chance of working. But it strikes me that since an Oreo (albeit 8.0) stock H918 ROM just dropped... maybe that would help some?
How do people generally figure out the libs an app needs? Just looking at logs to see what an app can't find, or are there tools that can help? (like using ldd against C / C++ apps)
Thanks for any advice. I am not looking for people to do the work for me, just maybe saying what can or can't be done or maybe pointing in the right direction.
Thanks,
VelosterM14
And I guess I have my answer, at least from the general community at large.
All I can offer, is that a dev (jazzk) did something like this for the Galaxy S2. It was called Chameleon ROM. And it was perfect. Perhaps there is something there that can give you an idea of the way forward?
Thanks - it may actually help. I also found some other threads not really specific to LG but with info about the .xml manifests, checking logs to look for missing libraries, etc.
I'll see what I can come up with, it will be really slow because this is my first go at anything like this. But I do have about 20 years of Linux under my belt.
Also it is starting to look like the real problem with my camera on the spare H918 I have may not be LOS 15.1 or any of the various camera apps I've tried, but rather something wrong with the main rear camera sensor itself. Not sure, but about to find that out by taking this one back to stock and seeing if it works better there or not. I need to test some things under pure stock anyway like the Tmobile unlock app, etc.
I have other LG stuff I'd like to try to get working also, not just the stock camera. I'd really like to figure out how to either get involved with 2nd screen work or get more functionality like the native LG second screen software has working -- all the notifications features this 2nd screen has in stock setup are pretty nice. I like that what we have so far on LOS 15.1 is there and I'm sure even that was a lot of hard work, but I'd like to get more things working on that 2nd screen and maybe I can learn enough to help out.
So even if the camera is bad on this spare H918 and I either get the phone replaced by the eBay seller or I replace the camera sensor myself, I will eventually end up looking into all of this anyway. Just may be a long time before I get anywhere.
EDIT: It was the camera on this phone, it is equally bad on stock H91810P ROM with a full factory reset.
Sorry you have not seen the support needed here - you asked some incredibly spot on good questions a while back, and I just saw this post now.
If you or anyone else knowledgeable is reading this, please do keep the community updated on the progress for where all this is currently at.
VelosterM14 said:
And I guess I have my answer, at least from the general community at large.
Click to expand...
Click to collapse