Related
Created a new thread to save you some effort
MUST be on JB 4.1.2 or earlier and rooted, if not
You can get JB 4.1.2 from Telstra, look in Android development and flash it via RSD Lite, You must have an alternative input method (I use gmd gesture control), not free but do not consume any screen space; Now add to the buil.prop at the end (qemu.hw.mainkeys=1) and U will have the status bar but not the navbar and no fc.
I have some issues with menu action (auto hiddes and must retry), solved with cm 10 instead of Telstra ROM, little more batt consumption and no blutooth music at the moment.
UPDATE: No need to use another ROM, In Telstra ROM go to config in Your phone, developer options, and check "Disable HW overlays", Ready!
You can use other ROM (4.1.2+) if U want, I like Telstra Rom cause it have good battery and all features in your cell phone works.
Can you expand on what issues you had after making the edit in rsd lite?
Edit: pls disregard. My tired morning brain was thinking SQL lite.
Sent from my DROID RAZR HD using xda app-developers app
Where are you finding Telstra 4.1.2 for the Razr HD? I've done Google searches and found lots of dialog but no downloadable file.
How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png
Here is the link to Telstra Rom
lesdense said:
Where are you finding Telstra 4.1.2 for the Razr HD? I've done Google searches and found lots of dialog but no downloadable file.
Click to expand...
Click to collapse
Here is the link, I had to change two files because I live in Mexico and my carrier is Telcel, there is the explanation.
http://forum.xda-developers.com/showthread.php?t=2054906
Gesture Control
krucifix85 said:
How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png
Click to expand...
Click to collapse
Yes look good, but I like GMD gesture control because you can use gestures like an iPad or iPhone, no need to a NavBar tu pop up touching some place in the screen, well the matter is we have options
It's not a good thing to do. Next day one, you miss the bar.
correct ewsnadmy
krucifix85 said:
How do you go about bringing the bar back up? Is it easy to add it as a power button menu item?
Edit: nvm i see the gesture suggestion now
Edit2: I've found an app called Taskarou, which puts a nav bar menu as a side of screen overlay. Check it out, send very promising.
http://imageshack.us/scaled/landing/818/screenshot2013030608344.png
http://imageshack.us/scaled/landing/268/screenshot2013030608345.png
Click to expand...
Click to collapse
Taskarou looks similar to LMT (http://forum.xda-developers.com/showthread.php?t=1330150). But LMT has some lag and, at times, some bugginess. Does Taskarou tend to run smoothly for you?
Probably not possible to remove buttons without root huh?
Droid RAZR HD (current)
LG Optimus One P-504 (For Sale)
Says so in the op..
Sent from my MB886 using xda app-developers app
Now that 4.1.2 is widely available to Verizon users of Razr HD in the US can anyone confirm that you can simply upgrade to 4.1.2 (retaining root), add qemu.hw.mainkeys=1 to build.prop, and then have the Navigation Bar GO, the System Bar STAY, and no FCs? Because that would seem to be a straight-forward solution to what should be an easy problem to solve. I know this solution CAN work because I did exactly this to my Nexus 7. It removed the NavBar (and kept the System Bar), extended the wallpaper to full screen and resized all the icons. I have never had a Force Close. Every app sizes correctly. I use Button Savior to put exactly the function buttons I want in the order I want them right where I want them on screen (normally right under my thumb). Works flawlessly on the Nexus 7. Hope with 4.1.2 it'll become easy to install on Razr Maxx HD.
lesdense said:
Now that 4.1.2 is widely available to Verizon users of Razr HD in the US can anyone confirm that you can simply upgrade to 4.1.2 (retaining root), add qemu.hw.mainkeys=1 to build.prop, and then have the Navigation Bar GO, the System Bar STAY, and no FCs? Because that would seem to be a straight-forward solution to what should be an easy problem to solve. I know this solution CAN work because I did exactly this to my Nexus 7. It removed the NavBar (and kept the System Bar), extended the wallpaper to full screen and resized all the icons. I have never had a Force Close. Every app sizes correctly. I use Button Savior to put exactly the function buttons I want in the order I want them right where I want them on screen (normally right under my thumb). Works flawlessly on the Nexus 7. Hope with 4.1.2 it'll become easy to install on Razr Maxx HD.
Click to expand...
Click to collapse
Now that Root is available for 4.1.2, I tried this out and it worked.
You have to do the following:
1) Make sure to install LMT or PIE control
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
You shouldn't get force closes. I'm on stock 4.1.2 rooted
Are you urging the installation of LMT or PIE because one of them is specifically necessary for this remedy to work or because you have to have SOMETHING to navigate with if you remove NavBar? As I said in the original post, I prefer Button Savior, which works fine on my Nexus 7. Would using Button Savior instead of LMT or PIE change the result of the mod?
Sent from my DROID RAZR HD using xda premium
lesdense said:
Are you urging the installation of LMT or PIE because one of them is specifically necessary for this remedy to work or because you have to have SOMETHING to navigate with if you remove NavBar? As I said in the original post, I prefer Button Savior, which works fine on my Nexus 7. Would using Button Savior instead of LMT or PIE change the result of the mod?
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Nope. I was only aware of LMT and PIE control as a replacement. I'll check out Button Savior.
To my great frustration, this method did NOT work for me. Getting rid of NavBar while keeping System Bar on my Razr Maxx HD is a near obsession with me at this point. Because I was on a leaked version of 4.1.1 and couldn't upgrade to 4.1.2 I used the incredible information available on XDA (thanks to all) to downgrade to 4.0.4, update the version of 4.0.4, update to 4.1.1 and then update to 4.1.2. I used the VZ OTA updates for every upgrade step. Every step proceeded without error. Once I was on 4.1.2 I used the new root for 4.1.2 to establish root, which also went smoothly. Then I followed the directions in the earlier post -- I installed Button Savior so I'd have an alternate means of navigation, installed Root Explorer, edited build.prop to add a new line reading "qemu.hk.mainkeys=0", rebooted, edited that line to read "qemu.hk.mainkeys=1" (no quotes in either case), rebooted. It should have worked. IT DIDN'T! My NavBar is gone, which is good. My System Bar is gone, which is bad. And I still get "SystemUI has crashed"-type errors. After all these steps that's the same result I was getting on a leaked, rooted version of 4.1.1. I'd love to finally get this right. How?
lesdense said:
To my great frustration, this method did NOT work for me. Getting rid of NavBar while keeping System Bar on my Razr Maxx HD is a near obsession with me at this point. Because I was on a leaked version of 4.1.1 and couldn't upgrade to 4.1.2 I used the incredible information available on XDA (thanks to all) to downgrade to 4.0.4, update the version of 4.0.4, update to 4.1.1 and then update to 4.1.2. I used the VZ OTA updates for every upgrade step. Every step proceeded without error. Once I was on 4.1.2 I used the new root for 4.1.2 to establish root, which also went smoothly. Then I followed the directions in the earlier post -- I installed Button Savior so I'd have an alternate means of navigation, installed Root Explorer, edited build.prop to add a new line reading "qemu.hk.mainkeys=0", rebooted, edited that line to read "qemu.hk.mainkeys=1" (no quotes in either case), rebooted. It should have worked. IT DIDN'T! My NavBar is gone, which is good. My System Bar is gone, which is bad. And I still get "SystemUI has crashed"-type errors. After all these steps that's the same result I was getting on a leaked, rooted version of 4.1.1. I'd love to finally get this right. How?
Click to expand...
Click to collapse
That's not how the edit goes.
Its
qemu.hw.mainkeys=1
Not hk
Replace it. That may be what is messing your phone.
I have my navigation bar hidden and im using pie control which i like more than button savior.
Sent from my RAZR HD using Tapatalk 2
Unfortunately, while I typed the edit wrong in my post I typed it CORRECTLY in my build.prop edit. So, that's not the problem, evidently. Thanks for the great catch though!
lesdense said:
Unfortunately, while I typed the edit wrong in my post I typed it CORRECTLY in my build.prop edit. So, that's not the problem, evidently. Thanks for the great catch though!
Click to expand...
Click to collapse
I am having same issues with my Razr HD. Mine is new which came with 4.1.2 already but I have rooted with the new method, have safestrap installed, all root apps work, root is solid. I followed these steps to a T:
1) Make sure to install LMT or PIE control (** I installed PIE, got it working)
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
When it says "reboot" I just do a shutdown, wait 10 secs, then power back up (the Razr HD doesn't have reboot option when you press hold the power, only airplane mode and shutdown). I assume that is fine, but tell me if I need to be doing one of those soft resets (i.e. Vol down + power).
System UI FC's after it is set to =1. Not sure why. I have added the line above to the end of the build.prop file (in /system). Does it need to be at the top??
Also, wonder if the launcher has anything to do with it. I am on GO Launcher. I say this since the GO Launcher menu (swiping up on home screen) shows up just below the edge of my wallpaper but behind the wallpaper (so I only see a little bit of the menu then it disappears behind the wallpaper). I can still swipe up to pull a functioning menu in foreground, but this seems odd to me. Anyone else on GO Launcher getting this to work?
Would really love to claim the screen real estate the Nav bar takes up. I can't really understand by Moto/Verizon did this. They say the screen is 4.7, but with the Nav I bet you only have 4.5 or so....
UPDATE: I tried it with Apex Launcher and got same problems. I heard from someone else saying they also have issue on Nova Pro. So it appears not to be linked to launcher being used. I hope something can be found to make this work, having that extra room is SO nice
india23 said:
Now that Root is available for 4.1.2, I tried this out and it worked.
You have to do the following:
1) Make sure to install LMT or PIE control
2) Make sure to install LMT or PIE control
3) edit build prop file qemu.hw.mainkeys=0
4) reboot
5) edit build prop file qemu.hw.mainkeys=1
6) reboot
You shouldn't get force closes. I'm on stock 4.1.2 rooted
Click to expand...
Click to collapse
@india23... can you please enlighten us on the setup of your phone so we can try and understand why this is not working for many others on stock rooted 4.1.2?
- Do you have stock 4.1.2 received from OTA updated and then rooted with motochopper? If not, what do you have?
- What root explorer tool did you use to make edit?
- How did you edit the file, where did you place the new line, any spaces or empty rows before or after that line, etc
- what launcher are you using?
- what are the permissions on your build.prop file?
- anything else you think can help.
There are a number of us on stock OTA 4.1.2 that is rooted and this option doesn't work. It removed BOTH Nav and Status bar, AND there are System UI FC's. Many are saying this is not doable on Stock ROM but you are saying it works for you, so just need to try and understand how and why.
Thanks
surfmly said:
@india23... can you please enlighten us on the setup of your phone so we can try and understand why this is not working for many others on stock rooted 4.1.2?
- Do you have stock 4.1.2 received from OTA updated and then rooted with motochopper? If not, what do you have?
- What root explorer tool did you use to make edit?
- How did you edit the file, where did you place the new line, any spaces or empty rows before or after that line, etc
- what launcher are you using?
- what are the permissions on your build.prop file?
- anything else you think can help.
There are a number of us on stock OTA 4.1.2 that is rooted and this option doesn't work. It removed BOTH Nav and Status bar, AND there are System UI FC's. Many are saying this is not doable on Stock ROM but you are saying it works for you, so just need to try and understand how and why.
Thanks
Click to expand...
Click to collapse
I am using the Rogers XT925 version. It is running Stock 4.1.2 and has been rooted using Dan R's motochopper tool.
I used build prop editor from the play store to add the "qemu.hw.mainkeys" property:
https://play.google.com/store/apps/...vbS5qcnVtbXkuYXBwcy5idWlsZC5wcm9wLmVkaXRvciJd
I am using apex launhcer.
Hope this answers your questions. If not, I can clarify as needed.
Thanks.
Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
First of all, all I need from you to have is a root browser app and some simple knowledge about editing files in there, changing permissions, moving stuff around, and all that stuff. I personally use "root browser" app. It's up to you. Whatever app you're comfortable with is fine.
1. The annoying "AT&T address book subscription" or whatever they call it pop-up window that pops in your face every time you open your contacts.
{
"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"
}
Well, not anymore [emoji16] thanks to @NunHugger for pointing that out for us in one of his posts on the alliance ROM thread (and I happened to be an OCD. I take a screen shot of every useful post that I think will help me in the future and throw it in my SD card)
Using your root browser app navigate to system/csc/feature.xml and find this
<CscFeature_Contact_EnableAAB>true<
and change the "true" to false. Save, reboot, and enjoy.
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
3. If you flash an international based ROM, you may lose your AT&T 4GLTE signal icon and end up with only G4 in the status bar. Even though it doesn't mean you don't have LTE, but hell it's so annoying to look at.
That's a very easy one. From your root browser, navigate to system/build.prop and find this
ro.product.name=hltexx
And replace the "xx" with "att". Save, reboot, and enjoy.
Also, I don't know who figured it out first. it's an old one (since the note 2 days)
4. Losing screen rotation functionality.
Due to "debloating" especially for those who have just gotten root (thanks to @geohot) and they're debloating the hell out of their phones. LOL
Some problems might occur thanks to samsung for linking so many of their bloat to the device's main functions. I ran into this problem and it drove me crazy. Thanks to the power of Google search and this gentleman here @phyowaiummg for posting the solution for it. It's caused by removing samsung hub with titanium. Titanium removes this
"libgnustl_shared.so"
file (that apparently controls the rotation function on our phone) from system/lib when you uninstall samsung hub with it. Just find that file in another ROM zip file. Extract it and throw it into your system/lib. Change permissions to rw-r-r and reboot.
Do NOT delete. Just freeze with titanium. It's not worth it. You're only going to save 150+ MB by deleting all the bloat. IF you can't help it, then use "root app delete" app from play store and delete the bloat.
5. HOW TO FULL UNROOT AFTER TOWELROOT (how I did it. It worked for me):
First you need to be on stock ROM (assuming you have a backup of it).
a. Un-install recovery from SS then Un-install the app-SS- itself.
b. Open up your "root browser". On the very first page, just keep scrolling down and find "SS" folder. Delete that.
C. From supersu app, go to settings/full unroot and press that and continue accepting all the windows that pop up. (Do NOT reboot yet).
d. From root browser, navigate to system/app and look for the supersu apk and see if it's there. If so, delete it. If it's not there, then you may find it in system/prev-app or data/app. Delete the hell out of it wherever you find it.
f. From root browser, navigate to system/xbin and find busybox and su and delete both.
d. Now reboot and cross your fingers it works. It worked for me.
Let me know if it works for you as well, please!
6. If you don't like the 480 DPI on your phone and think that your apps are too big. Or you don't want to use any apps/xposed modules (or for some reason those modules didn't work for you) to change that, then there is a method for you to do so by only a small edit in your build.prop (Thanks to @UK2K for bringing it up to this thread. Make sure to smack his "like" button wherever you find his posts ) . Some folks say that 375 DPI is the perfect way to go.
You can do that by just opening your "root browser" app. Navigate to system/build.prop then find
ro.sf.lcd_density=480
and change 480 to 375, save, reboot, and, as always, enjoy!
If you would like to save the original just put a "#" at the beginning and make it look like this:
#ro.sf.lcd_density=480
and just create a new one by typing it like this:
ro.sf.lcd_density=375
then, save and reboot.
7. This is an awesome addition by @hp79. Make sure to smack his "like" button.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"
8. For those who are having GPS not locking problems, I've found this fix on XDA YouTube channel. What it is, is just download the file that has your country's/region's name from this website and throw it into your system/etc then reset your permissions to rw-r-r and reboot. It worked like a boss for me and I hope that for you, too.
Just follow what this video says http://youtu.be/oU67XHD0kj4
-Another fix for the GPS, just in case the above didn't work for you, found by @39FarmallM (thank you, sir):
I am going to quote his post for you guys:
"http://www.rom-central.com/showthrea...te-3-Rom-N9005 <==[This is where he found his fixes]
[SOLUTION] GPS Fix - When moving back to Note 3 Rom {N9005}
Hi guys
A lot of users have GPS problems when they move back to a NOTE 3 ROM after flashing a S5 PORT ROM.
Here is a possible fix. Tested only on N9005
Solution 1
On your dialer type in this USSD *#0011#
Press menu key > press back
Press menu key > press key input > Q
Press menu key > press key input > 0000
Wait for a few seconds and the screen options will change
*MAIN MENU comes up
*Tap [2] UE SETTING & INFO
*Tap [1] SETTING
*Tap [2] SYSTEM
Press om UMTS (Not there)
Press on Common (Not there)
*Press on [3] NV Rebuild
Press on NV Rebuild (Just once)
*[3] ALL
Wait for 30 seconds and then shutdown your phone
Power On phone
GPS should work fine now
Recommend to use GPS STATUS app to reset and download AGPS Data
Solution 2
Assuming you are on a S5 Port ROM, make sure GPS is enabled
Boot into recovery and without wiping anything "dirty" flash a note 3 rom and reboot
There will be a lot of force closes once reboot is complete. Reboot back into recovery
Wipe data and reboot into the Rom again. There may be a few force closes. Reboot back into recovery
Wipe 3 times (data, cache, system, boot)
I recommend latest Philz Recovery (use intall new rom option to wipe) <== [This is for those who have unlocked bootloaders and are able to flash a custom recovery. It still works with Safestrap, just in case you wonder]
Restore or install your desired Note 3 rom
GPS should work fine
Thanks"
-A Third fix by @rogerinnyc (thank you, sir). And since he has attached a zip file for you guys then I will just give you the link to his post and you do the rest
Hope that helps some of you guys. If anyone has a fix that I don't know about, please just pm me and I'll add it to op. Enjoy fellas.
...!!!
The first one for getting rid of that stupid contacts sync thing worked great! Thanks!
I just destroy that software with Titanium backup anytime it is a problem.
Nice write up k-alz
Sent from my SM-N900A using Tapatalk
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Walter.White said:
Here is a video that you guys might find interesting.
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
Click to expand...
Click to collapse
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
K-Alzwayed said:
Thanks dude. that's pretty cool. they're very talented. I'm guessing our bootloader is going to be cracked soon?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Great info thanks
tmoore3496 said:
Great info thanks
Click to expand...
Click to collapse
No problem buddy. Hopefully it helped you.
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
UK2K said:
Thank you for this. You've started me on my way to digging through my files and editing. .. After research of course.
Sent from my SM-N900A using XDA app
Click to expand...
Click to collapse
You're very welcome, man. Glad I could help
azpatterson3 said:
Just got my note 3 a couple of days ago after selling my mega on AT&T. So nice to have root access again. Thanks for the tips. Really like getting rid of that annoying contacts pop up.
Click to expand...
Click to collapse
Welcome to the awesomeness of our community where everyone is nice and very helpful.
DPI change
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
UK2K said:
I don't think I saw this in your thread but following your editing of the build.prop file I would like to add that the stock dpi of 480 was too "big" for me so after some reading I saw a few recommend 375 but they were using apps.
So by opening build.prop after remounting it as rw look for the line:
ro.sf.lcd_density=480
change to 375
save
remount to readonly -ro
If you would like to save the original just put a "#" at the beginning:
#ro.sf.lcd_density=480
ro.sf.lcd_density=375
I'll look again to make sure I didn't dupe someone that's given this tip.
Click to expand...
Click to collapse
Thanks, man. I'll add it to OP. :good:
K-Alzwayed said:
Thanks, man. I'll add it to OP. :good:
Click to expand...
Click to collapse
Sweet! My first mention! :laugh:
Thanks Sir.
Brilliant wi-fi fix!
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
K-Alzwayed said:
Hey guys. I've been an android user for the past 2.5 years and during my time using it, I've run into rooting and taking full control of my phone. BUT that comes with a price. And luckily, that price isn't that big of a deal (unless you really mess up your device by doing things you don't know anything about). A few tweaks and changes to your "build.prop, csc, lib....etc" contents with a reboot sometimes fixes problems real quick and you'll be a happy camper after thinking "oh sh*t! My phone sucks and this can't be fixed".
Without further a due, here are some of the annoying issues I've run into and after searching/asking I figured out how to fix them:
2. WiFi issues. Like, your wifi isn't sticking while you're using your phone. It disconnects constantly. Or you have to re-enter your password every time you reboot. That is easy as well. I am not sure who figured it out first, but I've seen some posts praising @Walter.White for finding that out. Thanks to him either way. He helps so much all the time regardless.
From your root browser, navigate to system/build.prop and find this
ro.securestorage.support=true
and change the "true" to "false". Reboot and enjoy.
Click to expand...
Click to collapse
sethomas1975 said:
Brilliant fix for the Wi-Fi problem. I softbricked trying to update last night and finally found a 4.4.2 file to load via Odin that worked and immediately was relieved I got it to work and pi$$ed when I realized wi-fi was wanky. This fix worked perfectly. Thanks for posting this. All my searching paid off. Haven't done any homework for college or done any work around the house yesterday or today, but got my Note 3 back up and running.
Click to expand...
Click to collapse
No problem. Glad it helped [emoji16]
THANK YOU!
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
jpstiehl said:
#4 - it was driving me crazy!
I actually didn't uninstall Samsung Hub but I did freeze it. Somehow that lib file went missing though.
Click to expand...
Click to collapse
Glad It worked for ya man
Here's some to add. One is for soft-menu, and the other is for disabling AT&T wifi by renaming the SSID.
[Enable soft menu keys]
edit "/system/build.prop", and add at the bottom:
Code:
qemu.hw.mainkeys=0
[Optional] Disable hardwired buttons.
edit "/system/usr/keylayout/Generic.kl", comment out these two lines so it looks like this:
Code:
# key 139 MENU
# key 158 BACK
After using a while, I found it works best if I keep the hardware buttons enabled too. Back key is now on both left and right side so it's easier to reach when using with one hand.
[Optional] Disable 3-dot menu button. When you enable soft-keys, there will be an additional menu shown in every app. This could waste lot of space. You should have Xposed mod installed, then look for Noverflow, and install that.
Noverflow xposed mod.
This doesn't work on Galaxy S5 Port Update 4 ROM, but works well with stock NC2 ROM.
[Optional] Once softmenu keys are added, you have less screen space. The Dialer app doesn't know how to scale, so you would have the bottom row keys chopped off a bit. You can make change the DPI settings so it'll shrink and be able to see everything.
Default screen DPI is 480. I changed it to 450.
Edit file "/system/build.prop", look for the line with "ro.sf.lcd_density=480" and edit so it looks like this:
Code:
ro.sf.lcd_density=450
[Optional] Remove AT&T wifi autoconnect.
I don't know why, but even if I uncheck autoconnect AT&T wifi, it still keeps trying. And you can't really remove the profile either.
Edit "/data/misc/wifi/wpa_supplicant.conf"
Look for "ssid="attwifi". Change that to something like this:
Code:
ssid="attwifi-sucks"
Hi
I just got a running 'cover' to my S5, but the thing is, that it push the power/volume buttons. Is their any way to disable the buttons, just for a period of time?
My phone is rooted and I looked in the generic file (where you change button actions) but their is 2-3 power button likes (142/143/152). Why is their 3? They say:
key 142 Power Wake
key 143 Power Wale
Key 153 Power Wake
Should I just delete them all? If I do so and my phone suddenly shutdown, will I be able to turn it on agian, when the power button is disabled?
Also, is their any other way?
Thanks in advance
Faspaiso said:
Hi
I just got a running 'cover' to my S5, but the thing is, that it push the power/volume buttons. Is their any way to disable the buttons, just for a period of time?
My phone is rooted and I looked in the generic file (where you change button actions) but their is 2-3 power button likes (142/143/152). Why is their 3? They say:
key 142 Power Wake
key 143 Power Wale
Key 153 Power Wake
Should I just delete them all? If I do so and my phone suddenly shutdown, will I be able to turn it on agian, when the power button is disabled?
Also, is their any other way?
Thanks in advance
Click to expand...
Click to collapse
Maybe there is a Xposed module for that, make sure to make a nandroid backup before you go deleting stuff.
gee2012 said:
Maybe there is a Xposed module for that, make sure to make a nandroid backup before you go deleting stuff.
Click to expand...
Click to collapse
I have read a little about Xposed, but I don't have it installed on my phone.
Just curious, so I don't do anything to ruin my phone. Is their any models or something, just like when I rooted, or is Xposed an universal app, that I just install?
Also, where do I get it? Found a few links on Google, but you know an save place?
Thanks in advance
Faspaiso said:
I have read a little about Xposed, but I don't have it installed on my phone.
Just curious, so I don't do anything to ruin my phone. Is their any models or something, just like when I rooted, or is Xposed an universal app, that I just install?
Also, where do I get it? Found a few links on Google, but you know an save place?
Thanks in advance
Click to expand...
Click to collapse
Its a universal app, here is the link http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053. Read the OP and download and install the apk file. Many usefull modules like Xblast for UI changes.
PS: users who respond to your question don`t want to ruin your phone neither
gee2012 said:
Its a universal app, here is the link http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053. Read the OP and download and install the apk file. Many usefull modules like Xblast for UI changes.
PS: users who respond to your question don`t want to ruin your phone neither
Click to expand...
Click to collapse
Thanks
Haha, I know. Not what I meant tho, so sorry for my bad english. What I meant, is that by an google search, their were tons of links from diffrent webpages, which I wasn't sure all were secure to download from.
But thanks for your answer!
I can't seem to find an Xposed module for it.
Any other ideas?
Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks
bluenote73 said:
Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks
Click to expand...
Click to collapse
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.
amphi66 said:
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.
Click to expand...
Click to collapse
Thanks. That worked for me. I don't know wtf is the problem with that build.prop editor I was using, but it worked flawlessly through the last 2 updates, but suddenly after B25 just seems to cause this problem right away.
Hey guys. ...i wanna disable my soft keys(nav bar) as i was able to do that...in invicta os...but...for there was some issues regarding battery life...so i revert back to stock rooted nougat...plz help me..asap
Harshseth said:
Hey guys. ...i wanna disable my soft keys(nav bar) as i was able to do that...in invicta os...but...for there was some issues regarding battery life...so i revert back to stock rooted nougat...plz help me..asap
Click to expand...
Click to collapse
Use an app called custom navigation bar from play store and via some adb commands written in the app you can hide the navbars easily
Link:- https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner.
Or use simpler apps like https://play.google.com/store/apps/details?id=in.omerjerk.fullscreenimmersive
For immersive mode without adb commands
Do hit thanks button if it helped. And contact for more help.
Sobhan Bhuyan said:
Use an app called custom navigation bar from play store and via some adb commands written in the app you can hide the navbars easily
Link:- https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner.
Or use simpler apps like https://play.google.com/store/apps/details?id=in.omerjerk.fullscreenimmersive
For immersive mode without adb commands
Do hit thanks button if it helped. And contact for more help.
Click to expand...
Click to collapse
Thnx for ur suggestion......but i want nav bars to disable permanently....like any custom rom .i tried using this app...but nav bars always comes.. whenever i swipe up or down......
Go to system folder and open build.prop file in text editor.
Now add one line in this, that is
qemu.hw.mainkeys=1
Well I have not tried this so pls do backup in twrp and then proceed also as this will remove navbars completely so setup an app like pie control earlier or else u will not be able to navigate. Hit thanks
Sobhan Bhuyan said:
Go to system folder and open build.prop file in text editor.
Now add one line in this, that is
qemu.hw.mainkeys=1
Well I have not tried this so pls do backup in twrp and then proceed also as this will remove navbars completely so setup an app like pie control earlier or else u will not be able to navigate. Hit thanks
Click to expand...
Click to collapse
Thnk u so much......just in case if i wish to get nav bars again.... would it be possible ?
Harshseth said:
Thnk u so much......just in case if i wish to get nav bars again.... would it be possible ?
Click to expand...
Click to collapse
Maybe deleting the line will do so but I really didn't try this at all so do a backup always
Sobhan Bhuyan said:
Maybe deleting the line will do so but I really didn't try this at all so do a backup always
Click to expand...
Click to collapse
Thnx bro