Database Users

Atrix Re-Birth Project

This page is dedicated to make a stable ICS-JB for the Motorola Atrix
Brief history about the project:
- Un unstable ICS for Motorola Atrix was leaked
- Developers worked on integrating kernel and drivers into existing build
- Kernel was found to be very unstable and new kernel is being ported to Atrix
- While we wait for the kernel, an ICS CM9 build is ready for anyone willing to join the challenge
Next step:
- Developers should get involved in fixing/enhancing the current build
- Code submission is done by forwarding the changes to the head development team for inclusion
Build source code is all available to anyone willing to participate. The build process follows CyanogenMOD builds.
Source Code location: https://github.com/MROM/android/tree/ics
Curent Team:
Project Managers: marcovrv and R3PL1C/\NT.
Head Developers: Epinter, MMontuori, and TPoint75.
Kernel developers: mvniekerk
Developers: Hayander, scanuto, ravilov, geleiahp, alberto88a, tachospeedo, Isaygarcia, digidrops, fanfantasy, hainguyen273, and caster62003.
Testers/Advanced Users: Carcara, EkzoMan, EMG92, Hayander, BusWah, Girafik, clockworkninja, rspaulo, Bravo9000, vigremrajesh, jlm-familiar, The-Milkybar-Kid, r3xx3r, ovitz, lightlord, ticiano_arraes, reix2x, Nargyle, diegofdg, shabeepk, pixut, Kaworu33, jhonnyx, Haxornator, fanhtc2, julian_fern, iximedaixi, heibailife, shadowed87, Matada02, Zeljko1234, tatperson, dibi91, NemeZZiZZ, Moonshield, bimasakti85, Cocolopes, Pont91, jeanpiere, pre4speed, jeffreygtab, nachobkcc, BravoMotorola and littleemp.
Without help, this project cannot continue.

Count me in for Rebirth
mmontuori said:
Dear fellow Atrix owners,
We all know by now that Motorola has cancelled the plans for upgrading to ICS, I was hoping myself to get the new drivers to update my own rom to ICS or JB. Well, this is not going to happen...
What do we do now?
We can either assume this is the death of this revolutionary device, or work on the Re-Birth. You probably know, but there are a group of developers working on upgrading the current Gingerbread version to ICS or JB. I am personally one of them...
We all need your help... we are donating our precious time and resources to make the Atrix 4G a better device that could last for another year or two, however, alone, we cannot continue with this...
WE NEED YOUR HELP...
If you are still reading this message, good, now it's time to decide if the Atrix is going to die in the couple of months or live for some time. We are looking for:
- People that can write code and troubleshoot (Android Java and C/C++)
- Testers
- Project managers (believe it ICS or JB is a full SDLC project)
- Android Advanced users not too scared of trying something new on their phones
- Donate Atrix Devices that you no longer need
- Of course, donations to at least justify the amount if time we spend on this
- If I forgot something, please reply to this thread with suggections
Again, you decide DEATH or RE-BIRTH
Take Care
Click to expand...
Click to collapse
It is certainly great to see commitment of this kind. I'm no DEV nor do i possess programming skills which could assist you. But please feel free to count me in as a tester and advanced user, more than willing to get his feet wet .

I will glady donate, as should others who wish to revive this device that surely isnt really outdated

I would love to be a tester and advanced user. I have 2 atrixes, so I can test to any extent on one of them. I would donate one but I need to have my main atrix as a backup to the s2 I am in the process of buying. So my backup backup is there for testing anything and everything needed.

I would have no problem in donating except I don't see anyone claiming that it is at all realistically possible to get the full ICS experience in our phones (meaning hardware acceleration and working camcorder). If that changes, I'd be happy to donate to keep my phone alive, but if it's just going to be another dissapointing waiting game with no outcome...
PS: Don't get me wrong, I'm not trying to rain on your parade or be an ungrateful bastard as I do really appreciate the work all of you devs put on this. I'd be happy to give money for a bounty.

i'd personally donate 50 dollars to the cause of keeping our phones alive. probably more as time went on as well, just to keep the project alive.
i would also be willing to test ANYTHING on my Atrix, as i have plans of replacing it soon anyways. the fingerprint scanner doesn't work anymore, and the touchscreen is dying.

I'm JUST NOW getting an Atrix and a Lapdock, a little late I know But count me as an advanced user willing to test anything. I hope to get webtop (In non-blur roms) working above all else, unfortunately since moto isn't willing to comply, that is also the most difficult task.

- Android Advanced users not too scared of trying something new on their phones
Click to expand...
Click to collapse
Count on me!

Love the intiative :fingers-crossed: I don't have any technical skills to share, but I'm willing to test and assist in any other way that I can.
Maybe we should get this posted on the Photon forums as well to consolidate the project?

Would you be able to develop a 3.x kernel?
Sent from my MB860 using xda premium

Tester and advance user!...
from the (m)ATRIX...

mmontuori said:
Dear fellow Atrix owners,
- People that can write code and troubleshoot (Android Java and C/C++)
Click to expand...
Click to collapse
One more developer ready here !

So you want to build a real ICS/JB ROM for Atrix?
Including a 3.x kernel, hardware acceleration and maybe working webtop?
If at least the first two things apply I would gladly donate for this one.:good:

nachobkcc said:
Count on me!
Click to expand...
Click to collapse
+1 :good:

You guys can count on me as a tester and advanced user!
Sent from my beloved Atrix

Android/Java developer over here. (Also some knowledge in C/C++)
Contact me via : [email protected]
---------- Post added at 01:07 AM ---------- Previous post was at 01:07 AM ----------
Android/Java developer over here. (Also some knowledge in C/C++)
Contact me via : [email protected]
If there is something i can do that doesn't take me a very lot of time (because of the for-a-life work)

This is possible but requires more than a couple of devs working close together to make it come true. And ofcourse, it will spend us certain time for fix the problem of Nvidia named Tegra2 by re-developing a brandnew driver for our device.
Once this mission completed, we can completely go further ahead to open up other attractive projects on this worth device

Definitely advanced user and tester. Have strong experience on tech related project management, just not on software development projects. Novice on java, almost intermediate on C, advanced in Pascal (dead language I know), but I think I'm a quick learner.
Have a "real" job, so time is limited but can arrange something. Just tell me where I can help.
m.rodriguez<at>computer.org
Sent from my MB860 using xda app-developers app

I am honored to be a member of this community!
Not a dev or a programmer here, but will do anything I can to give support.
Thank you all!
Sent from my MB860 using xda premium

I have some experience in Java, C/C++, the Android Framework and I am willing to learn more. But I also think, a project management is necessary to order issues, make possibilities clear, have a big picture, sharing knowledge. So, when you start, drop a message.

[Q] Some essential documentation badly needed

I read @Entropy512 write somewhere "we are more in need of developers than of testers at the moment"
To that effect I want to make an appeal to @maxwen @XpLoDWilD @Entropy512 @pulser_g2 and all other people who started the initiative to properly document out a few things
1. If a device maintainer wants to get his device added to omni ROM what should the steps be ?
2. To set up a omni ROM - compliant device tree what are the prerequisites. As in omniROM trees have been seen to be using a format of aosp.mk+custom.mk device makefiles where aosp.mk makes it AOSP-compliant and custom.mk is the omni additions. How custom.mk is to be made (a template maybe ?) should be be documented. In fact I would go out to say a device/custom/sample tree should be made as an example
3. Are there any guidelines as to how much the hardware side codes can be hacked with to make the devices supported ? (Many groups of developers have forks of hardware/qcom/* repos that are pretty liberally spread with #ifdef's and makes them break CTS/CDD in a huge way). How much will these hacks be supported ?
4. Obvious point, what are the fields in which you need help most badly as of now. That is to say ril/telephony experts are highly needed right now or are features the topmost priority or is the highest concern to make the hardware repos tip-top so that devices are completely stable
Also publishing some guides on how to get sources and build the ROM would be good too, but since you are looking for "Developers" right now, it can be assumed that they will figure that much out on their own at least

This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home

Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!

Entropy512 said:
Among other things I want to do is a "patches for a given feature" document so it's easier to find out how a given feature (such as status bar brightness) was implemented.
I really want to do it before I have too many patches to put in there, but I also have tons of stuff to fix!
Click to expand...
Click to collapse
What do you think about this idea? These common kernel patches could also fit into that document.

pulser_g2 said:
This documentation will be done.
Actually one of the key goals of omni is to properly document things.
Bear in mind exactly how early this is in the process - it was only yesterday we even made the links available for github...
Documentation will be a large part of going forward and it has been ongoing for a while. Currently that's the biggest task actually, much moreso than the actual development.
Developers don't only write code, they also write docs
To that effect, http://docs.omnirom.org is going to be the home
Click to expand...
Click to collapse
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)

championswimmer said:
if I can be of any help let me know,
I would love to see this project start off right from the beginning with proper documentation about EVERYTHING
also +100 to @Entropy512 's idea. documenting each feature and how it has been added is really important
I strongly urge that submissions via gerrit should be enforced to have a well written description in the commit message too. (it is so much easier now with gerrit 2.7+ we can do it right inside our browser after the patch has been uploaded too)
Click to expand...
Click to collapse
Yup. I've always tried to have a detailed commit message in anything I create, but I think we may need to start enforcing it so everyone does it.

Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?

orangekid said:
Is there any kind of current features / bugs / patches list on the official build? Or even just a changelog?
Click to expand...
Click to collapse
There are no official builds yet. Too early for that.
so much work to do.

Entropy512 said:
There are no official builds yet. Too early for that.
so much work to do.
Click to expand...
Click to collapse
Oh, I was under the impression there was a compiled "official" version for the N4, N7, etc...
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..

orangekid said:
No worries, in due time I'm sure. Be looking forward to the Nexus 5 build..
Click to expand...
Click to collapse
give us the device first

I follow Omni for the Nexus 5. Nightlies have started since Monday so I'd like to know if there's a general Omni changelog now or a specific one for each device.

I'm a developer without much ROM/Android development. I'd love to give a hand wherever possible, but like @championswimmer said, it's kind of overwhelming to jump in and help. I'm totally cool to be relegated to documenting things if that helps, but I also understand the interruption that it would cause for you guys to slow down long enough to explain what I need to know.
What I do have experience with:
Java
Jenkins
Minimal app development
Other crap that might or might not be helpful

[APP][DEV][WIP] DemiGod RPG for android

Hello everyone,
This is my first thread on XDA, and also my first time using github. I have been learning java for android for ~3 years now, and feel there is still much to learn. As an all-time gamer, I would absolutely love to make one of my own.
I have recently started my 1st open-source project on github. I am still learning quite a bit, and am looking to create a retro-style, turn-based RPG for android. Any collaberators feel free to chime in, offer advice, bring new ideas to the table, etc...
This project is just beginning and the downloads may not be fully functional as of yet. Downloads serve mainly for testing purposes for now, but feel free to check it out. Please let me know what you think.
WORKING SO FAR:
* Stats and Inventory Databases
* Character creation (Choose name and class)
* Simple Battle mechanics
* Enemy Database
* Random enemy from database used in battles
* Level-ups
* Status Screen
* Viewing pre-populated Inventory (No using/exchanging items yet)
KNOWN ISSUES:
* Re-positioning Virual D-Pad when it's size is bigger than screen causes a force close
* D-Pad position gets skewed when re-sizing caused by it not accommodating for D-Pad Position setting
* Map's/Area's bounds are not set (Graphics still being worked on)
Storyline:
Unknowingly, you are a demigod. Half mortal, half god. Ever since your early teenage years, you have had "incidents" in which you never quite understood the nature of. Sudden outrages, blackouts, and waking up feeling completely exhausted.
The more the hero aged, the more frequent the uncontrollable events would occur. Finally the hero can't help but to believe it is some sort of witchcraft, cursed as a child. For this may not be completely false, the hero is soon to find out his true origins...
Github link: https://github.com/MattMatt0240/DemiGod
* Licensed under GNU GPL v3

Credits:
@nikwen (introducing the idea of open-source to me/ help in development threads)
@ADDICT.ANK (collaborator, helping hand)
@sak-venom1997 (collaborator, helping hand)
Please let me know if you're left out

FAQs/downloads/screenshots
Download:
* Alpha v0.02 (Preview/Testing)
* Alpha v0.01 (Preview/Testing)

MattMatt0240 said:
Credits:
@nikwen (introducing the idea of open-source to me/ help in development threads)
@ADDICT.ANK (collaberator, helping hand)
Please let me know if you're left out
Click to expand...
Click to collapse
Well great. Thanx bro you created the thread required
and pls reserve a couple of post row for later updating..
Lets go for it then.

As i developer i see firm reasons to join it
But few questions arise in my mind and it will be good for all if answered in the op
* What is the storyline for this game ?
* Under which lisense is this app available ? (Creative Commons ,GPL ..)
I suggests adding requests for things you want to add in the github repo
Sent from my GT-S5302 using Tapatalk 2

sak-venom1997 said:
As i developer i see firm reasons to join it
But few questions arise in my mind and it will be good for all if answered in the op
* What is the storyline for this game ?
* Under which lisense is this app available ? (Creative Commons ,GPL ..)
I suggests adding requests for things you want to add in the github repo
Sent from my GT-S5302 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the suggestion. This is my first thread here on XDA, also my 1st time using github(or any repo for that matter).
Pretty much my 1st time taking my code anywhere else from my personal computer and sharing my code/ideas with anyone besides my wife (who could care less about all of it). I have been learning java/android all by myself for a while, and could use some help and/or insight from someone more experienced.
Welcome aboard :thumbup:
Noted to self thrice via tapatalk

MattMatt0240 said:
Credits:
@nikwen (introducing the idea of open-source to me/ help in development threads)
@ADDICT.ANK (collaborator, helping hand)
@sak-venom1997 (collaborator, helping hand)
Please let me know if you're left out
Click to expand...
Click to collapse
Haha. Thanks.
MattMatt0240 said:
Reserved for FAQs/downloads/screenshots
Click to expand...
Click to collapse
Wow, looks good. Is that a mockup or do you already have this working?

nikwen said:
Haha. Thanks.
Wow, looks good. Is that a mockup or do you already have this working?
Click to expand...
Click to collapse
I started working on this a while back (in a different project to learn from). Realized many of my errors in doing so, so started fresh. The screenshot is just a basic idea of how I want the gameplay to look like, and is not quite functional yet. I do all of the art myself (so far) but there are many aspects in which I'm not quite sure how to make work, such as inventory/shops, and maps.
If there's anything you see that you feel can be improved, please feel free to let me know
Thanks nikwen!
Noted to self thrice via tapatalk

Would you mind pushing the merged code to new branched and deleting the bin folder
These non essential files make the repo huge and people like me with slow internet have problems synchronising
Sent from my GT-S5302 using Tapatalk 2

sak-venom1997 said:
Would you mind pushing the merged code to new branched and deleting the bin folder
These non essential files make the repo huge and people like me with slow internet have problems synchronising
Sent from my GT-S5302 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I meant to do it sooner. Been busy the last few days, will do it soon. Should be done by the time you get on. I don't have much of a base yet, this is really just the start of an idea.
Noted to self thrice via tapatalk

Should be good now sak. I have slow internet as well, very slow unless I manage to find 4g at my house. I downsized the repo quite a bit, so it should be better for us all
Noted to self thrice via tapatalk

@sak-venom1997 I added a PreferenceActivity (settings) and made the D-Pad repositionable via those settings
If you get a chance, check it out and let me know what you think.
Noted to self thrice via tapatalk

MattMatt0240 said:
@sak-venom1997 I added a PreferenceActivity (settings) and made the D-Pad repositionable via those settings
If you get a chance, check it out and let me know what you think.
Noted to self thrice via tapatalk
Click to expand...
Click to collapse
What's about posting apks here or on Github every now and then? I'd love to give it a try but I don't want to build it myself every time.

nikwen said:
What's about posting apks here or on Github every now and then? I'd love to give it a try but I don't want to build it myself every time.
Click to expand...
Click to collapse
Wow, still new to github, didn't know they had a release system I could do that and put a link in the O/P. Keep in mind that (at this point) it isn't necessarily playable, but at least everyone could get a feel for it and put up suggestions
Noted to self thrice via tapatalk

MattMatt0240 said:
Wow, still new to github, didn't know they had a release system I could do that and put a link in the O/P. Keep in mind that (at this point) it isn't necessarily playable, but at least everyone could get a feel for it and put up suggestions
Noted to self thrice via tapatalk
Click to expand...
Click to collapse
Exactly.
So do it and lets gather the suggestions.
Sent from my LT26i using xda premium

nikwen said:
What's about posting apks here or on Github every now and then? I'd love to give it a try but I don't want to build it myself every time.
Click to expand...
Click to collapse
ADDICT.ANK said:
Exactly.
So do it and lets gather the suggestions.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Added download link to 3rd post. Constructive criticism is welcomed
Noted to self thrice via tapatalk

MattMatt0240 said:
Added download link to 3rd post. Constructive criticism is welcomed
Noted to self thrice via tapatalk
Click to expand...
Click to collapse
Thanks.
Looks good. Crashes very often but it's good considering that it's in its infancy. :good:
Will the character turn around when he's moved?
For sure I'll follow the development.

nikwen said:
Thanks.
Looks good. Crashes very often but it's good considering that it's in its infancy. :good:
Will the character turn around when he's moved?
For sure I'll follow the development.
Click to expand...
Click to collapse
Yes, I just need to crack down on drawing up some sprites Lol. Crashes may be caused by not creating a character first, and possibly a few other things that will be put in order in final production.
I was thinking of having the user being presented with a "setup" screen where they will have to adjust the D-Pad position and size. There's a few bugs in there I think. All of the activities are placed on the title screen temporarily simply for ease of access during development.
Regardless, thanks for the feedback, and yes it is still very early. I'm trying, and learning a whole lot quite fast
Noted to self thrice via tapatalk

Just a little update:
I have been working on trying to find an organized mapping system and think I found a satisfying solution. Before it was all hard-coded in java files leaving it a mess to read, and an activity for every "map" area.
Now, the maps will all be written in XML with a number identifier, which corresponds to the appropriate tile, translated by a separate java class. I tried using JSON, but @nikwen made a valid point... XML is more versatile and easier to read/use, thanks bud!
The inventory database has the path to the corresponding asset icon for each item, making it possible to match "xItem" with its relative icon. I was thinking I should do the same for enemies (once they are drawn). Enemy images are 100x100 pixels, used in battles, whereas item icons are the standard 32x32 px.
I also started playing around with animations, and obviously have much to learn on it.
I'll update the OP with another download, not much progress but still a lot of changes. Anybody feel free to chime in.
Noted to self thrice via tapatalk

MattMatt0240 said:
Just a little update:
I have been working on trying to find an organized mapping system and think I found a satisfying solution. Before it was all hard-coded in java files leaving it a mess to read, and an activity for every "map" area.
Now, the maps will all be written in XML with a number identifier, which corresponds to the appropriate tile, translated by a separate java class. I tried using JSON, but @nikwen made a valid point... XML is more versatile and easier to read/use, thanks bud!
The inventory database has the path to the corresponding asset icon for each item, making it possible to match "xItem" with its relative icon. I was thinking I should do the same for enemies (once they are drawn). Enemy images are 100x100 pixels, used in battles, whereas item icons are the standard 32x32 px.
I also started playing around with animations, and obviously have much to learn on it.
I'll update the OP with another download, not much progress but still a lot of changes. Anybody feel free to chime in.
Noted to self thrice via tapatalk
Click to expand...
Click to collapse
Good progress.
Looking forward to more improvements.

Sprint device tree bounty

Hello.... I'm starting this thread to set up a bounty for a working device tree.. For the sprint note 4..I am lacking in time to create one myself but have all the experience and ability to use it... So figured I'd offer a bounty to anyone willing to create us a working device tree to use to build Roms from source.... What I'm wanting is a tree that I can build cm and aosp based Roms from.... I'm not asking for Roms I'm asking for a tree that works that I can use to build the Roms myself as well as others.....
If interested in chipping in please list the amount and I'll add your name to the list..... Please Only people who are actually going to donate when/if the time comes ..
Thanks
Bounty:
spleef : $75
Herk718 : $20
Total: $95

@Herk718 $20

I understand the intention here, but I've always found that bounties immediately move work into closed repos, discourages collaboration, and raises questions about who gets the $ if for example, someone gets it 99% there but someone else jumps in for the last step. Will the bounty be split among all collaborators? Will you award the authors of any device repo you fork from? (It's turtles all the way down)
If you want development in the open and people helping each other to get your goal, consider not having a bounty as it's almost never the primary motivator for this kind of work... And often works against what you want. I can tell you personally... My experience with the nook tablet and bounties from a company that wanted to sell the port was pathetic. People were constantly hitting me up on irc and in PM for help, and stealing each others work, and making tiny changes to claim the bounty. Go back and read the forums for acclaim...
Or, look up what happened with the HP Touchpad, which is even more egregious... That fiasco made it to the blogosphere... But the code was flat out stolen and the irc logs pretty jaw dropping.
This is a MUCH smaller project, but still...

fattire said:
I understand the intention here, but I've always found that bounties immediately move work into closed repos, discourages collaboration, and raises questions about who gets the $ if for example, someone gets it 99% there but someone else jumps in for the last step. Will the bounty be split among all collaborators? Will you award the authors of any device repo you fork from? (It's turtles all the way down)
If you want development in the open and people helping each other to get your goal, consider not having a bounty as it's almost never the primary motivator for this kind of work... And often works against what you want. I can tell you personally... My experience with the nook tablet and bounties from a company that wanted to sell the port was pathetic. People were constantly hitting me up on irc and in PM for help, and stealing each others work, and making tiny changes to claim the bounty. Go back and read the forums for acclaim...
Or, look up what happened with the HP Touchpad, which is even more egregious... That fiasco made it to the blogosphere... But the code was flat out stolen and the irc logs pretty jaw dropping.
This is a MUCH smaller project, but still...
Click to expand...
Click to collapse
@fattire
I do understand where you are coming from...these bounties most always end badly where someone does exactly as you described but let me try to ease some of your doubts....
What I'm looking for is for a person or team to step forward... Then after a discussion with them I'll add their name to the op as being the person doing the task.... Now no matter who else jumps in or steals code the money will only go to the person or team that I've talked with and is listed in the op..... So far as money split.... I would... during our discussion prior to having someone accept the task... And listing them as accepting the project talk this over and have it all mapped out as who gets what. What I'm expecting... What they're expecting.. The whole nines... Now these type of situations have a tendency of folks saying I'll donate then don't... If that were to be the case I'll donate the full amount myself... To address the closed repo.... I have a github account and have had one for years as well as being an XDA member for ages.... With a very good reputation.... My account on github is open and always will be... The idea here is to have a source for the public not just me...I have no intention on making anything private or closed source...... My only intentions are too get a device tree that we can use to build cm and aosp based roms from source... The idea of the bounty is solely to draw attention and offer a incentive to someone who is interested, willing, and able to provide us with the tree... I hope I've cleared up at least a little of your worries/doubts....And to be perfectly honest ...I hope that you and slayher accept the task... If you need to further discuss anything please feel free to contact me...I have several ways of doing so listed in my profile but I'll go ahead and list my hangouts info... [email protected]

Enjoy. https://github.com/slayher/android_device_samsung_trltespr

slayher said:
Enjoy. https://github.com/slayher/android_device_samsung_trltespr
Click to expand...
Click to collapse
Whoa... He's a wizard.
Sent from my SM-N910P using XDA Free mobile app

Slayer gets my donation he and always will be the captain
Sent from my SM-N910P using XDA Premium HD app

@slayher
Nicely done...I understand its a wip but using this I will be able to build? And will you continue to fix it up as things progress or is this a here it is I'm done sort of thing?

I dont have one, so will be happy to take input. It *should* build though. Just need to setup trltespr props

slayher said:
I dont have one, so will be happy to take input. It *should* build though. Just need to setup trltespr props
Click to expand...
Click to collapse
Willing to give u my wifes with a bad esn cause she thought she lost it
Sent from my SM-N910P using XDA Premium HD app

I am fine with that, but its hard to test mms/sms calls etc with a bad esn.

I can be the guinea pig. Yaaay.

Slather I have N910R4 USC. I can build test for our variant. Thanks for helping us out.
Sent from my SM-N910R4 using Tapatalk 2

Mod57 said:
Slather I have N910R4 USC. I can build test for our variant. Thanks for helping us out.
Sent from my SM-N910R4 using Tapatalk 2
Click to expand...
Click to collapse
Heh I came to post that Slayher started a repo but there ya go.. guess he posted it already No worries on the bounty thing-- I've just seen it go bad before... it was a cluster****. That was a 3-month project tho.. this shouldn't be anything like that.

fattire said:
Heh I came to post that Slayher started a repo but there ya go.. guess he posted it already No worries on the bounty thing-- I've just seen it go bad before... it was a cluster****. That was a 3-month project tho.. this shouldn't be anything like that.
Click to expand...
Click to collapse
Well I'll still donate my promised portion will do it today.... Thanks a bunch i have the weekend off so I'll be attempting to build once i get off work today
slayher said:
I dont have one, so will be happy to take input. It *should* build though. Just need to setup trltespr props
Click to expand...
Click to collapse
Good deal can't thank you enough.... Am going to try using it after work toda... Mind if I get your hangouts info makes things much easier to communicate if something goes funky
I'm going to close this thread today since the tree is in place we no longer need it guys can post in the cm12 thread here in the general section until I get the build uploaded then will create a thread in development section.... Thanks again @slayher @fattire y'all are outstanding.... Very glad to have people like you in the xda

Source Code

Looks like Huawei has posted some source code online: http://m.huawei.com/enmobile/consumer/support/downloads/index.htm with the label: FRD-L04_MM_EMUI4_1_opensource
I'm downloading it now, hopefully it's something good and useful!

anks329 said:
Looks like Huawei has posted some source code online: http://m.huawei.com/enmobile/consumer/support/downloads/index.htm with the label: FRD-L04_MM_EMUI4_1_opensource
I'm downloading it now, hopefully it's something good and useful!
Click to expand...
Click to collapse
It's broken (as always, bunch of liars), I have uploaded it to github so you can download it at a decent speed: https://github.com/XePeleato/android_kernel_huawei_FRD-L04 (ignore build.sh, it's the script I use to build it)
EDIT: Fixed, as always, check github, I haven't tested it, but if you want me to upload a flashable .zip, I'd need your fstab file.

Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?

Syssx said:
Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?
Click to expand...
Click to collapse
There's just one way to know! But honestly, the kernel as it is now, doesn't have any improvement, however it might be useful for a developer who wants to code a custom kernel or something like that.

Glad it's in a buildable state. Now, let's see what else Huawei is going to release.

--I think I should wait until I post my reply --

Hey Guys,
Just so you know, I have a direct line at Honor and am able to make requests as it relates to releasing sources and specific documentation. I am not a developer myself, but you guys can feel free to make requests here and I'll bring it back to Honor. It's really important that we get to the point where custom ROM development and full modification is possible on the Honor 8!

svetius said:
Hey Guys,
Just so you know, I have a direct line at Honor and am able to make requests as it relates to releasing sources and specific documentation. I am not a developer myself, but you guys can feel free to make requests here and I'll bring it back to Honor. It's really important that we get to the point where custom ROM development and full modification is possible on the Honor 8!
Click to expand...
Click to collapse
Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!
working kernel code - kinda have this XePeleato's work
device tree
full firmware images (for backup/restore use)
proprietary vendor files
documentation on the SoC

anks329 said:
Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!
working kernel code - kinda have this XePeleato's work
device tree
full firmware images (for backup/restore use)
proprietary vendor files
documentation on the SoC
Click to expand...
Click to collapse
Why would you need a "device tree"? I can create a working one for you in 5 minutes. (I know what you mean, the HAL drivers are not inside the device tree, I'd try to be more specific if you want them to understand what you are asking for)
svetius said:
Hey Guys,
Just so you know, I have a direct line at Honor and am able to make requests as it relates to releasing sources and specific documentation. I am not a developer myself, but you guys can feel free to make requests here and I'll bring it back to Honor. It's really important that we get to the point where custom ROM development and full modification is possible on the Honor 8!
Click to expand...
Click to collapse
Cool, I'd love to talk to them personally, but since that doesn't look possible, I'd like to ask for some things (It feels like Christmas lol)
Specific documentation (Code snippets, a document... you know) about:
Their OpenGL implementation​The Hi110X communications IC (Integrated Circuit)​The Audio system​The Camera, other companies with the same sensor released their drivers source so it isn't Top Secret​The SePolicy​
That would be a good starting point and in my opinion it's pretty reasonable.

XePeleato said:
Why would you need a "device tree"? I can create a working one for you in 5 minutes. (I know what you mean, the HAL drivers are not inside the device tree, I'd try to be more specific if you want them to understand what you are asking for)
Click to expand...
Click to collapse
My thought was, if we're asking, might as well go all out and get something like what OnePlus released for the 3. A full working device tree, kernel, etc.... http://www.xda-developers.com/onepl...-3-device-trees-and-kernel-sources-available/

anks329 said:
My thought was, if we're asking, might as well go all out and get something like what OnePlus released for the 3. A full working device tree, kernel, etc.... http://www.xda-developers.com/onepl...-3-device-trees-and-kernel-sources-available/
Click to expand...
Click to collapse
One Plus did went forward and released proprietary blobs for Dash charging that were supported on AOSP based ROMs. If Huawei don't want to release source codes for their OpenGL, Hi110x, composer, camera, etc implementations, then at least proprietary blobs free from EMUI crap that work with AOSP (this is the least I want; source code is always good as it means we don't have to depend on Huawei if things break or if we want to develop future versions of Android which if aren't released officially by Huawei).

anks329 said:
Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!
working kernel code - kinda have this XePeleato's work
device tree
full firmware images (for backup/restore use)
proprietary vendor files
documentation on the SoC
Click to expand...
Click to collapse
From this list, what are the "must-haves"?
Would be nice for others to chime in.

svetius said:
From this list, what are the "must-haves"?
Would be nice for others to chime in.
Click to expand...
Click to collapse
The most important things we need are:
Proper documentation about the SoC and if possible, a Board Support Package for Kirin which will greatly boost development.
Proprietary blobs which don't include EMUI crap and Huawei's mistakes.
We already have the kernel source which thanks to Huawei was zipped in a non-case sensitive OS and the stock firmware images to extract vendor blobs (which don't work well with AOSP/CM).

hackslash said:
The most important things we need are:
Proper documentation about the SoC and if possible, a Board Support Package for Kirin which will greatly boost development.
Proprietary blobs which don't include EMUI crap and Huawei's mistakes.
We already have the kernel source which thanks to Huawei was zipped in a non-case sensitive OS and the stock firmware images to extract vendor blobs (which don't work well with AOSP/CM).
Click to expand...
Click to collapse
While in my opinion this is totally correct, it's also crucial to ask for reasonable stuff or Honor will think that We are just noobs asking for a 'git pull && make' solution, (that they will obviously not support).
I know this was anks' idea, but by asking for binary blobs ready to use with stock android, you are really telling them to code again a big part of their drivers and libraries. They won't do that since they are not going to put that much effort just to please us. Maybe We can suggest them to 'organize' their code for future phones.

XePeleato said:
While in my opinion this is totally correct, it's also crucial to ask for reasonable stuff or Honor will think that We are just noobs asking for a 'git pull && make' solution, (that they will obviously not support).
I know this was anks' idea, but by asking for binary blobs ready to use with stock android, you are really telling them to code again a big part of their drivers and libraries. They won't do that since they are not going to put that much effort just to please us. Maybe We can suggest them to 'organize' their code for future phones.
Click to expand...
Click to collapse
I guess I was dreaming way too much. I'm expecting too much from someone who has delivered nothing in the past. We'll keep it simple then. Honor, please release Kirin documentation, schematics and Board Support Package.

Both @hackslash and @XePeleato make great points. I guess I was going for a wish list, dream case option where they would be willing to put in some work for us. Realistically, I agree, good documentation and organized code will go a long way. Would it be possible to keep the lines of communication open? If there's an issue developers run into with the released code, if we can go back and ask for something additional/clarifications.

anks329 said:
Both @hackslash and @XePeleato make great points. I guess I was going for a wish list, dream case option where they would be willing to put in some work for us. Realistically, I agree, good documentation and organized code will go a long way. Would it be possible to keep the lines of communication open? If there's an issue developers run into with the released code, if we can go back and ask for something additional/clarifications.
Click to expand...
Click to collapse
I also have the same question. Since @svetius is going to be a middle man and he will carry our queries to the Honor, it would have been much better if a group of members at XDA who have experience with Kirin devices were selected and were allowed to do the talking. This way, that group could better address the problems faced in developing and the stuff which is need to implement Kirin's proprietary stuff.
Atleast there should be a separate thread here in XDA which is solely for the purpose of addressing all queries to @svetius which he would carry on to Honor. At this point, I am clueless what's happening with the partnership and if there has been even some communication regarding this between the two partners.

All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?

svetius said:
Hey Guys,
Just so you know, I have a direct line at Honor and am able to make requests as it relates to releasing sources and specific documentation. I am not a developer myself, but you guys can feel free to make requests here and I'll bring it back to Honor. It's really important that we get to the point where custom ROM development and full modification is possible on the Honor 8!
Click to expand...
Click to collapse
Setup a page on their website for developers like what SONY has been doing.

scafroglia93 said:
All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?
Click to expand...
Click to collapse
Of course We have the kernel source, go ahead and build CM with it.