Facebook Lite - white bar at bottom of screen - Redmi Note 9S / Note 9 Pro (Indian Model) Question

Hiya all,
Not sure if anyone else seen this and/knows a solution?
Facebook Lite, when opened, has a white bar along bottom of screen in dark mode.
App is selected as using fullscreen mode and when not selected it's exactly the same.

Probably the navigation bar used for gestures, it can be a bit buggy sometimes. Try switching to 3 button mode or hide it altogether with an app like Immersive Mode Manager (MIUI's built-in "fullscreen mode" is a bit lacking to say the least).

(root) (system) (vendor) (overlay) (framework-res__auto_generated_rro. apk) apk editor with this apk file. We're going to the values folder, we're adding a new document document name (dimens.xml) we write this code in this document
<?xml version="1.0" encoding="utf-8"?>
<resources>
<dimen name="navigation_bar_height">0dp</dimen>
</resources>
And we say save. We create apk and we name it the same.
respectively (system) (vendor) (overlay) here we replace it with apk of the same name

yunusarpc said:
(root) (system) (vendor) (overlay) (framework-res__auto_generated_rro. apk) apk editor with this apk file. We're going to the values folder, we're adding a new document document name (dimens.xml) we write this code in this document
<?xml version="1.0" encoding="utf-8"?>
<resources>
<dimen name="navigation_bar_height">0dp</dimen>
</resources>
And we say save. We create apk and we name it the same.
respectively (system) (vendor) (overlay) here we replace it with apk of the same name
Click to expand...
Click to collapse
Disabled navigation bar apk

yunusarpc said:
(root) (system) (vendor) (overlay) (framework-res__auto_generated_rro. apk) apk editor with this apk file. We're going to the values folder, we're adding a new document document name (dimens.xml) we write this code in this document
<?xml version="1.0" encoding="utf-8"?>
<resources>
<dimen name="navigation_bar_height">0dp</dimen>
</resources>
And we say save. We create apk and we name it the same.
respectively (system) (vendor) (overlay) here we replace it with apk of the same name
Click to expand...
Click to collapse
Try nunu only on phones that don't have navigation bars, such as galaxy j7 sm-j701f

{
"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"
}
Samsung galaxy j701f android 9 no problem

Same my problem miui 10 android 9 pie all Apps working fine but Instagram and Fb lite

yunusarpc said:
(root) (system) (vendor) (overlay) (framework-res__auto_generated_rro. apk) apk editor with this apk file. We're going to the values folder, we're adding a new document document name (dimens.xml) we write this code in this document
<?xml version="1.0" encoding="utf-8"?>
<resources>
<dimen name="navigation_bar_height">0dp</dimen>
</resources>
And we say save. We create apk and we name it the same.
respectively (system) (vendor) (overlay) here we replace it with apk of the same name
Click to expand...
Click to collapse
Sir help me

Related

[GUIDE][ICS]Use PNG Images as Notification Background for Stock / Stock Based ROM

Now here's tutorial on how to put any PNG image as notification pulldown background..
Here I'm using lidroid's modified SystemUI, should work on other stock based SystemUI
First you need to decompile your SystemUI.apk
Open res/values/drawable.xml with any good xml editor (here I'm using NP++)
Delete this line:
Code:
<item type="drawable" name="notification_tracking_bg">#xxxxxxxx</item>
the #xxxxxxxx value maybe vary in each ROM, just delete the whole line )
Save
Prepare your desired .png file, can be opaque or transparent, and can be in any size/dimension (the system will resize it to match the screen)
Rename it to notification_tracking_bg.png and put it in res/drawable-hdpi
Recompile your SystemUI.apk, push to your phone and you are.......
Done !!
The result will be looked like these :
{
"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"
}
Remember to
ALWAYS MAKE BACKUP !!
before doing anything above..
I don't responsible of any negative things like bootloop, bricked device, burned SD card, you late to go to school, or the third world war caused by the guide above..
You have been warned !!
Click to expand...
Click to collapse
Good luck..
iiandskater said:
Now here's tutorial on how to put any PNG image as notification pulldown background..
Here I'm using lidroid's modified SystemUI, should work on other stock based SystemUI
First you need to decompile your SystemUI.apk
Open res/values/drawable.xml with any good xml editor (here I'm using NP++)
Delete this line:
Code:
<item type="drawable" name="notification_tracking_bg">#xxxxxxxx</item>
the #xxxxxxxx value maybe vary in each ROM, just delete the whole line )
Save
Prepare your desired .png file, can be opaque or transparent, and can be in any size/dimension (the system will resize it to match the screen)
Rename it to notification_tracking_bg.png and put it in res/drawable-hdpi
Recompile your SystemUI.apk, push to your phone and you are.......
Done !!
Good luck..
Click to expand...
Click to collapse
First I like your guide and i tried to do follow that, but i need your help. Can you explain more cleary, i used apk manager to de-compile systemui.apk then copied to sd and used Root explorer to move it to system/app and set permission 6-4-4 and then reboot phone, But when the phone started, i lost my notification and got alert mess com.adroid.systemui stopped. Force close
p/s sorry for my poor english

[MOD][TUT] Add ROM version into Settings with Build.prop control

With this mod, you can add an item about the version of your rom, making it editable from the build.prop.
What you need:
-Apktool
-Settings.apk
-A text editor
-Notepad++ recommended
Let's begin!
Open command promot and move to your Apktool's folder. Then, type this:
Code:
apktool d Settings.apk
{
"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"
}
When the file is decompiled, go to Settings/res/xml, find and open (with Notepad++) device_info_settings.xml.
In device_info_settings.xml, find the line wich begins:
Code:
<Preference android:title="@string/mod_version" android:key="mod_version"
or if it's a PAC rom, line could begin with:
Code:
<Preference android:title="@string/mod_version" android:key="mod_version"
Add before (preferred) or after this line (depends if you want to see your rom version before or after of Cyanogenmod Version):
Code:
<Preference android:title="@string/rom_version" android:key="rom_version" android:summary="@string/rom_version_default" style="?android:preferenceInformationStyle" />
The file should look like this:
Save and close the file.
Now go to Settings/res/values and open strings.xml.
Go at the end of file (before </resources>) and add these two lines: (replace Your_ROM with your rom name)
Code:
<string name="rom_version">Your_ROM version</string>
<string name="rom_version_default">Unknown</string>
Final result will be this:
Save and close.
For other languages, procedure is identical but instead to go to res/values, go to res/values-** (**=language). For example, for italian translation, go res/values-it instead res/values and change from "NextCyan version" to italian translation or rather "Versione NextCyan".
We have just added a item into Settings--> About device. Now we have to create support for changing the version from build.prop. And here perhaps comes the hard part.
Go to Settings/smali/com/android/settings/DeviceInfoSettings.smali
Now press Ctrl+f and type "mod_version" or "cm_version" in case it's a PAC rom.
In various results, look for lines similar to these:
Select lines from .line XX to .line XY, where is contained "mod_version" or "cm_version" as follows:
Copy the lines (Ctrl+C).
Now, if you have added the line before "Cyanogenmod version" (into device_info_settings.xml) open this spoiler
Paste the code (Ctrl+V) above .line XX (in my case above .line 94) and make some empty lines, like this:
In new lines, you need to replace "mod_version" (or "cm_version") with rom_version.
The second thing to do, is edit the line to write into the build.prop, then edit "ro.cm.version" to "ro.rom.version".
else, if you have added the line after "Cyanogenmod version", open this
In this case is needed to paste the code before .line 96 (for me) and making some empty lines, you'll see this:
In new lines, you need to replace "mod_version" (or "cm_version") with rom_version.
The second thing to do, is edit the line to write into the build.prop, then edit "ro.cm.version" to "ro.rom.version".
Save and close the file.
Come back to the main folder, where's place apktool and type:
Code:
apktool b settings
Now, with WinRAR/Winzip/7-Zip, extract Settings.apk in a folder called Settings-new.
Go to Settings/build/apk and copy all files and folders and paste them into Settings-new folder replacing old files.
Compress all content of Settings-new folder...
...and rename from Settings-new.zip to Settings.apk --> File Ready
Screen of build.prop
Screen "About device"
Sorry for my bad english (x100)
Tested on:
-Samsung Galaxy S Advance
-Samsung Galaxy Mini
Click to expand...
Click to collapse
Credits:
[email protected] for test it on Galaxy Mini
Click to expand...
Click to collapse
Reserved Just in case
Reserved2

[DISCONTINUED][GUIDE] Adding PIE Controls to ROM [4.0+]

PIE Controls in 4.0+ ROMS
{
"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"
}
In this guide i will be telling you how to implement PIE Controls in any ICS or above roms!!
Click to expand...
Click to collapse
Requirements:
Code:
* Apktool or anyother tool to decompile/recompile apks
* [URL="http://forum.xda-developers.com/showthread.php?t=1330150"]LMT Launcher[/URL]
* Settings.apk
Step 1:
Decompile your settings.apk and your LMTLauncher.apk as well.
Step 2:
Inside of the decompiled LMT launcher, open the AndroidManifest.xml file and delete the below line. Now save and exit.
Code:
<category android:name="android.intent.category.LAUNCHER" />
Step 3:
Navigate to the res->xml folder inside of your decompiled settings apk and open the settings_headers.xml file.
Paste the code below where you feel fit.
I have chosen to place the code under the "<intent android:action="com.android.settings.MANUFACTURER_ APPLICATION_SETTING" />" line.
Code:
</header>
<header android:title="@string/navigation_settings" />
<header android:id="@id/pienav_settings" android:title="@string/pienav_label">
<intent android:targetPackage="com.android.lmt" android:action="android.intent.action.MAIN" android:targetClass="com.android.lmt.LMT" />
Step 4:
Navigate to the res->values folder inside of you decompiled settings apk and open the strings.xml file.
Paste the following code at the bottom of the file above the "</resources>" line.
Code:
<string name="navigation_settings">Navigation</string>
<string name="pienav_label">Pie Controls</string>
Step 5:
Navigate to the res->values folder inside of you decompiled settings apk and open the ids.xml file.
Paste the following code at the bottom of the file above the "</resources>" line
Code:
<item type="id" name="pienav_settings">false</item>
Step 6:
Recompile the apks!!! Probably you wont get any errors!! If so post your errors i will try my best to help you out!!!
Step 7:
You may need to sign your LMTLauncher.apk as you have modded the AndroidManifest.xml file but no need of Settings.apk!!
Step 8:
Create a flashable zip and flash it!!! Using adb or using root explorer to replace apps may not work at times!!!
Credits:
Code:
* Xda
* Google

AndroidManifest Error (No resource identifier found for attribute resizeableActivity)

I am trying to hack a game called MilkChoco - Online FPS. I can confirm that this game uses "xigncode" to block hacking tools such as Lucky Patcher, Game Killer etc... I am so close to hacking this game by removing xigncode detection but at this very last step, I am having problems. Let me describe what I've done (the modifications) and the problem at the end.
1) I decompiled the .apk with apktool.
{
"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"
}
2) I go to the folder with all xigncode related files.
C:\Users\Dell\Desktop\apktool\MilkChoco_1.3.4\smali\com\wellbia\xigncode
3) I use Notepad++ to go to the above directory and search the following
.method public initialize(Landroid/app/Activity;Ljava/lang/String;Ljava/lang/String;Lcom/wellbia/xigncode/XigncodeClientSystem$Callback
4) I double clicked on the result to directly go to that file. This is what appears.
5) I simple added this to the .prologue line so that it appears like this.
.prologue
const/4 v0, 0x1
return v0
I believe this will remove xigncode detection. This is all I did with the modification for the .apk file. If I'm wrong that this will not remove xigncode detection, please let me know.
6) I save the file and recompiled the app. However there is this error.
C:\Users\Dell\Desktop\apktool\MilkChoco_1.3.4\AndroidManifest.xml:9: error: No resource 'resizableActivity' in package 'android'
Here is the full display of the error.
I did some google searches for 'resizableActivity' but couldn't find anything useful. Here is the ORIGINAL AndroidManifest.xml when I decompiled the apk.
As you can see in Line 9, 'resizableActivity' is mentioned. Lacking my knowledge, is there any error in the above screenshot, especially in Line 9?
I did these changes to the line. The first two doesn't work, however the error does not occur after my third change.
1) Changed "false" to "true" (at the end of the line) DOESN'T WORK
<application android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:resizeableActivity="true">
2) Changed "true" to "false" (near the beginning of the line) DOESN'T WORK
<application android:allowBackup="false" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:resizeableActivity="false">
3) Original code is:
<application android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:resizeableActivity="false">
I deleted the last part of the code so it looked like this
<application android:allowBackup="true" android:icon="@mipmap/ic_launcher">
The error does not occur after this change. I can successfully recompile the apk. HOWEVER, when I tried to install the apk, it says "error parsing the package". I'm really loosing my mind over this. I would strongly appreciate it if someone could explain why the error is mentioning AndroidManifest.xml. Thank you.

How to fix app crashing when using the showFloatWindow API on Huawei devices running EMUI before version 9.1

A number of reports were received about crashes when the showFloatWindow API is called on devices running older versions of EMUI. Let's take a look at this crash today and how we can fix the issue.
Start by integrating version 6.1.0.301 of the Game Service SDK into a project and successfully implemented the floating window function.
Then, when testing the game on devices running a version of EMUI earlier than 9.1, the game crashed when showFloatWindow API is called. The crash logs are as follows.
{
"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"
}
The error logs suggested that the issue was caused by missing layout files during layout implementation. This error suggests that c_buoycircle_window_small.xml, c_buoycircle_hide_notice.xml, and c_buoycircle_hide_guide_dialog.xml layout files were not found in this project. However, they had been saved under the layout folder as displayed in the following figure.
The next possible issue could have been that the layout files were obfuscated. So, let's check the build file to be sure:
As you can see minifyEnabled was set to true, indicating that the obfuscation function was enabled. This was also the case for shrinkResources, which meant that resource files were excluded during package creation.
One option of course would be to simply disable the shrinking of resources. By commenting out this line the game would run fine and the API call wouldn’t crash, however, the resource files are no longer compressed and will take up much more space.
To compress the resources, you can create an XML file that contains the resources tag in the project or use the keep.xml file in the res/raw directory, and specify the resources to be reserved in the tools:keep attribute as follows:
XML:
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="http://schemas.android.com/tools"
tools:keep="@layout/c_buoycircle*" />
This solution allows the floating window function to work and is able to compress the resource files.
Note: If you have integrated the Game Service SDK, Huawei suggests that you add the following resources and configure the following obfuscation scripts.
@drawable/c_buoycircle*
@drawable/hms_game*
@Layout/c_buoycircle*
@Layout/hms_game*
@StRiNgS/hms_game*
@StRiNgS/c_buoycircle*
nice article

Categories

Resources