[Solved] Increase Mic Volume Level on CM-Based ROMs! - T-Mobile LG G2x

**UPDATE 29 MAY**
CM7-RC3 and CM7 nightly 20120527 both work with the March 2012 baseband and have much higher outgoing volume! I'm not sure the issue I opened on the tracker had any part in this, but thanks to all who helped anyways! Your support was very much appreciated.
As CM7-based ROMs sync to the newer source, I am sure that they too will be fixed.
****************
I'm converting this thread into a Call to Arms! If you are frustrated with the low microphone volume on anything based on CM, please visit the thread on CM's issue tracker to leave your comments and "star" the issue. This is NOT an attempt to flood their thread with meaningless garbage. My intent is to let the CyanogenMod team know that this issue is very real and annoying. I think I can speak for most of us in saying that CM is a blessing to the Android world and that we mean no disrespect. My sole intent is to not let this issue get swept under the rug as it has in the past.
If you have a minute, please leave comments both here AND on the issue tracker to ensure this gets taken care of in due time. Please be respectful with your comments, but share your experience with the team in order to let them know that you are affected. Thank you all for your support with this issue.
r4d14n7 said:
This project is hereby abandoned by me. I don't have the knowledge, and I don't have the time to learn. If someone else wants to pick this up, I left a fair amount of documentation and research here in the thread and I will be available through PM if you have any questions. The best thing you can do right now is check the official bug report on CM's Issue Tracker, star it and maybe leave a comment or two. Sorry to let you guys down, but I pushed as many buttons as I'm capable of pressing at this point in time. Hopefully RC can figure this one out.
Original post and edits follow:
*Update again* I hit a wall and am not savvy enough to know where else to look. I submitted this bug to the issue tracker on CM's google code site here: http://code.google.com/p/cyanogenmod/issues/detail?id=5190
Feel free to head over there and "star" it to get updates. I really hope they will help us out. Thanks for the support guys. Going to give them a little bit and see where it takes us.
*Update* Changed thread title for clarity. In the process of trying to unpack/edit/repack a kernel to increase the volume of the microphone. Lucky for me, it's mostly scripts.
Let me start this thread out by saying that I am not a developer, coder, github user, etc. Yes, I'm a noob when it comes to all things coding.
Alright. I searched and searched and searched some more for the commit on CyanogenMod's github. I found it.
https://github.com/CyanogenMod/andr...mmit/a042d3bba7dc7d563ef58dfd2b0811722d924f86
I *think* this is the patch that caused the low microphone volume since October of last year. It could be one of its parent patches, but it's related. This commit is also included in CM's ICS branch, which could be causing the low microphone volume issue that some of us have been experiencing for so long.
I went to edit that file so I could try to fuddle my way through a build (which I've never done before) but I couldn't find the actual file in the github. Was this file removed? Are input volumes adjusted somewhere else now? I'm spoiled by our developers and would love it if someone would try reverting this patch if it's possible. Anyone else feel the same?
Click to expand...
Click to collapse

Update! bassmadrigal from the CyanogenMod staff helped me locate the microphone volume values. They are in the /sys/devices/platform/star_wm8994/data file. Using an older CM7 (167) build, I was able to modify the volumes until the phone reboots. I tested the voice quality by calling my own voicemail since the volumes can be different while in a call.
Having done this, I flashed a newer CM9 build. The values at the specific registers in that file are indeed different on CM9, but I was unable to modify them. Any modifications to that file via root explorer or adb were ineffective. I even went so far as to delete the file completely, but it was regenerated within seconds. There is some kind of built-in security (either in Android 4.x itself or CM9) that prevents manipulation of this file, and others I'm sure.
Does anyone know of a way to manipulate this file?

r4d14n7 said:
Update! bassmadrigal from the CyanogenMod staff helped me locate the microphone volume values. They are in the /sys/devices/platform/star_wm8994/data file. Using an older CM7 (167) build, I was able to modify the volumes until the phone reboots. I tested the voice quality by calling my own voicemail since the volumes can be different while in a call.
Having done this, I flashed a newer CM9 build. The values at the specific registers in that file are indeed different on CM9, but I was unable to modify them. Any modifications to that file via root explorer or adb were ineffective. I even went so far as to delete the file completely, but it was regenerated within seconds. There is some kind of built-in security (either in Android 4.x itself or CM9) that prevents manipulation of this file, and others I'm sure.
Does anyone know of a way to manipulate this file?
Click to expand...
Click to collapse
You're a legend man! Thanks for chasing this issue.
Sent from my LG-P999 using xda premium

From what I'm told, this file is actually part of the kernel. And I know nothing about any of this stuff. Is there anyone who knows how to modify and build their own kernel from source of whom I could ask some questions? I browsed around on Faux's github, but I seriously have no idea what I'm looking at.

DupleX01 said:
You're a legend man! Thanks for chasing this issue.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Man, I'm just trying to get the ball rolling on this ignored bug. I guarantee if I can fix it myself, I will definitely share.

Oh man, I hope this leads to the bug getting fixed. I love MIUI and CM, but the low mic volume has forced me to go back to using stock.

zenstrom said:
Oh man, I hope this leads to the bug getting fixed. I love MIUI and CM, but the low mic volume has forced me to go back to using stock.
Click to expand...
Click to collapse
I'm no kernel dev, but I'm still working on it. Hopefully I'll be able to get this issue resolved.
Edit: And by working on it, I mean asking kernel devs if they could build a test kernel with these changes included.

r4d14n7 said:
I'm no kernel dev, but I'm still working on it. Hopefully I'll be able to get this issue resolved.
Edit: And by working on it, I mean asking kernel devs if they could build a test kernel with these changes included.
Click to expand...
Click to collapse
Good luck to you sir!!!
Sent from my LG-P999 using xda premium

Lol, I just can't stop thanking. I was so happy to see that I wasn't the only one (thanks mt3g for your empathy there) to notice this annoying issue in CM based ROMs, when I've opened a thread the other day:
http://forum.xda-developers.com/showthread.php?t=1538240
IMHO, for some reason this bug just never got enough attention.
So, I'm crossing my fingers.
Sent from my LG-P999 using xda premium

Oh definitely, it just seemed to get shoved under the rug like it never happened a bunch of people in Baldwin guy cm7 thread stated it a bunch and it never got any attention if the OP can point someone in thebright direction after he does a bunch reading and reaching out to people then it can get resolved. It is honestly the only "bug" in cm7 that I hate. A bunch of people said they just switched ril's to fix it but I don't think so, I've done plenty of recording and what not with voicemails and I can easily tell between 2.3.3 to cm7 and found a build that was around 150ish
Sent from my LG-P999 using xda premium

mt3g said:
Oh definitely, it just seemed to get shoved under the rug like it never happened a bunch of people in Baldwin guy cm7 thread stated it a bunch and it never got any attention if the OP can point someone in thebright direction after he does a bunch reading and reaching out to people then it can get resolved. It is honestly the only "bug" in cm7 that I hate. A bunch of people said they just switched ril's to fix it but I don't think so, I've done plenty of recording and what not with voicemails and I can easily tell between 2.3.3 to cm7 and found a build that was around 150ish
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Almost all of the old CM7 builds are still hosted here: http://goo.im/cm/p999/nightly but for some reason the 170's are missing. Haha...
I agree with you on it being the only thing I hate about CM7/9.
Anyway, another update for you guys. I found a guide on how to unpack the kernel and ramdisk from boot.img so I can modify this file, then repack it. Downloading Ubuntu now. Going to install it in a Virtual Machine and see if I can do this. Might take me a bit though. I'm a busy guy

Well, I was able to unpack the kernel and split it into the kernel and ramdisk. The ramdisk contains the "sys" directory, but it's empty. I can't find the file that I need to modify. Maybe it's in the kernel part of the split.

I would just like to say thank you.
And I wish I could help!
Sent from my LG-P999 using xda premium

So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA

I'll take a look at it when I get the chance.

redmonke255 said:
So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Low mic volume is the issue. Speaker volume is fine.

nightf0x said:
Low mic volume is the issue. Speaker volume is fine.
Click to expand...
Click to collapse
Yea sorry that's what I meant, I haven't had complaints about that but maybe I'm just loud.
Sent from my LG-P999 using XDA

redmonke255 said:
Yea sorry that's what I meant, I haven't had complaints about that but maybe I'm just loud.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Record your self on a stock based rom or leave a voice mail its very noticeable, speaker phone is almost pointless while on cm7/9 you set the phone down 2 feet from your face and they can't hear you practically it sounds like you're whispering.
Sent from my LG-P999 using xda premium

mt3g said:
Record your self on a stock based rom or leave a voice mail its very noticeable, speaker phone is almost pointless while on cm7/9 you set the phone down 2 feet from your face and they can't hear you practically it sounds like you're whispering.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You're absolutely right mt3g, speakerphone is horrible. And I'm typically kind of a "chin talker" who lets the phone drift down away from the mouth. If I pay attention to holding the phone up further in front of my mouth and speak firmly, I can usually get heard alright on the other side, but I'm used to phones in the past picking up a lot better, and sometimes I need to speak softly if my kids are napping, etc.
FYI, this is my test environment (to eliminate variables):
Always call voicemail to perform the tests, because the input volume can change from just using a voice recorder app to actually in a call.
I play the same part of the same song at the same volume with my phone in the same position every time.
Just nandroiding back and forth between stock/early CM7/late CM7/CM9, there is a major difference.

redmonke255 said:
So if it's based in the kernel, do other kernels face this problem?
I'm using CM7.2 with faux kernel and haven't noticed low speaker volume.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
If I'm not mistaken, custom kernels designed for CM7/9 are based on the original CM7/9 kernels. Regardless, I have personally verified this issue exists with faux's and morfic's kernels.

Related

Is there other voodoo kernals besides fauk123?

Sent from my LG-P999 using XDA App
I really wish the CM7 team would integrate the voodoo functionality into the standard CM7 kernel.
Is there a reason not this hasn't been done already (other than someone just not getting around to it yet)?
lannister80 said:
I really wish the CM7 team would integrate the voodoo functionality into the standard CM7 kernel.
Is there a reason not this hasn't been done already (other than someone just not getting around to it yet)?
Click to expand...
Click to collapse
Whoops, hit thanks instead of quote. This is what happens when I leave late for work and don't have my morning coffee
I believe the reason is the author requested it be pulled, he didn't like the implementation of it on the g2x. (I believe this is in part due to the fact that nvidia hasn't released source they need to make it work 100%)
I've found that voodoo on the g2x was a placebo at best. Sure, it made it louder, but the dynamic range seemed to lessen (especially on the high end) when using it. On devices that have it implemented properly, it's a beautiful audio engine, however.
(I could be wrong on this, it's second hand info at best, so feel free to correct me.)
Thanks for the info. Makes allot more sense now.

[TWEAK][GB] Faster Scrolling (Disable Scrolling Cache)

after noticing this mentioned in truckerglenn's port of f1, i did a little searching and found this great how-to thread (be sure to thank the OP!)...clearly written below the level of our beloved "devs" but along the lines of those, like me, who are new to the whole process and looking for a few guidelines while getting our hands dirty
i did both of these tweaks last night on ZEUS BUILD 3 FIXED (and updated), and as they mention in the original thread, increasing the sound increment works visually but audio levels become distorted above 15 (thanks samsung!)...maybe someone knows how to figure this one out
the scrolling tweak seems to work well (or i'm a sucker for placebos).....i've noticed that i can get to the bottom of very long lists and pages in fewer swipes
http://forum.xda-developers.com/showthread.php?t=1411317
for those that dont care to do it themselves but would love to give feedback...i've included my modded framework.jar from ZEUS BUILD 3 FIXED (and updated) to include the scrolling mod...if you're on that rom, just use root explorer like you should know how by now, and drop this baby in /system/framework
Reboot should take a little....dont panic!
and for those on ZEUS BUILD 3 FIXED (and updated) who just aren't sure...i've also included a cwm flashable zip with the stock framework
so now...whadya got to lose? o_0
hope it works!
EDIT: according to Dani, this should work on any att based GB ROM....so thanks for the tip!
Nice
Sent from my SAMSUNG-SGH-I997 using xda premium
the audio can be tough to find the best drive without clipping.
the distortion can come from many things but if it's clipping it can be damaging to the speaker or hardware. basically analogue audio should change voltage in smooth sinodal(sp?) patterns. if you exceed the input voltage on an amp it can't reproduce the wave and you get a partial sinodus with a flat (dc) area that creates heat in the speaker and extra current draw. it can also damage the input stage of the hardware. things are a little different on digital but you will still get nasty harmonics that can damage stuff. also too much gain can mean that the output stage reaches the source voltage before the top of the wave. the problem is getting the most out of the hardware and figuring which level is causeing the clipping.. there will be an ideal gain for each stage and the content will vary in volume.. its a big balancing act and manufacturers tend to leave a good amount of extra potential to avoid clipping at any stage. some extra may be added in the framework some in the kernel drivers but it either takes critical listening and trial and error or some edjucated guessing.
I don't know anything about drivers or kernels so I'm not that Guy but maybe if I try the framework mod I could find a compromise but I never really find that kind of time lately.
Dani897 said:
the audio can be tough to find the best drive without clipping.
the distortion can come from many things but if it's clipping it can be damaging to the speaker or hardware. basically analogue audio should change voltage in smooth sinodal(sp?) patterns. if you exceed the input voltage on an amp it can't reproduce the wave and you get a partial sinodus with a flat (dc) area that creates heat in the speaker and extra current draw. it can also damage the input stage of the hardware. things are a little different on digital but you will still get nasty harmonics that can damage stuff. also too much gain can mean that the output stage reaches the source voltage before the top of the wave. the problem is getting the most out of the hardware and figuring which level is causeing the clipping.. there will be an ideal gain for each stage and the content will vary in volume.. its a big balancing act and manufacturers tend to leave a good amount of extra potential to avoid clipping at any stage. some extra may be added in the framework some in the kernel drivers but it either takes critical listening and trial and error or some edjucated guessing.
I don't know anything about drivers or kernels so I'm not that Guy but maybe if I try the framework mod I could find a compromise but I never really find that kind of time lately.
Click to expand...
Click to collapse
Thanks Dani for the input...just to clarify, by distortion I mean the audio maxs out at level 15, if you adjust higher than that, it seems as if audio drops to a lower level and increases to max again as you increase...say you made it so there were 30 increments as opposed to 15...its like this:
1min............15max 16min..............30max
I hope that makes sense...the OP concluded that it wasnt compatible w Samsung but im hoping someone w more pointed knowledge could work it....that would def be a plus in future roms
Sent from my SAMSUNG-SGH-I997 using Tapatalk
albee320 said:
Thanks Dani for the input...just to clarify, by distortion I mean the audio maxs out at level 15, if you adjust higher than that, it seems as if audio drops to a lower level and increases to max again as you increase...say you made it so there were 30 increments as opposed to 15...its like this:
1min............15max 16min..............30max
I hope that makes sense...the OP concluded that it wasnt compatible w Samsung but im hoping someone w more pointed knowledge could work it....that would def be a plus in future roms
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
ohh, I get it.
ill read the tutorial and see if I notice an obvious problem... but I don't really know Java, just hoping something jumps out as not right.
---------- Post added at 07:59 PM ---------- Previous post was at 07:52 PM ----------
nah this ones gonna need some research. there may be some other file that maps the levels and that might need some Modding.
Cool! Yeah the bullet about smooth scrolling on truckerglenn's F1 port thread really caught my eye too. That's the only thing I miss from the iPhone is the smooth scrolling.
Has anyone tried this on any KL2 rom or will it just work on zeus?
Sent from my SAMSUNG-SGH-I997 using xda premium
tmease1 said:
Has anyone tried this on any KL2 rom or will it just work on zeus?
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
it "should" work on most of the leaks.
Follow the original link for instructions on how to do it on the other roms for the infuse. The posted links are for the zeus rom from dman, while the files posted may work on roms other than zeus I'd highly advise not using them. Follow the link in the first post to get the smooth scroll into whatever rom you're currently using.
crash822 said:
Follow the original link for instructions on how to do it on the other roms for the infuse. The posted links are for the zeus rom from dman, while the files posted may work on roms other than zeus I'd highly advise not using them. Follow the link in the first post to get the smooth scroll into whatever rom you're currently using.
Click to expand...
Click to collapse
I highly advise not being such a wuss. jk but seriously there is little chance of harm using it in a different att based gb rom. I just installed it on bionix and no problems.
I went ahead and tried it on the stock KL2 rom and it works just fine. Thanks guys.
Sent from my SAMSUNG-SGH-I997 using xda premium
I tried the the hack in infuse 4g from rogers but I stuck in boot loop
aburyan1 said:
I tried the the hack in infuse 4g from rogers but I stuck in boot loop
Click to expand...
Click to collapse
what rom are you using?
albee320 said:
what rom are you using?
Click to expand...
Click to collapse
RUXKG3....stock Rogers 2.3.3 rooted
aburyan1 said:
RUXKG3....stock Rogers 2.3.3 rooted
Click to expand...
Click to collapse
You tried doing the hack like decompiling editing and compiling? maybe the wrong text editor.. text editors and source code are weird. try notepad++ or vi on linux
or you tried the att file stock Rogers rom? our framework is different so it wont work like that. the file posted is for att gingerbread.
Flashed this on Zeus 5. Can't really tell if it made anything smoother but at least I didn't bootloop.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Seems a lot faster. Wonderful job.. is something burning?
Sent from my SAMSUNG-SGH-I997 using xda premium

Ok all g2x ics stuff goes here!!

ICS ANDROID QUESTIONS GO HERE!!!!!
Quite frankly im sick of seeing a new thread or an old thread revised every 4 weeks. Basically from the point of a dev and a fan I am submitting this thread. I want to see every old or dev thread closed and all questions or suggestions pointed here.
I have personally exhausted most of my resources trying to fix the problems we have within our tegra g2x builds. This device is completely closed source rather like to admit it or not. blame it on all you want to.ether
The bottom line is lg and nvidia only releases source for their bottom line **** that makes tegra work, and we have done patched that in and made it work to some extents.
Yes Alot of us devs can make cm9 work and alot of us can make aosp4.0.3+ work. but they will not opensource their work. To the same extent we where stuck at with the vibrant and the gps issue.
All i can say is do not buy another lg device or another tegra device. Yes the transformer is bad ass, but if you protest to a level to where no one wants there work they will be forced as an oem to make there manufactures push their source and make it relevant to the point the oems do.....
Thanks for this, all the other ones seem really useless and never stay on track anyway. . I wonder how long it'll take before some guy trolls the hell out of this one. Lets try to keep this one only pertaining to AOSP ICS or CM9 development and/or progress.
This works...but at some point it will get off track...most of the people that are in the the other threads can't get a working build and since we don't have any builds to test anymore its tough to stay on topic with something you aren't using.
Sent from my LG-P999 using XDA App
Forget ics wheres the new weapon rom is wat im after!
kwes1020 said:
This device is completely closed source rather like to admit it or not.
Click to expand...
Click to collapse
Yea, that's crap, I mean, one of the things I like about Android is the open-sourceness. If only OEM's would realize that an open-source system will, in my opinion at least, get more and better support FROM THE COMMUNITY tahn a totally closed system. Take Windows for example, we all have have things to complain about and most can't do that much, even with third-party programs which can be used to correct problems or bugs or add features. On the other hand, there's a game series I follow where the Dev's explicitly made the games open for easy modification, the only "closed" part is the actual engine itself which was developed from scratch. And what resulted was a fan base who took initiative to correct bugs and add features, sure people didn't like the fact that the games had bugs initially but not only did the community take action but the devs even incorporated community fixes into official patches and credited the person who made the fix. Now the dev company has gone solo and publish their own games and are due to release a fourth in the series with a strong fan base. And here we have people who will refuse to ever touch, Nvidia and/or LG ever again, and not just because of bugs, but the fact that it's closed and we get crap for official releases and fixes and crap for support.
/end rant
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
moeahmad1995 said:
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
I just compiled the aosp 4.0.3 for G2x. I used the google's sources not CM9. However it doesn't boot. I was just wondering how did you guys got it to boot?
Also, the aosp source requires recovery as well to make the otapackage. Is there any way to make the otapackage without recovery? This is not a very big issue as i can manually make the otapackage.
booting up is the big hurdle. Any help is highly appreciated
Thanks
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Well CM has had perfectly working ICS build except camera since Thanksgiving. That was like 2+ months ago, maybe they've fixed camera by now who knows.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
People can remember CM for being the first to release ICS for the G2x but only because they kept their work secret and didn't share or because they shared their work with others and others with them and they came out on top because they are better or they didn't because they aren't better, etc.
@moeahmad1995
Back on subject? It's a general thread which is all inclusive: "Ok all g2x ics stuff goes here!!"
Волк said:
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
Click to expand...
Click to collapse
I'd guess that there are many reasons for CM to keep their source closed for now, not the least of which is reputation. Also competition is one of the things that drives development. Open source is not just about giving hard work away for free.
Here's a great article that helped me to better understand the nature of open source.
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
yeah every build I've made has the same issues as yours which is no working data sound and cam.
Sent from my Galaxy Nexus using xda premium
If there's anything I can do, let me know. I can't help much with development, but I have access to a large audience. For those who don't know, I'm a writer for ACSYNDICATE.NET and will help any way I can. Thanks for sticking with it devs, and thanks for all the new roms!
Sent from my LG-P999 using xda premium
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
SefEXE said:
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
Click to expand...
Click to collapse
Dammit, I was going to post that
IRASadPanda said:
Dammit, I was going to post that
Click to expand...
Click to collapse
Post it anyways!
It's a joyous occasion!
Well we need to know what they did so we can see if the fix would work on the g2x
Sent from my G2x XDA app cuz I'm stalking your mom....
http://forum.xda-developers.com/showpost.php?p=22200247&postcount=385
"
marsgod
Yesterday, 09:47 AM
# 385
I hope this help fix audio problem...
--------------------------------------------------------------------------------
Here is my fix for SU660 ICS audio...and it work for my ICS AOSP 4.0.3 (SU660 = KR version P990)
I think currently, we must use the libaudio from CM7/Stock rom.......
SO...
1. Modify star-common/BoardConfigCommon.mk
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_AUDIO_LEGACY := true
# Use dirty hack to allow froyo libaudio
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
2. Add audio.primary.p990 audio_policy.p990 into your star-common/star.mk. (This will use hardware/cm/audio. DONT USE audio.primary.tegra audio_policy.tegra!)
3. Use my hardware_legacy.tgz , extract it into star-common/include. The code is mainly from VorkTeam's github, thanks. I only made some fix in it.
4. Copy from CM7/Stock rom : libaudio.so, liba2dp.so, liblvvil.so
Audio should work now...
--------------------------------------------------------------------------------
Attached Files
hardware_legacy.tar.gz - [Click for QR Code] (5.7 KB, 12 views)"
Sweet!!!! Well we should have everything working but the camera? Ill test if anyone need be!!! Would be nice to start seeing some new alpha builds
Sent from my LG-P999 using XDA App

[DEV/ROM][FROM SOURCE][CAF GB 2.3.6][build #20][3/21]

Here is my Skyrocket ROM built from Code Aurora Forum source. This is Android 2.3.6. It is not even close to a daily driver and probably never will be.
DO NOT INSTALL THIS UNLESS YOU ARE VERY EXPERIENCED IN DEBUG AND KNOW HOW TO USE 'adb'.
I am posting this to help with the effort to build a community ICS ROM. Perhaps my device tree will help. As such, I do not plan on spending any more time debugging the issues with the rom. I would rather focus on helping the community get an ICS build going.
Link to my device tree: https://github.com/dferg/android_device_msm8660_skyrocket
Link to build instructions: https://github.com/dferg/android_device_msm8660_skyrocket/blob/master/README.md
Link to Code Aurora Forum: https://www.codeaurora.org/xwiki/bin/QAEP
Link to the ROM (build #20): http://d-h.st/gU2
What works?
calls (no audio), sms, 2D graphics, wifi, bluetooth
What doesn't work?
cell data, audio, nfc, int+ext sdcards
Instructions for install:
In CWM, wipe factory
In CWM, install this zip
Reboot + wait up to 3 minutes
If you get the lock screen with no way to unlock, connect to your computer and run "adb reboot". You should then get the proper unlock slider.
Notes:
sdcard is detected incorrectly, so do NOT allow it to attempt a format (it will say 'damaged sdcard'--just ignore this)
Even though it says "No SIM Card" calls in and out will work, although no audio...
Updates: 3/21/12
Added link to build instructions on Github
Pushed commits to Github that simplify the build
reserved...........2
You should be more optimistic
It will work some day, don't think it won't ever be working.
Sent from my SGH-T989 using Tapatalk
kr3w1337 said:
You should be more optimistic
It will work some day, don't think it won't ever be working.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Agreed, and thanks for this
Sent from my SAMSUNG-SGH-I727 using xda premium
just for my understanding, what is the hurdle to getting data to work, seems like it is always the hardest thing to enable.
For gb builds on our phone I always see call audio being a hurdle
people who live in glass houses sink ships
nrm5110 said:
For gb builds on our phone I always see call audio being a hurdle
people who live in glass houses sink ships
Click to expand...
Click to collapse
Nrm is right. Audio seems to be the biggest hurdle.
This rom makes an LTE connection but the data connection just isn't used. Not sure why, but this problem seems easier than audio (which I have had no luck debugging so far)
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.
Longcat14 said:
Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.
Click to expand...
Click to collapse
He stopped working in this for ICS.
Longcat14 said:
Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.
Click to expand...
Click to collapse
Thanks Longcat. Like alphadog pointed out, I'm not actively working on this one right now in favor of helping out the ICS efforts. But if someone else would like to collaborate or even pick up where I left off, please have at it. My reason for starting this ROM was to eventually get CM7 fully stable, as you suggested.
I wish someone would be able to pick this up I understand the importance of ics but the hurdles with gb seem far fewer than ics and would tide the masses over once I get my other hdd set up with Ubuntu I hope to take a peek
people who live in glass houses sink ships
Id love full cm7 made for this
Sent from my SAMSUNG-SGH-I727
droid512 said:
Id love full cm7 made for this
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Fyi code Aurora is different than cm lol
people who live in glass houses sink ships
FYI: I updated the OP with a link to the build instructions. I also pushed changes to my Github that simplifies and cleans up some of the build.
topprospect said:
FYI: I updated the OP with a link to the build instructions. I also pushed changes to my Github that simplifies and cleans up some of the build.
Click to expand...
Click to collapse
Just fyi. Eugen373 is working on aosp for t989. Apparently with good results.
billydroid said:
Just fyi. Eugen373 is working on aosp for t989. Apparently with good results.
Click to expand...
Click to collapse
Any links on him talking about status of it for us to follow? I checked 989 general and dev real fast. Didn't see anything.
R4INS said:
Any links on him talking about status of it for us to follow? I checked 989 general and dev real fast. Didn't see anything.
Click to expand...
Click to collapse
Yes, a link to his post would help. I searched XDA and Github, finding only stuff about Vibrant roms that he has done.
topprospect said:
Yes, a link to his post would help. I searched XDA and Github, finding only stuff about Vibrant roms that he has done.
Click to expand...
Click to collapse
It's from twitter, eugen373. Not sure if he has pushed anything to github. You can ask him, he is extremely helpful guy.
Sent from my SGH-I777
Eugene's Twitter Post
billydroid said:
It's from twitter, eugen373. Not sure if he has pushed anything to github. You can ask him, he is extremely helpful guy.
Sent from my SGH-I777
Click to expand...
Click to collapse
Check https://twitter.com/#!/Eugene373. Looks like he is very close,

cm10 soon?

i know we had a thread and everything reguarding this and the p990 (2x), however the changelog on BBQLog has the p999 G2x actually implemented into the menu for devices. this is good news for us that have been waiting patiently !!
click LGE and its there offically
http://changelog.bbqdroid.org/#
Was it not there before? And I wouldn't get too excited, the Optimus One is listed there also and I HIGHLY doubt that is going to get official CM10
I believe that's still the cm7 changelog.
It just says cm10
It wasn't there before. When the 2x got close it was there. It wasn't there a couple days ago, that's for sure.
Perhaps for cm7, even if it is for a nightly once a month.
Sent from my SGH-T999 using xda app-developers app
it's new
qpinto said:
It wasn't there before. When the 2x got close it was there. It wasn't there a couple days ago, that's for sure.
Perhaps for cm7, even if it is for a nightly once a month.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It is certainly new look at the log dates there is work being done today also the work has been done every few hours apart.
No, no and no.
The entry in the BBQLog has been there for quite some time.
If you knew how it worked, you'd also know that all of those changes are generic and have absolutely jack squat to do with the p999.
Try selecting a different, unrelated device if you don't believe me. You'll see the same changes. Maybe more as other devices have cm10 changes checked in.
None of the changes I see on BBQLog say anything about the p999 getting cm10.
My money is on "ain't gonna happen". If it was going to happen, we'd have heard something by now from Ricardo or others. The fact that there's been silence basically tells me that there's a huge roadblock and nobody wants to take the heat for coming out publicly and killing off the G2X's last hope.
EDIT: If I'm wrong, I'll eat a sock.
EDIT 2: Okay, no sock. But I'll eat my words.
qpinto said:
It wasn't there before. When the 2x got close it was there. It wasn't there a couple days ago, that's for sure.
Perhaps for cm7, even if it is for a nightly once a month.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
We already still get updates, almost weekly for cm7.
I'm running the 11-18 build now.
G2x-temasek CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
lotherius said:
No, no and no.
If it was going to happen, we'd have heard something by now from Ricardo or others. The fact that there's been silence basically tells me that there's a huge roadblock and nobody wants to take the heat for coming out publicly and killing off the G2X's last hope.
Click to expand...
Click to collapse
I take the silence to mean that no one has really given it a go yet. I think if there was a huge roadblock, they wouldn't keep that a secret. Just today someone posted an unrelated G2X comment on one of RC's G+ posts... If he had tried and didn't think he could get it to work, I think he would have let us know, at least to shut us up a little bit.
jayknight said:
I take the silence to mean that no one has really given it a go yet. I think if there was a huge roadblock, they wouldn't keep that a secret. Just today someone posted an unrelated G2X comment on one of RC's G+ posts... If he had tried and didn't think he could get it to work, I think he would have let us know, at least to shut us up a little bit.
Click to expand...
Click to collapse
That's not necessarily the case. Letting people know this device is hopeless could also cause more people to bug him.
This speculation is unwarranted anyhow. I am however curious to why there hasn't been an update on CM10 for us. I do think that likely there was an unexpected encountered problem like the call bug issue on the O2x and still persisting WiFi drain.
And I have two other devices running a full working CM10, and besides the working camera and better battery life, they really aren't that different in terms of fluidity. If RC releases a ported CM10 for us it will likely still have most of the same issues.
We just have to patient. I mean, I don't have the money to buy another device, so I have no choice. If you have had the opportunity to jump ship... why *Haven't* you already? It's been nearly a full year since LG dropped this phone from support and we found out Nvidia won't share drivers, and some of you are still here complaining?
Sent from my LG-P999 using xda app-developers app
jayknight said:
I take the silence to mean that no one has really given it a go yet. I think if there was a huge roadblock, they wouldn't keep that a secret. Just today someone posted an unrelated G2X comment on one of RC's G+ posts... If he had tried and didn't think he could get it to work, I think he would have let us know, at least to shut us up a little bit.
Click to expand...
Click to collapse
Never think you understand what an angry programmer will do. They are not like regular people and won't feel at home on earth until the mothership picks them up.
Since ics official for p990 gonna come shortly, I guess latest we get what we want is sometime after source drop.
Beyond that I can't comment on what I don't know. I won't be buying an lg product for two reasons now though.
Sent from my LG-P999 using Tapatalk 2
bluenote73 said:
Never think you understand what an angry programmer will do. They are not like regular people and won't feel at home on earth until the mothership picks them up.
Since ics official for p990 gonna come shortly, I guess latest we get what we want is sometime after source drop.
Beyond that I can't comment on what I don't know. I won't be buying an lg product for two reasons now though.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Yea I figured he's going to use official p990 sources first to fix up cm10 for o2x, then hopefully port to our phone.
Hopeful speculation.
Sent from my LG-P999 using xda app-developers app
Idk about original post but 2 things bugs me and this is my first/last time complaining: 1. Its been about a month and not a single word. An yes,no, maybe would be enough so I would atleast know to whether hope patiently or dont hope and 2. I cant do anything about it :'( ow well lol
Agreed just a simple yes after p990 is up and running and no ETA would be all I would need. Sorry I know I will get flamed for this but I can't hold back..... RC is a xxxxxxxx for never answering his over 50 or so inquire's about p999 .... I stopped counting at 50. Even a " I will get to it in time" would be something.
rosevilletoyota said:
Agreed just a simple yes after p990 is up and running and no ETA would be all I would need. Sorry I know I will get flamed for this but I can't hold back..... RC is a xxxxxxxx for never answering his over 50 or so inquire's about p999 .... I stopped counting at 50. Even a " I will get to it in time" would be something.
Click to expand...
Click to collapse
wow
please discard your g2x and move on. lol
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
rosevilletoyota said:
Agreed just a simple yes after p990 is up and running and no ETA would be all I would need. Sorry I know I will get flamed for this but I can't hold back..... RC is a xxxxxxxx for never answering his over 50 or so inquire's about p999 .... I stopped counting at 50. Even a " I will get to it in time" would be something.
Click to expand...
Click to collapse
justjackyl said:
wow
please discard your g2x and move on. lol
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Click to expand...
Click to collapse
Allow me to play devils advocate....
I don't see anything wrong with people just wanting an update. Even a plain "yes we will eventually get to the p999" just so people are not waiting in vain. That would probably put out a lot of the repetitive "When are we getting cm10" questions. A lot of people are patiently waiting for an update, or a word, or anything and it would be nice to know for sure that something will be done eventually. Right now it just comes across as the project is dead in the water.
I am not bagging on the developers btw. They are awesome because they do this stuff for free and on their spare time, but it would only take a minute to put the word out, if it's a go or not. Just saying...
skarookidoo said:
Allow me to play devils advocate....
I don't see anything wrong with people just wanting an update. Even a plain "yes we will eventually get to the p999" just so people are not waiting in vain. That would probably put out a lot of the repetitive "When are we getting cm10" questions. A lot of people are patiently waiting for an update, or a word, or anything and it would be nice to know for sure that something will be done eventually. Right now it just comes across as the project is dead in the water.
I am not bagging on the developers btw. They are awesome because they do this stuff for free and on their spare time, but it would only take a minute to put the word out, if it's a go or not. Just saying...
Click to expand...
Click to collapse
The moment they say "No", the mass exodus would begin. I wish they'd just come out and say "No" so that this subforum would quiet down.
The p990 just got dropped again from CM support, so doubt we'll get it.
Does RC know that the G2x is also experiencing the bug sound? Maybe some one can port it over to check. It's the only thing holding it back from being Stable.
Sent from my LG-P999 using xda app-developers app
Bulletblitz27 said:
The p990 just got dropped again from CM support, so doubt we'll get it.
Does RC know that the G2x is also experiencing the bug sound? Maybe some one can port it over to check. It's the only thing holding it back from being Stable.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
What's your source?
Sent from my Xoom using Tapatalk 2
P990 General thread, "CM10 User Thread" Tony said it himself.
I suggest you guys start looking over at their threads, because not much is happening here other than complaining.
Sent from my LG-P999 using xda app-developers app
The P990 won't get CM10 properly working until the ICS source drops for the phone. Luckily there have been rom leaks, but who knows how long it's going to take LG.
And then IF they get the sources we MIGHT get a fully working CM build.
Don't hold your breath guys, a lot of stars have to line up before we'll get anything.
Sent from my LG-P999 using xda app-developers app

Categories

Resources