LG Canada refuses D803 LP update - any chance of using D800 ? - G2 Q&A, Help & Troubleshooting

According to this and this, LG Canada is refusing to update the G2 to Lollipop or release the kernel.
I'm wondering if anyone knows whether the D800 source code is close enough to the D803 to be usable ?

sandys1 said:
According to this and this, LG Canada is refusing to update the G2 to Lollipop or release the kernel.
I'm wondering if anyone knows whether the D800 source code is close enough to the D803 to be usable ?
Click to expand...
Click to collapse
what you could do :
get a gitcompare on the kernel defconfig, d803 vs d802 in kitkat source, which is available. I know in kitkat, one could take a d802 rom and flash a d803 kernel on top and be done.
http://opensource.lge.com/osSch/list?types=ALL&search=D803
So, it might be VERY similar.
Then, verify the blobs in vendor. and see if anything is different.
THEN head over to mahdi rom thread and ask around for dr87's patch for different models. Somebody, somewhere already knows all of this. NOW, if the radio is different for lollipop, then houstonn, we have a problem. I'm not building any roms now. There's just too much time involved in getting it all together and building and xda and all. But this would be my approach.
diffchecker:
https://www.diffchecker.com/ujexruvv

mathsz said:
what you could do :
get a gitcompare on the kernel defconfig, d803 vs d802 in kitkat source, which is available. I know in kitkat, one could take a d802 rom and flash a d803 kernel on top and be done.
http://opensource.lge.com/osSch/list?types=ALL&search=D803
So, it might be VERY similar.
Then, verify the blobs in vendor. and see if anything is different.
THEN head over to mahdi rom thread and ask around for dr87's patch for different models. Somebody, somewhere already knows all of this. NOW, if the radio is different for lollipop, then houstonn, we have a problem. I'm not building any roms now. There's just too much time involved in getting it all together and building and xda and all. But this would be my approach.
diffchecker:
https://www.diffchecker.com/ujexruvv
Click to expand...
Click to collapse
thanks for the reply - I'm doing this for the first time (though I'm a professional programmer on Linux). could you help out in clarifying what do you mean when you say defconfig diff. The kernel source for the KK DD803 has these defconfigs : http://pastebin.com/qZh4c8Nu
secondly, to verify the binary blobs - do I need to download the entire source (as opposed to just the kernel) ? I'm not sure how to do this via commandline - do you have a diff command ?

Hi. Below lolipop distro is working on d803
http://forum.xda-developers.com/lg-g2/development/rom-vk-v5-0-f320s-l-k-d80x-vs-ls980-l01f-t3134093
I am getting network disconnects, but probably something we can work through together. together Everything else seems to be working pretty well

sandys1 said:
thanks for the reply - I'm doing this for the first time (though I'm a professional programmer on Linux). could you help out in clarifying what do you mean when you say defconfig diff. The kernel source for the KK DD803 has these defconfigs : http://pastebin.com/qZh4c8Nu
secondly, to verify the binary blobs - do I need to download the entire source (as opposed to just the kernel) ? I'm not sure how to do this via commandline - do you have a diff command ?
Click to expand...
Click to collapse
sorry mate, that got lost.
I think someone tried it and said it did not work.
my g2 is dead. this is a quick diffchecker
https://www.diffchecker.com/
it will show differences between d803 and d802. I'd compare kitkat sources and apply to lollipop.
Binary blobs : The blobs are in the vendor part of the source.
You've got the Rom (ie, cm)
then, the device tree (d80x)
the kernel tree (d80x)
and then, the vendor tree. Blobs or what you would call drivers are in the vendor tree.
I'm not gonna detail everything, there are TONS of "cook your own rom" tutorials on xda. The vendor files might prove a problem. But if you're lucky, the d802 should work. You'd need to edit out the sdcard in device tree too.
Sounds easy when written, I just don't have the patience to do it anymore. It is VERY time consuming.
cheers mate

Related

[Q] What is OpenSource Code Distribution?

I was looking for Sprint's kitkat update and came across LG's OpenSource Code Distribution. I'd post the link, but the software here won't let me. It has kernel and Android ZVC for download. Is this the kitkat update? If it is, how do I install it?
Thanks.
rklurfeld said:
I was looking for Sprint's kitkat update and came across LG's OpenSource Code Distribution. I'd post the link, but the software here won't let me. It has kernel and Android ZVC for download. Is this the kitkat update? If it is, how do I install it?
Thanks.
Click to expand...
Click to collapse
if you are speaking of this https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=LS980 then that is the source for the ls980 and the ZVC is kk but I do not know how would you flash it have you downloaded it so we can know what's inside the zip, it might just have the files needed to compile a rom
yes indeed
Yes, it is the source code. Plus there is a readme file with instructions on how to compile it into a rom. My point was that LG has given it to Sprint to compile after March 25th, the date on the files. So we should get it very soon.

[Q] Possible issue with LG G2 ( vs980 variant )

Since I can't find the answer I decided I'd post here in hopes that someone might know what's going on.
Which bootstack / modem is OMNI built for? 12b? 24a? 25b? 26a?
As I'm currently on the 25b bootstack and have no issues installing CM / PA / Liquid
but if I attempt to install OMNI , nothing happens. Does not run.
1. did I wipe all partitions correctly? yes
2. did I check the md5 sum? yes
3. am I using the current nightly? yes ( and the previous 3 nightlies all give me the same result )
I'd like to give this rom a try , but given that it refuses to run , I'm a little sad
if this question was in fact already answered, I apologize , my search-fu was not up to snuff.
alastrionia said:
Since I can't find the answer I decided I'd post here in hopes that someone might know what's going on.
Which bootstack / modem is OMNI built for? 12b? 24a? 25b? 26a?
As I'm currently on the 25b bootstack and have no issues installing CM / PA / Liquid
but if I attempt to install OMNI , nothing happens. Does not run.
1. did I wipe all partitions correctly? yes
2. did I check the md5 sum? yes
3. am I using the current nightly? yes ( and the previous 3 nightlies all give me the same result )
I'd like to give this rom a try , but given that it refuses to run , I'm a little sad
if this question was in fact already answered, I apologize , my search-fu was not up to snuff.
Click to expand...
Click to collapse
Jake is currently working on a major rebase to be compatible with 4.4 bootloaders/basebands.
The reason it has taken so long is that 4.4 bootloaders/basebands require LG's 4.4 kernel source, and LG's 4.4 kernel source had LOTS of problems with somehow causing permanent unrecoverable screen damage on various devices.

Porting D855 Lollipop Update for D850

Hello,
Working on porting .kdz Lollipop update file for D855 for D850. When I try to extract files from .kdz file, it says the headers are incorrect. I have tried just about every .kdz file extractor I can find, but all read the same error.
The link to the file:
http://forum.xda-developers.com/lg-g3/general/leak-lollipop-5-0-android-l-d85519h00-t2934345
When a solution is found, I will post the ported ROM as soon as possible.
I am posting here because I do not have 10 posts, therefore I can not post in the Development section.
Thanks,
Christian D
Isn't the problem with it not running for the D850 missing kernel sources? If we get a leak or an official for the D850, then it would be fixed. At least as that's what I was getting from reading through Cloudy 2.0 thread.
Yes that's the issue. With no stock kernel for D850 lollipop it will be near impossible to get a stable port running. You are correct in that you read that in Cloudys thread. He actually says that verbatim and that he will not release lollipop Cloudy without the official kernel. Unfortunately, like always, AT&T has to lie to themselves for months and make themselves believe people actually use their ****ty bloatware before they release the update. Tbh I think my next device is going to be a nexus device. I know they have had issues with lollipop but Google is fast to patch for the most part.
At least we don't have Verizon. Verizon customers won't get their update until Verizon figures out how to get lollipop to burn the Verizon logo into the user's retina thus completing the objective theyve been going after for years with the ever increasing amount of logos on their devices.... All their user will ever see is the Verizon logo. *queue ominous monk chant*

[Q] Support for LG G3 with Cyanogenmod 12?

Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Yup, i confirm, doesn't work on lg g3. Pitty.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
WOW great news!!
Thank's very much :victory:
mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:
Any progress ?
ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/
Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!

Port of lineageOS

Hello Guys,
Today I woke up with a new idea; I want to port LineageOS to the LG V20 version H990DS. I was tinkering with this idea for about one year, but never actually wanted to make the step. Until today. I used LineageOS and CyanogenMod since 2012.
The reason why I want to create the first port is because I have the time at the moment, so why not help the community? I do have four years of programming skills C/C++. Run Linux as daily driver etc... Do know how to use git, linux, autotools etc... The tricky part however is: I never compiled a Lineage OS rom from source and I don't think the compiling would be a problem, but the LG V20 H990DS isn't officially supported. My question is: Where do I start to program? How can I compile and build a working Lineage OS for the LG H990DS. Are there any good website I can read from?
I saw this:
https://www.youtube.com/watch?v=MGI3NSJFtKA&feature=youtu.be
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
https://www.reddit.com/r/LineageOS/comments/6iie9l/how_to_compile_lineage_os_141_for_unsupported/
https://www.reddit.com/r/LineageOS/comments/684qkp/help_noob_compile_lineageos/
So to make it easy: I want to program a working LineageOS for the LG H990DS, but don't have any understanding about where to start. I do have four years of programming skills, not so much, but know C and C++ well.
Thanks in advance,
Maurice
English isn't my native language, sorry for grammars.
someone help this man up.
Did you check the existing LineageOS thread?
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/post74550386#post74550386
If you want to help, I'd suggest asking him if there's anything you can do.
Thank you for your response. I do watch that thread, because I want lineageOS for the h990ds device. The problem however is that I don't want to jump right into the code. I want to know what I am doing with each line of code. At the moment I think I have to change some things in the kernel so that it can boot, but I don't know if that's true. And there is so many documentation about how to compile lineageOS, which I don't want to do. I want to program and compile lineageOS. Every tutorial skips the program parts and just compiles lineageOS.
So maybe a good programmer can give my some advice? Where to start and where can I find some documentation?
Best regards,
Maurice
Welcome!
First off, I recommend using Ubuntu 16.04 (I personally use 16.10 however). Be sure to follow the guide you linked from chef central carefully.
For the dual SIM variant, I don't believe any current source exists. Although with the similar hardware and if you have decent skills, you could get it going.
Take a look at the existing v20 trees:
V20-common: https://github.com/LineageOS/android_device_lge_v20-common
Msm8996-common: https://github.com/LineageOS/android_device_lge_msm8996-common
H918 (as a reference): https://github.com/LineageOS/android_device_lge_h918
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8996
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Those are the basics to check out. Now I did see someone converted the H918 tree to H990. Here's a link to that for reference: https://github.com/android-device-lge-h990/android_device_lge_h990
You will definitely need to make a custom defconfig in kernel sources. The device tree changes should be rather easy. You'll need to pull vendor files from stock and import the drivers and dts files from stock kernel source. If/when you get a working kernel and device trees there's a 99% chance you will need to Port other drivers and vendor files as stock files don't play nice in aosp. If I were you, I'd start looking through commit history on GitHub to see how the other devices we're brought up. That is how I learned everything.
Also, git will be your best friend when bringing up large projects, like kernel. Learn git, get comfortable with it. Cherry-picking and merging is what keeps us going.
Best of luck!
I suppose you could say there are dueling work-in-progress H990 trees since the other one is: https://github.com/x86cpu/android_device_lge_h990
The one you pointed to is mine. I was hoping for some collaboration with @x86cpu on there (in theory @x86cpu also has permissions to modify that repository, assuming I've set things up correctly). While the initial steps have been done, it is not finished! Some issues are left for getting LineageOS operational on H990 devices.
Of crucial note the modem fix in its current form is unacceptable to LineageOS (despite working). I've got two variants of one solution almost ready, but they're yet ready.
Thank you for your answer and I will look into it. I sure hope that I can help you some day, but first I want to understand the repository. After that I will help you both to code.
Really thank you and I will do my best to catch up with you.
As for the Ubuntu version. I personally use arch Linux (with plasma), because I like it more than Ubuntu. I don't think that's a problem and else I will compile the Ubuntu programs to arch. And I know my way around got. Use it for about 4 years now and now what merging/branching rebasing etc means and know how to use it.
@emdroidle I could help

Categories

Resources