Related
Motorola has released the sources of our smartphone
Here is the link: https://sourceforge.net/projects/motog.motorola/files/
Hehe
Motorola hasn't ''released the source'' for the G, many things needed to the fun start will probably be out along the next days. But it's a beginning
LuisUrrutia said:
Motorola has released the sources of our smartphone
Here is the link: https://sourceforge.net/projects/motog.motorola/files/
Click to expand...
Click to collapse
Bring on the hacking!
Where's my custom rom!!! hehe :laugh:
can't wait for them custom ROMs for the G!
CM11, miui, and PA ROM releases are imminent!
Sent from my XT1032 using XDA Premium 4 mobile app
Are you sure for PA MIUI and CM?
They give some information on twitter or fb?
osmoze30 said:
Are you sure for PA MIUI and CM?
They give some information on twitter or fb?
Click to expand...
Click to collapse
anyone who knows what their doing can build any of the AOSP based rom's for the moto G, with the sources available. (unofficial)
but if your asking if its been announced that the moto G is getting those officially then i have no idea.
Yes i'm talking about announcement by the MIUI , CM or PA Team. I ask it to Silencer96.
osmoze30 said:
Yes i'm talking about announcement by the MIUI , CM or PA Team. I ask it to Silencer96.
Click to expand...
Click to collapse
most official builds come from people maintaining unofficial builds, so you will more than likely see it here before its made official
New Version Source:
14.10.0Q3.X-84-14
http://sourceforge.net/projects/motog.motorola/files/14.10.0Q3.X-84-14/
As far as I can tell this is only the sources Motorola are legally required to open source.
Sorry guys, no device configs here
rymate1234 said:
As far as I can tell this is only the sources Motorola are legally required to open source.
Sorry guys, no device configs here
Click to expand...
Click to collapse
Kernel configs are included, I am running a self compiled kernel
a1Pha said:
Kernel configs are included, I am running a self compiled kernel
Click to expand...
Click to collapse
Yeah, the kernel configs are what's legally required by Motorola. Every manufacturer has to release the sources as part of the GPL. It's really nothing special
They legally don't have to but if they want to be googles favorite then they will they could release a manual and still be aosp
Sent from my SAMSUNG-SGH-T989 using Tapatalk
I'm working in a fully device config based in CM configs from other motorola phones, and i expect a build in the nearly days.
rymate1234 said:
As far as I can tell this is only the sources Motorola are legally required to open source.
Sorry guys, no device configs here
Click to expand...
Click to collapse
Is there something Motorola have not released that they have done for other phones? Would it be worth requesting?
lost101 said:
Is there something Motorola have not released that they have done for other phones? Would it be worth requesting?
Click to expand...
Click to collapse
Is licenses stuff, some android parts are GPL(Open source), these are Kernel and minor things, the rest of important part(Device and Vendor) are APACHE2 and the brands are allowed to don't release it.
Do the device and vendor repos contain drivers or just configs? Sorry for the noob question...
Sent from my XT1032 using xda app-developers app
This rss feed will notify of any changes or additions to the Moto G Source files. Numerous files appear to have been altered a few hours ago.
I am very interested in porting Xperia L to OmniRom and had starting work on it. The kitkat sources is already available anyway(see here). Compiling it is easy, just follow the instructions. I now have a working kitkat rom which unfortunately seem to have a serious bug of unable to go into deep sleep(dropped >40% over a night).
I have started work on the kernel sources and wish to invite all developers who are interested to work together.
For those of you with wifi issue, make sure that you are on stock rom 15.3.A.x.x
Extracted from Sony opensource
Most of the AOSP for Xperia L device configurations are cloned from the official Xperia L software version 15.3.A.0.x, so please make sure that you upgrade the phone software to, for example 15.3.A.0.26, before flashing the AOSP for Xperia L images, or certain functions like WiFi may not work.
Known issues/workaround:
1. There are some missing KLOG information that prevent building of the kernel( fix by disabling CCI_KLOG)
2. Deep sleep issue seem to be caused by wait_for_irsc_completion timeout(workaround by disabling
MSM_IPC_ROUTER_SECURITY)
3. Enable reboot recovery
Sources
Kernel 3.4 from Sony
Github version by me
Modified from Holofied Red Holo Theme (http://forum.xda-developers.com/showthread.php?t=2405512)
Count me IN
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Best of luck mate! @ Ghostfreak NB see if you can help this guy in this project!!
Navneet Suresh said:
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Click to expand...
Click to collapse
Have not worked with CAF kernel before. Moreover, the most important thing now is to get a stable working kernel for kitkat before embarking on anything else.
I will update my progress here in this thread. Its good to keep the communication open here so that others can also contribute/help. Right now, I can successfully compiled the zImage. Going to test it out later on.
update: notice that you have the 15.3.A.1.14 sources. Where did you get it from? My phone was running on this build before I flashed the AOSP 4.4 rom. Dont you have the CCI_KLOG compilation error on 15.3.A.1.14?
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
siankatabg said:
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Navneet Suresh said:
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
This is not an issue for me. What I would like to know is where did you get the A.1.14 sources from? Dont you have compilation errors from the sony sources
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Ghostfreak NB said:
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wonderful. Did you manage to compile from sony sources with the sa77_defconfig without any change?
I had to disable CCI_KLOG.
Ghostfreak NB said:
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont have the .14 sources. Its .12 that I am working on.
KillerKink said:
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
Click to expand...
Click to collapse
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
siankatabg said:
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
KillerKink said:
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
Click to expand...
Click to collapse
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
siankatabg said:
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the site. Yup, he did the pretty much the same as me.
Update: Kernel compiled via source is bootable.
KillerKink said:
Update: Kernel compiled via source is bootable.
Click to expand...
Click to collapse
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
The Dark Knight said:
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
Click to expand...
Click to collapse
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
KillerKink said:
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
Click to expand...
Click to collapse
I really can't believe my eyes.
You booted stock kernel on AOSP.
Hello everyone,
Today I hereby announce the initiation of The Flamingo OS project.
Anybody who wants to join this project can join. Following are the qualifications:
*Should have little knowledge of source building.
*Should be knowing about custom roms.
*Should have knowledge of linux commands(This is optional).
Purely CyanogenMod based rom.
Flamingo OS will be actually initiated in May.
Anybody who wants to join must qualify the above. Anyone who has good knowledge of developing websites and has money can also apply.
Hope you all join.
Sent from my GT-I9082 using Tapatalk Pro.
i can help for it
Ateekujjawal said:
Hello everyone,
Today I hereby announce the initiation of The Flamingo OS project.
Anybody who wants to join this project can join. Following are the qualifications:
*Should have little knowledge of source building.
*Should be knowing about custom roms.
*Should have knowledge of linux commands(This is optional).
Purely CyanogenMod based rom.
Flamingo OS will be actually initiated in May.
Anybody who wants to join must qualify the above. Anyone who has good knowledge of developing websites and has money can also apply.
Hope you all join.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
Do you have full sources ???
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
WalkerBales said:
Do you have full sources ???
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Click to expand...
Click to collapse
What do you mean. I am going to make it in may. Right now haven't yet started an organization on Github. But gonna make soon.
Sent from my GT-I9082 using Tapatalk Pro.
application to join ...
ported 5 roms ....
build a souce based rom...
know a liitle linux command and a bit of theming...
do i qualify..
Ateekujjawal said:
What do you mean. I am going to make it in may. Right now haven't yet started an organization on Github. But gonna make soon.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
I mean that do you have full MTK6577 sources ??
WalkerBales said:
I mean that do you have full MTK6577 sources ??
Click to expand...
Click to collapse
Nope. same bugs as cm11
Avenger4droid said:
application to join ...
ported 5 roms ....
build a souce based rom...
know a liitle linux command and a bit of theming...
do i qualify..
Click to expand...
Click to collapse
yup.
Ateekujjawal said:
Nope. same bugs as cm11
Click to expand...
Click to collapse
Which bugs are you talking about ???
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
WalkerBales said:
Which bugs are you talking about ???
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Click to expand...
Click to collapse
Bugs that will come out of cm11. I know, there will be many.
Sent from my GT-I9082 using Tapatalk Pro.
WalkerBales said:
I mean that do you have full MTK6577 sources ??
Click to expand...
Click to collapse
YEP HOPEFULLY ALL...CHECK THIS FOR FURTHER INFO...
http://forum.xda-developers.com/showthread.php?t=2678736
good news is i had found complete mtk sources and compiled rom out of it succesfully
and not so good news is
sources are of 4.1.2 and im new to this so i need developers help
Click to expand...
Click to collapse
always happy to help...
i know you have made latest cwm recovery for a116..
can also make it for a110 as we need upgradation to flash kitkat based roms..
also the recovery should have selinux..
Avenger4droid said:
YEP HOPEFULLY ALL...CHECK THIS FOR FURTHER INFO...
http://forum.xda-developers.com/showthread.php?t=2678736
always happy to help...
i know you have made latest cwm recovery for a116..
can also make it for a110 as we need upgradation to flash kitkat based roms..
also the recovery should have selinux..
Click to expand...
Click to collapse
We can make it ourselves, with selinux, but it requires work. Are you going to help @WalkerBales. Also we can flash it through bond bro's CTR recovery or by varunchitre15's twrp 2.5.0.0.
Sent from my GT-I9082 using Tapatalk Pro.
Ateekujjawal said:
Bugs that will come out of cm11. I know, there will be many.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
Oh yes you are right....
Ateekujjawal said:
We can make it ourselves, with selinux, but it requires work. Are you going to help @WalkerBales. Also we can flash it through bond bro's CTR recovery or by varunchitre15's twrp 2.5.0.0.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
I am having A116.... I don't have A110 !!
WalkerBales said:
Oh yes you are right....
I am having A116.... I don't have A110 !!
Click to expand...
Click to collapse
But at least you can help us.:good:
Ateekujjawal said:
But at least you can help us.:good:
Click to expand...
Click to collapse
OK I will.....
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Hi,
I have encountered an error when building slim for Xperia V(tsubasa)
http://pastebin.com/e2FYB6j8
Can anyone help me solve it? Thanks
Error ?
Just use google to find it or explain it better ^^
Send from my XZ With My Own Personal Modified MoonWalker SuperB !
Pandemic said:
Error ?
Just use google to find it or explain it better ^^
Send from my XZ With My Own Personal Modified MoonWalker SuperB !
Click to expand...
Click to collapse
I challenge you to Google the solution for me. This is because I have already looked through all the results on Google. If you do not know how to solve this I suggest you move aside.
Sent my Xperia P running CyanogenMod
Add android_hardware_qcom_media project to your local manifest
Garcia98 said:
Add android_hardware_qcom_media project to your local manifest
Click to expand...
Click to collapse
The funny thing is, I already have it in my manifest.xml and I also have the caf trees in my local_manifest.xml
Sent my Xperia P running CyanogenMod
I have solved the current error, but now I have another one :/
http://pastebin.com/hJHtv7UQ
Tried changing my qcom common tree to the one from slim but still same error. Also tried to include libril as prebuilt.
Sent my Xperia P running CyanogenMod
AndroidNoob69 said:
I have solved the current error, but now I have another one :/
http://pastebin.com/hJHtv7UQ
Tried changing my qcom common tree to the one from slim but still same error. Also tried to include libril as prebuilt.
Sent my Xperia P running CyanogenMod
Click to expand...
Click to collapse
What's your kernel source?
Garcia98 said:
What's your kernel source?
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_kernel_sony_msm8x60/tree/cm-11.0
Sent my Xperia P running CyanogenMod
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Disclaimer : I am not responsible for anything that happens to you or your device after flashing this mod. Though, nothing generally happens when you do it right. Make backup, always.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
Links removed
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Due to lack of my knowledge, I have dismissed this project.
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
TEST 1
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Click to expand...
Click to collapse
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
aweosomeabhijeet said:
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
Click to expand...
Click to collapse
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
I used sources and device tree from CM's repo
Doesn't matter, because I had removed assert from updater-script and no ROM flashing is required in here.
So all files must be good and compatible.
Hey, great job in compiling this. I want to try this out but what are the risks? Can I get hardbricked?
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
corphish said:
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
Click to expand...
Click to collapse
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
corphish said:
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
Click to expand...
Click to collapse
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
corphish said:
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
Click to expand...
Click to collapse
i did have a look at this recovery.img ... its definitly a TWRP build... but its damn wrong.... wrong qcom.fstab and recovery.fstab ... NO twrp.fstab ... healthhd seems to have wrong size (ok im not 100% with that but experience says it must be bigger) ... the Size of theme images is wrong.... AND the ramdisk size is totally above the size the kernel will load... thats why it leads to a "broken" recovery-load .... that will lead to a emergency load of kernel-inbuild recovery....
@ OP didnt you got make errors? after seeing this im sure you have build with -i -k
---------- Post added at 08:36 AM ---------- Previous post was at 08:22 AM ----------
ok without any kind of warranty that this will work... i have manipulated this recovery.img (NOT BUILD FROM SOURCE! MANUALLY REPAIR! ) ... maybe this works maybe not....
like you know my device is gone atm.... so maybe if my device is back i will have a deeper look into this...
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Click to expand...
Click to collapse
By making blind builds, you do "waste" the source code.
aweosomeabhijeet said:
I used sources and device tree from CM's repo
Click to expand...
Click to collapse
And you seriously expect a working build?
adil089 said:
Hey, great job in compiling this.
Click to expand...
Click to collapse
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for response thats exactly what i thought... He blind builded (see my comment above... Im not good in rom building but recoverys im good in... )
BTW maybe you let a word down on cm12.1 thread? Its a while ago now as varun said you will maintain our device... It would be nice to have a word from yourself about if its true or not
Sent from my Xperia T using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank You.
Please apply for closure of the thread
Sent from my HTC One
To everyone:
I am sorry for doing it all wrong and blindly. I just had ported to a similar device and had it working perfectly.
Never knew CM sources wouldn't work for XL. Basically I trusted on CM people for device tree and kernel, which I shouldn't have definitely.
If anyone feels to, can apply for closing down the thread. I have other devices, I'll try getting it to work on them.
Thank you
Sent from my HTC One
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Xperia_L said:
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry i am out of device... Maybe ask Olivier nice
Sent from my Xperia T using XDA Free mobile app
Thread closed upon request
Forum moderator,
matt4321