Related
Ok, long story short, after the Sense 5 update, the Bluetooth was completely messed up for me. Not only did the "Visible to All Devices" option never stick with each consecutive toggle, it never seemed to work or pair correctly with any other device and required me to constantly un-pair said device and re-pair it. This plagued me for a while till I was playing around with the Bluetooth configs in the system while working on my ROM. What I did was essentially edit the configs to make the settings stick.
IMPORTANT
When I tested it on my ROM, I lost the ability to make Bluetooth "Only Visible to Paired Devices" and could only switch between "Visible to nearly all devices" and "Never visible" or something similar. However, when I created a flashable zip and tried it on ARHD, everything worked fine with no missing options. Remember, anything could go wrong. I ended up with missing options, you may end up with crippled Bluetooth altogether. Always make a backup or have a ROM zip lying around to reflash in case of emergency
What does this MOD do ?
1. Makes sure toggles such as "Visible to nearly all devices" sticks after toggling Bluetooth On/Off
2. Fixes any Bluetooth issues when switching Bluetooth On/Off such as device connecting errors like I faced
3. Less issues when using A2DP (doesn't require constant un-pairing and re-pairing to make it work like it did most of the time)
Intructions
1. Download the ZIP
2. Make a backup (unless you have the balls to go through with no backup plan )
3. Flash the ZIP
Optional - 4. Wipe dalvik cache & cache
5. Reboot and enjoy
Download MOD
Download Rollback zip to undo chnages
Uses in other ROMs
ROM devs and chefs alike are allowed to use this MOD in their work. You don't need to drop me a PM or anything, just give credits and link this thread in your Changelogs to avoid issues with my MOD cluttering up your ROM thread.
Notes
1. I made this MOD to solve a problem I faced with Sense 5. It has solved my problem, it may solve yours too if you have the same. If it doesn't, refrain from posting negative posts here.
2. This is the first time I've attempted tampering with the system configs to such a degree to fix a problem such as this. If you feel there are ways I can improve on this MOD, please feel free to advise me or give suggestions.
3, If you face any issue, be patient with me. Like I said, this is my first time attempting something like this and I only succeeded by sheer luck.
I will get around to making a rollback zip for this MOD to save you guys the time and trouble of making backups till then, hope this helps
I would like to try this as A2DP usually fails to connect for me. I have to open up bluetooth settings, disable media streaming and then re-tick it to get it working which is inconvenient.
Could you upload it to a site that I don't have to sign up to to download? Thanks
Done
RohinZaraki said:
Done
Click to expand...
Click to collapse
Thanks that's great. I tried subscribing to box and although successful it wouldn't let me download the file??!!
Will install and give it a go in a bit. Thanks again.
optiknerv said:
Thanks that's great. I tried subscribing to box and although successful it wouldn't let me download the file??!!
Will install and give it a go in a bit. Thanks again.
Click to expand...
Click to collapse
Anytime.
Added a rollback zip. Flash it if you want your old bluetooth back
Thanks mate but I flashed the zip and sadly it didn't fix my connection error. Do I have to delete and re-add my bluetooth adaptor? I didn't get chance to try this earlier.
optiknerv said:
Thanks mate but I flashed the zip and sadly it didn't fix my connection error. Do I have to delete and re-add my bluetooth adaptor? I didn't get chance to try this earlier.
Click to expand...
Click to collapse
I think you should
Sent from my HTC One X using Tapatalk
RohinZaraki said:
I think you should
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Sadly it hasn't worked. Same problems as before. Slide the phone onto the car cradle, bluetooth turns on and phone audio connects but not media. Slide off and back on again and all connects ok... most times.
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
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.
Hi,
please give keywords and guiding advice, I will try to find the corresponding threads by myself
I have a brand new GT-I9195 Black Edition. I want to do as less damage as possible, so what do I have to do to get CM11 with Xposed framework running?
I just switched it on, started KIES 2 and connected. No SIM-card is inserted, no microSD-card, no WiFi connection. The phone is offline.
KIES says that the firmware is the most recent and gives this:
Code:
I9195XXUBML4 / I9195YBTBNA2 / I9195XXUBML4 / I9195XXUBML4 (DBT)
I assume this is not the newest firmware, and according to this thread (German) "I9195XXUCNE6 I9195OXACNE6 DBT 4.4.2 23.05.2014 is newer.
I have or see no possibility to upgrade via KIES.
Would the new firmware give me another, better modem/baseband firmware? If so, I would flash with Odin 3.09.
I think I need root permissions for Xposed and XPrivacy, at least this is what I did with my Sony Xperia mango. Is that correct?
What steps do I have to take to get root access without interacting with KNOX? Does it make sense to avoid the KNOX counter increase?
What part of the warranty will be void if KNOX is triggered?
What recovery should I use? There is already a recovery available, accessible by pressing Volume Up and home button at the same time when switching on.
I wanted to start with CM11 and no special kernel, just what CM11 brings, to keep it easy. So flashing serranoltexx M9 or later should be sufficient?
How do I get Xposed and XPrivacy to work? I want it working before putting in the SIM card and connecting to the internet. Do I have to worry about dalvik and ART?
GApps 20140105 from http://wiki.cyanogenmod.org/w/Google_Apps are the right ones?
Did I forget something?
Thank you
Raubsau
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
MarkAndroid.UK said:
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
Click to expand...
Click to collapse
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
Why is it so important to you to install XPrivacy before first boot?
Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
No one wants to brick their device, do they? I've never bricked mine and I've made lots of mistakes. It is highly unlikely unless you try to flash something not meant for your device or something similarly bad.
I certainly haven't found CWM being recommended over TWRP - devs here tend not to recommend, just point things out; ALL choices are yours. There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it. ROM's are built from components and not everything has to be there - one of the brilliant things about Android is how it interfaces with all the different aspects of a mobile device - it appears to be one program running everything but it is extremely modular.
With external apk's I just copy them to external SD and install them on the phone.
Raubsau said:
Do I have to worry about dalvik and ART?
Click to expand...
Click to collapse
Forgot this bit!
No. You can elect to use ART in the system setting of some ROM's (certainly SLIM) and I know some people who do. However, ART is still under development and by no means are all apps ready for it yet. Xposed Framework itself will not work under ART and won't be for quite a while yet.
MarkAndroid.UK said:
There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it.
With external apk's I just copy them to external SD and install them on the phone.
Click to expand...
Click to collapse
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Raubsau said:
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Click to expand...
Click to collapse
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
MarkAndroid.UK said:
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
Click to expand...
Click to collapse
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Raubsau said:
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Click to expand...
Click to collapse
'Small' would be fine
MarkAndroid.UK said:
'Small' would be fine
Click to expand...
Click to collapse
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Raubsau said:
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Click to expand...
Click to collapse
That's great, have fun and you're welcome
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
I intend to buy the 'black edition' too but I am worried whether the internals changed as it's a later model and hence CM wouldn't run on it...
black edition:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
"ordinary" black version:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-1.jpg
Thanks a lot
soikku said:
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
Thanks a lot
Click to expand...
Click to collapse
If the model number of the device you wish to buy is I9190 or I9195 then you can follow standard procedure.
Black edition is just cosmetic variation. Nothing special about that. Model number is always I9190/2/5.
So use normal procedure from threads in this forum. Good luck.
My phone looks like this:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
Info in the Settings menu says "GT-I9195".
As I was using XPrivacy fromt the start, some of these problems may have occured because of wrong restrictions:
- orientation of indicator in Google Maps shows wrong direction
- no compass app is working
I use my phone for calling, reading and writing mails, and remote control my media box. In the few cases I needed it for navigation, it worked fine (regardless of the wrong indicator).
Hope that helps.
Thank you for the replies, Raubsau and sasank360
Thank you for pointing out that the 'black edition' indeed is identical to the previous one internally.
I ordered the phone now and am looking forward to happy flashing (CM11 for the time being as freecyngn doesn't work for CM12 (yet)).
Friends, I am huge fan of Dolby Atmos mod and just feel that the device is somewhat incomplete without it.
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
From above link, I have tried installing almost all the versions, in both Official stock Oreo Rom as well as RR ROM For Honor 7x. Have also tried flashing through TWRP and Magisk module.
Could someone please help with porting Dolby Atmos for Honor 7x Oreo?
Adarshar42 said:
Don't try that, you will end up in bootloop.
Click to expand...
Click to collapse
Actually I have already tried all the versions there. It's not exactly bootloop, as technically bootloop means the phone keeps restarting as soon as it boots the OS. In this case, mostly the phone freezes on boot animation. However with one of the mods installed through Magisk in RR ROM, the phone booted and Dolby also got installed but kept crashing while opening. I think it should be fairly easy for experienced developers to make it work for our device..
Supposedly no sound mods will work yet on emui 8 due to it only using 64 bit drivers. Obviously this means that someone has to write 64 bit drivers for the mods before they will work
ryang872 said:
Supposedly no sound mods will work yet on emui 8 due to it only using 64 bit drivers. Obviously this means that someone has to write 64 bit drivers for the mods before they will work
Click to expand...
Click to collapse
Ahh ok.. That sounds reasonable..
hify_ameet said:
Actually I have already tried all the versions there. It's not exactly bootloop, as technically bootloop means the phone keeps restarting as soon as it boots the OS. In this case, mostly the phone freezes on boot animation. However with one of the mods installed through Magisk in RR ROM, the phone booted and Dolby also got installed but kept crashing while opening. I think it should be fairly easy for experienced developers to make it work for our device..
Click to expand...
Click to collapse
I gather you're on an honor 7, emui 8, i have 2 cents on this:
1. I believe, disregard if I'm wrong, your phone shipped with emui5, now, if this is so important to you, there is a working setup for emui5, you just have to roll back, and 2, i installed successfully a setup on openkirin's treble rr... Wonder why you couldn't.
One more thing, which setup was the one you could boot with, albeit the continuous crashes upon app fire up?
culiacanazo said:
2, i installed successfully a setup on openkirin's treble rr... Wonder why you couldn't.
Click to expand...
Click to collapse
Could you please tell me which mod you used and how you installed/flashed it? I am having trouble finding working audio mods on RR also.
Barthvader said:
Could you please tell me which mod you used and how you installed/flashed it? I am having trouble finding working audio mods on RR also.
Click to expand...
Click to collapse
Do note i was on kirins, not sure if it matters/there's another. Now, as you can see in the pic it's been a little bit (for my memory) so let me just backup and transfer (no external sd support, awesome idea!) because that does mean deleting, and after restoring, I'll check it out
culiacanazo said:
Do note i was on kirins, not sure if it matters/there's another. Now, as you can see in the pic it's been a little bit (for my memory) so let me just backup and transfer (no external sd support, awesome idea!) because that does mean deleting, and after restoring, I'll check it out
Click to expand...
Click to collapse
Did you get chance to test that? Did it work mate?
hify_ameet said:
Did you get chance to test that? Did it work mate?
Click to expand...
Click to collapse
You know, i lost my charger for my laptop so i really don't wanna mess with it but honestly i am starting to believe i was mistaking xposed for dolby, since both were impossible once and now Xposed is running... My apologies
If it works, with openkirin and magisk
There is a working Dolby magisk module that works with open Kirin find