Database Develop

[MOD] Resolution (dpi) changer *now with zips for all (hopefully) legend ROMs*

I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows

Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse

hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager

Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...

TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!

No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.

nice job
thanks bro

nice
spare parts is also in neonmod

xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!

xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App

Wow, really cool mod Love it!
Good job!

Cool, glad you like it

Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.

Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...

SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App

i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/

TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.

Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

[Q] Backlight of Softkeys

Hi there!
I want to disable the backlights of the softkeys, without installing an ad-filled apk.
I have installed Slimrom 4.3 from maclaw.pl and the setting to turn backlight off is invisible.
If you go with an rooted file explorer to /sys/class/leds/brightness and switch the value to 0, the backlight immediately turns off.
But if u restart the phone the value is changed everytime to 1 and the Backlight is back on.
So i thought i could write a script, that do this job for me., everytime i start my phome. The script is in the attachments.
Can anyone check if the script is okay? I dont want to brick my phone
And Do you know where the autostart folder for android devices is (like in windows), ive read something about kernel init or something.
And if i want to make a flashable zip out of this script, How to make it? because i dont want everytime i flash an update to work in the system.
Thanks for your time

Go to system settings-buttons-backlight & disable it. If that option it's not present on slim, simply download this. Don't mess with any system file cause this ain't a xperia phone:laugh:

Thanks, but my device is not listed under supported devices in this app and i dont want to keep a 3rd party app running that increases the battery drain and takes ram away. i prefer a little script at system start.
And no the option is not listed in the settings.

kinqme said:
Thanks, but my device is not listed under supported devices in this app and i dont want to keep a 3rd party app running that increases the battery drain and takes ram away. i prefer a little script at system start.
And no the option is not listed in the settings.
Click to expand...
Click to collapse
FYI, I'm using bln app & doesn't drain my bat nor ram (on cm11). Have a nice day

Okay i found that folder it is localized in /system/etc/init.d
I copied the file to there and it is workimg, on every restart the buttons keeps off.
But how to make a flashable zip with that file? is it enough to create a zip with the folder system and its contents are only th underfolder and the file?

kinqme said:
Okay i found that folder it is localized in /system/etc/init.d
I copied the file to there and it is workimg, on every restart the buttons keeps off.
But how to make a flashable zip with that file? is it enough to create a zip with the folder system and its contents are only th underfolder and the file?
Click to expand...
Click to collapse
Search on xda how to make it & if you sure it works I'll add it to my FAQ

Simple flashable fix for that http://www.mediafire.com/?dcq8si0xa1s348j

PolishVodka said:
Simple flashable fix for that http://www.mediafire.com/?dcq8si0xa1s348j
Click to expand...
Click to collapse
I asume it works on all maclaw roms (cm11) too, right!? Can I add it to my FAQ here. Of course I'll give you the proper credits on the special thanks section.

Here we go.
One zip to disable them and one to undo the patch.
thanks for your time

Can I add it to my FAQ?

Of course then other people who has the same problem can solve this problem

kinqme said:
Here we go.
One zip to disable them and one to undo the patch.
thanks for your time
Click to expand...
Click to collapse
Don't think so is good script, because when you got a notification than BLN turn on lights again and will be stay it on to second boot.

sorry my very first try.
i will look on my device, if this happens to me too

The only problem i had was with whatsapp, if u get a message there, the light keeps on till restart.
But in settings - notifications - lights in whatsapp u can turn off the notification lights and then the problem is solved. ( standard is white )
Tahnk you polishwodka

kinqme said:
Here we go.
One zip to disable them and one to undo the patch.
thanks for your time
Click to expand...
Click to collapse
Thanks

Working screen mirroring on rooted devices

Note: This solution only works on MK2 (4.3)
I have been researching a problem I have had on my SPH-L720 with custom ROMs where screen mirroring with my Samsung TV would not work. Based on a thread I found, I have solved my problem and wanted to share with others who may have a similar problem.
In my searching, I stumbled upon this thread: http://forum.xda-developers.com/showthread.php?p=50597640
The OP of that thread had several applications that he froze, and made some changes to the Build prop file, and the WFDConfig.Xml file. In the end, I only made one change to the WFDConfig.Xml file, and my screen mirroring started working.
1. Edit /system/etc/WFDConfig.Xml, and make the following change:
Code:
<HDCPValid>0</HDCPValid>
2. Reboot phone, and profit!
My setup is MF9 bootbootloader, NAE baseband, Negalite MK2 ROM.
If I have time this weekend, I will upgrade to Negalite NAE ROM, and test it there.
I take no credit for this solution, and credit the original thread above.
Hope this helps someone!

What program did you used to edit this? sorry noob here
Sent from my SPH-L720 using Tapatalk

Wow, thanks...I've been looking for a solution to this for awhile too. I made the changes on my stock rooted MK2 phone, and mirroring works great!
What program did you used to edit this?
Click to expand...
Click to collapse
I copied the file to my PC and used notepad++ to do the edit. Then copied the file back to the system/etc folder on the phone. You'll need root and a root-enabled file manager to write to the system folder. I used Root Browser (https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree), but there are several apps that will work.

ekco06 said:
What program did you used to edit this? sorry noob here
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
There are a couple of different ways to edit the file. For me, I used Root Explorer, navigated to the file, long pressed the file name, a menu came up and I chose 'Open in Text Editor'. From there it asked if wanted to mount the filesystem as r/w, I chose yes, edited the file, and saved it.

I couldn't find this line in my file, were you on Kit Kat or JellyBean?

For some reason I don't have that line in my WFDConfig.xml, I am on Baseband NAE, Negalite-wonderom-nae-r11, MF9 Bootloader. Any ideas?

gamester_47 said:
For some reason I don't have that line in my WFDConfig.xml, I am on Baseband NAE, Negalite-wonderom-nae-r11, MF9 Bootloader. Any ideas?
Click to expand...
Click to collapse
I just upgraded my phone to the exact same setup. When I look at the config file for NAE, it is a little different. But, I *think* the correct change would be:
Code:
<ContentProtection>
<Valid>1</Valid> [B]<------- Try changing this to 0[/B]
<Version>WFD_HDCP_2_1</Version> <!-- Valid values WFD_HDCP_2_0 and WFD_HDCP_2_1 -->
<CPPort>6789</CPPort>
<EncryptAudio>0</EncryptAudio> <!-- Valid values 0 / 1 to indicate Audio encryption or not -->
</ContentProtection>
I have made that change to my phone, but I am at work now so I will not be able to test this until later this evening. I will post my results when I get home.

cruise350 said:
I couldn't find this line in my file, were you on Kit Kat or JellyBean?
Click to expand...
Click to collapse
The fix in the OP is for 4.3 Jelly Bean. I just upgraded to 4.4 KitKat, and will have to test my theory on which setting to change when I get home.

Thank you!!! worked !!
man i was breaking my head on this one.. and soft bricked the phone a couple times trying to fix this, and to think the fix was so damn easy! :good::good::good:

Well, bad news on NAE (4.4.2) - the fix does not work. Under <ContentProtection>, I tried setting <Valid> to 0. When I mirror, I get a black screen with a message that says "Unable to enable Screen Mirroring. HDCP is not supported by the connected device" I can hear the sound from the phone on the TV, but no picture.

I just updated the OP that this only works with 4.3. I have gone back to Negalite MK2 ROM, and plan to stay there until a solution for NAE is found.
Does anybody have any other ideas on how to make screen mirroring work in 4.4.2?

Well i did update to NAE and tested the "contentprotection" value to 0 , also changed the name from Valid to HDCPValid and nothing , the TV says " the dive supports HDCP ? " or something like that .
under Developer options on KK now has HDCP checking settings. Tested all 3 options with Valid=0 and valid=1 and nothing.

hahansen3 said:
There are a couple of different ways to edit the file. For me, I used Root Explorer, navigated to the file, long pressed the file name, a menu came up and I chose 'Open in Text Editor'. From there it asked if wanted to mount the filesystem as r/w, I chose yes, edited the file, and saved it.
Click to expand...
Click to collapse
Ok thanks im about to give it a go ill post my result in a bit. Thanks in advance
Sent from my SPH-L720 using Tapatalk

? nothing happened. .smdh.
Sent from my SPH-L720 using Tapatalk

Anyone figure out how to get this working in 4.4.2?

jdip said:
Anyone figure out how to get this working in 4.4.2?
Click to expand...
Click to collapse
So will this work with a non Samsung (a Sony) TV?
Thank you!

Can't find WFDConfig.Xml file in system/etc directory

My screen is morroring great, but no audio
The ""0"" value worked great, I can see my S4 Mini Screen on my Samsung Smart TV but audio only comes from my phone speakers. I am confused. Any help would be appreciated.
Juan Pablo, from Peru

This works for 4.4.2 screen mirroring with root/custom recovery
http://forum.xda-developers.com/showthread.php?t=2621550
(Hdcpoff_sd800_4.4.2 file 3rd from bottom)
Extract and move ".so" file to system/lib then set permissions

[TWEAK] Remove Brightness Slider from Notification Panel

This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.

guyd said:
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
Click to expand...
Click to collapse
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.

Yoshi910 said:
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Click to expand...
Click to collapse
I can mod systemui.apk to remove them, if you want it.

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol

guaneet said:
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
Click to expand...
Click to collapse
haha, yea im not a fan of having a ton of threads all with mostly the same thing. ill see what i can do about the toggles, i can for sure get rid of the other stuff.

You can also simply install Lux and turn off its persistent notification

Could this be used to do other tweaks like remove icons/clock from the status bar?

mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.

teiglin said:
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
Click to expand...
Click to collapse
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.

mikeyinid said:
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
Click to expand...
Click to collapse
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Edit for basic instructions:
Use a root-enabled file manager or console to replace /system/priv-app/SystemUI/SystemUI.apk with the attached file, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz. Make sure the permissions of the new SystemUI.apk are rw-r--r-- (chmod 644 /system/priv-app/SystemUI/SystemUI.apk at the console). Reboot and enjoy.
Caveat: you may not be able to swipe away notifications from within the region previously taken up by the sfinder/qconnect bar.

Great! Can also be done via adb:
Code:
adb shell settings put system notification_panel_brightness_adjustment 0

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Thanks! Works great.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
How would you get it to work, I tried to install it but it won't install.

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Worked fine, thanks !

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons

EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
v2.2v said:
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
Click to expand...
Click to collapse
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
That worked flawlessly, thank you.

teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
perfect! thank you so much

teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...

Painless001 said:
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Click to expand...
Click to collapse
BINGO. Yea i forgot to mention that in my response, as well. Always fix permissions