Database Info

Unified Github for Galaxy Y

Hello Everybody,
I am new to these forums but I have seen the efforts to port cm7, cm9, etc to our device.
The ports so far are great, but there are major bugs though, which cannot be fixed.
Compiling from source is the way forward for us.
A few days ago I tried a test build of cm9 but it would not boot.
The problem was because there is no device tree on github for our device.Something like "android_device_samsung_totoro". There are two or three but those are incomplete.
So....
GITHUB REPOS FOR GALAXY Y
http://github.com/GT-S5360
All devs are invited to create and collaborate.
This will create a central resource system forum which anyone can fork, clone, sync, and improve the sources.
Those who want to add a repo can email me at [email protected]
Now,
For development(compile, debug, etc) we need two things:
1. The android source (any flavor)
2. Device File Tree (eg. "android_device_samsung_totoro")
Two teams should be formed for these two tasks, and the second task must be completed fast. An ideal example of this would be here:
github.com/teamhacksung/android_device_samsung_cooper
complete with an extract-files.sh
This unified github will help us bring AOSP, AOKP, CM7, CM9 and whatnot to our galaxy y.
Please pm me if you are interested for development, and we could form a team and collaborate to speed up work, that is to say compiling.

Reserved
Reserved for future use

Ita really grear news...........for all dev
Sent from my GT-S6102 using xda premium

The link is down.

Andromeduh said:
The link is down.
Click to expand...
Click to collapse
It's not. It just links to github.com instead of github.com/GT-S5360

Ok I will tell mr.marroc to joining you
He already make cm7 for our device maybe he can help u sir
Sent from my GT-S5360 using xda premium

Need some help
Thanks, tell every dev you know. I need some help in doing this

Trying to port kernel 3.0 for i9003, please help

Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.

crackerizer said:
Hello,
I have been porting kernel 3.0 to i9003 since last month.
Now, platform specific codes and most of the drivers are ported.
Today, I am able to finish the kernel build with minor warnings.
but I have problems customizing the init scrits to be used with the kernel.
Any help from more experience devs would be appreciated
Current status:
- Platform specific code and all drivers except battery are ported.
- The kernel is built successfully
- trying to pack it into normalboot.img
I can release the source now due to its size. ( asking a guy at github to increase my storage space). But will do asap.
Sorry to post in the wrong forum but I dont have permission to post in the dev forum.
Click to expand...
Click to collapse
Thank u very much! You could contact dhiru
Sent from my GT-I9003 using XDA

Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.

vishal24387 said:
Great...but main question is that whether device boot or not??? Because many people have successfully compiled kernel 3.0 but device doesnt boot.
Click to expand...
Click to collapse
That what I'm going to find out. For now, I'm trying to modify the init script and looking for help from some devs here to speed it up.

my wish- that you release it as fast as you can

R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success

sachin sharma said:
R u using
This?
i have also used this guide n compiled a kernel 3.0 successfully packed it using dhiru's boot.img from alpha 6
i have also modified sum codes
but still no luck i think these files need alot of config changes!!!!
n lastly best of luck i hope u get success
Click to expand...
Click to collapse
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.

vishal24387 said:
I will suggest u to start ur thread in development thread. In general section developers mostly dont come here. Also u should upload ur source code to github. It will help to other developers to look into ur source code & find out the problem.
Click to expand...
Click to collapse
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium

ephraim033 said:
He needs to pump up his post count first buddy
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?

vishal24387 said:
oh...I forgot about that Anyway how many posts one has to do so that he can post a thread in development section?
Click to expand...
Click to collapse
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium

ephraim033 said:
Not sure, i think it's 10?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, 10!

crackerizer said:
sachin sharma, can you explain your procedure during your port? I'll compare with mine to see if we do the same thing.
After checking the boot script, I don't think we can just do a drop-in replacement. I think modifying the init script is needed (and i'm working on it). Also, There are some changes in the kernel which can cause problem with the ported code. I'm thinking about droping RFS and J4FS support in the new kernel (and probably abandon all samsung code).
Click to expand...
Click to collapse
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!

@crackeziner is your 3.0 kernel booting ?

anuraagkochar said:
@crackeziner is your 3.0 kernel booting ?
Click to expand...
Click to collapse
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
what can do now??

Skander1998 said:
Probably not.
Booting itself is the main problem .. lol.
All my attempts to port this failed miserably.
Click to expand...
Click to collapse
Just give it try. Don't let it down guys
Sent from my GT-I9003 using XDA

sachin sharma said:
all we need is config file in /arch/arm/config for kernel 3.0 for our devices
all we have now is config file for kernel 2.6.7 thats wats preventing our devices to boot
i followed same procedure mentiond in that blog after that i used zoom config file edit it at some places wer i thought shud be a change like device name to galaxy sl etc
renamed it latona_galaxy_sl
even then no benefit but i havn't givn hope m still trying!!!!
main problem is that we dont know how to configurate config file as "make config" command gives a hell lot of options!!!!
Click to expand...
Click to collapse
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
u mentiond that u r getting errors while compiling right?
that means ur deconfig file is still not correct
all the codes needs to be changed according to "kernel 3.0"
not by porting codes from other kernels or previous kernels
n lastly all drivers are already given in the source code thers nothing to change in it except that u just have to compile!!!!!!

crackerizer said:
I have gone far more than that . All latona specific codes are ported not only the defconfig file. Most drivers (LCD, power switch, camera, etc.) are also ported. I'm now modifying the init script to match what the kernel have now. Hopefully it will boot.
Click to expand...
Click to collapse
But did it boot?? Did u test that? When do u think u will be able to test that?

[SOURCE]Full AOSP tree + proprietary source

https://github.com/aquila-dev/mt6577_FULL_AOSP_SOURCE
Just.. enjoy
The device tree is on mediatek/config
The kernel is a 3.0.13 one
This is ICS 4.0.4 aosp
Use the makeMtk command to build an image
I didn't post it on "A110 Original Android Development" category because it's not an original source... it has been leaked from an other device "mytqu-832" codename baoxue.
I found it after many hours of searching in mediatek leaked documents on chinese website (i don't speak chinese [neither read]).. then i searched on github by taping the localpath of a mediatek specific config file.. and found that ! :3
And because all smartphones are now just SoC.. a lots of things (if not everything) found here should perfectly work on a110 and king.
[EDIT: March 2014]
Github restore my repo (so the first link works again) o/ I absolutly don't know why, but that's great !
If needed varunchitre15 forked it:
https://github.com/varunchitre15/mytqu-832
PREVIOUS EDIT:
The repo has been take down by a DMCA request..
And since the complete folder takes 8GB and my upload is at 60kB/s... this will take a long to reupload it.
I juste take the most interesting part (mediatek folder) which takes 800MB uncompressed, and it's already on mega:
https://mega.co.nz/#!BwZ1iT6B!JJp9Q2FCATKEaTWWWRI85RE-tJU_fp-S4XYXtHp5QVY
(use 7zip to extract it.. i think it should work)
The other parts (kernel/framework/prebuilt/external) will follow soon.. (3.2GB compressed to upload, will take something like 15hours to upload..)
PS: PLEASE !!!! if u're porting cyanogen and you already made significant work on the port.. (like a bootable build) Send me a message, i'm very busy, i can't work for it, but keep interrest for it. Please also don't send me private message like "how to compile the kernel.."

Well done, for finding this... will be helpful .. :thumbup:
Sent from my Cynus T2 using xda app-developers app

aquila-dev said:
https:// github.com /aquila-dev/mt6577_FULL_AOSP_SOURCE
Just.. enjoy
The device tree is on mediatek/config
The kernel is a 3.0.13 one
This is ICS 4.0.4 aosp
Use the makeMtk command to build an image
I didn't post it on "A110 Original Android Development" category because it's not an original source... it has been leaked from an other device "mytqu-832" codename baoxue.
I found it after many hours of searching in mediatek leaked documents on chinese website (i don't speak chinese [neither read]).. then i searched on github by taping the localpath of a mediatek specific config file.. and found that ! :3
And because all smartphones are now just a SoC.. a lots of things (if not everything) found here should perfectly work on a110 and king.
Click to expand...
Click to collapse
Well, is it the MTK's ALPS source??
I'm asking it bcoz only ALPS builds supports dual sims(i think).
Also baidu.com hosted several files on setting up the ALPS build environment......

You seem to be good in finding stuff
Will be useful in building CM9
See if you can find JB sources as well
Btw if you find kernel sources for MT6589, you can pm me
I am planning to buy the Micromax A116 but only if I get sources

aquila-dev said:
https:// github.com /aquila-dev/mt6577_FULL_AOSP_SOURCE
Just.. enjoy
The device tree is on mediatek/config
The kernel is a 3.0.13 one
This is ICS 4.0.4 aosp
Use the makeMtk command to build an image
I didn't post it on "A110 Original Android Development" category because it's not an original source... it has been leaked from an other device "mytqu-832" codename baoxue.
I found it after many hours of searching in mediatek leaked documents on chinese website (i don't speak chinese [neither read]).. then i searched on github by taping the localpath of a mediatek specific config file.. and found that ! :3
And because all smartphones are now just a SoC.. a lots of things (if not everything) found here should perfectly work on a110 and king.
Click to expand...
Click to collapse
GREAT !!!! :victory:

balamu96m said:
Well, is it the MTK's ALPS source??
I'm asking it bcoz only ALPS builds supports dual sims(i think).
Also baidu.com hosted several files on setting up the ALPS build environment......
Click to expand...
Click to collapse
Yes it supports the dual sim feature.
#
# MTK Build Info
#
MTK_BRANCH = ALPS.ICS2.MP
MTK_BUILD_VERNO = ALPS.ICS2.MP.V1.26
Click to expand...
Click to collapse

aquila-dev said:
Yes it supports the dual sim feature.
Click to expand...
Click to collapse
Awesome!

Bro can you start building cm9
aquila-dev said:
https://github.com/aquila-dev/mt6577_FULL_AOSP_SOURCE
Just.. enjoy
The device tree is on mediatek/config
The kernel is a 3.0.13 one
This is ICS 4.0.4 aosp
Use the makeMtk command to build an image
I didn't post it on "A110 Original Android Development" category because it's not an original source... it has been leaked from an other device "mytqu-832" codename baoxue.
I found it after many hours of searching in mediatek leaked documents on chinese website (i don't speak chinese [neither read]).. then i searched on github by taping the localpath of a mediatek specific config file.. and found that ! :3
And because all smartphones are now just SoC.. a lots of things (if not everything) found here should perfectly work on a110 and king.
Click to expand...
Click to collapse
With full source in hand, kindly start cm9 compiling process.....:silly:
btw, when i try to clone in windows they say source may be corrupted..any tip bro?:fingers-crossed:

nexi4droid said:
With full source in hand, kindly start cm9 compiling process.....:silly:
btw, when i try to clone in windows they say source may be corrupted..any tip bro?:fingers-crossed:
Click to expand...
Click to collapse
Why are you cloning it in windows bro?? We can't cross-compile Android in Windows environment....
Get a Linux distro and clone it there........
Anyway if you had completed cloning in windows, just copy the whole directory to your Linux......

can we expect cm 9 ???:silly:

Dj_cool said:
can we expect cm 9 ???:silly:
Click to expand...
Click to collapse
No it doesn't support dual sim
Sent from my HTC Explorer A310e using xda premium

DanceOff said:
No it doesn't support dual sim
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
I am sure most of us are willing to sacrifice dual sim support if we are on cm or ubuntu!
Sent from my Micromax A110

Dj_cool said:
can we expect cm 9 ???:silly:
Click to expand...
Click to collapse
See here....very interesting
http://www.jetdroid.org/shanzhai/2012/11/21/mt6577-kernel-source-released/
https://github.com/wiko-sources/cink-king
Hmm...the source releases seem to be growing now

pradipsoman said:
See here....very interesting
http://www.jetdroid.org/shanzhai/2012/11/21/mt6577-kernel-source-released/
https://github.com/wiko-sources/cink-king
Hmm...the source releases seem to be growing now
Click to expand...
Click to collapse
this is ics kernel sources ryt .?

mmxa110user said:
this is ics kernel sources ryt .?
Click to expand...
Click to collapse
Yes... right

DanceOff said:
No it doesn't support dual sim
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
Absolutly false.
Do you know what means override ?

How stupid am i ?
The device tree has been provided by wiko, i've cloned the source but i've didn't take a look to it..
https://github.com/aquila-dev/wiko_s9081_stock_kernel/tree/master/mediatek/config

aquila-dev said:
How stupid am i ?
The device tree has been provided by wiko, i've cloned the source but i've didn't take a look to it..
https://github.com/aquila-dev/wiko_s9081_stock_kernel/tree/master/mediatek/config
Click to expand...
Click to collapse
That means when they will release jb update they will provide jb aosp tree
Awesome
Btw any update abt jb release?

They just are waiting for google agreement..

@aquila-dev
we are also patiently waiting for the release of these kernel sources.
in order to fix some of the bugs with the cynus t2 rom on our phones, the a919.
specifically the accelerometer, gyroscope and the proximity sensors.
aquila, does the cynus t2 jb rom fully work on the cink king? without any sensor issues?

[Req][New MMX canvas2 rear cam issue]

Hi respected devs and users,
I hope there is a serious issue going around this forum,you guyz know that MMX is now selling canvas2 with jb out of the box.
You guyz @Dark4Droid @BOND1987 @sagarwep @andiroxu @bsuhas @mufti.arfan @bindassdost @khan_frd2002 @pratikmore @mmxandy @superdragonpt @varun.chitre15 and many more did a fantastic job by bringing the 4.2 to our device which was an almost impossible.
The issue is now the new canvas2 with 4.2 installed is not having a working rear cam.
As this is a forum for our beloved device we don't have a seperate section for the latest canvas2 variant,actually many users are suffering because of this and also many users will buy canvas2 in future.
I know that MMX don't care about even announcing the changes they made to the device as they always do,so as you devs are the only responsible for the miracle happened and happening to our device in this forum,so please kindly address this issue so that this forum may have many upcoming canvas2 supporters who buys the phone in future.
My kind request to users who have the canvas2 with rear cam not working to post a log cat while opening your camera in 4.2,so that it will be easy to find the actual issue.
You users can make this thread active by responding with proper log cats.its in your hands.
Thank you,
Showstopper1

Most probably it's an Kernel issue.
And the best guy for the Job is @varun.chitre15, he haves an deep know how, of your kernel/phone, and he is the Best guy in your community for fixing kernel issues.
However, if i was him, i would leave your community, as you have NO respect for him and his work.
Another guy, just tooked his patches from his ThunderZap kernel, and claim as it was ALL his work.
Even after his Kernel thread got closed, and all the Moderation warnings/edits you (the MMX community) are still distributing "his" Kernel on this foruns, and in your FB Group (yes i know, im part of your FB Group too...).
Where's the respect ?
B.Regards

my canvas 2 came with jb and rear camera not working... but i dont know how to get logcat

poran123 said:
my canvas 2 came with jb and rear camera not working... but i dont know how to get logcat
Click to expand...
Click to collapse
Google it.
Sent from my Micromax A110 using xda app-developers app

This is a kernel issue, or maybe .. if we get the new system modules from these "new" models, it may help in solving it , since I beleive that front cam is already working?

Please find the solutin we need must waiting for resolution.... of cam

mufti.arfan said:
This is a kernel issue, or maybe .. if we get the new system modules from these "new" models, it may help in solving it , since I beleive that front cam is already working?
Click to expand...
Click to collapse
Yes,Sir Only front cam is working on new canvas 2 with fixed 4.2 roms on new canvas 2
Let's see what will happen in future!!
Where can we get system modules,by unpacking kernel??

nightwalker said:
Yes,Sir Only front cam is working on new canvas 2 with fixed 4.2 roms on new canvas 2
Let's see what will happen in future!!
Where can we get system modules,by unpacking kernel??
Click to expand...
Click to collapse
No they are in /system/lib folder.
Sent from my Micromax A110 using xda app-developers app

mufti.arfan said:
No they are in /system/lib folder.
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
ok,so we need to use stock jelly bean rom or the device should have it preloaded with jb out of the box??

nightwalker said:
ok,so we need to use stock jelly bean rom or the device should have it preloaded with jb out of the box??
Click to expand...
Click to collapse
The pre loaded one, and it's kernel compilation time, if that will be different than our it means kernel is new. If it's same then we can try libs from it, if that doesn't work either then its a hardware thingy.
Sent from my Micromax A110 using xda app-developers app

superdragonpt said:
Most probably it's an Kernel issue.
And the best guy for the Job is @varun.chitre15, he haves an deep know how, of your kernel/phone, and he is the Best guy in your community for fixing kernel issues.
However, if i was him, i would leave your community, as you have NO respect for him and his work.
Another guy, just tooked his patches from his ThunderZap kernel, and claim as it was ALL his work.
Even after his Kernel thread got closed, and all the Moderation warnings/edits you (the MMX community) are still distributing "his" Kernel on this foruns, and in your FB Group (yes i know, im part of your FB Group too...).
Where's the respect ?
B.Regards
Click to expand...
Click to collapse
Dear @superdragonpt
Who are you to say such a things? Are you moderator or administrator of the thread/forum? Who gave you such a right to make decision who is wrong and who is right? If you and others have such a soft corner of the people here then why not solving their problem promptly and answer me or anyone by your work. You say I theft the patches from thunderzap then tell me if he has produced all the codes/patches by his own. Buddy I think you have no knowledge of kernel development and you are giving such a stupid comments here. All the patches are there on GitHub and kernel.org. Now not uploading kernel sources is my problem. Why I am not uploading is to me and not your pain to take.
Moreover people like you are not obeying forum rules and you are openly discussing the out the thread discussions openly rather then sending a PM. It's you who started and that's why I am writing here otherwise I too like to PM the things first. So stop this nonsense wise-man.

andiroxu said:
Dear @superdragonpt
(...). Now not uploading kernel sources is my problem. Why I am not uploading is to me and not your pain to take.(...)
Click to expand...
Click to collapse
^^ Yeah buddy.
Keep it going, fooling everybody
/ offtopic

superdragonpt said:
^^ Yeah buddy.
Keep it going, fooling everybody
/ offtopic
Click to expand...
Click to collapse
If you think that my no source is making you fool then it's to you.
Everybody is fair handsome here and know everything.
Sent from my GT-I9500 using xda app-developers app

New mmx have slight hardware change i guess or the kernel issue some one needs to share their device(or system libs) here so that devs can make a change

andiroxu said:
Dear @superdragonpt
Who are you to say such a things? Are you moderator or administrator of the thread/forum? Who gave you such a right to make decision who is wrong and who is right? If you and others have such a soft corner of the people here then why not solving their problem promptly and answer me or anyone by your work. You say I theft the patches from thunderzap then tell me if he has produced all the codes/patches by his own. Buddy I think you have no knowledge of kernel development and you are giving such a stupid comments here. All the patches are there on GitHub and kernel.org. Now not uploading kernel sources is my problem. Why I am not uploading is to me and not your pain to take.
Moreover people like you are not obeying forum rules and you are openly discussing the out the thread discussions openly rather then sending a PM. It's you who started and that's why I am writing here otherwise I too like to PM the things first. So stop this nonsense wise-man.
Click to expand...
Click to collapse
Some people feel themselves as moderators here buddy!! As a member of A110 community you should be aware of this !!!

superdragonpt said:
^^ Yeah buddy.
Keep it going, fooling everybody
/ offtopic
Click to expand...
Click to collapse
Yes you are right. I need specs and made for camera in new models because without that no one can help or need sources which are not released by MMX yet.
Anyone kindly give the manufacturer name of camera. It can be known by using Andromizer app on xda or any app from play store which gives full hardware information.
Sent from my GT-I9500 using xda app-developers app

@superdragonpt & @andiroxu Stop it friends....Dont fight... Just understand we are fighting for Cheap[i didnt mean price] device.... Human relations is far better than Device Relations... I know i got plenty of friends because of MMX C2.... But Why fight for it? I agree both Varun and andiroxu have their own capablities,better leave them alone...
And @superdragonpt : Any Add-ons for 4.2 ? :laugh: More ROM's are on NR... I am using Xperia Messaging app on 4.2 :angel:

andiroxu said:
Yes you are right. I need specs and made for camera in new models because without that no one can help or need sources which are not released by MMX yet.
Anyone kindly give the manufacturer name of camera. It can be known by using Andromizer app on xda or any app from play store which gives full hardware information.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
bro i have install the app but i didnt find any information about camera.... m using miui rom 4.1.2 and i dont have the backup of the original JB rom which came along with my phone

andiroxu said:
Dear @superdragonpt
Who are you to say such a things? Are you moderator or administrator of the thread/forum? Who gave you such a right to make decision who is wrong and who is right? If you and others have such a soft corner of the people here then why not solving their problem promptly and answer me or anyone by your work. You say I theft the patches from thunderzap then tell me if he has produced all the codes/patches by his own. Buddy I think you have no knowledge of kernel development and you are giving such a stupid comments here. All the patches are there on GitHub and kernel.org. Now not uploading kernel sources is my problem. Why I am not uploading is to me and not your pain to take.
Moreover people like you are not obeying forum rules and you are openly discussing the out the thread discussions openly rather then sending a PM. It's you who started and that's why I am writing here otherwise I too like to PM the things first. So stop this nonsense wise-man.
Click to expand...
Click to collapse
Derp, so you mean to say that the patches I merged have got no contribution of mine?
Certainly they were taken from mainline but from what you posted I can surely tell that the 3.4.69 upgrade you claim to is nothing other than a gimmick which just involves only bumping the makefile version staging just as doing the very famous fake build.prop Android version trick. I hope you don't come out with a Linux Kernel 4.0 from your closed shell someday. If you have really upgraded it to mainstream, then prove it. You made this comment because you never really upgraded your kernel because if you did, you would have known what conflict resolution is and how much efforts it involves. Wait I will step down one level for you. So you have got problem for uploading your sources no? Come on then show me output of
Code:
git rev-list HEAD --count
using screen capture. I have no business with whether you upgraded your kernel or not but I am really interested to see that screenshot.
2. Now regarding stealing my work, yes you did that. Because usage of someone's work which plays an important role, without their permission is defined as stealing. And you know very well that the Mediatek vermagic hack which force loads all modules, the authorization of which I keep with me, is what you have merged without prior intimation to me or any acknowledgement. Now don't make me to reveal everything in public.
And why not discuss this in public? So people won't know about your deeds?
I really need to see your sources now because I have understood what kind of game you are playing, I am not sure what all stuff you took from ThunderZap because even undervolting commit belongs to me.
P.S: Users should really stay away from this because this matter is not as simple as it appears. There is a lot you all don't know about this which happened under the hood.
Edit: I really don't understand in what sense comment of @superdragonpt sounds like a moderator?

mayur.3.92 said:
Some people feel themselves as moderators here buddy!!!
Click to expand...
Click to collapse
Buddy, let me tell you this:
Im not an MOD, but i can't stand people that STEALS, other's work, And what's worse is that he is CLAIMING it is his work.
You don't understand what we are talking about, and that's normal, the "normal" xda user don't understand this things, but believe me i know.
The normal xda user, just want RESULTS, and don't care about GPL and credits, and dont even imagine HOW MUCH WORK was involved.
The normal xda user, just come here, download and thats it!
@andiroxu Yes you have stolen varun's work. and you should be an shame of yourself.
Come on prove that im wrong, and upload your kernel sources...
But PLEASE don't repeat tha same trick you've done in your kernel thread when you uploaded FAKE sources.
I didnt wanted to come in public with this statments, i dont even own an micromax phone (my phone is an ZTE), but if there is something that gets on my nerves is this things.
I have an DEEPLY RESPECT with all the work that @varun.chitre15 have done, just like every other dev.
These devs are the reason we have custom roms and kernels, as an alternative to our stock ones.
varun.chitre15 said:
Derp, so you mean to say that the patches I merged have got no contribution of mine?
Certainly they were taken from mainline but from what you posted I can surely tell that the 3.4.69 upgrade you claim to is nothing other than a gimmick which just involves only bumping the makefile version staging just as doing the very famous fake build.prop Android version trick. I hope you don't come out with a Linux Kernel 4.0 from your closed shell someday. If you have really upgraded it to mainstream, then prove it. You made this comment because you never really upgraded your kernel because if you did, you would have known what conflict resolution is and how much efforts it involves. Wait I will step down one level for you. So you have got problem for uploading your sources no? Come on then show me output of
Code:
git rev-list HEAD --count
using screen capture. I have no business with whether you upgraded your kernel or not but I am really interested to see that screenshot.
2. Now regarding stealing my work, yes you did that. Because usage of someone's work which plays an important role, without their permission is defined as stealing. And you know very well that the Mediatek vermagic hack which force loads all modules, the authorization of which I keep with me, is what you have merged without prior intimation to me or any acknowledgement. Now don't make me to reveal everything in public.
And why not discuss this in public? So people won't know about your deeds?
I really need to see your sources now because I have understood what kind of game you are playing, I am not sure what all stuff you took from ThunderZap because even undervolting commit belongs to me.
P.S: Users should really stay away from this because this matter is not as simple as it appears. There is a lot you all don't know about this which happened under the hood.
Click to expand...
Click to collapse
^^ THIS.

Device tree, vendor files.

Hi, I'm currently trying to build AOSP for our device from source however I cannot figure out how to add device support, I've followed so many guides on editing the local_manifests.XML but I can't seem to get it to work.
Can any of our devs explain to me how to build AOSP with the addition of our device support? I'm not entirely worried about kernel ATM as our source was released so I will build that.
I just can't for the life of me add device support properly.. Could anyone link me to a guide or some other stuff to read? Google is very unhelpful when googling Linux related issues.
Edit - to clear up any confusion bottom line as of right now I basically need to know how to implement the device tree we already do have (several github links, mainly cm based) into my AOSP source.
Would I just technically copy the files into Google's already created device/vendor/ folders?
https://source.android.com/source/add-device.html using this link as reference. May be very bland.

christopherrrg said:
Hi, I'm currently trying to build AOSP for our device from source however I cannot figure out how to add device support, I've followed so many guides on editing the local_manifests.XML but I can't seem to get it to work.
Can any of our devs explain to me how to build AOSP with the addition of our device support? I'm not entirely worried about kernel ATM as our source was released so I will build that.
I just can't for the life of me add device support properly.. Could anyone link me to a guide or some other stuff to read? Google is very unhelpful when googling Linux related issues.
Edit - to clear up any confusion bottom line as of right now I basically need to know how to implement the device tree we already do have (several github links, mainly cm based) into my AOSP source.
Would I just technically copy the files into Google's already created device/vendor/ folders?
https://source.android.com/source/add-device.html using this link as reference. May be very bland.
Click to expand...
Click to collapse
Try building CyanogenMod instead. They have device specific instructions!
Sent from my MotoG3 using Tapatalk

am2012 said:
Try building CyanogenMod instead. They have device specific instructions!
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ya you can dl the source for both the device and vendor ........copy them over to the source and you shouldn't have a problem

am2012 said:
Try building CyanogenMod instead. They have device specific instructions!
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
he's trying to build aosp.. why would he build cyanogenmod?

HelpMeruth said:
he's trying to build aosp.. why would he build cyanogenmod?
Click to expand...
Click to collapse
Fair enough. I imagine as he posted this 6 months ago, he has been successful in his attempts!