Dears,
sometimes I find the Notification LED too bright on my Z3 Compact whereas on the Z3 of my wife it could definitely be increased (it's actually hardly visible except in the dark). So, I'm looking for a way to adjust/increase/decrease the brightness of the Notification LED on these mobiles.
Prior to posting this here I checked within XDA forum as well as I googled around a lot, but all solutions I found were for older models (e.g. Xperia S) only. Maybe I'm just too blind to see and someone please point me to the right place.
Now, what I found on Z3/Z3C (both of them are on the latest 4.4.4 but should be similar on LP) are the following three directories which I believe is the right place for the modification to do...
/sys/devices/leds-qpnp-f6141a00/leds/led:rgb_blue
/sys/devices/leds-qpnp-f6141a00/leds/led:rgb_green
/sys/devices/leds-qpnp-f6141a00/leds/led:rgb_red
Inside each of the above directories there's a text format file "max_brightness".
For the Z3 the standard values are:
max_brightness = 420 (blue)
max_brightness = 511 (green)
max_brightness = 98 (red)
For the Z3 Compact the standard values are:
max_brightness = 511 (blue)
max_brightness = 511 (green)
max_brightness = 255 (red)
I'm able to open the files, change the value inside and save, but after reboot (which anyways would be required for the new values to come into affect, I think) the old values (files?) got restored automatically. Even I tried to replace the original files with new ones via the Filemanager of TWRP recovery, but it get ERROR code 1 (can't overwrite).
Any much valued knowledgeable Dev able to please point me to the right method/direction over here?!
EDIT:
Got a bit further on why these can't be modified directly and even reset themselves over-and-over again. Reason being that "sys" is the mount point for the sysfs pseudo file system, which is a reflection of the kernel's device object structure and the directories represent the kernel objects, and files are attributes of those objects. Hence, anything underneath and within "sys" only exports information about various kernel subsystems, hardware devices and can't be changed here. Most obviously I now seem to have entered a steep learning curve, uuuhh. How to modify/adjust these kernel parameters, is there some other "real" file that can be used to override default values at boot time?
UPDATE:
Found the way of changing/overriding the standard kernel values of "max_brightness" (for respective color) via Recovery Script. So, if one has [NUT]'s Dual-Recovery installed (likely, if you're rooted ), then you'll find a file /system/etc/install-recovery.sh which in turn is calling install-recovery-2.sh in the same directory. If it doesn't exist (like in my case), just create it and put the following lines:
echo %value% > sys/class/leds/led:rgb_red/max_brightness
echo %value% > sys/class/leds/led:rgb_green/max_brightness
echo %value% > sys/class/leds/led:rgb_blue/max_brightness
where %value% can be anything between 0 and 255. Re-boot and done.
Only problem left: values > 255 are strangely not getting accepted that way. Means, if you put e.g. 500, upon next boot it defaults back to max. 255. Hence, for now I'm able to lower the brightness of the Z3C very well but increasing it on the Z3 doesn't work yet.
Can anyone help me with that last step?
sxtester said:
UPDATE:
Found the way of changing/overriding the standard kernel values of "max_brightness" (for respective color) via Recovery Script. So, if one has [NUT]'s Dual-Recovery installed (likely, if you're rooted ), then you'll find a file /system/etc/install-recovery.sh which in turn is calling install-recovery-2.sh in the same directory. If it doesn't exist (like in my case), just create it and put the following lines:
echo %value% > sys/class/leds/led:rgb_red/max_brightness
echo %value% > sys/class/leds/led:rgb_green/max_brightness
echo %value% > sys/class/leds/led:rgb_blue/max_brightness
where %value% can be anything between 0 and 255. Re-boot and done.
Only problem left: values > 255 are strangely not getting accepted that way. Means, if you put e.g. 500, upon next boot it defaults back to max. 255. Hence, for now I'm able to lower the brightness of the Z3C very well but increasing it on the Z3 doesn't work yet.
Can anyone help me with that last step?
Click to expand...
Click to collapse
Hi!Are you solve?
My sony E5823 Z5 compact white
Notification LED is too brightne
I think Reduce brightness
{
"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"
}
Related
After I ran Mister Muffin's "Auto Config Script" I lost the use of the Nook home button somehow and my wifey wants it back!!!! Right now I am using Zeam Launcher and "bpk's Softkey 2.0" with Home Switcher in order to get back home.
Does anyone know a way to get it back? Right now the Nook button only wakes the unit.
Thanks in advance!
I've seen the home button stop functioning on devices that are no longer provisioned. Check settings.db, the 'secure' table for 'device_provisioned', which should be 1. From the command shell on the device via terminal or adb, you can use getprop to examine this property.
wumpus11 said:
I've seen the home button stop functioning on devices that are no longer provisioned. Check settings.db, the 'secure' table for 'device_provisioned', which should be 1. From the command shell on the device via terminal or adb, you can use getprop to examine this property.
Click to expand...
Click to collapse
Could you give me the ADB code in order to do this?
adb pull /data/data/com.android.providers.settings/databases/settings.db
C:\temp>sqlite3 settings.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from secure where name='device_provisioned';
103|device_provisioned|1
sqlite> .q
PTzero said:
adb pull /data/data/com.android.providers.settings/databases/settings.db
C:\temp>sqlite3 settings.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from secure where name='device_provisioned';
103|device_provisioned|1
sqlite> .q
Click to expand...
Click to collapse
Thanks!
I pulled the settings D/B OK but I do not understand how to use SQLITE commands
Read my previous post and follow it. Type "sqlite3 settings.db", etc.
Not reconized as an int/ext command.
Look in your AdroidSDK/tools directory for sqlite3
Ok I did that exactly as you had it. Is that correct? Do I need to push the file back to the Nook?
Opps, I see no such table secure......
Ran again and get Error near "103": syntax error
One possible problem is my nook never goes into USB Mode now when I plug it in, uninstalled usb componets and will reboot to see if that works....
Had the same problem
I've definitely experienced the same issue after running the script.
After reading this post I checked my own settings.db and found that my device_provisioned variable was set to 0. here's how I fixed mine... sort of.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db
C:\temp>sqlite3 settings.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from secure where name='device_provisioned';
10|device_provisioned|0
sqlite> update secure set value=1 where name='device_provisioned';
sqlite> .q
c:\temp\adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
In the end I seem to have gotten more control of my nook button, but I still seem to have problems getting the SoftKeys 2.0 to work correctly. Right now it does function as a proper home button, and returns me to ADW launcher, or launches the explode desktop view when I'm in ADW.
Still fudging with the settings to see if I can get it back to normal
I can't get any of this to run correctly, besides mine looks to already be on 1 in setting db.
I am still not able to get Nook into USB Mode.
If I wipe this thing what is the easiest way to restore all my App's, some that were purchased?
This isn't the Q&A section
{
"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"
}
Apply your question(s) in the proper sub-forum, or it might result in a temporary vacation
Mikey1022 said:
This isn't the Q&A section
Apply your question(s) in the proper sub-forum, or it might result in a temporary vacation
Click to expand...
Click to collapse
Well I thought this was the proper section at the time I have since corrected the problems so you can lock/delete if you wish.
Just adding my appreciation for this fix, I had the same issue and was able to fix it. Damn! I wish I had searched the forum earlier, I went from 1.00 to 1.01 and thought I was fubar, went thorugh the entire process again and loaded apps and then I finnaly search for the issue..
Does anybody get the prompt for authorizing the PCs that connect through ADB?
According to several articles (example here), whenever a computer connects it's RSA key will be validated and a prompt will appear on the device if it's still not registered:
{
"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"
}
I'm running 4.2.2 (10.3.A.0.423 Generic ES) and never get this prompt, despite using the latest ADB version (1.0.31).
/data/misc/adb/ exists on the device but is empty, BTW.
Can anyone else confirm this, or preferably a way to activate the behavior?
UPDATE
I found the problem :victory:
On the /default.prop file (which is part of the kernel and therefore can't be manipulated directly), there's this:
Code:
ro.secure=1
It controls whether adb connections will run as root (if 0) or as shell (if 1).
But there's an additional parameter that should be there:
Code:
ro.adb.secure=1
which if set, triggers the standard behavior described before - prompting for a visual confirmation of the RSA key of the incoming connection.
Once I added an init.d script with
Code:
[COLOR="SeaGreen"][B]setprop ro.adb.secure 1[/B][/COLOR]
everything is working properly.
Bump!
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Sent from my C6603 using Tapatalk 2
kingvortex said:
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Click to expand...
Click to collapse
I had tried all that
After digging into the code I found the solution, check the OP.
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Sent from my C6603 using xda premium
gm007 said:
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Click to expand...
Click to collapse
It would be useful if I had stumbled on that earlier
Actually, I want mine to be "secure" in the sense that it only allows adb connections from my computer, and prompt for any new ones.
That's what the ro.adb.secure is for.
As for the uid of the shell once you're connected, I want to be root and therefore ro.secure=0.
But since I'm running the stock kernel and can't unlock my bootloader to run a custom one, I use an insecure adbd binary, instead of changing ro.secure to 0.
I got this error I searched a lot before I found the solution. I'll post it here in case some people needs it.
I've just installed CM12 nightly and when I tried to install an APK from my SDCARD, I got an "Application Not Installed" error without any error number.
"unknown source" is turned on in the security setting.
Tried via ADB install and got: [INSTALL_FAILED_CONTAINER_ERROR].
Logcat was showing:
Code:
E/Vold ( 109): Error creating imagefile (Read-only file system)
E/Vold ( 109): ASEC image file creation failed (Read-only file system)
W/Vold ( 109): Returning OperationFailed - no handler for errno 30
The solution was to go to Settings -> Applications -> Menu -> Preferred install location
And change "Let the system decide" to "Internal device storage".
Everything is working fine now.
Hope it will help some others !
I dont have this option under settings -> apps. Please hlep
JoJo2211 said:
I dont have this option under settings -> apps. Please hlep
Click to expand...
Click to collapse
Post a screenshot of your Settings > Apps screen.
also need help, cant install apks, and i dont have this option in settings/apps, please help
Hey, No Preferred Install Location, Please Help.
{
"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"
}
---------- Post added at 10:11 PM ---------- Previous post was at 10:03 PM ----------
Primokorn said:
Post a screenshot of your Settings > Apps screen.
Click to expand...
Click to collapse
I cannot upload any images , they dont allow me to
I know it's been a while, but I want to add to this thread in case someone else comes across it and is having a similar issue. Based on what I've pieced together, this is what's happening. CM12 did away with the option to select the default install location for apps. This used to be under Settings -> Apps -> 3-dot overflow menu.
Now, that option is gone and in the background CM12 has set the default install location to be "Let the system decide." Of course when the apps are large enough, it wants to move them to the SD card and that becomes a problem when the device does not have an SD card or is out of space.
This bug also affects some large apps from the Amazon appstore and no amount of cache or data clearing and rebooting is going to resolve it. The simple and only solution I ever found, was to somehow tell the system to install all apps to "Internal storage." Otherwise you'll see a lot error codes 907 and 963 along with the dreaded "Application is not installed" message.
Since we don't have the option to do so via the menu we have to do it via a terminal emulator or adb. I believe they both require root, but I could be wrong on that one. The code would be as follows:
Code:
adb shell
su
pm set-install-location 1
Obviously skip the first line if you're entering into a terminal emulator. I hope this helps those who are still running into this bug that still rears its ugly head from time to time. Cheers.
Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
{
"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"
}
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
RealSykes said:
Hello XDA Community,
As a preface, I'm an idiot. I figured I could dabble around with different ROM's and through all of my insightful wisdom appear to have hard-bricked my phone in the process. As seen via the attached photos I at one point was able to boot my phone into Fastboot > TWRP > Flash Rom > Off to the races.
Now the phone will not boot period. When plugged into an outlet the blue indicator atop the camera doesn't even blink a blue color. Moreover, when plugged into my PC it is not found via my PC "Devices & Drives" folder. However, when I open the MiFlash tool the phone reflects as "COM3" whereas before it would show what I assume to be the unique ID for the phone.
I came across another thread titled "[EDL Flash] How to fix your hard brick [Mi 9T Pro/K20 Pro]" but even here it mentions the phone booting and displaying some type of error message.
Anyhow, this is a long shot but figured I'd give it a go and see what comes of it.
Thanks for any insight and for simply taking the time to read my post.
Image of MiFlash reflect COM3:
Update 1 - I've tried to flash a ROM and get error message: "Object reference not set to an instance of an object". Here:
Click to expand...
Click to collapse
That error message is some sort of program error:
https://stackify.com/nullreferenceexception-object-reference-not-set/
I'm no expert on c# programming so cannot say why that error occurred.
You could try to use adb commands, see if adb picks the device up, when you say it does not power on at all, does the phone go into bootloader mode? (, power and volume down)
MOD EDIT: QUOTE REMOVED
try it under windows 7 computer, preferably laptop with usb 2.0 port. It can recognize the device, if not, and standart unbrick method doesnt work even under w7, then you have to use test points on motherboard, edl account is needed for that, idk how to get it as i tried to get it several times but received only mails in chinese so i gave up, not paid too much to bother so much time on fixing one phone.
There is even modified version of flash tool that is believed to authorize any account logged in bypassin the authorize account error i can provide a link for you but not tested if its actually working.
MOD EDIT: QUOTE REMOVED
i actually did research about this while ago and it might help the guy unless he is willing to pay some russian scammer 60 bucks via teamspeak that is doing this stuff from either stolen or modified authorized account which i can provide link to @RealSykes pm me if u wanna try and give it a go, u can pay russian scammers few bucks in the end if all tries fails there is even command for adb if you have unlocked bootloader that will enter edl without test pin points, but u need to enter fastboot mode first which im assuming u cant from what i have understand.
Kind of important question, what did you do to screw up your phone? So others know what not to do.
https://c.mi.com/thread-2173190-1-0.html follow steps on this site if you already didnt find this by yourself, maybe it can give you and permission to flash, as it appears for some people it actually gave it. tried it myself for you now, and it appears my account is somehow ready to flash (authorized) now, but, i applied some time ago for actually get it, so, it can be different for you.
RealSykes said:
"Object reference not set to an instance of an object"
Click to expand...
Click to collapse
An Object is an instance of a Class , it is stored some where in memory. A reference is what is used to describe the pointer to the memory location where the Object resides. The message "object reference not set to an instance of an object" means that you are referring to an object the does not exist or was deleted or cleaned up. It's usually better to avoid a NullReferenceException than to handle it after it occurs. To prevent the error, objects that could be null should be tested for null before being used.
if (mClass != null)
{
// Go ahead and use mClass
mClass.property = ...
}
else
{
// Attempting to use mClass here will result in NullReferenceException
}
hardbrick and button not press
Need Guideline stepbystep pls.....
{
"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"
}
Manjaro is a GNU/Linux distribution utilizing technologies like libybris and Halium to run a Linux distribution on Android devices.Before starting the installation I should add that Manjaro libhybris is very experimental and it might break at any time so its more of a toy. If you want a smooth and more stable experience that can be daily driven, take a look at Droidian. Droidian on onclite
Requirements
Android 9 firmware for your device:
Redmi 7 onclite: LINK
Files
Download the latest rootfs: Manjaro-ARM-phosh-google-sargo-XXXXXXXX.zip. (Yes my work is based on google sargo and i used that as a base mostly because i also own a sargo so i experimented with that first then based my work off of that)
Download the adaptation package: adaptation-manjaro-onclite.zip.
Download TWRP or any recovvery: TWRP.img
Installation:
Boot into fastboot and run: fastboot flash recovery TWRP.img
Reboot into recovery: fastboot reboot recovery
in recovery wipe data and system.
Go into sideload mode and run: adb sideload Manjaro-ARM-phosh-google-sargo-XXXXXXXX.zip
After it's done go back into sideload mode and run: adb sideload adaptation-manjaro-onclite.zip
Now reboot.
The first boot will take a while.
NotesDefault passwordThe default password is 123456.
APNMobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after callsData connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Out of storageBy default when flashing Manjaro it allocates 8GB of storage to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
SSH accessconnect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
ApplicationsYou can find a list of mobile-friendly Linux applications at LinuxPhoneApps
What Works
Notification LED, Vibration, Carrier info, Data connection, Pin unlock, SMS, Battery percentage, Online charging, RTC time, SDcard, Shutdown, Reboot, Bluetooth, Flight mode, Hotspot, WIFI, Proximity, Rotation, Touch screen, Waydroid, Brightness
What doesn't work
GPS, Fingerprint, Offline charging, Dual SIM, Auto brightness, Torchlight, Audio, Calls, Audio routing, Voice calls, Volume control, Earphones, Loud speaker, Microphone,
Notes
Settings app does not open from the app drawer. If it has been opened from the app drawer it must be killed from the terminal.
To open the settings app run: GSK_RENDERER=cairo gnome-control-center
The fingerprint sensor acts as Enter keyboard key.
Final Notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Device specific telegram group: @Barrys_crib.
Thanks to the Manjaro team, Droidian Team, bibarub, supirlelik96 and TheKit for helping out to make this happen.
All the sources are available at
https://github.com/droidian-onclite/
Bry
But I want to know what is adaption package and how it works
Bry
But I want to know what is adaption package and how it works
Bro
But I want to know what is adaptation package and how it works
Sorry i sent it actually one time i dont know why it gone 3 times maybe the issue with network
the_arxyn said:
Bry
But I want to know what is adaption package and how it works
Click to expand...
Click to collapse
adaptation package is a sideloadable package containing all the binaires, scripts, configurations and other files needed to get the device to a working state. users flash the adaptation package once and that adaptation package installs a package as an example a deb package in debian which contains all the fixes and a repository for the user to update over the air via the package manager. so they do not have to flash anything else later they can just use the package manager and update and system will update just fine.