Database Develop

Source code (Android kernel, Ubuntu) now available

I didn't notice this when it happened, but it was pointed out in IRC (and not on the forums yet, I believe). The Android kernel and Ubuntu source code has been release in Motorola's usual site. I know some people have been waiting for tun.ko and cifs.ko - here's your chance. I might play around with a few modules myself, but I'm more excited about the Ubuntu source code release.
P.S. Oh, the people who were bellyaching and talking about how HTC was better than Motorola because HTC released kernel source code for some devices? Eat your heart out.
Credit to [http://forum.xda-developers.com/member.php?u=512640]jiggytom[/u] for pointing it out to me. This should have been in the original post.

awesome. thank you moto, finally opening some doors, even if it's just a little bit
it would be pretty sweet if they showed canadian customers some love and released source for the Bell Atrix as well :/

raybond25 said:
awesome. thank you moto, finally opening some doors, even if it's just a little bit
it would be pretty sweet if they showed canadian customers some love and released source for the Bell Atrix as well :/
Click to expand...
Click to collapse
I'm certain that for the source they released, it's identical for all released devices. The kernel version isn't going to be different, nor that for any of the webtop packages. Any differences lie elsewhere, and I don't expect Motorola to ever release that source code.

Sogarth said:
I'm certain that for the source they released, it's identical for all released devices. The kernel version isn't going to be different, nor that for any of the webtop packages. Any differences lie elsewhere, and I don't expect Motorola to ever release that source code.
Click to expand...
Click to collapse
good point. it's just annoying that the frameworks files aren't cross compatible - because almost any ROMs that will be released will rely on framework changes and landing AT&T edited frameworks on a Bell Atrix causes a soft-brick (i've tried, lol)
i guess we just need a canadian dev, or someone who's nice enough to effect some of the current AT&T framework changes that can be made to Bell frameworks.
I would if I knew how, and who knows, maybe i'll try and puzzle through it.

For what it's worth, I believe I pointed it out on irc.
Sent from my MB860 using XDA App

so what will this give us atrix users?

jiggytom said:
For what it's worth, I believe I pointed it out on irc.
Click to expand...
Click to collapse
To me, true. Not sure if anybody pointed it out to anybody before me (and they just decided not to tell anybody else). I was thinking about what to do about that, but credit where credit's due, right?

AHHHHH HEEELLSSS YEEAAHHH!!!!!! So what do we do now?

we just need the unlocked bootloader now!

Interesting, assuming the kernel compiles from the source, no extra proprietary files needed, I would be interested getting aufs.ko installed and working. My idea being that all the mods done here could be applied via the fs overlay and leave the stock system partition alone for updates. I know that init.d support is a bit of a hack via recovery.sh, no way to edit init.rc atm, so not sure if an overlay could be applied on the fly without issues while android is loading.

NFHimself said:
Interesting, assuming the kernel compiles from the source, no extra proprietary files needed, I would be interested getting aufs.ko installed and working. My idea being that all the mods done here could be applied via the fs overlay and leave the stock system partition alone for updates. I know that init.d support is a bit of a hack via recovery.sh, no way to edit init.rc atm, so not sure if an overlay could be applied on the fly without issues while android is loading.
Click to expand...
Click to collapse
There are entry points into init.rc, but I don't think you can replace it mid-flight. I'm using one of those entry points as it is.
You'd also hit the other problem I'm hitting, of trying to figure out what storage devices are available when. I'm not currently aware of any way to force the SD card to be loaded earlier, for example (even though I'd love that).

I'm sorry for my ignorance.
I am not a developer so I have a question, How will this be beneficial to the Atrix users?
Can this lead to an unlocked bootloader/custom roms?
What else can be gained from releasing the source code?
Thank you.

RacecarBMW said:
I'm sorry for my ignorance.
I am not a developer so I have a question, How will this be beneficial to the Atrix users?
Can this lead to an unlocked bootloader/custom roms?
What else can be gained from releasing the source code?
Thank you.
Click to expand...
Click to collapse
It will make it easier for tweaks and optimization to occur without access to the bootloader.
It could also mean that there is a possibility for custom Roms for the truly gifted Developers who can do it without modifying the Kernel. Has happened for the Milestone and is currently being undertaken for the Milestone 2 (Droid 2)

[wip]Porting the miui

MIUI dont have any armv6 libs so its not possible to port
please close

seems like 9.pngs are not correctly ported

tobbeson said:
hi i got a lot of request in porting MIUI
my first target is the launcher and i have already hit a bump
i used apk manager to first decompile it i then noticed that it wanted to have all imagery in the drawable folder but after that i get several errors that the drawables is missing but they are not
any help on this project is apreciated
Click to expand...
Click to collapse
you just started that is all needed for miui fans[cyanogen mod still i I L U ]
REST OF THE THINGS WILL COME MAN

hi,
according to this thread http://forum.xda-developers.com/showthread.php?t=884161&highlight=miui the guys over at the hero forum have ported all the pngs to mdpi but the problem are the miui devs because they wont release the source code.

xennr3 said:
hi,
according to this thread http://forum.xda-developers.com/showthread.php?t=884161&highlight=miui the guys over at the hero forum have ported all the pngs to mdpi but the problem are the miui devs because they wont release the source code.
Click to expand...
Click to collapse
But Desire have miui ROM where they get source code... ? Can we ask them gently?
Sent from my HTC Legend

janarp said:
But Desire have miui ROM where they get source code... ? Can we ask them gently?
Sent from my HTC Legend
Click to expand...
Click to collapse
well the desire is already hdpi we only actually need source code when porting the imagery
because the 9.png (i think) is created when compiling the apps

Ok. And what is the reason that miui devs wont release source code?
Sent from my HTC Legend

janarp said:
Ok. And what is the reason that miui devs wont release source code?
Sent from my HTC Legend
Click to expand...
Click to collapse
No idea actually seems stupid they could atleast release it or they should do a mdpi version

tobbeson said:
No idea actually seems stupid they could atleast release it or they should do a mdpi version
Click to expand...
Click to collapse
Yes that was I'm thinking too.
Sent from my HTC Legend

janarp said:
Yes that was I'm thinking too.
Sent from my HTC Legend
Click to expand...
Click to collapse
actually it is illegal in most countries not to release source code
android is open sourced in gplv2(i think)
and that states that all modifications to apps and system must be released open source

tobbeson said:
actually it is illegal in most countries not to release source code
android is open sourced in gplv2(i think)
and that states that all modifications to apps and system must be released open source
Click to expand...
Click to collapse
Where we can ask this source code? Maby I try to ask them and let's see what they say to me.
Sent from my HTC Legend

they are from china and this is .... difficult

xennr3 said:
they are from china and this is .... difficult
Click to expand...
Click to collapse
LOL ... good one.
Sent from my HTC Legend

They might speak English?

alexhtclegend said:
They might speak English?
Click to expand...
Click to collapse
Well try to ask them.
Sent from my HTC Legend

checked their whole website no contact what so ever
but if there are someone that wants to port the 9.png files then we maybe could make it work

Is their stuff covered by GPL? Android being open source doesn't mean anything that runs on it has to be as well. HTC doesn't need to open source Sense for example.

Trekvogel said:
Is their stuff covered by GPL? Android being open source doesn't mean anything that runs on it has to be as well. HTC doesn't need to open source Sense for example.
Click to expand...
Click to collapse
well sense is a standalone ui (launcher) like an app
but the actual android code that they edit is released
miui is built from aosp which is covered by GPL so that means that they must release big portions of the source code

The only thing they need to release source code for is the kernel

TheGrammarFreak said:
The only thing they need to release source code for is the kernel
Click to expand...
Click to collapse
And I read somewhere that they released kernel source code.
Sent from my HTC Legend

MTK 6577 Sources [ Complete]

Hi There we have found complete sources of our phone Micromax A110 MTK 6577
We were hoping if any one Awsum Dev could compile an omni rom for our Beloved Phone here is the link to the sources http://pan.baidu.com/s/1ACPRk#dir/path=%2F8377%E8%BD%AF%E4%BB%B6%E5%8C%85
If u want u can contact our devs u can contact @[email protected] and @khan_frd2002 and also our kernel dev @varun.chitre15
And for compiling there is this guide http://wenku.baidu.com/link?url=GlZC...3XdjfuZXcip5zm
I hope i will receive Positive results and replies
Thnx
Andromodgod:cyclops:

if possible please upload to a better file hosting site. this is so slow it's causing the download to fail

cybojenix said:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
Click to expand...
Click to collapse
Thnx for the reply 2 Questions
Are you from the omni team I.E help us in making rom
How long would the compilation take
U can contact all of us we are at http://forum.xda-developers.com/micromax-a110/development
Or Here
http://forum.xda-developers.com/micromax-a110/
Link will be provided as soon as possible :angel:

I'm a contributor there. I'm just curious as to what parts they change. seeing as mtk devices are dirt cheap here, I might consider getting some to work on if their sources aren't desperately bad
edit:
compilation doesn't take long. getting to the stage of getting a working compilation may take a while though
ps can the file labelled "alps patch" be uploaded first please. thanks

Thnx
@cybojenix Thnx for ur interest in our Phone one developer @[email protected] is already working on cm 10.2
And Varun Chitre is also a great dev u can ask anyone and all of them will help u
About the mirror i dont think it is possible cuz most of the people(Dev) Live in india or other places where the Internet connection is slow u can use an extension for firefox i will link it to you https://addons.mozilla.org/en-US/firefox/addon/downthemall/
ANd please try not to post cuz if u see ur post it say """"555 Posts"""" Lucky number
U can PM Me Thnx
I will ask devs to mirror it

yes buddy mirroring is needed....the downloading speed is so less that my downld has failed more than 4 tiimes..

Alps Patch file
Here is the link to patch file @cybojenix http://d-h.st/BAg

Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.

Entropy512 said:
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Click to expand...
Click to collapse
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk

cybojenix said:
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Source are uploaded here you go http://forum.xda-developers.com/showthread.php?p=48303269
Sent from my Nexus 4 using XDA Premium 4 mobile app

[SOURCE]Full MTK6577 AOSP tree + proprietary source: http://forum.xda-developers.com/showthread.php?t=2172440
*edit: These are sources for ICS. Reason: http://forum.xda-developers.com/showpost.php?p=48307124&postcount=134

Progress
Any report on the progress @cybojenix

andromodgod said:
Any report on the progress @cybojenix
Click to expand...
Click to collapse
Sources seem somewhat unhelpful at a first glance, however going deeper into them may reveal key parts that have Been overlooked
Sent from my Nexus 7 using Tapatalk

Any Good News
DO we have any good news from u @cybojenix
We are eagerly waiting for u

andromodgod said:
DO we have any good news from u @cybojenix
We are eagerly waiting for u
Click to expand...
Click to collapse
Please, check this comments:
http://forum.xda-developers.com/showpost.php?p=48628112&postcount=43
http://forum.xda-developers.com/showpost.php?p=48642380&postcount=44

mtk你还是放弃吧，很多都没有开源的，mtk提供整套方案给生产商，连生产商都没有源代码的。
Sent from my One X using xda app-developers app

I thought it is complete
Sent from my Nexus 4 using Tapatalk

Any news?

Related:
MediaTek driver sourcecode (want custom ROMs? read this!): http://forum.xda-developers.com/showthread.php?p=50146816

No complete source, nothing to accomplish.

[NEWS] Kernel Source of 5.1 Released !

Okay, so let me get this straight.
I just checked Google Git of Android One ( https://android.googlesource.com/kernel/mediatek/ ) then I found something.
Google & Mediatek has pushed lollipop-5.1 branch ! Which means, kernel for 5.1 are ready to build
Here's the full branch just in case anyone need it :
https://android.googlesource.com/kernel/mediatek/+/android-mediatek-sprout-3.10-lollipop-mr1
and if you want to clone it and build a kernel for it, just type :
git clone https://android.googlesource.com/kernel/mediatek/ -b android-mediatek-sprout-3.10-lollipop-mr1
Cheers !

Just one question please?
F4uzan said:
Okay, so let me get this straight.
I just checked Google Git of Android One ( https://android.googlesource.com/kernel/mediatek/ ) then I found something.
Google & Mediatek has pushed lollipop-5.1 branch ! Which means, kernel for 5.1 are ready to build
Here's the full branch just in case anyone need it :
https://android.googlesource.com/kernel/mediatek/+/android-mediatek-sprout-3.10-lollipop-mr1
and if you want to clone it and build a kernel for it, just type :
git clone https://android.googlesource.com/kernel/mediatek/ -b android-mediatek-sprout-3.10-lollipop-mr1
Cheers !
Click to expand...
Click to collapse
Hey thanks for the news ( btw this news already been realeased by XDA itself and varun already grabbed it)
but there are three branch
one is named as kitkat
one is named for lollipop
so what does that third brach (android-3.18 )is for and you seems to be a well learned person( reconized contributer ) so there one question
Will google release device tree of android one devices as it does for nexus device? is there any scope for it in future (it may seem noobie to you but i really don't know)
thanks

hjmodi said:
Hey thanks for the news ( btw this news already been realeased by XDA itself and varun already grabbed it)
but there are three branch
one is named as kitkat
one is named for lollipop
so what does that third brach (android-3.18 )is for and you seems to be a well learned person( reconized contributer ) so there one question
Will google release device tree of android one devices as it does for nexus device? is there any scope for it in future (it may seem noobie to you but i really don't know)
thanks
Click to expand...
Click to collapse
Oh, it's already posted ? I'm really sorry xD (I rarely check the XDA portal, please forgive me if I repost this)
About the first question, the third branch doesn't seem to contain any tag (or I maybe too foolish to see if there's any tag), so I can assume that it's either a beta or kernel 3.18 that'll soon arrive for our device.
And for the device tree, it depends for Google and/or Mediatek. I really have no idea in this, tho.
Again, sorry if I repost this !

[DEV][G925F] CyanogenMod 12.1 Development

Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
​

Reserved

i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)

vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.

add me as participant to the repos ^^
https://github.com/OldDroid

OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them

Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.

mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?

nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support

First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying

mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then

Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer

Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?

Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself

mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk

lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset

Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.

mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.

-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes

mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.