Database Users

Custom launcher on S7 Slim

For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!

I installed adw launcher ex on my s7 tablet and now my touch screen wont work. I've tried to connect it to my PC to root but my PC isn't seeing the device. I don't think its set on debugging mode. Is there anyway to fix this or is it hopeless.
Edit: nevermind I returned it to best buy.
Sent from my Desire HD using xda premium

I've root with gingerbreak and I've root explorer. I'll just edit bluetooth_power.sh with root explorer editing tools and add those code, right?
Sent from my IDEOS S7 Slim using XDA App

shishko said:
For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!
Click to expand...
Click to collapse
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk

Here is the evidence, custom launcher GO Launcher EX works on my HIS7 Slim (CDMA)

#!/system/bin/sh
#
# added by h00131430
#
echo 0 > /sys/class/rfkill/rfkill0/state
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Download file
http://www.multiupload.com/MKBGQUC10X

Worked for me.

glpro said:
Download file
http://www.multiupload.com/MKBGQUC10X
Click to expand...
Click to collapse
Link is dead, could you post another, please?

wheeqo said:
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk
Click to expand...
Click to collapse
Confirmed, working. I installed Zeam straight to portrait view, and no orientation bug anymore. Cheers!

huawei slim
who can make a better huawei s7 slim rom?

beenhow said:
who can make a better huawei s7 slim rom?
Click to expand...
Click to collapse
1. Tri-zet (Tried and works great) androidtablets.net
2. Zmey Mod (Still running) on ndroidtablets.net
3. Pirate 2.0 by Satec in this forum (Not sure this will run on my s7 105 and too lazy to flash this at the moment cos the ROM i using now is stable enough)

Tri Zet works great!

darkic said:
Tri Zet works great!
Click to expand...
Click to collapse
CM9 , CM10 , paranoid works great , too

Usb storage mass and ICS

Solution:
How to enable USB mass storage on Android 4.0 ICS Samsung Galaxy S2?
1.Bring up Settings.
2.Click More… (under Wireless and network).
3.Then select USB utilities ~ Set USB cable connection mode.
4.Select Connect storage to PC then.
5.Connect USB cable from phone to PC.
6.Select Turn on USB storage.
7.That’s all.

I was confused as to why my apps wouldn't install... Now i know why. Thanks dude

eheh it's quite different from gingerbred, yes.
I have found it just yesterday!!

rizxda said:
eheh it's quite different from gingerbred, yes.
I have found it just yesterday!!
Click to expand...
Click to collapse
It isn't really that different at all, it has always been under Network>USB utilities or something under GB. It's just that most of us used the pull-down notification.

its working with my usbStick but dosent work with the camera!?

Thanks, dude.
Was getting desperate because couldn't read my storage, on Bezke's ROM.
Cheers.

thank you very much...

OR, if you hate going through the menus everytime, you can do like I did and enable the USB mass storage by default (instead of that MTP which doesn't work on Mac OS).
Solution A - put this in your init script (if you have a kernel which supports init scripts, currently only CF-Root works on ICS).
Code:
setprop persist.sys.usb.config "mass_storage,adb"
Solution B - add/change the same settings in build.prop (you probably have now "persist.sys.usb.config=mtp,adb".
Code:
persist.sys.usb.config=mass_storage,adb
And reboot. When you connect your cable, it will default to USB mass storage mode just like it did on Gingerbread.

Solution C: JKay or any other ROM maker, add a button to the Message bar.
Sent from my GT-I9100 using XDA

VAXXi said:
OR, if you hate going through the menus everytime, you can do like I did and enable the USB mass storage by default (instead of that MTP which doesn't work on Mac OS).
Solution A - put this in your init script (if you have a kernel which supports init scripts, currently only CF-Root works on ICS).
Code:
setprop persist.sys.usb.config "mass_storage,adb"
Solution B - add/change the same settings in build.prop (you probably have now "persist.sys.usb.config=mtp,adb".
Code:
persist.sys.usb.config=mass_storage,adb
And reboot. When you connect your cable, it will default to USB mass storage mode just like it did on Gingerbread.
Click to expand...
Click to collapse
I have "persist.sys.storage_preload=1"

Danielfr said:
I have "persist.sys.storage_preload=1"
Click to expand...
Click to collapse
Got the same here.

Nice solution above but I just really wish it could be handled like my old HTC on GB with the dropdown notification.
Sometimes I just want to charge, sometimes mtp will do but more often mass storage.

i rly need this feature...i use it everyday to connect my gs2 to my car stereo....there'sno app capable a the moment?

That has nothing to do with what I wrote; as these are computers, even one letter makes a big difference, nevermind one entire word
I've checked the default build.prop files on XXLPQ and ZSLPE and they don't seem to include this setting by default, so you probably have to add it manually; either remount /system as r/w and edit through vi in ADB, either use build.prop Editor from the market.
@Elemetrix: changing the system property mentioned before gives you the old style setting instead of MTP.

VAXXi said:
That has nothing to do with what I wrote; as these are computers, even one letter makes a big difference, nevermind one entire word
I've checked the default build.prop files on XXLPQ and ZSLPE and they don't seem to include this setting by default, so you probably have to add it manually; either remount /system as r/w and edit through vi in ADB, either use build.prop Editor from the market.
@Elemetrix: changing the system property mentioned before gives you the old style setting instead of MTP.
Click to expand...
Click to collapse
editing build.rpop..didnt work

What exactly didn't work ? is it still going to MTP, is it not working at all anymore ?
Easiest way to check is to do a
Code:
getprop | grep usb
in Terminal Emulator and see if the values have changed.

VAXXi said:
What exactly didn't work ? is it still going to MTP, is it not working at all anymore ?
Easiest way to check is to do a
Code:
getprop | grep usb
in Terminal Emulator and see if the values have changed.
Click to expand...
Click to collapse
it is still picking as mtp,adb when i grep it. but i have confirmed i changed it in build.prop.. found under systems

can u make pls a detailed guide to us poor newbies? XD

xinfinityoO said:
it is still picking as mtp,adb when i grep it. but i have confirmed i changed it in build.prop.. found under systems
Click to expand...
Click to collapse
Was the build.prop saved ? can you grep the property name in build.prop and check it's still there after rebooting the phone ?
The
Code:
getprop | grep usb
should give you two more properties: sys.usb.config and sys.usb.state. They should have the same mass_storage,adb value.

VAXXi said:
Was the build.prop saved ? can you grep the property name in build.prop and check it's still there after rebooting the phone ?
The
Code:
getprop | grep usb
should give you two more properties: sys.usb.config and sys.usb.state. They should have the same mass_storage,adb value.
Click to expand...
Click to collapse
yes it was saved.. i even checked with root explorer.. and the rest of properties also states the same mtp,adb. can you attach your buildprop for me to test..
thanks

[Q] USB Debugging?

Hi Guys,
First off sorry if this isn't the correct place for this, if it isn't would somebody be good enough to move it to the right place.
I've got a rooted (via NookManager) Nook Simple Touch, the problem is I need to turn on USB Debugging but can't find any way to do so. What am I missing?
Thanks
-S

Sanukk said:
What am I missing?
Click to expand...
Click to collapse
You are not "lurking" hard enough.
Use 'NookColor Tools' to turn on USB debugging.
http://forum.xda-developers.com/showthread.php?t=868366
To run 'NookColor Tools' put the 'apk' in /system/app/ folder using any filemanager that has the ability to mount /system partition in write mode (ex. 'Rhytm software File Manager', 'Es File explorer')
After that there are 2 choices.
1. Use 'ABD Wireless' or 'ADB Konnekt' to connect to your PC via WIFI (the easiest way)
2. Configure Android Udev Rules on your linux machine. You can find the correct values in
a) any search engine ( look for 'android udev rules adb')
b) check out the list of my posts. I posted the correct values somewhere.
c) http://forum.xda-developers.com/showthread.php?p=18418152
http://www.joescat.com/linux/android_rules.html
If you can find one site or post that contains the correct instructions for Linux and Windows paste them in this thread. Make this thread useful.
EDIT :
Wireless solutions should work out of the box, without the need of using NookColorTools.

osowiecki said:
You are not "lurking" hard enough.
Use 'NookColor Tools' to turn on USB debugging.
http://forum.xda-developers.com/showthread.php?t=868366
Click to expand...
Click to collapse
NookColor Tools did appear in in a few search results, but as I have a Touch Simple rather than a Nook Colour, I just ignored it. I'll try it tonight after I get home. Thanks.
~S

[HOW TO] Unlock tethering on Marshmallow 6.0

Google made a change from Android 4.1.2 which allows operators to know when users are using tethering and conveniently block tethered devices from accessing internet.
This can be fixed permanently using the following procedure and no root required on all rom types (stock, mod):
1) Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2) Enable USB debugging under Settings -> Developer options
3) Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4) Start an adb shell: adb shell
5) In the adb shell, run this command:
Code:
settings put global tether_dun_required 0
Tested on Nexus 5 & 6 with Marshmallow STOCK ROM

Just tried this on a freshly imaged Verizon Nexus 6 with Marshmallow, and I'm still getting the prompt for subscribing to tethering.

Can you do this with sqlite editor? If so, how?

net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.

Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk

trent999 said:
Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
I'm on Verizon and that's what I did also.
Sent from my Nexus 6 using Tapatalk

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You don't need root to do it, you can make the change via recovery and adb shell commands.

wishkah said:
Can you do this with sqlite editor? If so, how?
Click to expand...
Click to collapse
I'm not sure this can be done with sqlite editor anymore because when I go to the file path data>data>com.android.providers.settings>databases there is no longer a settings.db in that location to edit.
Maybe I'm missing something.... IDK???

didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
Click to expand...
Click to collapse
editing the build.prop worked for me! thanks guys/gals

nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is Rooot needed to do this through adb?

That is my question, too.
For right now, I want to wait to unlock and root. I have reasons...
Can I edit and replace build.prop somehow under those conditions ?
I have ADB and fastboot both working and have pulled a copy of the stock Lollipop build.prop onto my laptop. I can edit it, but can I push the revised copy back with the boot loader still locked and no root ?
I read somewhere about achieving temporary root via fastboot booting twrp, instead of flashing, but that fails for me and I cannot find the referencing thread.
Sent from my VS985 4G using Tapatalk

Same boat here. I'd love to enable this, but don't want to do too much as I'm switching to a 6P in two weeks.
Do you need root to mod this? i'm not able to R/W system without it I assume?

So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.

Yes, the above is what I have been looking at, but it is important to realize it requires an unlocked bootloader, which requires a total phone wipe.
Plus I am concerned that this will prevent any future OTA, like to Marshmallow for mine, and also make it impossible to use Android Pay on that device, if those issues matter to you.
Yes, I know it is self-limiting to have a stock, locked N6.
Sent from my Nexus 6 using Tapatalk

pmhesse said:
Note that this does make the scary This device is corrupt... message appear at bootup.
Click to expand...
Click to collapse
Also note that this will also make you unable to apply any future OTAs (neither pushed to you by Google, nor sideloaded via ADB).
18 months ago, before /system validation became a thing, I would have recommended this method to a lot of "casual" modders - booting to TWRP to fix a couple things, and then going on their merry way with an unrooted "stock" (or close enough to it as to not matter) device.
Now that /system validation is a thing (breaks OTA applicability, dm-verity), I wonder if it's actually more advisable that people keep TWRP installed, and take the time to fully educate themselves about what they're doing, so that in the future they can fix things themselves more easily (and manually apply the monthly security patches, etc.).
I'm honestly not sure about the right answer - what do folks think?

pmhesse said:
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Click to expand...
Click to collapse
Ah. I don't have TWRP installed. Thats what I was missing. I went full stock besides my unlocked bootloader with Marshmallow. Not being able to Android Pay also sucks as I do use that. Wonder if I set it up first, then do this if it will let me still use the cards I load.

Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
editing the build.prop worked for me! thanks guys/gals
Click to expand...
Click to collapse
So the command did not work but adding the net..etc to build prop worked anyone in T-Mobile done this yet? Thanks

Correct, the command didn't work, but the line at end of build.prop did. Should work for any carrier.

Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
Thank you!

MIUI 11 Update Notification

OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:

- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse