[GUIDE] [ROOT] Force Mute / Shutter Sound OFF in Google Camera 4.4+ [new] - Android General

Force Mute / Shutter Sound OFF in Google Camera
Google recently added option in Google camera to Mute Shutter sounds. "• Mute Camera Shutter Sounds - Turn shutter sounds off from Settings (this option is only available in some locations)."
But this option didn't show up for most users/countries.
Here is a way to force enable the Mute option.Need not delete audio files.​
REQUIREMENTS:
latest Google Camera
root
any root explorer like fx,solid explorer,es,..
STEPS:
With any root explorer navigate to data/data/com.google.android.GoogleCamera/shared_prefs
open file com.google.android.GoogleCamera_prefs.XML
find line pref_camera_sounds_key
Change 1 to 0
Save :good:
No more damn sound!
​

I tried this on my Pixel 3 XL, it works temporarily, but every time settings button is pressed within the camera app, this number resets back to 1.
Next I tried magisk module "Disable screenshot and camera sounds" by ant9000 (updated on Nov 25 2018), but that didn't work at all (looking at the module, it replaces sound files with silenced sound files, but that method has not worked for a while, since Nougat release. Google made sounds part of the APK, the seperate files don't do anything ~ https://forum.xda-developers.com/showpost.php?p=72650754&postcount=3 )
Next I tried magisk module "MuteCameraSounds" by knightbat (updated on Oct 25, 2018), but that didn't work either (looking at the module, it also just replaces sound files)
Next I checked magisk module "Camera video shutter sound off" by dr.bathman (updated on Oct 20, 2017), but that one is too out of date to be usable and looking at it, also just tries to replace sound files.
Next I tried the method where removing the sim card, then restarting the phone, should make the sound toggle appear in the camera app preferences (suggest here 20 days ago https://redd.it/a6n1w4 ). But that didn't work either.
Next I tried to mess with permission and owner settings for the com.google.android.GoogleCamera_prefs.XML to see what would happen if I forbid the app from writing to file. But even after changing the file to read only and changing the owner of the file from app_10113 (camera) to root, and removing "change system settings" permission from the camera app, camera STILL somehow manages the change file owner back to itself and file permissions back to writable, and change the pref_camera_sounds_key back to 1.
Only solutions at the moment, other than not ever accessing camera preferences, appear to be writing a custom app that either
1) Upon activation of the app, changes the pref_camera_sounds_key to 0 and then completely shuts down the camera (to force it to read from the prefs file upon activation)
2) App that actively monitors if the prefs file changed, and if it did, quickly edit in that 0.
If this were windows, I'd whip up an ahk script that does this in no time, but I have zero experience creating android apps unfortunately, and no time at the moment to learn it.
I also tried to edit the official google camera .apk by replacing camera shutter sound ogg files with silent files, but this breaks the cryptographic signature of the apk, making it impossible to install the apk. Signing such apk with a new signature is likely possible, but beyond my skill level.

Related

[Q] GravityMod2 questions

C3C076 or one of you who are more familiar with this than I might be able to answer this...only I can't post in the proper thread due to thread post count....
Couple of things about this mod for the ThL W8. I have it running just fine but have some issues with it.
1. How do I get rid of the circle battery mod and go back to the stock battery icon?
2. How do I change the font on the lockscreen 'clock' app? The bolded hour looks terrible.
3. How do I stop the lockscreen from showing the left side box temporarily? It is showing that you can slide left to install widgets on the lockscreen but I don't like how it unbalances the look of the lockscreen.
4. Version 1.4 changelog mentioned that empty sim card slot notifications would be hidden....I still see a message for sim slot 2 being empty until I click the clear notification button.
5. Now that I think about it, could I just replace the digital clock app in 1.4 gravitymod2 with the stock clock app from android 4.1.2? If so, how?
Link to thread in question:
http://forum.xda-developers.com/showthread.php?t=2249808
1) You have 3 options a) learn to live with it b) decompile SystemUI and edit resource XMLs to hide circle mod and unhide stock battery c) flash different ROM
2) You can replace clock with another clock lock screen widget. There are many of them on play store, e.g. DashClock
3) There's no option for it. It's default Android 4.2 feature. There's an app called "lockscreen policy" which can disable side lock screen pages so it is maybe capable of hiding carousels, but I'm not sure.
4) it's not about disabling notification but hiding second signal icon in status bar
5) see 2)
C3C076 said:
1) You have 3 options a) learn to live with it b) decompile SystemUI and edit resource XMLs to hide circle mod and unhide stock battery c) flash different ROM
2) You can replace clock with another clock lock screen widget. There are many of them on play store, e.g. DashClock
3) There's no option for it. It's default Android 4.2 feature. There's an app called "lockscreen policy" which can disable side lock screen pages so it is maybe capable of hiding carousels, but I'm not sure.
4) it's not about disabling notification but hiding second signal icon in status bar
5) see 2)
Click to expand...
Click to collapse
Thank you for your reply C3C076.
Lockscreen Policy killed 3 birds with one stone! It disables lockscreen widgets, which also gets rid of the 'carousel' or box borders that show then fade for a second on the left side of the screen, and also disables the bold font on the clock hours! Nifty app and does just what I want there. Thanks for that!
6. There is a major bug that I and other uses are running into in the current version of GravityMod2 (1.4). My phone recent list and also text message contacts are getting split up. I send a message or make a call and it goes through fine. Then a return message or call is received and it shows up in my call log or messages as a different contact/person. It shows up received with the country code (+1) in my case and if I go to click on the profile/contact icon next to that number there is a message about an invalid number couldn't save contact. When I place calls by clicking on these received calls, I get a invalid number error message, click ok to dismiss it and then it will go through fine (using gv or not using gv in both cases).
I think that has something to do with the country code being added...I don't really know except it is kinda frustrating. Is there anything you can do to fix in an update to GravityMod2?
Ok Back to the topics above.
4. The missing sim icon is indeed gone (i didn't even really realize it because it never bothered me). The notification, other the other hand, really bugs me. I mean, that TRIANGLE CAUTION EXCLAMATION POINT! just BEGS for my attention and the notification comes up every boot or every airplane mode disable (cell radio on enable). I haven't tried this yet but I thought maybe freezing the specific sim toolkit app using titanium backup might cause this notification to not show up....unless the notification is from the OS itself in which case, any way you can disable that?
1. Thanks for the pointers. That will get me started towards changing the battery icon to suit my preferences.
7. Possible updates for the next version of GM2 to consider:
In version 1.4 of GM2, the file /System/etc/permission/com.android.sip.xml has the feature android.software.sip commented out (as per this topic by gmincca). I checked the other file: android.software.sip.voip.xml and the permission was not commented out. Maybe you missed that first one? Or it doesn't matter? I understand those permissions relate to the built in internet calling capability of this phone. I probably won't use it but I uncommented those two permissions in those files anyway using FX Explorer rooted to save the files after remounting as rw.
Volume levels for the earbuds while playing media (headset, media) were killing me ears! I used engineering mode to adjust the volume levels here under Headset mode, media, to be max of 112 and levels 0-6 to be 40, 64, 80, 96, 102, 108, 255. The last setting is for when plugged into a car speaker or external speaker you can still get max volume and the previous settings allow for actual listening with earbuds at a comfortable level. I do not know if these settings are on a per speaker basis and your mileage may vary with the usefulness of these. I thought it helped out a good bit. I also made some minor adjustments with the sound levels for the speakerphone (loudspeakermode, sph, level 6 to 160) to be able to hear the speakerphone better while on a phone call.
8. You got the auto brightness setting for the dark just right in your latest change. 0% brightness matched autobrightness just perfect! Only minor thing is in full daylight auto brightness was a little bit under 100% so didn't work as I thought. If the auto brightness % for full lux can be adjusted I'd like to know where, or if you could update for the next version of GM2 that would be awesome!
Thanks for all your hard work on this custom ROM for the ThL W8! Kudos/Karma/+1 to you!
6) This is a standard feature/bug of all mtk6589 4.2 roms. I can't do anything about it since we have no sources and messing with anything at java disassembled code level (smali) is a pain in the ass. Easy solution is to keep all your contacts with country code prefix and it'll be OK in case your operator sends the same caller ID for calls and messages. You should keep your contacts with prefix anyway to be able to call while roaming.
4) I might try removing that notification in the future
7) you're right about SIP. I missed that file. If you uncomment it SIP options will appear in Phone settings.
8) I didn't adjust upper levels, just lower ones. It would be helpful to measure light sensor values under different light conditions with some app and adjust levels. So if you like to experiment, any input will be welcome. I can send you current values.
C3C076 said:
6) This is a standard feature/bug of all mtk6589 4.2 roms. I can't do anything about it since we have no sources and messing with anything at java disassembled code level (smali) is a pain in the ass. Easy solution is to keep all your contacts with country code prefix and it'll be OK in case your operator sends the same caller ID for calls and messages. You should keep your contacts with prefix anyway to be able to call while roaming.
4) I might try removing that notification in the future
7) you're right about SIP. I missed that file. If you uncomment it SIP options will appear in Phone settings.
8) I didn't adjust upper levels, just lower ones. It would be helpful to measure light sensor values under different light conditions with some app and adjust levels. So if you like to experiment, any input will be welcome. I can send you current values.
Click to expand...
Click to collapse
6. I can say it is not solely 4.2 roms but also 4.1.2 as well. On the stock rom and on the update line brush package FH4, 4-28-2013 (4.1.2 and 4.2.1 respectively) both of those roms also experienced this issue with the contacts being added country codes on incoming calls/messages.
After I went through my google contacts and used UltraEdit32 (similar to notepad++) with regular expressions to remove parenthesis, spaces, and hyphens (and a bad contact that was gumming up the works), I was able to make calls again without it erroring out with that message. It would still give the error message but then the call would go through. I didn't add the country code at that time but I guess it wouldn't be to difficult to export/download my google contacts again, turn off syncing, fix/add my contacts, then delete the contact stores on my phones and resync with added country codes.
With that said, if I use the dialer to directly dial the number which isn't in my contacts I still get the "Call not sent, no valid number entered" error message. I have found this problem is related to Google Voice and the Dialer (Phone) app. If I turn off using Google Voice to make all calls or to ask every time and set it to do not make any calls, the calls will go through no problem, I need Google Voice though so I guess I'm left wondering if I can use a different dialer...perhaps the stock 4.2.1? I have no idea how to get started changing that though.
My phone's dialer is from GM2 currently: version 4.2.1-eng.zhangshuangshuang.1366707806
Other's who have had my same problems with GV integration had similar issues with Samsung's replacement/custom dialer causing issues. Can I get a stock dialer/phone app somehow?
4. Please! And thank you! Of note: using Titanium Backup to freeze the simtoolkit application didn't do anything. I didn't see stk1 and stk2 like in 4.1.2 and in the 'line brush update official 4.2.1 rom. I only saw the one simtoolkit app and freezing had no effect on the notification). When I long press the notification, and press 'app info' it brings up the phone app. This means the notification is coming from the phone app directly I guess.
8. I'd be interested in what the current levels are for the brightness. I can use GPS status to measure the current lux however it doesn't report the current screen light level brightness setting, just the incoming measured lux from the light sensor.
9. Developer mode is not enabled by default in GM2. I had to google to find my usb debugging setting. (Go to Settings -> About -> Press 7 times on the Build number). Maybe this is an easy toggle to enable this by default for the next build of GravityMod2? I mean we are flashing a custom rom after all Not a big deal really if not.
6) Using alternative dialer from vanilla Android is impossible "thanks" to dual sim extension. The changes in framework and telephony are too vast.
4) it's coming from telephony subsystem in the framework.
8) I'll provide lux/brightness pairs later today (hopefully)
9) My opinion is that it's OK how it is now. Most of the users don't need it. Those who do, already know how enable it or can find out easily.
Here are the brightness levels and corresponding LCD backlight values.
Code:
<integer-array name="config_autoBrightnessLevels">
<item>16</item>
<item>32</item>
<item>50</item>
<item>100</item>
<item>140</item>
<item>180</item>
<item>240</item>
<item>300</item>
<item>600</item>
<item>1000</item>
<item>2000</item>
<item>3000</item>
<item>4000</item>
<item>8000</item>
<item>10000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>30</item>
<item>50</item>
<item>60</item>
<item>70</item>
<item>80</item>
<item>90</item>
<item>102</item>
<item>110</item>
<item>120</item>
<item>130</item>
<item>180</item>
<item>200</item>
<item>210</item>
<item>230</item>
<item>255</item>
</integer-array>
C3C076 said:
Here are the brightness levels and corresponding LCD backlight values.
Code:
<integer-array name="config_autoBrightnessLevels">
<item>16</item>
<item>32</item>
<item>50</item>
<item>100</item>
<item>140</item>
<item>180</item>
<item>240</item>
<item>300</item>
<item>600</item>
<item>1000</item>
<item>2000</item>
<item>3000</item>
<item>4000</item>
<item>8000</item>
<item>10000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>30</item>
<item>50</item>
<item>60</item>
<item>70</item>
<item>80</item>
<item>90</item>
<item>102</item>
<item>110</item>
<item>120</item>
<item>130</item>
<item>180</item>
<item>200</item>
<item>210</item>
<item>230</item>
<item>255</item>
</integer-array>
Click to expand...
Click to collapse
I did some testing in direct sunlight.
Anything over 8000 lux needs full brightness to be able to see the screen (even when the screen is set to 100% brightness in anything over 8000 lux it is still kinda of hard to see but that's why it needs to be full brightness on auto for 8000+).
In shade, but still bright out, the lux read about 6000 and the auto brightness setting was good.
I in framework-res.apk, changing those last two lux levels I think would help.
<item>6000</item>
<item>8000</item>
...
<item>230</item>
<item>255</item>
I tried decompiling and recompiling framework-res.apk after making the changes but couldn't get it to work. I wasn't sure how to install it. I used apktool and apkmultitool to decompile framework-res.apk and then change /res/values/arrays.xml and saved the files. Then I compiled and also tried signing them to produce the new apk. So far so good.
I then tried installing using apkmultitool install apk and it didn't work. It just said waiting on device. I tried rebooting my phone, tried recovery mode, tried regular just plugged in and turned on mode and nothing. USB debugging is enabled.
I also tried copying the changed apk directly to /system/framework (after first mounting as rw and changing the permissions of the new apk to match the permissions of the current framework-res.apk) using copy and paste on FX "file explorer." It would freeze when I gave it the paste command (yes it had root permissions).
I don't know how to install the changed apk or how to update this to get the new brightness settings. As the copy operation had froze the app, even pressing home did not work so I had to use my nandroid backup to revert phone to a useable state again.
When you compile modified apk in multi tool, say yes when it asks you if it's a system apk. Then say yes to create "keep" folder and delete resources.arsc from it, and then finish compiling process.
C3C076 said:
6) Using alternative dialer from vanilla Android is impossible "thanks" to dual sim extension. The changes in framework and telephony are too vast.
4) it's coming from telephony subsystem in the framework.
8) I'll provide lux/brightness pairs later today (hopefully)
9) My opinion is that it's OK how it is now. Most of the users don't need it. Those who do, already know how enable it or can find out easily.
Click to expand...
Click to collapse
6. Great. Perhaps an alternative dual-sim dialer is available...I didn't check...are the stock 4.2.1 (FH4 4-28-2013 official update) dialer and the Eastcom/GravityMod2 dialers the same? Could that kind of change be made and fix up these crazy errors?
4. Does that mean it is also impossible or just kinda difficult to fix?
9. Agreed and hey, thanks for taking the time to answer all my questions. Hopefully I can help in some way too
I managed to solve 4) already. I mentioned it in GM2 thread.
C3C076 said:
When you compile modified apk in multi tool, say yes when it asks you if it's a system apk. Then say yes to create "keep" folder and delete resources.arsc from it, and then finish compiling process.
Click to expand...
Click to collapse
Apkmultitook didn't prompt me about this, possibly because I chose the decompile system apk option at first. In fact, the compile process finished just fine with no errors. (Hopefully it was a good format for being a system apk but it didn't ask about that so...)
Once I have the compiled apk...I wasn't sure what to do with it. I was able to verify I had changed the xml file by decompiling the new apk but couldn't get it installed on my phone. I was probably doing something wrong. Is copying and pasting correct?
Have you tried wiping dalvik cache?
C3C076 said:
Have you tried wiping dalvik cache?
Click to expand...
Click to collapse
In what order would I do that?
Wipe the dalvik cache from recovery....then what? Try copying and pasting the new apk again? How does wiping the dalvik cache help here?
OK. I wiped the dalvik cache and then rebooted. Tried replacing my current framework-res.apk again with the new one (after setting permssions on the file first) and I still get a freeze at coping files. I might try again later with a different app with root access that can remount the /system as rw. Or maybe look into creating a update.zip and trying from recovery if that is possible.
I typically use "adb push" while in recovery (system partition must be mounted)
Good new everybody.
Looks like I fixed the Caller ID issues. At least for phone calls now.
This means that contacts stored without country code will be matched to caller ID sent by operator containing country code.
Messages seem to be handled differently (damn it) but I will try to look into it, too.
C3C076 said:
Good new everybody.
Looks like I fixed the Caller ID issues. At least for phone calls now.
This means that contacts stored without country code will be matched to caller ID sent by operator containing country code.
Messages seem to be handled differently (damn it) but I will try to look into it, too.
Click to expand...
Click to collapse
Waiting for this update for phone and Messages.
C3C076 said:
I typically use "adb push" while in recovery (system partition must be mounted)
Click to expand...
Click to collapse
Thanks. That was part of the problem.
The other part was since it was a system apk, I signed it thinking that's what it needed but I read a comment that stated that system apks shouldn't be signed. All I had to do was make my changes, compile it, then copy over meta-inf and AndroidManifest.xml from the original to the newly compiled apk. Then, adb push was correct as you stated for system apks.
On a side note I had to manually put in my java jdk path for android's sdk by editing the \adt-bundle-windows-x86_64-20130219\sdk\tools\lib\find-java.bat file with my jdk path....and I had to make sure I had the adb driver installed which was another hiccup. Once all those settled then I could use adb and apkmultitool etc worked fine.
I pushed the changed framework-res.apk to my phone verifying the changes were made and testing the light sensor values with 'GPS Status' which shows the lux...AND IT WORKED!! I can now leave the brightness on Auto and it works just fine
The change made was to framework-res.apk\res\values\arrays.xml
Changed lines 554 and 555 to be 6000 and 8000 respectively instead of 8000 and 10000.
Can you incorporate this change into the next version of GM2 C3C076?
So, new topic:
10. What files in SystemUI.apk or framework-res.apk are for the Cyanogenmod circle battery? I looked all through those two and couldn't find the graphics of the circle battery?
Thanks again!
Great I will include it in today's release.
CM circle battery is not image based. It is a self-drawing ImageView. It's in CircleBattery.smali in statusbar/policy.
It is referenced in layout xmls. The change would be easy. Just remove references from 2 xmls and remove visibility="gone" from standard battery references.
@C3C076, sir could you share how you were able to fix the Caller ID problems of your phone/rom. I currently own a ZTE V987 and have been trying to look for a fix for the same problem. I currently have android 4.1.2 Thanks!

[Bug list][i9505][4.3] CyanogenMod 10.2 official

I decided to create this thread so that people don't need to hunt through the large discussion threads.
Note that this is *not* a thread for discussing the ROM.
I will update these posts based on *confirmed* bugs. By that, I mean two or more people confirming the bug on pure cm 10.2 - not using other kernels.
Also the ROM must have had a clean install (wipe data, cache, system) and not flashed over a previous install.
It's also worth reading what CyanogenMod have to say about the 10.2 nightlies (http://www.cyanogenmod.org/blog/this-week-in-cm-aug-16-2013) as it gives you an idea of what to expect from the ROM at this stage.
ROM is available here: http://download.cyanogenmod.com/?device=jfltexx
The official ROM thread is here: http://forum.xda-developers.com/showthread.php?p=42387383
The discussion thread is here: http://forum.xda-developers.com/showthread.php?p=41851449
Only flash the ROM with the latest CWM (http://www.clockworkmod.com/rommanager), TWRP 2.6.0 (http://techerrata.com/browse/twrp2/jfltexx), or the latest PhilZ (http://d-h.st/users/philz_touch/?fld_id=16685#files)
DO NOT use earlier versions of PhilZ (prior to 5.13.9) or you will have boot (no animation, hang on updating apps) and installation (no signal, no baseband) problems.
DO NOT use TWRP 2.6.1 as it fails to flash the ROM.
First time cm 10.2 users please see post #4 for some useful tips.
Sent from my GT-I9505
Bug list
Bluetooth
(Does not affect all users and may be related to BT 4.0 devices)
No audio on BT; doesn't connect/disconnect properly.
Compass
The compass doesn't work "out of the box".
Solution:
- when first using an app requiring the compass (Google maps, GPS status, etc), the compass is "frozen" until it is calibrated (rotate the phone 2-3 times about each of its three axes).
- the compass will then move, but very erraticly, often going around in circles
- if you exit the app and then reopen it, the compass will work properly from then on.
DSP
DSP distorts sounds. This affects music play back.
Workaround: freeze DSP using TB
Mobile network modes
(Not everyone has this problem as it is language related)
- It is set to: GSM/WCDMA/LTE, but when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE).
- Selecting some options may cause an FC.
Network operator name
Name shows correctly on the notification shade, but only numbers are shown in Settings/Wireless&Networks/Mobile networks/Network operators
Apps
Camera
- HDR doesn't produce a proper HDR image. It only takes one low exposure image.
- Some people have been getting occasional green lines on photos taken using the front-facing camera.
- In Scene or HDR mode, touching on the screen does not refocus.
- (0908 ) Video recording at 1080p will cause the phone to reboot.
- (0908 ) Exposure is locked at the value of the first photo taken (if taken without flash). Subsequent photos use the same exposure as the first photo.
Workaround: change the flash mode to automatic then change it to none. Then it will work properly. But this needs to be done each time the camera app is started.
File Manager
(1113: reintroduced ) In root access mode the bookmark for the internal SD card points to /storage/emulated/0 which doesn't exist.
Workaround: bookmark /data/media/0 or /storage/sdcard0
Terminal
- su doesn't inherit PATH if it was previously modified by export.
- Arrow keys don't work properly in su mode.
Fixed
List of fixed bugs (version fixed)
Headphone mic doesn't work (20130818 )
Phone picks up sound from the phone microphones.
Workaround: keep the phone close to you.
Home key long press (20130818 )
Changing the option in Settings/Buttons/Home Button:Long press doesn't actually change the long press behaviour of the Home button.
Key backlight (20130827)
There is no longer an option to disable the backlight on the menu and back keys.
Workaround: flash this http://db.tt/evvZLhkx. Note that if you wiped /data then you must flash this file *after* the ROM has booted for the first time.
Lock screen (20130924)
If the icons of the shortcuts are changed, they must all be changed at the same time otherwise the ones that were previously changed revert to the original app icon.
Quick Settings panel
- (0924 or earlier) Orientation tile: it doesn't lock/unlock screen rotation immediately. It needs a screen change (such as bringing up the recent app list) to take effect. (20131001)
Random reboots
(0909) Some users get random reboots.
Root cause: bug in Chrome beta. See http://forum.xda-developers.com/showthread.php?p=45642265
SELinux status (20130818 )
Repeated taping on the SELinux status in Settings/About phone will freeze the phone and cause it to reboot after some time.
Sound recording (20131011)
Volume is very low in Sound Recorder and video recordings.
Partial workaround: use Smart Voice Recorder https://play.google.com/store/apps/details?id=com.andrwq.recorder and disable automatic gain control.
Workaround: use ktoonsez kernel and faux sound control app to increase the microphone gain.
Super user (20130815)
Does not work properly after a clean install.
Workaround: change Root access to Apps and ADB in Settings/Developer options
Apps
Camera
- No option to save to external SD card. This may be by design rather than a bug. (20130821)
Workaround: use Gallery2.apk from cm 10.1
- (1017) Note: cm are working in the camera. The camera will sometimes hang, often after using video. Force closing it results in a "Can't connect to camera" message. A reboot is required to reactivate the camera. (20131021)
File Manager (20130918 )
In root access mode the bookmark for the internal SD card points to /storage/emulated/0 which doesn't exist.
Workaround: bookmark /data/media/0
Trebuchet
- Icons in folders disappear after a while. (20130817)
Workaround: use a different launcher
- When icon labels are hidden, the label on an app will reappear if it is updated. (20131001)
Terminal
- (0918 ) In su mode, /sdcard points to /storage/emulated/legacy (/data/media/legacy), which is empty, instead of /storage/emulated/0 (/data/media/0). (20131011)
First time users
A few things you need to know:
Developer options
Only shows up in Settings when you tap 7 times on the Build number in Settings/About phone.
Reboot options on Power menu
Check Advanced reboot in Settings/Developer options.
ADB
For your PC to get ADB access, enable USB debugging in Settings/Developer options.
Watch your phone when you first run ADB and allow the PC access to your phone.
Internal SD card
With Android 4.2.2 (or was it earlier?) the internal SD card is now mounted at /data/media/0 in order to support multiple user profiles. Your files may still be in /data/media/legacy.
Sorry for repeating, but this information could be useful (cwm 6.0.3.6, cm10.2 nightly 14/08, previous firmware - cm10.1 nightly 13/08).
mreugene said:
Everything is ok after installing via last cwm and some magic
I had two minor bugs:
1. unable to update the software - fixed by readding the google account and cleaning dalvik cache.
2. crashes of keep, play music, google disc and youtube- fixed by reinstalling these programs.
Click to expand...
Click to collapse
Deleted
awesome
Glad to see this being worked on.
I had issues with the focal camera and would love some a2sd support. I had to go back to stock aosp but certainly wiling to do any testing if needed.
Very convenient.. Thanks!
Deleted
Just did a clean flash. Noticed directly that LTE didn't work. It says LTE in status menu. But no LTE in data connection. Not even HSDPA. Calls and Sms works.
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
is there any mute calls or not?
Audioboxer said:
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Mohanned85 said:
is there any mute calls or not?
Click to expand...
Click to collapse
Take these questions to the discussion forum.
Sent from my GT-I9505
deezytg1 said:
Glad to see this being worked on.
I had issues with the focal camera and would love some a2sd support. I had to go back to stock aosp but certainly wiling to do any testing if needed.
Click to expand...
Click to collapse
I'm not a developer; I'm simply providing a list of bugs to help our community of cm 10.2 users.
Sent from my GT-I9505
Audioboxer said:
Titanium backup doesn't work on 10.2 for me.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Developer options
Only shows up in Settings when you tap 7 times on the Build number in Settings/About phone.
ADB
For your PC to get ADB access, enable USB debugging in Settings/Developer options.
Super user
Does not work after a clean install.
Workaround: change Root access to Apps and ADB in Settings/Developer options
OR
Install SuperSU from Play Store and install binaries
TB will work fine then...
bariz143 said:
Just did a clean flash. Noticed directly that LTE didn't work. It says LTE in status menu. But no LTE in data connection. Not even HSDPA. Calls and Sms works.
Click to expand...
Click to collapse
Went to the mall and saw LTE appears which I didn't expect to work since I've been on AOSP for a while without it. Quickly did a speed test and got 8 Mbps down and 3.5 up and this is with Sprint.
vboyz103 said:
Went to the mall and saw LTE appears which I didn't expect to work since I've been on AOSP for a while without it. Quickly did a speed test and got 8 Mbps down and 3.5 up and this is with Sprint.
Click to expand...
Click to collapse
LTE or 4G works fine for me also.
Sent from my GT-I9505
There is a bug in Trebuchet launcher. After reboot some of icons in folders simply disappear
two bugs I noticed:
Alternate action of 'long press Home button' doesn't stick (after closing settings It's back to app-switching when I long press, where I selected Search-app)
Mobile network modes set to: GSM/WCDMA/LTE, when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE)
lostfriends said:
There is a bug in Trebuchet launcher. After reboot some of icons in folders simply disappear
Click to expand...
Click to collapse
Can others confirm this?
Akerboom said:
two bugs I noticed:
Alternate action of 'long press Home button' doesn't stick (after closing settings It's back to app-switching when I long press, where I selected Search-app)
Mobile network modes set to: GSM/WCDMA/LTE, when opening the drop-down menu it selects the option LTE (which is two above GSM/WCDMA/LTE)
Click to expand...
Click to collapse
Can others confirm these?
For me, the network modes work properly. And I don't have an LTE option on its own.
Sent from my GT-I9505

Android Permissions - Not able to switch off

Hi all,
Just out of curiosity. I have a 3rd party app on my phone (not available on the Google Play Store, obviously)
I am currently running Android 7.0. When accessing the settings - - > apps--> theApp--> permissions where one can adjust the permissions on demand, I noted that the "Telephone" permission for this specific app cannot be switched off.
When selecting to switch it off there is the usual prompt that the app won't work as intended and I "continue anyway". The slider goes into the off position. Then when clicking back and then opening the permissions, the Telephone permissions switch is back into the on position.
What do you make of this? I have suspected that the app is "spying" somehow for quite some time. Reverse engineering on the apk itself had some very strange permissions logged in the Android Manifest file.
I would really like to hear your opinion....
41 views and zero replies....

[ROM][PX30][Q][10.0] Malaysk ROM for PX30 RK3326 with Android 10

Only for devices processor Rockchip PX30, MCU - MTCD, MTCE Android 10.0 !
Mod Q 10.0 Android PX30 RK3326​For PX5 RK3368 mod 10 android is HERE
For PX6 RK3399 mod 10 android is HERE
Only for those who have 10 android installed, a PX30 processor and have an installed MCU that starts with MTC (X) - where X can have different letters.
With firmware device, you need to understand all the risks. Neither I nor the website is not responsible for your actions and possibly killed devices! Everything you do - you do at your own peril and risk.
Before installing the firmware, be sure to try to get into the Recovery (I have this method - I press the RESET button (RST) and hold the buttons on the front panel of the device until the buttons blink - I release the RESET button and immediately press the RESET button again for a short time 1-2 times ).
IMPORTANT!! : You cannot change the firmware versions in the system partitions - System, Vendor, ODM and Product (this is due to the fact that in 10 android these sections are dynamic and protected by the android itself from changes)- otherwise you will have a BLACK SCREEN after reboot and you will have to go to RECOVERY and reinstall the firmware from there (you can without deleting the data).
How do you know if your device is suitable for this forum thread? You can see the device in Settings - System - About device: look at the photo
​What's added, fixed in LITE firmware version:
Can't update Magisk module !! Only Magisk Manager can be updated!
Root access (Magisk) 8.0.2
IMPORTANT!! : You cannot change the firmware versions in the system partitions in LITE - System, Vendor, ODM and Product - otherwise you will have a BLACK SCREEN after reboot and you will have to go to RECOVERY and reinstall the firmware from there (you can without deleting the data).
Added ESFileExplorer, RootExplorer programs.
Two modified launchers with the ability to customize them (located in Mod Settings).
Enabled the ability to start the screensaver and set the start time to 15-30 seconds 1-3-5-7-10 minutes.
By default, video viewing while driving is enabled and audio mute in Navigation is set to -3.
Changed basic Settings.
Possibility to set viewing of Internet traffic speed in the Status Bar.
Ability to change color and gradient in the Status Bar.
Many other changes and additions.
Installing LITE firmware version:
Unzip the archive and write the Update.zip file to a SD card or USB flash drive (must be formatted in FAT32). Insert into the loaded device. After a few seconds, the update menu will appear. We put a checkmark on Wipe Data (you will lose all your installed programs) and click on the Install button. See the screenshot below. The machine will reboot and the firmware installation will begin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download LITE version:
Version updated as of March 28, 2022.
Be sure to read the instructions inside the archive, along with the firmware !!!
I want to warn you: Everything that you do, you do at your own peril and risk.
Can't update Magisk module !! Only Magisk Manager can be updated!
Download: https://disk.yandex.ru/d/8f8jtvsBHvA8wA
Mirror: https://mega.nz/file/JhBSVJZa#vDTqAplSQGZ1zNqyifxiC4OzIw-9RVfscxYyGLUIJfo
----------------------------------------------
What's added, fixed in FULL firmware version:
Can't update Magisk module !! Only Magisk Manager can be updated!
Full root access (Magisk)
IMPORTANT!! : You cannot change the firmware versions in the system partitions - System, Vendor, ODM and Product - otherwise you will have a BLACK SCREEN after reboot and you will have to go to RECOVERY and reinstall the firmware from there (you can without deleting the data).
Seven completely modified launchers with the ability to view tags for listening to music (any music app), Bluetooth music and radio stations.
The ability to customize Launchers (enable, disable unnecessary functions in the settings) and weather settings in them and display the speed via GPS.
4 types of screen savers with analog and digital clocks, with the ability to display GPS speed, weather, music listening tags (any music application),
Bluetooth music and radio stations from the Radio app. Full customization of screensavers - color, font, disabling unnecessary functions, your car logo, etc. In the settings.
Change splash screen - hold your finger in the center of the screen for 3-5 seconds - the view will change. Other screensavers are in the OEM app.
Changed the volume bar and reduced its disappearance time. It is also fully configurable in Settings Mod - Mod settings - Sound settings.
Fully customizable panel status with the ability to enable and disable buttons and icons in it in the settings and it is possible to completely disable it.
Reload key added to the status bar.
Added buttons "Screensaver", "Music", "Navigation", "Bluetooth Music" in the status bar (can be enabled or disabled in the settings).
Changed the function of calling the brightness panel in the status bar.
The screensaver is now launched in all programs, in the Mod Settings there is an Application Whitelist, where you can specify applications where the screensaver will not start.
Added a list of applications in the Mod settings, where you can specify autostart after sleep.
Added equalizer ViperFX - you can watch the settings in the video
Changed Bluetooth Music app.
Applications Music, Radio, Video have been completely changed. You can install standard applications from the OEM application.
Video files can be played in the background.
Now when you switch on rear view camera the brightness is in creased up to maximum automatically
4 different types of radio apps have been added in the OEM app (including radio with Day and Night support)
Go to the OEM app and install the app from there.
3 different types of Music app have been added in the OEM app.
Split screen support (not all apps support)
Added online radio PCRadio
Mod settings - MOD Settings - System settings - added automatic screen brightness by GPS.
Supports 1280X720 and 1024X600 screen resolutions.
Added four customizable buttons to screensavers to launch your programs.
- Long press on the button - select the application.
- Short press on the button - start the application.
You can now configure the MODE button to launch your applications.
- Located in Mod Settings - MOD Settings - System Settings - Select applications to launch by pressing the MODE button.
- If it is disabled, the standard method of operation of the MODE button is used (launching Radio-Music-Video)
Added the ability to automatically adjust the sound based on GPS speed.
Located in Settings mod - MOD Settings - Sound settings - Auto volume control by GPS.
Added the ability to set pop-up messages about playing Music, Radio, Bluetooth music and PCRadio.
Located in Mod Settings - MOD Settings - System Settings - Popup Settings.
Fixed GPS work.
- Improved location accuracy.
- With a cold start - satellites are located in 40-70 seconds.
- With a hot start (after sleep or reboot) - instantly.
Anyone who had problems with USB ports or missing WiFi - fixed.
USB and WiFi are initialized after the system is fully booted and after sleep.
New method and settings of the whitelist of programs to run after sleep (located in Mod Settings - Mod Settings - System Settings)
New whitelist for programs in which the screensaver will not start (located in Mod Settings - Mod Settings - Screensaver Settings)
Redesigned Launcher with day and night support. Also added to Mod Settings - Mod Settings - Launchers to configure it. You can customize the display of the main screen
- Clock, GPS speed, Weather or choose to display your logo (download a logo on the Internet (for example, a BMW car logo),
in PNG format and preferably with a transparent background and copy the file to the device's internal memory)
If after updating the firmware, every time the system boots, the location permissions for the launcher are asked, go to Mod Settings - Mod Settings -
Launcher Settings - Launcher with day and night support and enable GPS speed display.
New graphic equalizer in Music and Screensaver apps, with four different graphic equalizers and color selection.
You can now set the time for showing music and radio notifications in Mod Settings from 1 to 10 seconds.
You can change the DPI of the screen. The range is from 260dpi to 160dpi (standard 220 by default) - I set it to 200dpi. Located - Mod Settings - Mod Settings - System Settings.
You can assign the launch of your applications to the buttons on the steering wheel or on the front panel of the device. Located in Mod Settings - Mod Settings - Car (as you select applications there, then assign buttons through the standard application, for setting the buttons on the steering wheel, for example). - you can watch the video on how to configure -
More flexible graphic equalizer settings are in Mod Settings - Mod Settings - Sound Settings.
Mod Settings - Mod Settings - Car - added GPS fix (enabled by default).
Redesigned regular widgets for managing Music, Radio, Bluetooth music, etc.
Configurable rear camera parking lines, you need to go to Settings Mod – Car - related settings – Extra settings and enable 1-2-3 type of Rear view ruler.
EasyConnected has been updated to the latest version.
Can't update Magisk module !! Only Magisk Manager can be updated!
Many other fixes and additions.
Installing FULL firmware version:
You must download the LITE version, read the instructions inside the archive and be sure to install the LITE version on your device.
Download FULL version:
Installation only on LITE firmware version and only through online update. Download the LITE version and read the instructions inside the archive.
VIDEO FULL version
Online update 1.1.8.5 released on August 12, 2021
BETA FULL version 1.2.2 from 03 December 2021
Sample ViperFX settings -
Important information (announcement of future OTA updates) - https://forum.xda-developers.com/t/...-rk3326-with-android-10.4185981/post-84457467
Who wants to translate Settings into their native language - https://forum.xda-developers.com/an...roid-6-8-9-t3955343/post80203246#post80203246
----------------------------------------------
Many thanks to the respected Graser from the 4PDA forum for invaluable help in creating the firmware!
+++++++++++++++++++++++++++++
This post is in edit mode! Errors and inaccuracies are possible!
Please excuse me in advance! I very rarely answer questions and do not use private messages!​
reserved
Hello master,
I updated my PX30 android 9 with mod installer (from Hal9k)
I had to flash a stock android 10 rom first and let it boot (your zip was aborted with mod installer on android 9)
All is fine, I'm updating OTA paid version now.
For other users, why don't you build your own recovery to update from 9 ? (just a suggestion to update more easily and if it's possible ! :fingers-crossed: )
Thank you for great work again :good:
Sorry for double post.
After 2 days , its great rom , I really like your Mal dark launcher :good:
I have 2 problems for now :
1- no FM or AM signal (I checked everywhere my antenna is ok, I don't understand)
2- no mp3 pictures with music player. Tags are oK with songs and artists but no pictures. I downloaded Poweamp and it's perfect ( Stellio or default player from plastore don't even see mp3)
Good job
Edit: problem with volume bar too. When higher than 9, it shows only 1 instead of 10 11 ... see pic
I'm so grateful that I found this ROM!
I upgraded my ISUDAR from the stock Android 10 to your ROM few hours ago. The option to upgrade didn't pop up after inserting the SD card but it was possible to upgrade through recovery. I was a bit nervous, but it worked no problem.
My main reason for trying an alternative system was the fact that the stock is really slow, especially Spotify and Google Maps. After the upgrade, I think everything became about twice snappier. Still not 100% ideal, but way better and more usable (honestly, I regret not buying PX5, I wasn't informed).
As for hardware, I haven't found any problems. Audio works, Bluetooth works, WiFi works, GPS works, Steering Wheel buttons work (next and previous song button is swapped but that's okay, I can remap it, same problem with the original ROM). I can't test FM reception yet because my antenna is not connected (I have a Ford and haven't bought the FAKRA pigtail yet) .
I need to test it more but I think I will buy the full version from you!
Nice work!
Hi,
I have another problem with BT calls, when I call someone, discussion starts and 2/3 sec later I have black screen and bootloop
I checked BT in factory settings, the only one works is SD-BC6
BTmusic is working as it should, BT connection is ok, I don't understand
Hi, I installed the lite version so far. The ROM works fine. I have two or three issues.
1. The parking radar display does not work at all. I'm not using backup camera, I'm only using the parking radar display with the parking sensors and it does not show.
2. The Bluetooth app has a delay, when you dial it takes a few seconds untill the phone actually starts dialing.
3. When you are in a call and you have the green phone icon flashing in the down right corner, the touch screen is not responsive in the lower part.
The last two issues are common with the stock rom also. Can they be fixed?
So for the ROM feels smoother than stock A10, haven't tried bluetooth yet since I use CarPlay so I wonder if the other issues reported would also occur.
Possibily will purchase the full version too.
DSGTS said:
2. The Bluetooth app has a delay, when you dial it takes a few seconds untill the phone actually starts dialing.
3. When you are in a call and you have the green phone icon flashing in the down right corner, the touch screen is not responsive in the lower part.
The last two issues are common with the stock rom also. Can they be fixed?
Click to expand...
Click to collapse
Problem solved with 20201117 rom ! no problem with BT Calls, no more delay, now you can navigate on the screen in call, I hope you will read this @Malaysk
ric69 said:
Hello,
No one has feedback on the BT phone part bug with PX30 RK3326 ? When I receive or I call someone, conversation start and 2/3 second later, unit reboots itself
Thanks for feedback
[edit] I see there is a new update in mic-autoradio, I will try if something is better https://www.mic-autoradio.com/updates/
They are writing new fix :
4. Bluetooth contact syncing raise problem.
[edit2] Problem solved with 20201117 rom ! no problem with BT Calls, no more delay, now you can navigate on the screen in call, I hope you will read this @Malaysk
Click to expand...
Click to collapse
Hello. Please try to install the LITE version again and update it again by OTA update (I slightly corrected the firmware) and write please - will your problem be solved?
OK I'm trying now :good:
I re-wrote my last post (people don't have to test mic-audio in your thread :laugh: you can remove my "quote" from your post)
ric69 said:
Problem solved with 20201117 rom ! no problem with BT Calls, no more delay, now you can navigate on the screen in call, I hope you will read this @Malaysk
Click to expand...
Click to collapse
Nice! Than you very much. What about the Parking radar display? Is it possible to have a proper Canbus app with a proper park pilot image in full screen. For now the parking radar image with the parking sensors appears now and then.
I must report that BT Calls bug was my fault ...
Not really but the problem was my SDCard ! when I inserted my 16gb sdcard in "GPS" slot and configured "only for media and transfers", then bug was appearing and when I started a call, 2/3 sec later, unit reboots.
I found if I move my sdcard to 2nd slot (ext-sd) then I can make calls without any problem :cyclops:
So I don't know if my sdcard 16gb sandisk is buggy (it works fine on 2nd slot) or if it's bug with config sdcard program in android10
:victory:
Hello. Do the "Accessibility Options" work in this rom?
ShadoVeX said:
Hello. Do the "Accessibility Options" work in this rom?
Click to expand...
Click to collapse
Hello I don't know
Yesterday, I had big issues when unit restarts itself after lots of popups " system not responding" or rebooting when I started to listen music, I tried to remove sdcard (w or w/o, it was the same :silly: ) I wanted to try MTCDialer but it was not a good idea
So back to android9 and waiting patiently for next update :fingers-crossed:
Finally my sdcard is not in fault and is working as it should in A9 (with mp3 tags) :good:
Hello Everyone,
I installed the LITE version and it is working perfectly except the mobile stick. I tried 3 different sticks with the same result: the signal strength icon showed up on the notification area and then dissappeard. (these sticks was working with the stock android 10 roms)
Is this a LITE version disability?
Online update of the full version 1.1 from 2 December 2020
1. Added 5 attempts to initialize WiFi every 20 seconds with network availability check
2. Added forced activation of disabled WiFi SSIDs, device why it periodically sets the working SSID status Disable and automatic connection does not occur.
3. Brightness adjustment service. When the rear or front camera is turned on, the brightness rises to the maximum allowed
4. The display of pop-up notifications has been changed. (Elimination of a potential error)
5. Redesigned service, excluding the simultaneous operation of different players. Fixed a bug that caused the current player to close when going to sleep
6. Redesigned algorithms to run ScreenSaver. It will not start when the rear camera is turned on.
7. Elimination of various small bugs
8. Introduced MTCDialer. Basic f1x application, redesigned to support Android 10 (voice dialing program. You need to sync
your contacts in the bluetooth application)
9. Added an alternative program for your contacts and calls (it is necessary to synchronize your contacts with the Google account)
10. Added a new equalizer. You need to install it from the OEM application from the EQ_DSP folder.
11. Fixed voice prompts in the google maps application.
12. Added new mod applications Music 7 types. Located in the OEM application in the Music_Mod_Malay folder
13. Added new mod applications for Radio 12 types. Are in the OEM application in the Radio_Mod_Malay folder (some have the ability to write their own radio station names)
14. Added RDS Radio show in screensaver and in some launchers. RDS settings are - Mod settings - MOD settings - Car - RDS display settings.
15. Fixed Lock Screen
16. Many other corrections and additions.
To get an update, you can go to Mod Settings - OTA updates - click on the update search button or reboot - the update menu will appear automatically.
Malaysk said:
Online update of the full version 1.1 from 2 December 2020
1. Added 5 attempts to initialize WiFi every 20 seconds with network availability check
2. Added forced activation of disabled WiFi SSIDs, device why it periodically sets the working SSID status Disable and automatic connection does not occur.
3. Brightness adjustment service. When the rear or front camera is turned on, the brightness rises to the maximum allowed
4. The display of pop-up notifications has been changed. (Elimination of a potential error)
5. Redesigned service, excluding the simultaneous operation of different players. Fixed a bug that caused the current player to close when going to sleep
6. Redesigned algorithms to run ScreenSaver. It will not start when the rear camera is turned on.
7. Elimination of various small bugs
8. Introduced MTCDialer. Basic f1x application, redesigned to support Android 10 (voice dialing program. You need to sync
your contacts in the bluetooth application)
9. Added an alternative program for your contacts and calls (it is necessary to synchronize your contacts with the Google account)
10. Added a new equalizer. You need to install it from the OEM application from the EQ_DSP folder.
11. Fixed voice prompts in the google maps application.
12. Added new mod applications Music 7 types. Located in the OEM application in the Music_Mod_Malay folder
13. Added new mod applications for Radio 12 types. Are in the OEM application in the Radio_Mod_Malay folder (some have the ability to write their own radio station names)
14. Added RDS Radio show in screensaver and in some launchers. RDS settings are - Mod settings - MOD settings - Car - RDS display settings.
15. Fixed Lock Screen
16. Many other corrections and additions.
To get an update, you can go to Mod Settings - OTA updates - click on the update search button or reboot - the update menu will appear automatically.
Click to expand...
Click to collapse
Hi,
I installed the latest full version. The system did not boot at the first boot, it went into recovery and asked for a factory default. I did the factory reset and the system eventually started. There are a few issues:
1. it seems sluggish, it doesn't seem as fast as the lite version.
2. The unit does not go into autosleep, even if it is set to go into autosleep. This is very annoying.
3. Every time the system boots, it doesn't see the usb. I have to unplug the data stick and reconnect it in order to make it visible to the system.
4. At every boot it doesn't keep the mod settings. For instance, I set it to hide the status bar, but after the boot it is not hidden, even if the setting is set to hide it.
5. The issue with the Bluetooth call is still present, when I try to make a call it takes seconds until it actually starts making the call.
6. Please fix the issue with the lower part of the touch screen, wich is not working during the calls.
Hi, where can I find the download link for Lite version? I wanted to download Android 9 Malaysk Rom. For that I found link and instructions. In this topic I did’t find. Or maybe I’m just blind
tutte80 said:
Hi, where can I find the download link for Lite version? I wanted to download Android 9 Malaysk Rom. For that I found link and instructions. In this topic I did’t find. Or maybe I’m just blind
Click to expand...
Click to collapse
Yes, I’m blind. Found it

Can't change permissions in root dir anymore?

New phone, Pixel 5. Trying to disable the annoying shutter noise when a picture is taken. Phone is rooted (and confirmed with rootchecker), can access the root dir. Found the camera sound file (to replace with silent audio file).
No file browser I've tried (5+ of them) will let me change the permissions so I can write to the folder/file. It's moved in Android 11 to root/product/media/audio/ui
Any way to change the permissions there?

Categories

Resources