Success! Ladies and gentlemen, we are in business! :good:
I've rebuilt ICS from the 4.0.4 + Samsung patch tree, with the a2dp max bitpool set to a more appropriate 64. For the first time ever, let your Glide sound the way it should over bluetooth!
Updated library (and source patch) attached. Simply push audio.a2dp.default.so to /system/lib/fw (root & rw /system required), or use the CWMR flashable update provided by thegreatergood (CWMR_a2dp-bitpool-fix.zip).
Please note this binary is only compatible with the official ICS (IMM76D/UCLH2) and the leaked ICS build! It will have no effect on the previous Gingerbread build.
Take a nand backup with CWMR before you begin! If this library is corrupted, your phone will hang during bootup!
Code:
6 [email protected]:/system/lib/hw# logcat | grep -i bitpool
D/A2DP ( 3768): min_bitpool: 2
D/A2DP ( 3768): max_bitpool: 53
D/A2DP ( 3768): bitpool=53
53 is the max supported by the headset I'm using, and it sounds great!
Note - if you want to apply the source patch yourself, the target files are in external/bluetooth/bluez/audio.
Thanks to thegreatergood for creating a CWMR flashable archive!
Enjoy!
lambgx02 said:
Hi guys,
So like many, I've got the new ICS build up and running, and it does resolve a lot of issues (hey - a working compass in Google Maps!).
One issue it does not resolve is the poor bluetooth a2dp audio quality. Still locked at 35 bitpool. Sigh.
I'm working on resolving this situation, now that (I hope) the proprietary broadcom binaries and junk are gone, and will post progress here. If anyone has any comments / suggestions / patches let me know!
Click to expand...
Click to collapse
Ya that is one thing that really is bothering me with the leak is it takes forever to connect with Google maps I Mean close to 15 minutes!! Perhaps I should start looking at switching to the release if you say this is fixed....Just wish someone would make a CWM version.
This should be in the general section
Sent from my SGH-I927 using xda premium
jayjayjoker2 said:
This should be in the general section
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Why? I'm working on a solution to the problem that could involve binary or source patches, recompiles, and some complex debugging and/or side effects. I don't think it's good to expose everyone in the general section to this process..
lambgx02 said:
Why? I'm working on a solution to the problem that could involve binary or source patches, recompiles, and some complex debugging and/or side effects. I don't think it's good to expose everyone in the general section to this process..
Click to expand...
Click to collapse
Well if you are developing then that's fine
Sent from my SGH-I927 using xda premium
Thread moved
This does not belong in Development, until a file is ready for downloading - that's what belongs in Development. Until then, it belongs in General.
jayjayjoker2 said:
This should be in the general section
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
reinbeau said:
This does not belong in Development, until a file is ready for downloading - that's what belongs in Development. Until then, it belongs in General.
Click to expand...
Click to collapse
Just so we're clear here (I wouldn't want to make the mistake twice) - you're saying threads of technical nature that involve potentially pasting code snippets, log dumps, modifications to /system and other risky procedures which may (soft) brick devices belong in the general discussion forum, unless the first message contains an attachment?
If so, when my 4.0.4 source tree build finally completes and I upload a modified /system/lib/hw/audio.a2dp.default.so and diffs, should I expect complaints that the thread belongs in the development section?
lambgx02 said:
Just so we're clear here (I wouldn't want to make the mistake twice) - you're saying threads of technical nature that involve potentially pasting code snippets, log dumps, modifications to /system and other risky procedures which may (soft) brick devices belong in the general discussion forum, unless the first message contains an attachment?
If so, when my 4.0.4 source tree build finally completes and I upload a modified /system/lib/hw/audio.a2dp.default.so and diffs, should I expect complaints that the thread belongs in the development section?
Click to expand...
Click to collapse
Development discussion, once something is developed, takes place in the thread if the developer allows it, since there its no Q&A section.
Sent from a state of Serendipity
Success! See first message.
Pandora sounds a lot better with Ford Sync now, thanks.
Sent from my SGH-I927 using xda premium
This is amazing. All this time, I thought it was because my headphones sucked.
Awesome to see a new MOD. :good: . I still go with the wired headphones, as Bluetooth headphones previously didn't sounded great. Maybe this is what was needed. Will surely check this out.
can the fix be done on GB? i'm still using it until i'll have custom rom that will support my language.
i know it been compiled for ics but can we use the source to change the gb version?
taiber2000 said:
can the fix be done on GB? i'm still using it until i'll have custom rom that will support my language.
i know it been compiled for ics but can we use the source to change the gb version?
Click to expand...
Click to collapse
Sadly, no. This is the main reason I was so excited when the ICS source was released.
The problem is the Gingerbread build uses a proprietary Broadcom binary for managing bluetooth, and I wasn't able to hack the binary itself. Tried for weeks.
I hope an ICS build comes out for you soon!
Greetings.
After overwriting the original file, and rebooting the phone, i noticed a minor audio quality improvement (minor, but clearly noticeable) by using a Nokia BH-905 headset, and listening to music files, however i do not tested calls yet.
Necc86 said:
Greetings.
After overwriting the original file, and rebooting the phone, i noticed a minor audio quality improvement (minor, but clearly noticeable) by using a Nokia BH-905 headset, and listening to music files, however i do not tested calls yet.
Click to expand...
Click to collapse
The quality improvement depends on the headset, which can also set the maximum bitpool size. If the BH-905 limits the bitpool to 45, that would only be slightly better than the stock 35. If you're interested, you can check the negotiated bitpool size with:
Code:
logcat | grep -i bitpool
.. shortly after connecting A2DP.
Note that this patch will have no effect on voice calls, since they use a different profile (HSP / HFP).
Using Motorola S805's here, and a very noticeable increase in quality. Looks like mine support a max of 53.
lambgx02 said:
Sadly, no. This is the main reason I was so excited when the ICS source was released.
The problem is the Gingerbread build uses a proprietary Broadcom binary for managing bluetooth, and I wasn't able to hack the binary itself. Tried for weeks.
I hope an ICS build comes out for you soon!
Click to expand...
Click to collapse
damn, thanks man. i hope that a port of aosp/aokp or cm9/10 will be out and then i will upgrade to it - and i believe there isn't a problem in those roms with the bitpool. btw how can i know the maximum bitpool of my headset? i have a sony erricson mw600.
taiber2000 said:
damn, thanks man. i hope that a port of aosp/aokp or cm9/10 will be out and then i will upgrade to it - and i believe there isn't a problem in those roms with the bitpool. btw how can i know the maximum bitpool of my headset? i have a sony erricson mw600.
Click to expand...
Click to collapse
Just connect them and start playing some music while running:
Code:
logcat | grep -i bitpool
Even with the 35-limited stock library it should tell you what headset requested.
How i do install it? Flash CWM? Both zips?
Related
Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
madplaya1 said:
Since, frx07 is coming out sooon. What are features that are coming with it or fixes ?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
There will be a formal list when it drops. I will make a thorough post of what's changed when the time is right.
The big ones are RIL & BT. Audio routing won't make FRX07, so BT audio won't work, but pairing with BT devices & transferring data should.
Great , thanks!
Sent from my MSM using XDA App
seems silly to me to evenrelease fr0x7 without the BT and the audo routing fixes already in place at least for the rhodium users., i understand that the BT and audio routing fixes are mostly RHOD specific so why not make 2 version's of FR0x7? Those are the changes that most ppl weant they want there BT and loud speakerphone. Just curious as to why it would even be released without those things since the fixes are out, if it means having to wait to release fr0x7 than wait IMO. i donno just my 2 cents
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
helicopter88 said:
Audio routing isn't stable,isn't for all the devices and it's still being developed
So it's a time waste adding it now,then frx08 will have it..
Click to expand...
Click to collapse
Couldn't have said it better myself. Audio routing will not be implemented until it's stable.
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Sent from my MSM using XDA App
madplaya1 said:
Shouldn't the dev start focusing more on gingerbread because it's newer, just wondering? Or what?
Click to expand...
Click to collapse
If you think GB has been forgotten, you are sorely mistaken. Your thread asked about FroYo, so that's what we've been talking about...
Lol ok
Sent from my PG06100 using XDA App
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
bArAbAts said:
hi there every1,
i was wondering if there is gonna be a working Camera in FRX07 for us Rhod100_nl users with the wrong board??
grtzzzz
Click to expand...
Click to collapse
Kernel issue, not a build issue from what I can tell.
Also, from what I've gleaned - the cam works, but only in low light. See
[UPDATED 04/29][DEV - Camera ( camcorder improvement ) ] Camera tests for more information.
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
EMB Driver said:
Bluetooth data would be great. I have an asus transformer which will not connect to an adhoc network, so WiFi tethering is out. The only solution I can find for tethering a honeycomb tablet is through pdanet tablet, which requires android on both devices and uses bluetooth. Thanks for all the hard work.
Click to expand...
Click to collapse
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
PlacidFury said:
Is there a wpa supplicant hack for the transformer? My A500 tablet has the same issue stock, but with mod or custom ROM wifi tethering to my rhodium works perfect on ad-hoc. Anyway, maybe worth looking into.
Click to expand...
Click to collapse
Yes there is. I'm on an adhoc posting this from my TF right now. check the TF section for the xoom supplicant file or just flash prime 1.5 as this fix is already implimented in that rom
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
gallahad2000 said:
Will it have the new MMS fixes? That's the biggest thing missing for me. People love to send pictures and I always have to boot WiMo and ask them to resend it.
Click to expand...
Click to collapse
Yes, it will work for all carriers assuming you set your APN. Still hashing out the best way to do this, might just have to leave it up to the end-users to configure.
I flashed prime on my TF last week. Works great and has the WPA supplicant fix already built in.
I can tether to my TP2 in winmo or whatever! Works GREAT.
Also, waiting for FRX07. Great work on FRX06!
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
bArAbAts said:
@arrrghhh, tnx for your reaction, but im not an android expert, is there a way to implement the fixes mentioned there in frx07??
keep up the good work!!
tnx!
Click to expand...
Click to collapse
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
arrrghhh said:
Not easily, there's many, many changes. The easiest way would be to pull from the XDAndroid repo (all of our code is available...) and build your own system image.
07 will be out soon. In the final stages of testing.
Click to expand...
Click to collapse
Is there a thread or website that shows the info on FRX07
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveats:
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
BT might still be flaky
The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
logcat attached
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
welard said:
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
Click to expand...
Click to collapse
Interesting, does any sound work...? Does it play thru the earpiece instead of the rear speaker? What about previewing ringtones? Next time you pull a logcat, make sure to use -v time. Using GetLogs makes it much easier .
Thanks for testing btw. The more the merrier! If we're going to make this change global, we want to make sure no devices are left in the dust. So it's up to you guys to test and ensure that it works properly! If it doesn't, we'll try to fix it.
If anyone feels like hopping on #xdandroid on freenode while testing, that would be great! Thanks again!
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
am20033 said:
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
Those commands are necessary if you have a SD card that doesn't play nicely. If you need 'em, put 'em in.
Thanks for the logs, I'll pass them on. Anything you can say about 'em? What happened during the logs...? Please be as specific as possible. The more information, the better.
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
arrrghhh said:
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
Click to expand...
Click to collapse
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
welard said:
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
Click to expand...
Click to collapse
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
arrrghhh said:
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
Click to expand...
Click to collapse
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
welard said:
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
Click to expand...
Click to collapse
Post those CSV's if you could!
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
hear are my csv's......thanks...
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
cbolumar said:
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
Click to expand...
Click to collapse
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
arrrghhh said:
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
Click to expand...
Click to collapse
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
cbolumar said:
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
Click to expand...
Click to collapse
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
arrrghhh said:
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
Click to expand...
Click to collapse
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
cbolumar said:
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
Click to expand...
Click to collapse
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
arrrghhh said:
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
Click to expand...
Click to collapse
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
cbolumar said:
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
Click to expand...
Click to collapse
Don't misconstrue, I haven't done any of the actual development on this acoustic code .
See Jerome's tree if you want to see where this all started. A few others have cloned his tree and made some modifications. We're still working out the kinks. Perhaps it can help your port as well...
Like I said earlier, I am betting the userland stuff will work for you folks without a ton of changes (don't know for sure!). The kernel stuff for this new acoustic will need to be ported - our kernel will not work on your device.
Hello,
I flashed my Arc with baseband 62 on the latest CM 9.0 FXP106. I'm pretty satisfied so far. The only thing that bugs me is that it seems that I can't add any APN's. That means if I want to add a new APN and I want to save it, it won't let me do it.
I tried backing it up with APNsBU (ROOT) -> didn't work
Hard reset -> didn't work
Fixing permissions in ROM Manager -> didn't work
Thanks for your help!
1.) Have you heard of posting in the relevant thread?
2.) It's a known bug. Read before post and use the search!
Sent from my LT18i using xda premium
Hey,
as I don't have 10 posts yet I can't post in the CM9.0/FreeXperia Thread.
I actually looked through a lot of posts and didn't find any relevant help.
Thanks for your reply though.
dont find it?it is already mention posted so many time..
Sent from my LT18i
this problem is in all xperia 2011, few networks operate
I have the same problem, does anyone know a way around this?
monstercable said:
I have the same problem, does anyone know a way around this?
Click to expand...
Click to collapse
Bin4ary posted a probably way to fix it, check out CM9's thread for more information.
Bin4ry said:
From what i can tell now the problem is that in CM9 we are using the ICS (ofc ) RIL-structure. There are already some oldRil features implemented, but this features are mainly for phones which use standard communications. We are having this weird Qualcomm RIL which acts different. For example we have no Status which tells System that SIM is ready, this status is piggybacked for us in another call.
On the other side we SE implemented some more messages for additional informations. For example: OperatorInfo is not standard one, it has one more entry.
So i need to go through the lines and check we're i can implement the different structure well without breaking other devices. Maybe i am able to trigger all needed parcel reads from RIL, maybe not. The main difference is lying in some other files which was still working in GB RIL structure.
Please wait for next week when i am able to work again on this issue. It's annoying me too
No. I will work on GSM data. Jerpelea will fix this problem ASAP.
Since we are 2 people working on this CM9 for the SE phones we can split the work.
And it is always better to work on 1 problem after another.
You see, 2 people -> 2 Todo lists
Regards
Click to expand...
Click to collapse
Thanks for your help. I didn't get that this was related to the APN issue.
This build was edited by me (mainly for my personal use), based off of Zips Creamed Glacier's 3.11 release, but contains fixes I pulled from IceColdInsomnia 6.2.1.
I don't normally start dev threads, so bare with me (I'm no dev)
What's new:
- Practically everything that's included in Zips Creamed Glacier 3.11 - includes, FFC unlock, Working games (Draw Something does work!), mdj's kernel and so forth.
- I fixed the weather/geolocation issues found in 3.11
- I fixed the USB mount issue in 3.11 (you couldn't mount as a mass storage device while the phone was on [gave you two options that didn't work])
- I fixed the full signal bars issue (reported full bars at all times you'd have service)
- Also included the romcontrol.apk from IceColdInsomnia 6.2.1 and the settings.apk (for those who wanted ROM control settings but had to use the widget shortcuts to use them, you no longer have to as it's included in the settings)
- Replaced the systemui.apk with IceColdInsomnia 6.2.1's (you can haz 4g icons!)
- Replaced Trebuchet with Apex Launcher (This was part of my personal liking, Apex Launcher is the best ICS launcher IMO, try it out)
- May be forgetting something else...
All of the fixes mentioned above were fixed by pulling their respective files from IceColdInsomnia 6.2.1
* Don't ask any of the devs for wifi calling, as it's assumed to not work until T-Mo updates wifi calling for ICS (which should be whenever a T-Mo phone officially has ICS) or unless a dev performs some sort of magic ritual and get it working and stable
------edit------
As of 3/29, 9:07 PM (Lol)
This is what I've got, thanks to one of our fellow users that found me on twitter and showed me this (I don't know what his user name is on XDA)
http://forum.xda-developers.com/showpost.php?p=24210094&postcount=932
My thanks goes to:
- zipsnet - his 3.11 build was used as a base, that's why games work and etc. (ICS thread link here: http://forum.xda-developers.com/showthread.php?t=1555574)
- blackwing182 - for certain files from his build to fix usb and location issues and the AOKP files for ROM control (will post which ones they were specifically later) (ICS thread link here: http://forum.xda-developers.com/showthread.php?t=1551456)
and those also to those mentioned in their thanks lists (tell me who I forgot to mention and I'll add you here)
Enjoy!
Downloads:
Original (From my minus account, lol): taken down for the time being...
kingsteve032's upload (should be faster to DL!): taken down for the time being...
Also:
- Here's the flashable low mic fix by lincore: http://forum.xda-developers.com/showpost.php?p=24008900&postcount=531
- Don't use the DSPManager that comes with the ROM and complain about volume levels. I'm not sure if this info is correct, but after snooping around in other device forums, like always, a dev put in his OP that the DSPManager isn't really configured for ICS but instead for CM7. I'm not sure if this is true or not, but I don't use the DSPManager anyways so
And:
- Check out this dev's new awesome and useful app: http://forum.xda-developers.com/showthread.php?t=1559185
Reserved...
Just in case...
I dont see the DL link!
There it is
And, did you include fixes such as Low-mic volume? And did you include the Mail app or does it need to be flashed?
Just posted it! I had to look for them, lol
linknight said:
I dont see the DL link!
There it is
And, did you include fixes such as Low-mic volume? And did you include the Mail app or does it need to be flashed?
Click to expand...
Click to collapse
Basically all that you would find in zips' build, I think the only app I took out was trebuchet and the only app I added was apexlauncher. If not, I can fix them later.
For the low mic issues, I didn't put those in my zip, but I can post the link to the fix in my OP.
I love this version of Zip's rom. Very stable. Daily driver. Thank you.
Excellent job! Let's hope the "OMG, you can't combine two different open source projects, that's disrespect!" trolls don't crap up this thread.
Sizzlechest said:
Excellent job! Let's hope the "OMG, you can't combine two different open source projects, that's disrespect!" trolls don't crap up this thread.
Click to expand...
Click to collapse
I was actually wondering why this wasn't done sooner, but since I know so little about how development works, I kept my mouth shut. It seemed like such a logical thing to do.
systemui.apk gives you the 4G icon
BUMP^^^
Downloading now will report, thank you
Update: working well smooth no fcs yet, face unlock works sometimes.
linknight said:
I was actually wondering why this wasn't done sooner, but since I know so little about how development works, I kept my mouth shut. It seemed like such a logical thing to do.
Click to expand...
Click to collapse
Lol, I started on this as soon as zips released 3.11 cause I wanted to fix games and try face unlock but he had the issue with the full signal bars and stuff.
blackwing182 said:
systemui.apk gives you the 4G icon
Click to expand...
Click to collapse
Haha, my bad. I don't remember which one it was that did it, but I did include both.
-edit-
I fixed it with my ninja edit skillz yo. Lol
Maybe I'm missing something... But I don't see a link
Sent from my MyTouch 4G using Tapatalk
cool! your own thread!
were you able to get wifi calling working?
Good job. Are you using mdj's kernel on this?
Sent from my HTC Glacier using Tapatalk
sckboy78 said:
Good job. Are you using mdj's kernel on this?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Yep, maybe I should add that in the post.
-edit-
I put it in there.
0.0 said:
cool! your own thread!
were you able to get wifi calling working?
Click to expand...
Click to collapse
No cause you didn't reply to my question!!! Lol
ringnutz said:
Maybe I'm missing something... But I don't see a link
Sent from my MyTouch 4G using Tapatalk
Click to expand...
Click to collapse
It's near the bottom of the OP...?
I2IEAILiiTY said:
It's near the bottom of the OP...?
Click to expand...
Click to collapse
Yezzir. Are you currently using tapatalk?, I'm guessing from your sig.
I2IEAILiiTY said:
No cause you didn't reply to my question!!! Lol
Click to expand...
Click to collapse
oh crud...skimmed over it haha. well, it went past the enabling screen. it actually connected, so i assume it worked. i never actually made a call on it tbh...
Are there any known 4.3 or 4.4 ROMs with working phone mic?
I've used CM 10.2 Stable (4.3) and Carbon Rom (4.4.2). Both work great, the only issue is that the headset is not usable for calls (low mic output). My solution for now is using the earbud/mic, but I'm curious to know if anyone has made progress on this. Aside from this, the various ROMs are near perfect for my needs.
I'm not very knowledgeable on the details of writing ROMs, but would any type of source code release from LG help developers solve this? Curious to know what the main hurdles are for the devs and what tools they need.
Thanks.
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Neroga said:
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
markusrussell225 said:
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
Click to expand...
Click to collapse
Still no luck on a solid working phone microphone (low volume on other end). And the search continues.
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
markusrussell225 said:
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
Click to expand...
Click to collapse
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
ja.andro said:
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ask because this is a problem has existed on all known roms since 4.3.1 for the E980 on ATT. Never been able to get a straight answer anywhere so I figure I would generically post it. I have reached out to some devs but not luck.
Any success on your searching?
thureos said:
Any success on your searching?
Click to expand...
Click to collapse
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
markusrussell225 said:
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
Click to expand...
Click to collapse
I saw that solution but I went back to rooted and debloated stock, I am very pleased with speed and stability.
Thanks
i've made the edits suggested on that post and still get the same issue...i dont remember having this issue before but i thnk youre right and the previous roms werent 4.4...oh well i live on the phone for work so back to stock for me. for now i guess...wanting a new phone anyways, hope we get the g pro 2 or g3 soon