Develop Bugs

Compiling Android for the Epic.

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.

Unfinished Business - I'm done, have at it.

Ok, I've come to realise, after some prodding from my wife, that I've been just way to focused on all of these projects I've begun, searching for a way to create that next great thing, and always managing to fall just short of achieving it. At this point, I've decided to take a step back, and calm down on working with my A100.
So, I put everything I've been working on into 1 zip file, so anyone who wishes may begin their own work on anything in there.
The projects that are currently in there in various forms:
Jellybean ROM, yeah, I was working on getting a jellybean ROM for us A100 users. Never got it to boot all the way, worked on it for probably 6 hours yesterday. Thanks to randomblame for this.
AOKP A500 port, also semi completed, it never booted all the way, stuck on boot animation.
Extracted A100 CM9 boot.img folder, with the ramdisk and kernel, for use with the above two projects, or any other porting you wish to do.
DSIXDA Kitchen for linux, useful abilities include extracting and building boot.img files. Can be used for any number of things that I never used it for, however its included anyways. Try out modding some stock ROMs or something, just play around with it.
Morfic's Bin Tools, a full set of every tool you could ever want, for use with ADB or any number of things, if you can think of it, Morfic included it. Huge thanks to Morfic for this.
CWM Touch Recovery .img I created this as an experiment for/with another user, and its actually posted up in my Nightly Builds posting, however its been reported SD card doesn't mount on it. The partitions are all correct so it won't brick, but enjoy playing with it. Includes all of the files for it, as well as the ready to flash .img file.
Couple of documents, 1 being a complete partition map as reported by TWRP Recovery, useful for knowing which device blocks are which partition.
Other document is cat /proc/partitions and cat /proc/cmdline, output is from my working device, and can be used to verify bootloader information as well as raw partition information, if available. Comes from my bootloader flashed and unlocked A100, and as you can see, reports A200, and as far as I can tell, the wrong CPUID.
Anyone can feel free to take a look, and see what they may want to finish, or not. I give full consent to use anything in this zip file, as I didn't really create it, but I give it anyways. Anything in this zip is, I think, GPL compliant (such as the CM9 kernel and aokp with CM9 kernel, jellybean with CM9 kernel, etc).
CWM Touch was created by the bot, so I hold no credit for this either, only the 2 document files are truly created by me, and I give full consent for their use.
If you do manage to create something out of any of this, all I ask is a thanks somewhere in the post :good:
So whats next for me?
Well, I'm taking a break for awhile. I'll continue the Nightly CM9 Builds until official nightlies begin, and I'll keep updating the Guides as I have the time, and I'll fix any releases (like my scripts) as I find issues or issues are reported. The only thing I am actively pursuing is the bricking issue. I'm still looking for, and hoping to get, a bricked A100 for testing, as my request post mentions, I would love a donated unit (or loaned) for some testing. Also, the battery issue, as it does occur somewhat often, I would love a chance to work on one of the A100s with the battery charge issue.
Oh, and I'll still be around XDA, helping where I can as always. Anyone can feel free to add me for gtalk, twitter, google+ or whatever else, and feel free to ask questions, for help, or just say what's up and chat! I also tend to visit #iconia-dev on freenode.
Ok enough blabbing gimme your shiz!
Unfinished Business 421 MB zip file, with zips and random ish inside.

:'(
Sent from my A100 using Tapatalk 2

Thanks for all the hard work, man. I've seen soo many posts from you helping people on here.
I see where your coming from, sometimes I get sucked into what I'm doing too, whether it be mobile, or desktop pc's. I hear about it too from the wife too, and like you said you have to step back and enjoy the little things..

Romman0 said:
Thanks for all the hard work, man. I've seen soo many posts from you helping people on here.
Click to expand...
Click to collapse
Thank you for noticing but I do intend to keep helping on the forums, I'm just not doing anymore projects for awhile.
Tapatalked from my A100 - CM9 unsecured tester.

Thanks for your effort and work to bring custom ROM and lots of support on this tablet. Life always comes first. Good luck to you pio.
Sent from my Nexus S using xda premium

Thanks for all your efforts. They are greatly appreciated.

You have helped the community in tremendous amounts. Hopefully someone takes up these projects.
Sent from my A100 using xda app-developers app

You have been a huge contribution to the A100 scene. Thank you so much.
Sent from my A100 using Tapatalk 2

[DEV] B2G=FirefoxOS

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?

[ROM][WIP] Carbon ROM 4.3 Unofficial 9.15.13 4.2 BL

As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
As a favor I built Carbon ROM for a friend, and as it mostly works, he suggested I put it up for all of you guys to use, which I'm doing now :good:
Please refer to this thread http://forum.xda-developers.com/showthread.php?t=2137013 for a better understanding of the ROM and what it can do and features, otherwise here is some options it has:
-PIE!
-HALO
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
Who is Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
7.18.13
Initial release build, corrected non operational WiFi
8.06.13
Updated source, dock should now be fully funtional
9.15.13
Updated to 4.3
Built with CM's device tree and kernel source
As my tester no longer has this device, this is completely untested, reports are welcome!
THANKS, CREDIT, PROPS
Team Carbon
CyanogenMOD
AOKP
Google
Linaro
diesburg - for testing and suggesting releasing so you guys enjoy it also
Drgravy - 4.2 builds based on his device/vendor tree and kernel binary, and whoever else is included in the making of those.​

Notes, info, warnings
First and foremost, I do NOT own this device, I don't even own an Asus device, and not counting the N7, never have. I am building this blind and rely only on feedback from testers and users. As such, please remember this as you decide to yell about broken stuff.
This isn't a primary development device for me, I'm always willing to offer support on anything I release, but please don't expect daily builds. Weekly, perhaps, but it's mostly as I have the spare time to.
4.2 Bootloader only, I can not be held responsible if you flash this on any other bootloader and whatever happens, happening.
Information concerning updating and installing the correct bootloader and recovery can be found at the following:​[GUIDE]Upgrade TF300t to Jellybean 4.1 or 4.2, root, recovery & remove bloatware by krabappel2548 - please remember this is for the 4.2 Bootloader ONLY, please follow instructions for updating to 4.2 bootloader and recovery!
[GUIDE] How to install Universal Naked Drivers by tobdaryl - for setting up your PC to get going so you can root/flash/recovery/ROM your device.
[VIDEO Overviews and How To's] ASUS Transformer Pad 300 (TF300T) by AllAboutAndroids - for those who need or prefer video style instructions, swing by here and watch what they have to offer.
I'd be happy to add any additional information as it's needed, as I don't own the device I'm not real familiar with it and whats available information and utility wise. These looked like very informative threads to help users who may need a little guidance to getting ready to use Carbon on their device.
BUGS
BT does not work Rebooting will have BT working.
Some keys on the keyboard do not work
Whatever else?
​

Where can I get this?
You can visit pio-masaki.com, it's under the TF300T header, builds are always dated, and if multiple builds of the same date are made, they will include sequential build numbers, such as B2, B3, etc.
For those who don't want to go find it, here you go:
http://www.pio-masaki.com/index.php?dir=TF300T/Carbon/
Hosting for the site is made possible by diesburg for the best user experience and speed.
FAQ
Q. BT doesn't work!?
A. Reboot, BT should fire up as normal after the first reboot.
Q. HALO isn't appearing after I enabled it in settings, what gives?
A. Go into any UI besides Tablet UI (phablet, whatever you want to call its default UI mode) then reboot, enable HALO in settings, then pull down the statusbar and tap the circle icon, HALO will then appear. You can then go back to Tablet UI if you wish.
Q. I want to throw money at you / throw my daughter at you / bear your children! How can I do this?
A. Money can be freely donated (freely donated meaning in no way required or expected, however loved and appreciated as it's my only income and diapers are expensive) by clicking the donate to me link under my name to the left. Also please consider donating to diesburg for the hosting he has paid for. For throwing daughters around, maybe seek therapy, she may not like it. For children bearing, my wife wouldn't care for it, so get that out of your head. I also accept devices (old/broken/new/wet/bricked/whatever).
Kernel source: https://github.com/CyanogenMod/android_kernel_asus_tf300t
Device tree used: https://github.com/CyanogenMod/android_device_asus_tf300t

Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

As he posted above, when I tested, BT won't turn on. Some shortcut keys on the dock don't work. Both battery meters and the dock battery seem to be working. FYI, if you switch the UI mode to tablet mode or something, it requires a reboot for it to take. I think there may be a couple small issues with Halo. Enable halo and download any file from any site using the browser and you should see what I saw.(Hard to explain, but the download progress in the status bar never goes away, jacks your whole status bar)
And keep in mind what pio_masaki said, he doesn't have this device. So if you need help with something in the rom, how to or something, he may not be able to help, I will help as much as I can since i actually have the device. Please don't bomb him with ETA's . His main priorites for development of ROM's are for devices he owns and AFAIK, that will not change, he will release new builds when he does and until then, wait patiently.
Sent from my TF300T using Tapatalk

wigginst said:
Fancy seeing you here
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
HAHA hey I didn't know you had one of these, you traitor!:highfive:

Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

wigginst said:
Just got it. Wife has the thrive now (still running fine now).
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta
Click to expand...
Click to collapse
I need to sell the excite and get one of these :beer:

I have really liked it so far and has a good development community.
Sent from my Transformer Pad TF300T using Tapatalk 4 Beta

Just want to throw a reminder out... this is for 4.2 bootloader.... if you're on 4.1 you will have to upgrade.... if you have any doubt about what you are doing with the upgrade process and flashing the new recovery, please, for the sake of your own tablet, read, read, read, until you are sure about what you are doing. If you need help with upgrading the bootloader and flashing new recovery, let me know and we will post links to threads that have directions.
Sent from my TF300T using Tapatalk 2

cool to see this here going to dl and flash this
I'll let you know how it goes

pio_masaki said:
I need to sell the excite and get one of these :beer:
Click to expand...
Click to collapse
that would be a dream come true....lol....
Sent from my TF300T using Tapatalk 2
---------- Post added at 05:45 PM ---------- Previous post was at 05:18 PM ----------
Ok, just want to report that after one reboot, bluetooth turns on now. On initial install and first boot it wouldn't. I have nothing to test it with ATM though to see if it actually pairs with something.
Sent from my TF300T using Tapatalk 2

I am going to try this right away. Great to see a brand new ROM for our devices!

Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app

andrewnelson23 said:
Man! I just flashed Jellybam v9.2 and nooww it gets released I tried building this before, but it didn't work! -_- what did you have to do to get this to build correctly. I added the device tree and vendor tree, updated the vendorsetup.sh and added a carbon.mk to the device tree, but it didn't build correctly.
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.

pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app

andrewnelson23 said:
Gotcha! Makes sense. Yeah I'd like to see how you got it to work with the carbon.mk. I'd like to build it for my phone too. Thanks
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
I run carbon on all my devices lol. Sadly I have to build it myself since none are supported by the team.

pio_masaki said:
Likely the carbon.mk wasn't correct then. I build it for a few devices so I'm used to the way carbon builds so it didn't take much ton get it going here, drgravy's trees were 99% set already.
I'll put the trees I used up, I don't usually put them up until it works. Sometime tonight for whoever wants to tinker with the remaining issues.
Click to expand...
Click to collapse
if you put up a frameworks_base I may submit a pull request to get the dock functions working

Drgravy said:
if you put up a frameworks_base I may submit a pull request to get the dock functions working
Click to expand...
Click to collapse
Its on their github, carbondev. I'm sure its broken because the asusdec and something else didn't get along with the framework yet, unlike cm there's no real dock support in Carbon. Now that WiFi and I suppose BT are working it looks like only the dock stuff is left.

Gr88 to see pio posting stuff for our tab
His builds are quality :thumbup:
Will d/l and report back.
DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T

AOSP No call sound

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