Develop Bugs

[Gen9] Rooted 3.2.69 firmware v0.1 with superuser.apk for SDE

Hello All,
Here is a stock repackaged firmware to be used if you enabled SDE like described here.
To install it:
1) Extract zip file content
2) Copy rooted_withsu.squashfs.secure to internal storage root. You can do it the usual way or with adb with this:
adb push rooted_withsu.squashfs.secure /data/media
3) Reboot
4) On boot menu, select "Recovery system"
5) Select "developer edition menu"/"flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
Download firmware here.
And let me know if it worked for you,
LeTama

* reserved *

It is ok
http://www.jbmm.fr/?p=23638
{
"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"
}

All working for me too. Good work people

How do you get to "developer edition menu"/"flash kernel and initramfs"
Currently if I press and hold power / volume down to boot I get 3 options. Android, Developer Edition and Recovery System. If I select Developer Edition and press the power button it comes up with Booting Developer Edition and then appears to reboot this then loads standard android.
Can I just check that im doing this correctly?
Thanks
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Lol. Im a dumbass... Recovery menu then developer edition menu.

My bad, as I don't have the boot menu, I didn't write proper description:
On boot menu, select "Recovery System" then you'll see a menu with the "developer edition menu" entry. First post modified to reflect that.

All done . If I boot developer edition I have root, If I boot standard I dont - Thank you very much
One thing I note is that superuser apk doesnt retain its memory after a reboot.
So far i have just tried a couple of tools that reboot / shut down your archos (as for me thats all im desperate for doing as im installing the device into my cars dash and have no access to the button). Reboot and Shutdown works fine, but if you ask for the bootloader it seems to mess up - will look at writing something fresh anyway as all I really need is the ability to send it to sleep on ac power disconnect

hotrodder said:
All done . If I boot developer edition I have root, If I boot standard I dont - Thank you very much
One thing I note is that superuser apk doesnt retain its memory after a reboot.
So far i have just tried a couple of tools that reboot / shut down your archos (as for me thats all im desperate for doing as im installing the device into my cars dash and have no access to the button). Reboot and Shutdown works fine, but if you ask for the bootloader it seems to mess up - will look at writing something fresh anyway as all I really need is the ability to send it to sleep on ac power disconnect
Click to expand...
Click to collapse
Thanks for the feedback, I'll check the superuser problem.
You know about the reboot_into command, right ?
syntax: reboot_into sde|android|recovery

letama said:
Thanks for the feedback, I'll check the superuser problem.
Click to expand...
Click to collapse
Ok, I believe I know why you loose settings: If you reboot into "regular" android (ie, without root), android detects that the superuser application was removed from the firmware and removes associated data. I'm not sure I can do anything about this, don't boot into regular android is probably the best advice I could give
After all, no need to go there anymore.

Wow, thats a real help many many thanks. If i call reboot_into -s sde post booting then it should always boot back into sde even if it boots off due to battery power yeah?
I know im a bit of a noob when it comes to android (been a windows coder for a while).
There isnt a way to put the device into "deep sleep" using the command line is there? Basically the whole aim of rooting this device for me is to make it so I can either put it to sleep or power down when external power is removed. I should now be able to shut it down, but id like to make it "sleep" instead if possible as that will come to life a lot faster. The aim being that i will add external power when i flick the key in my car (waking the device up), and then when i switch off it will lose power and be put into sleep mode. If the battery dies then it will recharge when i flick the key again and do a full boot anyway - which i should be able to force into sde as above.

hotrodder said:
Wow, thats a real help many many thanks. If i call reboot_into -s sde post booting then it should always boot back into sde even if it boots off due to battery power yeah?
Click to expand...
Click to collapse
Yes, correct.
hotrodder said:
There isnt a way to put the device into "deep sleep" using the command line is there? Basically the whole aim of rooting this device for me is to make it so I can either put it to sleep or power down when external power is removed. I should now be able to shut it down, but id like to make it "sleep" instead if possible as that will come to life a lot faster. The aim being that i will add external power when i flick the key in my car (waking the device up), and then when i switch off it will lose power and be put into sleep mode. If the battery dies then it will recharge when i flick the key again and do a full boot anyway - which i should be able to force into sde as above.
Click to expand...
Click to collapse
Well, I didn't check power management much in these new kernels, but first, I'm not sure I understood the purpose of this. What differs from the normal power management ? I would do this: "Screen/Timeout 15 seconds" (to power down quickly), and "Application/Development/Stay Awake" (To keep screen up while power is on) ? You add on top "About tablet/Power Management/Deep sleep" for better sleep and you're good ?

Thats what I do currently, but there are times that it doesnt go to sleep. I will be using as a media player, and if you have music playing the screen will go off but leave the music playing which will stop it from powering down, although i can probably kill any running apps on power off. Also I use the full size USB slot on the back to connect a laptop hard drive - and ive noticed that it seems to wake the device up when you just turn off the screen, but doesnt if you hit the power button and tell the device to sleep. Ive played with settings related to the USB port but no luck so far with that one. Sorry for hijacking the thread though - i got a bit off topic.

hotrodder said:
Thats what I do currently, but there are times that it doesnt go to sleep. I will be using as a media player, and if you have music playing the screen will go off but leave the music playing which will stop it from powering down, although i can probably kill any running apps on power off. Also I use the full size USB slot on the back to connect a laptop hard drive - and ive noticed that it seems to wake the device up when you just turn off the screen, but doesnt if you hit the power button and tell the device to sleep. Ive played with settings related to the USB port but no luck so far with that one. Sorry for hijacking the thread though - i got a bit off topic.
Click to expand...
Click to collapse
I see. I'm not a power management expert, so maybe someone could give you better advice.
One other lead I could give you: do you know /sys/power/wait_for_fb_sleep ?
This one is nice, a cat on it will be blocked until the screen goes off. It doesn't solve your usb drive problem, but you could use it if you need to be notified that screen goes off.
I'll take a look at kernel source code to see if I can find something.

thanks lekama so much
after step 8) Select OK to reboot. after reboot, it boot normally and i didn't saw any SDE in boot menu to choose it. plz help ^^.
---------- Post added at 07:39 AM ---------- Previous post was at 07:14 AM ----------
yeah, i choosẽn "developer edition menu" and it boot into rooted,
thanks again for ur good worked ^^ kaka

works on my 80 G9 here, thanks!
is there any way to mount /system rw? i want to push a patched wpa_supplicant for enabling adhoc-support..

i'm installed Chainfire3D to play games, but it's not enough space to install driver, and i can't remove system apps, i think this isn't really rooted ...^^..

a1Pha said:
works on my 80 G9 here, thanks!
is there any way to mount /system rw? i want to push a patched wpa_supplicant for enabling adhoc-support..
Click to expand...
Click to collapse
Not with this firmware, this is pure stock with exactly the same way of of mounting system from a read-only squashfs.
You have two solutions, repackage your own squashfs or modify the initrd to mount an ext4 image for instance.

conmeo8ya said:
i'm installed Chainfire3D to play games, but it's not enough space to install driver, and i can't remove system apps, i think this isn't really rooted ...^^..
Click to expand...
Click to collapse
It is rooted. You can run any rooted application with it.
However, as I explained above, this firmware is pure stock with the same squashfs method meaning read-only /system. It's more like a proof of concept that SDE works properly.
I don't have much time to maintain builds and I'd prefer someone else to come up with one, but if nobody does, I'll do one running on r/w ext4 image.

Thanks. Is there any known way to bypass the 256 byte Archos security signature?
//Edit: In the squashfs, I mean.

a1Pha said:
Thanks. Is there any known way to bypass the 256 byte Archos security signature?
//Edit: In the squashfs, I mean.
Click to expand...
Click to collapse
losetup -o 256 /dev/loopx img.secure and mount
or dd if=img.squashfs.secure of=img.squashfs bs=256 skip=1 and unsquashfs

[Q] Any other way to bypass activation screen. [Solve]

I have a big problem on my HTC Droid Incredible.
Bypassing the activation screen really irritates me and i can't turn on the USB Debugging which is the key to root and s-off my phone and to bypass the activation screen.
The procedure i did for bypassing the activation screen are: tap 4 corners, safe mode, call *228 and end call after few seconds (did this several times), cdma workshop, ##778 change the nam setting, and non of them works for me.
cmlusco member of xda told me that the best way to bypass it is to change the build.prop in any rom i'm going to flash on my phone. Then he give me this link http://forum.xda-developers.com/showthread.php?t=1306400 and i think this is it, but in the end still failed because i need to turn on my USB Debugging.
Please help me to bypass my Droid Incredible.
I'm here in Philippines and there is no Verizon network provider here.
I already solve this problem and I can use my Droid Incredible. Sweet!!!View the 3rd post how did i do that.
Click to expand...
Click to collapse

are you able to fix this?im having EXACTLY the same problem.

yup I already fix it, just follow this procedure.
1) try to enable usb debugging mode by doing this procedures.
for this,you should need wi-fi.
so,let's start
1)when the phone calls to *228 tap contacts icon,right to the "end call"
2)try to add a new contact and enter facebook or other socialnet dialog.
phone asks you to enable wifi, do this and connect your wifi network
3)next hold the search button and (via voice search) search in google "market"
4)tap to the official market page, phone asks you about opening this page,choose market app.login in the google accounts,if you need.
5)search in market "usb debug" app. install it and tap "open' in the market app
6)enable usb debugging and enjoy)
and for those who don't have a wifi connection in there home, this procedure is for you.
1. call *228 and tap the contact on the right side of end call.
2. add contact and put any information.
3. try to connect it in facebook to prompt the setting window.
4. tap setting.
5. tap search softkey and type application.
6. finally you can enable usb debugging without any problem.
thanks to ramazancik94 for giving this life saver step for enabling usb debugging mode.
2) root and s-off your phone by following this procedure root 2.3.4,downgrade,and s-off
3) if you already have CWM, rooted, and s-off your phone try to install some ROM using CWM in development section. Double check if your phone is s-off via hboot (press and hold power button and volume down), your phone is rooted if you install CWM, and find some ROM that suits your need.
4) Try to use the "end call bypass" if this method doesn't work with you this will be your last resort. Delete the phone.apk before you install the rom, to delete the phone.apk open the "blah blah blah rom.zip" and go to data> system app> find phone.apk and please don't extract the rom and delete the phone.apk or i won't work, just delete it from the zip.
Note: Deleting the phone.apk will result for disable your phone signal. So you're going to use your phone for music, game, watch some movies and wifi internet. You won't be able to use it for call, text and mobile data, and also please read it carefully so you won't **** your phone. You've been warned
For more information visit this thread: help bypass the activation
All big thanks to cmlusco, ramazancik94 and tiny4579 for their help

need help
sir maybe you can help me with this...im new to android phones and i dont think i can make it
can you please send me the step by step procedure of the things i need to do after i put my phone in USB debugging mode?hope you dont mind
my email is [email protected]
my tcp account is kian0926, im here in the Philippines as well and im glad that you were able too fix yours, hoping that i can use mine as well, saving this device from a trash can
many thanx in advance...

i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............

Kian0926 said:
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Click to expand...
Click to collapse
You cant just click on the adb.exe file, it is a cmd line program. Open a cmd prompt on your pc and type " cd C:\mini-adb_inc " then type in your adb command, example " adb devices " this should show the serial number of your phone if connected to the pc and adb and drivers are setup correctly.

thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now

Kian0926 said:
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Click to expand...
Click to collapse
What makes you think the cd command didnt work, did it give an error? All cd does is change the directory to C:\mini-adb_inc where the adb file is located. It is ok if it says just adb and not adb.exe, your pc is just set to hide extensions. When you first open the cmd prompt to the left of where you type it will say something like C:\users\your_user_name\desktop >, when you type cd C:\mini-adb_inc it should go to the next line, and to the left of where you type now it should say C:\mini-adb_inc >Then type adb devices and see if a serial number comes up.

"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..

Kian0926 said:
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Click to expand...
Click to collapse
You have to type " cd C:\mini-adb_inc " or what ever the path is to the adb file. here actually try this. Go to the folder where the adb file you unziped is. Then hold ctrl + shift and right click on an empty space in that folder, and select open cmd prompt here. then type in your adb command, ie adb devices.

after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..

Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Sorry to say, but if you cant enter hboot, or boot up to the os or recovery, then the phone is more thsn likley bricked. Unless its a battery issue. Does it vibrate at all when trying to start?

Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Does it boot when plugged in? There MAY be some help if it can boot when connected to AC power.

Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
I've experience this, just a blinking orange led. What did I do was i charge it and a couple of minute the the blinking orange led stops and it become a steady orange led.

Easier way (offline)
Found what could be an easier way, I'm playing with my sister's incredible and I can get usb debugging enabled by using any of the official verizon update packages (could be a rom, but I downloaded the smallest hboot upgrade from htcdev), it appears to send some commands in usb mode that trigger the activation of usb debugging, what's funny if that if you either disconnect before it's done, or it fails, it leaves usb debugging on.
Non-sense.
EDIT: You just have to open the utility, you don't to flash or disconnect.

Such and old thread but I have a Incredible that a friend gives me and I couldn't access the market app by search function. What I did was search anything with voice commands, then a navigator window opens and change the URL to: market://details?id=usb, it opens the market app and I can install the USB debug app

Simple method, without the use of USB Debudding/rooting flashing:
Go to Emergency dialer,
Enter ##778, and press 'call'
Select 'Edit Mode'.
Password is: 000000
Select 'NAM Settings'
Make the following changes:
MDN = your 10 digit phone# (0000000000)*
MIN1 = your 7 digit phone# (0000000)
MIN2 = the area code of your phone# (000)
Press the 'back' key and go to 'HOME SID/Home NID' settings
Select 'Home SID/NID #1', and change the first value to '189' (Leave the 65535 alone).
Now press your 'menu' key
Press 'commit modifications' "button"
Phone Should reboot now.
Changing MDN using cdmaDevTerm
In some phones MDN cannot be changed, in this case you need to connect the phone to the computer as a "modem" device, and use the opensource cdmaworkshoptool / cdmaDevTerm from here:
http://code.google.com/p/cdmaworkshoptool/
Connect the tool, select manually / automatically the COMPORT for your HTC device, Read from device, Change the MDN to 0000000000 Select write
Disconnect and reboot your device.
It should now by pass the activation.
most of the ref. from
http://androidforums.com/incredible...g-activation-screen-no-service-available.html

[MOD]No notch ? Welcome to the immersive mode ! Remove the notification bar

Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
EDIT: I have tested "Immersive Manager Application" from Google Play Store and it's perfect. Very simple and it works even when you reboot your phone.
No more need to type adb commands below except at least few adb commands to grant the Secure Settings permission to the app. This is well explained by the application when you launch it the first time.
I let the adb commands below for information in case we had some "purists" who prefer adb than an immersive app.
1/ Enable the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Enable USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:

Pls the screen..
Redmi K20 cihazımdan Tapatalk kullanılarak gönderildi

pidobeuliou said:
Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
1/ Activate the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Activate USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:
Click to expand...
Click to collapse
Thanks for the instructions bro... I like the immersive mode on all the apps but i do not in instagram app, What is the command to get the immersive mode on all the apps but not in some specifics one?

The setting is reset on reboots. How can it be persisted?

salzzz said:
The setting is reset on reboots. How can it be persisted?
Click to expand...
Click to collapse
Do you have root permissions? If the asnwer is "yes" you can do this:
Install terminal emulator from google play store. Open it and writte "su"
now writte this:
settings put global policy_control immersive.status=*
Tachan! you have immensive mode active. Only save the command in a note app. Always you reboot your phone the only thing you have to do is open terminal, su and paste your command.
A lot more easy and fast than do it with adb. the only "problem" is you need root.
If someone knows how to add an exception, please say so.

How do you show it on lock screen? Any ideas?

"Permission denial: writing to settings requires:android.permission.write_security_settings"

ramsyst said:
"Permission denial: writing to settings requires:android.permission.write_security_settings"
Click to expand...
Click to collapse
Did you manage to overcome this getting same error here
NVM, fixed it

ralphoberholzer said:
Did you manage to overcome this getting same error here
NVM, fixed it
Click to expand...
Click to collapse
Still getting the same error, how did u get around it ?

ramsyst said:
Still getting the same error, how did u get around it ?
Click to expand...
Click to collapse
Enable USB debugging (security settings) under developer options.
I used SystemUI Tuner as it allows for blacklisting apps (sucha as whatsapp) that don´t manage full screen well.

ralphoberholzer said:
Enable USB debugging (security settings) under developer options
Click to expand...
Click to collapse
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
Worked great, Thanks

pidobeuliou said:
Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
1/ Activate the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Activate USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:
Click to expand...
Click to collapse
I am sorry friend, bootloader unlocked ?

wilmerwils said:
I am sorry friend, bootloader unlocked ?
Click to expand...
Click to collapse
No, it's not necessary to unlock the bootloader.
You have just to activate the developper mode as I indicate it.

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
Yes, it's true. Each time you reboot the phone, you should loose the setting.
And good point, thank you Ramsyst, I didn't check on Google Play Store the myriad of immersive mode applications!!
I have tested "Immersive Manager Application" and it's perfect. Very simple and it works even when you reboot your phone. :good::good:
I had previously created a task with Tasker and AutoTools (paid version) to change the immersive mode with the "Custom Setting" feature. But knowing that there are many apps (free and paid version) doing that better than AutoTools, it's not usefull to describe how I did it.

pidobeuliou said:
Yes, it's true. Each time you reboot the phone, you should loose the setting.
And good point, thank you Ramsyst, I didn't check on Google Play Store the myriad of immersive mode applications!!
I have tested "Immersive Manager Application" and it's perfect. Very simple and it works even when you reboot your phone. :good::good:
I had previously created a task with Tasker and AutoTools (paid version) to change the immersive mode with the "Custom Setting" feature. But knowing that there are many apps (free and paid version) doing that better than AutoTools, it's not usefull to describe how I did it.
Click to expand...
Click to collapse
Thank you too! I didn't know this immersive mode was possible until i stumbled on your thread. Now, we can all enjoy that beautiful screen 100%!

No devices / emulator found ... Please help. I instal drivers do all on this topic

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
With Tasker you already have an option to make all apps you want to go immersive! There is no need to use any other command or app.
I believe everybody in the world should buy tasker
Is the best Android app. It may looks hard in the begining, but your imagination is the limit to do whatever you want.

Hi how can i used this on split screen but in full screen mode with status bar and navigation?

MrYuu said:
Hi how can i used this on split screen but in full screen mode with status bar and navigation?
Click to expand...
Click to collapse
You're right. I had never tested the split screen function. The notification bar is not hidden on split screen mode even when immersive mode is activated. The result is a bit weird as there is a mix of notification bar and app on the top of the screen.
"Google search" indicates that you are not the first one to face this issue... but apparently no solution has been found so far.
If somebody can help.

missing accessibility menu (help)

So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help

broyoto said:
So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help
Click to expand...
Click to collapse
I have the same problem with my TV, as I found out the problem is from the brand side. They choose a rom that that does not have this... The only way to give permision to an app is only through ADB that it is not an easy job

I also have the same issue with my TV, waiting for the solution.

I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
{
"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 same way I resolved this and other apps

The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission

Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,

I have the accessibility menu but when I install any app it doesn't appear on accessibility menu at all.

sophiesaelig said:
I also have the same issue with my TV, waiting for the solution.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Wow...Din't expect your reply. If you're official developer or team of Button Mapper, just want to tell you one thing.
"You saved my ass so many times". I just love your app and have been using it since a year, happy to say I paid for full version since starting.

ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
Thank you, I did it at the same app.
I tried to do it for this app " Mouse toggle for Android tv" but it didn't work, Can you help me?

Deleted member 1198227 said:
Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,
Click to expand...
Click to collapse
If any have found workaround let me know, this bug is very annoying

ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Bought a tv in europe ( developper and usb debuggibg activated) can't run any adb command though. Adb: not found

[GUIDE] Enable Adaptive Audio on Pixel 4/XL

Hey everybody,
I guess I was not the only one being a bit disappointed that google didn´t make adaptive audio available for the Pixel 4 devices as well.
To be honest I personally think it´s a bit of a gimmicky feature that´s not very critical, but making it exclusive to Pixel 5 left a bitter after taste.
Here´s how to enable the feature persistent across reboots on a rooted device:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
https://www.apkmirror.com/apk/google-inc/device-personalization-services/device-personalization-services-r-11-playstore-pixel5-353007393-release/device-personalization-services-r-11-playstore-pixel5-353007393-android-apk-download/
2. Flash the attached magisk module Adaptive_Audio_Settings_Enabler.zip via magisk manager app and do a reboot.
Wait a few minutes after the phone booted successfully and the entry in settings will appear.
Manual command method, doesn´t survive reboots but works on unrooted devices as well:
1. Download the pixel 5 device personalization app from apkmirror and install the app:
Device Personalization Services R.12.playstore.pixel5.357001175 APK Download by Google LLC - APKMirror
www.apkmirror.com
2. Make sure to have USB Debugging enabled via developer options and have a working adb environment. Then connect your phone to pc.
3. Type the following:
Code:
adb shell
4. then type (this step is not needed)
Code:
su
grant superuser permission in the window that opens on your phone.
5. Now paste the following commands:
Code:
device_config put device_personalization_services AdaptiveAudio__enable_adaptive_audio true
Code:
device_config put device_personalization_services AdaptiveAudio__show_promo_notification true
You can enable it now in settings and try the feature for yourself.
A few notes here:
I´m unsure how much profit this feature really gives, even on the Pixel 5. When enabling it on my 4XL the sound gets a bit more bassy.
Judging from the logs it should be working as it is with the steps described above. It might be that it´s tuned towards the Pixel 5, but well... Having options is always nice
The guide with the manual commands works without root, for those that don´t like to run rooted. I was able to disable and enable the feature back again without the need for root. Maybe some apps can execute scripts without root on the phone so it will stay across reboots. Somebody else has to figure this out though.
Have fun with it
{
"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"
}

Reserved

Wow, would you also happen to know how to enable night sight portrait mode on P4?

Thanks m8, you are a legend.
Works great on my 4XL stock, no root.
I followed the guide without the "su" part on adb shell

Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.

Zilla0617 said:
Thank you for the tip, but whenever I reboot the phone it will not stick, I'm currently rooted.
Click to expand...
Click to collapse
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously

Freak07 said:
You´re correct. I didn´t notice it, because it takes a short while for the setting to disappear after rebooting.
I made a magisk module, that passes the command every boot after a timeout. Magisk required obviously
Click to expand...
Click to collapse
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.

Zilla0617 said:
After installing the module, I added the commands using adb shell but adaptive sound still does not persist after a reboot.
Click to expand...
Click to collapse
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.

Freak07 said:
Flash the module in magisk manager, reboot, wait a few minutes and the entry should pop up. It needs a few minutes. There’s no need for any manual commands with the module.
Click to expand...
Click to collapse
It's working. Thank you

Working like a charm thank you mate.

how i do adb Do you have an example please?

How do I get back to the original device personalization service app?

oraned said:
how i do adb Do you have an example please?
Click to expand...
Click to collapse
There are plenty of guides on xda on how to setup adb.
How to install ADB on Windows, macOS, and Linux
If you're on Windows, Linux or macOS, you can follow these step by step instructions to install ADB on your desktop or laptop PC.
www.xda-developers.com
If you are rooted with magisk and unfamiliar with command line, there's also the magisk module.
tifone said:
How do I get back to the original device personalization service app?
Click to expand...
Click to collapse
Open it in play store and hit uninstall. Then update again and it will install the latest one for pixel 4.
https://play.google.com/store/apps/details?id=com.google.android.as
Open this link when viewing xda via browser on your phone.

I am sorry telling you that my friend but I am rooted and did yesterday the process and everything was ok, after some seconds as you said the adaptive sound wan in my menu.
Today as I went to check if it was still there, kaboom, disappeared so I uninstalled everything and did it from the beginning, so it can be installed again.
Have an idea why?

Let's go ahead and give this a try. Thanks

Can confirm that it still does work. But after rebooting even with the root method and the module still showing up in magisk adaptive sound vanished in settings. Reinstalling the module makes it appear again and function.
Edit: The feature just vanished without a reboot. Guess Le Googs doesn't wan tus usingit RIP.

The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.

tifone said:
The comment above and I are experiencing the same symptoms. When a module is installed, it is initially visible in the configuration, but sometimes it is not present after a period of time. If you reboot each time, it will come back.
However, I wish it could be maintained without rebooting.
Click to expand...
Click to collapse
How long does it persist for you after you reboot?

zetsumeikuro said:
How long does it persist for you after you reboot?
Click to expand...
Click to collapse
That can't be verified. However, sometimes when time passes, it may not be in the setting.
I don't think there's a solution, but thanks for letting me use a service that doesn't support it.

I think I figured out why it sometimes disappears when I check it after some time.
I'm using the dolby digital plus module, but after deleting this module once, I tested to see if it disappears after a while, and the adaptive sound was maintained.
I'm not sure if it's causing a conflict between modules. I also noticed that the two modules run together at first.