• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10, AOKP41)

IMUcarmen said:
I don't get it. When I change that lib file it makes my dialer unusable. How come I'm the only one experiencing this. So not only does it not fix my issue, but literally creates a whole new one. Any ideas?
Click to expand...

That is odd? I followed your directions and it worked great for me. Weird.
 
azoller1 said:
Yeah I put the file in my ROM also and then the phone fc when I try calling someone weird....
Click to expand...

At least I'm not alone. Has done this to me on aokp and cm. It's very frustrating because I use speaker phone for every call I make and its so hard to hear
 
Now pushing the original files back isn't working. My phone keeps rebooting and the dialer is still unusable. This sucks
 
Hey neph...can you pm me or just post the directions for fixing call audio on cm10...I saw that you posted the file and said to push it in cwm, but is that different then just installing from sd while in cwm?
 
IMUCarmen and others, like afbcamaro stated, it's the permissions on the file. When you move the replacement file in there, you must modify the permissions on it to be 644, or RW-R--R--. You can use a terminal emulator or a file browser that can change permissions. Then reboot and you should be good to go. Any files to be replaced in the system areas need these permissions. If you guys aren't sure on getting stuff to work with these sorts of testing, don't worry about it. One of the other people can test it, and as TDM has shown, I'm sure he'll release a beta 3 with the fixes implemented in a very timely manner. I just hate to see one of you guys modify something you really didn't want to modify, then it's glorious fun to fix it.

Edit: If changing the permissions like this manually does not work, then the permission changer likely did not actually change the permissions. Possibly no actual root privileges on whatever app you used?
 
Well I know what permissions it needs and why it didn't work for me is I had tried using cm10.1 phone apk and was seeing if it would work but it wouldn't because I put the modded .lib file in my ROM I'm making so I think the .lib file for me was not why the phone app was force closing but instead the inverted cm10.1 phone app, and IMU Carmen didn't you flash those 4.2 apps? Maybe that's why
 
cryoaura said:
IMUCarmen and others, like afbcamaro stated, it's the permissions on the file. When you move the replacement file in there, you must modify the permissions on it to be 644, or RW-R--R--. You can use a terminal emulator or a file browser that can change permissions. Then reboot and you should be good to go. Any files to be replaced in the system areas need these permissions. If you guys aren't sure on getting stuff to work with these sorts of testing, don't worry about it. One of the other people can test it, and as TDM has shown, I'm sure he'll release a beta 3 with the fixes implemented in a very timely manner. I just hate to see one of you guys modify something you really didn't want to modify, then it's glorious fun to fix it.

Edit: If changing the permissions like this manually does not work, then the permission changer likely did not actually change the permissions. Possibly no actual root privileges on whatever app you used?
Click to expand...

Can you post a screen shot of the permissions you are taking about?.

How come this was never mentioned before and how come no one else is having this issue? It seems to me everyone is just moving the file and that's is all that is required for it to work. I'm not saying you are wrong but can you please post a screenshot of the permissions I need to set and I'll try it. I have a feeling its not going to work though
 
I used ES File Explorer to move the file. In ES settings, I went into root and checked all the boxes (including mount ./system/ as writeable). Then I copied libaudcal.so from /system/lib to the sdcard for a backup. Next I copied the file I downloaded from /sdcard/downloads to /system/lib, confirming overwrite. Finally I rebooted and all was good.

Just fyi...
 
Here's an example using ESFE with root privileges enabled. When you just copy the file over, it is only 600, or RW-------. You need to make it 644 or RW-R--R--.

3.png
 
azoller1 said:
Well I know what permissions it needs and why it didn't work for me is I had tried using cm10.1 phone apk and was seeing if it would work but it wouldn't because I put the modded .lib file in my ROM I'm making so I think the .lib file for me was not why the phone app was force closing but instead the inverted cm10.1 phone app, and IMU Carmen didn't you flash those 4.2 apps? Maybe that's why
Click to expand...

This is kind of odd. The .so file is the driver library that other applications utilize. If permissions aren't proper or the .so file is corrupt, any applications that utilize that library will FC do to the library not properly loading. Of course if the app is corrupt or incompatible to begin with, it will FC as well. Think of the .so file as a dll file for windows. Also I'm not trying to be demeaning to anyone or anything, so don't take it like I'm saying you don't know how to do something. Just covering all the bases. I forget to do things or just don't do things right even though I do those things all the time. If that sentence makes any sense. Try downloading another app that utilizes the libraries such as teamspeak or something like that. See if those FC on you.
 
IMUcarmen said:
Full wipe
Click to expand...
Even so, wipe only removes settings, data and apps, not the GPS files, so flashing the v7 first and testing it *may* be the solution.

TBH, I flashed the cab, but didn't engage gps before flashing cm10, so that might be the issue. It's possible the hardware isn't connecting to the software (maybe a kernel issue?) unless the hardware is active when flashed.
 
MrB206 said:
Even so, wipe only removes settings, data and apps, not the GPS files, so flashing the v7 first and testing it *may* be the solution.

TBH, I flashed the cab, but didn't engage gps before flashing cm10, so that might be the issue. It's possible the hardware isn't connecting to the software (maybe a kernel issue?) unless the hardware is active when flashed.
Click to expand...

That's how I got mine to work to: restored a nandroid that I knew had GPS, connected the GPS, than reinstalled AOKP41 and GPS came right up. I was even able to restore my AOKP41 nandroid and GPS still connected, even though it hadn't worked before on that install.
 
You must log in or register to reply here.
Back
Top Bottom