Related
hi how can we customize android on first boot. ie change settings to how we want, like enable data roaming, wifi settings. can this be done in a script in init.d folder? lots of settings are in databases so how can we change the values in them
richmondo said:
hi how can we customize android on first boot. ie change settings to how we want, like enable data roaming, wifi settings. can this be done in a script in init.d folder? lots of settings are in databases so how can we change the values in them
Click to expand...
Click to collapse
Some things can be changed in /system/build.prop
Others in the init.rc and init.devicenamehere.rc, which are in the ramdisk. And some ROMs do have a init.d/*, but that's not standard AOSP.
Are you trying to change a running ROM or customize one for flashing?
For flashing a new own customized rom, how we can made roms, have ap2sd??? ( should we add anything special??
How can we add some new languages to rom..??
I need to add Arabic - persian just for supporting the characters but when I ad fonts to rom, it just shows them disconnected.. how can I fix this..??
.
RichmondoUK said:
hi how can we customize android on first boot. ie change settings to how we want, like enable data roaming, wifi settings. can this be done in a script in init.d folder? lots of settings are in databases so how can we change the values in them
Click to expand...
Click to collapse
<bool name="def_enable_mobile_data">true</bool> change <bool name="def_enable_mobile_data">false</bool> Data transfer is disabled by default.
<bool name="def_install_non_market_apps">false</bool> change <bool name="def_install_non_market_apps">true</bool> Checkbox Unknown sources in Settings \ Security will be marked for easy installation of necessary software.
Lol thanks but this is basic now compared to what i do now as currently work on the xtended settings app.
It occurred to me that as we need to flash the wi-fi modules zip via CWM in any ROM we choose to use when we marry it with a new kernel, it might be handy to create single "flash packs" containing these modules plus other useful JB tweaks. I have been actively monitoring ROM threads (FXP, AOKP and PACman particularly) and come up with some selections that I like to use as a starter. This is a personal choice, feel free to amend as you see fit to meet your own needs, or more importantly add your own for others to benefit from.
None of this is my work per se, I have simply compiled the efforts of others into single one-shot files in an effort to stop my SD card getting any more cluttered than it already is!
TWEAKS UPDATE 01/12/2012
AOKP
AOKP JB Milestone 1 and FlyKernel v0.3
AOKP JB Milestone 1 and kernel from PAC v16.1.0 alpha
AOKP JB Milestone 1 and kernel from PAC v17.0.0
AOKP JB Milestone 1 - Not kernel specific, no Wi-Fi modules
CM10 FXP
CM10 FXP145 and FlyKernel v0.3
CM10 FXP145 and kernel from PAC v16.1.0 alpha
CM10 FXP146 and FlyKernel v0.3
CM10 FXP146 and kernel from PAC v16.1.0 alpha
CM10 FXP146 and kernel from PAC v17.0.0
CM10 FXP145/ 146 - Not kernel specific, no Wi-Fi modules
MIUI
MIUI JB 2.11.9 and kernel from PAC v16.1.0 alpha
MIUI JB 2.11.9 and kernel from PAC v17.0.0
MIUI JB 2.11.9 - Not kernel specific, no Wi-Fi modules
PAC
PAC v16.1.0 alpha/ v17.0.0 and FlyKernel v0.3
PAC v16.1.0 alpha/ v17.0.0 - Not kernel specific, no Wi-Fi modules
Please note: All the files and build.prop tweaks are integrated into the /system of the ROM when you use a FlashPack. Consequently, they are not deleted if you do a wipe data/ factory reset, wipe cache or wipe dalvik cache after you have installed it. So, if you want to use a different kernel with the SAME ROM you DO NOT need use another FlashPack... The files and tweaks will still be on your phone, you simply need to flash the Wi-Fi modules ONLY for the new kernel.
WI-FI SLEEP AND FRONT CAMERA FIXES
Click Here
FILE SPECIFIC KERNEL WI-FI MODULES
FlyKernel v0.3
FlyKernel v0.4
FlyKernel v0.5
FlyKernel v0.5a
FlyKernel v0.6
FlyKernel v0.7a
FlyKernel v0.8
FlyKernel v0.8fix
PAC v16.1.0
PAC v17.0.0
PAC v18.0.0
LINKS TO ORIGINAL ROM AND KERNEL THREADS
{RAY}[DEVELOPMENT] - CM10 - FreeXperia Project
[WIP][ROM][JB 4.1.2][P?+Aokp+Cm] P.A.C All in 1 ROM !!!!!! Jellybean alpha v16 5/11
[AOKP][JB] Xperia Ray - KangXperiaProject - [milestone 1]
[ROM] MIUI Jelly Bean 2.11.9 for Sony Xperia Ray
[FlyKernel][JB][4 November]Flykernel JellyBean 0.3 - OC/UV, SLQB, TinyRCU etc.
☠ [APK][Tweaks & Mods] █ PIMP MY ROM █ v2.1 {Any Device // Any Rom}[ALPHA][WIP] ☠
CM10 FXP145 and FlyKernel v0.3
I have started the thread off with flash packs SPECIFICALLY designed to be used with FlyKernel v0.3 when married to FXP145 CM10, some of the elements may already be included in other ROMs or might prove incompatible in other combinations.
The linked folder contains;
FlashPack_v2
FlyKernel v0.3 Wi-Fi Modules
Bravia Engine
xLoud Engine
Xperia S Keyboard
Build prop tweaks - for battery
Build prop tweaks - Media Stage Fright for video playing
Build prop tweaks - Net TCP buffersize optimisation for better downloading
There is already a line in FXP145 buildprop for wifi.supplicant_scan_interval=15. This is superseded by the value in the build prop tweaks for battery. You should remove the original line after installing either flash pack.
The text file is included for reference and shows what lines are added to the build prop by a script in the zip file.
The keyboard is available in many threads though thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, thomas1991_12 for his excellent kernel, and of course the FXP team for all they have done.
I want to download, but I have to make an account at 4shared ;S
Also in order to avoid unnecessary questions, you should explain in a little more depth how to delete the line from build.prop.
xzeiP said:
I want to download, but I have to make an account at 4shared ;S
Also in order to avoid unnecessary questions, you should explain in a little more depth how to delete the line from build.prop.
Click to expand...
Click to collapse
Use root explorer. Go into system. Hit once Mount R/W button to change R/O. If you press long on build.prop, then a list appers, chose "edit with text editor". Delete suggested line. Exit (It ask you to overwright current build.prop, and creates build.prop.bak) Hit again R/O to change back R/W exit root explorer, restart your phone to changes take effect.
The files are too big to attach as zip files I'm afraid. 4shared is free and seems as good as any file sharing site, I don't really want to mirror unless there is a big problem.
Sent from my Xperia Ray using xda app-developers app
Will we really get bravia engine I've read numerous threads saying it's impossible on custom roms
gavster26 said:
Will we really get bravia engine I've read numerous threads saying it's impossible on custom roms
Click to expand...
Click to collapse
I made it, i don't know if it works, i don't feel any difference. But some users do.
Make a backup, try it, and if you think it's not working, then you can use the remover zips from this post Don't forget to delet build.prop lines after remove!
Edit: see sgs3 thread with custom rom and xLoud and Bravia engine.
If you don't mind me adding a bit of tweaking I have done myself to my phone after setting it up (do not apply these if you have no clue what you are doing):
1. Changing governor and scheduler
Settings->Performance->Processor->CPU governor->SmartassV2
Settings->Performance->Processor->CPU governor->Set on boot (checked)
Settings->Performance->Processor->I/O scheduler->I/O schedulor->noop
Settings->Performance->Processor->I/O scheduler->Set on boot (checked)
Settings->Performance->Memory management->zRAM-> 18%
Settings->Performance->Memory management->Allow purging of assets (checked)
2. Disabling unused apps
I disable the following apps by going into Settings->Apps->All, then clicking on the app and then finally pressing disable.
Disabling of these apps removes functionality, however, if you are like me and do not use voice related apps and prefer the gmail app, then you should not feel a change, except for more multitasking.
CM Updater
Picasa Uploader
Talk
Google Search
Google Partner Setup
Google text-to-speech E
Pico TTS
TalkBack
Voice Dialler
Email (if you use Gmail)
Exchange Services (if you use Gmail)
Android keyboard (AOSP) if you use Xperia keyboard
Themes provider
Browser (I use dolphin mini)
ANT radio service (I cannot get radio to work)
3. Disable persistent search bar
Settings->Launcher->Homescreen->Search bar (UNcheck)
4. Use 3 homescreens
Settings->Launcher->Homescreen->Homescreens->3
Settings->Launcher->Homescreen->Default screen->2
I hope that you will get just a bit more juice out of your JB with these tweaks.
Daniel_GT said:
I have started the thread off with flash packs SPECIFICALLY designed to be used with FlyKernel v0.3 when married to FXP145 CM10, some of the elements may already be included in other ROMs or might prove incompatible in other combinations.
The linked folder contains;
FlashPack_v1
FlyKernel v0.3 Wi-Fi Modules
Bravia Engine
xLoud Engine
Xperia S Keyboard
Build prop tweaks - for battery
There is already a line in FXP145 buildprop for wifi.supplicant_scan_interval=15. This is superseded by the value in the build prop tweaks for battery. You should remove the original line after installing either flash pack.
FlashPack_v2
As v1, plus;
Build prop tweaks - Media Stage Fright for video playing
Build prop tweaks - Net TCP buffersize optimisation for better downloading
The text files are included for reference and show what lines are added to the build prop by a script in the zip file.
The keyboard is available in many threads though thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, thomas1991_12 for his excellent kernel, and of course the FXP team for all they have done.
Click to expand...
Click to collapse
Swiched from kernel found in original FXP 145 to flykernel V0.3. Flashed FlashPack v2. Will report results after one day of use.
Questins:
1. Is Bravia engine enabled or i have to enable it in the menus? And what exactly does it do? Better colors?
2. For X loud engine same question as for Bravia engine.
3. Had some Xperia keyboard installed, after flashing i have same keyboard, i would assume that they were the same? I had Xperia_S_ICS_Keyboard, that is the file name, but cant remember where did I found it.
4. What is media stage fright?
Thank you in advance and thank you for this flashpacks!
shubri said:
Swiched from kernel found in original FXP 145 to flykernel V0.3. Flashed FlashPack v2. Will report results after one day of use.
Questins:
1. Is Bravia engine enabled or i have to enable it in the menus? And what exactly does it do? Better colors?
2. For X loud engine same question as for Bravia engine.
3. Had some Xperia keyboard installed, after flashing i have same keyboard, i would assume that they were the same? I had Xperia_S_ICS_Keyboard, that is the file name, but cant remember where did I found it.
4. What is media stage fright?
Thank you in advance and thank you for this flashpacks!
Click to expand...
Click to collapse
Bravia and xLoud is always on. I can't edit FXP or PAC settings.apk to make it on/off (i dont't know what to edit in smali files)
media stage frigt is for video wieving. many users reported, that mkv, mp4, etc video files casusing FC, and the phone restarts. I tested this lines and didn't have any problems with mp4 and mkv files.
Build.prop tests and results: #1196
mkv file reference: #1340
mp4 file reference: #1262
shubri said:
Swiched from kernel found in original FXP 145 to flykernel V0.3. Flashed FlashPack v2. Will report results after one day of use.
Questins:
1. Is Bravia engine enabled or i have to enable it in the menus? And what exactly does it do? Better colors?
2. For X loud engine same question as for Bravia engine.
3. Had some Xperia keyboard installed, after flashing i have same keyboard, i would assume that they were the same? I had Xperia_S_ICS_Keyboard, that is the file name, but cant remember where did I found it.
4. What is media stage fright?
Thank you in advance and thank you for this flashpacks!
Click to expand...
Click to collapse
In reply;
1 & 2. Please refer to this and subsequent posts in the PAC thread. There is no setting to change, they are permanently enabled.
3. That's the same one.
4. Existing system features enabled by the build prop tweaks. For a fuller description do a search, there are lots of posts with more detail/ alternatives, this one for example.
PAC v16.1.0 alpha/ v17.0.0 and FlyKernel v0.3 (UPDATED 13/11/2012)
FlashPack SPECIFICALLY designed to be used with FlyKernel v0.3 when married to PAC v16.1.0 alpha/ v17.0.0, some of the elements may already be included in other ROMs or might prove incompatible in other combinations.
The attached file contains;
FlashPack_v3.1
FlyKernel v0.3 Wi-Fi Modules
Bravia Engine
xLoud Engine
Set configuration to PhoneUI
Build prop tweaks - for battery
The text file is included for reference and shows what lines are added to the build prop by a script in the zip file.
Thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, pluGinSz for the config settings, thomas1991_12 for his excellent kernel, and of course szl.kiev for all he has done.
CM10 FXP145 and kernel from PAC v16.1.0 alpha
FlashPack SPECIFICALLY designed to be used with kernel from PAC v16.1.0 alpha when married to CM10 FXP145, some of the elements may already be included in other ROMs or might prove incompatible in other combinations.
The linked folder contains;
FlashPack_v4
PAC v16.1.0 alpha Wi-Fi Modules
Bravia Engine
xLoud Engine
Xperia S Keyboard
Build prop tweaks - for battery
Build prop tweaks - Media Stage Fright for video playing
Build prop tweaks - Net TCP buffersize optimisation for better downloading
There is already a line in FXP145 buildprop for wifi.supplicant_scan_interval=15. This is superceded by the value in the build prop tweaks for battery. You should remove the original line with a root explorer (such as ES) after installing the flash pack.
The text file is included for reference and show what lines are added to the build prop by a script in the zip file.
The keyboard is available in many threads though thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, szl.kiev for his excellent kernel, and of course the FXP team for all they have done.
Is this xs keyboard thee same as the rest because the one iI havee garbles and dissaperss when I type on a browser
gavster26 said:
Is this xs keyboard thee same as the rest because the one iI havee garbles and dissaperss when I type on a browser
Click to expand...
Click to collapse
The one included here is the S keyboard and is very stable. I've had no trouble with it at all.
Sent from my Xperia Ray using xda app-developers app
PAC v16.1.0 alpha/ v17.0.0 - Not kernel specific, no Wi-Fi modules (UPDTD 13/11/2012)
FlashPack designed to be used with PAC v16.1.0 alpha/ v17.0.0. This version is not kernel specific and does not contain Wi-Fi modules.
The attached file contains;
FlashPack_v5
Bravia Engine
xLoud Engine
Set configuration to PhoneUI
Build prop tweaks - for battery
The text file is included for reference and shows what lines are added to the build prop by a script in the zip file.
Thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, pluGinSz for the config settings and of course szl.kiev for all he has done.
AOKP JB Milestone 1 or CM10 FXP145/ 146 - Not kernel specific, no Wi-Fi modules
UPDATED 11/11/2012
FlashPack designed to be used with AOKP JB Milestone 1 or CM10 FXP145/ 146. This version is not kernel specific and does not contain Wi-Fi modules.
The linked folder contains;
FlashPack_v6
Bravia Engine
xLoud Engine
Xperia S Keyboard
Build prop tweaks - for battery
Build prop tweaks - Media Stage Fright for video playing
Build prop tweaks - Net TCP buffersize optimisation for better downloading
There is already a line in AOKP JB Milestone 1 or FXP145/ 146 buildprop for wifi.supplicant_scan_interval=15. This is superceded by the value in the build prop tweaks for battery. You should remove the original line with a root explorer (such as ES) after installing the flash pack.
The text file is included for reference and shows what lines are added to the build prop by a script in the zip file.
The keyboard is available in many threads though thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, and of course championswimmer, and the FXP team for all they have done.
MIUI JB 2.11.9 and kernel from PAC v16.1.0 alpha
FlashPack SPECIFICALLY designed to be used with kernel from PAC v16.1.0 alpha when married to MIUI JB 2.11.9, some of the elements may already be included in other ROMs or might prove incompatible in other combinations.
The linked folder contains;
FlashPack_v7
PAC v16.1.0 alpha Wi-Fi Modules
Bravia Engine
xLoud Engine
Xperia S Keyboard
Build prop tweaks - for battery
Build prop tweaks - Media Stage Fright for video playing
Build prop tweaks - Net TCP buffersize optimisation for better downloading
There is already a line in MIUI buildprop for wifi.supplicant_scan_interval=60. This is superceded by the value in the build prop tweaks for battery. You should remove the original line with a root explorer (such as ES) after installing the flash pack.
The text file is included for reference and show what lines are added to the build prop by a script in the zip file.
The keyboard is available in many threads though thanks and acknowledgement goes particularly to Wechy77 for the engines and all the build prop tweaks, I refer you to his threads for fuller explanations of each element, szl.kiev for his excellent kernel, and of course thetrisatria for all he has done.
Looking forward to FXP146 fix.
146 is out
Ok we have new version out, i think that kernel included is the same as for 145, concluded this from the same size of it.
Someone reported that flykernel v 0.3 is working with it as long as u flash wi fi modules.
Anyway:
Will there be changes to flykernel, shall we expect v 0.4?
And new version of flashpack for flykernel married with 146?
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
Are there any build.prop or system.prop edits to add preferred network options entries or and changes to add in device tree as I want to compile rom for my device g4 plus but all the roms have only 3g and lte of course *#*#4636#*#* is a workaround But I want to have it in the system settings.
Hi, there!
Now that we can use Project Croissant to get ChromeOS running or non-Chromebook devices, what is missing is a better kernel for improved compatibility.
Thanks to the threads by @nabil2000 I was able to successfully build a chromeos-4.14 kernel that boots on my test device (Lenovo MIIX320-10ICR - Z8350 processor) using a CONFIG from FydeOS 5.31 with most hardware enabled (WiFi, Bluetooth, sound), but it has the same issue as latest ATB builds: it freezes after a while. This doesn't happen with latest FydeOS or CloudReady builds (CloudReady bought FlintOS so I guess they are using some of their code now), so my guess if that their kernels have some patches that aren't included in the Chromium git. FydeOS is open-sourced only for RaspberryPi and TinkerBoard, there are no sources available for the PC or VMWare versions (PC version is not open source as many say, so be aware).
I already have some ideas to make the trackpad as well as the battery meter and brightness work, but it is not useful if the kernel isn't as stable as FydeOS (virtually no freezes or crashes once booted). I have already checked, and the issue is not the intel_idle.max_cstate issue that plagued most BayTrail/CherryTrail devices in the past (using value 1 doesn't change anything).
So any ideas how to get FydeOS kernel source? Patches to make the current chromeos-4.14 kernel stable?
UPDATE: As @nabil2000 reported, it seems that FydeOS is not willing to release their kernel source. But it is possible to get kernel config from v5.31 using configs.ko module, which is missing in the next version (v6.0). Using FydeOS v5.31 as base it is possible to build a very stable kernel for CherryTrail devices.
Thanks
Installation v71/v72 - kernel 4.14
FydeOS has the best support for the MIIX320-10ICR, with some caveats:
It will boot to a black screen, but you just need to wait until it finishes loading the hit Ctrl+Alt+Fn+F2, the screen will blink and then hit Ctrl+Alt+Fn+F1 to go back to ChromeOS (for some reason, the developer shell is blank in 5.31 but it seems to work fine on 6.0). Use Ctrl+Shift+Fn+F3 to rotate the screen manually;
WiFi works out of the box, Bluetooth is detected but audio does not work (Chromium misses a library for audio over Bluetooth);
Sound works too, but you need to install some UCM files (more about this later);
Camera does not work, and the trackpad works very well, with gestures, but does NOT click (tap to click work with a custom conf file, see below - the trackpad actually sends two events when clicking the physical button, as some Windows devices do, and this doesn't work with cmt driver).
First I tried to build the ChromeOS file using the chromium.img from FydeOS v5.31. It booted fine and I was amazed to see the ChromeOS logo and Google enrollment, but PlayStore setup didn't finish (low space?) and there was no way to install it to another driver: many GPT errors and the installer failed...
Then I tried to do everything on place:
Booted to FydeOS on USB drive;
As I could not get to the dev shell in v5.31, I had to login then use crosh and shell, then installed it on a second external disk (120GB SATA on USB, /dev/sdb):
PS: your device may be a different one, check the correct device name using "lsblk" or "fdisk -l" and be aware that this installation erases the whole disk!
Code:
sudo chromeos-install --dst /dev/sdb
After installing, I have used option 2A from GitHub page (very detailed, thanks!) with the script, soraka (or pyro) and caroline recoveries (both versions 11151.113 = v71) on another disk:
PS: FydOS v5.31 kernel does not have support to VTPM_PROXY, while v6.0 does, it means you cannot use swtpm.jar with FydeOS v5.31 and chromefy. For nocturne or Android Pie ARC, you must use FydeOS v6.0, otherwise ARC won't work.
Code:
sudo bash ./chromefy.sh /dev/sdb recovery.bin caroline.bin
Answered YES to use the local installation, YES to resize partitions and NO in the end to keep SELinux as enforced (it may work fine if you keep it to enforced with nocturne recovery tho when using FydeOS v6.0);
Rebooted using the final installation, logged in and everything seemed fine, but then Play Store would not show installed apps even after a reboot, so I tried a powerwash and it seems it fixed the issue, now it seems to be working fine.
Original post: https://forum.xda-developers.com/showpost.php?p=78891386&postcount=729
Post installation fixes v71/v72 - kernel 4.14
1. Sound
You need to install UCM files using linuxium-install-UCM-files.sh script after remounting rootfs as RW.
Code:
sudo remount -o rw,remount /
sudo bash ./linuxium-install-UCM-files.sh
2. Headphone jack
You must send this quirk to the rt5645 module when loading it, so while rootfs is still RW, as root add a file named "miix320.conf" to /etc/modprobe.d with this line:
Code:
options snd_soc_rt5645 quirk=0x1030
PS: if you have used the correct UCM files then the audio should change between speakers and headphones, but not mic. To enable internal mic:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev DMic
and to enable mic from headset:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev HSMic
3. Tap to click with trackpad
While rootfs is still RW, as root add a file named "50-mixx320.conf" to /etc/gestures:
Code:
Section "InputClass"
Identifier "MIIX320 conf"
MatchUSBID "048d:*"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tap Minimum Pressure" "1"
EndSection
PS: for this to work, make sure "tap-to-click" is enabled in trackpad section of system Settings. If you have another device, use "dmesg | grep input:" with "lsusb" to find your device USB id instead of "048d:*".
Still needing fixes:
- chrome://flags is blank for some reason, so any special flags should be added manually to "chrome_dev.conf" instead;
- Trackpad physical button click;
- Brightness control;
- Battery meter;
- Rotation;
- Automatic change between tablet/desktop modes;
- Cameras (hardly they will work as they rely on ATOMISP, which was abandoned and does not work even on newest kernels).
Original post: https://forum.xda-developers.com/showpost.php?p=78978577&postcount=757
reserved
Good news! With chromeos-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
lfom said:
Good news! With chrome-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
Click to expand...
Click to collapse
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
nabil2000 said:
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
Click to expand...
Click to collapse
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-dev in order to successfully build it.
lfom said:
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-devel in order to successfully build it.
Click to expand...
Click to collapse
I am a lazy billy - thanks - I like copy & paste, & think as little as I can afford
Could you help me patching it on my GPD pocket?
it uses cherry tail
https://forum.xda-developers.com/ha...gpd-pocket-t3928828/post79496417#post79496417
thank you