Develop Bugs

[App] LCD Density Changer v3.0 (update + link to new thread)

One last note: Users that have installed the previous versions should/ are adviced to download the new version from the other thread. The new version addresses the problem that one can't boot into the system because of a conflict between a particular density setting and a launcher and or widget.
The apk's attached to this post are now removed. Head over to the new thread to download the app.
Update v2.1 * addresses some problems other devices than the Galaxy S variants had with the former version. * some minor cosmetic changes. (note: I also opened a thread on the android developers forum, so other devices can profit from this tweak as well. I have decided to post my updates there and, of course, on the Android Market. The new thread can be found http://forum.xda-developers.com/showthread.php?t=765639
Update v2.0 * Added option to turn on/off compability settings for app scaling. * Possibility to restore default density setting (the default density that is stored is the density of your screen when you run the tool for the first time). * Added helpfile * Added option to reboot automatically after changing the density.
Update v1.1: a) Optimization of code: faster, more safe b) some cosmetic changes
I created a little app to play with the LCD Density Settings as described in this thread. The app lets you set the LCD Density Setting without edditing the build.prop file (directly).
Be aware that the tweak only will work with launchers like LauncherPro. It doesn't work with Samsungs own TouchWizardLauncher. (If you insist on experimenting with the TWLauncher, make sure that you have the USB Debugger enabled to get you out of the mess ).
Only requirements for this app to work is that you are rooted and have su, busybox and Superuser installed (in fact you have all those apps installed when you have rooted your device the "regular" way) AND that you like to experiment with things.. if you know what I mean.
Click to expand...
Click to collapse
Screenshots
{
"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"
}
Instead of a donation you can consider to buy the app from the Android Market (0,75 euro). Search for LCD Density Changer or scan:
I will keep this app for free for download and always up to date here on this forum!
Future work
I will keep on investigating how the software environment can be made compatible with lower density settings. My intention is to update the app constantly with new tweaks and settings so that eventually it can function as a full control panel for the density tweak.
Thanks to jdsemler who discovered this tweak.
Note: if you don't want to take any risk, make sure you make a nandroid backup. Although the new version is reported to be error-free, it is always a good idea to create a full system backup before one is going to play with these kind of tools.
(also) thanks to
* bratfink for giving some very useful input
* Cutefox for bringing to our attention that turning of the compatibility mode via an app called "Spare Parts" solves the scaling problem.
* Nelson Mandela for bringing peace
* Mahatma Ghandi for his inspiration
* Bell for inventing the phone
* Samsung for the upcomming GPS fix
* and many, many others I forgot to mention.
Download history
LCD Density Changer.apk (16.3 KB, 223 views)
LCD Density Changer v1.1.apk (17.6 KB, 91 views)
LCD Density Changer v2.0.apk (28.9 KB, 264 views)

What are the standard values?

HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.

jdsemler said:
HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.
Click to expand...
Click to collapse
Yeah, it's such a nice tweak. Thanks again! Any progression on the scaling issue?

Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.

Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.

jdsemler said:
Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.
Click to expand...
Click to collapse
nonetheless a very interesting problem. The thing that intrigues me is that some apps run full screen without any problem. I'm gonna decompile those apps later on to see how they have defined the layout.
BTW can you upload some of the dell streak prop files that may be relevant in this case?

lpsi2000 said:
Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.
Click to expand...
Click to collapse
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder

I attached my default (HDPI setting) Samsung build.prop and my current Dell Streak build.prop.
The Streak build.prop has a different fingerprint, because I'm using the 2.1 build and had to have a recognized (by Market) fingerprint to get to my protected apps.
The Streak does not have a /system.prop file, unlike the Samsung.

System.prob
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?

bratfink said:
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?
Click to expand...
Click to collapse
Makes sense. Question though, when do all these prop files load? Don't think it will work, but can an app at boottime change the system.prob values so that it doesn't affect the modified dpi value?

tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?

asrrin29 said:
tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?
Click to expand...
Click to collapse
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?

appelflap said:
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?
Click to expand...
Click to collapse
yes. when I try to use su I get
[1] Segmentation fault su

appelflap said:
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder
Click to expand...
Click to collapse
Yes, the app is what I use and I can't even get su to work under adb shell. It looks like I am going to need to re flash.

Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...

asrrin29 said:
yes. when I try to use su I get
[1] Segmentation fault su
Click to expand...
Click to collapse
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?

appelflap said:
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?
Click to expand...
Click to collapse
not sure that's going to work, because I can't get super user access until I grant it permission without a ui.

F_L_Abs said:
Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...
Click to expand...
Click to collapse
I'm sorry ... The Android SDK isn't the best toolkit to do such low level system hacking. The security levels are high, and to break them you have to do all kind of weird stuff. Anyway, I changed the first post and put a extra warning in it.

Is there a way to use Odin 3 to restore the files changed?

[MOD] Freeze Battery-Draining Services | 6/14

This Mod is flashed through CWM to enable 2 simple all-in-one commands to Freeze/Defrost SNS, DRM, and System Updates. Downloads at the end of this post. Read on to learn what they do and how to easily use them!
Fully Flash-able Test Version HERE
Freeze SNS, DRM, and System Updates for Better Battery
These services are, generally, best kept frozen 99.9% of the time. Not deleted, as I've experienced problems if they are actually removed, but disabling them saves me noticeable battery life.
You can use Titanium Pro, MyToolbox, ,Bloat Freezer, or Mybackup Pro to freeze services, but that's only after you've installed a rom. Then once you boot in, you have to buy and download that app, and then navigate a huge list of services to freeze.
But it only takes one line of code per service you want to freeze. That's right, the following commands can be entered into a terminal like Terminal Emulator to disable these processes:
Code:
su [I](Gains root)[/I]
pm disable com.sec.android.providers.drm [I](Disables DRM launcher)[/I]
pm disable com.sec.android.app.sns [I](Disables sns)[/I]
pm disable com.samsung [I](Disables updates)[/I]
However, these commands are lengthy, not easily memorized, and just a pain to write. The best solution I can come up with is to simplify the commands.
[Note] You do not want to do this if you don't understand how freezing these services may affect your day-day use. This will save some battery at the definite cost of DRM content functionality and Facebook Contact integration.
How To Use This Mod:
Still using Terminal Emulator, after you flash one of the linked .zip files, all you will have to type is the following:
To Freeze Services:
Code:
su
superfreeze
To Defrost Services:
Code:
su
superdefrost
DOWNLOADS:
Click Here!
If you like my work, click the Thanks button or donate a beer!
I am still in the works to make this work entirely solo once flashed from CWM.
PS: If you're looking for a free alternative to any of the apps I listed up above, this isn't it. This is only one small, dedicated part of those apps. I highly recommend buying one of them, you'll find them very useful.
PPS: This mod, and subsequent versions of it(hopefully!), is for the Epic 4G. I cannot guarantee that the script is accurate to any other phone. But the commands themselves are universal across Android.
Thanks to paulobrien for his explanation found here!

I can't answer you script question, but I have one of my own. Are those commands permanent, or will I have to type those in everytime I turn my phone back on? I'm assuming the latter, since you want to be able to do it easier.
Sent from the only thing i need.

zanderman112 said:
I can't answer you script question, but I have one of my own. Are those commands permanent, or will I have to type those in everytime I turn my phone back on? I'm assuming the latter, since you want to be able to do it easier.
Sent from the only thing i need.
Click to expand...
Click to collapse
These commands are indeed permanent on reboot. Pm Disable is exactly the function apps like Titanium use when "freezing" services. The goal is, I would like these commands to be executed while my rom is installing. I used a similar .zip file as a skeleton for the layout, but I'm just not sure what additional coding is required to make this work. I'm 99.9% positive it can be done.

Oh ok. So I now don't have to disable the drm or sns anymore. Cool, if I ever needed to re-enable them, what would I type in?
Sent from the only thing i need.

Surprisingly logical, you just have to type enable instead of disable.
-Sent from my Random Epic.

Ok, I thought so, but sometimes things aren't as simple as could be. Good luck on your script.
Sent from the only thing i need.

zanderman112 said:
Ok, I thought so, but sometimes things aren't as simple as could be. Good luck on your script.
Sent from the only thing i need.
Click to expand...
Click to collapse
Too often not as simple as it could be! There must be some sort of call function I'm missing. Lol
-Sent from my Random Epic.

So it seems no matter how I try to launch this, from etc/lib.d, as a tool, from data/local... etc. It doesn't seem to have any effect if not run from within Android itself.

RandomKing said:
So it seems no matter how I try to launch this, from etc/lib.d, as a tool, from data/local... etc. It doesn't seem to have any effect if not run from within Android itself.
Click to expand...
Click to collapse
I really wish I could help.
Sent from my Epic 4G, awaiting official gingerbread

zanderman112 said:
I really wish I could help.
Sent from my Epic 4G, awaiting official gingerbread
Click to expand...
Click to collapse
It's a shame, it'd be nice to have a rom install with some services like this disabled by default. Then there could be a matching patch to re-enable them if needed.

RandomKing said:
It's a shame, it'd be nice to have a rom install with some services like this disabled by default. Then there could be a matching patch to re-enable them if needed.
Click to expand...
Click to collapse
Yeah, it would be handy.
Sent from my Epic 4G, awaiting official gingerbread

I'm guessing that the Android runtime system has to be fully initialized and running for the pm command to work, and it's not in the limited runtime of the recovery environment.
Sent from my mind using telepathitalk

dwallersv said:
I'm guessing that the Android runtime system has to be fully initialized and running for the pm command to work, and it's not in the limited runtime of the recovery environment.
Sent from my mind using telepathitalk
Click to expand...
Click to collapse
That seems to be the problem, because I've gotten the tiny files themselves to run in the terminal, which is at least useful for streamlining this operation! But I can't get them to do anything in recovery, it just has no effect.

So I have come to the conclusion that this cannot be done from CWM due to reasons I've explained in post #1.
However, I have posted a workaround CWM flash-able which, still using Terminal Emulator, simplifies the commands down to 2 simple codes.
UPDATE: Turned out I posted bad .zip files with out of date updater scripts. The links have been fixed and should work as described in Post #1!

RandomKing said:
So I have come to the conclusion that this cannot be done from CWM due to reasons I've explained in post #1.
However, I have posted a workaround CWM flash-able which, still using Terminal Emulator, simplifies the commands down to 2 simple codes.
Click to expand...
Click to collapse
Sweet! At least you kinda got it.
Sent from my Epic 4G, awaiting official gingerbread

zanderman112 said:
Sweet! At least you kinda got it.
Sent from my Epic 4G, awaiting official gingerbread
Click to expand...
Click to collapse
Yup, kinda! The guys that wrote apps to freeze services deserve a lot of credit. They are fairly easy to use in bulk.
I wish I could make this automatic, but this way I only have to type two easily memorized commands to stop/start the 3 services I hate most!
UPDATE: Mediafire mirror links posted for when megaupload wants to be wonky.

You might be able to make this fully automatic with tasker. There is an option "device boot," there is the ability to launch an app, and to type, then close the app. Might look a little sloppy, but it should definitely work. I'll try it and report back later today.
EDIT: Works like a charm. For the Context, go into Event, System, Device Boot. For the Tasks, choose App, Load App, Terminal Emulator, then Input, Type, enter the text, then choose Input, Button, Back twice to close out of the app, as the Kill command will just restart it.
For what it's worth, there must be a way to have an application start off as disabled, because that's how CIQ starts, as far as I know. Perhaps the dev of the paid application Autostarts can shed some light on it for you.

Pointless816 said:
You might be able to make this fully automatic with tasker. There is an option "device boot," there is the ability to launch an app, and to type, then close the app. Might look a little sloppy, but it should definitely work. I'll try it and report back later today.
EDIT: Works like a charm. For the Context, go into Event, System, Device Boot. For the Tasks, choose App, Load App, Terminal Emulator, then Input, Type, enter the text, then choose Input, Button, Back twice to close out of the app, as the Kill command will just restart it.
Click to expand...
Click to collapse
Thats a nifty trick! Now I could patch Tasker and it's data into the rom itself. Now here's the question, is Tasker a persistently running battery draining service?
Pointless816 said:
For what it's worth, there must be a way to have an application start off as disabled, because that's how CIQ starts, as far as I know. Perhaps the dev of the paid application Autostarts can shed some light on it for you.
Click to expand...
Click to collapse
That may be true, but SNS, Updates, and DRM have to run consistently. Unlike some certain apps that run non-stop for no reason.

Just make the zip add a file to init.d that executes the command on next boot then deletes itself...
Sent from my SPH-D700 using XDA App

chris41g said:
Just make the zip add a file to init.d that executes the command on next boot then deletes itself...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I actually tried that, but the command "pm disable" just doesn't do anything from recovery for me. Unless I'm not calling for a function I need or something. Still toying around with it. I even tried to just patch it into one of the existing init.d files, but still no result.
Update: I'm a noob at developing. I can roughly understand existing script enough to rearrange it, but if somethings missing, I probably can't spot it. Haha

[APP][PORT] S Voice for Droid Incredible 2!!!

All this courtesy the leak: http://forum.xda-developers.com/showthread.php?t=1646610
For ICS ROMS ONLY!
Update: Most bugs fixed.
Link for S Voice Zip for Droid Incredible 2: [Dropbox Link]http://goo.gl/od4gS
Installation:
=========
1) Wipe Cache and Dalvik (don't wipe data, it will remove all your apps.) [RECOMMENDED]
2) Install Zip from Recovery
3) ??? Profit!
Alternate/Manual Method:
If zip is causing trouble or wanna do it without a reboot, copy the apk into /system/app/ and the library file into /system/lib/ and set 644 permissions aka rw-r--r-- for both files. Profit!
How to use:
=========
0) Set the Voice input as "Samsung powered by Vlingo".
1) Launch app.
2) Use the app once the introduction is done... Profit!
Known Issues:
===========
* Quitting the app before finishing the introductory setup causes FCs in subsequent launches. Only workaround so far is to clear app data.
* Now you can set personalized commands instead of "Hi Galaxy". But, some personalized commands (like play music) will force close the app, as the corresponding Samsung music app/Camera app etc. is missing. Can't help!
* You tell me!
CHANGELOG:
=========
[*] v1.2: Added the signed version of the app to fix network errors. Thanks to: http://forum.xda-developers.com/showthread.php?t=1662255
[*] v1.1: Fixed FC when setting personalized commands.
[*] Initial Release. Fixed FC bug by including a library file "libsvoxtts.so" present inside the APK at /system/lib/
Click to expand...
Click to collapse
Cheers!

This only works on ICS? I did it on GB and don't have the app.

Yup, Android 4.0 or later only...
Sent from my ADR6350 using XDA

How can I remove it from my phone then? Its just hogging up 25MB of space now.

jakob95 said:
How can I remove it from my phone then? Its just hogging up 25MB of space now.
Click to expand...
Click to collapse
Just go to any root file explorer.
Navigate to /system/app/. Delete voicetalk.apk
Navigate to /system/lib/. Delete libsvoxtts.so
Sorry, I forgot to mention ICS only

litetaker said:
Just go to any root file explorer.
Navigate to /system/app/. Delete voicetalk.apk
Navigate to /system/lib/. Delete libsvoxtts.so
Sorry, I forgot to mention ICS only
Click to expand...
Click to collapse
BUMP!! Updated to fix some bugs
EDIT: Btw folks, this seems to be only a bloody novelty! I tried calling my friend by saying his name... It successfully recognized the command and the name.. But it took bloody insane time to actually make the call!!! If anyone uses this to improve productivity as "Samsung" says, they'll lose their job the very same day for so! Well, it could be possible that since it is not meant for our phone AND/OR since the SGS3 has a quad core Tegra 3 (and the US version will probably have the S4 which is very powerful too) it may work well on those devices and not ours...
Anyway, hope a more seasoned dev than me can step in and tweak it and improve efficiency.
I'll be logcating away today and trying to improve this app's efficiency AND iron out some more bugs!

litetaker said:
BUMP!! Updated to fix some bugs
EDIT: Btw folks, this seems to be only a bloody novelty! I tried calling my friend by saying his name... It successfully recognized the command and the name.. But it took bloody insane time to actually make the call!!! If anyone uses this to improve productivity as "Samsung" says, they'll lose their job the very same day for so! Well, it could be possible that since it is not meant for our phone AND/OR since the SGS3 has a quad core Tegra 3 (and the US version will probably have the S4 which is very powerful too) it may work well on those devices and not ours...
Anyway, hope a more seasoned dev than me can step in and tweak it and improve efficiency.
I'll be logcating away today and trying to improve this app's efficiency AND iron out some more bugs!
Click to expand...
Click to collapse
Let's hope so. lol this was the only thing that kinda had me excited when i seen the SG3 release press thingy. oh and the hold phone to your hear to call someone your texting. other than that i didnt see much to get excited about ... thanks for your hard work btw.

litetaker said:
All this courtesy the leak: http://forum.xda-developers.com/showthread.php?t=1646610
For ICS ROMS ONLY!
Update: Most bugs fixed.
Link for S Voice Zip for Droid Incredible 2: [Dropbox Link]http://goo.gl/e2dOr
MD5: c1252f77e00d43b7de23430cae728d04
Installation:
=========
1) Wipe Cache and Dalvik (don't wipe data, it will remove all your apps.) [RECOMMENDED]
2) Install Zip from Recovery
3) ??? Profit!
Alternate/Manual Method:
If zip is causing trouble or wanna do it without a reboot, copy the apk into /system/app/ and the library file into /system/lib/ and set 644 permissions aka rw-r--r-- for both files. Profit!
How to use:
=========
0) Set the Voice input as "Samsung powered by Vlingo".
1) Launch app.
2) Use the app once the introduction is done... Profit!
Known Issues:
===========
* Quitting the app before finishing the introductory setup causes FCs in subsequent launches. Only workaround so far is to clear app data.
* Now you can set personalized commands instead of "Hi Galaxy". But, some personalized commands (like play music) will force close the app, as the corresponding Samsung music app/Camera app etc. is missing. Can't help!
* You tell me!
Cheers!
Click to expand...
Click to collapse
Server error after install. Can't get it to recognize any commands. Wiped cache and dalvic upon install and wiped app data after initial setup bc it wasn't working then either. Thanks keep up the hard work. May try the Apk version. Oh and gallery keeps force closing after installation s voice. So unfortunately I can't attach the screen shot lol.
Edit nvm sent report instead of clicking ok and other fixed it lol.
Edit...
{
"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"
}
Sent from my Incredible 2 using xda premium

xM Minton Mx said:
Server error after install. Can't get it to recognize any commands. Wiped cache and dalvic upon install and wiped app data after initial setup bc it wasn't working then either. Thanks keep up the hard work. May try the Apk version. Oh and gallery keeps force closing after installation s voice. So unfortunately I can't attach the screen shot lol.
Edit nvm sent report instead of clicking ok and other fixed it lol.
Edit...
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thanks for the report. The gallery doesn't force close for me. Which ROM did you install it on? And the server error may be a Samsung problem. Happened to me a couple times too. Or it may be an issue with missing libraries... could you obtain a logcat via ADB and I'll have a look at it...
Thanks
Sent from my Incredible 2 using XDA

litetaker said:
Thanks for the report. The gallery doesn't force close for me. Which ROM did you install it on? And the server error may be a Samsung problem. Happened to me a couple times too. Or it may be an issue with missing libraries... could you obtain a logcat via ADB and I'll have a look at it...
Thanks
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
Samsung shut down the servers till the sgs3 releases, rendering the app useless as of now. Wait till the servers are back up again...
Sent from my Incredible 2 using XDA

litetaker said:
Samsung shut down the servers till the sgs3 releases, rendering the app useless as of now. Wait till the servers are back up again...
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
The app now works. No more network errors thanks to signed app at: http://forum.xda-developers.com/showthread.php?t=1662255

litetaker said:
Thanks for the report. The gallery doesn't force close for me. Which ROM did you install it on? And the server error may be a Samsung problem. Happened to me a couple times too. Or it may be an issue with missing libraries... could you obtain a logcat via ADB and I'll have a look at it...
Thanks
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
Honestly I have no idea how to do a logcat. Never really had to. Usually the problems I end up having have already occurred with someone else so I just sit back and watch for the fix. Anyways about to try the new download. THANKS!

litetaker said:
The app now works. No more network errors thanks to signed app at: http://forum.xda-developers.com/showthread.php?t=1662255
Click to expand...
Click to collapse
Great job. You got the servers to work... Only problem i see now is that... I'm not in Cambridge MA lol. Every location search or weather query says it. (yes I made sure GPS was on lol) noticed in the help menu it also says something about MA. Anyways thanks again.
Sent from my Incredible 2 using xda premium

Well this app works, but fc's and is kinda a pain. Good work lite, seriously. I'm going to wait till I get a sg3.
Sent from my Incredible 2 using XDA

Nickolas said:
Well this app works, but fc's and is kinda a pain. Good work lite, seriously. I'm going to wait till I get a sg3.
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
If you know how to get a logcat I'd be glad to have a look and see what is it that is causing the FCs. If you don't know how to do it, there is an app on Play to do that...

Eh I gave up on it sry
Sent from my vivow using xda premium

LBE Security

I tried sideloading this app from an apk on my optimus v. It installed and opened fine but then it started shutting off my screen and it became unresponsive. Had to reflash JR5 to fix it. Just a heads up, do not install it.
Sent from my Nexus 7 using xda app-developers app

lulz

fleshdeep said:
I tried sideloading this app from an apk on my optimus v. It installed and opened fine but then it started shutting off my screen and it became unresponsive. Had to reflash JR5 to fix it. Just a heads up, do not install it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Development died on that app a while back .. wonder if the privacy was actually private ??

That would be a bummer if it's dead - actually worked very good on my photon 2.3.4/5 versions - especially in customizing app specific permissions / overall surprised to see what's really going on albeit the listed, and at often times - vague permissions listed on the play store.
As said, it's [LBE] does not work for jellybean / wish there was a simply comparable app that will run just like this on stock/root only builds - pdroid is all I hear of as an alternative, but it requires a few steps/patch - not even sure if it works better and optimized for N7.
Having a permissions manager goes a long way - even if you look at things closely from legitimate market sources - it is only getting worse. I'm being far from naive here Although LBE's origins were questionable and skepticism grew, enough people had checked it out to their best ability; in concern to why the app itself needed data connection, and what (if anything serious) was being sent. Haven't seen anything comparable to its finite permissions control upon installing anything. The N7 still needs something for sure...,
What else is out there?

Here is another thread for lbe 4 with english translaten

sirscrubsalot said:
That would be a bummer if it's dead - actually worked very good on my photon 2.3.4/5 versions - especially in customizing app specific permissions / overall surprised to see what's really going on albeit the listed, and at often times - vague permissions listed on the play store.
As said, it's [LBE] does not work for jellybean / wish there was a simply comparable app that will run just like this on stock/root only builds - pdroid is all I hear of as an alternative, but it requires a few steps/patch - not even sure if it works better and optimized for N7.
Having a permissions manager goes a long way - even if you look at things closely from legitimate market sources - it is only getting worse. I'm being far from naive here Although LBE's origins were questionable and skepticism grew, enough people had checked it out to their best ability; in concern to why the app itself needed data connection, and what (if anything serious) was being sent. Haven't seen anything comparable to its finite permissions control upon installing anything. The N7 still needs something for sure...,
What else is out there?
Click to expand...
Click to collapse
Well - a friendly bump to an imprtant topic... this already got buried fast amidst the many posts... seems that somebody has to do it. Seriously should not be overlooked

defim said:
Here is another thread for lbe 4 with english translaten
Click to expand...
Click to collapse
this is:
http://forum.xda-developers.com/showthread.php?t=1422479

What about appguard?
its what I use to manage permissions on an app.
http://www.backes-srt.de/produkte/srt-appguard/
Its in German but just select
"Download der appguard.apk"

[CM11] Netflix Fix

{
"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"
}
Description
This is a flashable zip of rlasalle15's script to fix screen corruption/artifacts in the Netflix app on CyanogenMod 11. This may or may not persist through netflix updates so if it stops working, try flashing it again!
Mirror(s)
Google Drive
Thanks to
rlasalle15 for the original script.
CyanogenMod for the edify scripting language.
XDA:DevDB Information
CyanogenMod 11 Netflix Fix Zip, a Tool/Utility for the Sprint LG Optimus G
Contributors
VoluntaryMan, rlasalle15
Version Information
Status: Stable
Created 2014-01-14
Last Updated 2014-04-03

Freakin sweet. Good lookin out brother!

Has anybody got this flash to work? I'm on CWM and it fails. Likewise my ROM toolbox won't let me move the file. Then again I'm running beanstalk

HdMsTrTeCh said:
Has anybody got this flash to work? I'm on CWM and it fails. Likewise my ROM toolbox won't let me move the file. Then again I'm running beanstalk
Click to expand...
Click to collapse
Try v1, v2 seems to be borked.

Full disclosure, but I'm intoxicated at the moment. Anyway, I greatly appreciate this. I haven't had Netflix working in quite awhile. I tried other method but was still having problems. Perhaps I wasn't getting the permissions right. I tried flashing version 2. It kept failing. I just now tried version 1 after you mentioned version 2 wasn't working right. I still had issues at first. I was just about to give up hope, and assume that my device hated me, but I messed around with the permissions once more, and... Eureka. It works great. So, really, thanks.
Sent from my LG-LS970 using xda app-developers app

pimpmyrom
Jeremy6820 said:
Full disclosure, but I'm intoxicated at the moment. Anyway, I greatly appreciate this. I haven't had Netflix working in quite awhile. I tried other method but was still having problems. Perhaps I wasn't getting the permissions right. I tried flashing version 2. It kept failing. I just now tried version 1 after you mentioned version 2 wasn't working right. I still had issues at first. I was just about to give up hope, and assume that my device hated me, but I messed around with the permissions once more, and... Eureka. It works great. So, really, thanks.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Didn't work for me. I used pimp my rom and faster media streaming under network and internet which improved things significantly. A little stutter at first then fine. Couldn't use it at all before this.

compudoc50 said:
Didn't work for me. I used pimp my rom and faster media streaming under network and internet which improved things significantly. A little stutter at first then fine. Couldn't use it at all before this.
Click to expand...
Click to collapse
This zip only fixes graphical distortions during playback, it has no effect on any other factors. I'm glad it was of help to you :good:

Thanks :good:
This fixed Netflix on my Sony Xperia Tablet Z running CM11. :highfive:

worked for me
I'm using an Optimus G Pro E980 and this fix worked for me. Thanks!

This just makes my netflix app crash at launch. Any way to uninstall the zip again?
EDIT: Just went to system/etc/init.d with root explorer and changed permissions to the same as the other files in that folder. Still crashes at launch.
I can get it to work using an older version of netflix and no patch. V 3.0.1 build 1016
You can get it here: http://forum.xda-developers.com/showpost.php?p=46545345&postcount=2942

jackiass said:
This just makes my netflix app crash at launch. Any way to uninstall the zip again?
EDIT: Just went to system/etc/init.d with root explorer and changed permissions to the same as the other files in that folder. Still crashes at launch.
Click to expand...
Click to collapse
Pretty sure the latest Netflix update with all of the UI changes broke this fix. It worked perfectly before the last app update.

spackmanbr said:
Pretty sure the latest Netflix update with all of the UI changes broke this fix. It worked perfectly before the last app update.
Click to expand...
Click to collapse
I don't have the Optimus G anymore so I can't do anything about it :\
Hopefully someone else can figure it out.

VoluntaryMan said:
I don't have the Optimus G anymore so I can't do anything about it :\
Hopefully someone else can figure it out.
Click to expand...
Click to collapse
Not a problem and not your fault, plus I'm using Chromecast most of the time anyway. The original script just doesn't work anymore. I just wanted to let jackiass know why he was getting force closes.
M8?

spackmanbr said:
Not a problem and not your fault, plus I'm using Chromecast most of the time anyway. The original script just doesn't work anymore. I just wanted to let jackiass know why he was getting force closes.
M8?
Click to expand...
Click to collapse
Nah, I got a Nexus 5. I was considering the One Max but I was just fed up with the non-Nexus experience.

Thanks for the replies. I can still watch movies on my bus rides using the older apk, though it would be nice with the updated functionality of the new one. I spoke with netflix support. The supporter first told me how much he loved my phone and CM and then told me it was no problem at all. I just had to revert to the original firmware of my phone, and everything should be hunky dory. Thanks for the help netflix!?

jackiass said:
Thanks for the replies. I can still watch movies on my bus rides using the older apk, though it would be nice with the updated functionality of the new one. I spoke with netflix support. The supporter first told me how much he loved my phone and CM and then told me it was no problem at all. I just had to revert to the original firmware of my phone, and everything should be hunky dory. Thanks for the help netflix!?
Click to expand...
Click to collapse
And here we have a perfect example of how useless customer support usually is

I have issues with Netflix also on my home built OmniROM for Asus TF101 tablet. The 98netflix script used to work like a charm, persisting through reboots and Netflix app restarts. Since the last 2 or 3 Netflix updates though I found that if I change the player type in the script to "10" and reboot, then Netflix app will start up fine and let me watch videos. If I stop the video, then back out to the main Netflix screen, the app force closes and any attempts to restart it result in the usual force close. If I reboot or manually rerun the script (with the "10" values) from a terminal as su, then Netflix is partially fine again, until I back out of the app or close it. It's like settings aren't being saved and I can verify that the nfx_preferences are changed at boot to reflect the player type before staring the Netflix app, but are gone after Netflix has ran. My hardware is Tegra 2 10.1" tablet for what it is worth.

sidneyk said:
I have issues with Netflix also on my home built OmniROM for Asus TF101 tablet. The 98netflix script used to work like a charm, persisting through reboots and Netflix app restarts. Since the last 2 or 3 Netflix updates though I found that if I change the player type in the script to "10" and reboot, then Netflix app will start up fine and let me watch videos. If I stop the video, then back out to the main Netflix screen, the app force closes and any attempts to restart it result in the usual force close. If I reboot or manually rerun the script (with the "10" values) from a terminal as su, then Netflix is partially fine again, until I back out of the app or close it. It's like settings aren't being saved and I can verify that the nfx_preferences are changed at boot to reflect the player type before staring the Netflix app, but are gone after Netflix has ran. My hardware is Tegra 2 10.1" tablet for what it is worth.
Click to expand...
Click to collapse
This script is basically telling netflix to use a different mode than what it thinks is best for your device. I think the new netflix apps might be checking that mode on exit and overwriting the changes made by the script (which runs at boot).
You could set a shortcut to the script in your application drawer and run it after exiting netflix.

Is there any news on solve the problem? Is there a new script? Netflix is great, but I hate get back to stock rom for use it :´(

lfuentes said:
Is there any news on solve the problem? Is there a new script? Netflix is great, but I hate get back to stock rom for use it :´(
Click to expand...
Click to collapse
We fixed it for Asus tf101 Tegra 2 tablet. It seems to survive updates to Netflix so far, but is Tegra 2 specific.
Sent from my SM-N900T using XDA Premium HD app