Related
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Maybe because there are too many new phones in this interval of time and our s3 mini is not the most popular
Sent from my Motorola Startac
joshtk98 said:
this phone we own has been around for around 6 months now, when i had a galaxy mini (not s3 mini, just galaxy mini) there were so many customization's ROMS in six months, but for our superior phone we have barely anything, i do appreciate everyones effort but there must be more customization's ROMS like AOSP ROMS. :crying:
Click to expand...
Click to collapse
The main problem seems to be that the ST-Ericsson Novathor sources are not available.
I think that devs are focusing on more powerful devices like the s3 or s4, bigger guns are always better, aren't they?
Sent from my GT-I8190 using xda app-developers app
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
vtetuan said:
Take a look in dev section. mostly threads ends with a "this is my code / customization!" war.
There aren't community around this device.
Click to expand...
Click to collapse
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42730302&postcount=25
The guy only wants to learn. And I'm not saying that you have no reason.
It's the classical fragmentation in Linux community, and now, in Android community.
New Macław said:
Last war was with me and Oliver, now we're working together in peace. I missed something?
But biggest problem is in no ste sources.
Click to expand...
Click to collapse
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Scuppa said:
How about this?
http://forum.xda-developers.com/showthread.php?t=2327646
Click to expand...
Click to collapse
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
New Macław said:
Really chaotic commits. But we've almost ready CM10.1 sources, so don't worry
Click to expand...
Click to collapse
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Paul L. said:
We have chaotic commits because we have a Jenkins server that requires sources to be uploaded to github and then synced by the server. We're not testing locally
The important ones you may encounter useful are in libhardware, libhardware_legacy, frameworks_av and frameworks_native, we're trying to use code from jellybean STE_AUDIO and adapt them to cm-10.1 (we're NOT coders so we did our best). Also, we build for two devices now, so we need to adapt the code to be common in some parts.
We can collaborate, maybe you could help us, and we can (if my teammates agree) get you some power (the jenkins) to build and upload automatically
Click to expand...
Click to collapse
I don't need access to your machine, I would like to keep releases on my own hand, but of course I can help you
Poke me at gtalk please: [email protected]
Guys any word on aosp for our device..?..dying to try one..come on give me some info or i will need to learn java..lol...
Prm593 said:
Guys any word on aosp for our device..?..dying to try one..come on give me some info or i will need to learn java..lol...
Click to expand...
Click to collapse
It was on forum many times, use search
Few users on this forum just start working on AOSP and i think CM, but it's just begining...
cheers
Mayex said:
It was on forum many times, use search
Few users on this forum just start working on AOSP and i think CM, but it's just begining...
cheers
Click to expand...
Click to collapse
sorry..but thnks
Prm593 said:
sorry..but thnks
Click to expand...
Click to collapse
Its not about only JAVA here you see. Building for a completely new device needs much more. If you are really keen to learn, then go ahead and pick up a book on Embedded Linux so that you can learn how a device tree is created, how it has to be edited and what sources are necessary to pull it off!
Cheers!
sarkar1990 said:
Its not about only JAVA here you see. Building for a completely new device needs much more. If you are really keen to learn, then go ahead and pick up a book on Embedded Linux so that you can learn how a device tree is created, how it has to be edited and what sources are necessary to pull it off!
Cheers!
Click to expand...
Click to collapse
ok bro thnks...but any luck with the aosp.?
I have idea. :silly:
We can post here any progress in building AOSP.
Could anyone who knows something post here that how looks work on AOSP? Any progress?
Calm down, guys. Don't get hyperexcited.
Developing a device tree is a hard and long process, as most of the things don't work and need proprietary files.
Give us some time. I'm sure that in the near future the development section will be full of ROMs
Sent from my C5303 using XDA Premium 4 mobile app
eagleeyetom said:
Calm down, guys. Don't get hyperexcited.
Developing a device tree is a hard and long process, as most of the things don't work and need proprietary files.
Give us some time. I'm sure that in the near future the development section will be full of ROMs
Sent from my C5303 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I couldn't say this better myself. First we need something that will boot atleast! Only then can the actual debugging start.
EagleEye, are you developing anything yet?
Cheers
sarkar1990 said:
I couldn't say this better myself. First we need something that will boot atleast! Only then can the actual debugging start.
EagleEye, are you developing anything yet?
Cheers
Click to expand...
Click to collapse
My thesis at the moment. I have a deadline on Wednesday.
I need to wait for my ISP to sort my connection out (probably tomorrow), set up a Linux on my ultra fast Pentium 4 beast :silly: (build server saves my ass) and I will start working on CM.
I'll create an IRC channel, so interested people can help me out.
Stay tuned
eagleeyetom said:
My thesis at the moment. I have a deadline on Wednesday.
I need to wait for my ISP to sort my connection out (probably tomorrow), set up a Linux on my ultra fast Pentium 4 beast :silly: (build server saves my ass) and I will start working on CM.
I'll create an IRC channel, so interested people can help me out.
Stay tuned
Click to expand...
Click to collapse
Awesome man! Send me the link to the channel... Build server :good:
Sent from my C5302 using Tapatalk 4
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
peters. said:
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
Click to expand...
Click to collapse
some hope's have come up..
cheer's guys
peters. said:
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
Click to expand...
Click to collapse
All kernels have proprietary drivers, every single vendor does it because the companies that manufacture CPU/GPU/wifi/nfc/telephony/bluetooth/etc chips don't want to release every bit of source code, so they release sources that should make the chip work easily on different builds of android, keeping a lot of code on precompiled binary files
Check the sony developer portal, they released the open-source pack for our devices...
As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Gokulbalram said:
As the title says, it'd be great if there was an updated list with the supported device which will be recieving 'L' from Omni.
Click to expand...
Click to collapse
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
iKillCypher said:
I have still yet use oppo device but from what I have seen so far it is a pretty much quite a kickass device as for sony I main yuga from time to time as this is the only device I got and we all know what happened back in the days of exynos4
Click to expand...
Click to collapse
What do you guys hate Exynos for? Kernel Sources?
Gokulbalram said:
What do you guys hate Exynos for? Kernel Sources?
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
chasmodo said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Click to expand...
Click to collapse
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Gokulbalram said:
Oh wow, even MediaTek is getting better. Meanwhile, this Bull****.
So @Entropy512, I read all the 100 posts, and I finally understand you.
Click to expand...
Click to collapse
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Entropy512 said:
As bad as Exynos is... MTK manages to actually be significantly worse.
Even if you have complete access to all of the source they give to an OEM (let's just say I've seen a complete leak for one MT6589 device), it's still a blob-ridden disorganized mess.
Click to expand...
Click to collapse
There's only one source for a MediaTek chipset, the one in Android One. At least MediaTek is getting better, they're taking steps.
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Entropy512 said:
There won't be, since L is not out and we have no idea what changes it is going to entail from a device support perspective.
As far as devices that are likely to receive "focus" from the team - Oppos and the Sony Xperia Z family. (Probably Z1/ZU also) - Because of how well Oppo and Sony have treated the open source community, in general, team members are more motivated to grab "older" devices they don't use any more in order to work on them.
However here's a list of devices that are likely to be dropped:
All Exynos 4210 devices (i777/n7000/i9100) - No active maintainers remain for these devices, they've been on minimal life support for two years now since Exynos-gate and the Superbrick fiasco of 2012.
I9300 - No active maintainer
Unknowns:
N80xx - Of 3 maintainers, the only one who remains is Humberto and he's kinda spread thin. So highly likely to get removed.
maguro - This didn't have an active maintainer for ages, but I think one did step up. I need to talk with the team.
Honestly, I'd love to just kill Exynos4 with fire with L and be done with that goddamned hell platform once and for all... But that is only my personal opinion.
Click to expand...
Click to collapse
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
ahmedelhofy said:
S2/S3/Note take a huge percentage in the download counts of any custom ROMs
it's a bad platform... But there is still lots of users using them regularly... Hopefully you guys can give us some L builds... I won't be that sad if you stopped since I know how hard it's to still even offer us some builds for KitKat...
Thanks..
Click to expand...
Click to collapse
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Gokulbalram said:
https://plus.google.com/u/0/+AndrewDodd/posts/cdPnNjLAb4F
Even I own an S3, but after reading this, I really wouldnt be pissed to see it being dropped
Click to expand...
Click to collapse
Yea, I know I already said that I won't be sad to see it getting dropped..
Last week, jakew02 said that he's going to drop support for Galaxy S4 LTE (jflte) when Lollipop arrived. He's leaving the source up, but OmniROM Lollipop on the S4 will need a new maintainer.
The key message here is that the core team can't maintain every device!
As much as we hate to remove devices, there will be a significant number removed, if there's no active maintainer for it. No device will be enabled for L nightlies (and thus official support) if there's nobody active and competent who is maintaining it.
If you've always wanted to get involved, now really is the time - L is upon us, and good things are happening
Going forward, if there is sufficient interest from the community (i.e. go out there and talk to devs and contributors from other projects please!), we are more than happy to facilitate making the 4.4 branch of Omni an ongoing project.
For this to work though, it would require enough developers to come together on legacy devices to make it viable. With new major Android versions, a lot of custom ROMs simply don't continue support for devices "left behind", but we're willing to try this out as an experiment. If there are sufficient (experienced) developers, we'll have 4.4 as an active project which will accept features and patches as normal.
For this to work though, it does require everyone to play their part - we'll need reliable people to review and approve changes etc, as well as active maintainers for devices.
aidfarh said:
Hi OmniROM devs,
While waiting for Lollipop to arrive, can you please get around to updating the yuga kernel and blobs? There's no point of Sony going to the trouble of publishing the up-to-date kernel sources if the roms are not going to take advantage of it.
Click to expand...
Click to collapse
Hi,
that's not really necessary if you ask me. We could always bring the kernel in sync with CAF, but that's it. This is also what OEMs do when updating their kernels (apart from fixes and such). Jerpelea, a Sony Mobile developer, agrees (see this post).
Also there aren't many "active" Xperia fusion3 (Z, ZL, Tablet Z) maintainers at the moment , and I haven't had enough time for such things.
BUT: Contributions are always welcome.
Help
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Hunter1998 said:
I don't know much of anything about developing but am fairly competent and comfortable with flashing ROM's and kernels. I own an N5, and would be willing to help however possible.
Click to expand...
Click to collapse
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
I became one overnight ._. (Nowhere near a skilled maintainer though.) I only know how to compile. Nothing other than that :/
lg e450
sorry if this the wrong thread to post.
I have an old lg e450(mtk 6575), and all the sources has been released by lg. Can anything be done to make this device alive?
Entropy512 said:
In that case - file bugreports in JIRA, since your device does have a maintainer. One does not gain the skills to be a maintainer overnight. Most people I know, including myself were "co-maintainers" (assisting with bringup but not solo) on devices for a year or more before their first time "flying solo".
Click to expand...
Click to collapse
Who do I need to contact to help?
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Wrong place bro
You can get help from @s.sawrav and @pirej,these are sort of devs who could help you.
Btw if you can,please try to compile also nougat if you can.
And use Google for things you want to learn like oc,governors and stuff there are some pretty good threads here on XDA on how to build kernels and add features to it like this here http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276 .
Wish you best luck?
Great, one more Dev for our little beast. Try Paranoid next ...
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
wow great!!!! i have some request. please build cm11. i know is oldschool, but its pretty light and stable for me
Keep up mates,... You are awesome!!
Great Work Bro
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819).....
Well down bro... Great to go.. There are developers here who may help you to grow. I wish you all developers good luck and hearty THANKS for all your works here..
Thanks & Regards,
Ashok M
Click to expand...
Click to collapse
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
Good job :good: but this is not the right section to post this,ask a moderator to move this thread to appropriate section,also checkout the chef central in android section of XDA and then there's google,it'll help you out a lot.
Thread belongs in Discussing forum not Development, moved as requested by OP
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
Just start from doing the green thing
That's the best way to learn, and when/if you are happy with the modifications you made, and you think that the rom you made is different enough to be posted as a different/new/your rom, then post it.
pirej said:
Just start from doing the green thing
That's the best way to learn, and when/if you are happy with the modifications you made, and you think that the rom you made is different enough to be posted as a different/new/your rom, then post it.
Click to expand...
Click to collapse
I'm not familiar with the meaning of "the green thing", I love plants, so it would be great it is a plant-related saying. Care to elaborate a little? At the moment I am learning some useful repo parameters and attempting to build Resurrection Remix which seems going just OK.
I am downloading too all the source code from CM11, I think that's gonna be doable for a newbie like me, AOSPA is just too much right now, so I gave up with that for now, even documentation is hard to get.
CENTSOARER said:
I'm not familiar with the meaning of "the green thing", I love plants, so it would be great it is a plant-related saying. Care to elaborate a little? At the moment I am learning some useful repo parameters and attempting to build Resurrection Remix which seems going just OK.
I am downloading too all the source code from CM11, I think that's gonna be doable for a newbie like me, AOSPA is just too much right now, so I gave up with that for now, even documentation is hard to get.
Click to expand...
Click to collapse
in my quote of your post... i used GREEN color to mark something..
pirej said:
in my quote of your post... i used GREEN color to mark something..
Click to expand...
Click to collapse
Oh, I see now, thanks for the advice. This XDA Forums app can't parse color tags, so I was lost.
Hey I Was hoping you could build and Maintain a stable Cyanogen 12.1! A lot of people are still using 12.1 and kumajaya has stopped active development on that ROM. Plus the Sailfish OS community would really benefit from your support
Hi guys,
Seems Samsung has released the opensource codes for galaxy a70 (sm-705gm) in Samsung open release center. Link given below.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=705gm
If can be used to build custom roms and twrp, please go ahead.
senseijtitus said:
Hi guys,
Seems Samsung has released the opensource codes for galaxy a70 (sm-705gm) in Samsung open release center. Link given below.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=705gm
If can be used to build custom roms and twrp, please go ahead.
Click to expand...
Click to collapse
If you are not getting the file using the link, go to http://opensource.samsung.com & search with 705gm. You will get the file.
Does Not Matter If...
senseijtitus said:
Hi guys,
Seems Samsung has released the opensource codes for galaxy a70 (sm-705gm) in Samsung open release center. Link given below.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=705gm
If can be used to build custom roms and twrp, please go ahead.
Click to expand...
Click to collapse
Yes But...
Are any Developer's even buying this device?
That's The Million Dollar Queston..
Waiting To See What Happens..
I am interested in this device, but waiting to see how many dev's start working on it?
I think, All a70 users together, should request, some dev(s) to work on this device.
united we stand!
what you all say?
rrd84 said:
I am interested in this device, but waiting to see how many dev's start working on it?
I think, All a70 users together, should request, some dev(s) to work on this device.
united we stand!
what you all say?
Click to expand...
Click to collapse
This was the situation with Lenovo p2. But dev's eventually got in and now they have a great development curve.... the p2 users donated money for one dev to buy p2 for development and well. That was initiated by a user. And development kickstarted soon after.
senseijtitus said:
This was the situation with Lenovo p2. But dev's eventually got in and now they have a great development curve.... the p2 users donated money for one dev to buy p2 for development and well. That was initiated by a user. And development kickstarted soon after.
Click to expand...
Click to collapse
I'm in
I'm in but how we do that?
alsartawi said:
I'm in but how we do that?
Click to expand...
Click to collapse
You mean donate or development?
senseijtitus said:
You mean donate or development?
Click to expand...
Click to collapse
donation, but also how we can contact a developer for kernels and custom roms, i really want to see all s10 features on this device, also missing features like original samsung vibrate on touch for navbar and samsung keyboard.
alsartawi said:
donation, but also how we can contact a developer for kernels and custom roms, i really want to see all s10 features on this device, also missing features like original samsung vibrate on touch for navbar and samsung keyboard.
Click to expand...
Click to collapse
We can check in custom rom telegram groups for this. But also check with certified developers in xda as well. PM would do here.
senseijtitus said:
We can check in custom rom telegram groups for this. But also check with certified developers in xda as well. PM would do here.
Click to expand...
Click to collapse
But first, we need to organize users who would be able and willing to donate. Once enough people are there and we can figure out on total if the amount offered is sufficient enough, we can start contacting dev's. After we have a dev ready to help, then start pooling in money and purchase the set and send ot to the dev.
senseijtitus said:
But first, we need to organize users who would be able and willing to donate. Once enough people are there and we can figure out on total if the amount offered is sufficient enough, we can start contacting dev's. After we have a dev ready to help, then start pooling in money and purchase the set and send ot to the dev.
Click to expand...
Click to collapse
just a heads up. according to XDA rules. donation threads have to be created by the developer itself who is interested in the device development. he has to green lit such a thread with an XDA admin. if it gets created by forum users it gets closed pretty soon as it is against the rules.
so first step would be finding an recognized developer willing to spend his free time on the device.
celoxocis said:
just a heads up. according to XDA rules. donation threads have to be created by the developer itself who is interested in the device development. he has to green lit such a thread with an XDA admin. if it gets created by forum users it gets closed pretty soon as it is against the rules.
so first step would be finding an recognized developer willing to spend his free time on the device.
Click to expand...
Click to collapse
Agreed. But who can help with this...
senseijtitus said:
Agreed. But who can help with this...
Click to expand...
Click to collapse
two options comes to mind.
A: look into devs that were or still are maintaining Samsung (Snapdragon based) phones and might be interested in the A70.
B: look into devs that maintain a device that has the same SoC (or SoC family) as those devs will have less than half as much work (it does depend on how far the kernel deviated from code aurora code) to maintain a second device if they have already established the knowledge on the primary device.
E.T.A. Unknown..
celoxocis said:
look into devs that were or still are maintaining Samsung (Snapdragon based) phones and might be interested in the A70.
Click to expand...
Click to collapse
The Operative Phrase Here Is: "Still Maintaining Samsung (Snapdragon Based) Phones".
In the U.S... Samsung Snapdragon devices have their bootloaders locked down.. ( Per Carrier's Request ) so you have Zero ROM Development..
IMO.. you have to love this device for what it brings to the table stock ( Widvine L1, Themes, AR Emoji, UI, Gaming etc ) just in case nothing Custom sprouts.. :angel:
RaiderWill said:
The Operative Phrase Here Is: "Still Maintaining Samsung (Snapdragon Based) Phones".
In the U.S... Samsung Snapdragon devices have their bootloaders locked down.. ( Per Carrier's Request ) so you have Zero ROM Development..
IMO.. you have to love this device for what it brings to the table stock ( Widvine L1, Themes, AR Emoji, UI, Gaming etc ) just in case nothing Custom sprouts.. :angel:
Click to expand...
Click to collapse
And Samsung pay
Yeah Buddy..
devilhunter47 said:
And Samsung pay
Click to expand...
Click to collapse
I Stand Corrected Sir..
That's the most important of all !
Now.. How Could I Forget That...
https://yadi.sk/d/hABqno4EmUj4Wgwhat news about twrp?I have not loaded,where the committed mistake.if who is engaged in creation of twrp I can provide the map of blocks and other information
naruba said:
https://yadi.sk/d/hABqno4EmUj4Wgwhat news about twrp?I have not loaded,where the committed mistake.if who is engaged in creation of twrp I can provide the map of blocks and other information
Click to expand...
Click to collapse
I am trying to make twrp for the device. Because this is my first time, I need device tree to be prepared. As of now, my attempts have not given any results. If you can help, would be great.
block map