Related
As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the US Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided the SGH-T889 community with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward. The SGH-I317 is very similar to the T889 and use nearly all the same build configuration.
My product is no more than a straight source built t0lteatt build as the CM11 spec is drawn up for the t0lteatt on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions (carrier network labeling is one such exception).
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build. I will not promise a timeline, I simply plan on weekly builds.
Let me know if anything is goofy.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up to your liking
DOWNLOADS
cm-11-20150322-COUGMADE-t0lteatt.zip
cm-11-20150313-COUGMADE-t0lteatt.zip
cm-11-20150222-COUGMADE-t0lteatt.zip
cm-11-20150206-COUGMADE-t0lteatt.zip
cm-11-20150130-COUGMADE-t0lteatt.zip
cm-11-20150116-COUGMADE-t0lteatt.zip
cm-11-20150107-COUGMADE-t0lteatt.zip
cm-11-20150101-COUGMADE-t0lteatt.zip
cm-11-20141220-COUGMADE-t0lteatt.zip
cm-11-20141212-COUGMADE-t0lteatt.zip
cm-11-20141209-COUGMADE-t0lteatt.zip
cm-11-20141206-COUGMADE-t0lteatt.zip
cm-11-20141201-COUGMADE-t0lteatt.zip
cm-11-20141126-COUGMADE-t0lteatt.zip
cm-11-20141027-COUGMADE-t0lteatt.zip
cm-11-20141020-COUGMADE-t0lteatt.zip
cm-11-20141011-UNOFFICIAL-t0lteatt.zip
cm-11-20141002-UNOFFICIAL-t0lteatt.zip
cm-11-20140921-UNOFFICIAL-t0lteatt.zip
cm-11-20140914-UNOFFICIAL-t0lteatt.zip
cm-11-20140906-UNOFFICIAL-t0lteatt.zip
cm-11-20140902-UNOFFICIAL-t0lteatt.zip
cm-11-20140826-UNOFFICIAL-t0lteatt.zip
cm-11-20140818-UNOFFICIAL-t0lteatt.zip
cm-11-20140810-UNOFFICIAL-t0lteatt.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0lteatt git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Hastily spouted for your befuddlement
Mine
Gimme
Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time :thumbup:
fatjoejr2001 said:
Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time [emoji106]
Click to expand...
Click to collapse
Not immediately. I have some stuff to focus on and figure out first. I'll look at it down the road.
Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!
frewys said:
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!
Click to expand...
Click to collapse
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.
Coug76 said:
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.
Click to expand...
Click to collapse
the builds are functionally the same(right?)
xda1zero said:
the builds are functionally the same(right?)
Click to expand...
Click to collapse
Yup. They are purely CM source home builds.
Eventually I will start doing subtle things to try learn more. Any changes to the I317 ROM will be tested on the T889 ROM first and documented in the OP.
If anyone out there has flashed this, how is your network being reported? Does it show AT&T?
New build is up.
Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off
Does this ROM have the camera blobs or whatever the correct term in it? I'm running OmniROM right now because they do and my photos have been significantly better.
edfuhr1 said:
Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off
Click to expand...
Click to collapse
I can't duplicate your bug on my T889. Both play music and Apollo work fine for me when the screen shuts off or times out. Are you running any battery saving settings?
New build posted in OP. Nothing changed other than the CM nightly changes and those from source. In what spare time I have I am digging through what I can find for ways to address the little things that bug me.
New build posted.
Hastily spouted for your befuddlement
Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!
tetrahedonism said:
Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!
Click to expand...
Click to collapse
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.
Coug76 said:
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.
Click to expand...
Click to collapse
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!
tetrahedonism said:
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!
Click to expand...
Click to collapse
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.
Coug76 said:
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.
Click to expand...
Click to collapse
Understandable! Good luck!
Hello,
I have a question on what is needed by developers to make Lollipop ROMs for our S3.
I have been following the releases and know that the images for the Nexus devices are up and that OTAs have begun. Is that what developers need as a starting point?
As you can tell I'm fairly clueless about this so I appreciate any information because I like to follow along.
Thanks!
Devs need the actual sources to build, which have been released. Unfortunately they can't work with the factory images for Nexus devices.
If I remember correctly, it took 2 or 3 months to get a usable KitKat build from Slim. (the first ones to do it, I recall.) We'd be lucky to see it by the new year, in my opinion.
Thank you for the info.
So they take the Nexus sources and then build it for our devices and then figure out how to add drivers for our hardware, etc?
Thank you for the timeline. I'm hoping it will be sooner, but your estimate is more realistic
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
philhouse said:
I saw this in the S3 international forum:
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-namelessrom-t2939673
And
http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Looks like they are hard at work on lollipop for their devices. I wonder if anyone is working on it for ours yet?
Click to expand...
Click to collapse
Im wondering the same and if anybody has taken interest in building it for the d2lte variants like the att etc..
I haven't seen anything yet in the forums, but I'm still hopeful that someone will!
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
philhouse said:
Found this today. Sweeeeet:
http://forum.xda-developers.com/galaxy-s3-att/orig-development/cyanogenmod-12-t2944071
Click to expand...
Click to collapse
Yeah I been on the ROM since it was provided.
Preface:Lots of great developers have been bringing Cyanogenmod to the Honor 5X, but no one has posted any experimental builds for people to flash. Since I have been able to build CM with the sources other developers have kindly created, I would like to share builds for others to try out on their devices without having to setup an Android build environment.
I would like to clarify a few things:
These builds are UNOFFICIAL and may not be daily driver material.
I just build these ROMs from sources OTHER developers create. See credits below for developer list.
I cannot provide ETAs for the next build, new features, or anything else.
I have only tested these builds on KIW-24, so other variants might not support this ROM.
You are solely responsible for flashing this ROM along with any damage that might result from said flash. See the disclamer.
See post 1 for install instructions and downloads
See post 2 for screenshots and changelogs
Disclaimer: Voided warranties, bricked devices, rogue alarms at 2AM etc. are all your own problem. Neither any developer nor XDA is responsible for any unpleasantness that may result from using this ROM.
Credits:
@deadman96385
@CosmoDroid
@crpalmer
@InkSlinger420
@EarlyMon
@wimbet
@Chainfire
Cyanogenmod
Google
And anyone else I might have missed. Let me know if I should add someone else to the credits.
To flash this ROM you need to:
Unlock bootloader and install TWRP
Boot into TWRP, perform wipe, and then flash ROM .zip and optional gapps *NOTE* non kiw-24 users see this post for information on flashing.
Reboot, and enjoy CM on the Honor 5X
Unofficial ROM Downloads:
3-10-16 - REMOVED by OP
Optional Gapps Downloads:
http://opengapps.org/ (ARM64, 5.1.1, Full)
Changelog:
3-10-16 - Initial build. (Tested) working features; wifi, BT, (some) data/LTE, normal phone features.
Known bugs:
No rear camera
No fingerprint sensor
No extra kernel features like Tap To Wake
Some cellular/data features may not work. I can't test this so check posts below to see if someone else can confirm.
Screenshots attached.
Del
Zakaria.R said:
Why is it kiw-24 specific ? I read on the other thread that it worked just fine on another variant
Click to expand...
Click to collapse
I can only test on kiw-24. Another user has reported being able to flash ROM on kiw-22. If you or someone else can confirm that this will work on other variants, I'll update the OP.
Nothing was posted cause there is still things that need to be fixed...lol.. Bugs in builds suck..
Awesome! 40 days after US release. ( i know its been around these forums for a little while) but having a flash-able file is a big bonus. Any general working or not working info ?
InkSlinger420 said:
Nothing was posted cause there is still things that need to be fixed...lol.. Bugs in builds suck..
Click to expand...
Click to collapse
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?
eruji said:
Awesome! 40 days after US release. ( i know its been around these forums for a little while) but having a flash-able file is a big bonus. Any general working or not working info ?
Click to expand...
Click to collapse
See post #3/reply #2
Bandit Development said:
I can only test on kiw-24. Another user has reported being able to flash ROM on kiw-22. If you or someone else can confirm that this will work on other variants, I'll update the OP.
Click to expand...
Click to collapse
Thanks for replying fast man, actually I don't own the device yet, I was following the development here and thanks to you guys I might consider getting it, you made a big difference hope you keep on with this, your work is much appreciated :victory:
Bandit Development said:
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?
Click to expand...
Click to collapse
My deal is this... I also have builds of BrokenOs (my rom) for this device but i havent posted any for public use, for one reason...Respect... @crpalmer is doing 95% of the legwork for this device over there at CM and Im sure once hes ready and comfortable with where it is, he will announce builds somewhere for it....I think its both premature, and kinda crappy, to make public someones work before even they think its ready for public use.... My 2 cents... Oh, and i dont care about credit for anything..Im just a rom dev, i get enough for that....
InkSlinger420 said:
My deal is this... I also have builds of BrokenOs (my rom) for this device but i havent posted any for public use, for one reason...Respect... @crpalmer is doing 95% of the legwork for this device over there at CM and Im sure once hes ready and comfortable with where it is, he will announce builds somewhere for it....I think its both premature, and kinda crappy, to make public someones work before even they think its ready for public use.... My 2 cents... Oh, and i dont care about credit for anything..Im just a rom dev, i get enough for that....
Click to expand...
Click to collapse
Thanks for your input. I certainly do respect @crpalmer along with all the other devs who have worked on this device, and I in no way want to detract from the fame/glory/respect they are due for all their hard work.
@crpalmer or any other dev, if you want me to remove this thread or change it in any way, please let me know. I don't want to step on anyone's toes. I was only trying to help others get a early taste of CM so they didn't have to build it themselves.
Appreciate the credit but I just fetch coffee and hound Huawei when necessary for devs doing actual work.
No harm removing me from the credits.
Thnx to all the devs trying real hard to get these awesome roms on our device.... Really appreciated
Sent from my KIW-L21 using Tapatalk
Bandit Development said:
Thanks for your input. I certainly do respect @crpalmer along with all the other devs who have worked on this device, and I in no way want to detract from the fame/glory/respect they are due for all their hard work.
@crpalmer or any other dev, if you want me to remove this thread or change it in any way, please let me know. I don't want to step on anyone's toes. I was only trying to help others get a early taste of CM so they didn't have to build it themselves.
Click to expand...
Click to collapse
Thank you @Bandit Development for the build. While I understand where @InkSlinger420 is coming from I much prefer the state of where @crpalmer has brough CM to over stock. I've been running this for about 4 hours. GPS works great, data and phone work great. Most importantly switching between apps doesn't draaaaaaaag.
Hopefully those responsible for the hard work on this rom will realize this wasn't an attempt to grab the spotlight, but rather a way to placate the masses. Also, needed or not, there is valuable information even in the few early posts because not everyone uses their phones the same way, so one person may never run into a bug that another person sees frequently.
Fingers crossed, but perhaps this thread will also limit the number of posts in the [Dev] thread asking when etc.......... I know I filled it with build questions which probably didn't belong there either. However, I'm trying to learn a little about rom development and one of the first steps to that is to be able to build the rom so you can test your tweaks, or at least see how someone else's changes affect the phone.
Bandit Development said:
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?
Click to expand...
Click to collapse
It would take me approximately 30 seconds to add automatic nightly builds to my autobuild server (I already generate some builds every night).
Consider that and the fact that I haven't done so as an indication of whether or not I thought builds should be posted right now...
crpalmer said:
It would take me approximately 30 seconds to add automatic nightly builds to my autobuild server (I already generate some builds every night).
Consider that and the fact that I haven't done so as an indication of whether or not I thought builds should be posted right now...
Click to expand...
Click to collapse
Wow, didn't realize you have a server dedicated to building. Because of this, I did not know that you wanted to wait to post builds. Would you like me to ask an admin to remove this thread? I sincerely don't want to mess with your work, plans, or anything else.
Bandit Development said:
Wow, didn't realize you have a server dedicated to building. Because of this, I did not know that you wanted to wait to post builds. Would you like me to ask an admin to remove this thread? I sincerely don't want to mess with your work, plans, or anything else.
Click to expand...
Click to collapse
You don't need to remove the thread, I am just pointing out that I don't think that the build is at a level of quality that represents well the work of CyanogenMod.
crpalmer said:
You don't need to remove the thread, I am just pointing out that I don't think that the build is at a level of quality that represents well the work of CyanogenMod.
Click to expand...
Click to collapse
Well, I'm happy to let you take over cooking builds if you'd like. I certainly don't claim to be able to make quality builds.
I would really appreciate any tips/info you'd like to share that would improve my builds. I've been trying to learn how to fix bugs and contribute to the ROM development, but the task seems to be a rather undocumented and slow-going.
Hey everyone.
Been awhile since I've been back here and I wasn't sure about all the new changes.
Couldn't find any information regarding the stock firmwares and if we are allowed to upload them here.
I'll Explain Further:
Stock Samsung firmwares used to be free to download at good speeds from samsung-updates (I think?), but now they go through download services that cost money unless you want to wait 8 hours for a slower download.
There were threads that listed all the stock firmwares bwfore and I was wondering if I could start a thread for downloading all the SM-P600 stock firmwares (and other Note 10.1" 2014 variations)?
Nice to be back and finally have a device I can play with. It's been YEARS :highfive:
h311sdr0id said:
Hey everyone.
Been awhile since I've been back here and I wasn't sure about all the new changes.
Couldn't find any information regarding the stock firmwares and if we are allowed to upload them here.
I'll Explain Further:
Stock Samsung firmwares used to be free to download at good speeds from samsung-updates (I think?), but now they go through download services that cost money unless you want to wait 8 hours for a slower download.
There were threads that listed all the stock firmwares bwfore and I was wondering if I could start a thread for downloading all the SM-P600 stock firmwares (and other Note 10.1" 2014 variations)?
Nice to be back and finally have a device I can play with. It's been YEARS :highfive:
Click to expand...
Click to collapse
Hi h311sdr0id,
i see you are a developer... If you say you wan't to play with that device, does that mean you have intention to build a custom rom or kernel for p600
This would be the best news since 6 month for p600 owners!
Though I'm not a fan of having to wait, it seems a fair comprimise. Typical "freemium" model. Slow is fine for occasional flashers, but the serious ones will want to pay. It costs to host/manage these updates so seems perfectly fair to me...
Stogie87 said:
Hi h311sdr0id,
i see you are a developer... If you say you wan't to play with that device, does that mean you have intention to build a custom rom or kernel for p600
This would be the best news since 6 month for p600 owners!
Click to expand...
Click to collapse
I am trying to get back into the realm of XDA and get used to how things are (before I had to take a little vacation). The last device I developed on was a Note 3/4..
I had a lot of people pretty pissed off at me for leaving when I did, but it wasn't my choice. So I need to re-clarify a few things with anyone looking for my first post in awhile:
Any insider information I had before this post was made here, is no longer something I can talk about. If you haven't had a chance to look around and read about what happened to me, you should. I am sorry for letting anyone down, but I had to choose my freedom over a device.
Plus, any information I had (including all of the work I had saved on my computers/devices) was taken from me. I have no access to any of it and I will never see it again.
Click to expand...
Click to collapse
So now that that's out of the way... Yes, I do plan on working on a ROM for the P600.
My work was usually geared towards ODEXED Stock Roms with all the fun stuff available that DEODEX had to offer. Many of the tweaks that were strictly available to DEODEX ROMs back then had to be reverse-coded to work with ODEX ROMs. I spent a lot of time dropping down ROMs from 1.2GB down to 250MB with add-on available. But I ran (and still run) these tiny ROMs on some of my other devices and they work great to this day.
I am working on a new Live AIO Distro (Debian/Ubuntu) for Android Development. That will continue to be my largest project. But I will be working on the P600 exclusively for a while. I just got one as a gift from another DEV.
If there's anything you are interested in specifically, please let me know. I will open a ROM Thread pretty soon to get some more ideas of what people are looking for.
planetf1 said:
Though I'm not a fan of having to wait, it seems a fair comprimise. Typical "freemium" model. Slow is fine for occasional flashers, but the serious ones will want to pay. It costs to host/manage these updates so seems perfectly fair to me...
Click to expand...
Click to collapse
I used to run my ROMs with weekly updates and fixes when they needed them. But for the most part, people didn't have many issues with my ROMs because I would spend a lot of time on them and test them thoroughly before releasing them. But I also kept to only a few devices at a time. Many big developers have many devices they're working on and so it's hard to spend too much time on one or two devices specifically. Only knew a few DEVs that really kept up on devices like hat back in the day.
But, no. I won't need money for anything. I have plenty of resources available to me that won't cost anyone anything. I do this as a hobby.
Thanks for that comprehensive statement. This are great news, because development for p600 was very poor during the last month...
I think the most important things for p600 we would like to have are:
- a stable stock kernel with permissive rights
- development support for cm 13, because many things doesn't work with it like camera, IR Blaster, Screen Mirroring and we have bad battery life. It also isn't compatible with LP 5.1.1 Bootloader (causing sound issues, random reboots etc.)
- A fast and debloatet stock rom with permissive rights, performance and batterylife optimizations
If you would be able to work on only one of these points, you would be a hero for most p600 owners
Any chance you would be willing to work on a sm-607t rom?
Im not cooking since windows mobile, but ill test.
I can also upload a backup of the stock rom to mega so you dont have to wait 8 hrs to download it.
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.