Develop Bugs

App to keep screen on for some apps

What are you using to keep the screen on during some aps. I have tried a few but haven't had much luck.
Hope others have had success

If charging, you could always enable the option (I think under Developer Options) to keep screen on during charging. Otherwise, you can also adjust screen timeout to something really high or Never.

I use Caffeine

I'm quite satisfied with KeepScreen
I tried IntelliScreen but it can do more than I actually need and so found it a bit too complex

If you already own Tasker, use it to do it.

khaytsus said:
If you already own Tasker, use it to do it.
Click to expand...
Click to collapse
Do you have a "script?" for tasker?

Have you tried Screebl?
Works perfectly for my tablet, has lots of settings you can play with if you need, but haven't need to at all myself though. try it out! Free version before v
https://play.google.com/store/apps/details?id=com.keyes.screebl.lite
Don't forget to hit thanks if that helps! Or if you just feel like it, that would be okay too
Sent from my Nexus 7 using xda premium

pmgreen said:
Do you have a "script?" for tasker?
Click to expand...
Click to collapse
No need, create a Profile for a context when said app is running, make the Task change the Screen On time. Nothing complicated.

pmgreen said:
What are you using to keep the screen on during some aps. I have tried a few but haven't had much luck.
Hope others have had success
Click to expand...
Click to collapse
Try Notification Toggle. There's a toggle for this and many more, so you don't have to use for every setting a separate app.
{
"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"
}

Stock original etc/hosts file needed...

So can anyone just tell me if the lines in the hosts file are "stock"? I am afraid AdAway might have messed it up or something. Currently mine lookes like this:
{
"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"
}
Thanks! BTW: I am on stock Android 4.4.2
Gesendet von meinem Nexus 7 mit Tapatalk

My stock ROM N7 2013 4.4.2 has only one entry:
127.0.0.1 localhost
FWIW, in your file, the :1 is for ipv6, it's the equivalent of 127.0.0.1, and the last entry is commented out (the #), and has no effect.
In short yours is not messed up, it's just not stock.

@mdamaged thanks for the reply! I used the # to comment it out because I had problem connecting to Google server (orange WiFi bar) and this fixed my problem. What is actually the stock one? Without the last two lines? Do you think adaway or any other xposed module created the 2 lines?
Gesendet von meinem Nexus 7 mit Tapatalk

ChiDi9901 said:
@mdamaged thanks for the reply! I used the # to comment it out because I had problem connecting to Google server (orange WiFi bar) and this fixed my problem. What is actually the stock one? Without the last two lines? Do you think adaway or any other xposed module created the 2 lines?
Gesendet von meinem Nexus 7 mit Tapatalk
Click to expand...
Click to collapse
No problem.
The stock one has the one line I posted.
127.0.0.1 localhost
...nothing else.
Yes, the 127.0.0.0/8 range is a rfc1122 address range, it is (normally) not routable over the internet, so indeed this would cause problems trying to connect to hosts with hostnames which have this mapped to them. This would likely be done by something which is made to stop ads being served, or from services from being contacted.
Given the hostnames being mapped I'd guess it was something trying to prevent communicating with the google services, not ad sites, not knowing what xposed modules were in use that's all I can say.

[Q] How to enable write to Ext SD for all apps?

I know there 's a ROM out in the dev section that fixes that, but I'd like to know how to do it manually, without flashing another ROM,,,can anyone help?
Thank you!

Is this what you're looking for?
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en

Cablespider said:
Is this what you're looking for?
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Click to expand...
Click to collapse
Thanks, I tried that but it didn't work

You can download root toolbox and there is an option for it there.
Sent from my LG-D851 using XDA Free mobile app

Get kitkat external sd fix by geeksoft.
Sent from my LG-D851 using Tapatalk

Use Root Explorer.
Enable R/W
Go to /etc/permissions
Edit platform.xml as the bottom of the picture (add "media_rw" line).
Save and reboot
{
"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"
}

mingkee said:
Use Root Explorer.
Enable R/W
Go to /etc/permissions
Edit platform.xml as the bottom of the picture (add "media_rw" line).
Save and reboot
Click to expand...
Click to collapse
This is the only way it should be done.

Thanks all for the suggestions - I tried the geeksoft apk and it did the trick. Actually, the first one I tried probably worked also, but the app I was using wouldn't work (iTag)...but i switched to another (Mp3Edit) and that worked like a charm!
Incidentally, I opened that permission xml file to look at any changes, and it appears the line was added just as it should.
Thanks again!

[MOD] Edit features.xml for International Network Indicators

Thanks to @siraltus, I am happy to report that his trick for getting the international icons that he shared in my thread in the Note 4 forum also works on a rooted S6 Edge. http://forum.xda-developers.com/showthread.php?t=2951057
Once rooted, edit system/csc/features.xml with an app like Root Explorer and this line:
<CscFeature_Framework_ReplaceDataTypeIconAsOpBrand>OYC</CscFeature_Framework_ReplaceDataTypeIconAsOpBrand>
Save, exit, and reboot.
{
"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"
}

Glad I could help. BTW, you should change your title, you're not editing the build.prop, you're editing the CSC feature set.

siraltus said:
Glad I could help. BTW, you should change your title, you're not editing the build.prop, you're editing the CSC feature set.
Click to expand...
Click to collapse
D'oh! LOL
Interesting thing though is that I am roaming up in Canada this week, and the phone is displaying the icons for the carrier on which I'm roaming. Bell shows 4G+ for LTE.

dc/dc said:
D'oh! LOL
Interesting thing though is that I am roaming up in Canada this week, and the phone is displaying the icons for the carrier on which I'm roaming. Bell shows 4G+ for LTE.
Click to expand...
Click to collapse
Hmm, try adding that line to others.xml, too. It's a "secondary" CSC feature file.

siraltus said:
Hmm, try adding that line to others.xml, too. It's a "secondary" CSC feature file.
Click to expand...
Click to collapse
I'll give that a try and report back.

It does not appear to have worked.

A combination of this whole adding vsw to device name in build prop will get rid of the s finder and quick connect in the pull down menu.. I actually use the xx method for device name to grant myself the combo signal style, combining download booster days signal and Wi-Fi into one blocky block
. very nice

Wrong. Sry pls delete
Gesendet von meinem SM-G928F mit Tapatalk

Reset dpi using adb and Swiftkey is messed up now

I have been resetting my dpi for years without issue. Now that I am systemless rooted on the 5X, I had to use adb to change dpi. Before I always used a file editor. So for some reason, resetting in adb gets me the Swiftkey keyboard in my pic. Nothing I do seems to fix it. Tried reinstalling Swiftkey, but it comes out the same. Google keyboard is not affected, nor is anything else. Also, if i change dpi using a file editor then Swiftkey works as it should. Anybody know what is happening here?
{
"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"
}

You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.

PhoenixTank said:
You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.
Click to expand...
Click to collapse
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.

jackdubl said:
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.
Click to expand...
Click to collapse
Sounds like you have it set up correctly, but just in case, checking output with the command here might help:
https://www.reddit.com/r/nexus6/com...i_to_493_swiftkey_is_now_freaking_out/cnc198j
FWIW, I have not tried changing on my 5X but have on my Shield K1 and ran into this.