Need somebody who can replace a file using a file explorer without accidentally bricking the phone.
PM me, I don't promise anything, but my speakerphone doesn't work, and hence it's a possible fix for everything, I can't test it out properly.
I can test it, send me the file and I will test or post it here so the people cant test it too.
igoorsoouza said:
I can test it, send me the file and I will test or post it here so the people cant test it too.
Click to expand...
Click to collapse
Very well, I shall say it once. These are NOT flashable files, I just can't post .conf and .xml files to xda.
- Backup /system/etc/audio_policy.conf and /system/etc/mixer_paths.xml
- Replace them with these files
- Report back whether X is working or Y is broken including your ROM (must be AOSP).
Seems to be working, music plays but i don't know if something is different, whatsapp audios and call seems to work properly but I'm listening to my voice while in Whatsapp call, in Skype conference the sound is very good. I'm still testing and like i said I'm using the Euphoria ROM and its hard to know if something changed like the music audio volume and other sounds but thanks for the work I will keep testing.
Well, someone has clearly downloaded it and hasn't reported back... Anyone else have any comments? I mean, if it's actually fixed, I can help get it merged where it's needed or whatever.
I just don't see the point of downloading the files I provided and then not posting in this thread :cyclops:
I'll be glad to test. I'm on a D806 from Argentina. PM me if I can help you. I'm now running a cm based CAF ROM which doesn't have that bug, maybe I can help you with something here, and also test in the ones that doesn't work.
Enviado desde mi LG-D802 mediante Tapatalk
hi,
thanks for this!
i can't test. i have a couple of friends that have the d800 with cm12, but not me. i would gladly apply a fix for them if there was one that has been validated. but i can't go fishing around on their phone, i dont see these guys daily.
Lanchon said:
hi,
thanks for this!
i can't test. i have a couple of friends that have the d800 with cm12, but not me. i would gladly apply a fix for them if there was one that has been validated. but i can't go fishing around on their phone, i dont see these guys daily.
Click to expand...
Click to collapse
Just give it to anyone with whatsapp/skype/microphone issues, have them backup the two .conf files, try it out and have them report back.
I can't say for sure this works on stock roms as well, as nobody bothered to give me a stock .conf or report if it works or not.
Choristav said:
Just give it to anyone with whatsapp/skype/microphone issues, have them backup the two .conf files, try it out and have them report back.
I can't say for sure this works on stock roms as well, as nobody bothered to give me a stock .conf or report if it works or not.
Click to expand...
Click to collapse
problem is, none of them can tell a file from a banana
Reporting:
I've tested it in RR, Bliss, Candy and Euphoria but none of them worked
Enviado desde mi LG-D806 mediante Tapatalk
Replaced both of them, rebooted, no effect noticed
Microphone is still ramping up as hell, when im not talking
i looked at the differences between your files and the CM12.0 ones, they are way too many. you obviously got them from a different source. where are they from? the stock lolli?
Related
I compiled my first ROM from source FRF91 for N1 w/root su+busybox+de-odex+gapps. The time of my AOSP -b master sync was around 9:00a pst, 07/10/10. This is not a "kang" of Modaco or CyanogenMod but I credit both and all teamdouche since I regularly need to look into their work to teach myself. Thank you dferreira and jr33 for not flaming my many noob questions and also thanks to dsixda for his reqularly updated android kitchen.
I still can't do much customizing and adding features because I still have to get better at too many things...sorry. Feel free to report bugs and I hope some of you could tell me how to fix simple things or add features by directing me to resources.
I am using themes by micromod777 for FRF91 that do work on this ROM.
Added:
Original Boot Animation (aka Holiday)
APN list
Trackball wake/unlock (crimsondr)
NFL app (jlevy73)
AccuWeather widget (allows multiple locations)
Logger app (michael.novakjr)
If you don't have the new radio installed, fastboot flash radio first.
Flash the ROM .zip after full wipe.
Remember to to do a nandroid backup first.
Radio Download >>> 3321c196d8ec1cf748fd20c3c4068520 32.36.00.28U_4.06.00.12_7 radio.img
(Fastboot flash using "fastboot flash radio radio.img")
ROM Download >>> 6af5516125105c92d8a3d87c6110defc shameless_aosp_frf91_1.0_signed.zip
...saved...
Really had to bump your Rom because no one was using it? nice...
nopenope said:
Really had to bump your Rom because no one was using it? nice...
Click to expand...
Click to collapse
Why this kind of comments? Do u think they help in anyway?
Sent from my Nexus One using Tapatalk
He's also the kind of guy who knows nothing other than wipe & flash and has nothing positive to offer the community... =/
nopenope said:
Really had to bump your Rom because no one was using it? nice...
Click to expand...
Click to collapse
no... i bumped it because i had an old post that i wanted to re-title and use. that post had no replies so i recycled it. why the hate?
Quick84 said:
He's also the kind of guy who knows nothing other than wipe & flash and has nothing positive to offer the community... =/
Click to expand...
Click to collapse
thanks for trying out this rom guys. it is not a cut-n-paste. i really did compile from source. it took 5 alphas to get to this release. it is like a hobby for me to try and solve puzzles and that's how i tackled making the rom. i have zero programming knowledge and have fun relaxing trying to follow steps in a process to accomplish a goal.
When will you work on your desire rom project again? We really need someone to work on desire port beside paul. hopefully you can challenge yourself and make that desire rom perfect.
lpasq said:
no... i bumped it because i had an old post that i wanted to re-title and use. that post had no replies so i recycled it. why the hate?
Click to expand...
Click to collapse
If you added stuff then cool but just the post saying *bump* not added new things to first post makes it seem that you just wanted your post to the top again. And to the guy who says i've never done anything for this community you might wanna change that and then your post well what have you done. my reply is don't worry its more then you'll ever. SO props to the update then
nopenope said:
If you added stuff then cool but just the post saying *bump* not added new things to first post makes it seem that you just wanted your post to the top again. And to the guy who says i've never done anything for this community you might wanna change that and then your post well what have you done. my reply is don't worry its more then you'll ever. SO props to the update then
Click to expand...
Click to collapse
thank you. ...not an update though. it's a source build compile. the post i recycled had a paste-n-bake kang of an early aosp 2.2 that chris soyars put out via a tweet... ...and hundreds of people downloaded it but not one person posted a reply since i made clear i simply was passing it along.
so you know... i think the other flame was also intended for me...not you.
not bad! gonna give this a shot!
How about compiling Stk.apk and extract the dictionaries from the LatinIMEGoogle.apk and putting them in the corresponding locations in your LatinIME source. That will get you more layouts than the Google keyboard and still all the features since they have now been included in the AOSP version. The Stk.apk (SIM Toolkit) is also useful for a lot of people, and only work AOSP based roms, and might possibly drive more people towards this rom if they want the stock experiance.
It should simply be a matter of running 'make -j4 LatinIME' and 'make -j4 Stk' with the -j flagset to your number of cores + 1 or 2.
blunden said:
How about compiling Stk.apk and extract the dictionaries from the LatinIMEGoogle.apk and putting them in the corresponding locations in your LatinIME source. That will get you more layouts than the Google keyboard and still all the features since they have now been included in the AOSP version. The Stk.apk (SIM Toolkit) is also useful for a lot of people, and only work AOSP based roms, and might possibly drive more people towards this rom if they want the stock experiance.
It should simply be a matter of running 'make -j4 LatinIME' and 'make -j4 Stk' with the -j flagset to your number of cores + 1 or 2.
Click to expand...
Click to collapse
I shall pm you prior to attempting so I can get clarification on any questions I may have. Thank you.
Sent from my Nexus One using XDA App
I'm working on the same kind of project you are. The problem I'm running into is that every app that tries to access GPS location FCs on me. Did you ever come across this? Maps won't run at all, and I've had to set my homepage to something other than Google since it FCs the browser when it calls for location. I've got a working build otherwise!
RMGeren said:
I'm working on the same kind of project you are. The problem I'm running into is that every app that tries to access GPS location FCs on me. Did you ever come across this? Maps won't run at all, and I've had to set my homepage to something other than Google since it FCs the browser when it calls for location. I've got a working build otherwise!
Click to expand...
Click to collapse
Very cool that you have a working build environment. What OS are set up in?
I do not get the error you describe. Run a logcat either with ADB or using Logger from Market. Reading the log makes it easier to ask for help based on the specific errors. That is what I do. Ask the pros for advice. Some are helpful. Most ignore us noobs.
I am happy to offer whatever help I can as a rookie. Just PM me.
From N1 via Tapatalk
lpasq said:
thanks for trying out this rom guys. it is not a cut-n-paste. i really did compile from source. it took 5 alphas to get to this release. it is like a hobby for me to try and solve puzzles and that's how i tackled making the rom. i have zero programming knowledge and have fun relaxing trying to follow steps in a process to accomplish a goal.
Click to expand...
Click to collapse
I'm in the exact same boat, just jumped into android about a month or two ago with my nexus (from an iPhone 2g, no less lol), ain't no turning back now
I'm also building a rom from source, more as a side-project to better familiarize myself with Android, but if it turns out well then that's always a plus.
Good luck on your rom!
wdfowty said:
I'm in the exact same boat, just jumped into android about a month or two ago with my nexus (from an iPhone 2g, no less lol), ain't no turning back now
I'm also building a rom from source, more as a side-project to better familiarize myself with Android, but if it turns out well then that's always a plus.
Good luck on your rom!
Click to expand...
Click to collapse
it is nice to know that other "hobbyists" are playing with aosp and the tools used to make roms. much success to you my brother
Hi Folks,
I have decided to post this fix as a separated thread because the gigglebread thread is growing incredibly fast and the reference to it gets lost in one or two days after being published.
When GB was at v5, I wrote this post on its thread, to offer to the community a fix that I've created to my device, because I realized that my pain could be the pain of others.
Well, that fix does not works on v8, it puts the system in a infinite boot loop. Therefore I rolled up my sleeves again to update it. And here it comes the updated version. Enjoy while it's hot.
Best Regards,
Ed.
could you please tell us what this fixes and is installation via custom zip option in xecovery?
Thanks in advance.
Hi, I'm sorry for this. The explanation was on the post linked in the previous message... Here's the Quote of that post:
edsena said:
Hi Folks,
I've been following this particular thread since its first day (coincidentally the same day that I started using an Android phone).
The main motivation for using this rom was that to be able to replicate my corporate e-mail and calendar. In order to do that, I would have to be, at least, using Android 2.2, because the company that I work for restricts access to earlier versions because the changes on the lock screen password options that took place on v2.2.
Despite of a few minor remaining bugs, this ROM works pretty well on my device. But, there is an issue that was really pissing me off: The inability of sending DTMF tones using the digits 0*#, because of the layout of the screen. Since I have to join several conference calls per week, that is a huge show-stopper for me. Well, I'm pretty sure that the creator of this ROM is quite busy working on some serious issues (like bluetooth) and do not has the time to take a look into these cosmetic issues, that's why I decided to roll up my sleeves and work on this.
I finally went thru this, and I decided to share this fix on the forum, since I read a lot of people talking about this issue as well. Attached to this post is an update zip file, which will tweak the position of the component of those screens, in order to allow the full visualization of both dialpads (in-call & initial).
To install the fix, just copy it to your sdcard and install it via xRecovery. Please take into account that this comes with no warranty at all, is provided *AS IS*, and I don't want to be responsible should anyone damage a device, loose data, etc, trying to install this package. I only tested it on my phone (where it worked like a charm) therefore I can't guarantee that it will work on other setups as well.
If you like this fix, please click on "Thanks" and feel free to send some bucks to finance some Duvels, Karmeliets or Guiness
EDIT: I've just added a tweak to the "Rotary Selector" to keep it from being in front of the "Calling Card" when an incoming call is received. Therefore now there's 3 zip attached to this post: One that has the 2 fixes and another one for each fix. You can figure out which is which by their names, which are pretty straight forward.
Best Regards,
Ed.
Click to expand...
Click to collapse
@edsena--thanks for elaborating;your original input did indeed get buried under the avalanche of responses to naa!
Awesome fix mate. Great job. But I see *#0 missing when the on call number pad is opened. Any way to fix that?
Sent from my E10i using XDA App
Have installed this and it works smooth .
work perfect in x10 mini pro
thank's.
works awesome! thx for the fix have you sent this to owain? he may post it in the first post
Perfect! Very Good fix!
Sent from my E10i using XDA App
Orkeren said:
works awesome! thx for the fix have you sent this to owain? he may post it in the first post
Click to expand...
Click to collapse
Or include it in his next version?
ruifung said:
Or include it in his next version?
Click to expand...
Click to collapse
That would be cool. Thanks edsena for these fixes.
Cheers,
evilbarcode.
ruifung said:
Or include it in his next version?
Click to expand...
Click to collapse
or that But I suppose that it would need some rewriting, as the old fix (released for v5) didn't work with v8... And it's just a cosmetic fix As far as I know Owains highest prioritys with this rom are FM and some bugfixes on apps not working...
Works Perfectly
Works like a charm!
Thx for this fix!
wow thx a lot dude..works perfect in my mini pro
sachith024 said:
Awesome fix mate. Great job. But I see *#0 missing when the on call number pad is opened. Any way to fix that?
Sent from my E10i using XDA App
Click to expand...
Click to collapse
This fix is supposed to solve that. Isn't it working for you ? Is anyone else experiencing the same issue ?
dude update it for V9 pls... not working in V9.. getting stuck at boot animation in v9..
raghurags said:
dude update it for V9 pls... not working in V9.. getting stuck at boot animation in v9..
Click to expand...
Click to collapse
Same with me. Request seconded
v9 have app .odex... ?? no .apk??
:S
plz. dude, we need it for v9 plz. thanks alot
now we need it for v10 man
So I flashed the xdark ics rom and then flashed the CM9 CDMA fix and Carrier fix files to see if it would work. And I was able to use the ROM to make several successful calls and even activate via the *228 but was not able to use any 3G data. Wifi, calls and pretty much everything worked great. My questio is if anyone here would be interested in taking a stab at getting 3G data working? I do not know if its just a matter of editing the build.prop or the phone apk. But just wanted to let all R800x users know that at least calls are working so technically you could use this as an every day for calls only and wifi.
Here is the link to the ROM. I am not the creator of this rom and take no credit for it whatsoever. That goes to xdarkmario.
Here is the link to the link.
http://forum.xda-developers.com/showthread.php?t=1729250&page=15
Here is what I wrote in my post regarding my outcome of flashing the said files.
-----------------------------------------------------------------------------------------
This is from post #150 (page 15)
So I have a CDMA R800x. I flashed this ROM and the CDMA Fix from Atarii and the Carrier fix from other ROMs and I was able to activate my phone via *228 from Verizon. I do not have 3G data, but I can make calls and wifi works when i flash the Doomkernel ICS wifi modules.
Would you be willing to look into the 3G data aspect of this ROM and see if its possible to get that working on this ROM?
Alsok this ROM is pretty cool so far. Very Clean.....
The carrier fix / CDMA fix were made to make any GSM CM9 ROM work on the R800x
Please niote, first time I use the dialer I get a com.android.phone error, but then it dials and works fine.
-----------------------------------------------------------------------------------------
I would like to get peoples thoughts on this as to how we can get 3G data working.
If I'm not mistaken the guy hacked up like three different roms and slapped them together. And I think it was partially the sony beta which will essentially screw us and put us at the point we are still on in finding a way to turn non aosp/aokp based roms for cdma. Maybe some new minds can figure something out for us abused X plays
I don't know what the basis of this ROM is but I did flash the CM9 CDMA fix and was able to make calls. Just no data. So that at least kills one of two problems right there.
Sent from my R800x using xda premium
So I guess no one is interested in attempting to get 3G data working on this ROM? Calls work just fine........ just need data working. Would it be something as simple as some build.prop edits or at most a phone.apk messed with.... anyone?
Logcat?
Supervenom said:
Logcat?
Click to expand...
Click to collapse
Oh yeah, I forget about logcat sometimes. I will download it and see what it comes up with and post the results here. I have never used logcat before.
jgregoryj1 said:
Oh yeah, I forget about logcat sometimes. I will download it and see what it comes up with and post the results here. I have never used logcat before.
Click to expand...
Click to collapse
Pax showed me a pretty nice app called "catlog" for log cats while your phones on, just thought Id share!
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
216Monster said:
Pax showed me a pretty nice app called "catlog" for log cats while your phones on, just thought Id share!
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
Click to expand...
Click to collapse
Just downloaded it. I am currently on my nandroid of 2.3.3 but will save the catlog app and later tonight or tomorrow when i have time I will run it and post the results of the LogCat here. Thank you 216Monster for the suggestion
I'd really like someone to get this working. I love this ROM and just flashed it.
I gave up on the project. I simply don't have the Tim's between wife, kids, work, etc to spend the proper time I need to figure everything out. Anyone willing to take the torch and run with it? Ill admit R800x users are on the short end of the leash. With that said I appreciate LLC the devs efforts to make things for own cdma phone even when they do jot have our specific model.
Sent from my R800x using xda premium
jgregoryj1 said:
I gave up on the project. I simply don't have the Tim's between wife, kids, work, etc to spend the proper time I need to figure everything out. Anyone willing to take the torch and run with it? Ill admit R800x users are on the short end of the leash. With that said I appreciate LLC the devs efforts to make things for own cdma phone even when they do jot have our specific model.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
I'm doing some testing now.
EDIT: Not working. I changed the APN settings and it still didn't work.
---------- Post added at 02:18 AM ---------- Previous post was at 01:47 AM ----------
Anybody need a logcat?
I'm a complete noob with modifying Android system files. But anyway, I noticed the APN folder and xml file are not in the SemcPhone.apk. That may be a problem and a cause as to why the phone app force closes.
Well, that time has come. I feel like our ROM is stable enough that I can finally proide support for it without you guys (unintentionally) clogging up the dev thread.
If you have a question, POST IT HERE. If you want to ask about install issues, how to get into devving, or rabid toasters, POST IT HERE. I am closing off the dev thread now that this is created. If you post there without a constructive helpful comment (I will put up criteria there), you will get yelled at, beaten, and sent to slink back to your hole from whence you came.
Okay, now that that's over, I will be providing support in this thread. I am not mean, scary, nasty, or like to drown puppies for fun, despite what the impression the above may give you. I am actually a very helpful person (as most pre-existing members here will agree), and will try to help you, even if you think it's a stupid question.
One rule here: Search first!
I cannot emphasize how important this is. As I said, I am more than happy to answer questions, but for the love of god please don't post something like "wherez the ICS guyzz, I don;t see it in this thrad, this forum sukks". Please use search first before posting. Thank you, and have a nice day.
Well, have fun, and I will answer any questions you have (even if they don't directly relate to ICS).
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
Guides (thanks to goldflame for these):
Drm manager
YOU MUST HAVE ROOT IN ORDER TO DO THIS!!!!
http://forum.xda-developers.com/showthread.php?p=31201787
Run this in terminal with su permissions
Open terminal Type su Accept the superuser request Follow the code from the post One condition if you reboot you have to repeat the third line of code.
This will fix the market
Here is rooting:
Download tsparky root on your computer from here: http://forum.xda-developers.com/showthread.php?p=31067529
Extract the zip plug in your Samsung, turn on USB debugging which can be found in settings-devoloper-usb debugging and run the bat file.
For those of you like me that when you open super user it fcs, here is a guide on how to fix that:
I have rooted, super user won't open now
OK follow theses steps
1) download and install Android commander (Google it)
1a) plug in your device and make sure USB debugging is on
2) open android commander
3) on the right panel go to /system/app and delete super user.apk
4) then go to /system/xbin and delete busybox and su
5) reboot and root again
Worked for me and two other people so it should work for you.
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
da1writer said:
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
Click to expand...
Click to collapse
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
hanthesolo said:
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
Click to expand...
Click to collapse
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
euphoriaflow said:
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
Click to expand...
Click to collapse
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Same at the epic 4g touch forums, but to be honest, I don't mind it being here at all. Not too late to move this over there, though.
Sent from my SPH-D710 using xda app-developers app
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
I do have the pass (I saved them in case we forget it). Also klin, it is considered for general but can be considered like dev too (in the sense of error reporting).
klin1344 said:
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
This is a subsection of our development thread, and while it may be better placed in general, it is best here, as we remove the chance of people who create accounts just to complain, and we obtain easier access for users. Plus, I believe I may have an idea to put the community to work, I just need to polish it a bit more.
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
Can't you reset it. Should be easy if you put a recovery email
Sent From My YP-G1 running ICS build 3.5
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
crancpiti said:
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
Click to expand...
Click to collapse
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
daniel644 said:
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
Click to expand...
Click to collapse
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
daniel644 said:
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
Click to expand...
Click to collapse
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
goldflame09 said:
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
Click to expand...
Click to collapse
Hold up a sec, I'm unsure of the situation a bit here... does oisis HAVE a Samsung Galaxy 4.0?
If not, I'm willing to toss a couple Tens his way (won't mention how much here) with a stipulation. I'm talking about Amazon Credit (which I have alot of) here... An Amazon gift card (via email) would have to be used as Amazon being the purchase website. PM me if there is an interest oisis if this is the case of you not having an actual SGP 4.0 ...
Edit: Ok, I just read that oisis actually did order one from China (?) but if it takes too long I'm still willing to help money wise if needed for any of these great 4.0 devs here developing the ICS rom
zaclimon said:
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
Click to expand...
Click to collapse
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
daniel644 said:
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
Click to expand...
Click to collapse
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
zaclimon said:
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
Click to expand...
Click to collapse
Yeah a file explorer (file browser) so I can access the LEGALLY obtained .apk's I've collected from the developers websites, to install them. for whatever reason there is NO file browser app in this CM9.
Edit1: This issue have workaround found to be raliable-ish, see post 6.
Edit2: I've figured it out, see post 12.
Greetings!
My device is Redmi Note 4X black 3/32GB. I have an issue with the microphone not working, but only during phone calls and only when using the built-in earpiece for communication. Switching to loudspeaker mode or plugging hands-free makes it work again.
This issue is reproducible only on custom AOSP based ROMs, but works as expected on Mi A1 ported ROM and on official and customized MIUI.
It's kinda strange, because some guys here don't encounter such problems with either the RN4(SD) or the RN4X(SD), both code-named "mido".
nasko_spasko said:
Greetings!
My device is Redmi Note 4X black 3/32GB. I have an issue with the microphone not working, but only during phone calls and only when using the built-in earpiece for communication. Switching to loudspeaker mode or plugging hands-free makes it work again.
This issue is reproducible only on custom AOSP based ROMs, but works as expected on Mi A1 ported ROM and on official and customized MIUI.
It's kinda strange, because some guys here don't encounter such problems with either the RN4(SD) or the RN4X(SD), both code-named "mido".
Click to expand...
Click to collapse
Read this : https://forum.xda-developers.com/re...dia-sounds-t3682812/post74247791#post74247791
sachin n said:
Read this : https://forum.xda-developers.com/re...dia-sounds-t3682812/post74247791#post74247791
Click to expand...
Click to collapse
Thanks! I'll try and report, but I have issue with the mic, not the speaker.
nasko_spasko said:
Thanks! I'll try and report, but I have issue with the mic, not the speaker.
Click to expand...
Click to collapse
Oh, nvm! Sorry.
I have same problem and dont find a solution.
I've found some sort of a workaround for this issue. The problem described in the thread is kinda different than mine, but seems to fix my problem too. It's in this XDA thread. All i did was flashing the two zip files from zile995: fix-audio-*-zile995.zip at the bottom of the OP.
As I said, this is a workaround, not a fix. If you know some of the maintainers for the device tree for LOS, feel free to mention them in this thread. I could make a fix proposal miself, but I don't have the time to invest in this. However if no progress is observed in the next couple of week, maybe I'll try to make it work and propose a fix to be pushed to upstream, so no more dirty flashes of patches to be required for the mic to work properly during a phone call.
Ok i will test too.
Edit: I have test and its work but i dont have lte and the other side say the volume is very low.
Schrotty35 said:
Ok i will test too.
Edit: I have test and its work but i dont have lte and the other side say the volume is very low.
Click to expand...
Click to collapse
Tested ot on LOS 14.1 and RR Nougat, in my case LTE works and the other guy says it's too loud. How come?
I have test with latest rr too. I dont know what is the problem. In the other Thread i have see there is a v6. I will test with this. Have you install both fix after install Rom direct?
Schrotty35 said:
Have you install both fix after install Rom direct?
Click to expand...
Click to collapse
Yup! It's not necessary, though. Flashing the v2 version is sufficient in my case. build.prop version does nothing. I'll play with it further during the weekend.
Cheers!
I have found a good fix which work for me.
You found it here https://forum.xda-developers.com/showthread.php?t=3630473
Done, fugured it out
Greetings, ppl!
I know it's been a while, but I've finally figured it out.
The property 'persist.vendor.audio.fluence.voicecall' should be set to 'false' instead of 'true'.
In the Official and all MIUI based ROMs it's set to false, but in all AOSP based ones it's set to true, which breaks in-call audio for alot of people, at least the ones with newer revisions of the board. So next I'll try to fork the device tree from the LOS project and modify it accordingly and build the ROM with it and see if it finally works out of the box.
Oh, such a relief! The mic finally works when calling people.
Could you please try and report? You're not supposed to, though. Flashing roms and testing configs can be annoying sometimes.
Happy holidays!
nasko_spasko said:
Greetings, ppl!
I know it's been a while, but I've finally figured it out.
The property 'persist.vendor.audio.fluence.voicecall' should be set to 'false' instead of 'true'.
In the Official and all MIUI based ROMs it's set to false, but in all AOSP based ones it's set to true, which breaks in-call audio for alot of people, at least the ones with newer revisions of the board. So next I'll try to fork the device tree from the LOS project and modify it accordingly and build the ROM with it and see if it finally works out of the box.
Oh, such a relief! The mic finally works when calling people.
Could you please try and report? You're not supposed to, though. Flashing roms and testing configs can be annoying sometimes.
Happy holidays!
Click to expand...
Click to collapse
i have exactly same problem
already wrote here in this sub forum without any response from the members here
will try today at the office and report to you later
thank you for sharing
done editing to false, now incall is nice but i hear low voice from other party in speakerphone mode although volume is full. ?
but it was more than enough since i dont use speakerphone mode that much
really appreciate your finding my friend
groovepeppy said:
done editing to false, no incall is nice but i hear low voice from other party, volume is full.
Click to expand...
Click to collapse
have you tested it on clean isntall? I mean no other patches applied?
nasko_spasko said:
have you tested it on clean isntall? I mean no other patches applied?
Click to expand...
Click to collapse
pardon me, the connection is bad over here
i believe i have edited my post because it was full of typos but it turns out its not edited yet.
please re-read the post you have quoted.
fyi, i clean flashed PixelExperience 8.1 ROM right after i arrived at work
setting this and that, root the phone using latest Magisk, install Root Explorer and did what you have wrote on post #12 and yes, i did not use any patch, just your workaround
Reboot the phone, test calling and i smile very wide.
one thing i found, setting up Google Assistant can't be done
it told me to say "Ok Google" but the app didn't hear me
so i change all of the "almost identical" line to false, like this....
persist.vendor.audio.fluence.voicecall=false
persist.vendor.audio.fluence.voicerec=false
persist.vendor.audio.fluence.speaker=false
Click to expand...
Click to collapse
Google Assistant recognize my voice now
But the speakerphone mode stay the same, the voice from the other end aren't loud enough.
once again say thanks to you for your effort
feel happy that i'm not the only one suffering this problem LOL
I still face the issue after editing build prop..
hi @nasko_spasko
I'm getting a bit irritated by this phone
How come i am (maybe with you too) the only one having this problem
Last night i look at latest xiaomi.eu build prop and i decide to get all audio related lines and overwrite the related lines in pixel experience's rom build.prop
crossing my finger here, wish me luck man
edit:
still i get very small volume for speakerphone mode
anybody knows how to gain the speakerphone output level?
@nasko_spasko
finally i fixed it
mic working fine in call
loud speakerphone
i did what he told me here.....
https://forum.xda-developers.com/showpost.php?p=74000643&postcount=210
change fluencetype to none and add one line in audio_platform_info.xml
reboot
works like a charm
by the way, i still use pixel experience rom.
groovepeppy said:
@nasko_spasko
finally i fixed it
mic working fine in call
loud speakerphone
i did what he told me here.....
https://forum.xda-developers.com/showpost.php?p=74000643&postcount=210
change fluencetype to none and add one line in audio_platform_info.xml
reboot
works like a charm
by the way, i still use pixel experience rom.
Click to expand...
Click to collapse
Thanks for lot! But, can you write the line to add in audio_platform_info.xml?
I'm in pixel experience too.