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 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
This rom is now available. I found it during a system-wide search on android file host. Its a new release. I have not tested it, but after testing the Xperia Z5 rom in an earlier post, I'd like to see someone else give this one a shot.
There's rom's out there guys, that we haven't seen on the boards. Lets find them, test them, and get them posted!! The moto community will be grateful! I'm assuming this xperia z5 rom is going to be a huge hit on here.
Once again, I'm new here, thus I can't post links yet. But go to android file host, search osprey and you'll find both the Xperia Z5 and the AOKP.
Those familiar with AOKP/AOSP will probably love this new rom!
Dude.. we're not going to flash a zip without any information.
I could just upload a zip with a script to hard brick your phone and name it Osprey Rom, Would you flash it?
HelpMeruth said:
Dude.. we're not going to flash a zip without any information.
I could just upload a zip with a script to hard brick your phone and name it Osprey Rom, Would you flash it?
Click to expand...
Click to collapse
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
Click to expand...
Click to collapse
Wow dude you got me there, i'm sorry man
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed.
Click to expand...
Click to collapse
You stated in your first post that you found it but had not tested it, so no, no one would want to test it from that. As for this post, I'm not sure what to make of that rambling, partly incoherent post.
Tel864,
At the moment I found it, I was testing the Xperia z5-g3 rom that I had found. A little later, I tested the AOKP that this thread is based upon. I apologize that I wrote my last post in a way that is difficult to understand for some people (you). But I'll try typing a little slower, for those who read a little slower.
So a brief recap for the reading impaired:
-Yes, I downloaded it.
-Yes, I tested it.
-No, I didn't really like it. Its a vanilla based rom, meant for customization by the end user using xposed and gravity box.
-It is a rather small build, about 315mb downloaded and about 900mb installed.
-I haven't found any rom breaking bugs, but again, I only tested it for about an hour before deciding it wasn't for me. But in all honesty, I knew it wasn't, as I had used AOKP and AOSP rom's in the past. I was merely testing it, so that those who are scared to do so -- would feel better about it.
Here's what I don't understand. Every week someone posts a new project, whether it be a kernel or rom. And every week, it is usually untested until they ask for volunteers. Sometimes the post will even go as far as saying that the it was developed without access to a moto g3, hence the developer themselves hadn't even tested it. Yet, with each new and untested project, person after person says "I'll test it!", "Sign me up!", "Ready when you are!!"
If testing a unknown rom isn't for you, then do us a favor... move on. Just curious though, what rom/kernel do you use? If you're running anything other than stock, then you took a chance when you installed it. The difference however, is that the OP made a 'pretty' and 'informative' initial post that caught your eye like a shiny object. If the same file that I mentioned in the original post, had specs, some graphics, and a few visually pleasing edits..... it wouldn't change anything about the file. It'd just change YOU, and YOUR mind.
So again, why do you trust ANYONE on here? Now... move on.
Interesting... I thought AOKP kind of folded a year or two ago, there haven't been any "official" builds since 2014. The Moto G is not listed as a supported device on their site, any generation of it, must be someones private port.
bubbyj said:
Tel864,
At the moment I found it, I was testing the Xperia z5-g3 rom that I had found. A little later, I tested the AOKP that this thread is based upon. I apologize that I wrote my last post in a way that is difficult to understand for some people (you). But I'll try typing a little slower, for those who read a little slower.
So a brief recap for the reading impaired:
-Yes, I downloaded it.
-Yes, I tested it.
-No, I didn't really like it. Its a vanilla based rom, meant for customization by the end user using xposed and gravity box.
-It is a rather small build, about 315mb downloaded and about 900mb installed.
-I haven't found any rom breaking bugs, but again, I only tested it for about an hour before deciding it wasn't for me. But in all honesty, I knew it wasn't, as I had used AOKP and AOSP rom's in the past. I was merely testing it, so that those who are scared to do so -- would feel better about it.
Here's what I don't understand. Every week someone posts a new project, whether it be a kernel or rom. And every week, it is usually untested until they ask for volunteers. Sometimes the post will even go as far as saying that the it was developed without access to a moto g3, hence the developer themselves hadn't even tested it. Yet, with each new and untested project, person after person says "I'll test it!", "Sign me up!", "Ready when you are!!"
If testing a unknown rom isn't for you, then do us a favor... move on. Just curious though, what rom/kernel do you use? If you're running anything other than stock, then you took a chance when you installed it. The difference however, is that the OP made a 'pretty' and 'informative' initial post that caught your eye like a shiny object. If the same file that I mentioned in the original post, had specs, some graphics, and a few visually pleasing edits..... it wouldn't change anything about the file. It'd just change YOU, and YOUR mind.
So again, why do you trust ANYONE on here? Now... move on.
Click to expand...
Click to collapse
I trust people with a high *thanks* rating, So if Squid or lost101 asks me to test something I don't expect that they want to brick my device. And please this is still Xda the place for the nice people .
I already said sorry for posting that hateful post, We can be friends.
I see you are really into testing new and exciting things, we need those people who will almost flash and test anything to make the experience for the end user as good as possible. Have a nice day and again sorry for the hate.
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
Click to expand...
Click to collapse
Thanks for the tip
However its not booting on my xt1550 stuck @Moto logo
I flashed @squid2's kernel and it booted but my setup wizard kept fcing
So unable to use the ROM..
androidbaba said:
Thanks for the tip
However its not booting on my xt1550 stuck @Moto logo
I flashed @squid2's kernel and it booted but my setup wizard kept fcing
So unable to use the ROM..
Click to expand...
Click to collapse
Just delete setup wizard via twrp
I have finally built it after trying different things, I fixed the problem myself. After receiving a whole lot of flak on my thread (that I intended to have this build already uploaded to) I have decided to ask if anyone wants me to create a thread for my sub-weekly builds. I will be building them as quickly as I feel they should be made (if errors happen) or weekly. Hope you guys are a little kinder this time to me. Or I might just stop replying to those comments. Anyways, let me know soon. Otherwise I'll take it as a no and just build it for myself.:good:
I am looking forward to it
Pls Share the Build.
Techie Android said:
I have finally built it after trying different things, I fixed the problem myself. After receiving a whole lot of flak on my thread (that I intended to have this build already uploaded to) I have decided to ask if anyone wants me to create a thread for my sub-weekly builds. I will be building them as quickly as I feel they should be made (if errors happen) or weekly. Hope you guys are a little kinder this time to me. Or I might just stop replying to those comments. Anyways, let me know soon. Otherwise I'll take it as a no and just build it for myself.:good:
Click to expand...
Click to collapse
This community is for sharing.You're more than welcome to share stuff that you feel worthy.
Though what you did the other day was incorrect,you'll get to know that yourself if you have a look at XDA rules.Just follow the rules and remember what is appropriate and what is not appropriate.
BTW,did you fixed the proximity sensor and random app crashes issue?
Please share. I've no idea what mistake you made and I really don't care too.
Mr.Ak said:
This community is for sharing.You're more than welcome to share stuff that you feel worthy.
Though what you did the other day was incorrect,you'll get to know that yourself if you have a look at XDA rules.Just follow the rules and remember what is appropriate and what is not appropriate.
BTW,did you fixed the proximity sensor and random app crashes issue?
Click to expand...
Click to collapse
I understand that about the rules and respect that and I admit I did not look at the rules regarding that, and I apologize for that. But it only took about a day to fixed the compiling problems, so all that whining to the mods to remove my thread was just plain unnecessary IMO. I will be more careful though now that I know that there are sensitive people here.
I'm not having any of that. Can you elaborate and maybe I can look into that more, what instance was it happening in? Remember I'm not associated with AOSPA on GitHub so I cannot make changes to the master. I'm still new to compiling ROMs and could probably use some insight on how and what is safe to modify on my local copy of the source. I was thinking about replacing jack compiler with the default toolchain now that jack has been depreciated.
Let me test this build out just to see what works/doesn't real quick and then I'll make another thread. I supposed it doesn't need to be flawless since I've seen worse ROMs pop up and they plain didn't half work. And sometimes they say to test it out yourself and report bugs... So I guess I'll upload it soon in a thread in the ROMs section.
Eagerly waiting for your build...
Techie Android said:
Let me test this build out just to see what works/doesn't real quick and then I'll make another thread. I supposed it doesn't need to be flawless since I've seen worse ROMs pop up and they plain didn't half work. And sometimes they say to test it out yourself and report bugs... So I guess I'll upload it soon in a thread in the ROMs section.
Click to expand...
Click to collapse
Yes,but devs only do that when they do blind builds aka builds for devices they don't have,since they can't test it themselves they release it to people having that device to test it out.
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
Techie Android said:
I understand that about the rules and respect that and I admit I did not look at the rules regarding that, and I apologize for that. But it only took about a day to fixed the compiling problems, so all that whining to the mods to remove my thread was just plain unnecessary IMO. I will be more careful though now that I know that there are sensitive people here.
I'm not having any of that. Can you elaborate and maybe I can look into that more, what instance was it happening in? Remember I'm not associated with AOSPA on GitHub so I cannot make changes to the master. I'm still new to compiling ROMs and could probably use some insight on how and what is safe to modify on my local copy of the source. I was thinking about replacing jack compiler with the default toolchain now that jack has been depreciated.
Click to expand...
Click to collapse
Some apps and games which were supposed to work(since they work out fine on other ROMs) give force closes.
About proximity sensor, when you place your device during a call on your ear then the screen should turn off normally,but it doesn't(on official AOSPA) due to proximity sensor issues, although it can be fixed by using another firmware ,it should be fixed(ROM side changes) so that people can use other firmwares too if they want to.
It's up! https://forum.xda-developers.com/oneplus-one/development/rom-t3656901
Mr.Ak said:
Yes,but devs only do that when they do blind builds aka builds for devices they don't have,since they can't test it themselves they release it to people having that device to test it out.
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
Some apps and games which were supposed to work(since they work out fine on other ROMs) give force closes.
About proximity sensor, when you place your device during a call on your ear then the screen should turn off normally,but it doesn't(on official AOSPA) due to proximity sensor issues, although it can be fixed by using another firmware ,it should be fixed(ROM side changes) so that people can use other firmwares too if they want to.
Click to expand...
Click to collapse
Yeah I had the proximity problem but never had my apps crash. But the proximity problem is fixed now.
can you build paranoid android with OOS blobs V3?
It uses 2.x right now, right?
also more video codec support?
Thread closed. Anything after this point I will not monitor. Go to https://forum.xda-developers.com/oneplus-one/development/rom-t3656901 to post.
so far aospa(just test it) in my OnePlus One has the following issues (official AOSPA from their website)
- The hardware keys light is broken(lights up whenever and for unknown time - also cannot be controller),
- The battery circle icon(my favorite) ...if you use the percentage, you can't see the percentage ...circle is having a thick layer(for some reason)
Didn't test it further as I can't have these obvious bugs, so back to LA-OS until it's better