Hi built AOSP 8.1 and calls have no sound at all wondering if anyone know's the fix or can point me to some commits that could fix it thanks!
liam_davenport said:
Hi built AOSP 8.1 and calls have no sound at all wondering if anyone know's the fix or can point me to some commits that could fix it thanks!
Click to expand...
Click to collapse
Yup its easy
joe_pacino said:
Yup its easy
Click to expand...
Click to collapse
Oh cool, dude with zero commits says its easy. Bet it's easy when you're just taking others work and posting it as your own.
HolyAngel said:
Oh cool, dude with zero commits says its easy. Bet it's easy when you're just taking others work and posting it as your own.
Click to expand...
Click to collapse
Breathe
If you know how to fix just share man, if you don't then dont. don't have to get mad about it. but you obviously don't care about open source or the community. There would be no roms or kernels if everyone just posted googles source with no changes.
HolyAngel said:
If you know how to fix just share man, if you don't then dont. don't have to get mad about it. but you obviously don't care about open source or the community. There would be no roms or kernels if everyone just posted googles source with no changes.
Click to expand...
Click to collapse
Revert feb 28 commit from razor on vendor by the way the trees yall see are for my testing purposes i have a paid github account which means i can have private trees i find errors and use the test trees to fix errors then i properly add everything another thing people dont know is people have things going on in their lives like i dont know machine ****s the bed all my work was on drives i rarely ever commited to github cause i sucked at picking so i saved all my crap locally and dident bother to upload to git since their was really no need then i lost everything and had to use github alone to try and make trees so when i got a machine i could just build then edit once i set up an if yall felt like i was doing something wrong u could of messaged me and talked to me about instead of pissing on how my trees are. And running traps about me cause one thing about me im humble and ill listen and take advice and im willing to learn bout dont talk **** about me thats some kids ****
joe_pacino said:
Revert feb 28 commit from razor on vendor by the way the trees yall see are for my testing purposes i have a paid github account which means i can have private trees i find errors and use the test trees to fix errors then i properly add everything another thing people dont know is people have things going on in their lives like i dont know machine ****s the bed all my work was on drives i rarely ever commited to github cause i sucked at picking so i saved all my crap locally and dident bother to upload to git since their was really no need then i lost everything and had to use github alone to try and make trees so when i got a machine i could just build then edit once i set up
Click to expand...
Click to collapse
Which of the 4 commits for feb 28th? all of them? just one?
Understandable on the rest. But definitely should work on fixing that if you're posting stuff publicly. no one cares if commits suck. if you're gonna be posting stuff online you should have your source available for the public, regardless if its kernel(this is actually required by GPL) or rom source. Otherwise it just looks like you either didn't do anything, or don't care and just wanna take others work and not contribute anything back.. Shouldn't care if someone kangs your work, hopefully they give credit where credit is due.
HolyAngel said:
Which of the 4 commits for feb 28th? all of them? just one?
Understandable on the rest. But definitely should work on fixing that if you're posting stuff publicly. no one cares if commits suck. if you're gonna be posting stuff online you should have your source available for the public, regardless if its kernel(this is actually required by GPL) or rom source. Otherwise it just looks like you either didn't do anything, or don't care and just wanna take others work and not contribute anything back.. Shouldn't care if someone kangs your work, hopefully they give credit where credit is due.
Click to expand...
Click to collapse
Remove apks from vendor keep everything to do with calling embms or just revert whole commit it dosent affect anything and i apoligize for my words im pissed like i said somebody could of took time out to message me i always do whatever i can to help and share my work and i only though i had to share the trees i was using not the edits i made i though that only pertained to kernels my trees are set to private anyway
Still no in-call audio with that revert. Anyone got anything else?
Try selinux permissive(if below doesn't work). Obviously not a real/permanant fix but just a workaround. Here's my tree (its just razorloves tree with updates + reverted commit) you can try it. Here's my vendor tree: https://github.com/shagbag913/proprietary_vendor_google
Then you have to add to the proprietary_files in device tree (just revert this: https://github.com/shagbag913/du_marlin/commit/9bfeabb076ff4a880fb61798f08b625baeb156db This fixed my problems with DU let me know if it helps
EDIT: BROKEN LINK
shagbag913 said:
Try selinux permissive(if below doesn't work). Obviously not a real/permanant fix but just a workaround. Here's my tree (its just razorloves tree with updates + reverted commit) you can try it. Here's my vendor tree: https://github.com/shagbag913/proprietary_vendor_google
Then you have to add to the proprietary_files in device tree (just revert this: https://github.com/shagbag913/du_marlin/commit/9bfeabb076ff4a880fb61798f08b625baeb156db This fixed my problems with DU let me know if it helps
EDIT: BROKEN LINK
Click to expand...
Click to collapse
sadly that didnt fix it either. setting permissive nor that vendor tree. Still no in-call audio. Trying to build pure stock AOSP here..
I did compare device tree's and not seeing anything different there. Thinking the issue is elsewhere. Framework or app but no idea. Building it blind myself sadly so hard to say.
HolyAngel said:
sadly that didnt fix it either. setting permissive nor that vendor tree. Still no in-call audio. Trying to build pure stock AOSP here..
I did compare device tree's and not seeing anything different there. Thinking the issue is elsewhere. Framework or app but no idea. Building it blind myself sadly so hard to say.
Click to expand...
Click to collapse
Do you get incoming calls?
shagbag913 said:
Do you get incoming calls?
Click to expand...
Click to collapse
yes just no audio
Try to get a logcat while incall
shagbag913 said:
Try to get a logcat while incall
Click to expand...
Click to collapse
Logcat
liam_davenport said:
Logcat
Click to expand...
Click to collapse
Can u upload the device tree to github? I mifht see a problem not.sure yet
shagbag913 said:
Can u upload the device tree to github? I mifht see a problem not.sure yet
Click to expand...
Click to collapse
Gonna drop AOSP for now too much work alone
Thanks for time and help tho Appreciated ^^
liam_davenport said:
Gonna drop AOSP for now too much work alone
Thanks for time and help tho Appreciated ^^
Click to expand...
Click to collapse
I will keep looking at the logs and see if I can figure something out
shagbag913 said:
I will keep looking at the logs and see if I can figure something out
Click to expand...
Click to collapse
If you need anything just PM me will try to reply ASAP
Wait this is just straight aosp? You guys should be using aosp trees then unless you already are
Related
Hey Guys,
I've noticed many other phones have guides explaining how to download and compile Android for their phones including proprietary drivers and misc files. I know CM6/CM7 and MIUI all are very clearly doing this but I was wondering if we could get any kind of documentation like that for the Epic? It doesn't have to include any super detailed coding information other then how to download AOSP, Samsungs required drivers, and build them into a "working" rom of some kind..
The drivers and kernels you guys have been using so far must be available via some kind of git command..
I'd love to be able to compile a ROM just to learn about it lol.
Think a quick and dirty write up for compiling a rom could happen? I think it would really help incoming developers and newbies alike.
+1 on this.
+1 as I would like a good starting point...
Samsung Epic using Team Viper's latest ROM and kernel
I'm glad to see some support for this. I sincerely hope a developer takes this seriously enough to help us out!
I'm answering my own question here
Check it out... it's how to build CM for the epic. Anyone interested in learning the process could probably follow this guide and accomplish it. Took it from the CM post in General.
http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Epic
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
mxcoldhit said:
Thank you! That is very interesting. I must try it!
Sent from my Shoe.... I mean my Samsung Epic
Click to expand...
Click to collapse
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
TheDub said:
I'm trying it now for fun... still downloading the source... the first repo sync takes a while, I believe it's a few GB's in size..
I don't believe this includes the kernel though... I'm sure it's posted somewhere for those interested in looking at it.. just gotta dig around.
Click to expand...
Click to collapse
way to go, man. keep us posted...
yogi2010 said:
way to go, man. keep us posted...
Click to expand...
Click to collapse
Steps seem to be broken.. the ./get-rommanager and ./getgooglefiles -v HDPI or whatever both don't work because of broken web links.
Seems this hasn't been updated in a while..
I tried to go on without them following the directions but it doesn't work, says something about the vibrant? idk.. I think the directions would need updating to work properly.. at least the code was fun to look at.
Still hoping a developer can teach us how to compile lets say just 100% AOSP for our phones using our progress so far with the drivers.. i think the drivers need to be their own branch of code so all devs can use them for their own roms.. maybe it's already like this? Idk pretty new to rom compiling.
Hi
This is my KANG of CM9 with JackpotClavin's tools.
http://www.mediafire.com/?jbd9qulr7tjqz16
I forgot to add SystemUI so you can add it manually from JackpotClavin github or if someone want, I can upload the KANG with SystemUI.
Nothing add to the kang, It is just to try what is new on CM9, not for daily use.
This kang has Gapps.
With love, JrM.
So is this a rom I can flash or does the UI need to be added first
Sent from my Amazon Kindle Fire using xda premium
You can flash it
Sounds like a deathtrap to me.
Maybe it is a trap ! Oh yes what a joke.
I am uploading Kang with JackpotClavin SystemUI to have sound toolbar and lockscreen without camera app.
Thelgow said:
Sounds like a deathtrap to me.
Click to expand...
Click to collapse
Yeah, deathtrap...
you know he just compiled the cm9 that all the cm9 devs are working on and have been releasing every now and again. So basically this is the most up to date cm9 you can get right now with all the fixes from the 2-19 build plus anything else they have done so far. Granted it wasn't released by them yet, but that doesn't mean it is bad, just that they didn't feel it had enough changes to warrant a new release. CM9 is opensource, anyone with know-how can compile it.
Yes that Kang is not so bad ... I just forgot to change systemUI, coz i dont really care :/
When someone compiles a ROM and wants to share it...if you don't have anything nice to say just don't say it. Otherwise you run risk of looking inept or worse...discouraging people from sharing stuff.
If its a bad ROM then the community will make it known. If it a ROM that simply works..then don't poo all over it without knowing what you are talking about.
androidcues said:
When someone compiles a ROM and wants to share it...if you don't have anything nice to say just don't say it. Otherwise you run risk of looking inept or worse...discouraging people from sharing stuff.
If its a bad ROM then the community will make it known. If it a ROM that simply works..then don't poo all over it without knowing what you are talking about.
Click to expand...
Click to collapse
I completely agree and thanks.
argentina_ said:
Hi
This is my KANG of CM9 with JackpotClavin's tools.
http://www.mediafire.com/?jbd9qulr7tjqz16
I forgot to add SystemUI so you can add it manually from JackpotClavin github or if someone want, I can upload the KANG with SystemUI.
Nothing add to the kang, It is just to try what is new on CM9, not for daily use.
This kang has Gapps.
With love, JrM.
Click to expand...
Click to collapse
Dont worry bout the haters, keep the builds coming, thanks a bunch, i dont want to build my own
Nice, thanks for this release
Sent from my PC36100 using xda premium
androidcues said:
When someone compiles a ROM and wants to share it...if you don't have anything nice to say just don't say it. Otherwise you run risk of looking inept or worse...discouraging people from sharing stuff.
If its a bad ROM then the community will make it known. If it a ROM that simply works..then don't poo all over it without knowing what you are talking about.
Click to expand...
Click to collapse
Thats what I was saying, I just laced it with much more sarcasm and annoyance.
I totally digged your sarcasm.
Hey,
from which github repos are you cloning? The JackpotClavin/[email protected] hasn't been updated for a while, the last (cm9-02-*) builds are done from that device/vendor tree. In the long term i want to switch to [email protected], but the device tree there has the flicker screen issue (it's different form JC's/mine, as JackpotClavin did a clean setup, didn't find the problem yet). To keep up with the latest changes you also need things like modified wpa_supplicant_6 to get ad-hoc wifi to work. The best way to get up to date would be if you drop that local_manifest.xml in your .repo folder and do a repo sync. (But as said, it uses the wrong device/vendor tree, but you can just replace KFire-Android/device-amazon-otter and KFire-Android/android_vendor_amazon_otter with the right one). it also uses a modified frameworks/base which includes the latest SystemUI changes+other stuff. If you have any problem ask on IRC, but i won't be around there this weekend (other people there can also help you).
Cheers,
sitic/Nind
nind said:
Hey,
from which github repos are you cloning? The JackpotClavin/[email protected] hasn't been updated for a while, the last (cm9-02-*) builds are done from that device/vendor tree. In the long term i want to switch to [email protected], but the device tree there has the flicker screen issue (it's different form JC's/mine, as JackpotClavin did a clean setup, didn't find the problem yet). To keep up with the latest changes you also need things like modified wpa_supplicant_6 to get ad-hoc wifi to work. The best way to get up to date would be if you drop that local_manifest.xml in your .repo folder and do a repo sync. (But as said, it uses the wrong device/vendor tree, but you can just replace KFire-Android/device-amazon-otter and KFire-Android/android_vendor_amazon_otter with the right one). it also uses a modified frameworks/base which includes the latest SystemUI changes+other stuff. If you have any problem ask on IRC, but i won't be around there this weekend (other people there can also help you).
Cheers,
sitic/Nind
Click to expand...
Click to collapse
Hi, I said I just made it for fun and if people want to try CM9 Change. It didnt include kinfle fire changes.
I can make a KANG with all changes from CM9 and Kindle fire, but :
First,I hate ppl who insults my job without explaination and english is not my langage so i cant debate.
Anyway thanks all for your replies, and if someone wants a Kang with all changes include (Kindle fire and CM9), just PM me, i will not post anymore.
argentina_ said:
Hi, I said I just made it for fun and if people want to try CM9 Change. It didnt include kinfle fire changes.
I can make a KANG with all changes from CM9 and Kindle fire, but :
First,I hate ppl who insults my job without explaination and english is not my langage so i cant debate.
Anyway thanks all for your replies, and if someone wants a Kang with all changes include (Kindle fire and CM9), just PM me, i will not post anymore.
Click to expand...
Click to collapse
Hey, don't worry about them, new devs are always welcome. (The problem was that they/we did not know what exactly you do/want to do.)
Show up in #kindlefire-dev channel on freenode to say hi or ask questions, that's the place we hang around and it is the best way to get up to date what we are doing currently and where help is needed. (Also don't worry, we won't harm you there)
In regard to CM9: You can do whatever you want with it, as it uses the apache open source license <3
Can you add the systemui in kang?
Sent from my ICS Kindle Fire using XDA premium.
Can you please add some screen shots and mention what works and what doesn't? Thank you
Please don't listen to rude a$$ people...any new dev work IS appreciated by most here...
Sent from my Amazon Kindle Fire using xda premium
hola
No te desanimes El Tom estate buenisimo, sigue adelante El problems sequence testosterone tonton screen que son Los mejores y tremendous que alguien talentoso les quite service El menorah sighed adelante!!!
This phone will never die
Synthetic.nightmare
I created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM Synthetic.nightmare if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
I have modified Synthetic-nightmare's ICS kernel, to hopefully support B2G here is the link
reserved
Mine
EDIT: Making this my reserve
Synthetic.Nightmare said:
This "build process" is just you syncing your repositories. There's still a mountain to climb once you get past this. It seems your manifest is off. When adjusting it look for things it says it cannot fetch. From there check to see if you got the repos and revisions and whatnot written out correctly in the xml in your manifest.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
hmm i will look at that here is my manifest https://github.com/deadman96385/b2g-manifest/blob/master/default.xml
Very exciting! Thank You and good luck.
Fixed some errors
Ok i fixed all of the errors except the one in OP!
Holy crap this is awesome. I need to thank all the devs here for your hard work. This is just so amazing.
Sent from my Toasted Marshmallow using XDA
Looking good brother hopefully we will get this bad boy up and running soon...
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
b4d455b345t said:
Is this actual FirefoxOS? Or an Android rom of some sort? Didn't see much info in the OP lol
Click to expand...
Click to collapse
Actual OS developed by Mozilla.
saranhai said:
Actual OS developed by Mozilla.
Click to expand...
Click to collapse
Ohhh shizzzz. :victory:
Our Glaciers would be able to rock 2 OSs (Android & Firefox) Can't wait.
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
THEindian said:
A couple potential reasons for the repo sync error if you are still getting that:
First off.
Virtual or dual boot?
Which version of Ubuntu?
Laptop or Desktop?
Hard wired or wifi?
Potential Problems:
Unstable Wifi/ethernet driver- Recompile the driver
Wifi/router is going down- Keep the router awake?
MOST PROBABLE: Crappy repo file- Just delete the folder/make a new folder if you have space and make a fresh repo file and try to pull it down again.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Also, how many processor cores do you have? do repo sync -j(#of processor cores + 1)
Click to expand...
Click to collapse
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Synthetic.Nightmare said:
a pleasant update.
I have created an organzation on github alongside deadman and Awesome and rebased to the lovely aospX source code (for stability).
Tonight deadman worked along with me to try and get our script all set up to properly repo sync (+some other things) and after a bit more work, I have managed to get it to where we can sync using the proper b2g command ./config.sh as stated correctly in the readme. This is kind of a big deal, because before, I was just working around some of the scripts doing things the traditional android way lol. There's still parts that are needed to be rolled back and stuff and who knows what there might be broken even after we get all that worked out, but I thought that there might be some other devs around here that may be interested in helping bring this over to us and possibly others who want to keep track of this.
Links:
Click here to start preparing for/downloading the source to help us with development
Click here to see the b2gX organization and keep track of development
You can see more by clicking any of the member's githubs and checking out their activity.
Devs: PM me if you want in. My team is always willing to collaborate with this who wish to contribute.
That's about all I can think of for now. Hopefully, we can bring you all some more good news soon.
Remember these links are here for you to keep track of development, so I don't wanna hear about no ETA's lol.
Click to expand...
Click to collapse
deadman96385 said:
I actualy have a Triboot,Ubuntu, Desktop,Hard Wired, i have deleted the folder am repulling down on to my extra hardrive. will edit when it finsh's.
Click to expand...
Click to collapse
Do you guys mind if i come on this project with you? This sounds very interesting...
I'll be downloading this at work tomorrow - 64 bit Xubuntu 11.10 (single boot), desktop, wired.
yeah this looks good, may have to give this one a crack in the near future
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
ggolemg said:
Open web os ported to galaxy nexus
http://www.theverge.com/2012/9/28/3425382/open-webos-galaxy-nexus-port
Sent from my Toasted Marshmallow using xda app-developers app
Click to expand...
Click to collapse
Just saw that on Cnet
Sent from my Dark JellyBellyG1 using xda app-developers app
Howdy dudes! Any news?
htc 2pst2.
any custom roms, anywhere?
I've searched and searched....they all seem shady, with "complete these 7 offers" before downloading the rom type of stuff.
Also, if sticking with stock--just remove bloatware, add various rooted apps, etc. <--that's the best case?
Any thoughts or advice are greatly appreciated. Thanks!
I requested the kernel source from HTC, as they don't have anything for the desire 530. I am interested in building both a CM13 and CM 14 ROM for this device.
Fullmetal99012 said:
I requested the kernel source from HTC, as they don't have anything for the desire 530. I am interested in building both a CM13 and CM 14 ROM for this device.
Click to expand...
Click to collapse
Really man that's great
Muhammad Hussain said:
Really man that's great
Click to expand...
Click to collapse
HTCDev contacted me today to tell me they forwarded it to the escalation team. I'm hoping that HTC pulls through and provides the kernel source.
I just need to get my build rig running so I can start pulling the CM repos and setting up the device and kernel trees.
Going to start with CM13, since the kernel will be for Android 6.0.1, but I will try a CM14 build at some point.
Fullmetal99012 said:
HTCDev contacted me today to tell me they forwarded it to the escalation team. I'm hoping that HTC pulls through and provides the kernel source.
I just need to get my build rig running so I can start pulling the CM repos and setting up the device and kernel trees.
Going to start with CM13, since the kernel will be for Android 6.0.1, but I will try a CM14 build at some point.
Click to expand...
Click to collapse
Lets collaborate on this. I also requested the source and my request was escalated last Monday so I should have a copy very soon. Already have my build environment and cm 13 source sync'd (bbqlinux) I'll put the source up if I get it before you
xerolath said:
Lets collaborate on this. I also requested the source and my request was escalated last Monday so I should have a copy very soon. Already have my build environment and cm 13 source sync'd (bbqlinux) I'll put the source up if I get it before you
Click to expand...
Click to collapse
Sounds good. My Build rig is currently down while I redo my den. my desk broke yesterday, and I can't buy a new one until friday.
Fullmetal99012 said:
Sounds good. My Build rig is currently down while I redo my den. my desk broke yesterday, and I can't buy a new one until friday.
Click to expand...
Click to collapse
is there any progression
I'm willing to help with testing.
DWil's Magic Carpet
wilbigdaddy2000 said:
I'm willing to help with testing.
DWil's Magic Carpet
Click to expand...
Click to collapse
Me too
Testing
I will also test. just as long as text and voice are reliable because my wife is pregos. lol. I'm pissed that T-Mobile didn't put video calling on it like most other android 6.0 have built in. some other things also. speaker phone needs help. If you boost the mid's it really helps. also memory management is poor. and I know the SD210 can go faster then 1.1ghz my wife has an lg that runs 1.2 something so there is a few examples of things to think about when building rom. I would build one too but I have no time going back to school to finish my EE degree.
Muhammad Hussain said:
is there any progression
Click to expand...
Click to collapse
I haven't recieved any word from HTC about kernel source, so I'm stuck until then.
Still waiting on HTC to provide the kernel source, however I am going to attempt to build if I can manage to pull the built kernel data from the device.
currently working on setting up my Cyanogenmod build environment.
Fullmetal99012 said:
Still waiting on HTC to provide the kernel source, however I am going to attempt to build if I can manage to pull the built kernel data from the device.
currently working on setting up my Cyanogenmod build environment.
Click to expand...
Click to collapse
Sent a request to HTC for a status update and the agent replied that I "Just have to keep checking the website" and that there was nothing more they could do.
Anyone have any contacts with HTCDev that would be willing to share?
Still no response from HTC Dev? Ill try too. Maybe if there is enough requests they will send it. So we should all start bugging them.
Kernel source is out now
zebidybob said:
Kernel source is out now
Click to expand...
Click to collapse
Yeap, the kernel source is already there
So is anyone making a cm13/14 ROM for this phone now that the source code is out
So have devs begun getting us a custom rom? I'm eager to test.
DWil's Magic Carpet
I appreciate every developer who works on this, you guys are the best!
I am in the process of building Lineage OS/Cyanogen for the Desire 530. My daughter is almost 2 and she occupies most of my attention at the moment. Be patient and I will post updates once I'm closer to a "Alpha" and "Beta" phases of release.
If anyone with the VZW(Verizon) Desire 530 who has had prior compiling experience would contact me via PM that would be helpful. I have the T-Mobile variant..
I also need to figure out why Family Mobile network locked their devices.
I am also searching for a few Droidoholics who have [How-To] and [TuT](Tutorial) experience to help populate the Device Forums.
Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.