I finally got the hotspot hack working but I was having the browser scrolling issue. After doing some reading, I found out that instead of using the op's framework.jar file, I had to extract and use the framework.jar out of e4gt-nociq-signed_hsh.zip file to fix the broken browser scrolling.
After the change, both the hotspot and browser scrolling seemed to work fine. But now I have the overscrolling effect turned on and my bouncing effect is gone.
Is there anyway I can disable the overscrolling effect? I actually prefer the stock bouncing effect. Also, which of these 2 effects is smoother in terms of scrolling? TIA
Related
Hi!
I've just flashed my samsung s with an official firmware xxjf3 (because I've made a mistake with the previous one....)
Now the phone is back like a new one, but I've noticed that the transition between homescreen and app screen has a very annoying and slow fade in/out that all other pages (options, direct app, widget and so on) don't have (they have another transition, faster and better - don't know how to explain).
It is possible to change this particular transition either by flashing the ohone again or change some file/hidden setting?
Thanks.
Running a non-rooted G2.
Anyone else notice sluggish screen rotation when going from landscape to portrait or vice versa? It seems like it takes over 1s to switch, closer to 1.5s I would say just trying to count out loud.
The only running apps I have besides the stock ones are Tasker, LauncherPro Plus, Beautiful Widgets (1 large widget on homescreen), BattStat, and SwiftKey.
Any way to adjust the speed at which the screen switches orientation?
Thanks
LP+ does have its moments where it slows down. Original launcher is nicee enough no need to replace it
I've noticed a couple glitches related to this now that I've rooted. It's slow, then it shows the icons and even on screen keyboard in smashed or stretched pixels before it changes orientation. Just for a split second but it's annoying and never did it before.
Yeah, I don't know why the automatic screen rotation is so slow with LauncherPro.
My solution for now was to disable the auto rotate under LauncherPro's Behavior Settings.
The G2 switches instantly to landscape mode for you once you slide out the physical keyboard. No lag this way, but you don't get it to change orientation unless you slide out the keyboard.
I've noticed this too! I thought I was the only one. The funny thing is that when you're in a program that needs the accelerometer there is no lag, but on homescreen there is that slight delay when rotating from portrait to landscape.
I've had this issue with SF, corrected by setting desktop scrolling speed to 0 on ADW launcher setting.
Not sure if this will work on your device.
Since I've had my GN I've noticed some weird lag between the button push and the screen transition, most notably on my Settings app. It seems like the phone waits for the button "glow" animation to finish before initiating the transition into the next screen.
For example, say I'm in settings and want to check out the battery page. I push the battery button and for about a half second, maybe more, it plays out the glow animation (glow light blue and fade back to the original darker blue) and then makes the transition. What makes me curious is that the glow animation doesn't seem do be as smooth as it should and the choppy framerate might be the culprit from allowing it to go to the next screen.
I ran into a similar issue when I was playing around with the Developer Options and set the Transition Animation Scale to 5x and all of a sudden my lock screen and menu animations slowed down considerably.
Has anyone else seen this issue? I know it seems small, but every detail counts!
jumpinghooligans said:
I ran into a similar issue when I was playing around with the Developer Options and set the Transition Animation Scale to 5x and all of a sudden my lock screen and menu animations slowed down considerably.
Click to expand...
Click to collapse
What did you expect to happen? That's what the scaling DOES. That's not an issue, that's expected behavior.
copkay said:
What did you expect to happen? That's what the scaling DOES. That's not an issue, that's expected behavior.
Click to expand...
Click to collapse
I understand this, I was just using it as an example to best convey the behavior I'm getting with the buttons. Like I said before it seems like the animation has slowed down very similar to when I slowed down the scaling animations. That puzzled me until I set it back to 1x but there is no such setting with button animations which is why I'm asking to see if I'm the only one.
On my Xperia Pro I've noticed a weird graphics issue where the wallpaper I apply is reduced in quality.
I have tested out the dithering options in CM7's settings and it does not help. Does anyone know if it might be specific to CM7 since it occurs on both Iyokan and MIUI. I've tried a few screenshot apps and other gallery apps to apply it in order to slim down the possible causes.
A screenshot I took as an example us attached.
Edit: Seems XDA reduced the quality even further.
Direct link can be found at cl(dot)ly/JfFb/screenshot-1348486699116.png
Hello everyone,
I just got my G4 and haven't really had a huge chance to test out the camera, which I can't wait to do. Nonetheless, just doodling around without, I have noticed some annoying issues.
-Trying to manual focus as far away as possible consistently crashes the camera app.
-Auto mode is extremely fluid and smooth, but switching to manual causes the app to lag a bit and the viewfinder to drop some frames
-Settings through the lil gear in all settings appears to be cut off (http://imgur.com/vawoxSR). It sort of seems like I should be able to scroll left and right or up and down through the settings bar, but it does not move.
That's all, nothing huge. Just thought I would see if anyone had had similar experiences or found any fixes.
You have changed the dpi, try to install xposed and then the module app settings (for lollipop version search on the official thread, if I'm right is on post #1847 here on xda) and change the dpi for the camera app back to 640 that will solve both issues.
Thanks a lot, that fixed it and makes a lot of sense in retrospect haha