Useful fixes for LineageOS 14.1
I am very glad that you are here!
It may be helpful to you:
__________________________________________________
Rollback to the official Android 4.1.2 without a PC
Today, we will roll back to the official android 4.1.2 without a PC, through custom recovery.
You need a phone S2-i9100 with the ability to enter into the recovery and installation of the zip file.
__________________________________________________
Restore the firmware on Samsung GT-I9100 Galaxy S II.
More detailed instructions on firmware with Odin.
__________________________________________________
[Guide/Tutorial] Installing LineageOS 14.1 + TWRP-3.1.0-0 for Samsung Galaxy S2 i9100
More detailed instructions on firmware with Odin.
__________________________________________________
Script remove the superuser indicator "#" !
Hello, I noticed that many of you don't like the superuser indicator ('#')
in the status bar and that some of you even flash SuperSU or Xposed, just to get rid of it.
Well, that's not necessary, because there is a much easier way.
__________________________________________________
Script fix Dialer for LineageOS !
- Has large photo of the caller
- Improved the display speed of the caller
- Enable call record (in test mode)
- In order to improve the quality of the recording of telephone conversations,
use a headset (headphones with microphone) !
__________________________________________________
Script fix CMFileManager for LineageOS !
If you have such a problem in the LOS!
"CMFileManager: not see the internal memory or it says that I need elevated rights to do..."
Root rights are recommended.
__________________________________________________
Script fix LockClock for LineageOS !
Weather widget clock with two assembly suppliers (OpenWeather and Yahoo weather).
__________________________________________________
Script fix Ril for LineageOS !
If you have such a problem in the LOS of 02/08, 02/13, 02/16 !
"Each time when I end a phonecall (no matter if it's incoming our outgoing calls)
I get a popping message that there is no reception, and the antenna shuts for about half a minute and then returns ..."
__________________________________________________
Root Addon Packages for Lineage OS!
Fixed the error 4, when installing addonsu-arm-signed.zip !
"addonsu-arm-signed.zip can't flash via recovery. Gives an error : Updater process ended with signal: 4 ..."
__________________________________________________
Download the scripts here__________________________________________________
Reserved...
Great job mate, thanks for the awesome fixes :good:
MigoMujahid said:
Great job mate, thanks for the awesome fixes :good:
Click to expand...
Click to collapse
Mutually, you also do many useful things!
You can also post useful fixes and additions here, just be sure to test them first!
LOS is constantly evolving, but with the advent of Innovations - appear flaws and inaccuracies!
I think our "Useful fixes for LineageOS 14.1" will serve for a long time and help all those who need it !
Thank you all...
@toy_story: Hi, can you please post the source code that need to be changed to enable call recording?
ale5000 said:
@toy_story: Hi, can you please post the source code that need to be changed to enable call recording?
Click to expand...
Click to collapse
Hello, I will write about the standard application Dialer.apk in CM and LOS.
In many countries, the recording of calls is prohibited by law. Google, SM, LOS and others, just protect themselves from trouble:
- They in the Dialer.apk application have installed filters for countries and mobile operators, who can be recorded and who can not.
- Changed the libraries and again the problem kernel.
Okay the lyrics aside, go to work, what needs to be done:
1) Unpack the firmware or copy from the already installed, but we have the file Dialer.apk.
2) Decompile Dialer.apk.
3) On the path: Dialer \ res \ values \ look for the file bools.xml
4) Using a text editor (preferably using Notepad ++ or something similar) open bools.xml
5) We search and check the line:
<Bool name = "call_recording_enabled"> true </ bool>
If instead of true it is written false ,change to true
6) Save the changes.
7) Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
Replace false with true
8) This line should be changed in all, from "values-mcc202" to "values-mcc505".
How many "values-mcc" , in so many countries is prohibited from recording a call!
Only after correcting all "values-mcc" , in the phone during the call to appear a choice for recording.
9) Compile (collect back) Dialer.apk
10) What to do with properly configured Dialer.apk, I think you know.
@toy_story: Thanks, do you know also a method to change the country detected by the phone?
Does it use the CSC?
If yes, can it be changed without change the ROM?
ale5000 said:
@toy_story: Thanks, do you know also a method to change the country detected by the phone?
Does it use the CSC?
If yes, can it be changed without change the ROM?
Click to expand...
Click to collapse
Hi, you could have done that before.
The record could be included by writing only 2 lines to the file "build.prop" or to install a suitable module for "Xposed"
Now if you take the application "dialer.apk" from LOS and from CM 13, it will be almost two different applications:
- change system libraries
- Enhance application security
- structure, location, and standard behavior
The control (check) is in 5 places, us for the time being limited to the easiest filter for the "MCC" country code.
And I think that a proven and well-working "Xposed" on android 7.1.? We will not see soon!
toy_story said:
Hi, you could have done that before.
The record could be included by writing only 2 lines to the file "build.prop" or to install a suitable module for "Xposed"
Now if you take the application "dialer.apk" from LOS and from CM 13, it will be almost two different applications:
- change system libraries
- Enhance application security
- structure, location, and standard behavior
The control (check) is in 5 places, us for the time being limited to the easiest filter for the "MCC" country code.
And I think that a proven and well-working "Xposed" on android 7.1.? We will not see soon!
Click to expand...
Click to collapse
I mean another thing.
I'm not sure but there should be another memory somewhere to flash.
Correct me if I'm wrong but doesn't CSC survive a format of the /system partition?
When you flash LineageOS it should read the country somewhere in the phone (I think) since the ROM is the same for all countries.
ale5000 said:
I mean another thing.
I'm not sure but there should be another memory somewhere to flash.
Correct me if I'm wrong but doesn't CSC survive a format of the /system partition?
When you flash LineageOS it should read the country somewhere in the phone (I think) since the ROM is the same for all countries.
Click to expand...
Click to collapse
Hi! No, you're wrong.
Yes, the disk is the same for all countries, but it already has different settings and behavior for different languages. Now when installing "LOS Pom" , the system automatically determines where we are (installation language), before this was not.
Behavior for countries is recorded in the form of a blacklist, according to the qualifications of "MCC" and "MNC".
MCC (Mobile Country Code) - the mobile country code in combination with MNC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
MNC (Mobile Network Code) - the mobile network code in combination with MCC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
Example:
Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
"Mcc202" - country code Greece
"Bools.hml" - with the parameter > false <
If we do not change to > true <
Then with this "POM" in the territory of Greece, the recording of the call will not work.
Previously, without modifying the "POM" workaround, the "modules" for "Xposed" were made.
toy_story said:
Hi! No, you're wrong.
Yes, the disk is the same for all countries, but it already has different settings and behavior for different languages. Now when installing "LOS Pom" , the system automatically determines where we are (installation language), before this was not.
Behavior for countries is recorded in the form of a blacklist, according to the qualifications of "MCC" and "MNC".
MCC (Mobile Country Code) - the mobile country code in combination with MNC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
MNC (Mobile Network Code) - the mobile network code in combination with MCC is the unique identifier of the cellular operator of GSM, CDMA, iDEN, TETRA and UMTS networks, as well as some satellite communication operators. ITU-T Recommendation E.212 defines mobile country codes.
Example:
Next on the path: Dialer \ res \ values-mcc202 \ open the file bools.xml and edit the line:
<Bool name = "call_recording_enabled"> false </ bool>
"Mcc202" - country code Greece
"Bools.hml" - with the parameter > false <
If we do not change to > true <
Then with this "POM" in the territory of Greece, the recording of the call will not work.
Previously, without modifying the "POM" workaround, the "modules" for "Xposed" were made.
Click to expand...
Click to collapse
I have installed it without SIM.
Before installation I have wiped system, data, cache (almost everything).
How can it detect country?
How can I verify what country is detected?
ale5000 said:
I have installed it without SIM.
Before installation I have wiped system, data, cache (almost everything).
How can it detect country?
How can I verify what country is detected?
Click to expand...
Click to collapse
Yes, I agree. Without a SIM card and without an Internet connection, applications will not determine in which country you are.
But you still insert a SIM card and will be connected to the Internet!
As soon as you insert the sim, the cellular operator will immediately tell your phone which country you are in.
Hi,
I just made a test with a fresh install of lineage-14.1-20170322-nightly-i9100-signed.zip, gapps pico with TWRP.
I installed Fix_addonsu-arm-signed.zip without errors, but the phone is still not rooted.
Any ideas what is going on?
As far as i remember last time i rooted it i had to use CWM-SuperSU-v0.97.zip too.
Thanks!
Edit: Please, ignore the above zzzz - i simply forgot to assign root rights to adb+apps in developer settings.
s2l9100 said:
Hi,
I just made a test with a fresh install of lineage-14.1-20170322-nightly-i9100-signed.zip, gapps pico with TWRP.
I installed Fix_addonsu-arm-signed.zip without errors, but the phone is still not rooted.
Any ideas what is going on?
As far as i remember last time i rooted it i had to use CWM-SuperSU-v0.97.zip too.
Thanks!
Click to expand...
Click to collapse
Follow the path:
Settings - Developer options - Root access - choose Apps and ABD
Check root access.
Restore the firmware on Samsung GT-I9100 Galaxy S II
More detailed instructions on firmware with Odin.
Script remove the superuser indicator "#" !
Script remove the superuser indicator "#" !
Hello,
I noticed that many of you don't like the superuser indicator ('#') in the status bar
and that some of you even flash SuperSU or Xposed, just to get rid of it.
Well, that's not necessary, because there is a much easier way.
So here is the "right way" to remove the "#":
Set in TWRP: Hide_SU_Icon.zip - Download
P.S. After the first power-up, you may need to reboot!
Disliked Returned back !
Set in TWRP: SU_Icon-REVERT.zip - Download
Script fix Dialer for LineageOS !
Script fix Dialer for LineageOS !
- Has large photo of the caller
- Improved the display speed of the caller
- Enable call record (in test mode)
- In order to improve the quality of the recording of telephone conversations, use a headset (headphones with microphone) !
Set in TWRP: Fix_Dialer.zip - Download
Be sure to "Wipe Cache / Dalvik"
If you see the message "Failed to start call recording" - do a reboot!
Disliked Returned back !
Set in TWRP: Dialer-REVERT.zip - Download
P.S.After installation, the phone briefly be slightly hotter than usual, this is due to the optimization of application.
Script fix CMFileManager for LineageOS !
Script fix CMFileManager for LineageOS !
If you have such a problem in the LOS!
"CMFileManager: not see the internal memory or it says that I need elevated rights to do..."
Root rights are recommended.
Set in TWRP: Fix_CMFileManager.zip - Download
Be sure to "Wipe Cache / Dalvik"
When you first start it may not see the folders, you need to reboot!
P.S. In nightie LOS from 02/26 before 03/29 deleted CMFileManager!
But the script still works well!
Script fix LockClock for LineageOS !
Script fix LockClock (version 3.5) for LineageOS !
Weather widget clock with two assembly suppliers (OpenWeather and Yahoo weather).
Set in TWRP: LockClock_LOS-mod.zip
Disliked Returned back !
Set in TWRP: LockClock_LOS-REVERT.zip
Wipe cache/dalvik after flash do not necessarily.
P.S. If you have installed my script "LockClock_LOS-mod.zip!" .
after upgrade LOS, even after the OTA,
it is necessary to again set in TWRP: LockClock_LOS-mod.zip!
Script fix Ril for LineageOS !
Script fix Ril for LineageOS !
If you have such a problem in the LOS of 02/08, 02/13, 02/16 !
"Each time when I end a phonecall (no matter if it's incoming our outgoing calls) I get a popping message that there is no reception, and the antenna shuts for about half a minute and then returns ..."
Set in TWRP: Fix_Ril - Download
Related
PoGo Ivy based on the work of elfinlazz & chuparCh0pper (special thanks to you guys!)
You can see your monsters iv and other stats as their nickname in the pgo app.
It doesn't actually change pokemon's nickname, only showing on app.
This does not use API, MITM or what ever red flagging action to server.
Feel free to use it.
I'm not responsible for any banned accounts or damaged devices, use at your own risk!
(Currently) not working with pgo v0.37.0, do NOT update until you are not forced to!
Features:
Can see IV, Level, localized Names and other stats in their nickname
Customizable string format(%NICK%, %NICK.#%, %LEV%, %LEV.#%, %IV%, %IV.P%, %IV.#%, %ATK%, %DEF%, %STA%)
Preview evolved CP/HP(nickname to evolving monster will show evolved CP/HP)
example: change nickname of Pikachu to Raichu and Pikachu's CP & HP values will change to evolved values
example2: change nickname of Bulbasaur to "EVO NEXT" and it shows Ivysaur stats, change to "EVO LAST" and it shows Venusaur stats
Optionally rename only favored monsters
Formats:
Nickname: %NICK% (shows the monsters name)
Nickname trimmed to # characters: %NICK.#% (eg. Bulbasaur: %NICK.5% -> Bulba)
Level: %LEV%
Level with # digits: %LEV.#% (eg. %LEV.2% -> 12.45 / %LEV.4% -> 12.4578)
IV: %IV%
IV left padded: %IV.P% (eg. 5 -> 005 / 78 -> 078)
IV with # digits: %IV.#% (eg. %IV.1% -> 89.3 / %IV.3% -> 89.361)
Attack (decimal): %ATK%
Attack (hex): %ATK.H% (eg. 15 -> F)
Defence (decimal): %DEF%
Defence (hex): %DEF.H% (eg. 15 -> F)
Stamina (decimal): %STA%
Stamina (hex): %STA.H% (eg. 15 -> F)
Candies needed to evolve: %CDY%
Fast move type: %FAST% (eg: Dragon, Normal...)
Fast move type abbreviation: %FAST.A% (eg: Dr, Ic ... Details)
Fast move typewith # digits:: %FAST.#% (eg. %FAST.3% -> Dra / %FAST.5% -> Drago)
Charge move type: %CHRG% (eg. Dragon, Normal...)
Charge move type abbreviation: %CHRG.A% (eg. Dr, Ic ... Details)
Charge move typewith # digits:: %CHRG.#% (eg. %CHRG.3% -> Dra / %CHRG.5% -> Drago)
Contribute your localized monster names
Feel free to contribute localized names for your language based on this pastebin, so i can add them in the next release.
Monster names currently implemented:
english
french
german
traditional chinese
Version History:
v1.0: Initial release
v1.1: Added formats %ATK.H%, %DEF.H%, %STA.H%
v1.2: Fix enable/disable functionality
v1.3: Fix unreadable preferences in MM (thanks to SGS5H @ xda for testing)
"Set custom format" now shows your format instead of default format
Add preview evolved monsters by manually changing nickname to "EVO NEXT" & "EVO LAST" (eg. Bulbasaur: EVO NEXT -> Ivysaur, EVO LAST -> Venusaur)
v1.4: Fix incorrect monster levels
Add feature to rename favored monsters only
Add formats %CDY%, %FAST%, %FAST.A%, %FAST.#%, %CHRG%, %CHRG.A%, %CHRG.#%
Switch to javalite protos (reduces apk size, multidex not needed anymore)
v1.5: Add missing movesets (should fix issues with %FAST... & %CHRG...)
Add traditional chinese localization (for monster names) (thanks to jerryh001 @ xda)
Download from xposed module repo:
http://repo.xposed.info/module/info.xposed.mirosz.pogoivy
Steps:
Install the module
Activate it in Xposed
Reboot
Run official pokemongo app
Enjoy
.
Can we have atk/def/sta available in hex as well as dec?
MrGodMan said:
Can we have atk/def/sta available in hex as well as dec?
Click to expand...
Click to collapse
show me an example please
mirosz said:
show me an example please
Click to expand...
Click to collapse
Instead of the atk using numbers 1 to 15 (decimal) it uses 1 to F (hexadecimal). This keeps the individual IVs as single characters for easier formatting.
eg a 15/12/5 Pokemon would show as F/C/5. This also has the advantage that you can remove the spacer character between each part.
PS, just installed app and it works good for me Thanks for keeping the app updated since elfinlazz seems to have stopped development.
mirosz said:
feel free to try my version and respond if its working for u or not, maybe we can fix it together
Click to expand...
Click to collapse
Hey, glad to see you are picking this project up. Unfortunately, the custom format still doesn't seem to do anything for me. Also, the preview text below "Set custom format" never changes to reflect the format I entered (it does change in the previous version of this module).
What's differences can you see between "ignore nicknamed pokemon" option when it's actived or not ?
Envoyé de mon SM-G935F en utilisant Tapatalk
crafty35a said:
Hey, glad to see you are picking this project up. Unfortunately, the custom format still doesn't seem to do anything for me. Also, the preview text below "Set custom format" never changes to reflect the format I entered (it does change in the previous version of this module).
Click to expand...
Click to collapse
The displayed text doesn't reflect what you have entered. Your changes are only visible in the edit field (after clicking "Set custom format")
What language and device are u using? please post the exact custom format u used.
nnrs1 said:
What's differences can you see between "ignore nicknamed pokemon" option when it's actived or not ?
Click to expand...
Click to collapse
if this option is enabled, the monsters you rename by hand on your own will not get overwritten by pogo ivy
MrGodMan said:
Instead of the atk using numbers 1 to 15 (decimal) it uses 1 to F (hexadecimal). This keeps the individual IVs as single characters for easier formatting.
eg a 15/12/5 Pokemon would show as F/C/5. This also has the advantage that you can remove the spacer character between each part.
PS, just installed app and it works good for me Thanks for keeping the app updated since elfinlazz seems to have stopped development.
Click to expand...
Click to collapse
thx, good to hear its working for u.
want upper or lower case?
mirosz said:
What language and device are u using? please post the exact custom format u used.
Click to expand...
Click to collapse
English, Nexus 5x, Pure Nexus rom. I even tried just setting the custom format to "%NICK%" but I still just get the default format in game.
mirosz said:
thx, good to hear its working for u.
want upper or lower case?
Click to expand...
Click to collapse
uppercase please
crafty35a said:
English, Nexus 5x, Pure Nexus rom. I even tried just setting the custom format to "%NICK%" but I still just get the default format in game.
Click to expand...
Click to collapse
which xposed version u using?
try to change devices language to french just to test if its language problem
edit:
ahh i think ive found the problem: https://github.com/rovo89/XposedBridge/issues/102
edit2:
try changing permissions like this using root browser:
/data/data/info.xposed.mirosz.pogoivy/shared_prefs/info.xposed.mirosz.pogoivy_preferences.xml -> 664
and
/data/data/info.xposed.mirosz.pogoivy/shared_prefs/ -> 755
mirosz said:
which xposed version u using?
try to change devices language to french just to test if its language problem
Click to expand...
Click to collapse
v86 -- French doesn't seem to help.
crafty35a said:
v86 -- French doesn't seem to help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68483222&postcount=10
^^ edit2
Doesn't seem to work. The file was already set to 664. I changed the folder to 755 and rebooted but still no luck.
crafty35a said:
Doesn't seem to work. The file was already set to 664. I changed the folder to 755 and rebooted but still no luck.
Click to expand...
Click to collapse
damn got a bootloop while testing a workaround
ok the last solution is to manually change the format in the preferences file :/
maybe there's a fix comming soon for xposed
Great Module so far. Thanks for your work!
mirosz said:
damn got a bootloop while testing a workaround
ok the last solution is to manually change the format in the preferences file :/
maybe there's a fix comming soon for xposed
Click to expand...
Click to collapse
The prefs file actually does contain my custom format, so I don't think that is the issue.
Thanks for updating this module I was wondering if the original was ever going to get updated again. I have one problem though when I disable the module within the POGO Ivy app it doesn't actually disable it for me. I can still see my IVs when I disable it.
TheJakee said:
Thanks for updating this module I was wondering if the original was ever going to get updated again. I have one problem though when I disable the module within the POGO Ivy app it doesn't actually disable it for me. I can still see my IVs when I disable it.
Click to expand...
Click to collapse
u need to restart pgo app, its not chnaged on-the-fly
mirosz said:
u need to restart pgo app, its not chnaged on-the-fly
Click to expand...
Click to collapse
I did restart it and nothing happened. Heck, I even restarted my whole phone and nothing happened. The Pokémon still had their IVs next to them.
I'm using the OnePlus 3 and everything worked fine in the old version.
TheJakee said:
I did restart it and nothing happened. Heck, I even restarted my whole phone and nothing happened. The Pokémon still had their IVs next to them.
I'm using the OnePlus 3 and everything worked fine in the old version.
Click to expand...
Click to collapse
Maybe you still have the old module active?
Based on latest KITKAT from @dsa8310.
Sharing with you my custom modified rom with KK image.
OPEN GAPS VERSION: DOWNLOAD 1024x600 and 800x480 image
To get root access, you have to type in Factory settings instead of 126 -> *#hct#root# and then ok (just once!).
UPDATE: 11.9.2017
openGaps version:
Lite 1024 x 600 openG version. Need testing!!!
- LITE version of system
- added xposed status bar module for remove status bar items (copy mtc-status bar to external GPS Card)
- new screen saver without null null text (if doesn't show install it manually from: system/app/mtcscreensaver)
- removed all the bloatware callendar, calculator etc...
- added new car launcher AG (trial) for me the best - full version 1€
- back to xposed mtc manager 1.13 module
- screen saver from @Malaysk
LITE VERSION OPTIMIZATIONS:
- kernel tweaks (changed parameters of dalvik vm etc,...)
- better ram management
- faster scrolling
- faster boot
- better responsiveness
- increased performance and app ram management
- better video acceleration
- disable sending android logging stuff
- force gpu&cpu rendering
PREINSTALLED APPS and MODULES:
All these apps and xposed modules are preinstalled and you just have to activate xposed modules you need:
- disable_service
- google-maps-9.2 (you can update it just install as normal apk)
- mtcservice-2.60
- mtcsound-2.0.5 (remove from xposed if you don't have sound mod for better performance)
- mtcxp-1.0
- quickreboot
- RootExplorer
- Titanium_Backup
- xposed-disablefullscreenkeyboard
- xposed-mtc-bt-2.3
- xposed-mtc-keys-5.2 (custom keys for harware buttons)
- xposed-mtc-manager-1.13 (mode button mod and no closing apps when starting the car, etc.)
- xposed-mtc-music-2.8
- xposed-mtc-poweramp-1.4 (working media keys and stopping power amp when mtc app is started)
- xposed-mtc-radio-1.11
- xposed-VolumeBar (replaces original volume bar)
- 7th floor sound mod preinstalled and working
OTHER ADDITIONS: (included in download to copy on external SD (GPS card)
There is also file to copy on SD card (GPS card) that has features for MTCManager:
- hardware mode button can be configured (included in download) as well to switch between apps and auto play them (radio, poweramp, music, pcradio etc)
- mtc screen clock
- mtc status bar
DISABLING THE SCREEN SAVER OR CHANGING TIME:
Edit on external SD/ GPS-Card : Mtc.Manager/settings.ini
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=false or true to activate
# Time off the screen if you do not set out full-time settings will be used in sec:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
MTC MANAGER CAPABILITIES:
capabilities
All configuration files must be on the external map in the mtc-manager directory.
1. The module carries the functionality of xposed-mcu , which does not allow the radio to go to sleep during the scrolling of the starter.
- when receiving a signal to turn off the module delays for 5 seconds, if at that moment the power reappears, nothing happens, in the absence of power, the radio recovers into sleep.
Due to the features of the implementation of the inclusion in our MCU, the screen goes out for the time of voltage failure.
This functionality can be disabled in settings.ini:
Settings.ini
Mcu_power = false
2. The module has a white list of applications that does not allow the system to close necessary services and applications when going to sleep and when pressing the "Acceleration" button in the blind. Thus, the module allows to refuse from using mtc-wakeup-service .
Filename with exceptions whitelist.ini
The file name of the white list application packages must be listed.
#
example
3. Accelerated start of user services. The services are started when the system kernel is loaded.
The list of services should be on the external map in the mtc-manager directory, the file name start_services.ini
each line should contain the service name in the format package name / full service name,
#
example
4. An alternative screensaver with a list of exceptions, running in any (even a non-standard application). The standard screen saver mechanism is activated.
It may not work on all firmware.
Settings in the settings.ini file.
Settings.ini
# Inclusion of an alternative screensaver, if false, the standard mechanism will work:
screenClock = true
# screen off time, if not specified, the value from the
default settings will be used: screenTimeout = 60
# screen saver program name
screenPackage = com.microntek.screenclock
# screen saver activation name
ScreenClass = MainActivity
# if the package name and activations are not specified, then the standard screensaver will be used
The exception list is located in the ss_exceptions.ini file - the package names must be listed, for example:
Ss_exceptions.ini
com.microntek.music
ru.yandex.yandexmaps
Also the screensaver will not start when talking on the phone, the rear view camera, navigation and turning off the radio.
If instead of a beautiful clock MTCSreenClock.apk a screensaver with a standard digital clock on a black background is called, you need to make sure that the MTCScreenClock application is installed.
If the application is installed, you can try setting screenPackage and screenClass parameters in settings.ini
5. Also in the module there is a "backup" for correct sound adjustment in MTC-Volume and MTC-Service .
#
The adjustment of sound in firmware on Android 4.4.4
6. Re-designation of OBD-device bluetooth.
Device names must be listed in the settings.ini file in obd_device parameter, separated by commas, in the form in which they are visible in the standard hands-free application. You can specify not names, but parts of names, for example:
Settings.ini
Obd_device = OBD, DUAL-SPP
7. Set the list of programs that are switched by the MODE button,
In settings.ini, set
Settings.ini
ModeSwitch = true
Programs are switched sequentially one after the other.
For correct sound switching, the applications used must be managed (play / pause) programmatically via intents. If the player does not support the start and stop playback of external intents, then you have to manually switch the sound.
When you click on the MODE button, the active application is searched for in the running list. Next, the application is sent a command (configurable in mode.ini) to close or pause the audio stream. After that, the default activation for the next application is launched and the application is sent a command to start playback (also configured in mode.ini)
#
Mode.ini
8. Disable the launch of the last running program.
Settings.ini
Clear_last_app = true
9. GPS time synchronization.
Settings.ini
Sync_gps_time = true
10. Turn on w-fi at startup.
Settings.ini
Wifi.on = true
Thank you Johnny! Love to see a lollipop version!
Hi Johny,
thx for sharing your custom Rom
Is this the openG or microG Version ?
Best regards
jun81 said:
Thank you Johnny! Love to see a lollipop version!
Click to expand...
Click to collapse
Working on it.
Do you guys prefer kikat or lollipop?
EagleSoldier said:
Hi Johny,
thx for sharing your custom Rom
Is this the openG or microG Version ?
Best regards
Click to expand...
Click to collapse
It's open gaps version because kitkat doesn't need micro g with 1 gb of ram. If someone else will be interested in MicroG I will give a try
personally lollipop works better..
jun81 said:
personally lollipop works better..
Click to expand...
Click to collapse
Done it, check the new thread.
thank you! gonna check it out!
I am waiting for the 800 x 480 Version to test it
EagleSoldier said:
I am waiting for the 800 x 480 Version to test it
Click to expand...
Click to collapse
Done, check it and report if screen saver is working
Johny DJ said:
Done, check it and report if screen saver is working
Click to expand...
Click to collapse
Awesome thanks
Will test it and report
Best regards
@Johny DJ
I've tested the ROM and everything is working well.
Screensaver don't work, I've activate the modules and placed the folders on GPS Card.
But the Screensaver don't appear.
To get root acsees , you have to type in Factorysetings instead of 126 -> *#hct#root# and then ok.
Overall a good ROM with some cool futures, hope you can fix the screensaver issue.
EagleSoldier said:
@Johny DJ
I've tested the ROM and everything is working well.
Screensaver don't work, I've activate the modules and placed the folders on GPS Card.
But the Screensaver don't appear.
To get root acsees , you have to type in Factorysetings instead of 126 -> *#hct#root# and then ok.
Overall a good ROM with some cool futures, hope you can fix the screensaver issue.
Click to expand...
Click to collapse
Yes you have to activate root once that's it.
Check folder mtc-manager on gps card called settings and change
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=true
# Time off the screen if you do not set out full-time settings will be used in sec: change this value to lower just to test:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
how long does it take to boot after initial flash? I been waiting like 20 minutes still on a black screen
Thanks @Johny DJ for sharing this ROM with us!
I installed and tested 800 x 480 version on my RK3188 unit. Most of the functions are working flawlessly. Noticed a couple of things that i wanted to let you know:
1) The bluetooth app appears out of scale on the screen. Number 0 in the dial pad is cut off, and the refresh button on the contacts is also not visible. Please have a look at the screenshots below:
https://ibb.co/cde7NQ
https://ibb.co/hwP7NQ
2) I'm quite new to xposed. I copied the folders to the SD card, but do i need to enable any modules for the screen saver to work properly ? The screensaver appears in the screen, but the speed indicator shows null.
https://ibb.co/bJ3Cp5
https://ibb.co/dL3dU5
Thanks !
gabesir said:
how long does it take to boot after initial flash? I been waiting like 20 minutes still on a black screen
Click to expand...
Click to collapse
same problem 1024x600
re download the file, flash again.. no boot logo just a black screen.
champikasam said:
Thanks @Johny DJ for sharing this ROM with us!
I installed and tested 800 x 480 version on my RK3188 unit. Most of the functions are working flawlessly. Noticed a couple of things that i wanted to let you know:
1) The bluetooth app appears out of scale on the screen. Number 0 in the dial pad is cut off, and the refresh button on the contacts is also not visible. Please have a look at the screenshots below:
https://ibb.co/cde7NQ
https://ibb.co/hwP7NQ
2) I'm quite new to xposed. I copied the folders to the SD card, but do i need to enable any modules for the screen saver to work properly ? The screensaver appears in the screen, but the speed indicator shows null.
https://ibb.co/bJ3Cp5
https://ibb.co/dL3dU5
Thanks !
Click to expand...
Click to collapse
1. Tnx for info, will correct tomorrow and upload update. I don't have 800 x 480 unit so I cannot test.
2. Yes you have to enable all the modules to get screen saver working properly.
gabesir said:
re download the file, flash again.. no boot logo just a black screen.
Click to expand...
Click to collapse
Hm... I didn't have problems on 1024 x 600, will check and update and also add screen saver tomorrow.
Johny DJ said:
Hm... I didn't have problems on 1024 x 600, will check and update and also add screen saver tomorrow.
Click to expand...
Click to collapse
Do you use my files from the firmware? Hmm ... you did not even write about it .... sad. I looked at the screenshots.
Malaysk said:
Do you use my files from the firmware? Hmm ... you did not even write about it .... sad. I looked at the screenshots.
Click to expand...
Click to collapse
I'm sorry yes, I used one, and I didn't write or mentioned yet because it's not working in other update I was planning to write if it will work, but I think it's related to your android settings so will not work on other image because it+s much more complex, that's why I didn't mentioned yet.
Based on latest LOLLIPOP with MICRO GAPS and OPEN GAPS 1024 x 600 and 800 x 480 from @dsa8310.
Sharing with you my custom modified rom with LP image.
UPDATE 29.8.2017:
MicroG version: 1024 x 600 and 800 x 480
- added screen saver with speed, clock and apps shortcut ported from well known developer @Malaysk (null null still present)
(if someone need: screen saver in the attachement - replace with root explorer: system - app - mtcscreenclock
MTCScreenClock (round)
- 1024 x 600 resolutions has different radio and bluetooth apk
- included all xposed modules and fast google maps
- remember to enable all xposed modules and copy folder contents to external gps card!!!
Enjoy
UPDATE: 3.9.2017 LINKS UP 2019
microGaps version:
Lite 1024x600 microG version.
openGaps version:
Lite 1024 x 600 openG version.
Lite 800 x 480 openG version.
___________________________________________________________________________________
- LITE version of system
- added xposed status bar module for remove status bar items (copy mtc-status bar to external GPS Card)
- new screen saver without null null text (if doesn't show install it manually from: system/app/mtcscreensaver)
- removed all the bloatware callendar, calculator etc...
- added a lot of tweaks to speed the units with 1gb ram
- added new car launcher AG (trial) for me the best - full version 1€
- new xposed mtc manager 2.5 module
LITE VERSION OPTIMIZATIONS:
- kernel tweaks (changed parameters of dalvik vm etc,...)
- better ram management
- faster scrolling
- faster boot
- better responsiveness
- increased performance and app ram management
- better video acceleration
- disable sending android logging stuff
- force gpu&cpu rendering
System now uses less than 470 Mb of ram
BEFORE YOU START:
1. With disable service app find google play store and disable the first 5 services from top including DailyHygiene.
2. Login to MicroG
3. In microG settings enable google device registration
4. Clear data on Google playstore or clear from recents
5. Enjoy fast 5.1.11. playstore (if not showing paid apps just restart HU)
MTCB MCU USERS
- DSA's mtcxp xposed module has to be enabled before the status bar will show.
PREINSTALLED APPS and MODULES:
All these apps and xposed modules are preinstalled and you just have to activate xposed modules you need:
- disable_service
- google-maps-9.2 (you can update it just install as normal apk)
- mtcservice-2.60
- mtcsound-2.0.5 (remove from xposed if you don't have sound mod for better performance)
- mtcxp-1.0
- quickreboot
- RootExplorer
- Titanium_Backup
- xposed-disablefullscreenkeyboard
- xposed-mtc-bt-2.3
- xposed-mtc-keys-5.2 (custom keys for harware buttons)
- xposed-mtc-manager-2.5 (mode button mod and no closing apps when starting the car, etc.)
- xposed-mtc-music-2.8
- xposed-mtc-poweramp-1.4 (working media keys and stopping power amp when mtc app is started)
- xposed-mtc-radio-1.11
- xposed-VolumeBar (replaces original volume bar)
- 7th floor sound mod preinstalled and working
OTHER ADDITIONS: (included in download to copy on external SD (GPS card)
There is also file to copy on SD card (GPS card) that has features for MTCManager:
- hardware mode button can be configured (included in download) as well to switch between apps and auto play them (radio, poweramp, music, pcradio etc)
- mtc screen clock
- mtc status bar
DISABLING THE SCREEN SAVER OR CHANGING TIME:
Edit on external SD/ GPS-Card : Mtc.Manager/settings.ini
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=false or true to activate
# Time off the screen if you do not set out full-time settings will be used in sec:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
MTC MANAGER CAPABILITIES:
capabilities
All configuration files must be on the external map in the mtc-manager directory.
1. The module carries the functionality of xposed-mcu , which does not allow the radio to go to sleep during the scrolling of the starter.
- when receiving a signal to turn off the module delays for 5 seconds, if at that moment the power reappears, nothing happens, in the absence of power, the radio recovers into sleep.
Due to the features of the implementation of the inclusion in our MCU, the screen goes out for the time of voltage failure.
This functionality can be disabled in settings.ini:
Settings.ini
Mcu_power = false
2. The module has a white list of applications that does not allow the system to close necessary services and applications when going to sleep and when pressing the "Acceleration" button in the blind. Thus, the module allows to refuse from using mtc-wakeup-service .
Filename with exceptions whitelist.ini
The file name of the white list application packages must be listed.
#
example
3. Accelerated start of user services. The services are started when the system kernel is loaded.
The list of services should be on the external map in the mtc-manager directory, the file name start_services.ini
each line should contain the service name in the format package name / full service name,
#
example
4. An alternative screensaver with a list of exceptions, running in any (even a non-standard application). The standard screen saver mechanism is activated.
It may not work on all firmware.
Settings in the settings.ini file.
Settings.ini
# Inclusion of an alternative screensaver, if false, the standard mechanism will work:
screenClock = true
# screen off time, if not specified, the value from the
default settings will be used: screenTimeout = 60
# screen saver program name
screenPackage = com.microntek.screenclock
# screen saver activation name
ScreenClass = MainActivity
# if the package name and activations are not specified, then the standard screensaver will be used
The exception list is located in the ss_exceptions.ini file - the package names must be listed, for example:
Ss_exceptions.ini
com.microntek.music
ru.yandex.yandexmaps
Also the screensaver will not start when talking on the phone, the rear view camera, navigation and turning off the radio.
If instead of a beautiful clock MTCSreenClock.apk a screensaver with a standard digital clock on a black background is called, you need to make sure that the MTCScreenClock application is installed.
If the application is installed, you can try setting screenPackage and screenClass parameters in settings.ini
5. Also in the module there is a "backup" for correct sound adjustment in MTC-Volume and MTC-Service .
#
The adjustment of sound in firmware on Android 4.4.4
6. Re-designation of OBD-device bluetooth.
Device names must be listed in the settings.ini file in obd_device parameter, separated by commas, in the form in which they are visible in the standard hands-free application. You can specify not names, but parts of names, for example:
Settings.ini
Obd_device = OBD, DUAL-SPP
7. Set the list of programs that are switched by the MODE button,
In settings.ini, set
Settings.ini
ModeSwitch = true
Programs are switched sequentially one after the other.
For correct sound switching, the applications used must be managed (play / pause) programmatically via intents. If the player does not support the start and stop playback of external intents, then you have to manually switch the sound.
When you click on the MODE button, the active application is searched for in the running list. Next, the application is sent a command (configurable in mode.ini) to close or pause the audio stream. After that, the default activation for the next application is launched and the application is sent a command to start playback (also configured in mode.ini)
#
Mode.ini
8. Disable the launch of the last running program.
Settings.ini
Clear_last_app = true
9. GPS time synchronization.
Settings.ini
Sync_gps_time = true
10. Turn on w-fi at startup.
Settings.ini
Wifi.on = true
Paypal:
https://paypal.me/johnydj?locale.x=en_US
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
grgart said:
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
Click to expand...
Click to collapse
Backup with titanium backup all your apps you want.
wipe data/factory reset from recovery, then flash the image with clear all
With titanium backup restore your apps back, thats it.
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
jun81 said:
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
Click to expand...
Click to collapse
1. Did you activate xposed mtc manager module in xposed app ?
2. Can you post picture, I didn't experienced this issue on my unit using the same image...
3. Please note this is 1024 x 600 resolution image...flashing on 800 x 480 can couse this issues you have...
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
jun81 said:
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
Click to expand...
Click to collapse
I added screen saver in latest version. But still don't know why you have problems with resolution. I can upload stock apps and you can try if there is also problem or not...
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
iselfdevi said:
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
Click to expand...
Click to collapse
Hard to say without knowing the exact version of his ROM youre running currently, but generally its a good idea to update the software as it is on any computer/smartphone/tablet. You shouldnt have to wipe data if youre already using it.
Read the thread to see the improvements that have been made recently - he lists them all.
Waiting for the 800 x 480 version !
champikasam said:
Waiting for the 800 x 480 version !
Click to expand...
Click to collapse
Done, check it out
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
champikasam said:
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
Click to expand...
Click to collapse
Full dropbox, check again...
Johny DJ said:
Full dropbox, check again...
Click to expand...
Click to collapse
Downloaded again. Same error
champikasam said:
Downloaded again. Same error
Click to expand...
Click to collapse
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Johny DJ said:
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Click to expand...
Click to collapse
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
champikasam said:
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
Click to expand...
Click to collapse
1. Hm...really don't know what happend to statusbar... try to disable / untick all xposed modules and reboot to see if some of xposed modules is cousing problems... I hope you did wipe all data / factory reset and then clear all and install from usb/sd and after that you can try wipe all data again and reboot, but everything should work because it's the same image from dsa's just added all the xposed modules...,
2. Yes, I forgot it, I updated image again and here: just copy folder in the rar with root explorer to system/app and change permisions just Maps.apk to r-r-w (664) reboot.
Try just to find your launcher in the android settings - apps and clear data.
Maps: https://www.dropbox.com/s/m44hv1189is36fr/Maps.rar?dl=0
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
airlink75 said:
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
Click to expand...
Click to collapse
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Johny DJ said:
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Click to expand...
Click to collapse
@Hal9k_'s MTCD ROM has a screen lock, I asked him how he did it and he said he just added back the original Android code.
EDIT : Lol, stupid me you said "lockclock" not screen lock ! Doh !
SailfishOS (SFOS) is a GNU+Linux system using libhybris to leverage Android drivers from LineageOS.
About everything should work (except NFC, no userspace support for now).
You're root and you've SSH, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build or newer,
and have booted it at least once (otherwise WLAN problems).
See latest release post for OTA update instructions, or flash ZIP download link.
Warning : flashing zip over previous SFOS install erases it ! So use OTA to avoid that, or use integrated backup app...
Note : SFOS only flashes boot partition and install itself in /data/.stowaways/sailfishos/ so :
you can go back to LineageOS only by flashing the LOS boot image
you can reclaim diskspace used SFOS by removing /data/.stowaways/sailfishos/
Reference Wiki page on merproject.org
Kernel | Device | Vendor source trees
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.).
This is not mandatory (though prefered for the full experience) : should you choose not to register (and even if you do),
you still can install an alternative store using OpenRepos client Storeman
Reserved
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
andrejchern said:
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
Click to expand...
Click to collapse
I have installated seilfish os some time ago in my moto g2 and the battery life and boot speed its superior then any version of android ... ?
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
tess1 said:
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
Click to expand...
Click to collapse
It's all politics, also it's the system I use daily
some sort of hommage to a french industry of old (1898), rough-rided by financialization (see, can't build idol3 themselves)
fighting planned obsolescence
taking the power back on a device
powering it with an OS independent from GAFAM
having closer to classical GNU+Linux distro, though not totally open in the case of SFOS
Since 2010 I've been a Nokia N900 then N9 user (which ran with Maemo, resp. Meego, predecessors to SailfishOS) until summer 2017 when I got a Xperia X for the SailfishX release. Only ever used Android for a month, until the build-SFOS-for-X documentation was released and dived in the OS-building fun...
At the beginning of 2018 I looked for a cheap and decent french-branded-androphone (2Gb RAM, HD display) with a working LineageOS port and found the idol3 to begin a new SFOS port. It's been a long 8 months journey, where rebuilding LineageOS if only for the patch-level was not much, then also wanted to "upstream" some fixes or upgrades (eg. kernel) I wanted in SFOS...
I started using my idol3 again and I love Sailfish OS as soon as I figure out android apps im gonna use it alot more
Everything work fine, but the double tap to wake up the telephone.
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Best regard.
Antonio from Italy.
vknecht said:
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it* and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
It's a systemd-based GNU/Linux with 32bits-userspace system, and about every basis function should work.
You're root, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build, and have booted it at least once (otherwise WLAN problems).
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.). This is not mandatory (though prefered for the full experience, for now) : should you choose not to register (and even if you do), you still can install an alternative store using OpenRepos client Storeman
*basic Anbox support was added, but don't count on it for now (plz contribute if you can), it may be broken.
If you really want to try it : (don't just copy/paste, fix the URLs !)
Code:
### As root (devel-su), on the phone via SSH :
# Add mal's Anbox for SFOS repository
ssu ar home_mal_anbox [url]http://repo.merproject.org/obs/home:/mal:/anbox/sailfish_latest_armv7hl/[/url]
pkcon refresh
pkcon install anbox-sailfishos anbox-sailfishos-image-mixed-32-64-bit
rm -f /var/lib/anbox/overlay/system/lib64/libGLESv*
cp /vendor/lib/egl/libEGL_adreno.so /var/lib/anbox/overlay/vendor/lib/egl/
# Install a keyboard APK, eg [url]https://f-droid.org/fr/packages/rkr.simplekeyboard.inputmethod/[/url]
mkdir -p /var/lib/anbox/data/app
cp *apk /var/lib/anbox/data/app
### Networking is broken at the moment... ###
### Comment anbox-bridge.sh lines (ExecStartPre and ExecStopPost) ###
### in /lib/systemd/system/anbox-container-manager.service ###
# Restart Anbox
systemctl restart anbox-container-manager
# There's no "back" button for now
# Run Anbox from app screen again to go back to Anbox app launcher
This is a simultaneous release of SFOS 2.2.1.18 and 3.0.0.8, if you have problem with one version, try the other
SFOS 2.2.1.18
SFOS 3.0.0.8
Sorry no screenshot or video for now, you can find for other devices, looks should be the same.
SailfishOS fir idol3 Wiki page
Kernel | Device | Vendor source trees
Click to expand...
Click to collapse
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
zorro_tj said:
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Click to expand...
Click to collapse
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
For donations, maybe it will be possible later.
h3cat3 said:
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
Click to expand...
Click to collapse
One thing I could do is try building LOS 14.1 with idol347 defconfig, but afaik it's not really working.
Otherwise one could follow the SailfishOS HADK using a working CyanogenMod base and I'd be glad to help, but don't have time to start it myself at the moment.
Thanks!
vknecht said:
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you. Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it? if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
zorro_tj said:
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you.
Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it?
if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
You're welcome For now I don't see any drain, let's hope it stays like this.
I found out that the ini file is not necessary if one sets tp_gesture_id to 2, but still have to set this value on boot
and/or find why it's not the same as in LineageOS by default.
3.0.1.11 release for idol3 is still in devel phase, once it's ready (~ one week or so) it will be published in testing phase and then you'll be able to do
OTA through commandline.
One can flash a devel-image, but then can't rely on OTA : will have to re-flash a testing-image or do risky/unsupported repository-switch.
Those are generally built using SailfishOS porters' Gitlab-CI group, latest being the 20190227 devel image
SailfishOS 3.0.1.11 beta3
Backup...
Update using OTA : the integrated graphical updater doesn't work for community ports
Easiest is to install sfos-upgrade either through Storeman or direct RPM dowload.
Flash image : (erases previously installed SailfishOS)
sailfishos-idol3-release-3.0.1.11-20190321-beta3.zip
Changes :
SailfishOS 3.0.1.11 release notes (points specific to officially supported devices don't apply)
Kernel : enabled Yama security module
Enabled doubletap to wake
Sorry, Anbox confirmed to NOT work, have to check required overlayfs support, maybe broken with the kernel updates.
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
andrejchern said:
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
Click to expand...
Click to collapse
Sorry to hear that... does it happen regularly/systematically and quite early after boot, or after (somehow) extensive usage, especially browser ?
I supposed you tried with flashing as well as OTA ?
A known cause for reboot is fixed in this build (and beta2 iirc) by an updated connman package ("rpm -qi connman" shows ip6tfix in version).
Maybe it's related to Yama security, will make a build without it...
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
andrejchern said:
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
Click to expand...
Click to collapse
Could you try flashing the ZIP inside the artifact from this devel build ?
It uses the same kernel as 3.0.0.8, ie. without yama, pstore and iirc RTC write support...
This build works fine, no reboots. Thanks.
SailfishOS 3.0.1.11 beta4
Update from any previous betas using OTA :
has to be done from commandline (on device or through SSH, USB prefered) since the graphical client in settings doesn't support community ports.
Code:
# Install sfos-upgrade package like this, or through Storeman
curl -O https://openrepos.net/sites/default/files/packages/5928/sfos-upgrade-2.4-1.noarch.rpm
devel-su
pkcon install-local sfos-upgrade-2.4-1.noarch.rpm
sfos-upgrade 3.0.1.11
reboot
# Patience, it takes an additional reboot to flash boot partition
# Go to commandline again and run :
devel-su post_sfos-upgrade
or install by flashing sailfishos-idol3-release-3.0.1.11-20190329-beta4.zip
(this replaces previously installed SailfishOS and SailfishOS-data, backup if needed)
Changes
Fall back to previous kernel
Hey mate, great job! Everything worked fine with sfos-upgrade from command line! Thanks a lot!!!
Just a question... I haven't prediction text, it's normal? Thanks again.
Antonio from Italy.
Carrier phones are odd-ball siblings of their global counterparts. As such, they do not enjoy nor receive the same level of support as that of the latter in the modding scene (custom ROMs, recoveries, etc.), even though both carry the same brand model name, e.g. Xperia XZ1 G8341 "Global" vs. Xperia XZ1 SO-01K "NTT DoCoMo". This is because of the subtle underlying hardware differences between the global and carrier variants, even if they have the same specsheet.
One can try flashing ROMs for a global variant onto one of these phones, but it can be a hit or miss, with some hardware components not working like NFC and even losing other functions like the fullseg receiver. And even if it seems to run fine, there may be other issues like poor battery performance because of a non-functioning hardware preventing deep sleep.
Given the above, if you're like me who has one of these carrier phones and doesn't mind running stock where everything works, then this guide is for you. This will allow you to customize several aspects of the system as indicated per section.
This guide has been made possible with the great work of @j4nn on his temproot exploit via CVE-2019-2215 here, extended to support carrier phones from NTT DoCoMo, au KDDI, and Softbank. Once you achieve temporary privilege escalation by running bindershell, you can execute the following commands from inside a terminal emulator (if you followed the howto from the link) or the adb shell. There is no need to setup Magisk. All changes are permanent, except for those in /data that will be erased upon factory reset.
Keep in mind the following:
1. Customizations in this guide were done on an Xperia XZ1 SO-01K from NTT DoCoMo. I think that the file system from the other carriers shouldn't differ that much, but let me know if there are any discrepancies and I'll see if I can help.
2. Make backup of the files if you wish to revert them later on.
3. Avoid making changes in files and/or directories other than those as detailed in this guide, specifically in /oem and /data.
4. The starting directory for files to be copied is assumed to be at /sdcard, i.e. the root directory of the internal storage.
5. Always remount as read-write before committing the changes in /oem:
Code:
# mount -o rw,remount /oem
6. Restart the phone for changes to take effect.
{
"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"
}
Let's get started.
• Boot animation
Shave off a few seconds of boot-up time by removing the boot animation, or you can replace this to whatever you want (you'll have to make sure that the boot animation is in compatible format with the phone). To remove:
Code:
# cd /oem/media
# rm bootanimation.zip
# touch bootanimation.zip
# chmod 644 bootanimation.zip
It is not enough that you delete the file, because then the system will load /system/media/bootanimation.zip. You need to create a zero-byte file with the proper permissions.
• Boot logo
I found an empty splash partition that is 32.64 MiB in size. I'm still trying to figure out if flashing a compatible boot splash image to this partition will make the bootloader load this image instead of the one built into it, just like in the case of the boot animation above. I still have to determine the compatible format for this splash image.
If you have further information regarding the format please share it here. I'm also trying to change the blinding light of that boot logo to something more tolerable.
• Emoji font
Fast fact: Did you know that emoji comes from the Japanese words 'e' meaning picture and 'moji' meaning character?
To replace (assuming you have a font file named MyFont.ttf):
Code:
# cd /oem/fonts
# rm ColorUniEmoji.ttf DcmColorIEmoji.ttf
# cp /sdcard/MyFont.ttf ColorUniEmoji.ttf
# chmod 644 ColorUniEmoji.ttf
The two ttf files are referenced in /system/etc/fonts.xml, but it is the ColorUniEmoji.ttf file that needs to be replaced to make changes to the system emoji. Removing this file will only defer the system to load all glyphs from /system/fonts/NotoColorEmoji.ttf, so rename your font file accordingly.
• Display font
To have your own font apart from the choices in Settings > Display > Change font for display (assuming you have a font file named MyFont.ttf):
Code:
# cp /sdcard/MyFont.ttf /data/system/fonts/UserFont.ttf
• Installing apps into /system
You can achieve the same effect of installing apps into /system (without triggering the 'Your device is corrupt' boot message) as follows (assuming you have an app named MyApp.apk):
Code:
# cd /oem/app
# mkdir MyApp
# chmod 755 MyApp
# cp /sdcard/MyApp.apk MyApp/
# chmod 644 MyApp/MyApp.apk
Replace /oem/app with /oem/priv-app as needed.
• Debloat
Effortlessly debloat your phone from carrier-specific apps and services by making modifications in /oem/android-config/early_config.xml. The package names contained in the xml file will disappear from the system upon restart. A factory reset will not even bring those packages back. You can remove the package names should you decide to have the need for them. Restart the phone and they will appear again.
Here's mine configured with the bare-minimum packages to avoid bootloops and other issues. You can change it to suit your needs, just follow the file structure. I purposefully didn't indent the lines I added to easily see them.
You can also rename or delete the folder /oem/deletable-app if you don't want to have those apps contained therein to be installed by the system upon a factory reset.
Note for SO-01K:
Do not include the com.nttdocomo.android.phonemotion package if you use the stock phone dialer com.sonymobile.android.dialer. The dialer will crash whenever you receive an incoming call, preventing you from answering it.
• GPS
UPDATE: The GPS doesn't work no matter what parameters are changed in the gps.conf file. It doesn't detect any satellites, so it doesn't lock-in on your coordinates, at least this is the case with mine. This may be another limitation of using a carrier-locked phone outside of it's country of origin. I'm afraid that the only remedy for this would be to flash a global ROM variant, especially if binaries are involved. I know this to be the case because I have an SOV37 on Japan ROM and no GPS work there also, but after flashing it to a Global ROM then I got GPS to work properly.
I'm still trying to find out how to fix this without unlocking the bootloader, but I'm not holding my breath.
Tweak the GPS parameters of the phone in /oem/android-config/gps.conf.
• Preset networks
Remove /oem/android-config/preset_networks.conf if you don't want to have carrier saved networks present whenever you reset your network settings or factory reset.
• APNs
I have always wondered why carrier phones don't automatically populate the APN for any SIM other than a Japanese SIM, even after having the phone SIM unlocked. As it turns out, the system of these phones doesn't really include the APN parameters of other networks outside Japan.
/system/etc/apns-conf.xml, which is where all APN parameters for all networks of the World can be found, is a symlink to /data/customization/apns-conf.xml, which itself is another symlink to /system/etc/customization/settings/defaults/apns-conf.xml, which is an xml file containing zero APN parameters.
As you can see, we can change this by replacing the symlink in /data/customization/apns-conf.xml with the full xml file from Google's source repository found here. This will download a file named apns-conf-full.txt. This is base64 encoded. To decode:
Code:
$ base64 -d /sdcard/Download/apns-conf-full.txt > /sdcard/apns-conf.xml
Unfortunately, upon every restart the system reverts /data/customization/apns-conf.xml to the original symlink. To prevent this, we need to make the file immutable with chattr, but this command is not available in the system.
If you followed the howto from the temproot link, and ran bindershell from a terminal emulator, you will come across the post of @Tifs detailing on how to successfully start Magisk from the same. You just need to download the arm64/busybox binary from one of the posted links.
When you have this and the xml files ready, then:
Code:
# cd /data/local/tmp
# cp /sdcard/Download/busybox .
# chmod +x busybox
# cd /data/customization
# rm apns-conf.xml
# cp /sdcard/apns-conf.xml .
# chmod 644 apns-conf.xml
# /data/local/tmp/busybox chattr +i apns-conf.xml
After restarting the phone, try Settings > Network & Internet > Mobile network > Access point names > Reset to default and see the available APNs for your SIM.
• VoWiFi / Wi-Fi calling
These carrier phones came provisioned with VoLTE and Video Calling but not Wi-Fi calling, at least in the case of mine. I'm not sure how useful Video Calling would be outside Japan, and it seems that Wi-Fi Calling is not used there. @pbarrette provided a great overview of the configs that enable VoLTE and Wi-Fi Calling here. But we are interested in enabling Wi-Fi Calling so here are the relevant changes to make:
1. Decompile /oem/overlay/com.android.carrierconfig-res-305.apk on your phone or PC.
2. Once decompiled, modify res/xml/vendor.xml with the following values as follows:
Code:
<boolean name="carrier_wfc_ims_available_bool" value="true" />
<boolean name="carrier_default_wfc_ims_enabled_bool" value="true" />
3. Rebuild the decompiled apk and overwrite the original file with the modified one.
4. Append the following line to /oem/system-properties/config.prop:
Code:
persist.data.iwlan.enable=true
5. It may be necessary to change/reinsert SIM after phone restart for the changes to take place.
• Build.prop
It is not possible to add or modify values in /system/build.prop without triggering the 'Your device is corrupt' boot message. However, you can add or modify certain values in /oem/system-properties/config.prop, which gets read into the system property database.
If you are using Gboard and you want custom themes for it, then you can append these lines for example:
Code:
ro.com.google.ime.themes_dir=/oem/etc/gboard_theme
ro.com.google.ime.theme_file=swiftinstaller.zip
Edit the values as needed.
Here are the other interesting values to modify:
Code:
# show the NFC icon
ro.nfc.icon.enable=true
# disable the forced camera shutter sound
ro.camera.sound.forced=0
It may also be necessary to decompile /oem/overlay/android-res-305.apk, then modify res/values/bools.xml as follows:
Code:
<bool name="config_camera_sound_forced">false</bool>
to turn off the forced camera shutter sound. I did both modifications, but try the config.prop value first. It may be enough.
* VoLTE / 4G calling
There should be a matching APN entry to use VoLTE with your network operator. Unfortunately, this is missing as well, and if you try to add it manually in Settings > Network & Internet > Mobile network > Access point names, it doesn't get saved. This is the case with mine.
UPDATE: I just acquired an Xperia XZ2 SOV37 "au KDDI" running Android 10. When I tried adding an APN of type 'ims' there, I got an 'Operator does not allow adding APNs of type dun, ims.' So it is a carrier-imposed restriction on the phone, only that in my XZ1 it fails silently.
You can add the APN entry in two locations:
1. /data/customization/apns-conf.xml, but you can only do this before making the file immutable; or
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
In both cases, this is the APN entry you need to add:
Code:
<apn carrier="IMS" apn="ims" mcc="{mcc}" mnc="{mnc}" type="ims" protocol="IPV4V6" roaming_protocol="IP" />
Replace the values in curly braces with the MCC and MNC of your network operator.
* CellBroadcastReceiver
Each carrier phone comes with their own way of receiving emergency alerts depending on the network operator. All of them however don't include the CellBroadcastReceiver app like the other models do.
If you want to receive such alerts, then download this apk here. Rename it as CellBroadcastReceiver.apk then do the following:
Code:
# cd /oem/priv-app
# mkdir CellBroadcastReceiver
# chmod 755 CellBroadcastReceiver
# cd CellBroadcastReceiver
# cp /sdcard/CellBroadcastReceiver.apk .
# chmod 644 CellBroadcastReceiver.apk
* Sound enhancement
Sound enhancements like the DSEE HX, ClearAudio+, etc. apply only on stock media players like the Music and Video player (but not on any other else it seems) in the case of Android 8.0 Oreo. On Android 9.0 Pie, these enhancements apply system-wide for all media playing apps. An upgrade is recommended if this customization is needed.
While customizations such as these may not come close to the level you get with custom ROMs (and the updated software and security that come with it), these will at least give you something to control and tweak AND STILL get a device with a locked bootloader (and all the goodies that come with it like passing SafetyNet and Key Attestations, Widevine L1, intact DRM keys, etc.). You get the best of both worlds, at the cost of running a not-so-updated system.
I will add more sections to this as soon as I made some more modifications. I hope you find this guide useful as much as I enjoyed creating it. If you do, please hit the LIKE button. It will be very much appreciated.
Changelog
* 2021-08-02: initial posting, revised with images
* 2021-08-03: added section on VoLTE
* 2021-08-04: updated VoLTE, added section on CellBroadcastReceiver
* 2021-08-11: updated GPS
* 2021-08-14: added section on Sound enhancement
braveheartleo said:
* VoLTE / 4G calling
There should be a matching APN entry to use VoLTE with your network operator. Unfortunately, this is missing as well, and if you try to add it manually in Settings > Network & Internet > Mobile network > Access point names, it doesn't get saved. This is the case with mine.
UPDATE: I just acquired an Xperia XZ2 SOV37 "au KDDI" running Android 10. When I tried adding an APN of type 'ims' there, I got an 'Operator does not allow adding APNs of type dun, ims.' So it is a carrier-imposed restriction on the phone, only that in my XZ1 it fails silently.
You can add the APN entry in two locations:
1. /data/customization/apns-conf.xml, but you can only do this before making the file immutable; or
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
In both cases, this is the APN entry you need to add:
Code:
<apn carrier="IMS" apn="ims" mcc="{mcc}" mnc="{mnc}" type="ims" protocol="IPV4V6" roaming_protocol="IP" />
Replace the values in curly braces with the MCC and MNC of your network operator.
Click to expand...
Click to collapse
braveheartleo
Thanks a lot for such a helpful post.
I have a SO-02K XZ2 Compact docomo, running android 9.0, unlocked bootloader, rooted.
I could not find file "apns-conf.xml" on "/system/etc/".
After rebuilding "android-res-305.apk" ... each time i tried to manually add APN (through Newtrok & internet > Mobile network > Advanced > Access Point Names) i end up with no APNs.
what could be wrong?
shamllakh said:
After rebuilding "android-res-305.apk" ... each time i tried to manually add APN (through Newtrok & internet > Mobile network > Advanced > Access Point Names) i end up with no APNs.
Click to expand...
Click to collapse
Hi, sorry for the very late reply, I must have missed the notification for this one.
If you read my post carefully, then you would have already gotten the answer to your question.
I'm not sure what you did after rebuilding the file, but if you followed my post correctly then you wouldn't have the need to manually add an APN entry for VoLTE, which doesn't get saved.
@braveheartleo regarding 4g/volte I tried to modify the apns-conf.xml. I managed to have ims registered but for some reason, after a while it reverts back to not registered even though i made it immutable. I would like to try the other way by decompiling android resapk but I don't know how to. Do you mind sharing a basic guide and the pre requisites. I tried recompiling in windows using apktool and I don't know if I'm doing it right, I didn't see any res folder after inside. I tried the apk tool on the go but I'm not lucky to have it installed, I think the development of the app has stopped years ago. I have sov36 so I am also thinking maybe it's deferent on how you do it compare to softbank?
braveheartleo said:
2. /oem/overlay/android-res-305.apk, by decompiling it and then modifying res/xml/apns.xml, rebuild and then overwrite with this one. I went this route.
Click to expand...
Click to collapse
@braveheartleo I managed to decompile android-res-305.apk but there is no res folder or apns.xml on it for sov36 au. I tried to look onto the same apk for s0-01k and it is present. I guess docomo build their firmware a bit different than kddi au. I tried modifying apns-conf.xml and i get ims registered but i still can't make calls. And after a while it reverts back to not registered even after making it immutable.
braveheartleo said:
• Debloat
Click to expand...
Click to collapse
I also want to add that they can easily debloat by flashing global rom and still have temp root. It worked on my xz1 au/sov36.
nitrams said:
I also want to add that they can easily debloat by flashing global rom and still have temp root. It worked on my xz1 au/sov36.
Click to expand...
Click to collapse
I just want to point that flashing global rom will loose the volte. But I have found a solution for that or maybe others already knew about it. By modifying oem/system-properties/config.prop and adding these lines and not justnthe volte but it will also activate wifi calling and video calling.
persist.data.iwlan.enable=true
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.data.iwlan=1
persist.data.iwlan.ipsec.ap=1
persist.radio.volte.dan_support=true
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.radio.VT_ENABLE=1
persist.sys.cust.lte_config=true
persist.rcs.supported=1
But still, im unlucky to have my carrier's volte work for me.
GitHub - edgd1er/voenabler: voenabler
voenabler. Contribute to edgd1er/voenabler development by creating an account on GitHub.
github.com