This is an extension of my Android Oreo Pixel Mod thread, found here https://forum.xda-developers.com/nexus-6p/themes-apps/zip-android-oreo-pixel-mod-t3661388
This thread is for the users who want the Pixel Mod but also the ability to use Substratum. Why does my original mod break substratum? It modifies the framework-res.apk. The pixel no longer gets it's features from a modified framework-res.apk. It gets it from a theme. Making a pixel mod work with Substratum now requires making the 6P do the same thing as the Pixel. However, to simplify the mod I mimiced the features by modifying the framework-res.apk. This breaks Substratum. Following this walkthrough will enable the Pixel Theme on your 6P without modifying your framework-res.apk. Exactly how Google does it with the Pixel. (Exciting right?) This will allow the use of Substratum. This is what I am using and I can verify that substratum works.
Here'es the first thing: The files that you will need.
1)My original Pixel mod (flashable) -- https://www.androidfilehost.com/?fid=961840155545590555
2)Stock framework (flashable) -- https://www.androidfilehost.com/?fid=673368273298981491
3)Pixel Theme files (NOT flashable) -- https://www.androidfilehost.com/?fid=889764386195925591
4)You need to be ROOTED
5)You need a file manager that has root functions and can edit file permissions. (I.E.: Amaze File Manager, EX File Explorer, MT Manager)
Here are the steps. This is as simple as I can make it at the moment. It's not too complicated, but if you are a beginner with this stuff make sure to make a back up. Even if you're not. Make a backup. You are responsible for anything that happens to your device and making a backup will save everybody.
Step 1) Download all files onto your internal storage
Step 2) Extract the contents of "NO FLASH Pixel Mod + Substratum.zip". You should have a build.prop file and a folder called "overlay"
Step 3) Move that folder in your Vendor folder. Leave behind the "build.prop" If you go to your root directory you should see the folder "Vendor". Along with folders like "sys" and "system". But you don't want those. You want "Vendor".
Step 4) Make sure the permissions are accurate. The 2 apk files that you will find inside the "overlay" folder (the framework file and the pixel.apk file you'll find in the "pixel" folder inside the "overlay" folder) are set to 644. The folders "overlay" and "pixel" ("pixel" is found within the "overlay" folder) needs to be set to 755.
Step 5) Edit the build.prop file found within your vendor to include the lines that are found in the included build.prop (See footer)
Step 6) Reboot into TWRP
Step 7) In this order flash "Android OPR6 Pixel Mod 6P.zip" and then "Stock Framework.zip"
Step 8) Reboot
Step 9) If you don't see Round Icons you may need to clear Pixel Launcher Data
If SystemUI is crashing after reboot, reboot into TWRP and mount the vendor partition. Then delete the overlay folder and that'll solve the issue
If you followed those correctly you should have now have a Pixel Theme (Accent color, Night Mode, and Round icons) with compatibility with Substratum.
*footer*
ro.opa.eligible_device=true
ro.com.google.ima.theme=5
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Suhas_JS said:
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Click to expand...
Click to collapse
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
krisyarno said:
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
Click to expand...
Click to collapse
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Definitely. I'm redoing the steps myself and I'm running into a weird bump. I'm going to revise it a little maybe. Definitely a good idea to reflash the vendor and take another shot though!
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Try setting build.prop to 600 instead of 644
revanmj said:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Click to expand...
Click to collapse
I believe so. Placing the overlay folder found from Pixel's vendor to the same place on the 6P should give the 6p the ability to use all the overlay service commands
krisyarno said:
Try setting build.prop to 600 instead of 644
Click to expand...
Click to collapse
Downloading the latest vendor image. Will keep you updated....
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
Thanks!
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
I appreciate your help throughout all of these releases
krisyarno said:
I appreciate your help throughout all of these releases
Click to expand...
Click to collapse
Pleasure's all mine. When we can not do something on our own, the least we could do is to assist someone who is more capable.
Coming back to the point, I am using Amaze & EX Explorer to replace the said files.
Strangely, I am getting various error messages, like "Insufficient space".
Also, everytime I try and copy a folder, it wont show up until I restart the device.
I know this is little too much for you to imagine. I'll may be post a short GIF in some time for you to get a gist of the issue.
Thanks and apologies for the story.
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Tested, substratum works but no night light
syfo said:
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Click to expand...
Click to collapse
Wich permission did you use for the build prop? 600 or 644?
Sent from my Nexus 6P using XDA-Developers Legacy app
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
bigcelo75 said:
Wich permission did you use for the build prop? 600 or 644?
Click to expand...
Click to collapse
600
Suhas_JS said:
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
Click to expand...
Click to collapse
I don't believe there is a need to wipe if your phone factory reset itself. There may be a chance that it didn't successfully factory reset. I would reflash stock system.img and stock vendor.img. That should undo everything and let you boot up
noooooo said:
Tested, substratum works but no night light
Click to expand...
Click to collapse
Same here. Is there a fix for that yet @krisyarno?
Sent from my Nexus 6P using XDA-Developers Legacy app[/QUOTE]
Sent from my Nexus 6P using XDA-Developers Legacy app
Not to contradict OP but I used 644 for files (.prop and apk's) and 755 for folders. Also I don't know if it helps but at first I didn't have night light and installed the "pixel" apk (inside the overlay folder), rebooted the device and voila! After that just cleared pixel launcher cache and that took care of the round icons.
Related
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"
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...
** Designed for stock Moto 98.72.22 and 98.72.22-based ROMs **
** FOR OTHER ROMS and updated stock, see post #7 **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default = same end result as SQL hack.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
0. Backup just in case!!
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Ismokel said:
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Click to expand...
Click to collapse
JB 246 98.72.22? I'm assuming you used a root explorer due to the FC. I recommend using Safestrap's built-in file manager (see the updated instructions).
I could also make a flashable ZIP to mitigate user-error if there is demand for it.
The last issues you mentioned are unrelated to this. The modified APK is exactly the same as the original, except for a single byte (1 -> 0) and deodexed. Oh, and a "false" to "true" in the manifest so we could manually clear data, but that didn't work out. You can decompile and compare yourself
Same issue here as Ismokel. It might be a signing issue, as I saw the same thing occur when I tried doing the mod myself and was experimenting with the different options for signing. It worked for me when I left the existing signature.
I would post my modded version, but I need to make one with only that mod first, as mine has mods to change other defaults as well.
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
You mentioned that yours worked for you without wiping data. Did you change default_entitlement_check in the xml resources or did you change something else? I was only interested in this mod to change the default and not the existing setting, but I'm still somewhat curious.
progrockguy said:
** Designed for stock Moto 246 (JB 4.1.2) and 246-stock-based ROMs **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
Click to expand...
Click to collapse
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
ShadyDreamer said:
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
Click to expand...
Click to collapse
Whoops!! 98.72.22 is the base I used. If you took OTA updates, that could explain the boot loops. See below on how to DIY
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
Brolzy said:
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
Click to expand...
Click to collapse
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
My safestrap instructions will work on your newly modified APK. (If you're going to try replacing via root file explorers, I suggest an overwriting Paste. That way you'll keep permissions in case android crashes and hot reboots. Do not delete, *then* paste. It'll likely crash before you can set the permissions.)
Good luck!
progrockguy said:
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
Click to expand...
Click to collapse
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
If you are using adb from a computer connected by USB to copy and install the apk, after using su you can use the stop command to close all apps, then you can safely move, rename, replace, or delete system apps without it crashing and rebooting. Just make sure you have it in the proper state before you reboot. If a prompt to allow su from adb comes up on the phone, be sure to allow it with no time limit in case you need to use su again before you use adb reboot to restart the phone.
ShadyDreamer said:
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
Click to expand...
Click to collapse
Curious, where did you get your APK from? Because stock is odexed.
My file also had a manifest edit (which didn't work out), but I doubt that's the issue since it works on two of my Bionics.
When I quoted the part I was replying to, I included your "All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM." line in the quote for a reason. I did that part.
If you accidentally deleted an application that you wanted later or just simply desire the files for development of custom TouchWiz based roms (or any other reason) and don't want to fish for them on a stock device, then here they are
These files are from the unmodified but rooted NG2 software. The only modification was that the device was rooted, so obviously @Chainfire's supersu is not part of the original files.
[sph-l720-system-app.rar - RAR archive] [MD5=(pending)] [File Size: ]
for all files in the /system/app directory: DOWNLOAD HERE
[sph-l720-system-priv-app.rar - RAR archive] [MD5=(pending)] [File Size: ]
for all files in the /system/priv-app directory: DOWNLOAD HERE.
**EDIT **
Note these are NOT flashable ZIPs. These are archives of each directory for cherry-picking the bloat apps.
**EDIT 2014 OCT 25TH***
Will not be making flashable ZIPS. If you so desire to do so, go for it. I now have the S5 and no free time as it is.
typefortytardis said:
If you accidentally deleted an application that you wanted later or just simply desire the files for development of custom TouchWiz based roms (or any other reason) and don't want to fish for them on a stock device, then here they are
These files are from the unmodified but rooted NG2 software. The only modification was that the device was rooted, so obviously @Chainfire's supersu is not part of the original files.
for all files in the /system/app directory: DOWNLOAD HERE
for all files in the /system/priv-app directory: DOWNLOAD HERE.
Click to expand...
Click to collapse
Thanks for this brother & correct me if I'm wrong, but shouldn't this be in the 'Themes & Apps' section?
Parkourkid93 said:
Thanks for this brother & correct me if I'm wrong, but shouldn't this be in the 'Themes & Apps' section?
Click to expand...
Click to collapse
You know what maybe. I'm sure anyone whom would use this would be for modding and making of TouchWiz based roms, but if this is the wrong place for this I do apologize.
typefortytardis said:
You know what maybe. I'm sure anyone whom would use this would be for modding and making of TouchWiz based roms, but if this is the wrong place for this I do apologize.
Click to expand...
Click to collapse
No big deal, most likely if it belongs in another section a mod will let inform you that its being moved, I was just curious, just downloaded, going to flash a tw ROM & test a few of these , did you pull these yourself by the way?
Parkourkid93 said:
No big deal, most likely if it belongs in another section a mod will let inform you that its being moved, I was just curious, just downloaded, going to flash a tw ROM & test a few of these , did you pull these yourself by the way?
Click to expand...
Click to collapse
Yes I did. I simply took them from a stock rom. Which I'm sure anyone could do - just I know I never thought to until i'm at a point where I have no choice but to flash back to stock. So now everyone has them handy.
They are simple file copies. It's not a flashable zip. Extract and use adb to push or simply copy to your device. Again these are mainly for those who are building custom TouchWiz based roms and want to include some of the bloat - but can be used by those who need some of the applications for whatever reason. But they aren't flashable and some probably will have to be replaced using adb push.
I will try to work on a flashable zip but that will take me some time. Also a flashable zip file doesn't help those whom say only want Sprint's Zone app for example but don't need the rest of the bloat. Just saying. But will post when I have made flashable zips for all-in-one bloat.
typefortytardis said:
Yes I did. I simply took them from a stock rom. Which I'm sure anyone could do - just I know I never thought to until i'm at a point where I have no choice but to flash back to stock. So now everyone has them handy.
They are simple file copies. It's not a flashable zip. Extract and use adb to push or simply copy to your device. Again these are mainly for those who are building custom TouchWiz based roms and want to include some of the bloat - but can be used by those who need some of the applications for whatever reason. But they aren't flashable and some probably will have to be replaced using adb push.
I will try to work on a flashable zip but that will take me some time.
Click to expand...
Click to collapse
Okay good, just making sure & I know, I barely use abd plus i'm already laying down, just got done playing Diablo 3, so I'm just going to push em using ES File Explorer lol
Parkourkid93 said:
Okay good, just making sure & I know, I barely use abd plus i'm already laying down, just got done playing Diablo 3, so I'm just going to push em using ES File Explorer lol
Click to expand...
Click to collapse
Someone else chime in here if this is wrong:
but... some of the touchwiz apps will refuse to work thru a simple file copy from within the device. If that happens, some of it - keyword "some" will be fixed by using a custom recovery like philz-touch or CWM or TWRP and clearing both cache and dalvik-cache after doing the file copy - at least that worked on 4.3 and 4.2.2. But KitKat has changed some things so I'm not sure.
If anyone else has dealt with this, please do comment....
When pushing .apks with ES or Root Explorer (my personal favorite) you do need root and need to place in the correct folder (system/app, system/priv_app, or system/lib if it's a lib file) and be able to change permissions - usually to rw, r, r.
... So definitely pay attention where you copy the files from and where ya put 'em.
If not done, they will not work.
Hope this helps someone!
Just wanted to let those of you whom are watching this thread know that due to personal stuff I have no time to make flashable ZIPs anytime soon but if anyone wants to take a stab at it before I get to it then be my guest
Will this zip file work on ASOP rom?
Sent from my SPH-L720 using XDA Premium 4 mobile app
axs3543 said:
Will this zip file work on ASOP rom?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No most of these apps need a TW framework.
Sent from my SPH-L720
Maybe I am missing it, or it's named something funny..but I am not seeing the stock messaging app in either of those zips. I apologize if it's right in front of me, but I don't see it!
Edit: I'm an idiot, I found it. SecMMS.apk. But it wont install, just says "App was not installed." Why would that be?
Did you manually push it to system/priv-app folder, set permissions, and reboot?
Don't try to just click on it and install via context menu
Sent from my SPH-L720 using XDA Free mobile app
Recorded Video Playback
I get "Unable to play video" message when I try to play back a video I recorded (I can play it on my computer)
carefree12 said:
I get "Unable to play video" message when I try to play back a video I recorded (I can play it on my computer)
Click to expand...
Click to collapse
Are you using a TW based rom? What file format is the video in? Will it play in another app, such as MX Player (great app btw I prefer it to any stock video app - I delete them)?
mxmr said:
Did you manually push it to system/priv-app folder, set permissions, and reboot?
Don't try to just click on it and install via context menu
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Yes I copied it to the system folder and then tried to install it. What do you mean by set permissions? For arguments sake I gave it rwxrwxrwx permissions and it still will not install.
vadyr56 said:
Yes I copied it to the system folder and then tried to install it. What do you mean by set permissions? For arguments sake I gave it rwxrwxrwx permissions and it still will not install.
Click to expand...
Click to collapse
Make sure you copy it to /system/priv-app folder, and set permissions to rw-r--r-- (644) NOT rwxrwxrwx, otherwise it will not work.
Reboot and you should be good to go.
mxmr said:
Make sure you copy it to /system/priv-app folder, and set permissions to rw-r--r-- (644) NOT rwxrwxrwx, otherwise it will not work.
Reboot and you should be good to go.
Click to expand...
Click to collapse
Rebooting and trying now, hoping my error with the permissions was the issue. Also, I'm not finding the stock calculator app in these archives. I may be being stupid again though, I apologize if that's the case.
Edit: No luck with the push, permissions, reboot attempt. I don't get what I could be doing wrong. And I'm definitely in the correct folder.
vadyr56 said:
Rebooting and trying now, hoping my error with the permissions was the issue. Also, I'm not finding the stock calculator app in these archives. I may be being stupid again though, I apologize if that's the case.
Click to expand...
Click to collapse
I attached the stock calculator app to this post
Edit: No luck with the push, permissions, reboot attempt. I don't get what I could be doing wrong. And I'm definitely in the correct folder.
Click to expand...
Click to collapse
One more time verify permissions are set correctly..they should match all of the other apps in the folder. Reboot to recovery and wipe cache/dalvik and try rebooting. Hopefully that works.
mxmr said:
I attached the stock calculator app to this post
Click to expand...
Click to collapse
Oh geez yup I'm an idiot again, thank you for providing that. Not sure what I'm doing wrong with the mms app though. Wondering if I should just install the bloated ROM and debloat it myself
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