Hi,
I'm currently porting CyanogenMod to the Samsung Galaxy Alpha (Exynos5430). As the Note 4 is coming with an Exynos5433 SoC I think they are very similar and we could exchange knowledge about porting CM if someone is working on it!
I have code to support exynos5430 ready and also for the wifi, init, etc.
The repo is here:
http://git.cryptomilk.org/projects/...re_samsung_slsi_exynos5430.git/log/?h=cm-11.0
Required PATCHES:
hardware/libhardware_legacy:
http://review.cyanogenmod.org/78177
http://review.cyanogenmod.org/78178
http://review.cyanogenmod.org/78179
hardware/samsung:
http://review.cyanogenmod.org/78176
hardware/samsung_sli/exynos5-insignal:
http://review.cyanogenmod.org/78565
http://review.cyanogenmod.org/78566
http://review.cyanogenmod.org/78567
http://review.cyanogenmod.org/78568
http://review.cyanogenmod.org/78569
system/core:
http://review.cyanogenmod.org/76217
system/netd:
http://review.cyanogenmod.org/78180
Awesome bro im sure you'll have plenty of testers here with note 4s including myself keep in touch
I don't have a Note 4. I'm working on the Samsung Galaxy Alpha with a Exynos5430 SoC. The Note 4 has a Exynos5433 SoC. So if someone wants to port CM to the Note 4. We can work on the common code together ...
It'll be awesome work for Note4, if someone start to work it on.
Yea what i mean is that the code would be a bit different but if somebody ports it over for 5433 than ill test for them
modpunk said:
Hi,
I'm currently porting CyanogenMod to the Samsung Galaxy Alpha (Exynos5430). As the Note 4 is coming with an Exynos5433 SoC I think they are very similar and we could exchange knowledge about porting CM if someone is working on it!
I have code to support exynos5430 ready and also for the wifi, init, etc.
The repo is here:
http://git.cryptomilk.org/projects/...re_samsung_slsi_exynos5430.git/log/?h=cm-11.0
Required PATCHES:
hardware/libhardware_legacy:
http://review.cyanogenmod.org/78177
http://review.cyanogenmod.org/78178
http://review.cyanogenmod.org/78179
hardware/samsung:
http://review.cyanogenmod.org/78176
hardware/samsung_sli/exynos5-insignal:
http://review.cyanogenmod.org/78565
http://review.cyanogenmod.org/78566
http://review.cyanogenmod.org/78567
http://review.cyanogenmod.org/78568
http://review.cyanogenmod.org/78569
system/core:
http://review.cyanogenmod.org/76217
system/netd:
http://review.cyanogenmod.org/78180
Click to expand...
Click to collapse
Awesome, gonna start it right now. Please, keep this thread up. Oh.. and THANK YOU for sharing! :good:
andrew.mackew said:
Awesome, gonna start it right now. Please, keep this thread up. Oh.. and THANK YOU for sharing! :good:
Click to expand...
Click to collapse
The patches should be upstream soon. I'm working on it with intervirgil. In the meantime I understood how audio works and started to implement an audio HAL. The basics work ...
modpunk said:
The patches should be upstream soon. I'm working on it with intervirgil. In the meantime I understood how audio works and started to implement an audio HAL. The basics work ...
Click to expand...
Click to collapse
Awesome! Looking forward to collaborate with you guys!
I got audio mostly working. The big issue I have is that I don't get Wifi working. If someone wants to start I can help bring a first build of the device up. It should be fairly easy with my exynos5430 branch soon. Most of the patches for the insignal branch are upstream.
Can i ask how it's going? I would love to see an CyanogenMod on the Note 4! Thnx for al de devs putting their time in this!!!
Any update?
Most of the patches I created for CM are upstream now. I got a lot of stuff working on the device already and know what to do. Just somone needs to start working on it. I can explain what needs to be done but you need to be able to write C/C++ code and understand strace output. If not it is not really a task for you.
modpunk said:
Most of the patches I created for CM are upstream now. I got a lot of stuff working on the device already and know what to do. Just somone needs to start working on it. I can explain what needs to be done but you need to be able to write C/C++ code and understand strace output. If not it is not really a task for you.
Click to expand...
Click to collapse
Yep, I think I can manage to deal with C/C++.. at least I did usually handle with at the college..
Furthermore, will be a pleasure to work together with you and others and collaborate with something for Exynos users like me.
Please count me in. Just let me know what I need to do and I gonna start it up at my side.
Normally you start with the recovery. After you have a working recovery you compile the kernel from the source for the recovery. The CM code needs kernel headers so you need the kernel compiled! After that take a look at the git history of my branch. Ask if you hit a issue.
For a start, read:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Porting order:
Recovery
Recovery + Kernel from Source
First CM build
Get graphics working (gralloc, hwcomposer, etc.; Kernel headers required)
Get Wifi working
Get Audio working
Get RIL working (You can't make a phone call without audio)
Power HAL
Lights HAL (maybe before RIL)
Sensors HAL (maybe before RIL)
Camera
GPS
Bluetooth
...
Guys there is one developer in XDA(raymanfx) that has experience in port cm12 for Exynos. I emailed him and he told me he would port cm12 to n910c exynos if we raise fund and buy him 1 unit so that he can work. He has already ported cm12 to samsung note 10.1 2014 p600 exynos tablet
Please join the XDA thread i have created and help us to fund to buy him 1 unit of n910c so that he can work
http://forum.xda-developers.com/showthread.php?t=2986964
Hi just a question...will it be cm12 with 64 bit support?
domy1985 said:
Hi just a question...will it be cm12 with 64 bit support?
Click to expand...
Click to collapse
Yes it will be CM12,
We dont know yet if it would get 64bit support,
Samsung told me by Mail The exynos will not receive 64 bit because it would not support it
Gesendet von iPhone mit Tapatalk
domy1985 said:
Samsung told me by Mail The exynos will not receive 64 bit because it would not support it
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
I doubt that very much..
They told ma by Mail a 32 bit Prozessor could not achieve the performance of a 64 bit processor.........?
Gesendet von iPhone mit Tapatalk
Related
Hi to all Broadcom BCM215XX armv6 devices running android!
I'm glad to announce that, our organisation, BroadcomCM will start working on the port of AOSP ICS drivers for our CPU and GPU, BCM21553. First of all, I've asked moderators to close all my threads, why? We know we have [GENERAL] Thread for our projects but most users don't care, so this will be the thread to talk about it, development!.
Samsung stopped the development on this devices long ago, but their drivers where not ever released. Thanks to our petition, we have managed to force Broadcom to release the drivers, and we managed to release them on ICS, android 4.0+, way!
Index:
Post 1 (this) ...................................... Information about drivers
Post 2 .............................................. Frequently asked questions
Post 3 .............................................. Drivers on Github (Opensource)
Post 4 .............................................. Videos showing HW working
Click to expand...
Click to collapse
A bit of introduction:
Broadcom gave to us test driver builds, which were prebuilt, .so libraries, and we could not edit them, but they gave us the code to patch framework to make those prebuilt libraries work with our AOSP project (by that time, CyanogenMod 7.2). After some re-search and lot of work on our team (thanks Legolas93), I managed to implement AOSP Alcatel drivers to our CyanogenMod 7.2 Based ROM. This was the biggest change ever happened to that device, as we managed to fix 100% HW and as a cosnequence, libstatgefright was fixed too, and HGL. This resulted on camera/vide recordi (media profiles, encoding and decoding) to work, this was RC1. REMEMBER: As we extracted this libs from sotck AOSP alcatel ROM they are prebuilt, so we can not modify them at all.
SInce that moment, project on HW was stopped, and we focused to fix other issues not releted to HW (ext4, backlight, led, tethering, BT...), and we managed (most of them), and everyone enjoys now a CM, AOSP and Cyanmobile port brought to you by broadcomCM.
What else?
Broadcom released, or seemed to, BCM21553 driver source for AOSP ICS source. They released the source, so now we can know how our chip work. What is weird about it, is that this chip is released for ICS source, when it is an armv6 chip, and any device of our family has official ICS. (Maybe BROADCOM are really nice people, or maybe they trolled us). We will add new tag to be defined on Boardconfig.mk to make the drivers work on it.
So.. We did it?
Yes, we forced Broadcom to release the source, you, we, we all did this possible, and we should be prud of ourselves.
Will with this come BroadcomCM to develop?
Well, yes and no, we already have some surpises for BroadcomCM ROMs owner, which were not reletated to drivers at all, and they affect all devices. As this work is nearly finished (first alpha), we will release this next week, and then we will start working on it. Keep calm, good things make people wait for it don't ?
What is now?
Now, nice question. We will implement this source code on our CM9, ICS, branch. (all sources can be found on our github), and implement them on the build, will that be easy? OF COURSE NOT. Broadcom trolled us with first test builds of drivers, so maybe expect the same from that sources, we don't know and we will not know unitl we build it, and we have to compare each file, ONE PER ONE, so it will be a hard work.
Frequently asked questions can be found on the second post, as well as a video to show you what was having a device with drivers, and what was not. (Qualcomm vs Broadcom [armv6]).
ANY ETA? (Estimated Time of Arrival)
No. I can not tell any eta, I'll maintain you informed to you on this thread. I'll start my work next week (Exams on this one, need to study ), and I'll keep calm, I'm as amazed as you, but we have to be very down to earth. Broadcom lied to us, maybe they made it too. It will take some time to study and implement, and then make them work!
WILL THAT FIX ALL THE ISSUES WE HAVE ON ICS?
No, but will fix the most important one, HW. What I mean by hardware is the animations will be smooth, video on second post. So hopefully we will run a good ICS build, but expect camera and Audio not working too. Audio? Well some progress have been made on shadows, camera? That will be hard, really hard. Even Cooper (Galaxy Ace MSM7x27 based chip wasn't able to run camera at the first, since Qualcomm not release their source too).
AND WHAT ABOUT CM7 (2.3.7 based roms)?
We hope 2.3.7 ROMs will benefict from it, but we are not sure, we will have to test them and implement on our CM7 tree, but as they are for ICS, or this seems to, first goal is ICS, as we have 100% HW working, but with prebuilt, for the moment is OK and not our priority,
CAN I IMPLEMENT THE DRIVERS ON MY DEVICE?
No, to implement those dirvers you will need big knowledge of BroadcomCM devices, and I think our team has. We have managed to solve many bugs, and, talk with broadocm to solve first driver errors we had.
Ok, we have managed to get drivers working on our CyanogenMod 9.1 Ice Cream Sandwich version 4.0.4. Remember the drivers were given in 4.0.1 which were a bit different from actual 4.0.4 used.
After the release of the ROM with first version of those drivers included, we are glad to announce that, as always, we opensourced this "4.0.4 drivers" as well as Broadcom did. Feel free to take them, and use it at your own, to build diferent ROMs, such as AOKP, Paranoid, AOSP... Or Jelly Bean . This are drivers source, you will need to cherry-pick them to your local repo:
/bionic
/frameworks/base
/hardware/libhardware
/system/core
Broadcom was nice, and they created a new HGL lib, which they open-sourced too, and give the name of libv3d, kind of a new HGL lib, which should complish all patches and BCM21553 requiriments, also opensourced on BroadcomCM.
/brcm_usrlib also known as libv3d
You can also find original patch on Broadcom's page (4.0.1 patch) and the diff files I've made, which they will give you more clues on how to implement them on other sources.
On those videos, we can see that those drivers are fully working! Thanks for those youtubers, we can show to the world that WE DID IT!
ME presenting those drivers:
COOPERVE:
TOTORO:
TASSVE:
CORI: (WIP)
you guys are amazing,thanx for all............
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
u doing a great job buddy.
keep it up. :thumb:
n best of luck for ur exams..
---------- Post added at 11:18 PM ---------- Previous post was at 11:18 PM ----------
CharsiBabu said:
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
Click to expand...
Click to collapse
yup..
Always Great biel and his team..
using the great ace -i
Only these lines in legacy_prebuilts.mk already made me start to give up the drivers must be another troll source, maybe I'm wrong...
libEGL_POWERVR_SGX530_121.so \
libEGL_tegra.so \
libGLESv1_CM_POWERVR_SGX530_121.so \
libGLESv1_CM_tegra.so \
libGLESv2_POWERVR_SGX530_121.so \
libGLESv2_tegra.so \
Maybe they gave us fake one or another test builds. Still will take time months/year. Just buy new phone. This doesnt worth it.
Good luck, BroadcomCM!
It means,that we can expect cm9 only woth not working camera and sound?
This is some real good news if the broadcomCM have given the proper sources... Well, let's hope bielt.v keeps us updates
Dr.Pepper said:
It means,that we can expect cm9 only woth not working camera and sound?
Click to expand...
Click to collapse
If we get stable cm9 thats also great for us..
using the great ace -i
I highly doubt a big manufacturer would "troll" its consumers and volunteer developers with "fake" driver sources.
Sent from my GT-I9195 using xda app-developers app
I don't think they trolled us, they wrote a documentation and made an announcement for Fake drivers? A big manufacturer like broadcom will not play hide and seek with us, they know that they will lose their respect.
Sent from my GT-S5360 using Tapatalk 2
NICE!
CharsiBabu said:
Does this mean we can build other roms as well?
like aokp / paranoid android / pac /miui etc.
Anyhoo, I wish you goodluck.
Click to expand...
Click to collapse
We can leterally "port" those, (copy paste u know, lol)
Mitko said:
I highly doubt a big manufacturer would "troll" its consumers and volunteer developers with "fake" driver sources.
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
Its natural, lol, happens once in a millenium, but these maybe true... but one thing is serioussly doubtful that the readme says
Readme.txt: last line:
make -j8 TARGET_DEVICE=generic_armv5
Click to expand...
Click to collapse
and armv5 doesn't exist ?? && moreover our bcm21553 devices are more likely to be armv6 variations....
really confuses me
Code:
I havent done enough research tho (due to less time on pc)
can anybody explain me that ??
There a long-long way to go. hopefully the awaited days come with good news.
XDA-Developer App
So I'm noodling through the source code, and I guess I'm gonna see what I can do to try and compile something for the Raspberry Pi. Fingers crossed.
EDIT: Also, according to wiki, ARMv5 is in fact a thing. Who knew?
http://en.wikipedia.org/wiki/ARM_architecture
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Does your kernel compile and boot on cm11? If it does, there shouldn't be much problems in getting it working on L.
Any news? Does it compile?
frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Ivan_Meler said:
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Click to expand...
Click to collapse
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
ztotherad said:
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
Click to expand...
Click to collapse
I know samsung does things like that (i have few other devices from them) but hey thats samsung and they are lazy so they dont want to update kernel version after device is relesed so they do this not to feel outdated on softwere side
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
frap129 said:
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
Click to expand...
Click to collapse
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
I was planning on working on that as well over the weekend.
polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Ivan_Meler said:
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Click to expand...
Click to collapse
I'm very new to the AOSP build process and didn't have much luck last night getting the CM device sources to play nicely with AOSP. I'm finding it difficult to find any relevant guides on porting over the CM device trees to pure AOSP. If you or anyone else can help by explaining the process or pointing to a guide that I may have missed, I'd be grateful. Plus the more people we have collaborating on his, the better our chances of getting Lollipop on our devices.
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Restl3ss said:
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Click to expand...
Click to collapse
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
polarEskimo said:
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
Click to expand...
Click to collapse
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Restl3ss said:
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Click to expand...
Click to collapse
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
polarEskimo said:
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
Click to expand...
Click to collapse
I'll push what I've got to github after this experiment
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Ivan_Meler said:
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Click to expand...
Click to collapse
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!
Build currently hangs at this:
Code:
host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night
Restl3ss said:
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Click to expand...
Click to collapse
I'm with you on that, I'd rather have pure AOSP than buggy CM nightlies. Also interesting choice of ROM name lol. Thanks for your hard work and I'm looking forward to pulling down your repos so I can take a stab at these compile-time issues.
Development is dead. Please delete..
Rmontoya83 said:
Good news I have a working Linage OS 13 build for the lg stylo 2 Plus GSM. Thought it was bug free still has some issues though . My PC took a dump I have the sources saved on my hard drive I will have a new PC on Feb 6 and will release the Rom For Free probably with in a few days from then. As I'm almost done porting a working lineage OS 14 for the device.
I will update the device tree on Github So I can get help from other devs to trouble shoot these issues better and collaborate works. I will also include a working recovery with the Rom for free . I am doing this in my free time so please be patient .
I will keep you posted ?
Any people interested in helping let me know.
Click to expand...
Click to collapse
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
cragains said:
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
Click to expand...
Click to collapse
You can downgrade your firmware .
Nice work let me know when the source is up at github , i may be able to help
I'm so anxious I can't wait to get my new PC! I will be compiling a lot faster. You guys are going to like this lineage OS port. Hang in there
Any screenshots?
I'm interested in this also
Pelegius22 said:
Any screenshots?
I'm interested in this also
Click to expand...
Click to collapse
Not at the moment I had the backlight on my display burn out . had to flash the stock rom back for warranty purposes and for some reason every time I try and back up via twrp the data gets corrupted.
So the only place I have a working Rom is stored on a hard drive and I get my PC back on the 6th this month so it will be up soon.
Twrp link
Rmontoya83 said:
You can downgrade your firmware .
Click to expand...
Click to collapse
No PC right now, I moved across the state, and left my PC.
Can't down grade
LG Stylo 2 PLUS
TWRP no ROOT
Got the new laptop up and running building starts tommorrow.
All souces are downloaded . I will start building the device tree tonight hopefully by end of week myself and @messi2050 will have a working lineage OS build for the ph2n. I stood up all night working on the list of proprietary files need for the build.
Now comes the hard work of adding all the required blobs to get it all functional please be patient. As we are doing this in out free time. Once the device tree is all setup it will be a lot easier to port other roms to this device such as omni aokp DU and so much more. I chose a 13 build as I'm new to this and its a lot easier to port a Rom that has many components that are stable with the version.
If you appreciate our work buy us a cup of coffee. Or hit the thanks button for the Devs working on this build .
Thanks to all the xda community.
We should work on a changelog concerning drivers for cheaper models like my tmousa k550.
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom kernel with more governors and overclock! Let me know if you need me to test, I have MetroPCS variant. Thank you also for your time and development for this amazing device!
Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom all the way.
I am sending this to you in hopes of curing my boredom...
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
we need all the help we can get
Giminji said:
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
Click to expand...
Click to collapse
@messi2050
has one repository done for device /device
i have the other kernel/
i am working on the blobs using @JackpotClavin utility tool to pull all the blobs needed for the build. once we have a stable tree we can work on building other roms.
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
https://github.com/RichieRich83
@messi2050
You rock brother.
Rmontoya83 said:
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
URL deleted I am too new.
@messi2050
You rock brother.
Click to expand...
Click to collapse
Both you and Messi are doing amazing things. When this is done, both of you are getting a cup of java (I couldn't resist Java instead of Joe or Coffee). I downloaded the jackpotcalvindonkey thing yesterday, did the make on it, but didn't get it out.
Btw, your github shows no public repos.
Well that was quick
Does anyone know about this topic?
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
nchantmnt said:
https://forum.xda-developers.com/mi-note-10/how-to/custom-development-t4018813
In short:there are same some efforts trying to get custom Roms but nothing groundbreaking yet.
I am working on the device tree right now to compile from source. Not ready yet and don't have the device in hand right now (should arrive soon) s.o. else is trying with treble images.
Click to expand...
Click to collapse
I thought device tree is something that was used to be leaked from Xiaomi
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
I hope soon
The more people help together the faster we can get some Roms ?
nchantmnt said:
The more people help together the faster we can get some Roms ?
Click to expand...
Click to collapse
If you have a group for this, would you pm?
No group yet, but you still get an pm
Anyone willing to collaborate is welcome to pm me as well
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
ignalop1983 said:
I have seen this Android 9 source code. Is it helpful?
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/tucana-p-oss
I thought this model would have more support and after 4 months there is no Rom. I hope that now that the price is going down more people buy it and we have more community. Thank you for what you know and develop.
Click to expand...
Click to collapse
Just an incomplete kernel sources, I think is useless.
https://www.xda-developers.com/poss...-fcc-certified-snapdragon-730g-penta-cameras/
There will be a lite edition soon. The only difference on hardware is number of pixels.
If its ROM is same or almost the same to current models, we should get some progress around development.
Anything new?
UtkuAblak said:
Does anyone know about this topic?
Click to expand...
Click to collapse
Please look at the existing topics first, before opening another topic!
nchantmnt said:
As far as I can see there is no device tree published by xiaomi for tucana (our device)
Only thing we have rn is kernel source.
But we can create device tree by ourself. There are some basic guides online. Rest is compare with existing device trees for similar devices and copy&paste.
for now I have downloaded k20 device tree, removed everything k20-specific (e. G. Popup Camera) and adapt further files for our device(s)
When my handset arrives (should be today) I can start unlock procedure (should take some time to get the code AFAIK), then I can unlock bootloader, flash custom recovery and see if I can get my device to boot properly after flashing... Then comes troubleshooting.
Right now I am expecting maybe a halfway booting device or broken/missing functionality at best. But we will see
Click to expand...
Click to collapse
Well, just tell me if you need help.
Same here, I am very tempted by the Note 10 but I am waiting for an aosp rom as many people complained about the stock miui rom
Any news or update on this? Would love to buy a Mi Note 10 as their prices have gone down but with the lack of development I'm kind of leaning towards the 9t even tho I'm worried about that front camera as some have had issues. I suspect not many are developing for this device because of the high price. Hopefully whoever said something up there about the Note 10 lite gets custom ROMs going with more devs
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
yes he is working on this device.
nchantmnt said:
I'm still trying here but very short on time. We have some good progress on device tree thanks to someone else (thanks Hlcpereira).
Click to expand...
Click to collapse
Awesome news! Thanks :good:
I think the development goes now straight because we have MIUI Stable based on Android 10 now.
Good luck!
Hello, I decided to come up with a project that aims to port higher Linux versions. When I say higher Linux versions, I mean those that are Linux 3.5 and up. The goal is to port Linux major updates as high as I can, but the main priorities are one that are LTS like Linux 3.10, 3.14 or even 3.18.
Only Android 7 will work on non-LTS versions. Oreo/pie and Android 10 support will be added only on LTS versions to lessen the conflicts when merging non-LTS versions.
What works:
Boots
Battery
Charger
Touchscreen
Display
USB
Sound
Buttons
Deep sleep
Camera
Video playback
Fingerprint
The rest of the sensors
WiFi
Bluetooth (works on Linux 3.7 and up)
Internet connection
Anything else I can't mention
What doesn't work:
You tell me
Drivers that can't be updated (yet) due to them being heavily modified by CAF and Samsung:
USB
Sound
MMC
Newer versions are more stable than the other due to the fact that I fix more bugs with every update.
The highest version as of now is Linux 3.8. I can only merge major updates during weekends due to my work.
Sources:
Linux 3.5
Linux 3.6
Linux 3.7
Linux 3.8
Linux 3.9
Feel free to open up issues and submit pull requests
It is highly recommended to delete mpdecision from /system/bin/ before flashing
Reserved
i don't understand what is this, is there some wiki i can read?
saikyom said:
i don't understand what is this, is there some wiki i can read?
Click to expand...
Click to collapse
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
darrendude1 said:
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
what are the benefits of updated kernel..cheers
Sent from my Unknown unknown using XDA Labs
Click to expand...
Click to collapse
Read these:
https://kernelnewbies.org/Linux_3.5
https://kernelnewbies.org/Linux_3.6
https://kernelnewbies.org/Linux_3.7
https://kernelnewbies.org/Linux_3.8
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
godofsalt said:
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
Click to expand...
Click to collapse
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
pascua28 said:
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
Click to expand...
Click to collapse
Well, Thank You. for the reply, as well as, all the information.
YES your project is a HUGE amount of work. Good guess, IS , you seem to want to take on this challenge! Good for you...
Yes, I do intend to really follow your project. Really looking forward to the great results that I hope we (you) can achieve !
Awesome...
Thanks
Hi guys! Linux 3.9 is up!
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
shmizan said:
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
Click to expand...
Click to collapse
Yeah, very tedious and requires a lot of skill
This is huge. Thank you for doing this, I will definitely be following this
pascua28 said:
Yeah, very tedious and requires a lot of skill
Click to expand...
Click to collapse
Yes, as well as time, the correct machine and layout....
Plus I believe it requires most patience than what I have!
BTW... This is great work, have not seen any issues on my S5..... (yet, but don't think that will happen though)
Thank you!
Sent from my Galaxy S5 using XDA Labs
Is this working on 5+ (katcc6)?
robla1000 said:
Is this working on 5+ (katcc6)?
Click to expand...
Click to collapse
Nope, S5 only. And at this point klte only until @pascua28 is finished bringing the kernel up to 3.10
Only working properly is klte, for now. Other variants might work but with bugs. Will fix for other variants when we get to 3.10
3.5 to 3.9 didn't work for me,I have klte
didn't work?
I ran 3.8 for weeks without any issues.. what exactly does not work?
many reboot ,i couldn't use
vlad3647 said:
many reboot ,i couldn't use
Click to expand...
Click to collapse
It's not for higher Android version.. If you have Android 9 or 10 then wait for version 3.10