Database Users

How about a Read-Only" forum for the Devs?

I have no idea where this should be posted, but since I have a Vibrant, and I know there is a lot of development going on with that platform, I figured I may as well post it here. I actually suggested this in the Bionix thread, but it got buried in all the other chatter pretty quickly. Hence, the reason for this post.
I think it would be great if the active devs here had read-only forums where they could post updates on their development efforts. That way people (non-devs mostly) could subscribe to those threads and get notifications whenever they post something. The ROM threads get so big so fast, it is hard to keep up without reading them several times a day (heck, several times an hour!).
This would require the admins here to set up the forum and grant editing rights to the active devs. Then a process would have to be developed to decide when new devs could be added to the list. In my mind, the way I envision this working is there would be one forum (call it "Developer's Corner" or something like that) and in it would be different threads for each development project. You subscribe to the threads that interest you and BAM, you are getting notifications from the forum when the devs post something there.
Skip

Devs rely on users to post bugs so they can fix them. How would this be possible with such a system?

...by sending bugs via PM to the dev?

ronin4740 said:
...by sending bugs via PM to the dev?
Click to expand...
Click to collapse
Why would you do that? Just use bug tracker on Google projects, it is far more organized e.g. http://code.google.com/p/cyanogenmod/issues/list
The idea of a read-only forum is just awful. If you want to follow the developer's progress then follow them on Twitter. You don't have to read every post, use the search functionality WITHIN that thread to search only in that thread to look for what you desire to find.

The real solution is to post a separate thread for each release. That way you know that everything in that thread is pertinent to that release and aren't looking through old replies that don't even matter anymore.
Sent from my SGH-T959 using XDA App

richan90 said:
Devs rely on users to post bugs so they can fix them. How would this be possible with such a system?
Click to expand...
Click to collapse
There would still be open forums (the ones that already exist) in which people will be able to post questions, bugs, etc.
zephiK said:
Why would you do that? Just use bug tracker on Google projects, it is far more organized e.g. http://code.google.com/p/cyanogenmod/issues/list
The idea of a read-only forum is just awful. If you want to follow the developer's progress then follow them on Twitter. You don't have to read every post, use the search functionality WITHIN that thread to search only in that thread to look for what you desire to find.
Click to expand...
Click to collapse
I didn't know anyone here was using the G bug tracker. That is a good idea.
As for using twitter, I am sad to admit that while I use twitter, I hadn't thought of following the devs there. I will take care of that today.
kangxi said:
The real solution is to post a separate thread for each release. That way you know that everything in that thread is pertinent to that release and aren't looking through old replies that don't even matter anymore.
Click to expand...
Click to collapse
This is also a very good point. The differences between some of the different revisions is quite drastic, and having all of the revisions in one thread is counter-productive.
The bottom line here is the current method creates one big mess and there is clearly room for improvement. I think if the devs had a way of posting announcements for which users can opt-in to receive notification when those announcements are posted, then that solves one small portion of the mess.
Would that be so bad?

You have just described Twitter.

I was under the impression that one dev didn't want to know about bugs in their roms inside of their threads.

heygrl said:
I was under the impression that one dev didn't want to know about bugs in their roms inside of their threads.
Click to expand...
Click to collapse
Only if it's super buggy and they know it is buggy, no reason to post bugs then.
Back on topic: Your idea got buried because it sucked. People read through all that, not everyone, but some do.

heygrl said:
I was under the impression that one dev didn't want to know about bugs in their roms inside of their threads.
Click to expand...
Click to collapse
Often when someone posts something that they already know is full of bugs they will ask people to not post about them, just because they are already known issues.

Al right. I guess it's just me then.
Back to our regularly scheduled programming.

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!

[REF]Galaxy SII ICS CM9 Progression Updates Here

Right thread is for updates and news in regarding how the progress of the port is coming along for the ICS to our Galaxy SII. Updates will be coming from directly from teamhacksung. I will be staying intouch with Codeworkx and will be providing the latest feedback he gives me to share on the thread with the rest of the community here.
Twitter Link for more news:
https://twitter.com/xplodwild
https://twitter.com/#!/SamMobiles
https://twitter.com/#!/Jeefke/ics-aosp-sgs2
What's working
Display
Touchscreen
RIL
Audio
Wifi
GPS
Sensors (needs tweaking)
SD Cards
Bluetooth
HWComposer (strange things are going on)
What’s not working?
Microphone on Phone Calls (trying to write a HAL from scratch)
Camera
Video Recording
Video Codecs
Device Encryption
USB Sharing (kernel update needed)
More Updates-12.12.11
Quote from the man himself:
Now with much more IceCream on my Sandwich!
Let me have a look at my visionarys orb.
I can see…
- Kernel 3.0.9
- New RIL (doesn’t work with old modem firmwares)
- TouchWiz (i still hate it, doesn’t feel good, stock aosp ics feels much better)
- Opencore is finally gone
- looks cleaner under the hood
- still old alsa, not the new tinyalsa
- users won’t be impressed
Now let me watch on my device…
- aosp framework
- graphics seems to work good
- it has sound, but cannot test mic beacuse of ril problems
- ril isn’t working very good, crashing all the time. might need to add a new samsung ril class like in the past
- gps seems to work
- hwcomposer is running
- camera is running
- bluetooth works
- wifi works
- sensors aren’t working yet, but should be no problem
- usb sharing works
Ok, too much said already.
Having Kernel sources would make it much easier, but that’s probably far away.
Stay tuned! Maybe we get ril fixed in a few days then we got something really amazing and clean for you.
More Updates 12/12/2011:
Today we could spend some more time to fiddle with this stuff.
RIL is very unstable, even on the leak.
It’s not usable. Probably have to wait for a newer leak. :-(
My o2 card doesn’t work, my vodafone card works.
Might be NITZ related.
Some little bugs here and there like unamplifed haptic feedback, broken sdcards and some other little things.
Sound is working, Mic is working , Camera is working, Wifi is working, Bluetooth is working, HWComposer, TVOutService is up…
To fix every little bug we need kernel sources for sure. So probably in january 2012.
If we can get RIL stable, we might release a aosp/cm9 build for you.
But don’t point at us if we don’t.
Latest from the team...Stay tuned for more as i get it...
Developers working on the project:
atinm
Adam G
codeworkx
coolya
GuiPer
nebkat
Unhelpful
xplodwild
Thanks:
To teamhacksung for working their magic to bring CM9 to us.
Codeworkx for his help in keeping this thread up to date.
And to Stylez, Conantroutman here for helping me out with previous thread and this one now.
Big thanks for the efforts of the AOSP team as well who as well started this whole project and now it is being carried on by TeamHacksung. Netchip, Yjwong, Chadouming, Biohazard and Paradoxxx deserve a mention as well because they to put a lot of effort in the project just a shame they could not carry on..So please give them thanks as well for their efforts.
Please read carefully here to:
If you don't stop annoying devs, they'll leave XDA forever. If this happens you'll never get this ICS Port onto your Phone. You have to wait for Samsung to release something which might be usable in about some Months. Start using your brains, read threads fully and understand it before you're going to add a post. And they are doing their best to get as fast as they can a stable build out to us. So we in return we can be patient and wait. All updates will be above and Codeworkx and i will bring the latest in the sticky here. Please watch here also

Latest so far from Codeworkx and the team
Since our try’s to get the microphone working on ICS using the samsung audio HAL wen’t bad, we decided to write a ICS compatible HAL from scratch. (stealing some code from the galaxy nexus)
Actually we’re able to control all ~134 mixer controls from within our HAL. We’re able to open the PCM’s and we’re able to read/write to it. The hardware dependant part is also working (e.g. telling the audio hw that we’re doing a call).
But all this doesn’t make sound working. We don’t know which mixers we have to set on which cases to get a little bit of sound, for example, out of the speaker.
The next few days will probably be wasted on figuring out which controls we have to touch at the right time.
The task is like jumping over a 100 miles height wall, because we’ve no documentation for the hardware and nobody of us knows what we’re doing. xD
But hey we’ve a damn big bulldozer. ;-)
Hope we’ve enough fuel for it to break the wall down.
Links to follow progress and ICS related stuff
http://codeworkx.de/wordpress/
Engadget ICS review. Click to read it
https://twitter.com/xplodwild
https://twitter.com/#!/SamMobiles

13/12/2011 Video Update with the latest by Ouverta
Latest video update regarding CM9
14/12/2011 New ICS leak by SamMobile:
From what you can see not really much to play with and not much to get excited about. I personally was going to download and see what it feels like but it just reminds me of the alpha builds...For me it is a miss. Views from people who have downloaded it though please post and let me know what you thought of this

[5/12/2011]More Updates.
New state -> waiting
Opensource Audio HAL:
Without any documentation or hints it’s a try & error task for some weeks.
Using Audio Blobs:
Not really possible because big S broke the ABI.
Did a lot of hacking on it, but it’s hopeless.
USB Gadget:
Big S touched the original Google USB Gadget code and made it a mess. It’s hooked up to touchscreen, charger, battery, mhl and probably some more stuff.
Not possible to implement the new USB Gadget required for USB Sharing without spending lot of time on it to clean up this disaster.
Graphics:
Nebkat and xplodwild fixed the graphics corruption on rotation and crt-off effects.
New state -> waiting for new kernel sources and a ICS leak.
Extended state -> We are very pissed about big S.
If big S is not going to be more cooperative, next Device will be a Google Device.
So far this is the latest updates by the team. It is kinda stop and start and very frustrating from what you can see but the team is trying so fingers crossed. Show support and patience and i am sure our patience will be rewarded

Thread is open to allow OP to edit posts.
Do not reply to thread and if you do have anything to add PM Matriak31
All posts will be removed and if needed infractions will be placed.​

stylez said:
Thread is open to allow OP to edit posts.
Do not reply to thread and if you do have anything to add PM Matriak31
All posts will be removed and if needed infractions will be placed.​
Click to expand...
Click to collapse
justmarcos12 said:
respectfully great job Matriak31!
Click to expand...
Click to collapse
ksantoshh said:
Good to get a taste of ICS
Click to expand...
Click to collapse
mp1806 said:
ice cream sendwich
Click to expand...
Click to collapse
What about the above post did you not understand.............

More updates...12/12/2011
Now with much more IceCream on my Sandwich!
Let me have a look at my visionarys orb.
I can see…
- Kernel 3.0.9
- New RIL (doesn’t work with old modem firmwares)
- TouchWiz (i still hate it, doesn’t feel good, stock aosp ics feels much better)
- Opencore is finally gone
- looks cleaner under the hood
- still old alsa, not the new tinyalsa
- users won’t be impressed
Now let me watch on my device…
- aosp framework
- graphics seems to work good
- it has sound, but cannot test mic beacuse of ril problems
- ril isn’t working very good, crashing all the time. might need to add a new samsung ril class like in the past
- gps seems to work
- hwcomposer is running
- camera is running
- bluetooth works
- wifi works
- sensors aren’t working yet, but should be no problem
- usb sharing works
Quote from the man himself:
Having Kernel sources would make it much easier, but that’s probably far away.
Stay tuned! Maybe we get ril fixed in a few days then we got something really amazing and clean for you.
More Updates 12/12/2011:
Today we could spend some more time to fiddle with this stuff.
RIL is very unstable, even on the leak.
It’s not usable. Probably have to wait for a newer leak. :-(
My o2 card doesn’t work, my vodafone card works.
Might be NITZ related.
Some little bugs here and there like unamplifed haptic feedback, broken sdcards and some other little things.
Sound is working, Mic is working , Camera is working, Wifi is working, Bluetooth is working, HWComposer, TVOutService is up…
To fix every little bug we need kernel sources for sure. So probably in january 2012.
If we can get RIL stable, we might release a aosp/cm9 build for you.
But don’t point at us if we don’t.
Latest from the team...Stay tuned for more as i get it...

New Links from SamMobiles..ICS leak maybe next week
https://twitter.com/#!/SamMobiles/status/145562676972621824
https://twitter.com/#!/SamMobiles/status/145602356896210945
For those who didn’t know yet:
The Guys from SamMobiles got a first ICS leak for the I9100 (with TouchWiz), but it looks like they don’t want to share before their new site gets online.
This means we’ll have the leak probably next week.
We asked them about just getting the blobs we need, but no chance.
They don’t want to share anything.
But hey, it’s just one week more. ;-)
Latest info from Codeworkx.

krabman said:
I'm going to go ahead and report this to admin. The purpose of this thread is the ICS team updates alone and its reason for being stickied. The commentary can stay down in general where as you all know a thread is ongoing. Then this and other posts not related to the thread purpose can be deleted and we can all go through just a few posts to find out the latest on the team progress. A condition which I believe many of us will prefer to allowing this to become an open thread.
Click to expand...
Click to collapse
The purpose of opening this up was to prevent 69079875439879 different threads being opened in the general section offering up such revelations as;
Idiot Number 1 said:
"OMG I cant waitz 4 teh ICS!!!!! "
Click to expand...
Click to collapse
And the timeless......
Idiot Number 2 said:
"Where I can haz DL linkzz.... plsszzzzz????"
Click to expand...
Click to collapse
Just check the OP for updates, don't read the thread....................

conantroutman said:
The purpose of opening this up was to prevent 69079875439879 different threads being opened in the general section offering up such revelations as;
And the timeless......
Just check the OP for updates, don't read the thread....................
Click to expand...
Click to collapse
And just to add it's an open sticky as already stated so as the OP can edit posts permissions wouldn't allow the edits on closed thread....
Most users respect wishes of OP and also mods but some can't read a small request! Its simple as if users can't respect a request and feel the need to increase mods time via posting then infractions will be placed.
Everything is set out in an easy laid FAQ info and being updated regularly as already stated if you have info PM OP to which even the link previous goes straight to PM write.. hay can't be that hard.
Think I need say no more...
Thx to users who can follow simple guidelines
Sent from my GT-I9100 using Tapatalk

conantroutman said:
The purpose of opening this up was to prevent 69079875439879 different threads being opened in the general section offering up such revelations as;
And the timeless......
Just check the OP for updates, don't read the thread....................
Click to expand...
Click to collapse
stylez said:
And just to add it's an open sticky as already stated so as the OP can edit posts permissions wouldn't allow the edits on closed thread....
Most users respect wishes of OP and also mods but some can't read a small request! Its simple as if users can't respect a request and feel the need to increase mods time via posting then infractions will be placed.
Everything is set out in an easy laid FAQ info and being updated regularly as already stated if you have info PM OP to which even the link previous goes straight to PM write.. hay can't be that hard.
Think I need say no more...
Thx to users who can follow simple guidelines
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry i had to say this but i love you two...You make my life a whole lot easier..And to everyone else..What they said

Hey matriak.
Sorry to say but i really don't like the post about sammobile. They said different times why they can't share it at the moment and have to wait this week. You shouldn't write that they don't want to. Their reason to wait is good enough.
Sent from my GT-I9100

rauschkugl said:
Hey matriak.
Sorry to say but i really don't like the post about sammobile. They said different times why they can't share it at the moment and have to wait this week. You shouldn't write that they don't want to. Their reason to wait is good enough.
Sent from my GT-I9100
Click to expand...
Click to collapse
Hey buddy. I respect your opinion i do but i have to respect codeworkx also for his involvement also in his project and this thread is his idea and mainly mine. I report news and updates as they are and that is how i read them. I will try and change it but for now that stays i am sorry
Sent from my GT-I9100 using xda premium

Matriak31 said:
Hey buddy. I respect your opinion i do but i have to respect codeworkx also for his involvement also in his project and this thread is his idea and mainly mine. I report news and updates as they are and that is how i read them. I will try and change it but for now that stays i am sorry
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No problem. Just wanted to tell you that they have a good reason to wait. Because i think we all want to have leaks in the future and not wait till samsung officially releases their stuff. I'm on my mobile today so i can't link you the corresponding post but i can send you the link to it this evening if you want.
Because i think it sounded not so fair and sammobile also does a lot for us.
Edit: forum.xda-developers.com/showpost.php?p=20190303&postcount=62
Sent from my GT-I9100

Cobesz said:
seriously dude? Think they didn't try that?
Google changed the android framework dramaticly, this is why alot of GB sources do not work with ICS.
Click to expand...
Click to collapse
Plus you do not need to be a genius to figure out that GB and ICS is totally different kettle of fish

Cobesz said:
Ain't you supposed to be relaxing on your vacation?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I am...But can't blame me i got the bloody xda bug..I like to keep up to date...

Matriak31 said:
Now with much more IceCream on my Sandwich!
Let me have a look at my visionarys orb.
I can see…
- Kernel 3.0.9
- New RIL (doesn’t work with old modem firmwares)
- TouchWiz (i still hate it, doesn’t feel good, stock aosp ics feels much better)
- Opencore is finally gone
- looks cleaner under the hood
- still old alsa, not the new tinyalsa
- users won’t be impressed
Now let me watch on my device…
- aosp framework
- graphics seems to work good
- it has sound, but cannot test mic beacuse of ril problems
- ril isn’t working very good, crashing all the time. might need to add a new samsung ril class like in the past
- gps seems to work
- hwcomposer is running
- camera is running
- bluetooth works
- wifi works
- sensors aren’t working yet, but should be no problem
- usb sharing works
Quote from the man himself:
Having Kernel sources would make it much easier, but that’s probably far away.
Stay tuned! Maybe we get ril fixed in a few days then we got something really amazing and clean for you.
Latest from the team...Stay tuned for more as i get it...
Click to expand...
Click to collapse
I didnt really get what this post means it's kind of murky...
Please Matriak can you explain what this post means!
Will the Codeworkx / CyanogenMod / SamMobile versions have TouchWiz?
Will it become easier for them when SamMobile releases the leaked version?
Did they get rid of those slimy soft keys at the bottom?
Why "users wont be impressed"?
Are sensors a tough problem to fix?
Ril?
.
.
.
.
.
& etc.
You guys are the best!
Thanks fo all the hard work!

Net.silb said:
I didnt really get what this post means it's kind of murky...
Please Matriak can you explain what this post means!
Will the Codeworkx / CyanogenMod / SamMobile versions have TouchWiz?
Will it become easier for them when SamMobile releases the leaked version?
Did they get rid of those slimy soft keys at the bottom?
Why "users wont be impressed"?
Are sensors a tough problem to fix?
Ril?
.
.
.
.
.
& etc.
You guys are the best!
Thanks fo all the hard work!
Click to expand...
Click to collapse
No it won't have TW. Codeworkx is talking about the leaked beta Samsung rom. Users won't be impressed because the rom is not done and it's clearly unstable. The problems he is referring to are all in the Samsung rom.
However, Codeworkx can use some parts of this rom the fix things in the AOSP rom they are building.

Net.silb said:
I didnt really get what this post means it's kind of murky...
Will the Codeworkx / CyanogenMod / SamMobile versions have TouchWiz?
Click to expand...
Click to collapse
Even I can answer some of these...
CM won't have TW, no way. But the version from sammobile will have TW as it's a Samsung based one.
Net.silb said:
Will it become easier for them when SamMobile releases the leaked version?
Click to expand...
Click to collapse
Maybe. I ain't interested in that anyway.
Net.silb said:
Why "users wont be impressed"?
Click to expand...
Click to collapse
When Codecworkx said that he should've mentioned why!! Anyway, sammobile posted yesterday that 'this thing is nowhere near finished', so you know what I mean.
One thing I don't understand, if it's a BETA then why so much disappointment? Maybe Alpha would be a proper name! Can't say...

Net.silb said:
I didnt really get what this post means it's kind of murky...
Please Matriak can you explain what this post means!
Will the Codeworkx / CyanogenMod / SamMobile versions have TouchWiz?
Will it become easier for them when SamMobile releases the leaked version?
Did they get rid of those slimy soft keys at the bottom?
Why "users wont be impressed"?
Are sensors a tough problem to fix?
Ril?
.
.
.
.
.
& etc.
You guys are the best!
Thanks fo all the hard work!
Click to expand...
Click to collapse
Do not know at the moment what SamMobile leak is as they have not released it just yet. Codeworkx and team have stated as above what they have done so far and what they have working.
For better explanations visit his blog. As it would be better explained there. I post as i see and try and answer as simple as i can. But for me it is pretty clear what is stated above so hopefully this is helpful enough..
Soft keys will be gone..Do not forget that we are using a different product than the galaxy nexus

Assemble Dev Team for an ICS ROM

As our device is dying in support I feel that we need to develop a large development team (10+ people) that will work on ICS for our gtablet. I mean after all our device is capable of running it ( Tegra 250). If you would like to be part of this team shoot an email to [email protected] explaining why you want to be part of this team and what you can contribute. Thank you.

You know that you need a new kernel for ICS to work properly right? Ch3vr0n5 and dpw13 are currently working on it over at slatedroid.

lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis

texasice said:
lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis
Click to expand...
Click to collapse
guys,
pm jazzruby, tek112 or fosser2, ch3vron..they are also over @ slatedroid viewsonic gtablet forum..
they have been working on a kernel with hw accel for HC3.2 and ICS. There are been some teaser pics by fosser with ics running on his gtablet.
I'm sure they could use your help...
kernel dev in the gtablet laboratory forum as well.

Cyanogen: Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. (12/2/2011)
Click to expand...
Click to collapse
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.

sjmoreno said:
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.
Click to expand...
Click to collapse
uhm based on what you quote nothing is said there we dont have qsd in our gtabs...

If anyone is interested and has dev experience shoot me a pm and i'll get you up to date. thanks

Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever

texasice said:
Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever
Click to expand...
Click to collapse
I appreciate that you didn't post the link to this, and please anyone else who "finds" this build (yes its out there) please do not post it anywhere either. It is extremely beta and has many problems (to the point where you would have to open your tablet to push the internal reset button). Thanks

i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev

Notion ink adam is getting official ICS, I suppose that will help a lot?

iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
I realize you're just trying to show people where it is, but if the devs don't want you pouring out THEIR work to the world just yet, I think it's best to listen.

iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
There are good reasons why the devs don't want this posted. Its not to spite anyone or rub it in their faces. 1 they don't want to be liable for someone elses damaged tablet, 2 do you know if the voltage regulators aren't correct it could fry your gtablet permanently, 3 they're a good hard working group who is doing this for zero dollars in their spare personal time and only want to put out a good working product. Have a little respect for their wishes. Be warned that alpha build could permanent damage your gtablet.

iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.

fosser2 said:
Well aren't you cool, learning how to use google and
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Kids.....they think they know everything! Haha, just kidding but hopefully maybe people understand why now. Im pumped about the HC release! Im tired of froyo and can't wait to play the THD games that required 2.3+. Thank you and the rest of the team so much for your hard work. Im not a programmer but im going to start digging for the technical info you need for the camera.

fosser2 said:
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Thanks to all the Devs working on this stuff for us! That said if you guys need any testing done just shoot me a PM, I rarely use my tablet any more and have cracked it open plenty of times for other hardware testing. I don't have much time to work on software anymore, but am more than willing to test stuff for you if you don't wish to risk your tablets. Again thanks for all your work.
Sent from my Nexus S using XDA App

MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.

Closing this thread - this is just getting out of hand folks.

[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