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.
Nice finally @!!1
Captivating has 3g and EDGE, no LTE.
Sent from my SPH-D700 using XDA App
iSaint said:
Nice finally @!!1
Click to expand...
Click to collapse
I really wanna know where it's all going. I have CM7-A4 on my phone right now, but I need everything to be fixed before I move. You can't be around girls with a phone that doesn't function, so I need this. And stock is better then anything tbh.
marcusant said:
Captivating has 3g and EDGE, no LTE.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks for the confirmation.
Don't forget that another problem lies not only in the rear facing camera, but the front facing one too. Let's just hope that they keep on it. I thank them as well for all that they've done so far.
You should make the "No ETAs" in the OP bigger and bold in case nubs don't read lol.
Anyway, I'm pretty excited for CM7. I do agree that the Nexus S 4G should help the Epic's 4G issue since they are both WiMax/CDMA. I don't think that would help the front facing camera, but I don't think it'll really be a problem since both the Nexus S and Epic have a VGA .3 MP Front Facing Camera
Original Android <3ers! said:
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.
props for this
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.
its a lot more then just this, but you get the idea
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.
uh.. no. the camera is different from the ns4g to the epic. they have all teh wimax stuff they got it all when source for the ns4g dropped. its just a matter of making sure it connects properly now.. oh and works...
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).
a break from pushing to github.. in the irc they are lively as ever
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
sweet jesus... this is gunna take a min forgive me
good stuff overall tho
How to port cm7:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
first! (to Deca's awesome contribution)
odub303 said:
first!
10chars
Click to expand...
Click to collapse
at spot #9 maybe
thers a reason this thread got closed and stopped dev.
last i saw we were missing source, something that is a tad important in any porting and working with a different phone.
But keep the dream alive man KEEP IT ALIVE!
EpicCM development is stalled right now until we get the 2.6.35 kernel source drop from Samsung.
Simply put, the Epic is very different on a hardware level than the other SGS phones. The NS4G has far more in common with the NS than it does with the Epic. Their kernel is not useful to us because so much has to be remapped to work with our hardware, not to mention certain device-specific drivers that are only available in the "Victory" branch.
Once we do have that source, the rest should follow very quickly. The platform itself needs very little tweaking.
UberPinguin said:
EpicCM development is stalled right now until we get the 2.6.35 kernel source drop from Samsung.
Simply put, the Epic is very different on a hardware level than the other SGS phones. The NS4G has far more in common with the NS than it does with the Epic. Their kernel is not useful to us because so much has to be remapped to work with our hardware, not to mention certain device-specific drivers that are only available in the "Victory" branch.
Once we do have that source, the rest should follow very quickly. The platform itself needs very little tweaking.
Click to expand...
Click to collapse
That ^, seemed to lengthy to type out. I have the device bits all in place and mostly sync'd with the rest of the galaxy s/sprint devices.
EddyBalls said:
Don't forget that another problem lies not only in the rear facing camera, but the front facing one too. Let's just hope that they keep on it. I thank them as well for all that they've done so far.
Click to expand...
Click to collapse
But be honest, how many of us ACTUALLY use the front facing camera? And they got it working on the Evo. Again, just some Kernel and Driver fixes should get it if we get the rear camera working.
|| Acer || said:
You should make the "No ETAs" in the OP bigger and bold in case nubs don't read lol.
Anyway, I'm pretty excited for CM7. I do agree that the Nexus S 4G should help the Epic's 4G issue since they are both WiMax/CDMA. I don't think that would help the front facing camera, but I don't think it'll really be a problem since both the Nexus S and Epic have a VGA .3 MP Front Facing Camera
Click to expand...
Click to collapse
Exactly.
shabbypenguin said:
sweet jesus... this is gunna take a min forgive me
Click to expand...
Click to collapse
Sorry. I just wanted to get it all out there.
Decad3nce said:
How to port cm7:
Click to expand...
Click to collapse
My apologies, I have no idea what that means...
i think the proper way to port cm7 is to have a city wide riot when your team cannot find any loopholes in the code of life to score success
cue youtube links to "flash bang nut shot"
and of course
o' canada...we stand on guard for thee!!!
(everyone sing the national anthem in unison...whee!...go canasian go!)
UberPinguin said:
EpicCM development is stalled right now until we get the 2.6.35 kernel source drop from Samsung.
Simply put, the Epic is very different on a hardware level than the other SGS phones. The NS4G has far more in common with the NS than it does with the Epic. Their kernel is not useful to us because so much has to be remapped to work with our hardware, not to mention certain device-specific drivers that are only available in the "Victory" branch.
Once we do have that source, the rest should follow very quickly. The platform itself needs very little tweaking.
Click to expand...
Click to collapse
So all we need is the Source?
Original Android <3ers! said:
So all we need is the Source?
Click to expand...
Click to collapse
Yes. Once we have the kernel source, the rest is cake.
I tried to compile from source last night but i kept getting a build.sh error, anyone know whats up there? im building in ubuntu linux 11.04
Art2Fly said:
I tried to compile from source last night but i kept getting a build.sh error, anyone know whats up there? im building in ubuntu linux 11.04
Click to expand...
Click to collapse
If you're building from the EpicCM repo, it won't work right now. We're in a transition stage, and a lot of stuff is waiting for the kernel merge before we can fix the build system.
UberPinguin said:
Yes. Once we have the kernel source, the rest is cake.
Click to expand...
Click to collapse
Awesome! So we're just waiting for the Epic's gingerbread kernel source and the rest is that easy?! Damn, if the Epic comes out with Gingerbread on the 20th like expected, Samsung will probably drop the source within the next few days. I smell early July to have CM7 if everything goes according to plan!!
Related
I'm new to this but here we go This is a port of the Desire HD Miui rom 1.7.15 with english patch. I'm using parts of superkids excellent Cyanogen rom to fix the hardware issues. It's a work in progress so don't get upset if things don't work.
So far from my testing these things work (your mileage may vary):
Camera (face camera not quite yet but main camera works nicely)
WIFI
GPS
Phone
Audio
Volume Keys
etc.
Not working:
Bluetooth
Sim contacts
Video playback
probably other stuff too
Installation instructions
Full wipe, install from recovery and then flash the excellent Unity V2 kernel from here. If overclocking is your thing, I use setcpu set to 245760 min, 1209600 max with smartass scaling.
The default kernel included won't enable WIFI so if you want it, flash the Unity kernel.
Try it out and see what you think. I'll try to look at fixing things as and when i get to them but bluetooth isn't going to be high on my priority list as I don't use it (but you're welcome to pull the rom apart and give it a whirl yourself!) I don't have a lot of time so if you want to try fixing things, please do as we'll all benefit
Download here (Mediafire)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice ill test it right away... flashing now
Update: everything you say is working works but you can add wifi to not working.
Beukhof1 said:
Nice ill test it right away... flashing now
Update: everything you say is working works but you can add wifi to not working.
Click to expand...
Click to collapse
wifi can be worked if using MDJ V2 kernel
How about battery cost?
Can the phone sleep correctly?
Now all the MIUI roms have a battery drain because the phone sleeps incorrectly.
Is camera quailty good?
Edit : I looked in the forum for the MDJ v2 kernel couldn't find it can you post a link please
Sent from my HTC Desire S using XDA App
still wait'n for perfect MIUI rom...
faddys123 said:
Is camera quailty good?
Edit : I looked in the forum for the MDJ v2 kernel couldn't find it can you post a link please
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
I think this link is for the kernel recommended?
Peace
Anyone got any screenshots?
chris5s said:
I think this link is for the kernel recommended?
Peace
Anyone got any screenshots?
Click to expand...
Click to collapse
thanks but apparently the wifi didnt working with that i will test it now anyways
faddys123 said:
thanks but apparently the wifi didnt working with that i will test it now anyways
Click to expand...
Click to collapse
No probs. Wifi not working is a ROM issue, I have that kernel flashed to my own custom ROM, wifi is fine.
Looking forward to seeing more MIUI development ... and some screenshots too
belantara said:
still wait'n for perfect MIUI rom...
Click to expand...
Click to collapse
Thanks for letting us know. I was concerned that you might try this one and be unhappy with it. On a more serious note, this kind of post does not help anyone! Did you even download this rom to try it or are you just informing us that you won't be happy until a 100% working Miui rom falls into your lap. We'd all love a perfectly working Miui rom but it won't happen overnight!
You're in a development forum, by it's very nature, you're not going to ever see many 100% working roms, hence the development in the forum name.
fugutrev said:
Thanks for letting us know. I was concerned that you might try this one and be unhappy with it. On a more serious note, this kind of post does not help anyone! Did you even download this rom to try it or are you just informing us that you won't be happy until a 100% working Miui rom falls into your lap. We'd all love a perfectly working Miui rom but it won't happen overnight!
You're in a development forum, by it's very nature, you're not going to ever see many 100% working roms, hence the development in the forum name.
Click to expand...
Click to collapse
+1
@belantara
you need to understand that the devs are doing this in their free time & are not asking for anything in return other than a little support
so if you have a negative comment why do you want to post it & discourage them??it isnt always easy finding the bugs & correcting them
Great
I find it great that there is a seperate thread for miui development now. Due to the fact that all the other miui roms are developed on extern sites.
I hope that more developers will start helping here.
I am not sure but why aren't working let's say miui-developers together to make a more stable, faster, and more complete rom. I meen we are a community here. Nobody has to fight against the others.
I've seen it for a long time in the HTC Hero forums, that developers try to beat each other instead of working together to make something great.
Like i can see here it's the same, yes sure it's difficult that someone works together with the chinese developers but it would be possilbe to work together with the guy from the english miui forum, who made a great version too?
After that it would be possilbe to ask some devs from other roms for help. i am sure no one will say oh no i fight this rom-war on my own. stop asking for help.
In fact the main idea of forums was the easy way to exchange information between persons from different countries, even with different languages. So they can work together and so they will be able to make better things. Like you can see it over at stackoverflow, someone has a question the other will help him.
why so much devs forget this fact?
--------------------
Oh and i am happy to see someone who tries his luck with cooking a rom
--------------------
If i had more time and some idea of cooking roms i would help you, but i think with my java knowledge i can't help that much.
Keep up your work it's great.
If anyone wants a detailed process of how to go about porting one rom from another I'd be happy to post it in here so more people can get on board and experimenting. My android hacking experience isn't great but I'm learning as I go (I have many years of linux experience which helps immensely). superkids work on the cyanogenmod rom is the reason I was able to bring a somewhat working Miui rom to the forum so big slaps on the back to him
I'll keep nibbling away at the issues and see what I can do but if anyone else wants to get involved, I'd be overjoyed. The more the merrier
Also, I've been in touch with superkid and he's happy with elements of his cyanogenmod rom being used to make Miui work. I've also been in contact with fusingblackrose on the Miuiandroid forums and his rom was my first port of call when starting off on this port so it's all good
I'm on this rom since yesterday night, what I can say for now is that it's a lil' bit slower than the 7.1.8 from fengbao wich I used for about a week.
I did not test the GPS yet, but there is an improvement in compatibility since the last release : the softkeys are now backlighted correctly.
I think all the issues we have are only about drivers, I am totally new at Android (only since AlpharevX release for Desire S) but as I'm intereested on it, I already know a lot about it, made tweaks and tested many roms, learned about the way it works in the inside.
I'd really appreciate you to post the process you are talking about, I still don't know how to edit roms, compile it and package it for a flash from recovery.
I'm sure I can help
If you need any type of help tell me
superkid said:
If you need any type of help tell me
Click to expand...
Click to collapse
we need bluetooth
When i fix it in mine will be fixed here too
Thanks!
i was waiting for this ROM.
- the WiFi works only if you install the UNITY v2 Kernel
- the sound works, but it has some problem... all the sounds (speaker, headphone, in call sound) are not clear, are a little bit distorted..
Thanks again, good work!
superkid said:
When i fix it in mine will be fixed here too
Click to expand...
Click to collapse
waiting ) want to listen music via bt )
Can i use some ita lang pack from this page?
How can i convert a lang pack from a device to another?
Hello,
use the pack for the desire HD.
I knew this summer was going to be a hit for the Doubleshot, but it seems all dev action has ceased since then.
Anyone know what's been going on with our device lately?
Just a BS thread to discuss our device. Devs feel free to chime in.
Or if you're secretly working on something and would like to tease us by letting us know what's coming, by all means...
Just remember to include an ETA
Someone we all know is working on something that looks pretty slick but that's ALLLL I'ma sayin'...............
:angel:
xmc_wildchild started school. That's what happened.
Dunno but I've been having gps speedometer issues
Sent from my myTouch_4G_Slide using xda app-developers app
gtmaster303 said:
I knew this summer was going to be a hit for the Doubleshot, but it seems all dev action has ceased since then.
Anyone know what's been going on with our device lately?
Just a BS thread to discuss our device. Devs feel free to chime in.
Or if you're secretly working on something and would like to tease us by letting us know what's coming, by all means...
Just remember to include an ETA
Click to expand...
Click to collapse
I know Strapped365 is working on a rom with the LG launcher. I'm sure he will post something on it in a few days when he's done and has time.
soldierexile said:
Dunno but I've been having gps speedometer issues
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
What kind of problems?
cybot_x1024 said:
I know Strapped365 is working on a rom with the LG launcher. I'm sure he will post something on it in a few days when he's done and has time.
Click to expand...
Click to collapse
Well it still has some issues. The major one is not going to deepsleep. Then the force close from portrait to landscape and back again. I'm racking my brain trying to figure it out though because I've gotten way more Widgets from LG added
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Well it still has some issues. The major one is not going to deepsleep. Then the force close from portrait to landscape and back again. I'm racking my brain trying to figure it out though because I've gotten way more Widgets from LG added
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
If the ROM is CM-based there's a kernel patch in the Alpha 6 thread
blackknightavalon said:
If the ROM is CM-based there's a kernel patch in the Alpha 6 thread
Click to expand...
Click to collapse
Yeah I just flashed that and its showing deep sleep as a usable CPU scale the phone just hasn't went there yet
Sent from my myTouch_4G_Slide using Tapatalk 2
I am currently but slowly lol! Learning and trying to port TWRP recovery in our device since 4ext for our device has still a long way.
For those wondering what twrp is
http://teamw.in/project/twrp
Here are some screenies from other devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I still don't have a development box to start developing so that first before the WIP since I would need to pull the whole CM build and compile it just to make this recovery. I don't think my good old vps is enough to do this kind of job and I'm not also considering to reformat my windows PC just for this.
I think it has been a pretty good summer for development on our MT4GS. We've got a nice crop of ICS roms to choose from, either AOSP or CM or several Sense flavors. It's a smorgasbord! :highfive:
Riyal said:
I am currently but slowly lol! Learning and trying to port TWRP recovery in our device since 4ext for our device has still a long way.
For those wondering what twrp is
http://teamw.in/project/twrp
Here are some screenies from other devices.
I still don't have a development box to start developing so that first before the WIP since I would need to pull the whole CM build and compile it just to make this recovery. I don't think my good old vps is enough to do this kind of job and I'm not also considering to reformat my windows PC just for this.
Click to expand...
Click to collapse
Do what I used to do and just buy a box for just $300 at a Best Buy and load Linux on it.
Sent from Spaceball One.
gtmaster303 said:
I knew this summer was going to be a hit for the Doubleshot, but it seems all dev action has ceased since then.
Anyone know what's been going on with our device lately?
Just a BS thread to discuss our device. Devs feel free to chime in.
Or if you're secretly working on something and would like to tease us by letting us know what's coming, by all means...
Just remember to include an ETA
Click to expand...
Click to collapse
Well Sun_Dream has worked on our phone with a bit of Sense roms if you dig that.
"HTC Doublshot ICS Bliss" sporting Sense 3.6: http://forum.xda-developers.com/showthread.php?t=1896643
and
"Doubleshot Android 4.0.4 Sense4.1+4A Base Ville_U_ICS_40_S_2.31.401.5": http://forum.xda-developers.com/showthread.php?t=1832805
Both seem solid, didn't quite test them out as I'm digging XMC's Jellybean.
Should be a lot of development when Sense 4.5 comes out though I sense ports coming.
blackknightavalon said:
Do what I used to do and just buy a box for just $300 at a Best Buy and load Linux on it.
Sent from Spaceball One.
Click to expand...
Click to collapse
Still won't be that helpful to me since we got a crappy internet in our country. Pulling a whole CM build would take me like almost a day of non stop downloading to do that
Unlike on a vps I could just pull both cm7 & cm9 in 30minutes
Riyal said:
Still won't be that helpful to me since we got a crappy internet in our country. Pulling a whole CM build would take me like almost a day of non stop downloading to do that
Unlike on a vps I could just pull both cm7 & cm9 in 30minutes
Click to expand...
Click to collapse
Ouch. Happy devving.
Sent from Spaceball One.
Riyal said:
I still don't have a development box to start developing so that first before the WIP since I would need to pull the whole CM build and compile it just to make this recovery. I don't think my good old vps is enough to do this kind of job and I'm not also considering to reformat my windows PC just for this.
Click to expand...
Click to collapse
"Just for this"????
Why? You afraid of your computer being *actually useful*???
Riyal said:
Still won't be that helpful to me since we got a crappy internet in our country. Pulling a whole CM build would take me like almost a day of non stop downloading to do that
Unlike on a vps I could just pull both cm7 & cm9 in 30minutes
Click to expand...
Click to collapse
If it helps I could give you teamviewer access on a virtual machine on my PC to access its resources when I'm not using it. Its not the best available but I'm sure it can help.
Sent from my HTC Vision using xda app-developers app
lbcoder said:
"Just for this"????
Why? You afraid of your computer being *actually useful*???
Click to expand...
Click to collapse
People in glass houses shouldn't throw stones...
Ok so where I'm at now. I have figured out I didn't need to use anything from the EVO Shift to get this LG launcher up and running. So its not a port anymore ( so it lost andromaus settings which were cool but caused wakelocks ), its more so a launcher replacement, all other cm9 functions work like they should. So right now I'm trying to figure out how to post it, and here are my posting options I can either
1. Just package all the launcher and widgets as a flash over for any CLEAN INSTALL OF AOSP/AOKP ( will need testers for AOKP ). And a certain set of gapps so the gallery don't get broken
Or
2. I can just pre package everything into a CM build ( gapps and all ) so nothing gets broken. Its your call here is a couple screen shots. And if anyone wants to give it a try just pm me ill get you a dropbox link
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Ok so where I'm at now. I have figured out I didn't need to use anything from the EVO Shift to get this LG launcher up and running. So its not a port anymore ( so it lost andromaus settings which were cool but caused wakelocks ), its more so a launcher replacement, all other cm9 functions work like they should. So right now I'm trying to figure out how to post it, and here are my posting options I can either
1. Just package all the launcher and widgets as a flash over for any CLEAN INSTALL OF AOSP/AOKP ( will need testers for AOKP ). And a certain set of gapps so the gallery don't get broken
Or
2. I can just pre package everything into a CM build ( gapps and all ) so nothing gets broken. Its your call here is a couple screen shots. And if anyone wants to give it a try just pm me ill get you a dropbox link
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I don't know about other people, but personally I'd go with option 2. You will have a lot less bugs to deal with and give yourself more time to focus on improving it and adding features. I don't know what you think about that but that's what I'd go with
Sent from my HTC Vision
Hey guys just wanting to know if anyone knows if we can port the paranoid android ROM to the atrix 2 ? There cm10 ROM for galaxy s3 is above all IMHO mainly for user fun
So can we contact them to port for the atrix 2 or can someone port it them self's?
Sent from my MB865 using XDA Premium HD app
You are not the first to ask, so please stop asking this question - or do it yourself.
It will come if/when it comes. And I highly doubt that somebody without an A2 will port it for us - but feel free to request that of them.
Btw, I have put some time into porting PA, then I dropped it for a while - since our phone does not play nicely with ports - but I plan on returning to it again.
If someone seriously wants to work on this, PM me.
Sent from my phone's mind
alteredlikeness said:
You are not the first to ask, so please stop asking this question - or do it yourself.
It will come if/when it comes. And I highly doubt that somebody without an A2 will port it for us - but feel free to request that of them.
Btw, I have put some time into porting PA, then I dropped it for a while - since our phone does not play nicely with ports - but I plan on returning to it again.
If someone seriously wants to work on this, PM me.
Sent from my phone's mind
Click to expand...
Click to collapse
Why did u drop the project? Dint it run properly?
siddhesh1609 said:
Why did u drop the project? Dint it run properly?
Click to expand...
Click to collapse
No, what he was saying is that porting roms without a compile, to our phone just does not seem to end well for any of the devs.
We have had way more success with compiling ROMs from scratch since ICS has showed up for us.
In GB I had compiled several ROMs and had a ton of issues getting them to work well. I then gave up for a while. I had cm7 working for a while with kexec, but that got to be a real pia.
I waited until ICS came out to try again, and I am 98% done with my CM10 compiled version, which I have been working on for almost 2 months now, so..... Long story short compiles are good on the A2, ports are not so good.
BTW a port means to take a working version from another phone with very close hardware to another and "port" it to work on the other phone. We have used the razr and bionic as starting points since they are very close relatives, but we have still had issues. It can also mean to take the code for something like aosp/aokp/cm, and get all the files together that are needed to make the rom work for a phone and start editing code, and then compile it, similar to what wang and I have done with cm10.
I will let alteredlikeness tell you what his thoughts were on his speciic PA port, but this is just a general thing with us.
siddhesh1609 said:
Why did u drop the project? Dint it run properly?
Click to expand...
Click to collapse
Yea, what jim said..
And I just really wanted to get PA on my phone - but I need a bigger linux partition on my computer to compile from source - so I decided to just try to port it (tried from 2 diff phones actaully), and I couldn't get past the boot animation or adb recognized after about a million different approaches.
I will still pursue this, but I agree with jim- gotta compile not port
Sent from my phone's mind
It's coming...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We got a lot of issues to work out, but cogeary and I are doing all we can to bring this to the A2.
One of the major issues is that my phone thinks it's a tablet... that screenshot was originally 768x1366.. and I can only see a small 540x960 window of that over-sized UI (need to turn on 360 rotation and flip the phone to see other areas of the screen)... besides that, there's no wifi, soft keys, or phone call audio - so, it's not usable yet.
This is not an invitation to PM about timelines or progress - so please don't. This is just to let everyone know that cogeary and I are working on this (and an excuse as to why I'm not updating Numa). Thanks to cogeary for answering my call to take on this beast..
If anyone's curious, the idea of porting it is dead - I deleted my Wubi install and installed Ubuntu as a guest in VirtualBox on Win7 for a quick way to get a larger partition - compiling it fresh from source..
...more screenies...
alteredlikeness said:
It's coming...
We got a lot of issues to work out, but cogeary and I are doing all we can to bring this to the A2.
One of the major issues is that my phone thinks it's a tablet... that screenshot was originally 768x1366.. and I can only see a small 540x960 window of that over-sized UI (need to turn on 360 rotation and flip the phone to see other areas of the screen)... besides that, there's no wifi, soft keys, or phone call audio - so, it's not usable yet.
This is not an invitation to PM about timelines or progress - so please don't. This is just to let everyone know that cogeary and I are working on this (and an excuse as to why I'm not updating Numa). Thanks to cogeary for answering my call to take on this beast..
If anyone's curious, the idea of porting it is dead - I deleted my Wubi install and installed Ubuntu as a guest in VirtualBox on Win7 for a quick way to get a larger partition - compiling it fresh from source..
...more screenies...
Click to expand...
Click to collapse
Dude !!!! :highfive:
alteredlikeness said:
It's coming...
We got a lot of issues to work out, but cogeary and I are doing all we can to bring this to the A2.
One of the major issues is that my phone thinks it's a tablet... that screenshot was originally 768x1366.. and I can only see a small 540x960 window of that over-sized UI (need to turn on 360 rotation and flip the phone to see other areas of the screen)... besides that, there's no wifi, soft keys, or phone call audio - so, it's not usable yet.
This is not an invitation to PM about timelines or progress - so please don't. This is just to let everyone know that cogeary and I are working on this (and an excuse as to why I'm not updating Numa). Thanks to cogeary for answering my call to take on this beast..
If anyone's curious, the idea of porting it is dead - I deleted my Wubi install and installed Ubuntu as a guest in VirtualBox on Win7 for a quick way to get a larger partition - compiling it fresh from source..
...more screenies...
Click to expand...
Click to collapse
Oh boy, oh boy, oh boy. I can't describe your awesomeness
brianmoyano said:
Oh boy, oh boy, oh boy. I can't describe your awesomeness
Click to expand...
Click to collapse
Sure you can...
Big progress in the last couple days for a usable alpha build - fixed the oversized issue, soft keys, touch sensors, and phone call audio (a sloppy fix IMO, but.. eh, it works - but, as I said earlier, my main intention was just to get this working on my phone)
Still no wifi, and got the common moto cm10 bugs, like the stuttering boot, rotation shrinkage & shrunken screenshot, data is a kinda buggy (works, but two bars), probably other bugs... still not a daily by any means.
And, the Paranoid settings can be a bit tricky.. not sure yet if it's buggy, or it's just me. I will probably be sending out a few test samples to some senior members soon.. watch your inboxes! (and don't call me, I'll call you... well, a few of you can if I forget - but you know who you are)
Big thanks again to cogeary and jimbridgman for their support (and some good old dumb luck/strategy) - now I can get a little more sleep at night.. :silly:
"Life... loathe it or ignore it, you can't like it." - Marvin, the Paranoid Android from Douglas Adam's Hitchhiker's Guide to the Galaxy (check out the books before the movie, if so inclined)
alteredlikeness said:
Sure you can...
Big progress in the last couple days for a usable alpha build - fixed the oversized issue, soft keys, touch sensors, and phone call audio (a sloppy fix IMO, but.. eh, it works - but, as I said earlier, my main intention was just to get this working on my phone)
Still no wifi, and got the common moto cm10 bugs, like the stuttering boot, rotation shrinkage & shrunken screenshot, data is a kinda buggy (works, but two bars), probably other bugs... still not a daily by any means.
And, the Paranoid settings can be a bit tricky.. not sure yet if it's buggy, or it's just me. I will probably be sending out a few test samples to some senior members soon.. watch your inboxes! (and don't call me, I'll call you... well, a few of you can if I forget - but you know who you are)
Big thanks again to cogeary and jimbridgman for their support (and some good old dumb luck/strategy) - now I can get a little more sleep at night.. :silly:
"Life... loathe it or ignore it, you can't like it." - Marvin, the Paranoid Android from Douglas Adam's Hitchhiker's Guide to the Galaxy (check out the books before the movie, if so inclined)
Click to expand...
Click to collapse
Well, you're awesome man.
Do you need something? It would be nice to help
That's cool! Finally with all the good roms coming in for the a2 I now have a reason to hold back from sellin ma a2 away! thanks devs! :thumbup:
Sent from my MB865 using xda premium
To the creator of pa rom for our beloved atrix 2 first of all thank you... is it going to be a pacman version of pure PHablet rom?:highfive: in anycase i m happy
---------- Post added at 07:14 PM ---------- Previous post was at 07:11 PM ----------
jimbridgman said:
No, what he was saying is that porting roms without a compile, to our phone just does not seem to end well for any of the devs.
We have had way more success with compiling ROMs from scratch since ICS has showed up for us.
In GB I had compiled several ROMs and had a ton of issues getting them to work well. I then gave up for a while. I had cm7 working for a while with kexec, but that got to be a real pia.
I waited until ICS came out to try again, and I am 98% done with my CM10 compiled version, which I have been working on for almost 2 months now, so..... Long story short compiles are good on the A2, ports are not so good.
BTW a port means to take a working version from another phone with very close hardware to another and "port" it to work on the other phone. We have used the razr and bionic as starting points since they are very close relatives, but we have still had issues. It can also mean to take the code for something like aosp/aokp/cm, and get all the files together that are needed to make the rom work for a phone and start editing code, and then compile it, similar to what wang and I have done with cm10.
I will let alteredlikeness tell you what his thoughts were on his speciic PA port, but this is just a general thing with us.
Click to expand...
Click to collapse
So if I m not wrong you devs need to do most of the things from scratch as in compiling the resources from repositories...
RESPECT !!!
siddhesh1609 said:
To the creator of pa rom for our beloved atrix 2 first of all thank you... is it going to be a pacman version of pure PHablet rom?:highfive: in anycase i m happy
---------- Post added at 07:14 PM ---------- Previous post was at 07:11 PM ----------
So if I m not wrong you devs need to do most of the things from scratch as in compiling the resources from repositories...
RESPECT !!!
Click to expand...
Click to collapse
Ya...... yes that's y things are buggy and take a long time to get right.... and y we all go NUTS when updates are "requested" or even "questioned"...
Sent from my MB865 using xda app-developers app
alteredlikeness said:
It's coming...
We got a lot of issues to work out, but cogeary and I are doing all we can to bring this to the A2.
One of the major issues is that my phone thinks it's a tablet... that screenshot was originally 768x1366.. and I can only see a small 540x960 window of that over-sized UI (need to turn on 360 rotation and flip the phone to see other areas of the screen)... besides that, there's no wifi, soft keys, or phone call audio - so, it's not usable yet.
This is not an invitation to PM about timelines or progress - so please don't. This is just to let everyone know that cogeary and I are working on this (and an excuse as to why I'm not updating Numa). Thanks to cogeary for answering my call to take on this beast..
If anyone's curious, the idea of porting it is dead - I deleted my Wubi install and installed Ubuntu as a guest in VirtualBox on Win7 for a quick way to get a larger partition - compiling it fresh from source..
...more screenies...
Click to expand...
Click to collapse
Dude so pleased you did it I moved on to a galaxy s3 but still have my a2 and use it a lot but mate thanks huge for doing this for the a2 community
Sent from my GT-I9300 using XDA Premium HD app
i know noob question from a Senior member but what are the Aries Common bugs? i flash the 4.2.2 roms and they say Aries Common Bugs but i have no idea what they are so can someone tell me what the bugs are?
http://forum.xda-developers.com/sh...d Questions Thread - No question too stupid!
TwitchyEye said:
http://forum.xda-developers.com/sh...d Questions Thread - No question too stupid!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think the common bugs are no gps working, no wifi calling, and something else. However I think it is in the general forum there is a bounty thread that lists them. I would check there.
Here r common bugs and more correctly, these are Aries common bugs for galaxy S 4G:
No GPS.
Earphone control set broken.
IRQs buggy (this is kernel bug for our phone as Bryan pointed it out).
Telephony buggy for AT&T (Bryan had on his phone but I'm not sure bout other users).
No Sammy bloatware compatible LOL.
Feel free to make an article bout the current aries common bugs at Galaxy S 4G wiki page for our phone so we can track and edit the list as well as everyone else can read what r the bugs from wiki.
Sent from my SGH-T959V using Tapatalk 2
It's almost like I predicted this question in advanced. I'll glady make some changes to the wiki before I leave for work later.
Sent from my SGH-T959V using xda app-developers app
daothanhduy1996 said:
Here r common bugs and more correctly, these are Aries common bugs for galaxy S 4G:
Click to expand...
Click to collapse
Just validating...
daothanhduy1996 said:
No GPS.
Click to expand...
Click to collapse
Check.
daothanhduy1996 said:
Earphone control set broken.
Click to expand...
Click to collapse
Check, I might have a fix for this, but I need to test my fix again.
daothanhduy1996 said:
IRQs buggy (this is kernel bug for our phone as Bryan pointed it out).
Click to expand...
Click to collapse
Check, still trying to figure this stuff out, but I think I know what this is... I'll go into details at the end.
daothanhduy1996 said:
Telephony buggy for AT&T (Bryan had on his phone but I'm not sure bout other users).
Click to expand...
Click to collapse
Yea... I've noticed t-mo users complaining of the same exact issues as well. I think this has to do with the IRQ issues.
daothanhduy1996 said:
No Sammy bloatware compatible LOL.
Click to expand...
Click to collapse
I'm guessing you mean that this doesn't work with stock roms? I'd like to see someone fix this. I was attempting a port of ICBINB to mtd, but I don't have time and need @dsexton702's help.
daothanhduy1996 said:
Feel free to make an article bout the current aries common bugs at Galaxy S 4G wiki page for our phone so we can track and edit the list as well as everyone else can read what r the bugs from wiki.
Click to expand...
Click to collapse
Totally, this would also make me happy if someone tested this stuff. Even more happy would be if someone figured out how to setup and run CTS for our device to find real bugs and post the results somewhere. Any takers?!?
So more info on the IRQ things...
I originally noticed this issue when we did the 3.0 port when bringing up the samsung-audi onenand mtd driver.
The driver didn't complain about finding an IRQ in 2.6.35.7, because there wasn't an IRQ set in the platform data for onenand back then. I'm wondering if the "no irq found" error the onenand driver spits out is benign...
But the bigger issue with IRQs is with power management interrupt controller (PMIC). Our PMIC driver is the max8998. In the 2.6.35.7 kernel, there were some REALLY NASTY hacks that samsung did to the PMIC, RTC (RealTime Clock... which is both the max8998 and s3c rtc drivers), the s5pc110_battery and the max17040 power drivers. There are a set of interrupts that are shared amongst them, and the other phones don't seem to implement this hack. The closest drivers I've seen are actually for the P1 (first gen galaxy tab, in aries). The code is a tangled web, and everytime I pull the string on it, the sweater keeps getting smaller. But it's not simple to figure out. The better way to handle what samsung was trying to achieve should now be handled with platform data structures. So I'm working on it, but as I mentioned before, I'm kinda going through some wacky life madness and time for phones is pretty low.
If there are other kernel devs around that know what they are doing and want to get some pointers to what code I'm talking about, I'd love to help out and see this stuff get fixed, I just personally don't have time to fix it myself. Please PM me or find me on skype/irc. My name is pretty unique and no one else that I know is: Bryan Hundven
Hope this info is helpful to someone.
Also, not to go off topic too much, I have in my possession an Epic4G (SPH-D700), and am going to look at the onenand driver and irq fixes they did to get a 3.0 kernel on it, as well...
I'm thinking about porting their kexec recovery hack. Let me know what you think!
bhundven said:
Also, not to go off topic too much, I have in my possession an Epic4G (SPH-D700), and am going to look at the onenand driver and irq fixes they did to get a 3.0 kernel on it, as well...
I'm thinking about porting their kexec recovery hack. Let me know what you think!
Click to expand...
Click to collapse
DO EEET!
(bhundven, your post was submitted yesterday at 4:20pm).
FBis251 said:
DO EEET!
Click to expand...
Click to collapse
Well, seems I need to send my epic4g to get jtaged. It's always something stupid. I updated bootloaders and must have dorked them while flashing. None of my computers will see it when in download mode. (yes, tried multiple computers, multiple cables, multiple drivers, etc...)
FBis251 said:
(bhundven, your post was submitted yesterday at 4:20pm).
Click to expand...
Click to collapse
I didn't notice that till you said it.
bhundven said:
Well, seems I need to send my epic4g to get jtaged. It's always something stupid. I updated bootloaders and must have dorked them while flashing. None of my computers will see it when in download mode. (yes, tried multiple computers, multiple cables, multiple drivers, etc...)
I didn't notice that till you said it.
Click to expand...
Click to collapse
Gah, is there UBM available for the epic4g?
FBis251 said:
Gah, is there UBM available for the epic4g?
Click to expand...
Click to collapse
I don't see it on mobiletechvideos, but @AdamOutler has plans for epic4g.
The common parts between this device and epic4g is that 8Gb (gigabit! 1GB... gigabyte) onenand-flex.
The problem download mode on this epic4g is having must be because I wrote a bad bootloader or the writing of the bootloader got interrupted somehow, as I can get into download mode, but the usb drivers always have problems enumerating the port.
I don't get much data from my windows computer, but on linux and mac os x I've got some pretty good indications that either something is wrong with the usb port on the epic4g or the bootloader is dorked. I'm able to boot the device with my usb uart setup and can confirm that both normal boot and download mode seem to setup correctly (with regards to what outputs from the uart) and I can access the SBL prompt.
I really wish there was a way to transfer a new kernel or bootloader via usb uart so that I could either fix my softbricked kernel or flash new bootloaders via SBL prompt, but I'll have to somehow get money to send this guy off to mobiletechvideos to get jtaged and request UBM.
bhundven said:
I don't see it on mobiletechvideos, but @AdamOutler has plans for epic4g.
The common parts between this device and epic4g is that 8Gb (gigabit! 1GB... gigabyte) onenand-flex.
The problem download mode on this epic4g is having must be because I wrote a bad bootloader or the writing of the bootloader got interrupted somehow, as I can get into download mode, but the usb drivers always have problems enumerating the port.
I don't get much data from my windows computer, but on linux and mac os x I've got some pretty good indications that either something is wrong with the usb port on the epic4g or the bootloader is dorked. I'm able to boot the device with my usb uart setup and can confirm that both normal boot and download mode seem to setup correctly (with regards to what outputs from the uart) and I can access the SBL prompt.
I really wish there was a way to transfer a new kernel or bootloader via usb uart so that I could either fix my softbricked kernel or flash new bootloaders via SBL prompt, but I'll have to somehow get money to send this guy off to mobiletechvideos to get jtaged and request UBM.
Click to expand...
Click to collapse
Hmm that's odd, I would have imagined that the sgs4g and epic4g would be similar enough that UBM would have been easy for the epic4g also.
Ha, no indication from windows. Figures.
How difficult would it be to JTAG it yourself?
FBis251 said:
Hmm that's odd, I would have imagined that the sgs4g and epic4g would be similar enough that UBM would have been easy for the epic4g also.
Click to expand...
Click to collapse
Yea, the xOM resistors are fairly similar. I don't have my iron with me, but I'm not sure I can get those tiny little resistors.
I should find some old electronics to buff my skills.
FBis251 said:
Ha, no indication from windows. Figures.
Click to expand...
Click to collapse
bleh...
FBis251 said:
How difficult would it be to JTAG it yourself?
Click to expand...
Click to collapse
If I only had a jtag... (to the tune of: if I only had a brain)
Even then, I'd have to figure out where the jtag pads are, and I need to get some smaller lead wires.
So... Back to being on topic...
@daothanhduy1996 and @DJLamontagneIII: could you guys point me to your aries kernels, and I will work on some fixes for ya
hmm... Should i help out?
bhundven said:
So... Back to being on topic...
@daothanhduy1996 and @DJLamontagneIII: could you guys point me to your aries kernels, and I will work on some fixes for ya
Click to expand...
Click to collapse
Here is mine, forked from DJ's. And thanks so much Bryan . (There r some commits that might looks stupid tho ^^)
Sent from my SGH-T959V using Tapatalk 2
So I not only got the bugs from Aries, but also went through the Dev section and compiled a list of all the kernels released for this phone, what version they are for, and links to the threads(although I didnt read through the 100s of pages of these threads for bugs)
I have it set up like the updated bible for kernels.
Should I post this on our 1 page wiki or as a thread the should get stickied? I'm still a little new here so I thought I should ask.
Also, should someone make a dev thread for Aries so you guys can work together outside of q and a section? It may make it easier for other devs that wanna help or for people that can test it.
Sent from my SGH-T959V using xda app-developers app
quoaz said:
So I not only got the bugs from Aries, but also went through the Dev section and compiled a list of all the kernels released for this phone, what version they are for, and links to the threads(although I didnt read through the 100s of pages of these threads for bugs)
Click to expand...
Click to collapse
Most of the kernels on the first few pages are the same kernel. Minor differences.
quoaz said:
I have it set up like the updated bible for kernels.
Click to expand...
Click to collapse
Where?
quoaz said:
Should I post this on our 1 page wiki or as a thread the should get stickied? I'm still a little new here so I thought I should ask.
Click to expand...
Click to collapse
There are many pages on our wiki. So I'm kind of confused.
quoaz said:
Also, should someone make a dev thread for Aries so you guys can work together outside of q and a section? It may make it easier for other devs that wanna help or for people that can test it.
Click to expand...
Click to collapse
The developers here don't really collaborate on XDA, because of trolls. We usually just collaborate on github. Devs that want to help should just work together on github. We've always done it that way, and it works great. We've always posted how to build from source on the wiki and usually post test builds for users to try.
bhundven said:
Most of the kernels on the first few pages are the same kernel. Minor differences.
Click to expand...
Click to collapse
I didn't include all of the first few ones in the list because they were so similar, I at least read the op of each kernel.
bhundven said:
Where?
Click to expand...
Click to collapse
Right now, in a text document on my desktop.
bhundven said:
There are many pages on our wiki. So I'm kind of confused.
Click to expand...
Click to collapse
I'll have to explore the wiki again then. As It only seems set up like one big long page to me at the moment.
bhundven said:
The developers here don't really collaborate on XDA, because of trolls. We usually just collaborate on github. Devs that want to help should just work together on github. We've always done it that way, and it works great. We've always posted how to build from source on the wiki and usually post test builds for users to try.
Click to expand...
Click to collapse
This is amazing, I'm going to check out github right after this.
This post has been the most informative post for me to date!
Development has begun! Find the new thread here!
Hey P9 users,
I see that you guys don't have much development going for you guys. How would y'all like it if I cooked up a kernel? Things I will need:
Patience because I don't have the device:
I will not add anything that could possibly brick your phone. All of my kernels are not like most that you see out there in the forums. It's more of an optimized kernel rather than a custom kernel.
Testers (follows suite with not actually having the device):
Self explanatory from above. There shouldn't be any problems, but if one does arise, I will need logs.
Hype and honesty:
Just kidding about the hype part, but the second part is what is really important. If you feel no difference after flashing the kernel, then let me know! I'd much rather you guys tell me it sucks instead of riding a bandwagon.
i would be pleased to test a optimized kernel!
paratox said:
i would be pleased to test a optimized kernel!
Click to expand...
Click to collapse
Alrighty, got something fresh out the oven. Doesn't have much changed, except for the fact that it's compiled with Linaro 4.9 and has a lot of compiler optimizations. If this boots and runs fine, I will create a development thread.
abyss-caf-huawei-p9-nightly-20160822.img
GitHub Source
If it does not boot, flash the stock kernel image or @paulobrien's updated kernel
Installation is the same as any other kernel:
paulobrien said:
You now have a new boot image (abyss-caf-huawei-p9-nightly-20160822.img). All that's left is to flash it to your device! Reboot to bootloader (either using 'adb reboot bootloader' or by powering on with volume down held).
Flash using 'fastboot flash boot abyss-caf-huawei-p9-nightly-20160822.img'
Then reboot using 'fastboot reboot'. Job done! In the About screen of settings you should see the date of the abyss-caf kernel and details of your my build machine.
Click to expand...
Click to collapse
Lovely, let's get stuff going! Would love to see more active development for the P9 (which agreed really are quite stagnant).
I working on something too, but it takes too much time.
emilrune said:
Lovely, let's get stuff going! Would love to see more active development for the P9 (which agreed really are quite stagnant).
Click to expand...
Click to collapse
Yes! Such a great device with little development is quite a shame.
dkionline said:
I working on something too, but it takes too much time.
Click to expand...
Click to collapse
Have to agree. It took a lot longer for me to set up this kernel for building. Very interesting, but I've got it under my control
I just need to know if this boots. If it does, I will start to overhaul it with more advanced changes
Care to tease us with some of your more Advanced stuff?
the problem is, what works with biglittle and what not. some snapdragon optimizing is not same as kirin. Im still in contact with zz for zzmove.
Maybe its easy to test and give u logcat?
Ty for taking your time, i really hope more developers will come. Im waiting on Cyanogenmod and a good kernel i hope yours will turn out great.
I miss having my HTC One X with root but for now i live with a stock huawei experience with Nova launcher and theme and i disabled many things with debloater.
I wish more developers would get their hands on it since the phone is cheap, i bought it for 2300kr = 275 dollars here in Denmark, and for 275 dollars you get a lot.
emilrune said:
Care to tease us with some of your more Advanced stuff?
Click to expand...
Click to collapse
Depends what people are looking for . I am limited and slowed because I don't own the device, but it is possible to add hotplugs and governors easily. Features like KCAL control, double tap to wake, etc. can eventually be implemented with the help of you guys and logs.
dkionline said:
the problem is, what works with biglittle and what not. some snapdragon optimizing is not same as kirin. Im still in contact with zz for zzmove.
Maybe its easy to test and give u logcat?
Click to expand...
Click to collapse
Whether it is Kirin or Qualcomm really does not affect the what can go into the kernel as much as it would affect ROM optimizing. Certain CAF kernel patches that are supposedly specific for Snapdragon devices can also be implemented into kernels for other devices as well. The Snapdragon 652 is the closest non-kirin relative to Kirin 955, so porting patches from a 652 kernel would be best.
Hugajohan said:
Ty for taking your time, i really hope more developers will come. Im waiting on Cyanogenmod and a good kernel i hope yours will turn out great.
I miss having my HTC One X with root but for now i live with a stock huawei experience with Nova launcher and theme and i disabled many things with debloater.
I wish more developers would get their hands on it since the phone is cheap, i bought it for 2300kr = 275 dollars here in Denmark, and for 275 dollars you get a lot.
Click to expand...
Click to collapse
It is a hard device to get in North America. I think the Honor 8 is the first one to break grounds over here in the states (Canada is even more limited than the US so not even sure if I can find one here).
I think whole community would be thankful even for this topic. This is a fairly new device and would be lovely to see some development for it...
furkey said:
I think whole community would be thankful even for this topic. This is a fairly new device and would be lovely to see some development for it...
Click to expand...
Click to collapse
I'm hoping to break the ice in terms of development, but I really need someone to test what I posted earlier before I can continue :silly:. I need to know if it boots so I know i'm on the right track.
kwoktopus said:
I'm hoping to break the ice in terms of development, but I really need someone to test what I posted earlier before I can continue :silly:. I need to know if it boots so I know i'm on the right track.
Click to expand...
Click to collapse
I think that is the easy part. Since the q&a part is the skipped part among other parts, it would be easier to find once you post in the development section
If I wouldn't buy the phone TODAY (yes I bought it today ) I would be gladly test it out but it is like a principle for me that I use the phone as it is for a couple of months.
furkey said:
I think that is the easy part. Since the q&a part is the skipped part among other parts, it would be easier to find once you post in the development section
If I wouldn't buy the phone TODAY (yes I bought it today ) I would be gladly test it out but it is like a principle for me that I use the phone as it is for a couple of months.
Click to expand...
Click to collapse
That's a very good principle that I USE to have as well :laugh:! Enjoy your device while it still feels foreign to you! I hate how after I use the phone for a couple of months it feels old to me.
My current principle is to make sure things are stable before I post in development, so I will wait until I have confirmation that this boots first :fingers-crossed:
kwoktopus said:
That's a very good principle that I USE to have as well :laugh:! Enjoy your device while it still feels foreign to you! I hate how after I use the phone for a couple of months it feels old to me.
My current principle is to make sure things are stable before I post in development, so I will wait until I have confirmation that this boots first :fingers-crossed:
Click to expand...
Click to collapse
It's my first phone with 2.5 D display and it is blazing fast right now However I am addicted to flashing things and I am afraid I will touch my phone's virginity with this old addiction I will hold on to that principle as long as I can
However, it breaks my heart when I have a look to development section since ,as I told before, my rom addiction. I believe it can be (I mean your kernel) a little push for other developers to cook some roms
And for the last, It would be beyond perfect if you could port stockish android like CM or other roms
furkey said:
It's my first phone with 2.5 D display and it is blazing fast right now However I am addicted to flashing things and I am afraid I will touch my phone's virginity with this old addiction I will hold on to that principle as long as I can
However, it breaks my heart when I have a look to development section since ,as I told before, my rom addiction. I believe it can be (I mean your kernel) a little push for other developers to cook some roms
And for the last, It would be beyond perfect if you could port stockish android like CM or other roms
Click to expand...
Click to collapse
I will definitely need the device in order to build any AOSP roms, it's a nightmare without it. Also, I am a Linux developer (C based), and have limited knowledge in device tree bring up.
kwoktopus said:
Alrighty, got something fresh out the oven. Doesn't have much changed, except for the fact that it's compiled with Linaro 4.9 and has a lot of compiler optimizations. If this boots and runs fine, I will create a development thread.
abyss-caf-huawei-p9-nightly-20160822.img
GitHub Source
If it does not boot, flash the stock kernel image or @paulobrien's updated kernel
Installation is the same as any other kernel:
Click to expand...
Click to collapse
It boots perfectly!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lightlance7 said:
It boots perfectly!
Click to expand...
Click to collapse
Development is full speed ahead now, see you guys in development section
Faptastic development kudos! Will see you all in the dev section