Related
DEVS! Would it be possible to use a FroYo Kernel for CM7 like the Droid X Developers did?
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Original Android <3ers! said:
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Click to expand...
Click to collapse
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
daddy_droid said:
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
Click to expand...
Click to collapse
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
And queue take 3... omfg, when will people learn, this is not to debate ETA.
Original Android <3ers! said:
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
Click to expand...
Click to collapse
really not allowed to talk about that? Since when can someone else take away my free speech rights to ask when something is gonna to be released? If you dont want to answer a question for eta then just dont reply to it. After all no one is making you reply to anything.
If you HAVE NOTHING TO SHARE DONT POST IN DEVELOPMENT.
I'm trying to be honest with you and save you from being flamed. Did you even read the first post? The devs don't have the kernel source for the Epic 2.3.3 or beyond, nor do they have it for the Nexus S 4G, so until then, they have to stop developing because they cannot do ANYTHING without it. So an answer to an ETA is never.
lynyrd65 said:
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
Click to expand...
Click to collapse
I think this would be a good idea while we wait for the Kernel source actually...
nullghost mentioned that CM6 would be in the same state as CM 7. Idk why, but yea.
No no, we're saying use the FroYo Kernel for CM7!
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Darkshneider said:
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Click to expand...
Click to collapse
No.
Sent from my SPH-D700 using XDA App
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
The reason being? I dont get how theres source for 2.2 and we cant get CM6, how would 2.3 source help us get CM7 working?
And I got my answer while typing because of Deca. Thnx!
Decad3nce said:
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
Click to expand...
Click to collapse
So you don't like me?
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
I don't mind you, your motives are good, but this environment fosters redundant and pointless poo flingin'. Which usually leads to us responding with the same information, over and over.
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
Great way to lose another Dev.
Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
lynyrd65 said:
Great way to lose another Dev. Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
Click to expand...
Click to collapse
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Decad3nce said:
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Click to expand...
Click to collapse
Developers tend to support developers.
Sent from my SPH-D700 using XDA App
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
Hello everyone,
i want to open this thread because seems that the development in this forum for acer a500 ICS AOSP has been stopped.
I know that lots of people "hate" thor2002ro for not relasing source code in fact this thread is only informative for who, as me, doesn't care about having or not having source but they want to try ICS on tablet.I think that it is the right place because is a custom rom. Then, with the permissions of thor2002ro, i decide to mantain a thread on xda copying what they publish on tegraowners. I take no credit for the rom, im only a messenger for you (if you do not want it, simply dont reply) and i try to update the thread when a new alpha is done:
thor2002ro said:
this is what I got so far building the device directory for our a500...
Works:
touchscreen
sensors(all tested)
usb
internal memory
hdmi
vibration
wifi(with signal bars working)
bluetooth
2D HW accel
3D HW accel
removable storage
storage menu in settings
Data usage
Backlight adjustment
Audio & Headphone & Microphone(thanks to digetx)
Green overlay transparency fixed
Recent apps(thanks to digetx)
GPS
Automatic Backlight
To do:
Camera
Camcorder
usb sdcard access to pc
hw codecs
vpn
HDMI sound
Installing:
wipe data
install rom zip
install gapps
reboot
Click to expand...
Click to collapse
version 59
Gapps 5.3
see it on ...you know what forum
Im not responsible for damage to your device. Flash at your own risk. Don't ask for support to me because im not the developer
You're not allowed to post links to Thor's ROM's on here until he decides to comply with the GPL. Don't be surprised if your thread gets closed.
now is ok?
Someone close this please...
Sent from my A500 using xda premium
Qwallace70129 said:
Someone close this please...
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Why? now there are no direct link
I've already deleted the link and having a PM chat with OP explaining Thor's situation, i guess there is no need to start another useless flaming/trolling war.
ale.landra91 said:
Why? now there are no direct link
Click to expand...
Click to collapse
I agree with you, but technically this should be in general since you did not create it yourself. Thank you for this though.
MOD-Please move to general
ale.landra91 said:
Why? now there are no direct link
Click to expand...
Click to collapse
Might not have a link, but it still is 'condoning warez' in promoting Thor's code.
every time in acer forum is an hell in 1 year on nexus section never happened to me
Errare umanum est, perseverare autem diabolicum
Welcome to the Internet I guess then? Larger forums will of course bring many more views and opinions, just have to go with the flow.
getting over this annoying spat that doesn't help the community one bit, i just installed the new ROM (v59) and played with it. aside from it being terribly buggy on the cyanogen/trebuchet side (it keeps freezing), it's pretty fast and a bit more intuitive than honeycomb. granted, alpha development is at a point where ICS's main eyecandy options (face detection via camera, integrated data counter and what not) don't work. that's why it's an alpha. the new gapps are nice.. but having a 501 with no data connectivity means i'll be rewiping and installing any other flavour of 3.2.1 tonight.
now, that's not the community's fault, but perhaps working together more instead of bickering at each other would fix me my ICS sooner, dammit. now go make me some ice cream sammiches ..
mihnead said:
nm, op delete pls, i took a while to post and the thread was gone
getting over this annoying spat that doesn't help the community one bit, i just installed the new ROM (v59) and played with it. aside from it being terribly buggy on the cyanogen/trebuchet side (it keeps freezing), it's pretty fast and a bit more intuitive than honeycomb. granted, alpha development is at a point where ICS's main eyecandy options (face detection via camera, integrated data counter and what not) don't work. that's why it's an alpha. the new gapps are nice.. but having a 501 with no data connectivity means i'll be rewiping and installing any other flavour of 3.2.1 tonight.
now, that's not the community's fault, but perhaps working together more instead of bickering at each other would fix me my ICS sooner, dammit. now go make me some ice cream sammiches ..
Click to expand...
Click to collapse
This is what i mean...only angry people. Learn to see the good side of the work. Nobody need anger and jealousy
Sent from my A500 using Tapatalk
Ok, sorry but this thread is dangerous now.
*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA, ezet, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!
You're right and in general I agree with you but this sub-forum is only to post ROM's preferably tested and without bugs. You should move this to General section or ask to mods to do that. Blefish is working on CM 10 and we (non-developers) need to wait.
Cheers.
to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)!
[edit]
with the above said, i do not mean to discourage any further development effort on this phone..
i actually welcome such activities very much honestly..
its just that ppl should also recognise those of us who try to move forward with newer and more powerful phones..
rqmok said:
*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA ezet, possibly me, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!
Click to expand...
Click to collapse
So why don't you make Jelly bean ?
iamelton said:
to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)
Click to expand...
Click to collapse
Our main problem is the just the lack of developers as I already said before, because saying our phones is old fashioned it ain't true, for an example the Huawei Ascend G300, imo that phone is not that far away from our phone in hardware and capability (and also it was release in May of 2012), but still it already has CM9, CM10, CM10.1, thats my point of view, we can't all have the same opinion. I just don't have the skill to do such things in the Android area, if I had I would work on this awesome device.
It's not dead, but it's been on life support for a very long time, now. Blefish is the only active, transparent developer this device has going for, and even he doesn't have public releases yet and encounters numerous issues. There is no real Jellybean for this device, regardless of the fact that the hardware is capable, and so for all intents and purposes it is dead, for the time being. But that could change.
Regardless, this is a terrible thread and if you want to help you shouldn't spam this forum. There are specific forums for this sort of inane garbage.
I think it's dead anymore since we can't go through jellybean. There are only 2 person as i know who have coding knowledge;dzo and blefish.Besides we haven't seen a working wifi for jellybean both of them;so this makes the phone dead,in my view.
i think the points are quite clear now.. in android world, a phone is "dead" if there is not much active development/support for the latest updates going around (either officially or from individuals)..
[edit]
OP, just did a search and found out that u ported a xperia style rom to our phone, so that makes u a developer of this phone.. thx for the work..
(though another GB rom does not interest me that much.. )
I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800
Would just like to clarify something
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
HD2 is dead and it still has developers.
It's not developing, it's passed on. This phone is no more. It has ceased to be. It's expired and gone to meet its maker. This is a late phone. It's a stiff. Bereft of life, it rests in peace. If we haven't bought it , it would be pushing up the daisies. It's run down the curtain and joined the choir invisible. This is an ex-phone. Capisci?
rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
ok i take back my previous recognition of u as a developer.. now you are a developer-to-be for this great phone.. (honestly, no sarcasm attached.. )
and while i think u8800 is dead, u see it as a living pal.. no problem.. case closed.. (no sarcasm, again..)
now back to business.. i would very much be happy to see a jb rom created and surely would give it a try in my u8800..
i just hope u can keep this enthusiasm and keep working on this jb-rom-to-come..
honestly speaking, having enthusiasm on something and start working on it are not that difficult.. its the persistence and patience (in dealing with obstacles) that make the difference..
good luck and hope to hear from u soon.. :good:
Blefish said:
I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800
Click to expand...
Click to collapse
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:
rastek said:
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:
Click to expand...
Click to collapse
I understand what you are trying to say to Blefish.
I'll tell you. May it be 3.0.8 or 3.1 kernel, the story is the same: no Bluetooth and no WiFi. The 3.0.8 will need to be made compatible with CM10, but making WiFi and Bluetooth work will still won't be easy. That's why it is better to work on 3.1 kernel when you know that both kernels have the same story.
I hope you understand.
My phone is not dead!!!!!!!!!!!
Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app
alexmbra said:
My phone is not dead!!!!!!!!!!!
Click to expand...
Click to collapse
That's the spirit!!
rastek said:
Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes, it is a matter of configuration.
All we have right now are the drivers from Aurora and the drivers from official Huawei ROMs. To make CM10, the drivers need to be taken from an older ROM and put into CM10. Now, it is not just a matter of copy-pasting. Our current drivers are not compatible with JB. Blefish has made some things working. The biggest problem is the WiFi. The old WiFi drivers need to be made compatible with CM10, and this is the hardest part. This is why there has been no one, yet, who has been able to do this.
No matter what kernel it is, may it be 3.0.8 or 3.1, the WiFi drivers need to be made compatible with CM10.
I think oguzhan mobile was able to fix the WiFi to the extent where it actually turned on, but it wouldn't scan. I don't know why he stopped development. I am not sure what kernel oguzhan mobile was using, but I think it was 3.0.8. I think you might be right that it would be easier for our phone to use the 3.0.8 kernel, but I think the 3.1 kernel would run better with CM10.1.
If you really want to know why Blefish wouldn't use 3.0.8 kernel, then you would need to Blefish himself. I have already said what I think, but I am not sure if I am right.
I am going to give it a try with 3.0.8 kernel. It might be easier than 3.1 kernel. I'll just have to find out
I like the way you talk....
Waiting for JB...
Sent from my U8800 using Tapatalk 2
Just follow @rtammekivi on Twitter if you want to know what's going on.
Phone is dead
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