{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all, i have to say that CyanogenMod Team, OmniRom team or other team don't want to build a distribution of Android L for Samsung Galaxy S2 because it's too older and came with Android 2.3.6 (All those Teams said that don't want to port Android L to devices which came with Android Gindgerbread or lower).
OmniRom on twitters said:
yousif monther on 8 nov
at omni_rom will you support the s2 i9100 ?
OmniROM on 8 nov
at yousif monther Most likely not - see the XDA post. We badly need more device maintainers and developers. i9100 will need loads of work!
Source: OmniRom on Twitter: Whee! First OmniROM 5.0 build just booted on the flo (N7 2013). Developers, get involved!
I also read that there is a Build of AOSP 5.0 made by NovaFusion team for Samsung Galaxy S3 Mini ... but we can't use this Rom as a point of reference because of his different processor... Samsung Galaxy S2 has Exynos 4210.
Older device wich has get Android L:
Samsung Galaxy S3 Mini: [ROM][5.0.0]Android Open Source Project 5.0 20141106
Samsung Galaxy S3 (Not too old, but it's old ): [WIP] Android 5.0 Lollipop for Galaxy S3 (GT-I9300)
T-Mobile Samsung Galaxy S II SGH-T989 (skyrocket): [ROM][5.0.0] AOSP Lollipop Early Preview [November 7, 2014]
But all these distributions can't help us!
So, What we can do is to wait for stable source codes of:
OmniRom
CyanogenMod
ParanoidAndroid
or other major custom distribution
Let's try together or just Discuss It!
Sorry for my bad English!
Rofl....chill bro, 5.0 just came out... have some patience. When some similar devices have a good build ( stable ) , then we can start to port/compile it from sources...till then, have patience.
dodgedroid said:
Rofl....chill bro, 5.0 just came out... have some patience. When some similar devices have a good build ( stable ) , then we can start to port/compile it from sources...till then, have patience.
Click to expand...
Click to collapse
Yah, i know. I wanna help devs on this build , so i'm trying to figure out how can i port a kernel for our device!
A Word To The Inexperienced Users (I am primarily included)
Buddy, what part of "error 404: I9100 developers not found" part don't you get? I too eagerly want to get that Android Lollipop sensation on my old i9100 (two and a half years old now), but I have no knowledge in the real development, yes you read write, R E A L. You think building ROMs is development? Want me to teach you how to set up Ubuntu, download sources, and build ROMs? But does it make any of us "developers"?
Back to the real talk. So you want Android Lollipop 5.0, hell, we all want it. Seeing all those "Android 5.0 ported to blah blah" made you drool all over the screen, and gave you some hope, no? Buddy, what you are seeing are AOSP ports, that's Android Open Source Project, you read that? O P E N S O U R C E... But wait a minute, Exynos is a closed-source bastard, so why shake a leg if it ain't going to be stable, or even "bootable"? Do you think it's that easy? Just create a thread on the legendary i9100 forums and boom, hook up the devs like fish. No... And even if a developer seen your thread, they probably no longer own the device, or remembered the pain and agony of maintaining for the i9100. Do you think CyanogenMod developers ported KitKat to our device? We go ahead and talk all proud claiming "the developers" are supporting our device. HELL NO, it's amazing people who don't belong to anyone that get encouraged to do the work, people that break the limits ridiculous OEMs put to kill a device. Wanna know how KitKat and CyanogenMod 11 came to our device? You guessed it, "the developers" didn't do hell. CyanogenMod did it? They're busy cleaning their crap now that they've gone corporate, they are useless if it weren't for the maintainers of devices, people that break the locks and rule their phones, CyanogenMod just claims they're "the developers" but they can kiss my ass. @Wayland_ACE, if you are reading this, sir, I thank you for your amazing contribution, the days and hours you've put into bringing Android 4.4 to our device, the amazing builds of the first and early KitKat builds, builds that I still keep to this day. @milaq, when CyanogenMod's Jenkins eats the dirt, you were there providing us with nightlies that proved to be stable, preparing that device tree, and bringing CyanogenMod 11 to what it is today. Thank these two for KitKat, because THEY started the real work, and others came along. But you know what? The real credit for custom ROM goes to @codeworkx, Mr. Daniel Hillenbrand, you are the bestest of the best, the elite developer, with TeamHackSung, you guys were invincible, gods amidst the battle Samsung started, you, sir, deserve all the "thank you"s and glory, you and Mr. Andrew Dodd @Entropy512, and Mr. Guillaume Lesniak @XpLoDWilD, and all the other real developers that were barely involved with CyanogenMod. The spotlight was taken away from you, and all the noobs chanted "Thank you CyanogenMod" and forgot the real cheese, making you look like underdogs, but you guys were the The Powers That Be, TPTB from day zero. Mr. Andrew, I've read your posts (still am reading, uni = so little time) on Google Plus, and I enjoyed seeing real developers again. Although I had that pale face every time I read, I enjoyed every second of it, seeing people like you wiping Samsung's butts, cleaning and fixing their mistakes on their products, and now that you guys dropped Exynos support in general, Samsung walks in triumph, lingering around with a big grin, the walk of pride, no one to shed the light on their manufacturer errors, their own mess. Thank you, sir, and all those I mentioned, if you read this, I, on behalf the i9100 users enjoying the never-meant-to-run-on-i9100 KitKat that you developers opened path for since 2011. Thank you, for all your work, and our words will never repay you the effort put into reviving a dead device, a device that Samsung killed with its own "official" firmwares.. what a joke...
Back to you again my friend, take no offense towards you, as my words are words of a suffering i9100 user who keeps track of real development, something we haven't seen for a long time. Today's new upcoming developers have the balls to call themselves developers? In what right? Those people I mentioned up there, they hacked the crap out of Exynos, they don't have closed-source in their dictionary, and still, they kept on going, even when Mr. Guillaume bricked his Note back then, that's the ultimate sacrifice they did, not just damaging their devices, devices they bought with their hard-earned money, but also the time they put, and My Oh' My is time money... Today's development is all about Qualcomm, HA! With the right guides and tools, I can make you @CoolJoseph96 a developer, and we'll all do the Yippee ki-yay!!
Porting Android 5.0 from AOSP isn't a walk-in-the-park. You need the right drivers to be merged and stuff, drivers for the camera, for GPU, RIL related things, touchscreen and CPU code (stuff I have no experience of), AOSP comes with nothing, so you (not you personally) need to put in to get to call your device "a phone", because no one is willing to use Android Lollipop that barely has the 5.0 in About Phone. The device is dead, my friend, doing such threads is nice, motivational, you can probably do a "fight cancer" campaign that I'd guarantee it'll work, but a developer thread to bring developers to do something that reminds them of taking a poop (same as developing for Exynos), I don't think it'll help much. But here's a little bit of light at the end of tunnel for you, when CyanogenMod released CM 12 sources, or Omni or any other team releases their own source code, our chances will definitely increase, as porting AOSP like that to Exynos 4210 is like asking Apple for iOS sources, wait.. never mind (let's hope they don't take me to court...).
I apologize for bashing the thread like that my friend, I mean no harm or anything bad towards you, but this isn't as easy as we users think it is, Mr. Daniel used to spend days to get a new Android version booting on our device, and double the days to getting the device tree up and fixing bugs... etc. Patience is the key in such a situation, who knows, but take this for granted, all the ROMs starting from Android 5.0 and above are getting UNOFFICIAL tags, yup, no official maintainers, no official releases, and please don't tell me you believe CyanogenMod 11 Snapshots are made for stability on our device, because if anyone does, I sure got one hell of a laugh to enjoy. It's as stable as the Nightly branch.... which.... is.... unstable.... and because no developer tests those builds or commits new changes to bringing them to a real stable state, you just get lucky over there with the illusion of stability.
At the end of this long post, either grant some users (I'm heavily included) some time to understand how "it's meant to be played" and we, not me and you, but every enthusiastic member, will revive this device. The i9100 is capable, so let's see how far it'll go, although I am getting a new device (hoping this week or the one after, it's a Note 4 by the way), but still, I diligently feel that I must contribute to such an amazing device like many great names did, Mr. Chandra Poerwanto @fusionjack for years of giving and powering us with not only Slim, but a Sabered one, Mr. Yuri @dorimanx for your amazing power core, a legacy left for us to enjoy and new versions of Linux with customizations, Mr. Marco @Markox89 for your great work back in 2013 helping Mr. Pavel build the alpha CM11, and for the -O3 Linaro builds, @_Sale_ for NeatROM, a powerful tool and great firmware, @Nico_60 for Spirit ROM, Mr. Vivek @Vivek_Neel for everything you've given us when we barely had support of anything, but you were there since day 1 working for our device, Mr. Armen @Biftor for the one and only Biftor series, @Goldie for the amazing guides on smali and Alliance ROM, @bajee11 for Rootbox, a ROM I wish to have on KitKat, @sooti for Beanstalk, Liquid Smooth and all other ROMs you've maintained loyally, @infected_ for joining the powerful ROMs with amazing toolchains bringing not only unique features, but real smoothness as well, @Christiancs1969 for CyanoFox and @mnt Mantas Zilius, you guys rocked back then, too bad to see the ROM dead for us, the amazing Mr. Ghokhan Moral @ghokhanmoral thanks to you sir (although you're inactive for years now) I attempted to root my phone for the first time after 4 months of owning it, and it was the only custom kernel back then I used, dualboot, tweaks.., @nims11 for being an awesome maintainer, @Hopper8 for living up to the Recognized Contributor title, what an amazing member, @HardCorePawn for introducing Slim to our device, and what a love story that was and still is on my phone, @rkoby13 (you rock my friend) for being "that awesome member", you are a motivation in my eyes, a member that helped many and been a big brother at most situations with your broad knowledge, @pulser_g2 because every awesome member passed through this device and left a trace, @cybernetus and @Computoncio for keeping the legacy dorimanx left for us alive, you guys deserve a job well done by the end of the day, a big thank you guys to all the people I mentioned and definitely forgot to mention, your work and help will be commemorated by the humble users that look at this device and say, "Hell, this thing still runs, The Great Ones of today passed on this one, if it ain't for them, it would've been just another smartphone". Sorry for bringing this here, but I had to, let the forums know who made the Galaxy S2 legendary, and for all those members leaving and getting new devices that have the same forums as the i9100, the forum didn't make it itself, it's the real developers and members that made it. God bless you all.
Android 5.0 on i9100? In order to beat the beast, you have to be a beast, so roll up your sleeves and make a difference, because these people I quoted up there, the big hearts and spirit they got, we must be motivated by them, enough hiding behind our fingers and waiting for everything to come to us, let's give them a big thank you by warming up a little and do the work for once ourselves. Have a nice day/night buddy, peace out
Paul_Kolanjian said:
Buddy, what part of "error 404: I9100 developers not found" part don't you get? [...]peace out
Click to expand...
Click to collapse
Thanks for the long and true post.
I've seen many mentions of my nickname all over XDA for i9100, mixed replies, etc. So yes, I will try to port Omni 5.0 to the i9100 when the code base is stable, however while I can do the base bringup, I won't be able to maintain it long-term. So while I will attempt to port it and make most of it work, I might not can/want to make it 100% bug-free.
Paul_Kolanjian said:
Buddy, what part of "error 404: I9100 developers not found" [...] peace out
Click to expand...
Click to collapse
The best post i ever read ! Thanks for your reflections!
Paul_Kolanjian said:
Buddy, what part of "error 404: I9100 developers not found" part don't you get? I too eagerly want to get that Android Lollipop sensation on my old i9100 (two and a half years old now), but I have no knowledge in the real development, yes you read write, R E A L. You think building ROMs is development? Want me to teach you how to set up Ubuntu, download sources, and build ROMs? But does it make any of us "developers"?
Back to the real talk. So you want Android Lollipop 5.0, hell, we all want it. Seeing all those "Android 5.0 ported to blah blah" made you drool all over the screen, and gave you some hope, no? Buddy, what you are seeing are AOSP ports, that's Android Open Source Project, you read that? O P E N S O U R C E... But wait a minute, Exynos is a closed-source bastard, so why shake a leg if it ain't going to be stable, or even "bootable"? Do you think it's that easy? Just create a thread on the legendary i9100 forums and boom, hook up the devs like fish. No... And even if a developer seen your thread, they probably no longer own the device, or remembered the pain and agony of maintaining for the i9100. Do you think CyanogenMod developers ported KitKat to our device? We go ahead and talk all proud claiming "the developers" are supporting our device. HELL NO, it's amazing people who don't belong to anyone that get encouraged to do the work, people that break the limits ridiculous OEMs put to kill a device. Wanna know how KitKat and CyanogenMod 11 came to our device? You guessed it, "the developers" didn't do hell. CyanogenMod did it? They're busy cleaning their crap now that they've gone corporate, they are useless if it weren't for the maintainers of devices, people that break the locks and rule their phones, CyanogenMod just claims they're "the developers" but they can kiss my ass. @Wayland_ACE, if you are reading this, sir, I thank you for your amazing contribution, the days and hours you've put into bringing Android 4.4 to our device, the amazing builds of the first and early KitKat builds, builds that I still keep to this day. @milaq, when CyanogenMod's Jenkins eats the dirt, you were there providing us with nightlies that proved to be stable, preparing that device tree, and bringing CyanogenMod 11 to what it is today. Thank these two for KitKat, because THEY started the real work, and others came along. But you know what? The real credit for custom ROM goes to @codeworkx, Mr. Daniel Hillenbrand, you are the bestest of the best, the elite developer, with TeamHackSung, you guys were invincible, gods amidst the battle Samsung started, you, sir, deserve all the "thank you"s and glory, you and Mr. Andrew Dodd @Entropy512, and Mr. Guillaume Lesniak @XpLoDWilD, and all the other real developers that were barely involved with CyanogenMod. The spotlight was taken away from you, and all the noobs chanted "Thank you CyanogenMod" and forgot the real cheese, making you look like underdogs, but you guys were the The Powers That Be, TPTB from day zero. Mr. Andrew, I've read your posts (still am reading, uni = so little time) on Google Plus, and I enjoyed seeing real developers again. Although I had that pale face every time I read, I enjoyed every second of it, seeing people like you wiping Samsung's butts, cleaning and fixing their mistakes on their products, and now that you guys dropped Exynos support in general, Samsung walks in triumph, lingering around with a big grin, the walk of pride, no one to shed the light on their manufacturer errors, their own mess. Thank you, sir, and all those I mentioned, if you read this, I, on behalf the i9100 users enjoying the never-meant-to-run-on-i9100 KitKat that you developers opened path for since 2011. Thank you, for all your work, and our words will never repay you the effort put into reviving a dead device, a device that Samsung killed with its own "official" firmwares.. what a joke...
Back to you again my friend, take no offense towards you, as my words are words of a suffering i9100 user who keeps track of real development, something we haven't seen for a long time. Today's new upcoming developers have the balls to call themselves developers? In what right? Those people I mentioned up there, they hacked the crap out of Exynos, they don't have closed-source in their dictionary, and still, they kept on going, even when Mr. Guillaume bricked his Note back then, that's the ultimate sacrifice they did, not just damaging their devices, devices they bought with their hard-earned money, but also the time they put, and My Oh' My is time money... Today's development is all about Qualcomm, HA! With the right guides and tools, I can make you @CoolJoseph96 a developer, and we'll all do the Yippee ki-yay!!
Porting Android 5.0 from AOSP isn't a walk-in-the-park. You need the right drivers to be merged and stuff, drivers for the camera, for GPU, RIL related things, touchscreen and CPU code (stuff I have no experience of), AOSP comes with nothing, so you (not you personally) need to put in to get to call your device "a phone", because no one is willing to use Android Lollipop that barely has the 5.0 in About Phone. The device is dead, my friend, doing such threads is nice, motivational, you can probably do a "fight cancer" campaign that I'd guarantee it'll work, but a developer thread to bring developers to do something that reminds them of taking a poop (same as developing for Exynos), I don't think it'll help much. But here's a little bit of light at the end of tunnel for you, when CyanogenMod released CM 12 sources, or Omni or any other team releases their own source code, our chances will definitely increase, as porting AOSP like that to Exynos 4210 is like asking Apple for iOS sources, wait.. never mind (let's hope they don't take me to court...).
I apologize for bashing the thread like that my friend, I mean no harm or anything bad towards you, but this isn't as easy as we users think it is, Mr. Daniel used to spend days to get a new Android version booting on our device, and double the days to getting the device tree up and fixing bugs... etc. Patience is the key in such a situation, who knows, but take this for granted, all the ROMs starting from Android 5.0 and above are getting UNOFFICIAL tags, yup, no official maintainers, no official releases, and please don't tell me you believe CyanogenMod 11 Snapshots are made for stability on our device, because if anyone does, I sure got one hell of a laugh to enjoy. It's as stable as the Nightly branch.... which.... is.... unstable.... and because no developer tests those builds or commits new changes to bringing them to a real stable state, you just get lucky over there with the illusion of stability.
At the end of this long post, either grant some users (I'm heavily included) some time to understand how "it's meant to be played" and we, not me and you, but every enthusiastic member, will revive this device. The i9100 is capable, so let's see how far it'll go, although I am getting a new device (hoping this week or the one after, it's a Note 4 by the way), but still, I diligently feel that I must contribute to such an amazing device like many great names did, Mr. Chandra Poerwanto @fusionjack for years of giving and powering us with not only Slim, but a Sabered one, Mr. Yuri @dorimanx for your amazing power core, a legacy left for us to enjoy and new versions of Linux with customizations, Mr. Marco @Markox89 for your great work back in 2013 helping Mr. Pavel build the alpha CM11, and for the -O3 Linaro builds, @_Sale_ for NeatROM, a powerful tool and great firmware, @Nico_60 for Spirit ROM, Mr. Vivek @Vivek_Neel for everything you've given us when we barely had support of anything, but you were there since day 1 working for our device, Mr. Armen @Biftor for the one and only Biftor series, @Goldie for the amazing guides on smali and Alliance ROM, @bajee11 for Rootbox, a ROM I wish to have on KitKat, @sooti for Beanstalk, Liquid Smooth and all other ROMs you've maintained loyally, @infected_ for joining the powerful ROMs with amazing toolchains bringing not only unique features, but real smoothness as well, @Christiancs1969 for CyanoFox and @mnt Mantas Zilius, you guys rocked back then, too bad to see the ROM dead for us, the amazing Mr. Ghokhan Moral @ghokhanmoral thanks to you sir (although you're inactive for years now) I attempted to root my phone for the first time after 4 months of owning it, and it was the only custom kernel back then I used, dualboot, tweaks.., @nims11 for being an awesome maintainer, @Hopper8 for living up to the Recognized Contributor title, what an amazing member, @HardCorePawn for introducing Slim to our device, and what a love story that was and still is on my phone, @rkoby13 (you rock my friend) for being "that awesome member", you are a motivation in my eyes, a member that helped many and been a big brother at most situations with your broad knowledge, @pulser_g2 because every awesome member passed through this device and left a trace, @cybernetus and @Computoncio for keeping the legacy dorimanx left for us alive, you guys deserve a job well done by the end of the day, a big thank you guys to all the people I mentioned and definitely forgot to mention, your work and help will be commemorated by the humble users that look at this device and say, "Hell, this thing still runs, The Great Ones of today passed on this one, if it ain't for them, it would've been just another smartphone". Sorry for bringing this here, but I had to, let the forums know who made the Galaxy S2 legendary, and for all those members leaving and getting new devices that have the same forums as the i9100, the forum didn't make it itself, it's the real developers and members that made it. God bless you all.
Android 5.0 on i9100? In order to beat the beast, you have to be a beast, so roll up your sleeves and make a difference, because these people I quoted up there, the big hearts and spirit they got, we must be motivated by them, enough hiding behind our fingers and waiting for everything to come to us, let's give them a big thank you by warming up a little and do the work for once ourselves. Have a nice day/night buddy, peace out
Click to expand...
Click to collapse
Truly one of the best posts I have read so far.
Well said!
And Thanks for the appreciation.
Vivek_Neel said:
Truley one of the best posts I have read so far.
Well said!
And Thanks for the appreciation.
Click to expand...
Click to collapse
a monster post
+1
I'll take a look, but no any promises...
What a result for the I9100. :thumbup:
Compiling lollipop
Hey guys,
I really want android 5.0 on the S2 ( i9100 ) so i decided to help , but there is only 1 problem i am not a pro in ubuntu.
I compiled a kernel once but it wasn't booting.
But here's my question:
Can someone help me with it so we will make a development team
My pc can be on during the whole day/night
the specs are:
Intel Core2Duo @ 1,80GHz
4 GB R.A.M
200GB hdd
256mb Video memory ( BAD )
Please pm me if u want to help me or if you want to form a team.
Thanks in advance
@Paul_Kolanjian wind stopped blowing when i read your post, past time images started to flash in my brain as i read every word..
Truly the best appreciation post for all (current/ex) i9100 developers, thank you very much developers for all you've done..
btw i'd like to add 1 person to my thank list, that is @krarvind who introduced slim to our device.
We have to wait!
jeffreyvh said:
Hey guys,
I really want android 5.0 on the S2 ( i9100 ) so i decided to help , but there is only 1 problem i am not a pro in ubuntu.
I compiled a kernel once but it wasn't booting.
But here's my question:
Can someone help me with it so we will make a development team
My pc can be on during the whole day/night
the specs are:
Intel Core2Duo @ 1,80GHz
4 GB R.A.M
200GB hdd
256mb Video memory ( BAD )
Please pm me if u want to help me or if you want to form a team.
Thanks in advance
Click to expand...
Click to collapse
We'll wait for a stable source code of OmniRom or CyanogenMod! After there're some progress with these rom we can do something
CoolJoseph96 said:
We'll wait for a stable source code of OmniRom or CyanogenMod! After there're some progress with these rom we can do something
Click to expand...
Click to collapse
I want to make the AOSP Android 5.0.0 .
Do you want to help me?
Please p.m me
jeffreyvh said:
I want to make the AOSP Android 5.0.0 .
Do you want to help me?
Please p.m me
Click to expand...
Click to collapse
Wow. Aren't you on fire.
Well, right now I am waiting for stable CyanogenMod 12 source code.
If I am not mistaken, Omni sources are up and running right?
rqmok said:
Wow. Aren't you on fire.
Well, right now I am waiting for stable CyanogenMod 12 source code.
If I am not mistaken, Omni sources are up and running right?
Click to expand...
Click to collapse
Yes you are right!
Do you want to join my team for the development?
Because every little piece of help does make it a shorter time to wait
XpLoDWilD said:
Thanks for the long and true post.
I've seen many mentions of my nickname all over XDA for i9100, mixed replies, etc. So yes, I will try to port Omni 5.0 to the i9100 when the code base is stable, however while I can do the base bringup, I won't be able to maintain it long-term. So while I will attempt to port it and make most of it work, I might not can/want to make it 100% bug-free.
Click to expand...
Click to collapse
Hi XpLoDWilD, i krów it is wrong tread but do you will try it also for n7000?
Sent from my GT-N7000 using XDA Free mobile app
Paul_Kolanjian said:
Buddy, what part of "error 404: I9100 developers not found" part don't you get? I too eagerly want to get that Android Lollipop sensation on my old i9100 (two and a half years old now), but I have no knowledge in the real development, yes you read write, R E A L. You think building ROMs is development? Want me to teach you how to set up Ubuntu, download sources, and build ROMs? But does it make any of us "developers"?
Back to the real talk. So you want Android Lollipop 5.0, hell, we all want it. Seeing all those "Android 5.0 ported to blah blah" made you drool all over the screen, and gave you some hope, no? Buddy, what you are seeing are AOSP ports, that's Android Open Source Project, you read that? O P E N S O U R C E... But wait a minute, Exynos is a closed-source bastard, so why shake a leg if it ain't going to be stable, or even "bootable"? Do you think it's that easy? Just create a thread on the legendary i9100 forums and boom, hook up the devs like fish. No... And even if a developer seen your thread, they probably no longer own the device, or remembered the pain and agony of maintaining for the i9100. Do you think CyanogenMod developers ported KitKat to our device? We go ahead and talk all proud claiming "the developers" are supporting our device. HELL NO, it's amazing people who don't belong to anyone that get encouraged to do the work, people that break the limits ridiculous OEMs put to kill a device. Wanna know how KitKat and CyanogenMod 11 came to our device? You guessed it, "the developers" didn't do hell. CyanogenMod did it? They're busy cleaning their crap now that they've gone corporate, they are useless if it weren't for the maintainers of devices, people that break the locks and rule their phones, CyanogenMod just claims they're "the developers" but they can kiss my ass. @Wayland_ACE, if you are reading this, sir, I thank you for your amazing contribution, the days and hours you've put into bringing Android 4.4 to our device, the amazing builds of the first and early KitKat builds, builds that I still keep to this day. @milaq, when CyanogenMod's Jenkins eats the dirt, you were there providing us with nightlies that proved to be stable, preparing that device tree, and bringing CyanogenMod 11 to what it is today. Thank these two for KitKat, because THEY started the real work, and others came along. But you know what? The real credit for custom ROM goes to @codeworkx, Mr. Daniel Hillenbrand, you are the bestest of the best, the elite developer, with TeamHackSung, you guys were invincible, gods amidst the battle Samsung started, you, sir, deserve all the "thank you"s and glory, you and Mr. Andrew Dodd @Entropy512, and Mr. Guillaume Lesniak @XpLoDWilD, and all the other real developers that were barely involved with CyanogenMod. The spotlight was taken away from you, and all the noobs chanted "Thank you CyanogenMod" and forgot the real cheese, making you look like underdogs, but you guys were the The Powers That Be, TPTB from day zero. Mr. Andrew, I've read your posts (still am reading, uni = so little time) on Google Plus, and I enjoyed seeing real developers again. Although I had that pale face every time I read, I enjoyed every second of it, seeing people like you wiping Samsung's butts, cleaning and fixing their mistakes on their products, and now that you guys dropped Exynos support in general, Samsung walks in triumph, lingering around with a big grin, the walk of pride, no one to shed the light on their manufacturer errors, their own mess. Thank you, sir, and all those I mentioned, if you read this, I, on behalf the i9100 users enjoying the never-meant-to-run-on-i9100 KitKat that you developers opened path for since 2011. Thank you, for all your work, and our words will never repay you the effort put into reviving a dead device, a device that Samsung killed with its own "official" firmwares.. what a joke...
Back to you again my friend, take no offense towards you, as my words are words of a suffering i9100 user who keeps track of real development, something we haven't seen for a long time. Today's new upcoming developers have the balls to call themselves developers? In what right? Those people I mentioned up there, they hacked the crap out of Exynos, they don't have closed-source in their dictionary, and still, they kept on going, even when Mr. Guillaume bricked his Note back then, that's the ultimate sacrifice they did, not just damaging their devices, devices they bought with their hard-earned money, but also the time they put, and My Oh' My is time money... Today's development is all about Qualcomm, HA! With the right guides and tools, I can make you @CoolJoseph96 a developer, and we'll all do the Yippee ki-yay!!
Porting Android 5.0 from AOSP isn't a walk-in-the-park. You need the right drivers to be merged and stuff, drivers for the camera, for GPU, RIL related things, touchscreen and CPU code (stuff I have no experience of), AOSP comes with nothing, so you (not you personally) need to put in to get to call your device "a phone", because no one is willing to use Android Lollipop that barely has the 5.0 in About Phone. The device is dead, my friend, doing such threads is nice, motivational, you can probably do a "fight cancer" campaign that I'd guarantee it'll work, but a developer thread to bring developers to do something that reminds them of taking a poop (same as developing for Exynos), I don't think it'll help much. But here's a little bit of light at the end of tunnel for you, when CyanogenMod released CM 12 sources, or Omni or any other team releases their own source code, our chances will definitely increase, as porting AOSP like that to Exynos 4210 is like asking Apple for iOS sources, wait.. never mind (let's hope they don't take me to court...).
I apologize for bashing the thread like that my friend, I mean no harm or anything bad towards you, but this isn't as easy as we users think it is, Mr. Daniel used to spend days to get a new Android version booting on our device, and double the days to getting the device tree up and fixing bugs... etc. Patience is the key in such a situation, who knows, but take this for granted, all the ROMs starting from Android 5.0 and above are getting UNOFFICIAL tags, yup, no official maintainers, no official releases, and please don't tell me you believe CyanogenMod 11 Snapshots are made for stability on our device, because if anyone does, I sure got one hell of a laugh to enjoy. It's as stable as the Nightly branch.... which.... is.... unstable.... and because no developer tests those builds or commits new changes to bringing them to a real stable state, you just get lucky over there with the illusion of stability.
At the end of this long post, either grant some users (I'm heavily included) some time to understand how "it's meant to be played" and we, not me and you, but every enthusiastic member, will revive this device. The i9100 is capable, so let's see how far it'll go, although I am getting a new device (hoping this week or the one after, it's a Note 4 by the way), but still, I diligently feel that I must contribute to such an amazing device like many great names did, Mr. Chandra Poerwanto @fusionjack for years of giving and powering us with not only Slim, but a Sabered one, Mr. Yuri @dorimanx for your amazing power core, a legacy left for us to enjoy and new versions of Linux with customizations, Mr. Marco @Markox89 for your great work back in 2013 helping Mr. Pavel build the alpha CM11, and for the -O3 Linaro builds, @_Sale_ for NeatROM, a powerful tool and great firmware, @Nico_60 for Spirit ROM, Mr. Vivek @Vivek_Neel for everything you've given us when we barely had support of anything, but you were there since day 1 working for our device, Mr. Armen @Biftor for the one and only Biftor series, @Goldie for the amazing guides on smali and Alliance ROM, @bajee11 for Rootbox, a ROM I wish to have on KitKat, @sooti for Beanstalk, Liquid Smooth and all other ROMs you've maintained loyally, @infected_ for joining the powerful ROMs with amazing toolchains bringing not only unique features, but real smoothness as well, @Christiancs1969 for CyanoFox and @mnt Mantas Zilius, you guys rocked back then, too bad to see the ROM dead for us, the amazing Mr. Ghokhan Moral @ghokhanmoral thanks to you sir (although you're inactive for years now) I attempted to root my phone for the first time after 4 months of owning it, and it was the only custom kernel back then I used, dualboot, tweaks.., @nims11 for being an awesome maintainer, @Hopper8 for living up to the Recognized Contributor title, what an amazing member, @HardCorePawn for introducing Slim to our device, and what a love story that was and still is on my phone, @rkoby13 (you rock my friend) for being "that awesome member", you are a motivation in my eyes, a member that helped many and been a big brother at most situations with your broad knowledge, @pulser_g2 because every awesome member passed through this device and left a trace, @cybernetus and @Computoncio for keeping the legacy dorimanx left for us alive, you guys deserve a job well done by the end of the day, a big thank you guys to all the people I mentioned and definitely forgot to mention, your work and help will be commemorated by the humble users that look at this device and say, "Hell, this thing still runs, The Great Ones of today passed on this one, if it ain't for them, it would've been just another smartphone". Sorry for bringing this here, but I had to, let the forums know who made the Galaxy S2 legendary, and for all those members leaving and getting new devices that have the same forums as the i9100, the forum didn't make it itself, it's the real developers and members that made it. God bless you all.
Android 5.0 on i9100? In order to beat the beast, you have to be a beast, so roll up your sleeves and make a difference, because these people I quoted up there, the big hearts and spirit they got, we must be motivated by them, enough hiding behind our fingers and waiting for everything to come to us, let's give them a big thank you by warming up a little and do the work for once ourselves. Have a nice day/night buddy, peace out
Click to expand...
Click to collapse
This surely one of the best things I have read in a long time... I haven't been here since the release of the phone...but I have seen @Wayland_ACE did when 4.4 was released... He did a great job and dorimanx and all the other great devs... Also Seeing @XpLoDWilD wanting to revive the exynos 4210, sir you're amazing... Although @Entrophy512 seems to want to just completely remove exynos 4210 from his life , at least you want to try...
XpLoDWilD said:
Thanks for the long and true post.
I've seen many mentions of my nickname all over XDA for i9100, mixed replies, etc. So yes, I will try to port Omni 5.0 to the i9100 when the code base is stable, however while I can do the base bringup, I won't be able to maintain it long-term. So while I will attempt to port it and make most of it work, I might not can/want to make it 100% bug-free.
Click to expand...
Click to collapse
Wayland_ACE said:
I'll take a look, but no any promises...
Click to expand...
Click to collapse
Dudes, you're awesome
@Paul_Kolanjian
Thanks for such a long post. Finally something worth to read through
And thanks for the compliment. Although I didn't do much, other than helping out lost souls on the way.:angel:
If Android 5.0 will come to S-2 it will....if not....i'm more than happy and extremely thankful to SlimRoms Team and @fusionjack who's maintaining SlimSaber for us.....it's just raw power that makes me to keep my device instead of changing it
---------- Post added at 05:08 PM ---------- Previous post was at 05:02 PM ----------
jeffreyvh said:
Yes you are right!
Do you want to join my team for the development?
Because every little piece of help does make it a shorter time to wait
Click to expand...
Click to collapse
Sorry to say....but with your machine specs it would take looooong to compile the ROM. Not mentioning that you have to learn of "how to" on the way....that could be difficult coz nowadays knowledge is expected from one that offered help with "Real development stuff" like @Paul_Kolanjian said in his super post above.
The "Real Developers" don't have time to teach newbies all over. But luckily developers are very smart and they made a bunch of "How to's" all over the Google. And you can find a lot of info on that IMHO
@QA Bot went haywire, eh?...LOL
Hello everyone,
most of you probably don't know me since I did not develop for Samsung devices for quite some time now.
I would be interested in aiding the Exynos 5420 development scene (in particular on the Galaxy Note 10.1) and prepare a custom Android distribution for it (Team EOS 5.0 - Lollipop).
I can get all the required drivers and binaries I need for development, since most of it is open source luckily.
And the Nexus 10 (manta) can still be used as reference for many things.
All I need is a development device to debug on.
It is particularly important that this is the Galaxy Note 10.1 EXYNOS (WiFi-only variant), and not the LTE (Qualcomm) variant.
I created this thread to ask whether someone has a spare device lying around, maybe because of the little development on Exynos 5 devices, or if people would be willing to donate a device (I'm a university student and unfortunately can not afford the full price for a new device. I'm willing to dive into the Exynos development scene and spend time on this device though, including extensive debugging).
You can leave a reply in this thread or contact me on gmail: [email protected]
I have a better idea. Sending device is a problem. But we can donate to you, and then u can purchase P600 or P601 on SWAPA or EBAY. not new but fully working
I would be glad to see working AOSP/MAHDI or other ROMs runnig on my P601
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
RaymanFX said:
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
Click to expand...
Click to collapse
I think it would be better to ask for donations because there is not a lot of people here although it would be hard. There have been previous instances where at least 2 different devs raised donations for this device before stopping development shortly after so people do have some trust issues. It would take a while but i'm sure people would donate considering you are offering an AOSP experience. If you renamed this thread to something like: Donations needed for new device- AOSP rom development. Then it would catch a lot of eyes because that's what a lot of people want The question remains whether people would actually donate. The average cost for you would be around 250-300 euros I think. That means you would need around 28 people (10 each). Whatever way you decide to go down, I wish you luck and I look forward to any rom developments if you do manage to get the device :good:
You seem to have quite a respectable history (in both Rom & kernel developement), so I think getting enough donations should be doable (and I'd be willing to donate a few bucks myself)
But I do have a few questions:
1) What about warranty? Some devs who had collected donations for a (used) device, have bricked their devices -> no more developement
Therefore P600 owners might be scared / hard to convince
2) what exactly is "Team EOS 5.0" and what makes it different from other Roms? Would you perhaps consider developing other Roms / kernels as well? (like porting over PA for example?)
Or would you maybe consider becoming the official P600 CyanogenMod maintainer (since we don't have one, yet)? [<- I think this one would be reason enough to donate]
Last but not least:
You could ask one of the XDA members who managed the previous donation-collections for help (they have successfully done it before, so they might be able to do it again :fingers-crossed: )
PS: The Note 10.1 2014 is great for college, trust me - I'm a student, too . All you need is the Papyrus-App from the Play Store.
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
RaymanFX said:
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
Click to expand...
Click to collapse
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
22sl22 said:
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
Click to expand...
Click to collapse
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Hey guys. That donation thread I started a while ago was on a whim cause I wanted Hyperdrive by sbreen on my Note. Was lucky enough to have him commit and get enough people chipping in for the tablet which was met with success. I'm by no means a great organizer or somebody with tight connections here on XDA . Probably would be best if someone who wanted to head it up would start a new thread stating the case.
Best of luck!
RaymanFX said:
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Click to expand...
Click to collapse
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
RaymanFX said:
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
Click to expand...
Click to collapse
Sure, i'll open one now :good:
I'll also post a message in here after the new thread has been created so that people know http://forum.xda-developers.com/galaxy-note-10-2014/general/rumours-plans-to-android-5-0-t2861225
EDIT: before I open the thread, how much do you actually need? $300 is about 240 Euros, not 270 so we will need a bit more, say $350, would that be OK?
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Why a P600 model and not the P601 model?
The p601 to develop is exactly the same from p600 plus the phone side.
Sent from my SM-P601 using XDA Free mobile app
Why the delay? Here are the first 10 €!
RaymanFX said:
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Click to expand...
Click to collapse
Hi RaymanFX!
Glad to see that a real dev wants to take our device and port CM11 for us.
I do not make many words, but simply push the first $ 12.12 to you.
That's the current rates for 10, -€.
Hope it works as good as for sbreen (dev from HyperdriveRom) and many people jumps like lemmings behind me. :good: Haha!
Hope also we get the money quickly together and will try to continue to encourage people to make a small donation.
10,-€
Transaktionscode:
7R473626855605042
You also get a short pm
Hey RaymanFX, excited for asop 5.0 but curious about some of the stock features that make this tablet. Is there any way to preserve multi window support or s-pen features ?
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Yay!
Sent from my LG-H811 using Tapatalk
Hnk1 said:
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
Click to expand...
Click to collapse
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
v1rk said:
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
Click to expand...
Click to collapse
aaronrw said:
Yay!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
sweetrobot said:
about ****ing time!!! so sick of the nonSense...
cm / aosp / aokp ftw.
paperweight for the last couple of months. tried a bunch of the existing roms, just not my cup of tea.
Click to expand...
Click to collapse
k1moe said:
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Click to expand...
Click to collapse
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Hnk1 said:
DEVELOPMENT PROCESS
INTRODUCTION
I am starting this forum in hope of educating my readers about ROM development according to my experiences. Further, I will highlight what is the usual developers' thought process before they decide to build a ROM for a specific device. The reasons why they usually choose a certain device or why they prefer one device over another would also be stated briefly. I also have intention of looking into ways how we can speed up ROM productions for any device and what you can do to play your part.
I UNDERSTAND YOUR FRUSTRATION FOR NO CUSTOM ROMS EVEN AFTER SOME MONTHS BUT THIS DOESNOT GIVE YOU THE RIGHT TO SPAM
I am sure many of you must be really disappointed by the lack of development for your device and I know this must be frustrating when we see other devices are getting ROMS so quickly. I know many are too excited when they find a little about any OTA/ Custom ROM and sharing such news is fully justified. However, it's beyond my logic & thinking why the forums are SPAMMED for any little information they might find anywhere regardless of their sources or if it has been ALREADY POSTED. I reckon many of these threads could have been avoided by simply searching in the forum.
ROM DEVELOPMENT
I can assure you that many develoeprs are working very hard to PORT and develop different ROMS for a device. However, the reason we can not see any CUSTOM roms till yet is due to complicated nature of a device itself.
Usually developers prefer a device which is :
1. Easy to work with, less complicated to code with or in other terms DEVELOPER friendly. For example, for a while I had a real issue with HTC phones as they have too many things to work with like Bootloader, S Lock, Radios, Hboot version etc while in Nexus devices you only need to unlock your device with one fastboot command. That's all and you are ready to flash ROMs.
2. Personal preference of Device. This simply means that we all have different tastes and thus we choose different devices. A certain developer might only work for a certain brand while other might work with few brands. This has nothing to do with anything but a personal choice.
3. A device that promises reward in terms of money/self satisfaction. Developers usually go for devices which have most active users so if their intention is also to get some money out of it in terms of donation, this will work well with devices which are more in number.
4. Knowledge about a certain brand more than another.
5. MONEY TO BUY A CERTAIN DEVICE/DEVICES. Suppose a developer wants to make ROMS for Xperia L/ SP/Z and Xperia U. Yet he only has 500 dollars to choose from. He then will have to make a choice between devices and this will eventually mean that not all of the devices get the same treatment. Money is the most decisive factor why a developer doesnot chose your device but rather another. For example purpose only, if I have to choose between devices, I might prefer SP over Xperia L as I can see more future of SP than Xperia L(I might be wrong).
6. Simply he bought a device or it is gifted/donated to him
SOME REQUESTS
Please STOP bugging developers by trivial questions. Just think how many other people ask the same question and it gets very frustrating to actually work on the device itself.
Every developer has a LIFE apart from developing ROMs. They also have a family, school, work, hobbies, bad days and so much like us. So they will do it when they feel like doing it. Just sit back and relax. Enjoy your device until developer releases the ROM for your device. Asking a REASONABLE question seems plausible but asking same questions/useless questions without using brains is just STUPID. Kindly refrain from that.
If you have seen a developer who has taken the initiative to work on your device , the best thing to do is to be patient. Let him concentrate. Spamming and spamming again won't help really.Yet some users start SPAMMING developers, their twitters, blogs and accounts. That's really sad. You can discuss on the forum what you think about it but IRKING developers isnot really cool.
WHAT CAN YOU DO TO HELP DEVELOPERS AND SEE CUSTOM ROMS.
1. Search the form first and look for answers. DON'T start new posts/questions/threads when it is ALREADY mentioned in some other section.
2. STOP PMing/SPAMING developers but rather ask a question WHICH havenot been asked before in the forum. Do not engage in the habit of making a new forum for everything. Try to keep threads as little as possible.
3. Follow developers and see what they have updated about on their official twitter,facebook,etc rather than bugging them on different forums/social websites.
4 DONATE THEM. DONATE THEM . DONATE THEM!
The amount of efforts they put, sitting for hours in front of their PCs and I know how frustrating it gets when you try to run commands and everything seems to work yet you can not boot up your ROM. And worse, you can not find WHY really. Just a change in line in build.prop results in failure of ROM to boot up and specially working from source to build ROM is really really tough. The best thing you can do is being supportive and patient !
A ROM development requires not just EXCESSIVE amount of hardwork, time, energy and dedication but also they need MONEY to actually buy devices and try it on. They are happy and encouraged to keep on developing ROMs when they see their efforts are not wasted and they are rewarded and respected for what they do.
SOME BASICS OF ROM DEVELOPMENT
Usually this is required to make a full custom ROM
Blobs which contain hardware information which comes from hardware manufacturer like Qualcomm in case of Snapdragon processors
A fully functional device tree
Latest Android source (Or the android version source you want to build for)
Specific Custom ROM coding which is based on Android Source
Usually a device tree and kernel tree is needed before custom roms can be made available. This is a long trial and error process in which every component of hardware is made functional as usually manufacturers do not provide any code for their devices and thus new code is to be written which is very frustrating and long process!
Click to expand...
Click to collapse
Hnk1 said:
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Click to expand...
Click to collapse
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Thank GOD
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
I'll be happy to donate
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
v1rk said:
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Click to expand...
Click to collapse
Cheers for side information. I know the developer and I'm pretty sure you'd get a kernel and Cm12.1 pretty soon.
Actually I Would let the developers sort out their differences themselves, for me it is Cm12.1 coming pretty soon.
agentfusion said:
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
Click to expand...
Click to collapse
Whhhaaatttttt?!?!?! Miui?!?!?
Wait
Galaxysm said:
Whhhaaatttttt?!?!?! Miui?!?!?
Click to expand...
Click to collapse
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
agentfusion said:
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
Click to expand...
Click to collapse
Nice I can't wait!!
Nice to see this coming ... And for MIUI I haven't been able to use it since I change my original EVO ... It would be great to have it as an option ...
Great news
Daily reminder that CM12 is a desperately needed and coveted thingy for the m8+1.
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
vegetaleb said:
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Cm12.1 is lolipop 5.1
Anyone knows the progress on this...
epedrosa said:
Anyone knows the progress on this...
Click to expand...
Click to collapse
Be patient. The OP says "within a month" and it has only been roughly 2 weeks