Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
$> su
#> alsa_amixer
It throws some error but It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
nice catch man...anybody with f240 already tested this?
will try to download cm11 roms and definitely going to try this one...
Thank you!
notohp said:
Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
prompt> alsa_amixer
It throws some error about module not found or something. It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
Click to expand...
Click to collapse
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
esaintor said:
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
Click to expand...
Click to collapse
Yes just that. You can flash it right after flashing roms. :good:
no luck.
notohp said:
Yes just that. You can flash it right after flashing roms. :good:
Click to expand...
Click to collapse
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
esaintor said:
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
Click to expand...
Click to collapse
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Still...
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I tried on omni but no success
I executed this command didn't restart still no sound
esaintor said:
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
Click to expand...
Click to collapse
Okay I will test it with omni rom once I am back home. Could you point me to the link?
here is the link
notohp said:
Okay I will test it with omni rom once I am back home. Could you point me to the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2562998
GOT IT!!!
esaintor said:
http://forum.xda-developers.com/showthread.php?t=2562998
Click to expand...
Click to collapse
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
esaintor said:
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
Click to expand...
Click to collapse
Glad you got it worked...may be this line ..."I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine," had a brief mention but anyway...I will edit the OP...:good:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
nguyenthienqui said:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
Click to expand...
Click to collapse
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
esaintor said:
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
Click to expand...
Click to collapse
i had same problem with my f240k Android OS drained alot of battery so I switched to Mokee 4.4.2, its AOSP so like 99% CM
battery problem is fixed so is sound....get around 4 hours of SOT
try it if you like:
http://forum.xda-developers.com/showthread.php?t=2639469
Tested of F240L
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
mudu8 said:
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
Click to expand...
Click to collapse
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
notohp said:
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
Click to expand...
Click to collapse
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
mudu8 said:
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
Click to expand...
Click to collapse
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
notohp said:
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
Click to expand...
Click to collapse
I'm not very conversant with the methods of kernel extraction etc.
I reckon you could compare the chinese CM11 Kernel to the stock CM11 one and see which files need manipulating in order to get it working and also what differences exist between the E98X and F240x models.
No pressure though it just my opinion.
It seems F240 models get little support around here, so if we could figure this out it would be great.
Related
I'm fairly new to custom roms and flashing. On my AT&T Galaxy S3, I decided to update to 4.3. However, I tried updating ota using the About Phone > Software Update, however, that wasn't working for me (It kept saying: No updates available). I knew this wasn't true, so I searched around and found an option (In which all I had to use was the stock recovery and flash it on there, so I did. However, I found out about Knox and how rooting is not an option with knox, so I decided to look into custom roms. I got a custom recovery, noticed warranty bit 1, don't really care about that since I'm out of warranty anyways. So I flashed a lot of custom roms and their versions (Cm 10.2/11, Paranoid Android, Slim Bean, Illusion, and more) only to find out that I can't play any videos (browser, youtube, 3rd party apps, gallery, and even recording camera didn't work)(Also audio doesn't work at all). Now I want to switch back to regular stock 4.3 using the same file I used before. I tried flashing with a custom recovery (twrp and cwm) and it kept giving me:
(assert failed: file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2:user/release-keys" ||
file_getprop("/system/build.prop". robuild.fingerprint")
== "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB:user/release-keys"
E:Error in /sdcard/update43.zip
(status 7)
Installation aborted)
I searched around, and other people got this error mostly on a nexus when trying to get back to stock firmware. I found out that I need the stock recovery for the samsung galaxy s3 At&t, which I've searched around, and I can't find. Does anyone know a thread, or can upload their at&t samsung galaxy s3 stock recovery?
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
codemonkey98 said:
Status 7 is an error in the updater script. You may have a bad zip. Have you checked the MD5SUM in the zip that you downloaded?
Click to expand...
Click to collapse
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
danman0 said:
I re-downloaded the zip (which worked before on stock recovery). I don't know how to check the md5sum (On most roms, maybe this one since this one doesn't get to the point where it checks for it, it says checking for md5sum, then later says no md5sum found and skips). Maybe this is because It's expecting me to be on the "samsung/d2uc/d2att:4.1.2/JZO54K/I747UCMG2" version so I can update to the "samsung/d2uc/d2att:4.3/JSS15J/I747UCUEMJB" version. On Keyes 3 under my device apparently my current version is:
I747UCUEMJ2/I747ATTEMJ2//I747UCUEMJ2
And Keyes tells me that my devices current firmware is not supported to update firmware via keyes. Any ideas how to get back to stock? Also, does anyone have a clue why any sound and any video won't work on custom roms for me?
Click to expand...
Click to collapse
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
n_alvarez2007 said:
I've had this issue before, VERY annoying. What I did was I downloaded a program for Windows called Notepad++ which allows you to edit the md5sum file.
What you need to do is unzip the file and search for the md5sum file and open it in Notepad++. Delete the lines that read "assert" and have the troublesome ID you mentioned in the OP. Re-zip the file and try flashing it again. Should be fine.
Click to expand...
Click to collapse
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
danman0 said:
I already have notepad++, but where do I search for the md5sum, since I've wanted to use Odin to flash this but it isn't a tar or md5 file. Should I check the updater script? And is this the reason audio and video don't work on any custom room I try?
Click to expand...
Click to collapse
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
danman0 said:
Sorry for sounding like a noob, but I am new to all of this. All I need is some help, I would prefer to run custom roms over stock (I like Illusion) except for video won't work as well as audio? Is there any way to fix that at least, or is there a way to fix my rom/recovery?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Ali7000 said:
http://www.sammobile.com/firmwares Search for you're model and download the LATEST firmware. Returning to 4.1.2 or lower will brick you're phone
Click to expand...
Click to collapse
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
danman0 said:
Can't do that since At&t update 4.3 (Latest) is pretty much ota and can't be downloaded from that site. It only goes up to 4.04.
Click to expand...
Click to collapse
http://www.sammobile.com/2013/11/20/android-4-3-rolling-out-for-the-att-galaxy-s-iii/ Just a news update
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
COfatboy said:
Have you tried this rom?
http://forum.xda-developers.com/showthread.php?t=2252932
I have been running this and have had no problems with anything working. As others have said don't flash anything besides 4.3 or you risk bricking your phone.
Click to expand...
Click to collapse
I am flashing this right now. I hope that this will work. It turns out that only mxplayer videos work, and no other third party video app. I looked around and these issues are most likely from not updated binaries or something, as mentioned in some threads.
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
danman0 said:
Turns out that this rom: http://forum.xda-developers.com/show....php?t=2252932 doesn't work on my phone since it just never boots from the glowing samsung logo. I have attached a link to my video of how audio and video don't workand and only work on mxplayer.
http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
danman0 said:
I tried a bit later and got this rom to boot, but I'm having same issues with audio and video. Also, I can't turn on wifi.
Click to expand...
Click to collapse
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
BCSC said:
You will need to flash a kernel to get the wi-fi to work. Try this one. works for me and many others who have suggested it. http://www.androidfilehost.com/?fid=23196940996968860
Post # 3 here, http://forum.xda-developers.com/showthread.php?t=2498233, is where I got that kernel. Be sure to thank him when it works.
Click to expand...
Click to collapse
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
danman0 said:
I got the wifi to work, but I still can't record video or hear audio. However, youtube does play up to 4 seconds of video, then the video freezes, but the bar resets to 0 and keeps moving forward and I don't see any more video other than the frozen frame. Could this be because of my custom binary count being 13?
Click to expand...
Click to collapse
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx? Have you Factory wiped since discovering these issues?
BCSC said:
The custom binary count just means you have been busy flashing non-official stuff. It is not related to your audio problem. Are you still on S3rx?
Click to expand...
Click to collapse
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
danman0 said:
Yes, I'm still on S3rx. When I first reboot my phone, I can't see the clock widget on the lock screen, but when i unlock and relock, it appears. Also, my imei and phone info is wiped, but since that doesn't explain audio and video not working, it doesn't matter at the moment. What else could be causing audio and video to not work?
Click to expand...
Click to collapse
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached. See here:http://forum.xda-developers.com/showthread.php?t=2540998
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
BCSC said:
Sorry but I'm gonna ask a few more questions and see what I can find,
1. When you last tried to flash the stock 4.3 update, did you use the OTA zip that includes Knox and the bootloader?
2. Have you attempted to flash the stock rooted Att S3 image without the bootloader attached
3. Without imei you aren't receiving service are you?
The reason I'm asking so much about the stock ROMs is because somehow the audio/video issue you are having may be fixed by going back to stock and wiping everything and reinstalling your kernel again. I have not experienced an issue like this myself, these are just the steps I would take.
Click to expand...
Click to collapse
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
danman0 said:
I don't remember what a bootloader is, but I downloaded the stock firmware from here http://www.smartphonejam.com/2013/11/upgrade-att-galaxy-s3-official-android43-i747ucuemjb-ota-update.html since software update option wasn't showing any updates for me. Later on I installed loserskater's 4.3 noknox and selinux permissive version but i had the same problems as i do with S3rx right now. Then I decided to go to custom roms, thats when sound and video don't work at all.
I don't know how to unattach the bootloader image (if there is one).
Yes, I don't receive and service http://www.youtube.com/watch?v=231HdNzlauQ
Click to expand...
Click to collapse
I'd recommend heading here and installing the upndwn4par stock ROM again. You did flash the one with the bootloader via that link you sent me. This link does not contain that bootloader. It has already been removed. Flash this and then wipe everything (cache,dalvik and full wipe/factory reset). http://forum.xda-developers.com/showthread.php?t=2540998. This could fix your video/audio issue.
s for your IMEI problem you may find your answer here: http://forum.xda-developers.com/showthread.php?t=2374063
I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?
Himay85 said:
I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?
Click to expand...
Click to collapse
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.
roper15 said:
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.
Click to expand...
Click to collapse
Thank you I'll give it try. I'll have to find the stock ROM for my phone. I didn't back it up like a newb
I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.
ericdabbs said:
I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.
Click to expand...
Click to collapse
I don't think it's primarily hardware related when most of us didn't have issues before 4.4.2.
I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.
Hakukoru said:
I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.
Click to expand...
Click to collapse
Can you share these files? Would they work on a stock based ROM?
ledvedder said:
Can you share these files? Would they work on a stock based ROM?
Click to expand...
Click to collapse
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.
Hakukoru said:
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.
Click to expand...
Click to collapse
Thanks, but it didn't work. Gave me a bootloop
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Awesome, I'll give it a try this weekend.
polymath257 said:
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Click to expand...
Click to collapse
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
chuck864 said:
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
Click to expand...
Click to collapse
I flashed a previous build with TWRP, CWM, as well as 4EXT. I have done this one (so far) only under TWRP, but any of the most recent recoveries should work.
chuck864 said:
Can either recovery be used or do you recommend one over the other? Haven't flashed my d-inc 2 in a while.
P.S.
Thanks for posting this. I know you're not a dev but there are some people who like to flash new roms for the fun of it.
Click to expand...
Click to collapse
That's how I got into building.
polymath257 said:
I flashed a previous build with TWRP, CWM, as well as 4EXT. I have done this one (so far) only under TWRP, but any of the most recent recoveries should work.
Click to expand...
Click to collapse
I used CWM from your post and it worked fine.
Man... All I can say is wow... :highfive:
I can't believe 4.4.4 is running on my incredible. Only been running it for 30 minutes but so far looks great.
What's Working,
camera, ffc, panorama, wifi, gps, bluetooth, torch, screenshots, rotating hardware buttons, google now, chrome, maps.
My phone isn't activated so I can't test mobile data, etc, but it does show verizon service under my signal strength.
What's Not Working.
Recording video, rear or ffc,
Playing videos.
I can't play videos I have recorder previously. Acts like it is going to play them then just says "Can't play this video."
Videos in you tube app act like they are gonna play but go into an endless buffering loop
No video inside of chrome either. I think it is broke on everything.
Gets a little slow at times but overall very nice work. :good:
Here is a link to the KK gapps if anyone else wants to give it a try.
http://goo.im/gapps/gapps-kk-20140606-signed.zip
Update
Just wanted to post an update for anyone who is curious. I've tried tweaking a few things to get some more speed out of it.
I switched to ART and apps got really slow so i switched back. I'm thinking it has to do with converting the apps because the dex2oat process was running pretty high.
One thing that did help was changing the SElinux mode from enforced to permissive with this app.
link
I also installed facebook, which ran well to my surprise, and overclocked to 1420.
Other than the video and lag issue it seems to be pretty solid.
Maybe this will get someone's attention and breath some new life into an old but solid device. :fingers-crossed:
Doublepost from prev forum and cannot get gsm to work. Worked on 5/16 build but not this one. Cannot get preferred network type to stick. Does not seem to recognize sim card.
#Update#
I know this build doesn't have Dev support but just i just wanted to share what I've found.
Tried to listen to some music via head phones and it hard rebooted my phone. Plays fine through the phone speaker and through Bluetooth but it dies as soon as I plug in my head phones. Hard reboot every time.
Sent from my XT1080 using XDA Free mobile app
chuck864 said:
#Update#
I know this build doesn't have Dev support but just i just wanted to share what I've found.
Tried to listen to some music via head phones and it hard rebooted my phone. Plays fine through the phone speaker and through Bluetooth but it dies as soon as I plug in my head phones. Hard reboot every time.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Do you have a logcat of this? I can see if I can track down what is going on.
polymath257 said:
Do you have a logcat of this? I can see if I can track down what is going on.
Click to expand...
Click to collapse
I will get one this weekend and post it for you.
polymath257 said:
Do you have a logcat of this? I can see if I can track down what is going on.
Click to expand...
Click to collapse
Here are the log files. The logcat looked pretty empty so I got a last_kmsg as well. It wouldn't let me upload them for some reason so I zipped them together. Recommend opening them in wordpad for nice formatting.
Procedure:
booted the phone
launched a terminal
started the logcat
plugged in the headphones
I wiped all partitions, and installed the zip and resulted in a status 7 error. Using EXT4 recovery. Gonna try downloading again. Can I get an MD5?
MD5 matched. Still same error. Something about permissions denied or something and then status 7 installation aborted.
polymath257 said:
Here is a link to my 6/26/2014 build from evervolv sources. THIS IS UNOFFICIAL. If preludedrew wishes me to delete it, I will, immediately. This is a 4.4.4 build.
A recent recovery is required; see
http://forum.xda-developers.com/showpost.php?p=53106281&postcount=1114
I make no guarantees about this build. I am not a developer (yet?); I am only a builder. I have tested it on my own device and it seems to work well. But I do not have an activated phone, so take that with a grain of salt.
http://d-h.st/mZD
Click to expand...
Click to collapse
Osiris19 said:
I wiped all partitions, and installed the zip and resulted in a status 7 error. Using EXT4 recovery. Gonna try downloading again. Can I get an MD5?
MD5 matched. Still same error. Something about permissions denied or something and then status 7 installation aborted.
Click to expand...
Click to collapse
You have to use one of the newer recoveries from the OP. I haven't tried TWRP but can confirm CWM works fine.
I'll try TWRP. Any idea if EXT4 will be supported?
Osiris19 said:
I'll try TWRP. Any idea if EXT4 will be supported?
Click to expand...
Click to collapse
I couldn't say maybe someone will make a build.
Osiris19 said:
I'll try TWRP. Any idea if EXT4 will be supported?
Click to expand...
Click to collapse
The latest version of 4EXT should work. Use v1.0.0.6 RC3, the testing build.
chuck864 said:
Here are the log files. The logcat looked pretty empty so I got a last_kmsg as well. It wouldn't let me upload them for some reason so I zipped them together. Recommend opening them in wordpad for nice formatting.
Procedure:
booted the phone
launched a terminal
started the logcat
plugged in the headphones
Click to expand...
Click to collapse
I have played with this a bit on my phone also. It seems that the streams get messed up when the headphone is plugged in. For me, I can plug and unplug the headphones as long as there isn't any music playing, but the instant I attempt to play music with them in, or plug in when music is playing, the phone reboots. I haven't had much time to dig in the source code yet, but when I do, I will let you know what I find.
polymath257 said:
I have played with this a bit on my phone also. It seems that the streams get messed up when the headphone is plugged in. For me, I can plug and unplug the headphones as long as there isn't any music playing, but the instant I attempt to play music with them in, or plug in when music is playing, the phone reboots. I haven't had much time to dig in the source code yet, but when I do, I will let you know what I find.
Click to expand...
Click to collapse
I thought the dmesg was much more useful for this kind of stuff.
Lgrootnoob said:
I thought the dmesg was much more useful for this kind of stuff.
Click to expand...
Click to collapse
You could be right. I'm not familiar with the different log types. Correct me if I am wrong but I believe that the dmesg is cleared on hard reboots and not soft and this is a hard reboot.
Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris
Works for me. Thanks!
Sent from my Nexus 9 using Tapatalk
Works on http://forum.xda-developers.com/showthread.php?t=3129778
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Have you flashed the stock vendor.img with fastboot?
wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Hey wfyjay,
sorry to hear about your nexus. Well, my fix only creates a property-file which stores version-information in /vendor and should have nothing to do with your touchscreen problem. However, as fleischbanane said, have you tried flashing the vendor image which is included in Google's factory image?
fleischbanane said:
Have you flashed the stock vendor.img with fastboot?
Click to expand...
Click to collapse
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk
wfujay said:
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Factory images are located here: https://developers.google.com/android/nexus/images
gladiac said:
Factory images are located here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk
wfujay said:
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Well, that's odd. If you flashed back to stock then the vendor-partition (as well as all the other important partitions) must be in their original state. I'm afraid your touchscreen problem is unrelated to my fix. You could post a logcat (adb logcat) on the forum and someone might be able to figure something out or relock the bootloader and send your nexus in for warranty. I'm not sure if I can help you any further.
What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip
mgiusto said:
What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip
Click to expand...
Click to collapse
Hi, this file is supposed to be flashed via the recovery (TWRP, CWM, ...) just as you would do with a normal rom.
Worked for me, running Broken 2.4
Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk
Cuzz1369 said:
Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Hey there,
well, the error occures as soon as the values in /vendor/build.prop do not match those in /system/build.prop. Most roms only flash /system - leaving /vendor completely untouched. And since most roms change /system/build.prop in every release which in the end causes the error message to appear. At the end of the day, there is no mechanism that ensures that the values of those two files actually match. In an ideal world, roms should provide /vendor as well. In a less ideal world, roms should patch /vendor/build.prop themselves. In _this_ world, roms just don't care so I created this update-zip.
Hope that clears things up,
cheers gladiac
gladiac said:
Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris
Click to expand...
Click to collapse
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.
Anubis22666 said:
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.
Click to expand...
Click to collapse
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers
gladiac said:
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers
Click to expand...
Click to collapse
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually plz? Or direct me to a guide
Anubis22666 said:
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor file/folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually perhaps? Or direct me to a guide
Click to expand...
Click to collapse
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.
gladiac said:
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.
Click to expand...
Click to collapse
Thank U so much for Ur kind help.
I checked, this /vendor folder doesn't have the 'build.prop' file in it,it has just three folders. Although /system folder does have the 'build.prop' file. See attachments, please
Hello, I have flashed several roms ranging from marshmallow to nogout and can-not get Viper4Android to work. Let me explain the problem. V4A only works with the music player that comes with the initial install but does not work with any player that I have paid for such as the likes of Jet Audio and Neutron Player. This is highly frustrating as the cheesy player that comes with the initial install is not strong enough to kick my duel air chamber headphones. I have tried all the normal fixes that normally work such as switching SElinux mode to permissive and some other ones that Viper users quite frequently use. If anyone is willing to help me figure this out or has already solved this problem or knows of some fixes to this that would be highly appreciated if I could get your feedback to this problem. Any and all replies are welcome.
Ok, guys heres an update: I got V4A to work on customized stock ViperOne based on stock marshamallow by changing the HTC_AUDIO_CONF file to the same name but with .bak at the end of it but it only works for headphones so when I connect the usb DAC it shows yes, yes, yes witch means working for usb but there is no sound output. Now that I got it working Im going to figure out how to get it to output sound through the usb dac otg When I figure that out im gonna start working on how to get this to work on most of the custom roms for our device. But one thing at a time. Also some help from the people who use V4A on HTC would be nice.
Try this:
First flash this - https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-cleaner-v1-2-android-7-x-t3482211
Then flash this - http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip
Phalangioides said:
Try this:
First flash this - https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-cleaner-v1-2-android-7-x-t3482211
Then flash this - http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip
Click to expand...
Click to collapse
I'm charging my device as soon as it charges I'll give a try and let you know if it worked
Phalangioides said:
Try this:
First flash this - https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-cleaner-v1-2-android-7-x-t3482211
Then flash this - http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip
Click to expand...
Click to collapse
What rom did you do this on?
Phalangioides said:
Try this:
First flash this - https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-cleaner-v1-2-android-7-x-t3482211
Then flash this - http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip
Click to expand...
Click to collapse
OK it worked the first zip did it. The second zip did not work I had to use the Viper from magisk viper v15 version. Everything works now including output from USB. I figured it was that files needed yo be cleaned out where the audio files are. Thanks. :good: Now its all good sounds are pleasurable again . Thanks for the link.
OGdroidster said:
OK it worked the first zip did it. The second zip did not work I had to use the Viper from magisk viper v15 version. Everything works now including output from USB. I figured it was that files needed yo be cleaned out where the audio files are. Thanks. :good: Now its all good sounds are pleasurable again . Thanks for the link.
Click to expand...
Click to collapse
You should really use that edit button instead of making few posts in a row Also about thanks - look at my signature.
I've used it on all the roms I've used - MM sense and customs, N customs and those two zips always worked.
However, I'm currently on stock, unrooted, unmodified MM sense and it doesn't work - the app flashes, but the status is abnormal, it can't modify the system partition - simply put, stock rom needs to be rooted in order for v4a or other things to work, just pointing that out.
Phalangioides said:
You should really use that edit button instead of making few posts in a row Also about thanks - look at my signature.
I've used it on all the roms I've used - MM sense and customs, N customs and those two zips always worked.
However, I'm currently on stock, unrooted, unmodified MM sense and it doesn't work - the app flashes, but the status is abnormal, it can't modify the system partition - simply put, stock rom needs to be rooted in order for v4a or other things to work, just pointing that out.
Click to expand...
Click to collapse
I always use root even if I'm on stock. That is a must. When I'm on stock no root means can't do certain things. Kinda like if you were to have no sudo on Ubuntu. I wouldn't be able to install anything so root is a must. Always has been. I wrote those posts before I tried it out. My HTC was charging but yea whole lot of posts. OK I just edited this because I ported the two files audio config and policy config from my old droid 4 running ressurection and it worked. I did this because the radio wasn't working with that flashable zip from the link you gave me.I added a small touch of my own to one of the files and wola there you have it all audio including the radio works. I was wondering if you would like to test the two files on your device to confirm that it works and it isn't just working on mine. That way I could put files in XDA and share them for other users to use.