Database Develop

[Q] [KFTT] customizing the status bar on default launcher

I have a rooted 7" Kindle Fire HD and was wondering if there was a way to further customize the status bar without installing extra apps or a different launcher.
In particular, I'd like to see the battery percentage (isn't that a stock option from ICS onwards?), and I'd like to be able to see the notifications that would normally be displayed in the top left corner (e.g. Trillian, Tapatalk) where the Fire only displays the device name.

[KFTT] customizing the status bar on default launcher >
Eismagier said:
I have a rooted 7" Kindle Fire HD and was wondering if there was a way to further customize the status bar without installing extra apps or a different launcher.
In particular, I'd like to see the battery percentage (isn't that a stock option from ICS onwards?), and I'd like to be able to see the notifications that would normally be displayed in the top left corner (e.g. Trillian, Tapatalk) where the Fire only displays the device name.
Click to expand...
Click to collapse
Eismagier,
Prerequisites: Root the Kindle Fire 7" HD and 2 with Windows - Noob (Simple) Version
We have not had time to test this tool on the Kindle but it is worth a shot.
Step 1: Download com.calsto.omega.statusbar-1.apk to your desktop
Step 2: Using Windows Explorer move com.calsto.omega.statusbar-1.apk from your desktop to Kindle/Internal Drive/Download folder.
Step 3: Using ES File Explorer or Root Explorer with Root Permissions, move com.calsto.omega.statusbar-1.apk from /sdcard/Download to /system/app folder.
Step 4: Using ES File Explorer or Root Explorer change the permissions of com.calsto.omega.statusbar-1.apk in the /system/app folder to: User: Read Write Group: read and Others: Read
Step 5: Tap com.calsto.omega.statusbar-1.apk to install, then Reboot the Kindle
Step 6: Go to the /Apps folder on the Kindle, find Omega StausBar - make changes.
Please reply when you have successfully tested the product. Thanks!

prokennexusa said:
Eismagier,
Prerequisites: Root the Kindle Fire 7" HD and 2 with Windows - Noob (Simple) Version
We have not had time to test this tool on the Kindle but it is worth a shot.
Step 1: Download com.calsto.omega.statusbar-1.apk to your desktop
Step 2: Using Windows Explorer move com.calsto.omega.statusbar-1.apk from your desktop to Kindle/Internal Drive/Download folder.
Step 3: Using ES File Explorer or Root Explorer with Root Permissions, move com.calsto.omega.statusbar-1.apk from /sdcard/Download to /system/app folder.
Step 4: Using ES File Explorer or Root Explorer change the permissions of com.calsto.omega.statusbar-1.apk in the /system/app folder to: User: Read Write Group: read and Others: Read
Step 5: Reboot the Kindle
Step 6: Go to the /Apps folder on the Kindle, find Omega StausBar - make changes.
Please reply when you have successfully tested the product. Thanks!
Click to expand...
Click to collapse
I can confirm that this works. There's even quite a few cool themes.

[KFTT] customizing the status bar on default launcher
Krsmqn said:
I can confirm that this works. There's even quite a few cool themes.
Click to expand...
Click to collapse
Krsmqn,
Thank you. I looked at the code, it appeared to be solid.
FYI: We sent you a PM regarding the Nvidia driver install.
Good night.

prokennexusa said:
Please reply when you have successfully tested the product. Thanks!
Click to expand...
Click to collapse
Step 5 should probably be "Tap com.calsto.omega.statusbar-1.apk to install." before rebooting the Kindle, otherwise you get into a loop of "Omega StatusBar has stopped".
That said, the app appears to work fine on the Fire HD. The only problem I've noticed so far is that I get occasional "flashes" of the regular status bar. Some of these appear random, others are reproducible (selecting the Theme Manager, for instance).

Any way to get notifications to show up?
Sent from my KFTT using Tapatalk 2

Buy the pro version. Ive followed the steps to the tee, even doing as suggested regarding installing the apk before reboot and it fc's everytime on boot. If you open the app however i can get it to work after boot but oddly its not compatible with the hide statusbar option in nova. The default statusbar is displayed in the homescreen and omega one when an app is open.
Sent from my KFTT using xda app-developers app

[KFTT] customizing the status bar on default launcher - Omega StatusBar
Eismagier said:
Step 5 should probably be "Tap com.calsto.omega.statusbar-1.apk to install." before rebooting the Kindle, otherwise you get into a loop of "Omega StatusBar has stopped".
That said, the app appears to work fine on the Fire HD. The only problem I've noticed so far is that I get occasional "flashes" of the regular status bar. Some of these appear random, others are reproducible (selecting the Theme Manager, for instance).
Click to expand...
Click to collapse
Eismagier,
Thank you, we are used to programs initializing themselves when they are moved to /system/app - we have added this step to the instructions.

On my 8.9" Kindle Fire HD (rooted), Omega StatusBar crashes as soon as I turn accessibility on (which the app says is necessary to get notifications). Is there a workaround for this?

Dr. Drax said:
On my 8.9" Kindle Fire HD (rooted), Omega StatusBar crashes as soon as I turn accessibility on (which the app says is necessary to get notifications). Is there a workaround for this?
Click to expand...
Click to collapse
This
Sent from my KFTT using Tapatalk 2

Omega Status Bar is buggy with Kinology. I've also tried Rom Toolbox and only been able to change the battery image. I even went as far as manually tinkering with the SystemUI.apk (with unfortunate results). Does anyone know a reliable app or method of changing the icons on the status bar, or completely changing the entire theme of it?
Any help would be appreciated.

Try ninjamorph
Sent from my CyanogenFire HD

Krsmqn said:
Try ninjamorph
Click to expand...
Click to collapse
It looks like Ninjamorph hasn't been updated since August 2010, and the developer's website registration has expired. Have you actually tried it on the HD?

When I found Ninjamorph and began using it, I was already on Kinology (which wasn't very long ago), so I wouldn't know how effective it is on the original Rom. The program itself is very easy to use. You are on Kinology?
Sent from my CyanogenFire HD

Krsmqn said:
When I found Ninjamorph and began using it, I was already on Kinology (which wasn't very long ago), so I wouldn't know how effective it is on the original Rom. The program itself is very easy to use. You are on Kinology?
Click to expand...
Click to collapse
No, I have a KFHD8.9, so I can't use Kinology. Ninjamorph will probably work on the stock ROM, but I just get generally nervous about using software that's been abandoned by the developer for years.

Lock gear from launcher shortcut

Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
EDIT:
jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.

fOmey said:
Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app

karoolus said:
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app
Click to expand...
Click to collapse
I tried this particular application, although it FC's here..

fOmey said:
I tried this particular application, although it FC's here..
Click to expand...
Click to collapse
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch

karoolus said:
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch
Click to expand...
Click to collapse
Yes im aware of that, you obviously didn't read the OP very well.. Thanks anyway..

Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module

Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.

fOmey said:
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.
Click to expand...
Click to collapse
Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Awesome tag team. Works great with Nova!

How do you modify the key?
Sent from my SM-N900V using xda app-developers app

bosshogg38 said:
How do you modify the key?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Root file explorer.. Open the file as a text file.

can you guys please post instructions thank you!

jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.

fOmey said:
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
Click to expand...
Click to collapse
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".

MaTtKs said:
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".
Click to expand...
Click to collapse
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE

fOmey said:
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE
Click to expand...
Click to collapse
Awesome. Thanks buddy.

MaTtKs said:
Awesome. Thanks buddy.
Click to expand...
Click to collapse
I can't get this to stick...I make the changes, and save, but when I go back in they are different again.
Using root explorer.
Sent from my SM-N900V using xda app-developers app

[HOW TO] Note3 Playstore/Samsung Apps Spoof

Alright guys, Iv figured out another nice little mod to view both Samsung Apps & Google Playstore as a Note 3 on your mobile device, in my case my Galaxy S4.
You might be wondering why we would even want to do this ? At this stage Note 3's have access to exclusive APK's for example the app "Atooma" for the gear !
Your mobile device MUST be rooted. Also please keep a backup of your original build.prop.
Also I cant confirm this works on every device, although works perfectly fine on my Galaxy S4 i9505.
So lets dive straight into it.
1. Open/pull "/system/build.prop" from your rooted mobile device using a root file browser or adb.
2. Open file in a text editor.
3. Replace the default lines with the following:
Code:
ro.product.model=SM-N9005
ro.product.brand=samsung
ro.product.name=hltexx
ro.product.device=hlte
ro.product.board=MSM8974
ro.build.description=hltexx-user 4.3 JSS15J N9005XXUBMJ3 release-keys
ro.build.fingerprint=samsung/hltexx/hlte:4.3/JSS15J/N9005XXUBMJ3:user/release-keys
4. Save changes.
5. Set permissions to your modified build.prop if they do not match with other files in the /system directory.
6. Navigate to "Settings -> Application Manager -> All -> Google Playstore" and "Clear data", "Clear cache" & "Force Stop".
7. Restart device.
You will now have access to Note 3 exclusive apps, I recommend downloading the apps you want and reverting the changes you have made to the build.prop.
What I have done is kept a backup of my original build.prop in the system partition and I just swap them around when I need to by renaming & restarting, remembering to clear data & cache of the Playstore !
Remember to hit thanks !

Is this only for 4.3? Or will it work on 4.2.2?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

E3SYLER said:
Is this only for 4.3? Or will it work on 4.2.2?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Unconfirmed, I would say only 4.3.. although you never know, just give it a try.
Worse case scenario if anything goes wrong just reflash your rom and it will revert all your changes.

What text editor did you use on your device? I'm trying to find one so I an try it out
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

E3SYLER said:
What text editor did you use on your device? I'm trying to find one so I an try it out
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I use root explorer, which includes a text editor.
I would recommend pulling your build.prop to your PC tho, so you can simply copy & paste.

fOmey said:
I use root explorer, which includes a text editor.
I would recommend pulling your build.prop to your PC tho, so you can simply copy & paste.
Click to expand...
Click to collapse
just tried and when i try to replace the build with the modded one it wont keep the mod it reverts back to sgh-i337
im using 4.2.2 i think thats my problem.
thanks for the intel i will try it again when i get 4.3http://forum.xda-developers.com/images/smilies/laugh.gif

If this works with earlier versions (pre-4.3) then this would remedy the issue that I and so many others have been having
with the Gear Manager application where it won't sync with the watch because it detects that you are using an "unsupported device".
I might try this out sometime...

On-screen buttons on HTC one :eek:

Guys, I'm using a HTC One M7 and in some apps there's onscreen buttons, I'd like to know why. I'm using the venom sense 6 6.1.0 Rom.
Sent from my HTC One using XDA Free mobile app

Yo
Grab a root explorer
Then go to system
open build.prop
Search for qemu.hw.mainkeys=0
^Should be at the very bottom
And remove that and save the file and restart.
Try again

uZzY94 said:
Yo
Grab a root explorer
Then go to system
open build.prop
Search for qemu.hw.mainkeys=0
^Should be at the very bottom
And remove that and save the file and restart.
Try again
Click to expand...
Click to collapse
Would changing the value to 1 keep the onscreen buttons permanently?
Edit: Nevermind, I answered my own question by trying it out myself.

Sprint Nexus 6 Wifi Tethering *root* UPDATED WORKING

Has anyone got "net.tethering.noprovisioning=true" to work? I am able to toggle portable wifi tethering set it up and connect but will pull no data .
UPDATE
Got it to work after installing Sqlite editor from GPS.
Instructions: Open Sqlite editor navigate to data/data/com.android.providers.settings/databases/settings.db > click on Global > add string Setting.db addition of tether_dun_required value 0
Then open root explorer and open build.prop add net.tethering.noprovisioning=true to bottom
Reboot=Profit

wytecaztle said:
Has anyone got "net.tethering.noprovisioning=true" to work? I am able to toggle portable wifi tethering set it up and connect but will pull no data .
Click to expand...
Click to collapse
Have you also added the line
tether_dun_required
Value=0
To the settings database in data/data/com.android.providers.settings/databases under the global tab

I'm going to try this for t mobile hope it works

It jas been mentioned before that tmobile users need to only modify the settings database. There is a thread that mentions these details 3 or 4 pages back...
http://forum.xda-developers.com/nexus-6/help/nexus-5-tethering-hack-nexus-6-t2946775

chrisduclo said:
It jas been mentioned before that tmobile users need to only modify the settings database. There is a thread that mentions these details 3 or 4 pages back...
http://forum.xda-developers.com/nexus-6/help/nexus-5-tethering-hack-nexus-6-t2946775
Click to expand...
Click to collapse
doesn't the build.prop trick do the job as well?

For sprint device i did both with successful results.

For Sprint, I only added tether_dun_required, rebooted and it worked. This was after I factory reset, however. It didn't work before that for an unknown reason.
Sent from my Nexus 6 using Tapatalk

What app did you guys use to edit the database?

jumbodogs said:
What app did you guys use to edit the database?
Click to expand...
Click to collapse
Sqlite editor. I can try and create a flashable zip that does the same thing sometime today so it's easier for everybody. I'd have to test it myself of course.
Sent from my Nexus 6 using Tapatalk

Thanks to everyone here!
Mods Can you move to General section please.

Hey all. Are you guys using the Nexus 6 from the GPS or from Sprint? I got mine from Sprint, rooted and added lines to setting.db and build.prop factory reset and still can't even toggle Portable Wifi without getting Tethering or Hotspot Error....
My next task is to flash the factory rom direct from dev.google

I am unable to Wi-FI tether even after doing both tether_dun_required and the net.tether.noprovisioning in the build.prop. Bought straight from GPS, so not sure what I am doing wrong :/
EDIT:
It was a typo by me, the actual string is "net.tethering.noprovisioning"... "tethering" not "tether" after fixing this, all works well. I'd advise anyone struggling to just give spelling another check.

bymoe1up said:
Hey all. Are you guys using the Nexus 6 from the GPS or from Sprint? I got mine from Sprint, rooted and added lines to setting.db and build.prop factory reset and still can't even toggle Portable Wifi without getting Tethering or Hotspot Error....
My next task is to flash the factory rom direct from dev.google
Click to expand...
Click to collapse
Hey all,
So I had to edit the two files in a specific order. Here's what worked for me on a Sprint Nexus 6.
- Root device
- add the additional line for build.prop
- factory reset
- check to see if you can toggle WiFi tether/hotspot from settings [if so continue]
- add line value to settings.db
- soft reboot
Hope it works.
Sent from my Nexus 6 using XDA Free mobile app

great write up, i make it work using the directions provided..!
now anyone can make a mod for this? like APK or flushable zip?

bymoe1up said:
Hey all,
So I had to edit the two files in a specific order. Here's what worked for me on a Sprint Nexus 6.
- Root device
- add the additional line for build.prop
- factory reset
- check to see if you can toggle WiFi tether/hotspot from settings [if so continue]
- add line value to settings.db
- soft reboot
Hope it works.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just to share what worked for me. It wasn't working for me initially on a Sprint N6 either, but I really didn't want to factory reset. I was able to just recreate the steps you did but replacing the factory reset with a soft reboot and now it's working.
Since I had already made the changes unsuccessfully, I did have to delete then re-add the entries since it does seem to matter the order they were done.
**edit: welp, Nevermind. It worked a few times but now I'm back to seeing the error saying I may not be subscribed.
**edit #2: I had the letter t in "true" capitalized. Changed it to lower case, reboot and it's been working for two days!

For those that don't want to edit files (but don't mind spending a couple bucks)... I can confirm that "WiFi Tether Router" app is working as well.
Settings for the N6, as provided by the dev:
Interface wlan0
Method 2
Channel 1
Encryption wpa2-psk
"No Firmware Reload" <- UNCHECKED
Verify those, reboot, then open and enable (Root required for it to reset the radio).
*Edit: clarity

From what I could gather from the thread and personal trial and error, this is what worked for me.
1. Unlock
2. Root
3. Download root explorer and sqlite editor
4. Open sqlite editor
4.a - under the files tab navigate to "data/data/com.android.providers.settings/databases/settings.db/global"
4.b - click the + symbol to add a new entry
4.c - In name section put "tether_dun_required" all lower case exactly as it appears here.
4.d - In value section put "0" thats the number zero.
4.e - click save and exit program.
5 Open root explorer
5.a - Under the root tab browse to "/system"
5.b - long press on file "build.prop" choose "open in text editor" choose "yes" to remount as read-write and continue
5.c - add this as a new line to the bottom of the file "net.tethering.noprovisioning=true" all lower case exactly as it appears here. Just 1 uppercase letter here can make it not work.
5.d - save and exit
6 Reboot
7 Native tethering should work now.
Hope this helps. Let me know if I missed anything. Typed this up on my Nexus 9 tethered from my Nexus 6. :laugh:

Thanks for this. Worked perfect for me.

mengy007 said:
From what I could gather from the thread and personal trial and error, this is what worked for me.
1. Unlock
2. Root
3. Download root explorer and sqlite editor
4. Open sqlite editor
4.a - under the files tab navigate to "data/data/com.android.providers.settings/databases/settings.db/global"
4.b - click the + symbol to add a new entry
4.c - In name section put "tether_dun_required" all lower case exactly as it appears here.
4.d - In value section put "0" thats the number zero.
4.e - click save and exit program.
5 Open root explorer
5.a - Under the root tab browse to "/system"
5.b - long press on file "build.prop" choose "open in text editor" choose "yes" to remount as read-write and continue
5.c - add this as a new line to the bottom of the file "net.tethering.noprovisioning=true" all lower case exactly as it appears here. Just 1 uppercase letter here can make it not work.
5.d - save and exit
6 Reboot
7 Native tethering should work now.
Hope this helps. Let me know if I missed anything. Typed this up on my Nexus 9 tethered from my Nexus 6. :laugh:
Click to expand...
Click to collapse
This is what i did and worked for me and i only had to edit build.prop using the phone. I'm sure that it will work for everyone else. I'm also wondering if there is a way to edit/add the line we need for build.prop without having to root? something like "build.prop net.tethering.noprovisioning=True" in adb shell and it will add the line for us? hope someone can answer this for me please.
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: settings put global tether_dun_required 0
Edit the Build.Prop
6. Then open root explorer and open build.prop add net.tethering.noprovisioning=True to bottom

Thanks for the info. It works using Cricket sim
Sent from my Nexus 7 using Tapatalk