Database Users

Devs, Please don't hide your Known Issues

I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.

I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.

Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate

They don't care to list them. It's beneath some of them.

Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!

If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.

The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.

I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene

kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.

Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"

chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.

OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?

swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.

So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.

Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.

Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---

N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!

Oppo Find 5 Needs Developer Help, Donations Will Be Given, Help Make the Oppo Find 5

Oppo Find 5 Needs Developer Help, Donations Will Be Given, Help Make the Oppo Find 5 A Beast Modded With, Roms, Kernels, TWRPs, CWMs, We Need Someone Who Can Do This If You Are Willing To Donate Time To Oppo Find 5, And We Donate CASH.
I know that paperWastage and drewX2 have been doing some awesome work on the Oppo Find 5(OF5), but they cant do everything by themselves. TWRP and CMW are already working, but need updateded I think so. So I came up with an idea last night that would take some of the stress off their back and maybe someone could help them get things going a little faster, of course I will donate and I’m sure other will also. If my idea sounds stupid just delete this thread, I’m just trying to get as much help as we can on development with this device since it has the same CPU and GPU as most devices out today the quad core - S4Pro. The phone cost $499 and if we all pitch in a few bucks we could have the money for this phone to give to a developer who has worked with the S4Pro chipset before and knows most of how it operates and they will know what they are doing with the S4ProChipset. If this sounds like a good idea, I will start off by donating $20 so that that we can order this phone and send it to the developer of our choice. We need a really good dev. that isn’t working on anything right now and can spend some time turning our Oppo Find 5 into a beast.
If everyone agrees to donate a little as you want anything will help we only need $400to get this phone , I have saw more than that raised in one day. I don’t want to be in control of the money someone with a little ore authority here at XDA can do that. So does this sound like a good Idea, If so start getting in contact with some of the best developers that you know and let them know we got a free phone waiting on them and other donation for time and effort.
I WILL ADD NAME IF YOU ANT ME TOO - LIST OF DEVELOPERS. I will add others as people get in touch with the me or other developers and give them either give a YES or NO for committing time to the Oppo Find 5. When list is made we will all vote of which developers to send the phone out to so they can begin development.
1. drewX2 - He is working on Mod of CM10 and he does not even own the Oppo Find 5. Definitely on the top of my lists CM10 WORK http://forum.xda-developers.com/showthread.php?t=2197147
2. paperWastage- I think he has Oppo Find 5 already though still dedicating a lot of time and a beer of coffee would be nice.
3.
4.
5.
6.
7.
8.
9.
10.
If you want your name on the list put in post and I will add it, I only made 10 for now if we need more I will add them later. Hopefully this is something that people consider; you don’t have to donate all kinds of money even $5 will work, Hell $3 will work, anything to get us closer to that $400. Everyone does not need to donate like some people will and donate $20 or $30 dollars. Because right now we need some serious help paperWastage and drewX2 have been doing some awesome work, a couple people can’t do this all by themselves, and if we want to make this phone worth every cent we spent for it, we really need to make this a nice phone that we can flash Roms, Kernels, and all the good stuff then this is a good opportunity to make it happen.

I'd buy a phone for a Dev. I think Entropy512,KamMa NODO-GT and XpLoDWilD already have the phone though....I haven't had a S4 Pro phone before so I don't know any experienced devs,but count me in for $10 a month.

I want to contribute whith my donations.
I´ve already make one to Kamma AOSP´s proyect
My next donation will go to Xplodwild when he launch his new builds of CM10.1

Donations do nothing but fragment the community in almost all situations. In fact, more often than not, users don't even remotely get their money's worth from device donations to developers.
Hell, in my opinion even teamhacksung device donations for CM bringups were bad ideas in the long run - they caused developers who had potential to achieve something to just say "****it, teamhacksung is here, I'll just kang".
If the device is still in a bad state after 4-5 months - yeah, then maybe it's time to start considering donation drives.
But a device that has only had kernel source available for 2-3 weeks? Hell no.
It often takes MONTHS to properly learn a device's ins and outs. You can't just throw devices at developers and immediately have good stuff overnight. More often than not, developers who take donations in advance will just take donations for another device in a month or two - I've seen it all the time.
Don't donate to encourage work to be done - only donate for work that has already been done.
And I'll be blunt - drewx2 should never have created a CM thread here. Blind development almost never works and fails spectactularly instead, especially for a CM bringup. Blind development only works for devices that are 99% identical to one the developer owns (I777 vs. I9100, N8010 vs. N8013, I777 vs. S959G, etc.) His thread is just a donation ploy. Any maintainer with the discipline to do a bringup knows when it is NOT the time to publically release anything because it's nowhere near ready, and also knows that you do NOT do blind development for a CM bringup.

Mod please delete thread, devs should get paid after they show progress in thier work
Mod please delete this thread everything you said made since. Give donation to the people when the work is in progress and completed, and not before I always give donations for devs efforts but you have taught me a lesson.
You know what you are doing Entropy512, you been around awhile, and I wish so bad you had this device even if you would work on it. I really like the phone its badass and its not all that buggy it just needs some kinks ironed out and in my opinion some kernels because this kernel is not running like it should. We need a kernel so we can play with and overclock or underclock with good governors to ramp it up or down.Come on down faux and show-p plus many more.

Can't we all just get along? Work together already.

Okay, enough is enough. This thread has just turned into a playground, as well as being pointless and jumping the gun in the first place. At everyone involved in the arguing, you really do need to stop doing it publicly. At the OP, be patient and see what the developers bring.
Thread closed at OP request.

Galaxy Note 10.1 2014 Exynos Developer Device

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 ?

Development for Z2 tablet

I have created this thread to prevent spamming the Android Development forum.
Starting point: http://forum.xda-developers.com/showpost.php?p=58117080&postcount=93
Originally Posted by BabelHuber
I honestly do not understand your whining here: We have:
- Pre-rooted stock ROMs for WIFI and LTE
- CM11 and CM12 for WIFI and LTE
- PAC ROM (4.4 and 5.0) for WIFI and LTE
- AOSP for LTE (WIFI will follow according to the guys from FreeXPERIA)
So nothing is "dead".
The Z2 tablet is not a best seller, it is a high-end Android tablet with a very limited user base. Of course devices which have sold an order of magnitude more like the Samsung Galaxy S5 or the HTC One M8 attract more developers, but then look at the forums for the Galaxy S5 Mini, where there is hardly any development at all. Compared to such devices we do very well here.
I personally am glad that we have good developers supporting our tablet and a range of custom ROMs to choose from and I am thankful for the ROMs we have and for the work the developers spend in their free time.
Finally, this is XDA here - if you think there are too few ROMs here feel free to make your own one instead of alienating the developers we have by complaining about their work.
Click to expand...
Click to collapse
Hi,
Waoh !
OK, sorry... I take it all back.
Did not thought my post would suggest such vehement reaction.
In fact, what did I wrote ?
Simply that on the whole channel dedicated to "Z2 Tablet Android development" there has not been a single post in over 3 weeks...
Which makes me fear that development is not really alive for a device I really like.
Does it deserve such reaction ?
Maybe. But I beg to differ...
I am not whining, I am not complaining... I was just stating.
That makes a difference to me. Maybe not to you...
Regards.
Click to expand...
Click to collapse
See, CM12 and Lollipop AOSP were updated just 2 days ago, on 2015-01-10. PAC was updated today, before it was updated on 2015-01-05. Yesterday, a new pre-rooted stock ROM for the SGP521 was posted.
Yet you ask if development is dead.
In my opinion, this is insulting the developers who do the work for us - for free, mind you!
I do not want to start a flame war or a non-technology-related discussion here. I merely want to point out that I do not share your view and that I am thankful for the ROMs we have.
Also I want to point out that I appreciate the work the developers do - we already have 'lost' a developer here in this forum who was alienated by some comments from certain members, and I think this shouldn't be repeated.
Hence I felt that I have to reply to your post to make the developers know that there are members on this board who do not share your view. Usually I simply ignore such posts to prevent spamming the forums, but I think your repeated complaints (no Apps2SD, no 4.4 AOSP, no new developments) warrant a reply.

BabelHuber said:
I have created this thread to prevent spamming the Android Development forum.
Starting point: http://forum.xda-developers.com/showpost.php?p=58117080&postcount=93
See, CM12 and Lollipop AOSP were updated just 2 days ago, on 2015-01-10. PAC was updated today, before it was updated on 2015-01-05. Yesterday, a new pre-rooted stock ROM for the SGP521 was posted.
Yet you ask if development is dead.
In my opinion, this is insulting the developers who do the work for us - for free, mind you!
I do not want to start a flame war or a non-technology-related discussion here. I merely want to point out that I do not share your view and that I am thankful for the ROMs we have.
Also I want to point out that I appreciate the work the developers do - we already have 'lost' a developer here in this forum who was alienated by some comments from certain members, and I think this shouldn't be repeated.
Hence I felt that I have to reply to your post to make the developers know that there are members on this board who do not share your view. Usually I simply ignore such posts to prevent spamming the forums, but I think your repeated complaints (no Apps2SD, no 4.4 AOSP, no new developments) warrant a reply.
Click to expand...
Click to collapse
you are both wrong, aosp daily builds are well, everyday, same with the official cm12 since, we get official, p.s. the current recovery in cm12 doesn;t flash, you have to downgrade the boot.img every time to the one from cm11 before updating

[Great News] [Official] [CM12.1][Coming Soon]

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