Develop Bugs

[JVP] Automatic brightness fix DIY

I've made this thread to show you how to fix this frustrating bug. After few steps you'll get working light sensor better than in previous GB versions
Files need to be replaced or edited:
- services.jar
- framework-res.apk
- sensors.default.so
Recommended kernel:
- Galaxian*
Based on original Samsung sources
All Voodoo addictions (color fix, sound V9)
CPU frequencies: 100MHz, 200MHz, 400MHz, 800MHz, 1000MHz, 1200MHz, 1300MHz, 1400MHz.
CONFIG_HZ=500
CWM 3.0.0.5 based on, and fully compatible with CF-ROOT
Light sensor polling 1s instead of 2s
Compatible with RFS and EXT4
Much more I can't remember
What needs to be done:
framework-res.apk edit
1. Get apk manager (attached)
2. Put framework-res.apk in "place-apk-here-for-modding" folder
3. Run apk manager, decompile with dependancy (option 10)
4. Drag twframework-res.apk from your ROM into the script, or extract it somewhere and type path to it
5. Go into projects\framework-res\res\values\arrays.xml
6. Replace two sections:
<integer-array name="config_autoBrightnessLevels">
<item>30</item>
<item>300</item>
<item>600</item>
<item>1500</item>
<item>1500</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>80</item>
<item>150</item>
<item>200</item>
<item>255</item>
</integer-array>
Click to expand...
Click to collapse
7. Delete .bak file if you got one after changes
8. Go back to script and select compile
9. Say y
10. Say y
11. Delete resources.arsc from keep folder
12. Enter in script
13. U'll find unsignedframework-res.apk in "modding" folder
14. Use ADB
Code:
adb push unsignedframework-res.apk /data/local/tmp/framework-res.apk
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/framework-res.apk
cp /data/local/tmp/framework-res.apk /system/framework/
rm /data/local/tmp/framework-res.apk
reboot
services.jar replace/edit
Attached services.jar should be compatible with all JVP releases as long as author didn't modified it. If you are not sure you can always edit your own version by doing:
1. Get apk manager (attached)
2. Put services.jar in "place-apk-here-for-modding" folder
3. Rename it to services.apk
4. Run apk manager, decompile (option 9)
5. Go into projects\services.apk\smali\com\android\server\
6. Replace PowerManagerService.smali file with the one from my services.jar
7. Delete .bak file if you got one after changes
8. Go back to script and select compile
9. Say n
13. U'll find unsignedservices.apk in "modding" folder
14. Rename it to services.jar
14. Use ADB
Code:
adb push services.jar /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/services.jar
cp /data/local/tmp/services.jar /system/framework/
rm /data/local/tmp/services.jar
reboot
sensors.default.so replace
1. Use ADB
Code:
adb push sensors.default.so /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/lib/hw/sensors.default.so
cp /data/local/tmp/sensors.default.so /system/lib/hw/
chmod 644 /system/lib/hw/sensors.default.so
rm /data/local/tmp/sensors.default.so
reboot
GALAXIAN KERNEL:
1. Go to the Market place
2. Install SGS kernel flasher
3. Extract zImage.7z to your internal SD card
4. Select zImage and flash
5. Be happy
New version of sensors.default.so! Now all 4 steps are working!
BTW. With those files you will now loose BLN!

Thank you very much in providing this fix.

Thks
This is what I have been waiting for....
I will recompile my services.jar n framework-res.apk and incorporate them into my custom rom.
Thank you so much!

i do not get it =) what is this fixing Oo

$omator said:
i do not get it =) what is this fixing Oo
Click to expand...
Click to collapse
It fixes the Auto brightness issue in some kernels.

i guess when auto brightness is checkedit is not reacting or reacting wrong?

Im guessing this only works on deodexed?

This is a fix of the moth !
THANK YOU SIR !
btw., what kernel is this? your own ?
Simce I can't find Galaxian anywhere on the forum.
Btw. where are the attached binaries from? Extract from original JVP kernel ?

$omator said:
i guess when auto brightness is checkedit is not reacting or reacting wrong?
Click to expand...
Click to collapse
In some kernels the brighness is reversed or totally wrong.
This has fixed it.

@ Brotuck
Will you try and include this in your GingerMod Rom? (...does it need it?)

eternal-intent said:
@ Brotuck
Will you try and include this in your GingerMod Rom? (...does it need it?)
Click to expand...
Click to collapse
I already updated my GM22 @ damians site.
It also uses a slightly different value, tested it today worked fine !

Brotuck said:
I already updated my GM22 @ damians site.
It also uses a slightly different value, tested it today worked fine !
Click to expand...
Click to collapse
Cool.
Well, I'm off to check it out...
And to the OP thanks, I'm interested to see what effect this has...it's not that I'm lazy, I just still lack confidence in my adb (dis)ability or I'd be more inclined to try and do it myself.

CWM can ask

ok now i see what is going on here =)
-provided sensors.default.so is 1:1 with stock JVP one
Click to expand...
Click to collapse
-arrays.xml is tweaked when compared to stock - and my guess OP made an error here as
<!-- Array of output values for LCD backlight corresponding to the LUX values
in the config_autoBrightnessLevels array. This array should have size one greater
than the size of the config_autoBrightnessLevels array.
-->
Click to expand...
Click to collapse
those are stock values from JVP below
<integer-array name="config_autoBrightnessLevels">
<item>30</item>
<item>2000</item>
<item>6000</item>
<item>11000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>32</item>
<item>70</item>
<item>116</item>
<item>177</item>
<item>253</item>
</integer-array>
Click to expand...
Click to collapse
Click to expand...
Click to collapse
-at the services.jar few more tweeks that i do not see much sense in =)
i would realy like to see explanation of those changes
Click to expand...
Click to collapse

Ill look at this properly, but couldn't you put this in a CWM flashable package? Thanks if you can.
Sent from my ever changing Galaxy S

CWM flashable package, please

The biggest "problem" is that you need to change values in the framework.
And that one is connected to the theme you use.
Battery color / lockscreens stuff like that.
So making 1 general CWM is a problem....
If you encounter brightness problems, like not responding to changes or bright light in the dark (when it should be darker)
Then but only then consider this mod, if you do not know how to do it, then ask the theme maker.

ill rephrase my question =)
why those fixes (left stock, right this fix/tweak)
ALL_BRIGHT from 15 to 255
ANIM_STEPS from 10 to 50
AUTOBRIGHTNESS_ANIM_STEPS from 10 to 50
LIGHT_SENSOR_DELAY from 2000 to 1000

@$omator: it`s working! i think this is the only relevant answer!
you know a better way? then do it and start your own thread!

I'd like to try this fix but I can't because each time >compile< gets me an error in APK Manager! Something like "unknown source" and "could not exec command". Does anyone here have any success with this fix and Bezke JVP-ROM?

[APP][MOD] MiFile Explorer! + TUTORIAL "How to transfer files without an USB cable"

[APP][MOD] MiFile Explorer! + TUTORIAL "How to transfer files without an USB cable"
Hi mates!!
This was the last version of MiFile Explorer by HootanParsa, I've modified it with the ICS/JB theme
I would like to share it with you :good:
(ROOT + CWM 5x IS REQUIERED, INSTALLATION PROCESS)
DESCRIPTION
This is a POWERFULL lightweight file explorer, allows you root access, edit text files, change permissions, FTP Sever connections and many more!
CHANGELOG (by apooonet)
v3.0.4 :
- Optimized loading lists and thumbs
- Fixed Some little bugs
INSTALLATION (.apk file)
1. Donwload the .apk file
2. Copy/move it and paste into /system/app (use your favourite file browser)
3. Long press in the .apk file and set the following permissions:
Code:
____________________
| |
| [B][SIZE="3"]|@| VTR_MIFILE.apk[/SIZE][/B] |
| |
| |
| [B][COLOR="Red"] R W E[/COLOR][/B] |
| [B][COLOR="blue"]Owner[/COLOR][/B][COLOR="White"]![/COLOR] x-x-- |
| [B][COLOR="blue"]Group [/COLOR][/B]x---- |
| [B][COLOR="blue"]Others [/COLOR][/B]x---- |
| |
| |
| [B]AGREE [/B]| [B]CANCEL [/B]|
|____________________|
4. Reboot!
and ENJOY IT!
CWM FLASHBLE ZIP INSTALLATION
1. Download the zip file.
2. Boot into recovery.
3. Install from sdcard
4. Flash it
6. Done!, reboot system now
CREDITS
HootanParsa for the original apk
Me by modded .apk and to create the tutorial
TUTORIAL Forget your USB connection to transfer files from your laptop to your Galaxy Ace!
How to transfer files without a USB cable using Mi File Explorer
1. You need to install MiFile Explorer (see above)
2. Open the file browser, click on "share" and set up your FTP connection point, long press to edit the values.
{
"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"
}
3. Set your own values, IS COMPULSORY TO MAINTAIN THE CORRECT PATH >>> /mnt/sdcard/FOLDERNAMEWHATEVERYOUWANTINYOURSDCARD |Example: /mnt/sdcard/download|
*** You'll be able only to access to the specified folder in the path then in "My network sites", so if you want to access to ALL your sd card folders set by default "/mnt/sdcard"
4. Ready! Start your FTP service (by pressing on the icon / long press and then "start")
It's time to configure the network place in Windows (I'm using Windows XP)
1. Go to "My Network Places"
2. Click on tools, then click "Connect Network Drive ..."
3. Uncheck "Reconnect at logon" (optional) and click on "Subscribe to remote storage or connect to a network server"
4. Follow the connection wizard, entering the FTP server address that Mi File Explorer provided you when you created the FTP point
5. Uncheck "Log in automatically" (optional) and create your own profile (using the same user name you put to create FTP point)
6. Put a name to the folder that will keep the connection between devices and will appear in "My Network Places"
7. ENJOY transferring files via WiFi instead of using an USB cable!!!
WINDOWS XP/VISTA/7/8.x USERS
To make to work MiFileExplorer modded by me or any other version is A PIECE OF CAKE in Windows!
1°. Enable the FTP server
2º. Go to your PC/laptop and open Windows Explorer or any folder (Windows Explorer ISN'T INTERNET EXPLORER)
3º. Put this: "ftp://xxx.xxx.x.xxx:xxxx" in the address bar, as the IP address set by the aplication and press ENTER :laugh:
4º. ENJOY transferring files via WiFi instead of using an USB cable!!!!
HELLYEAH!!! :laugh:

Thank you, It looks really good

Viper The Ripper said:
Hi mates!!
This was the last version of MiFile Explorer by apooonet, I've modified it with the ICS/JB theme
I would like to share with you :good:
DESCRIPTION
This is a POWERFULL lightweight file explorer, allows you root access, edit text files, change permissions, FTP Sever connection and many more!
CHANGELOG (by apooonet)
v3.0.4 :
- Optimized loading lists and thumbs
- Fixed Some little bugs
INSTALLATION
Just put it in System/app and set the permissions
x-x--
x----
x----
...then reboot!
and ENJOY IT!
CREDITS
apooonet for the original apk
Click to expand...
Click to collapse
Which rom're u using?
Sent from Speriance ®

Blackstard said:
Which rom're u using?
Sent from Speriance ®
Click to expand...
Click to collapse
xwks2 stock rom modded by me

Viper The Ripper said:
xwks2 stock rom modded by me
Click to expand...
Click to collapse
Please share it with us .. It looks really nice )
Sent from my GT-S5830 using xda premium

GeRmAnRoMs said:
Please share it with us .. It looks really nice )
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
At the moment I'm using android 2.3.5 (xwks2)
I'll try to port it to 2.3.6 when I've free time, but it's a piece of cake make a similar theme with UOT kitchen

help in step 3 ican't ste the folder it sys inalid , what did oyu set?im using windows xp aswell

Andraxo said:
help in step 3 ican't ste the folder it sys inalid , what did oyu set?im using windows xp aswell
Click to expand...
Click to collapse
...?
You write so quickly
Could you especify me more?
Following the tutorial is death easy!

Viper The Ripper said:
...?
You write so quickly
Could you especify me more?
Following the tutorial is death easy!
Click to expand...
Click to collapse
whatever i write in the folder formula it alwayssays invalid what sohuld i write if i write the /mnt/sdcard it says invalid?

Andraxo said:
whatever i write in the folder formula it alwayssays invalid what sohuld i write if i write the /mnt/sdcard it says invalid?
Click to expand...
Click to collapse
Share> (long press on the icon) Edit> Set your own values!, by default the address is "/mnt/sdcard" if you want to change it to other address, you need to make a new folder in your sdcard or put an address there.
Example1: (creating a new folder un your sdcard) you create "ftp" folder in your sd card, so the address will be "/mnt/sdcard/ftp" (without quotes)
Example2: (link the existing folder) "download" folder is created by default when you open internet browser, so put this address "/mnt/sdcard/download"
You only can access to the specified folder in the path in "My network sites", but if you want to access to ALL sd card folders set by default "/mnt/sdcard"
FIRST POST UPDATED!
I hope it work for you!
I've never had any problem with it...

Viper The Ripper said:
Share> (long press on the icon) Edit> Set your own values!, by default the address is "/mnt/sdcard" if you want to change it to other address, you need to make a new folder in your sdcard or put an address there.
Example1: (creating a new folder un your sdcard) you create "ftp" folder in your sd card, so the address will be "/mnt/sdcard/ftp" (without quotes)
Example2: (link the existing folder) "download" folder is created by default when you open internet browser, so put this address "/mnt/sdcard/download"
You only can access to the specified folder in the path in "My network sites", but if you want to access to ALL sd card folders set by default "/mnt/sdcard"
FIRST POST UPDATED!
I hope it work for you!
I've never had any problem with it...
Click to expand...
Click to collapse
thank you and anyways solution for what i was facing is not use "\\" but use "//" lol

Im enjoying it in windows xp, but how to do this in windows 7 ?
Thanks

Amrao said:
Im enjoying it in windows xp, but how to do this in windows 7 ?
Thanks
Click to expand...
Click to collapse
this should work similarly, this weekend I will try to find out for sure

HELLYEAH WINDOWS 7 USERS!! xD
To make work MiFileExplorer modded by me or any other is A PIECE OF CAKE in Windows 7!
You just need to use Windows Explorer
1°. Enable ftp server
2º. Go to your PC/laptop and open Windows explorer or any folder
3º. Put this in the address bar, as the IP address set by the aplicaccion "ftp://xxx.xxx.x.xxx:xxxx"
4º. Enjoy it!

Amrao said:
Im enjoying it in windows xp, but how to do this in windows 7 ?
Thanks
Click to expand...
Click to collapse
There you go buddy! :good:
First post updated!

Viper The Ripper said:
HELLYEAH WINDOWS 7 USERS!! xD
To make work MiFileExplorer modded by me or any other is A PIECE OF CAKE in Windows 7!
You just need to use Windows Explorer
1°. Enable ftp server
2º. Go to your PC/laptop and open Windows explorer or any folder
3º. Put this in the address bar, as the IP address set by the aplicaccion "ftp://xxx.xxx.x.xxx:xxxx"
4º. Enjoy it!
Click to expand...
Click to collapse
well thanks but i am afraid that just entering the address of ftp:XXXXXXXXXX we would only copy from device to PC but not from PC to device any how i will check that.

Amrao said:
well thanks but i am afraid that just entering the address of ftp:XXXXXXXXXX we would only copy from device to PC but not from PC to device any how i will check that.
Click to expand...
Click to collapse
Muajajaj! You relly?...
Try it and tell me them

Very useful! Thanks man!

mikkosci said:
Very useful! Thanks man!
Click to expand...
Click to collapse
Did you try it using Xp or W7? Could you give me feedback please?
The last mate didn't tell me nothing after he tried it anyway, both method should work as hell! xD

Viper The Ripper said:
Did you try it using Xp or W7? Could you give me feedback please?
The last mate didn't tell me nothing after he tried it anyway, both method should work as hell! xD
Click to expand...
Click to collapse
Sorry dude I was out of town and as I was worried it didn't worked with window 7 like it amazed me with window xp.

[ROM][WIP/Experimental][AOSP][4.3.1] Google Edition for SGS4A (int'l) v0.8

What?
work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
build makefiles modified, using CM files where possible
some small code modifications
for I9295 international only
stuff is broken, for how long i do not know. I'm still learning this stuff
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned
How?
grab the file: https://drive.google.com/folderview?id=0BzJzDM42pkRvcUVyZDRVSERzdlk&usp=sharing
if coming from another rom: factory reset + system format
upgrading previous version shouldn't need factory reset or system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
help with development if possible
Credits
Google for Android (and Google search, boy this wouldn't have happened without it )
CyanogenMod for stuff i'm using to make this happen
SlimRom guys
LeJay for jactivelte kernel sources and other stuff
ohwarumbloss for testing CM builds and donations
Chainfire for root
other donators and testers
Changes v0.8
Video preview fixed
sub-1080p video recording fixed
Audio volume settings copied from SlimRom jf-common, more volume
Changes v0.7.1
Only kernel changes
Newer Broadcom wireless drivers from S4 CM 10.2 kernel
EXT4 and JBD2 drivers from S4 CM 10.2 kernel
MSM-8960 related stuff from S4 CM 10.2 kernel
Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me
Changes v0.7
dualboot version available
network location working
backup to google account working. For those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
Changes v0.6
dualboot version available
some merges from S4 kernel, no changes in functionality
cwm update script doesn't format system anymore
libbt-vendor natively built instead copy from CM build. No change in functionality
Changes v0.5
Sdcard should now work (FAT32 at least, report exfat)
Sports Tracker doesn't crash UI when 'network' location provider isn't found
Changes v0.3 & 0.4
[*]Receiving calls fixed
Hanging up the call fixed
NFC doesn't crash on the background anymore, cannot test though
Bluetooth fixed, using lib from CM build
Changes v0.2
WiFi dhcp fixed
SuperSu included
init.d support
bash included
Bluetooth updates, but no full fix yet
Bugs v0.8
Whoa, are there any?
Bugs v0.7.1
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Bugs v0.6
Some problems with locations, network locaion isn't really enabled
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Backup account set to debug-only private cache for some users
Bugs v0.5
Some problems with locations
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Fixed Bugs
Sdcard doesn't mount
Cannot receive calls
Cannot hang up a call
WiFi connects, but doesn't get IP address
Bluetooth service fails at start, bluetooth doesn't work
NFC seems to be crashing on the background
no root as of yet
Source code
https://github.com/spegelius
Will be updating manifests and other stuff there when i figure a good way to get my changes there.
Oh and mods, if this fits the regular development section better, feel free to move it

A little incentive. Confirmation number: 1D974208B4414071D
I'll test and report. I'm on the GDE 4.2.2 port from Darkman now.

Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas

ohwarumbloss said:
Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas
Click to expand...
Click to collapse
Thanks for digging this stuff out. Some of those might be needed, i'l be adding them from CM repos one by one and testing how it works. I did another build, now adding Superuser to makefiles but still no go. Superuser does pop up after boot, telling su binary neds updating... Also added some init.rc scripts which are in CM build, but still no luck. After some digging, it seems that with 4.3, Google has made rooting bit more difficult. Root is my nr. 1 prio now, i'll need it to restore Titanium backups...
I've been using the rom few days now and it seems to work very well all in all. I had a camera hang yesterday, and after killing camera app it said Cannot connect to camera. Could get a logcat...

Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app

ohwarumbloss said:
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Well i have the Superuser app as embedded in the rom and when starting TB, logcat shows that su binary tries to start, but fails with error:
D/su ( 2213): su invoked.
D/su ( 2214): starting daemon client 10062 10062
E/su ( 2215): connect failed with 2: No such file or directory
E/o.gZ ( 1909): Root shell has terminated unexpectedly.
Did a search of the error and it seems that it's related to root setting in developer options. The problem is, there's no setting for root in there. Gonna have to do some diffing between CM and AOSP settings.
Haven't looked into the dhcp yet.

To get root working:
install SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Run in adb shell:
Code:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
I'm trying to get supersu integrated, but latest from github doesn't like to play ball. Maybe i'll just use the above release and integrate it... Koush's Superuser doesn't display the dialog for root access when using CM's version and latest from github didn't find some symbols.
Edit: use value 3 if you want to give root access to apps and adb

Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away

spegelius said:
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away
Click to expand...
Click to collapse
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?

mythi said:
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
Click to expand...
Click to collapse
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?

spegelius said:
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?
Click to expand...
Click to collapse
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..

mythi said:
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
Click to expand...
Click to collapse
Ok, could be. Don't know how ramdisk is created during build, have to look into it.
Also, found a quite major bug: cannot receive phone calls, at least i can't. That's kinda big problem, considering this is a phone still

Use dsixda kitchen to exreact the boot.img and view/edit its contents

mythi said:
Use dsixda kitchen to exreact the boot.img and view/edit its contents
Click to expand...
Click to collapse
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.

spegelius said:
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
Click to expand...
Click to collapse
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue

mythi said:
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue
Click to expand...
Click to collapse
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?

spegelius said:
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?
Click to expand...
Click to collapse
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue

mythi said:
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue
Click to expand...
Click to collapse
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...

spegelius said:
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
Click to expand...
Click to collapse
Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .
Sent from my GT-I9295 using Tapatalk

Don't give up!
Let me know if there's something I can do!
Saturday 95℅ free time if the weather doesn't turn to warm (bike is calling)
Sent from my GT-I9295 using xda app-developers app

How can I change camera shutter sound with root?

I overwrited shutter.ogg in system/media/ui but no change then i realized that i must change it in SamsungCamera.apk in priv-app directory. I opened it with apk editor and placed the file in res/raw directory and then repacked it then copied to priv-app directory but this time gave me error"application not installed" when i try to open camera app.Any solution you should offer?
Or how can I change system apps in priv-app directory
SM-A705FN cihazımdan Tapatalk kullanılarak gönderildi

I used this app with root to debloat:
https://labs.xda-developers.com/store/app/de.realvoxel.appmanager
I then added these to cscfeature.xml for my region:
<CscFeature_Framework_SupportDataModeSwitchGlobalAction>TRUE</CscFeature_Framework_SupportDataModeSwitchGlobalAction>
<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Common_DisablePhoneNumberFormatting>TRUE</CscFeature_Common_DisablePhoneNumberFormatting>
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
The last entry is what you're looking for specifically.
I uninstalled the device security apk. Disabling anti-malware
in the csc file removes an otherwise dead link from Device care.
You'll need to use omc decoder to decrypt your cscfeature.xml found here:
https://forum.xda-developers.com/android/software/decode-encode-omc-files-omc-decoder-t3791471/amp/
These are old tricks but still work
I used fx file manager to then overwrite the system file.
There's a Majisk module as well to remove camera sounds but i've not tried.
Interestingly, it appears Samsung tried to do the same with their phone connect/disconnect audio files in the UI folder... only to be trumped by their own apk.

[APP][MOD][V1] MIUI FM Radio APP (STEREO IMPROVEMENT, RDS show on notification, 76MHz-108MHz) for HMK20/MI9T

{
"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"
}
ROOT ACCESS NEEDED FOR SYSTEM APP REPLACEMENT.​YOU CAN DO IT THROUGH MAGISK, TWRP RECOVERY OR ROOT FILE MANAGER.​
-COMPATIBILITY TESTED-​
TESTED XIAOMI EU ROM 12.5 WEEKLY
21.2.24 version
21.2.3 version
21.1.28 version
21.1.20 version
-FEATURES-​
DISABLED FAULTY AF FUNCTION
IMPROVED STEREO BLENDING VALUES
RDS SHOW ON NOTIFICATION (ONLY AT THIS TIME)
FM BAND UNLOCK: 76 - 108 MHz
-HOW TO INSTALL-​
>MANUAL<​
FIRST OF ALL, PLEASE MAKE BACKUP OF THE ORIGINAL APK FILES!
COPY system/system_ext/app/FM/FM.apk
PLACE IT to the SD or computer storage
COPY system/app/MiRadio/MiRadio.apk
PLACE IT to the SD or computer storage
REPLACE under system/system_ext/app/FM/FM.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REPLACE under system/app/MiRadio/MiRadio.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REBOOT the system
>MAGISK<​
Instead of manually copying the files, it can be installed as Magisk module:​
Download the attached FM-Radio.zip
Do not unzip, leave as is
Open Magisk Manager, Modules tab, take Install from storage and point to the downloaded zip
Reboot
-HOW TO UNINSTALL-​
>MANUAL<​
RESTORE YOUR ORIGINAL BACKED UP APK FILES FROM SD OR COMPUTER' STORAGE
COPY original APK from SD or computer storage
REPLACE system/system_ext/app/FM/FM.apk with original APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
COPY original APK from SD or computer storage
REPLACE system/app/MiRadio/MiRadio.apk with original APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REBOOT the system
>MAGISK<​
Disable or uninstall MIUI FM Radio module
-SCREENSHOTS-​
Spoiler: SCREENSHOTS
-BUGS-​
PLEASE TELL YOU
-MOD DOWNLOAD-​
Spoiler: MODDED APKs DOWNLOAD
FM.apk
MiRadio.apk
Spoiler: MAGISK MOD ZIP DOWNLOAD
FM-Radio.zip
UNDER DEVELOPMENT, PLEASE BE PATIENT...

media1997 said:
YOU CAN DO IT THROUGH TWRP RECOVERY OR ROOT FILE MANAGER
-HOW TO INSTALL-
FIRST OF ALL, PLEASE MAKE BACKUP OF THE ORIGINAL APK FILES!
COPY system/system_ext/app/FM/FM.apk
PLACE IT TO THE SD OR COMPUTER STORAGE
COPY system/app/MiRadio/MiRadio.apk
PLACE IT TO THE SD OR COMPUTER STORAGE
REPLACE under system/system_ext/app/FM/FM.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REPLACE under system/app/MiRadio/MiRadio.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REBOOT THE SYSTEM
-HOW TO UNINSTALL-
RESTORE YOUR ORIGINAL BACKED UP APK FILES FROM SD OR COMPUTER' STORAGE
COPY ORIGINAL APK FROM SD OR COMPUTER STORAGE
REPLACE system/system_ext/app/FM/FM.apk with original APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
COPY ORIGINAL APK FROM SD OR COMPUTER STORAGE
REPLACE system/app/MiRadio/MiRadio.apk with original APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REBOOT THE SYSTEM
Click to expand...
Click to collapse
Instead of manually copying the files back and forth (prone to errors), it can be installed as Magisk module:
- download the attached FM-Radio.zip
- do not unzip, leave as is
- open Magisk Manager, Modules tab, take Install from storage and point to the downloaded zip
- reboot
To uninstall:
- disable or uninstall MIUI FM Radio module from Magisk Manager
Disclaimer:
I've only packed the developer's apk files to the Magisk module, to make installation (and uninstallation) easier.
Hence, don't ask me about the bugs
@media1997:
You can unzip to analyze the structure. You can easily see how your files are packed into the module and if needed, how can you release further improvements

@zgfg
Hi,
This was the fastest way for me to replace simply for the first time. I thought of a similar method later. Thank you for your help!

I'm trying to make this work on my Redmi Note 8 Pro in Lineage OS 18. I have exported the APKs from the MIUI rom which my current Lineage OS is built upon. There is a device /dev/fm and the firmware is also in place. However, the apks keep crashing and show as "false" without icon in tha app drawer. Installing through package installer results in online radio version (in Chinese). Any suggestion on how to debug? Do I have to spoof MIUI to make it work?

media1997 said:
-HOW TO INSTALL-​
>MANUAL<​
FIRST OF ALL, PLEASE MAKE BACKUP OF THE ORIGINAL APK FILES!
COPY system/system_ext/app/FM/FM.apk
PLACE IT to the SD or computer storage
COPY system/app/MiRadio/MiRadio.apk
PLACE IT to the SD or computer storage
REPLACE under system/system_ext/app/FM/FM.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REPLACE under system/app/MiRadio/MiRadio.apk with this mod APK file
GIVE IT chmod 644 permissions (-rw-r--r--)
REBOOT the system
Click to expand...
Click to collapse
Hello,
I tried to install on Magisk rooted 12.0.4.0 (QFJEUXM), but not working - both apk (FM.apk and MiRadio.apk) are in system/app folder
Thank for improving stock MIUI FM radio apk
Ideas for future updates:
-support resume audio (after watching YouTube video for example)
-support floating window (always active app)

The mod works also on the latest Xiaomi.eu weekly 2021.2.24 (A11)

imperfect said:
I'm trying to make this work on my Redmi Note 8 Pro in Lineage OS 18. I have exported the APKs from the MIUI rom which my current Lineage OS is built upon. There is a device /dev/fm and the firmware is also in place. However, the apks keep crashing and show as "false" without icon in tha app drawer. Installing through package installer results in online radio version (in Chinese). Any suggestion on how to debug? Do I have to spoof MIUI to make it work?
Click to expand...
Click to collapse
Hello, This may be caused by APK using the signature of the xiaomi.eu rom or framework dependecies. Maybe the qualcomm library be a little different? You can try to trace in adb logcat.

B^4g said:
Hello,
I tried to install on Magisk rooted 12.0.4.0 (QFJEUXM), but not working - both apk (FM.apk and MiRadio.apk) are in system/app folder
Thank for improving stock MIUI FM radio apk
Ideas for future updates:
-support resume audio (after watching YouTube video for example)
-support floating window (always active app)
Click to expand...
Click to collapse
Hi,
Probably because the apk is modded from the xiaomi.eu rom. This ROM' s system app signatures is different from the factory global/china rom. Good ideas, thank you for share it!

I never used that before... I was thing of expandine the frequency also UP so to get some airplanes... but anyway I wonder why it is MONO and 22050 hz when recorded.