Related
Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
I'm using an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Yes I'm using Cronos Froyo, and I'm an honest user who doesn't care much for xda forums politics.
I've read the comments that the moderators have written in the thread and whilst I understand what they have written, do end users really have to suffer because of a dispute between developers?
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
Also, I wonder if the xda moderators have consulted laywers about the GPL as it is a legal document and thus won't be as black and white as it seems. A lot of companies behave not dissimilarly to feeyo and survive the threat of any action.
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
plonkersaurus said:
Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
I'm using an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Yes I'm using Cronos Froyo, and I'm an honest user who doesn't care much for xda forums politics.
I've read the comments that the moderators have written in the thread and whilst I understand what they have written, do end users really have to suffer because of a dispute between developers?
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
Also, I wonder if the xda moderators have consulted laywers about the GPL as it is a legal document and thus won't be as black and white as it seems. A lot of companies behave not dissimilarly to feeyo and survive the threat of any action.
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
I believe he still releases in his forum - just do a google search
nope, it seems his account has been suspended on the domain, not good.
plonkersaurus said:
sing an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Click to expand...
Click to collapse
There's AOSP ROMs. Without even plugging my own, there's the Fusion project for a start.
Froyd and Fusion are Cyanogen based roms which I've tried and don't work so well for me.
I'd count them as Vanilla roms not AOSP
Dude. You might as well turn xda into thepiratebay.Breaking a software licence is illegal no matter if the software is proprietary or open source.
Sent from my HTC Hero using XDA App
plonkersaurus said:
Froyd and Fusion are Cyanogen based roms which I've tried and don't work so well for me.
I'd count them as Vanilla roms not AOSP
Click to expand...
Click to collapse
The only non AOSP thing about them is:
They include Google Apps
They include proprietary libs grabbed from the phone to make the phone work.
Guess what, that's what AOSP ROMs do too, the ones released here anyway, since they're largely unusable without Google Apps (Market, etc) and the libs needed to make the phone work.
If you want plain AOSP, you better have an ADP1, ADP2 or a Nexus One. There is no such thing as a pure AOSP Hero ROM.
What people mean when they refer to AOSP, is they yanked the git straight from Android and compiled it for X phone, adding in whatever apps along with the Google apps and the prop libs.
Cyanogenmod is also AOSP in that same sense. Only there's a ton of people working on the repo and fixing stuff that Android don't or haven't yet.
If you've run into a CM based ROM that doesn't work well for you then it's still down to the builder. Chances are if they made an "AOSP" ROM, it'd be even worse.
I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.
Hacre said:
The only non AOSP thing about them is:
They include Google Apps
They include proprietary libs grabbed from the phone to make the phone work.
Guess what, that's what AOSP ROMs do too, the ones released here anyway, since they're largely unusable without Google Apps (Market, etc) and the libs needed to make the phone work.
If you want plain AOSP, you better have an ADP1, ADP2 or a Nexus One. There is no such thing as a pure AOSP Hero ROM.
What people mean when they refer to AOSP, is they yanked the git straight from Android and compiled it for X phone, adding in whatever apps along with the Google apps and the prop libs.
Cyanogenmod is also AOSP in that same sense. Only there's a ton of people working on the repo and fixing stuff that Android don't or haven't yet.
If you've run into a CM based ROM that doesn't work well for you then it's still down to the builder. Chances are if they made an "AOSP" ROM, it'd be even worse.
Click to expand...
Click to collapse
Cyanogenmod roms change a lot more things than just needed to get android working properly and I'm not a huge fan of all the changes
plonkersaurus said:
Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
.....
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
.....
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
1... Switch to another ROM, or stick with what you have, they are your two options.
2... No, other devs do not have a "donators only beta testing section", and regardless if they did or not, I think you need to go and re-read all the info the mods have given about the GPL issue before adding your 2 pence worth.
3... I owe feeyo nothing. He may have produced ROMS, but contribute to the community he did not.
Sent from my HTC Hero using XDA App
plonkersaurus said:
I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.
Click to expand...
Click to collapse
Hahaha what. Being a developer doesn't mean you "get" the point of the GPL. Plenty of developers over at Microsoft don't "get" it. That doesn't make it any less valid.
In fact your entire post just screams "I do not understand open source development, what on Earth is wrong with people doing stuff themselves and hoarding it".
The "pioneering development" as you put it doesn't happen by individuals because it happens in groups. You know, lots of minds working towards a common goal.
Jesus on a bike.
EDIT: woah..
plonkersaurus said:
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
I missed this when I first read the OP. Hahaha no he wasn't. Battery life has to be one of the most done to death topics on these forums and do you know what? Your battery life is solely dependent on you the phone user, providing of course the developer or the cooker hasn't done something utterly retarded to the ROM that causes battery to run down.
Until Froyo was released, Cronos wasn't even a compiled ROM it was a precompiled Sense ROM and as such subject to all the whims of the HTC base that the rest of us were.
Oh and I don't owe him anything. Never used his ROM, never benefited from what he apparently gave back to the community (nothing). He owed me and whomever else asked him for it, source code, which happened to be the one thing he never once provided while being happy to make use of source code provided by others.
Hacre said:
Hahaha what. Being a develloper doesn't mean you "get" the point of the GPL. Plenty of developers over at Microsoft don't "get" it. That doesn't make it any less valid.
In fact your entire post just screams "I do not understand open source development, what on Earth is wrong with people doing stuff themselves and hoarding it".
The "pioneering development" as you put it doesn't happen by individuals because it happens in groups. You know, lots of minds working towards a common goal.
Jesus on a bike.
Click to expand...
Click to collapse
I didn't mention GPL anywhere in my post.
I mentioned that I wouldn't help this community due to the fact people would be accepting donations for what would be in part my work which I think is immoral.
That is what my post was about.
Plus I think you will find Linus wrote Linux by himself so individuals are capable of greatness.
plonkersaurus said:
Plus I think you will find Linus wrote Linux by himself so individuals are capable of greatness.
Click to expand...
Click to collapse
Re check your history. Linus did not write Linux by himself. He wrote the first kernel by himself. Linux wasn't truly born until he released it along with the source code and people started fixing it, writing drivers for it and writing coreutils/toolchains around it. It didn't approach anything like popular until it got x86 support and the kernel reached a level of maturity in the 2.0.x releases. Collaborative development/debugging. It's an amazing thing. Stunted quickly by the "I will not share" attitude that you're defending and supporting.
I am genuinely curious as to how you can guarantee that people will receive donations for your work. Or why you'd even care. My kernel source tree is used by others, I don't lose a wink of sleep over whether they get donations for their finished ROM or not, it doesn't matter.
Donations are just that, donations. They are not a fee. They are not someone taking someone else's work and then charging for it. They're something that an individual feels that they want to give to someone out of the kindness of their hearts as a thank you as well as the fact that donations are quite a rarity.
I got my first donation today. It'll buy me a few beers. It won't make me rich. I got it for my work on the kernel and my work on the Villain 2.2 ROMs. Have a guess how many people at Villain are now pissy that I got a donation and not the project itself. None. Have a guess how many GNU developers are now hand wringing themselves with pure fret because some guy got bought a beer for some work he did on their code. None.
You didn't have to mention the GPL in your post. The GPL is why these ridiculous threads keep springing up, it was the GPL and the failure to adhere to it, that got Feeyo canned.
People with your attitude toward community development have no place on these forums. Kindly take the door that has a Feeyo shaped hole in it.
plonkersaurus said:
I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.
Click to expand...
Click to collapse
If you don't want to share then Android is not for you.
And why the big deal about asking for donations. Its not free to run a site. And a donation is hardly mandatory, the clue is in the name, no-one was bent over and forced to do anything they never wanted to.
I have used Villain on and off since Feb and haven't donated a penny.
.... and Batman? Really? Yes he makes the decisions that no one else can, for the greater good, the bigger picture... he doesn't play hero just to boost his own ego.
Sent from my HTC Hero using XDA App
Hacre said:
EDIT: woah..
I missed this when I first read the OP. Hahaha no he wasn't. Battery life has to be one of the most done to death topics on these forums and do you know what? Your battery life is solely dependent on you the phone user, providing of course the developer or the cooker hasn't done something utterly retarded to the ROM that causes battery to run down.
Until Froyo was released, Cronos wasn't even a compiled ROM it was a precompiled Sense ROM and as such subject to all the whims of the HTC base that the rest of us were.
Oh and I don't owe him anything. Never used his ROM, never benefited from what he apparently gave back to the community (nothing). He owed me and whomever else asked him for it, source code, which happened to be the one thing he never once provided while being happy to make use of source code provided by others.
Click to expand...
Click to collapse
Ok, so you never used his rom. I did and it was leagues ahead of anything else at the time. It made our phones really usable with 2.1. I remember when it was first released it was in the top 5 threads for a week on the front page of xda so I'm sure I wasn't the only one to experience this.
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.
plonkersaurus said:
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.
Click to expand...
Click to collapse
My first four or five requests were incredibly polite. There were a plethora of polite request the first time he pulled this stunt too. My reason for asking was irrelevant. However my reason for asking for those particular sources, were twofold:
1: I didn't believe it.
2: If it was true then the community should damn well get access to it so we as a group can get it up to full working order so that EVERY ROM DEVELOPER can make use of it.
Taken over? What? I now don't believe that you're a developer, at least nothing outside pointing and clicking in a GUI based programming tool in some office somewhere, because you clearly have no idea of what collaborative development is. You cannot shut anyone, ANYONE, out of a GPL project, that's the whole frigging point. See my signature? Source code. Source code anyone can take and modify. Source code people are welcome to change, fix, port, patch and if they want to, submit a pull request so I can merge those fixes in.
Click the link. Follow the fork tree. Observe the magic as my changes move upstream to the original cyanogenmod + Hero kernel. Observe further magic as changes they make merge their way down into my kernel. Yeah I/we are really all about shutting people out.
Stop trolling.
plonkersaurus said:
Ok, so you never used his rom. I did and it was leagues ahead of anything else at the time. It made our phones really usable with 2.1. I remember when it was first released it was in the top 5 threads for a week on the front page of xda so I'm sure I wasn't the only one to experience this.
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.
Click to expand...
Click to collapse
You might be right, maybe they wouldn't have let him be in the team, maybe they would have. Who cares, they would have had to credit it to him either way, just as they credit help from other developers now.
The main point is that he wasn't willing to help push things forward. He wanted all the spotlight for himself.
Sent from my HTC Hero using XDA App
Hacre said:
Re check your history. Linus did not write Linux by himself. He wrote the first kernel by himself. Linux wasn't truly born until he released it along with the source code and people started fixing it, writing drivers for it and writing coreutils/toolchains around it. It didn't approach anything like popular until it got x86 support and the kernel reached a level of maturity in the 2.0.x releases. Collaborative development/debugging. It's an amazing thing. Stunted quickly by the "I will not share" attitude that you're defending and supporting.
I am genuinely curious as to how you can guarantee that people will receive donations for your work. Or why you'd even care. My kernel source tree is used by others, I don't lose a wink of sleep over whether they get donations for their finished ROM or not, it doesn't matter.
Donations are just that, donations. They are not a fee. They are not someone taking someone else's work and then charging for it. They're something that an individual feels that they want to give to someone out of the kindness of their hearts as a thank you as well as the fact that donations are quite a rarity.
I got my first donation today. It'll buy me a few beers. It won't make me rich. I got it for my work on the kernel and my work on the Villain 2.2 ROMs. Have a guess how many people at Villain are now pissy that I got a donation and not the project itself. None. Have a guess how many GNU developers are now hand wringing themselves with pure fret because some guy got bought a beer for some work he did on their code. None.
You didn't have to mention the GPL in your post. The GPL is why these ridiculous threads keep springing up, it was the GPL and the failure to adhere to it, that got Feeyo canned.
People with your attitude toward community development have no place on these forums. Kindly take the door that has a Feeyo shaped hole in it.
Click to expand...
Click to collapse
I think the problem here is your attitude, you seem to think you own the place. I am free to stay here as I wish as far as I know. I also don't believe you are reading my posts correctly as you seem to think I am against community programming which is further from the truth.
I never said I wouldn't share. I wouldn't share with you. I think community programming is great all things being equal. It seems to me that the hero community here is terrible right now and thus I wouldn't help it.
Getting people banned definitely isn't making you friends either. I honestly never saw you wanting to work with feeyo only to get at his work.
I would have no problem helping out trying to get android to work on the Xperia X1 and supplying my source code as that is a true example of people working together.
Hacre said:
My first four or five requests were incredibly polite. There were a plethora of polite request the first time he pulled this stunt too. My reason for asking was irrelevant. However my reason for asking for those particular sources, were twofold:
1: I didn't believe it.
2: If it was true then the community should damn well get access to it so we as a group can get it up to full working order so that EVERY ROM DEVELOPER can make use of it.
Taken over? What? I now don't believe that you're a developer, at least nothing outside pointing and clicking in a GUI based programming tool in some office somewhere, because you clearly have no idea of what collaborative development is. You cannot shut anyone, ANYONE, out of a GPL project, that's the whole frigging point. See my signature? Source code. Source code anyone can take and modify. Source code people are welcome to change, fix, port, patch and if they want to, submit a pull request so I can merge those fixes in.
Click the link. Follow the fork tree. Observe the magic as my changes move upstream to the original cyanogenmod + Hero kernel. Observe further magic as changes they make merge their way down into my kernel. Yeah I/we are really all about shutting people out.
Stop trolling.
Click to expand...
Click to collapse
That's not what I mean by shutting people out. I'm not trolling but replying to your false accusations.
You are also trying to personally discredit me by calling me a point and click GUI programmer which is below the belt. You know nothing about me.
What I mean is, working together as these roms are virtually the same project is about communicating. Something that would not have happened and does in a real collaborative effort.
I'm sick of this thread and having to defend myself because you fail to understand what working together really means. And no it's not just following rules. It's obvious you aren't a professional programmer. People skills and management are just as important as being able to program and that is the point I am trying to get at.
I think you've formed your opinion and regardless of how many times Hacre blows your point out of the water, your not going to be swayed are you. He shouldn't even have to explain himself to you, every point had been covered in the other fan threads already.
Sent from my HTC Hero using XDA App
Landed here from the "Custom Roms" link on the XDA forums. What exactly is Paranoid Android? Could there be a sticky for users new to it? Perhaps with some reason on why this ROM is awesome, like CM's "Why Mod?" page?
I haven't found any information *about* this ROM on paranoidandroid.co, and I'm not the only one who's confused.
http://forum.xda-developers.com/showthread.php?t=2583582
#stayparanoid
Pirateghost said:
http://forum.xda-developers.com/showthread.php?t=2583582
#stayparanoid
Click to expand...
Click to collapse
Sadly, that's only the change log. No answers to the question in the first post. Anyone? I'm curious too!
djgebel said:
Sadly, that's only the change log. No answers to the question in the first post. Anyone? I'm curious too!
Click to expand...
Click to collapse
The change log thread contains a list of all features. Period. What more do you need? Use this ROM and you will increase inches? Get more women?
#stayparanoid
Summarize what the ROM is about
Pirateghost said:
The change log thread contains a list of all features. Period. What more do you need? Use this ROM and you will increase inches? Get more women?
#stayparanoid
Click to expand...
Click to collapse
Certainly not more snark or irrelevant hashtags; more of an outsider's perspective instead of a core dev's one would help. Keep in mind that the vast majority of the users haven't a clue what Paranoid Android is, and are rather trying to decide on which ROM to flash. They're not going to compare change logs. How could we help them choose Paranoid when it's right for them?
focus of the ROM - is it theming? de-bloating? features? a mix? security, since it's called Paranoid?
features differentiating it from other ROMs (raison d'etre - why was this ROM made when there are so many out there)
device compatibility - what phones has it been tested on?
stability notes - how mature is the ROM?
what works, what doesn't
Irrelevant hash tags?
Just like the blog states,
Paranoid Android is a custom rom focused on open devices. We aim to not simply add to Android but extend it, utilizing the same design philosophies Google uses with AOSP (Android Open Source Project). You won't find a sea of options but a minimalistic user focused approach to Android.
We only support nexus, oppo, and 1+ devices.
Honestly, if a user wants to know what it is, there are dozens of android blogs and videos that have covered it all.
We don't have our website up, simply because of lack of time and manpower. Everything we have included works. We don't break devices.
And if you actually look at the change log thread it covers the features in detail, so your comment about comparing the change log is null
#stayparanoid
My apologies. Its been a rough day. I will post something more coherent after I recover from today's events
#stayparanoid
Actually that changelog thread has detailed descriptions of each feature they added to AOSP.
Not only the version-to-version changes.
Those feature descriptions are detailed. Not big words but rather a what-you-get. Clear and detailed.
I say that is the most usable description about a custom ROM. Thanks for the PA team!
Sent from XT910 running AOSPAL
Pirateghost said:
We only support nexus, oppo, and 1+ devices.
#stayparanoid
Click to expand...
Click to collapse
Not to forget the official unofficial legacy group over on G+ haha ?☺
#LegacyRocks
Sent from my Paranoid Bionic
1+ models supported?
Pirateghost said:
Irrelevant hash tags?
Just like the blog states,
....
We only support nexus, oppo, and 1+ devices.
...
Click to expand...
Click to collapse
1+ Wich models are 1+?
I get a bit confused
http://www.gsmarena.com/htc-phones-45.php
HTC list:
One E8 CDMA
One E8 Dual sim
One M8 CDMA
One M8 For win CDMA
One Remix
Etc...
torsoen said:
1+ Wich models are 1+?
I get a bit confused
http://www.gsmarena.com/htc-phones-45.php
HTC list:
One E8 CDMA
One E8 Dual sim
One M8 CDMA
One M8 For win CDMA
One Remix
Etc...
Click to expand...
Click to collapse
1+ is the brand, the manufacturer, the company. Their first phone is the one plus one. Let's not be dense here.
#stayparanoid
Hi OmniRom Devs,
I just want to ask, how the plans look like to offer the great OmniRom for the coming Android L Release?
Do you have already a timeline etc.?
Thanks and kind regards,
Chris
cnexus4 said:
Hi OmniRom Devs,
I just want to ask, how the plans look like to offer the great OmniRom for the coming Android L Release?
Do you have already a timeline etc.?
Thanks and kind regards,
Chris
Click to expand...
Click to collapse
Initial release on Bloomsday 2015, final stable release Dismember 2016.
Pray tell me, how dafuq do you expect anyone to give you any information on the timeline when nobody has seen the L sauce code, mainly because it hasn't been yet released?
You think that Omni team is clairvoyant or something?
God must love intellectually challenged people, he created so many of them.
chasmodo said:
Initial release on Bloomsday 2015, final stable release Dismember 2016.
Pray tell me, how dafuq do you expect anyone to give you any information on the timeline when nobody has seen the L sauce code, mainly because it hasn't been yet released?
You think that Omni team is clairvoyant or something?
God must love intellectually challenged people, he created so many of them.
Click to expand...
Click to collapse
Thanks for the friendly answer.
As I'm not a developer and have no glue how it works with android but I like OmniRom very much, I asked myself what's the strategy of this rom.
I don't want to be a stupid user - I want to understand also the backgrounds.
chasmodo said:
Initial release on Bloomsday 2015, final stable release Dismember 2016.
Pray tell me, how dafuq do you expect anyone to give you any information on the timeline when nobody has seen the L sauce code, mainly because it hasn't been yet released?
You think that Omni team is clairvoyant or something?
God must love intellectually challenged people, he created so many of them.
Click to expand...
Click to collapse
Also, this question has been answered before.
And as you hinted, "we won't have the slightest clue until AOSP source drops, and we have no idea when that will happen"
Absolute earliest for more news is November 3 - but sometimes AOSP source can take 1-2 weeks or more after the first OTAs start rolling out.
We won't have any clue how much work is going to be needed until the source drops. But I expect that this integration cycle is going to be a ***** - LOTS is changing. We'll pretty much have to redo UI/UX stuff for example. Kinda reminds me of when ICS first dropped.
cnexus4 said:
Thanks for the friendly answer.
As I'm not a developer and have no glue how it works with android but I like OmniRom very much, I asked myself what's the strategy of this rom.
I don't want to be a stupid user - I want to understand also the backgrounds.
Click to expand...
Click to collapse
This is a developers forum! If you aren't one, then your comments are probably not appreciated!
Petrus44 said:
This is a developers forum! If you aren't one, then your comments are probably not appreciated!
Click to expand...
Click to collapse
Everybody has to start somewhere...and this is a Q&A forum, where better to ask a question?
Be nice.
Petrus44 said:
This is a developers forum! If you aren't one, then your comments are probably not appreciated!
Click to expand...
Click to collapse
Time to work on your people skills.
Entropy512 said:
Also, this question has been answered before.
And as you hinted, "we won't have the slightest clue until AOSP source drops, and we have no idea when that will happen"
Absolute earliest for more news is November 3 - but sometimes AOSP source can take 1-2 weeks or more after the first OTAs start rolling out.
We won't have any clue how much work is going to be needed until the source drops. But I expect that this integration cycle is going to be a ***** - LOTS is changing. We'll pretty much have to redo UI/UX stuff for example. Kinda reminds me of when ICS first dropped.
Click to expand...
Click to collapse
Hope that google launches the source tomorrow. I want so bad to test the new Android.
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
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
apollus said:
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Thundery Steak said:
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Click to expand...
Click to collapse
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
apollus said:
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
Click to expand...
Click to collapse
I would really try not to do it on OS X. You need a proper Linux distribution to use, seeing as you're going to be following HADK very closely. It's not doable on OS X system and will never be. You require a Linux system to build another Linux system. If you went through HADK multiple times, you would know this.
I see why you think that OSX and Linux are alike, but they're really not, even when they are both UNIX systems. OS X is bastardized UNIX system and doesn't contain the GNU toolchain and the only thing it shares with Linux is the UNIX core.
Thundery Steak said:
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you..
Click to expand...
Click to collapse
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
mal-, how is your port of sailfish for the xperia pro working out?
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Thundery Steak said:
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Click to expand...
Click to collapse
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
apollus said:
mal-, how is your port of sailfish for the xperia pro working out?
Click to expand...
Click to collapse
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
mal- said:
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
Click to expand...
Click to collapse
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know...
I'm probably gonna end up putting fedora on this machine and start trying to learn to use linux (to port). Will be taking a UNIX/Linux intro class soon anyway, so that will come handy.
I am really sick and tired of boring old android and I think the effort to get Sailfish is well worth it... Gonna keep checking into freenode to see if people mention the Z3C.
Mal, thanks for your posts.
apollus said:
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know.
Click to expand...
Click to collapse
It depends on the person doing the porting at how early stage they add the information to the wiki page. Some do it very early some wait until it's reasonably usable. Of course it would be nice to have information about all ongoing porting activity.