Related
Hey, did anyone successfully get ubuntu touch on an lg g2? I've tried for weeks and still can't... Help?
kuksenko said:
Hey, did anyone successfully get ubuntu touch on an lg g2? I've tried for weeks and still can't... Help?
Click to expand...
Click to collapse
I started looking into it yesterday hit a major roadblock when noticed that LG G2 is CM-11.0 based and Ubuntu touch is CM-10.1.
Talked to Rsalvetti he said that hes been working on something and should have a update next week.
Like to help out
I have an LG G2 and would like to pitch in on the development effort. Also have ordered a G Pad 8.3 so I should be able to piggyback if I work on both devices. Love to see a full featured Ubuntu on these devices.
LG G2 korea version F320l Help me all
my phone lg g2 f320l no recovery mode no charge no bootloader. Computer to usb device QHSUSB_Bulk [Qhsusb_dload] help me ]
End up needing someone to test it, when something is made, I can help. I have the G2 ls980.
Sent from my G2 using Tapatalk 4
what's the status on this?
I just got the source downloaded and started playing around a bit....
Ubuntu touch on back burner?
I was excited to try and pitch in on this but it seems like the Canonical drive for Ubuntu touch development has lost steam lately. I had read somewhere that priorities had shifted and it was not receiving the same attention and effort that it was during Q3 2013. I'm still excited to contribute but it doesn't seem like there is a lot of progress on the project on a regular basis. That could just be my impression but I don't see the progress spreadsheets getting updated for the most popular phones and tablets shipping over the last 2 quarters.
Last time I started working on this they where merging all the phablet codebase with the android 4.2 framework and working on installing their own code review system (gerrit) for phablet.
Haven't swing around to ask in the IRC but rsalvetti could tell what's the status on a phablet build for 4.2
skay said:
I was excited to try and pitch in on this but it seems like the Canonical drive for Ubuntu touch development has lost steam lately. I had read somewhere that priorities had shifted and it was not receiving the same attention and effort that it was during Q3 2013. I'm still excited to contribute but it doesn't seem like there is a lot of progress on the project on a regular basis. That could just be my impression but I don't see the progress spreadsheets getting updated for the most popular phones and tablets shipping over the last 2 quarters.
Click to expand...
Click to collapse
Well, there's a difference between their official builds for Nexus devices and community builds. There's been a lot of work on the official builds lately. You can see improvements on those supported devices every day. It's just logical that Canonical cannot take care of tens or hundreds of devices. Therefore they focus on a small selection. If you don't see any progress on a particular, officially not supported device, it's not Canonical's fault.
By the way: They rather speed up development. To manage this, they even quit their cloud storage service: http://beuno.com.ar/archives/318
I talked to Ricardo Salvetti he told me that you can check out a branch of their ubuntu modified android framework with this command.
repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1
I am in the process of figuring out now how to get libhybris and get the old brunch command working.
Haven't gotten on IRC but if you get on it through the week during the day i am sure they can help us out.
Ill let you guys know if i have any luck getting the device,kernel and other repositories checked out.
annerajb said:
I talked to Ricardo Salvetti he told me that you can check out a branch of their ubuntu modified android framework with this command.
repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1
I am in the process of figuring out now how to get libhybris and get the old brunch command working.
Haven't gotten on IRC but if you get on it through the week during the day i am sure they can help us out.
Ill let you guys know if i have any luck getting the device,kernel and other repositories checked out.
Click to expand...
Click to collapse
That's excellent that Ricardo Salvetti gave you assistance to get going on development for G2. I didn't get in touch (not pun intended) with him yet even though
I have been on the Ubuntu touch IRC channel to try and follow current development activity and news. As for the previous post, I don't expect Canonical to do
any significant development except on the original 4 (now 3) platforms that they planned to support with corporate development. I see they have discontinued
support for the Samsung Galaxy Nexus and so now are down to 3 devices. I made my comment on slow development pace since I didn't see much being
added or updated to many of the most popular 2013 phones/tablets that you would expect to see get a decent amount of community dev support. Furthermore,
since UT is based off of CM10.1 it is difficult to try and support new devices since CM10 is now basically in maintenance with CM11 receiving most of the dev
support for newer devices. I love Canonical and there commitment to open source Linux development but it just seems like the Ubuntu Touch development is
facing an uphill battle to remain relevant when newer devices are becoming really difficult to support due to the dated started point for CM based branch
development. At this point I would love to hear Canonical talk about a strategy to shift newer Ubuntu Touch development to a CM11 base if that could be
managed.
skay said:
That's excellent that Ricardo Salvetti gave you assistance to get going on development for G2. I didn't get in touch (not pun intended) with him yet even though
I have been on the Ubuntu touch IRC channel to try and follow current development activity and news. As for the previous post, I don't expect Canonical to do
any significant development except on the original 4 (now 3) platforms that they planned to support with corporate development. I see they have discontinued
support for the Samsung Galaxy Nexus and so now are down to 3 devices. I made my comment on slow development pace since I didn't see much being
added or updated to many of the most popular 2013 phones/tablets that you would expect to see get a decent amount of community dev support. Furthermore,
since UT is based off of CM10.1 it is difficult to try and support new devices since CM10 is now basically in maintenance with CM11 receiving most of the dev
support for newer devices. I love Canonical and there commitment to open source Linux development but it just seems like the Ubuntu Touch development is
facing an uphill battle to remain relevant when newer devices are becoming really difficult to support due to the dated started point for CM based branch
development. At this point I would love to hear Canonical talk about a strategy to shift newer Ubuntu Touch development to a CM11 base if that could be
managed.
Click to expand...
Click to collapse
cm 11.0 is 4.4.2 the reason I had to wait for a while for development on the LG G2 was exactly that they did not supported CM11 with the command I posted before they now support CM11 Devices and I believe they moved their core 3 devices to CM11 already.
Exactly for the reason you mentioned about CM10 being in maintenance.
annerajb said:
cm 11.0 is 4.4.2 the reason I had to wait for a while for development on the LG G2 was exactly that they did not supported CM11 with the command I posted before they now support CM11 Devices and I believe they moved their core 3 devices to CM11 already.
Exactly for the reason you mentioned about CM10 being in maintenance.
Click to expand...
Click to collapse
Well that is great to hear. I guess I haven't been following UT as closely as I probably should. I'm very eager to pitch to get some development underway on LG G2 and LG G Pad 8.3. I was just discouraged because these newer platforms all have been moving onto KitKat and UT was using JB (CM10.1) base for development so it seemed like an uphill battle even with a lot of help from Canonical devs. Since they are moving UT development up to CM11 these and other platforms should be a much easier development task since work on CM11 and 4.4.2 AOSP projects is very active, hence getting questions answered should be a lot easier.
Got the easy part done building ubuntu touch.
Now I am working on getting it to boot it is really hard since I have no way to diagnose why it's stuck on the LG logo.
Does anyone know how to build a serial usb cable for lg devices I did one for samsung and it helped debug issues in the past.
annerajb said:
Got the easy part done building ubuntu touch.
Now I am working on getting it to boot it is really hard since I have no way to diagnose why it's stuck on the LG logo.
Does anyone know how to build a serial usb cable for lg devices I did one for samsung and it helped debug issues in the past.
Click to expand...
Click to collapse
Looks like the Andropod interface can get you USB debugging. Post back if you wind up using it for UT development on the G2.
http://m.youtube.com/watch?v=XBZM4QW5iB4
skay said:
Looks like the Andropod interface can get you USB debugging. Post back if you wind up using it for UT development on the G2.
http://m.youtube.com/watch?v=XBZM4QW5iB4
Click to expand...
Click to collapse
Thanks I found it when I tried getting it working. But that does not appear to mention it's for the kernel it's supposedly used for debugging applications.
Looking at the block diagram I don't think it will work since basically that device is a USB to serial command adapter.
While I need the phone to output serial (done in kernel) and to figure out which wiring is the one to read that serial output.
I could try setting up a framebuffer but i gave it a quick attempt and it didnt work.
Additionally I haven't figured out how to flash the kernel without having to use the ubuntu installer. and that means that I have to reinstall everything from scratch and that takes about 40 minutes.
If I could figure out the command to flash the kernel I could do a adb push kernel && adb shell flash kernel. And that would take 3-5 minutes.
Thank God I went with the nexus 5
sent via multirom with power of my UBER? HAMMER?HEAD
4.4.2 base out for AOSP roms for LG-G2
Hay there! please check out the LGG2 forum there they get 4.4.2 base for aosp roms.... like SLIMKAT is now based on 4.4.2 base.. so now you can get that thing try to port to LG G2.. I guess
Any update on this?
This still alive vs980
So with marshmallow releasing recently on the note 4, (for most) whats the opinion of staying stock or rooting and rom'ing for Nougat? If not already possible im sure it will be very soon. I did like a few features of 7 so if there was a stable ROM i might consider finding a daily driver myself. Otherwise i have been very happy with 6.0.1
Maybe ask the same question in a month. I think the code was barely released.
I'm pretty sure N is out for Nexus devices.
Actually I just saw this: http://techxat.com/android-devices-getting-cm14-nougat-rom-big-list/
So we are getting CM 14/Nougat. It's a matter of, when. Trust me, don't ask that. It'll happen when it happens. Everyone around here basically works for free. Some take donations. If someone comes up with a Nougat ROM sooner than someone else, whenever that is, then great, but we'll see at least CM 14 at some point, maybe another Nougat ROM as well from another author.
Had anybody noticed this? Maybe some dev willing to work with it? Below it is the link. Just search for can will do =)
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
From what I can tell there is really no difference in the kernel sources. I can use a kernel built on CAN-L01-11 source when I run LOS, but my device is AL10, I would guess it works the other way around also. Maybe someone with more time can compare the original sources released for both and see if anything is different. If not, hopefully LOS 14 will come to life soon for our device.
I am in the middle of switching jobs (very time consuming as a foreign resident in China). Good news is I will be making more money and will be able to build a build machine in the next few months.
wangdaning said:
From what I can tell there is really no difference in the kernel sources. I can use a kernel built on CAN-L01-11 source when I run LOS, but my device is AL10, I would guess it works the other way around also. Maybe someone with more time can compare the original sources released for both and see if anything is different. If not, hopefully LOS 14 will come to life soon for our device.
I am in the middle of switching jobs (very time consuming as a foreign resident in China). Good news is I will be making more money and will be able to build a build machine in the next few months.
Click to expand...
Click to collapse
I really think that there is no difference too, as we already tested with @#Henkate builds. I just specified the models to be precise, but my device (caz-tl10) would probably be able to run a LOS (or derivative) ROM built for these models I mentioned. Maybe, the thing to be aware is the partition size for our models, but as system probably has the same size, it wouldn't be a major thing.
I really want to learn and to build, but I don't have enough storage for sources and will have to wait a bit. It would be really nice to have a LOS/AOSP build with updated software
Would be nice to see Slim on the Huawei, I bought the thing simply because of the size being close to the Nexus 5. Loved that thing, but has been given to my son (he is 2 and a half, so no wifi or calling, but it runs the games he wants).
Vinnom said:
I really think that there is no difference too, as we already tested with @#Henkate builds. I just specified the models to be precise, but my device (caz-tl10) would probably be able to run a LOS (or derivative) ROM built for these models I mentioned. Maybe, the thing to be aware is the partition size for our models, but as system probably has the same size, it wouldn't be a major thing.
I really want to learn and to build, but I don't have enough storage for sources and will have to wait a bit. It would be really nice to have a LOS/AOSP build with updated software
Click to expand...
Click to collapse
Well, there must be differences in the kernel source between CAZ-TL10 and CAN-L11/L01 since those models aren't mentioned at CAZ's source on huawei's website. For example, at the source code of EMUI 4.1, both L01 and L11 are mentioned, so they use the same kernel.
Last night I've updated the defconfig by looking at a commit from Moto G4 Play (harpia), at the defconfigs of Xiaomi Redmi Note 4 (mido), Moto G5 Plus (potter) and of course, the defconfig from CAZ-TL10. You can see the commit here. Other changes might be needed too, but I'll see about that later.
You can use Google Cloud Platform for building, as I'm doing now. You only need a credit card and 1$ (which they'll give back in 1 day or so).
wangdaning said:
Would be nice to see Slim on the Huawei, I bought the thing simply because of the size being close to the Nexus 5. Loved that thing, but has been given to my son (he is 2 and a half, so no wifi or calling, but it runs the games he wants).
Click to expand...
Click to collapse
Slim it's on my "to do list". If I'll manage to build los14.1, then I'll build Slim7, otherwise Slim6.
Last night I've started to build LOS14.1 and fixed some minor build errors which you can see on my github, but then I've ran into this build error after ~30 mins of building (usually it takes 1h 30m to finish a build, thanks to GCloud platform...). I've searched a bit and found a post where a dev has the same issue and is saying that hwcomposer isn't compatible with the kernel source and that must be because I'm still using MM source since Huawei didn't publish N source for L01/L11. There's a cm14.1 branch left by Grarak and there's a commit which contain something which appear in the build error. He might tried to build cm/los 14 and ran into the same build error, I don't know. But I'll try that commit today and I'll also do more research. I'd like to build it successfully today, but I'll see how it goes.
#Henkate said:
Well, there must be differences in the kernel source between CAZ-TL10 and CAN-L11/L01 since those models aren't mentioned at CAZ's source on huawei's website. For example, at the source code of EMUI 4.1, both L01 and L11 are mentioned, so they use the same kernel.
Last night I've updated the defconfig by looking at a commit from Moto G4 Play (harpia), at the defconfigs of Xiaomi Redmi Note 4 (mido), Moto G5 Plus (potter) and of course, the defconfig from CAZ-TL10. You can see the commit here. Other changes might be needed too, but I'll see about that later.
You can use Google Cloud Platform for building, as I'm doing now. You only need a credit card and 1$ (which they'll give back in 1 day or so).
Slim it's on my "to do list". If I'll manage to build los14.1, then I'll build Slim7, otherwise Slim6.
Last night I've started to build LOS14.1 and fixed some minor build errors which you can see on my github, but then I've ran into this build error after ~30 mins of building (usually it takes 1h 30m to finish a build, thanks to GCloud platform...). I've searched a bit and found a post where a dev has the same issue and is saying that hwcomposer isn't compatible with the kernel source and that must be because I'm still using MM source since Huawei didn't publish N source for L01/L11. There's a cm14.1 branch left by Grarak and there's a commit which contain something which appear in the build error. He might tried to build cm/los 14 and ran into the same build error, I don't know. But I'll try that commit today and I'll also do more research. I'd like to build it successfully today, but I'll see how it goes.
Click to expand...
Click to collapse
I really understand your point, but what makes me think about no differences is that the link I shared leads to Cannes AL10 and Cannes TL10, which seems to be international models, but inside the file "README_Version.txt" is written that "This kernel package is released for the phone software version--CAZ-B368,MLA-B351". This really made me think that they are compatible. Maybe the various Nova types are differs in radio/modem and storage, Idk. Really made me wonder.
Thanks for the tips for google cloud storage. First I'm trying to build at least the kernel, so I can understand a bit of the process =) At least the kernel tree I can handle with my limited storage xD
PS
Is good to know that you are making quick progress to LOS 14.1 =D
Vinnom said:
I really understand your point, but what makes me think about no differences is that the link I shared leads to Cannes AL10 and Cannes TL10, which seems to be international models, but inside the file "README_Version.txt" is written that "This kernel package is released for the phone software version--CAZ-B368,MLA-B351". This really made me think that they are compatible. Maybe the various Nova types are differs in radio/modem and storage, Idk. Really made me wonder.
Thanks for the tips for google cloud storage. First I'm trying to build at least the kernel, so I can understand a bit of the process =) At least the kernel tree I can handle with my limited storage xD
PS
Is good to know that you are making quick progress to LOS 14.1 =D
Click to expand...
Click to collapse
Umm, I haven't checked that readme. Maybe I'll try that kernel source someday.
If you'll use Google Cloud Platform, then you won't need to worry about your storage, as GCloud uses own storage, like a virtual one. When you'll sign up to GCloud, you'll see that you'll have to make an "instance" and you'll have to choose "PC specs" (CPU, ram, storage). You get 300$ free and the trial is available 1 year if I'm not wrong.
I have about 150-180$ left ( I can't remember properly) and that's kinda enough. Also, I can get another trial since I have a second credit/bank card . As a tip, make sure that you'll shutdown the instance everytime you stop using it, otherwise it'll take money after some time (e.g. if the instance has been on overnight or 1-2 days). That's how I ended up with less credits available, by forgetting to shutdown it.
Here's a great guide about how to build ROM from source. I've used it myself at begin. However, keep in mind that you'll need newer java version than the one which is mentioned there.
Regarding LOS14.1, after spending the whole day (today), I've finally built the kernel without any errors. It turned out that I had to use newer CAF source and the one left by @Grarak in "caf-n" branch was useful. Probably I would've had difficulties in finding which CAF source I should use or I would've been stuck if the one by Grarak wouldn't have been there.
Tomorrow, when I'll start building the ROM, the errors related to the kernel which I've encountered yesterday should be gone since I've built the kernel successfully.
I think the chances are pretty high that the ROM won't boot, not sure, but I'm quite excited .
The thread tittle is called "Cannes al10 & cannes tl10 emui 5.0 source code release" and we talk about... you know We've went off topic.
Thank you for working so hard on this device. Living in China as a non-Chinese it is really hard to get a credit card. I will be moving in about a week and have a much better job. Hope I can get a build device together and help you out. Again, thanks for all your work.
@Vinnom
Finally, Huawei has published the source code...
There says "CAN-L10, L11", but I don't think there's L10. Probably is just a typo as they did with "Andriod".
#Henkate said:
@Vinnom
Finally, Huawei has published the source code...
There says "CAN-L10, L11", but I don't think there's L10. Probably is just a typo as they did with "Andriod".
Click to expand...
Click to collapse
Maybe lol
Btw, do you know the differences between L10 and L11?
EDIT [OT]:
I didn't have the time to answer your in the OT thread yet, but later today I'll xD
Vinnom said:
Maybe lol
Btw, do you know the differences between L10 and L11?
EDIT [OT]:
I didn't have the time to answer your in the OT thread yet, but later today I'll xD
Click to expand...
Click to collapse
I don't know and I don't think there's CAN-L10, but I'm not sure though.
Usually when a New J series is out, our community of great developers are all over it finding ways to root and making rooms. Since the J4 has been out for a few months there hasn't been any sort of news or updates. Are there any teams working on it?
I'm afraid that the possibility is slim, since the J4 is not widely released (do correct me if I'm wrong) in the US, UK, or other big-market countries, but rather released in smaller-market countries in Africa, Asia, etc, and even so released rather quietly w/out major press releases. So unless the phone is widely released (relative to other Galaxy phones out there), I'm inclined to believe that such teams would have little to no access to the J4, and thus no development to progress for it.
(Believe me, I'm remaining optimistic that at least an unofficial recovery might be on the works, but there won't be much progress unless the J4 is more widely used/picked-up)
Or, you can learn how to do it yourself.
Not the TWRP porting, but you can definitely MOD your stock ROM to add features Samsung annoyingly disable for not being a "premium" device.
You don't need to know much of coding, you can learn as you go. When the J2 Prime was released (and even to this day) there aren't any custom ROMs so I had to teach myself and I've accomplished great things
Just wait for TWRP and then the doors will open, you'll see
;77491224 said:
Or, you can learn how to do it yourself.
Not the TWRP porting, but you can definitely MOD your stock ROM to add features Samsung annoyingly disable for not being a "premium" device.
You don't need to know much of coding, you can learn as you go. When the J2 Prime was released (and even to this day) there aren't any custom ROMs so I had to teach myself and I've accomplished great things
Just wait for TWRP and then the doors will open, you'll see
Click to expand...
Click to collapse
Huh, that's interesting; I'll surely take a look.
Could you further elaborate on the "features" that Samsung disabled? (I don't use a lot of Samsung G's built-in features, so I'm not too knowledgeable on such; tried Google-searching, only came up w/ disabling apps, so that didn't really help...)
Debstup said:
Huh, that's interesting; I'll surely take a look.
Could you further elaborate on the "features" that Samsung disabled? (I don't use a lot of Samsung G's built-in features, so I'm not too knowledgeable on such; tried Google-searching, only came up w/ disabling apps, so that didn't really help...)
Click to expand...
Click to collapse
For starters, things like edge screen or scroll capture (things that I use a heck of a lot)
I found it funny is that all it took as to change a bit of code here and there, add the right apps and edge screen was working perfectly on the J2 Prime (a very low-end phone).
Samsung went out of their way to delete this feature which is pretty ridiculous if you ask me.
Themes were also disabled for this device, but after reading a few guides I was able to implement a ROM control that allows the user to change the color to their liking
The dev community is always willing to lend a hand, just as long as you're not lazy and expect everything to be put out for you.
I feel the J4 can make a dev out of someone looking to add more functionality to their device (the J2 Prime made a dev out of me )
Ok, so the TWRPBuilder's experimental TWRP build (huge thanks to @yshalsager for this miracle) is on TWRPBuilder's site: twrpbuilder.github.io/downloads/twrp/
Like any TWRP builds, there is ABSOLUTELY zero guarantee that it would work (I tried the first one & it didn't work, haven't had the chance to test the latest one yet)
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
Ok, so the TWRPBuilder's experimental TWRP build (huge thanks to @yshalsager for this miracle) is on TWRPBuilder's site: twrpbuilder.github.io/downloads/twrp/
Like any TWRP builds, there is ABSOLUTELY zero guarantee that it would work (I tried the first one & it didn't work, haven't had the chance to test the latest one yet)
The J4 uses identical chipset as the J5 prime G570F/M/DS.
I have both and they are great phones for their segment.
Sadly neither are well supported by ROM developers, due to the Exynos chip, I think.
missioner said:
The J4 uses identical chipset as the J5 prime G570F/M/DS.
I have both and they are great phones for their segment.
Sadly neither are well supported by ROM developers, due to the Exynos chip, I think.
Click to expand...
Click to collapse
@yshalsager did a test custom recovery for J4 (via TWRPBuilder): https://twrpbuilder.github.io/downloads/twrp/
Have been unable to test it atm (stuck in 7-day jail); if you want to have a go at it & let him know the results, go right ahead!
but first we have to unlock oem.but the problem is no oem unlock in the settings
brownstyle said:
but first we have to unlock oem.but the problem is no oem unlock in the settings
Click to expand...
Click to collapse
Yeah that's the 7-day "jail" I was talking about - theoretically you have to leave your phone on non-stop (no reboots, no shutdowns) for 7 whole days straight, then the OEM Unlock option should become available in Dev Settings (it's a confusing security measure by Samsung on Oreo devices)
any update guys? im really bored with this phone now
up
guys can we root our device j4 using magisk?
#push
#push
#push
#push
Do not spam, if you don't get an answer then that means that nobody is working on it
up
brownstyle said:
up
Click to expand...
Click to collapse
Dude
Hi folks..
My mind simply has hard time to process why there's almost nothing custom for this Galaxy A71 or any other recent Galaxy phone? It's been already over 9 months A71 is on the market and there is no official TWRP support (neither OrangeFox).. No official custom ROMS like Resurrection Remix, Evolution X and neither LineageOS.. Pls don't count unofficial crap where you have missing basic functionality or decent camera.
I have left Samsung flag-ship world back in 2015 not willing to pay money for the development path they choose.. Anyway, I found shelter with Xiaomi since then and never experienced any deficit for custom made stuff. Now I bought A71 and am stunned with the fact there isn't any motivation to support it.. I have wrote to multiple telegram threads without any answers so asking here.. Is there some blocker from made by Samsung to start supporting Galaxy phones? Or just devs got tired of their sh***t.. Don't get me wrong, I liked Samsung a lot.. and now tried to come back when I got my hands on A71 - hardware wise excellent device but unfortunately will return due to lack of community around. And it isn't just this Galaxy phone - S20s, S10s, Note 20s, 10s.. previos A series...
Thanks for any comments..
MacGyver27 said:
Hi folks..
My mind simply has hard time to process why there's almost nothing custom for this Galaxy A71 or any other recent Galaxy phone? It's been already over 9 months A71 is on the market and there is no official TWRP support (neither OrangeFox).. No official custom ROMS like Resurrection Remix, Evolution X and neither LineageOS.. Pls don't count unofficial crap where you have missing basic functionality or decent camera.
I have left Samsung flag-ship world back in 2015 not willing to pay money for the development path they choose.. Anyway, I found shelter with Xiaomi since then and never experienced any deficit for custom made stuff. Now I bought A71 and am stunned with the fact there isn't any motivation to support it.. I have wrote to multiple telegram threads without any answers so asking here.. Is there some blocker from made by Samsung to start supporting Galaxy phones? Or just devs got tired of their sh***t.. Don't get me wrong, I liked Samsung a lot.. and now tried to come back when I got my hands on A71 - hardware wise excellent device but unfortunately will return due to lack of community around. And it isn't just this Galaxy phone - S20s, S10s, Note 20s, 10s.. previos A series...
Thanks for any comments..
Click to expand...
Click to collapse
Blame Samsung for keep releasing broken kernel source, dev. Can't start if sammy keeps releasing sh*ty broken kernel source, until now 2.0 and 2.1 updates having broken kernel source. There is no other companies in the world that do such stupid thing except Sammy sh*t. Thanks! also we can rewrite the kernel to fix sammy mistakes but it needs a talented and dedicated dev.
Samsung has lost its reputation for being developer friendly long ago. At best you're only going to find some GSI that work on this phone. At worst, you won't find anything at all.