Database Users

Tip for browsing with Opera Mobile 9.7 on the HD

Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Height = 4096
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.

Slothie said:
Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
Hi,
thanks for the Tip ... but,
In 9.7b1 I can't find:
- Maximum Zoom
- Maximum Overview Zoom
- Minimum Zoom
- Zoom Slider Maximum
in 9.5 they exist but not in 9.7

not sure if it's something i've done, but after making those changes i can't launch Opera any more!!
I get the htc loading page for about about 20 seconds and then it just closes - anyone else had this problem or know how to solve?

Slothie said:
Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Height = 4096
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
It also makes the text tiny.
Does anyone have the original settings please, stupidly I did not note them down.

MaskedMarauder said:
It also makes the text tiny.
Does anyone have the original settings please, stupidly I did not note them down.
Click to expand...
Click to collapse
In Opera 9.5 i have the following settings which allow me to open links without zooming. Min overview zoom is the only changed variable.
Browser Buffer Height = 1400
Browser Buffer Width = 960
Maximum Zoom = 200
Minimum Overview Zoom = 85
Minimum Zoom = 160
Virtual Screen Width = 960
Zoom Slider Maxinmum = 500

So will altering these settings change the width of text elements and reduce the amount of zoom? I'm running this on an HX4700 with a 4.0" screen (I know, I'm getting my touch HD in less than 30 hours). When the zoom action happens, it automatically zooms to the width of the column element (ingenious) so I can scroll throught he column without side scrolling. However the width of the elements are too narrow and as such causes the zoom to be too high. I'd like to use the 4" display and VGA rez to read smaller but more amount of text.

I've no idea mate sorry. I just copies and writes up what i sees

MaskedMarauder said:
Does anyone have the original settings please, stupidly I did not note them down.
Click to expand...
Click to collapse
Just noted these down from my new HD, here they are:
Browser Buffer Height = 1400
Browser Buffer Width = 960
Maximum Zoom = 200
Minimum Overview Zoom = 60
Minimum Zoom = 160
Virtual Screen Width = 960
Zoom Slider Maxinmum = 500

Thank you very much saad.salman & Freypal

i've been looking for that setting (minimum overview zoom) for a while - cheers!!

Riceburner said:
i've been looking for that setting (minimum overview zoom) for a while - cheers!!
Click to expand...
Click to collapse
it doesn't work in Diamond 2 Opera ><

nick666 said:
not sure if it's something i've done, but after making those changes i can't launch Opera any more!!
I get the htc loading page for about about 20 seconds and then it just closes - anyone else had this problem or know how to solve?
Click to expand...
Click to collapse
Get a hold of opera.ini >>windows>opera9
edit the file, the first few lines are the ones you will need to change.
Just copied this from mine..
[Adaptive Zoom]
Minimum Zoom=160
Minimum Overview Zoom=70
Browser Buffer Height=1400
Browser Buffer Width=960
Maximum Zoom=200
Virtual Screen Width=960
Zoom Slider Maximum=500
after changing back, having had the same problem you did...
Good Luck

Slothie said:
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
Just note that with this tweak you will lose the ability to trigger mouseover action for links.

Neville.Holland said:
Get a hold of opera.ini >>windows>opera9
edit the file, the first few lines are the ones you will need to change.
Just copied this from mine..
[Adaptive Zoom]
Minimum Zoom=160
Minimum Overview Zoom=70
Browser Buffer Height=1400
Browser Buffer Width=960
Maximum Zoom=200
Virtual Screen Width=960
Zoom Slider Maximum=500
after changing back, having had the same problem you did...
Good Luck
Click to expand...
Click to collapse
I had the same problem but I can't find the file I can't search my phone's files either...

Ekkoe said:
I had the same problem but I can't find the file I can't search my phone's files either...
Click to expand...
Click to collapse
I could only imagine it being in the one of the following
\Windows
\Windows\Opera
Possible \Application Data but unlikely I think.
I'm running the standard 6.1 HTC original ROM.

Forget all that. Everything is running. It didn't go as smooth and understandable as I might have hoped, but it works now. Thanks!

[GUIDE] Automatic backlight

Our Nexus S has been blessed with the release of ICS 4.0 in which the light sensor values have been significantly improved over GB. In GB we had about 5 or 6 light sensor values which would decide how bright to set the screen. This created an opportunity for the CyanogenMod team to code the Automatic backlight settings with filtered values in between to try to help the community with correct brightness levels. Still it was a far cry from what is now possible because of the fine increments in light sensor delivered in with the 4.0 binaries.
These settings are a good starting point and can serve well as default values for most. However, depending on your eyes and Voodoo settings you might have to adjust them to your own comfort. So lets get started.
Open the CyanogenMod Settings (if you don't have them in your app menu, ask your ROM developer to integrate them)
Go to Display-> Automatic backlight
Enable - obviously turn this on
Window length - set as low as possible. 2 is the lowest currently. Since our sensor values degradation is very fine now, this is less of use
Reset threshold - set to disabled. Again, this depends on the window length
Sample interval - set to 2s. This will ask the processor to check the brightness level every 2 seconds. You can set it based on what you feel is correct but obviously low values can improve accuracy but uses more cpu and drains your battery quicker
Use custom - check this. we'll set our own values
Screen dim level - this is the default setting for your screen lowest dim level. I use 10 but you might have to use more or less depending on the quality built of your screen and voodoo settings.
Edit other levels... - skip this to the last step
Allow light to decrease - check this.
Decrease hysteresis - set to 0%
Now tap on "Edit other levels..."
Scroll down and tap "set number of levels" set it to 25. Now set the "Lower" value and a "Screen" value for it. The first "Lower" value is set to 0 and can't be modified. "Upper" value is set automatically based on the two values of "Lower" and "Screen". "Buttons" value never worked on the Nexus but with proper kernel support they can change based on light sensor conditions. For now, set all button values to 255.
All values can be set from 0 to 255. Here are my default values:
Code:
Lower | Screen
0 | 10
5 | 20
10 | 30
15 | 40
20 | 50
30 | 60
40 | 70
50 | 80
60 | 90
80 | 100
100 | 110
120 | 120
140 | 130
180 | 140
220 | 150
260 | 160
300 | 170
380 | 180
460 | 190
540 | 200
620 | 210
1240 | 220
2480 | 230
4960 | 240
10000 | 255
Go up and hit "save and apply" after setting it up.
If you're wondering why these values, I doubled the last increment every 4th value. Since the lowest values are the most important for us because we usually are indoors with different lightning conditions, the higher values can be quickly set to max 255 screen brightness when anything over 10,000 hits the sensor such as sitting too close to a powerful light bulb or if you happen to find yourself on Mercury during the day (might want to bring a suit also ).
Modifications and adjustments:
If the screen seems too bright or too dim at any time, go back to the "light sensor levels" screen and look up the current screen value. It's the 2nd line after "Sensor (filtered/raw)". Then scroll down and find a "Screen" setting which is equal to that value and modify it. Try not to move around and make sure the "Sensor (filtered/raw)" values stay the same. What you are doing is simply adjusting your phone's brightness to fit current light sensor level so if it changes while you set it, you wont know if it worked. Also, you can adjust all "Screen" values by 5 or more (down or up) if it feels like it's all off your comfort level.
If you really want to get down and dirty and understand all the fuzz in details byrong over at HTC Droid Incredible forums posted a great explanation and all the science behind it. Just remember that their phone is limited to just a few light sensor values where ours has virtually thousands and that's why I chose to almost eliminate the filtered value to control flicker. But it's up to you if you want to play with that. Also, he has a great post on CPU usage titled "Effects of CPU Frequency and Screen Brightness on Power Consumption". Make sure to check it out.
And one last note regarding the voodoo settings... your screen is different than other phones. I have 4 Nexus S phones and none of them can be set to the same voodoo settings to create the same colors. Depending on screen fabrication quality and possibly date of manufacture, it will vary slightly and sometimes greatly. So if you post your voodoo settings and someone says they suck now you know why.

Awesome guide, thanks!

Or if you're not on CM, grab this app : https://market.android.com/details?id=com.vito.lux , you can set levels based on lux values with ease. Also on new year's sale now at half the price.

madd0g said:
Or if you're not on CM, grab this app : https://market.android.com/details?id=com.vito.lux , you can set levels based on lux values with ease. Also on new year's sale now at half the price.
Click to expand...
Click to collapse
Tried it, works great.

I have this enabled on CM setting and followed your directions...One question? Am I supposed to have automatic brightness levels checked in system settings, display, brightness? Thanks! I believe yes but just want to be sure

Necro but how are these settings in regards to battery life?

[Q] Delay for screen wake when receiving a call

Do you guys also have this issue with the screen taking 2-3sec to wake up after the phone stats ringing on incoming calls? Or is it only me? Do you guys have a fix? Or is it because I have exdialer installed?

I find there is a delay with it sadly
Sent from my LG-D802 using xda app-developers app

DialerEx was probably the cause. Uninstalled relieved partially the issue

I had this problem but i think having Go power manager lower my cpu caused it. I turned that off and it seems like i don't have the delay anymore

It depends greatly on your governor and CPU hotplug - I am using Ondemandplus with a 1 Ghz screen off frequency and Intelli hotplug. I get about 2-3 seconds of delay from when my phone vibrates to when the screen comes on (I use a QuickWindow case), but I was surprised today to find the screen instantly on when receiving a call.

Anyone find a fix for this yet?

*WARNING: Do not manually set your screen off frequency lower than 1Ghz. This will cause screen wake on call issues*
I get near instant screen wake on call with this and anyone is welcome to test it out.
Added the xml as an attachment that you can just extract and import directly into tasker!
Requirements are:
-Must be rooted
-Tasker app
-Secure settings app
Profile: Force Screen On Call (46)
State: Display State [ Isff ]
State: Call [ Type:Incoming Number:* ]
Enter: Anon (47)
A1: Secure Settings [ Configuration:Screen & Keyboard Lights On
1 Second Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]

Nice work
This does the trick,but it has a slight bug. My lockscreen wallpaper appears before the contact who is calling. Is this normal ?
demoncamber said:
*WARNING: Do not manually set your screen off frequency lower than 1Ghz. This will cause screen wake on call issues*
I get near instant screen wake on call with this and anyone is welcome to test it out.
Added the xml as an attachment that you can just extract and import directly into tasker!
Requirements are:
-Must be rooted
-Tasker app
-Secure settings app
Profile: Force Screen On Call (46)
State: Display State [ Isff ]
State: Call [ Type:Incoming Number:* ]
Enter: Anon (47)
A1: Secure Settings [ Configuration:Screen & Keyboard Lights On
1 Second Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
Click to expand...
Click to collapse

I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801

demoncamber said:
I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801
Click to expand...
Click to collapse
That would be really cool thanks

demoncamber said:
I couldn't get that to stop, I think the screen is turning on before the call screen even gets initiated. I'll let you know if I find a way around it.
Sent from my LG-D801
Click to expand...
Click to collapse
Did you manage to solve something with the wallpaper appearing before caller? Really annoying, and it's almost perfect [emoji12]

metalboy94 said:
It depends greatly on your governor and CPU hotplug - I am using Ondemandplus with a 1 Ghz screen off frequency and Intelli hotplug. I get about 2-3 seconds of delay from when my phone vibrates to when the screen comes on (I use a QuickWindow case), but I was surprised today to find the screen instantly on when receiving a call.
Click to expand...
Click to collapse
Awesome

I actually have a bit of a better more optimized profile now. Attachment XML incoming. What this actually does is allows you to set as low as you want screen off cpu frequency in the first part, and then when the phone rings it will boost the cpu to max set frequency, or anything you want to set it to manually above 1GHz will work.
First things first, download the attachment, then first import the 3 files ending in tsk.xml into tasker, they should show up in your tasks section, then import the one ending in prf.xml
Then you can set whatever frequencies you want for your screen off max freq in "display off cpu" task in tasker, this can be basically anything. Then you can open the "Wake_On_Ring" task and set that max freq to anything ABOVE 1000mhz. I have it default set at 1.9GHz and it works almost instantly for me on call. But it's up to you. After that, everything is good to go.
Here's what it looks like:
Profile: Display Off Wake On Ring (27)
State: Display State [ Is off ]
Enter: Display Off Ring Manager (52)
A1: Perform Task [ Name display Off Cpu Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq OFF ]
A2: Perform Task [ Name:Wake On Ring Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq ON ]

Can't wait to give it a try, I will give you feedback regarding this soon

demoncamber said:
I actually have a bit of a better more optimized profile now. Attachment XML incoming. What this actually does is allows you to set as low as you want screen off cpu frequency in the first part, and then when the phone rings it will boost the cpu to max set frequency, or anything you want to set it to manually above 1GHz will work.
First things first, download the attachment, then first import the 3 files ending in tsk.xml into tasker, they should show up in your tasks section, then import the one ending in prf.xml
Then you can set whatever frequencies you want for your screen off max freq in "display off cpu" task in tasker, this can be basically anything. Then you can open the "Wake_On_Ring" task and set that max freq to anything ABOVE 1000mhz. I have it default set at 1.9GHz and it works almost instantly for me on call. But it's up to you. After that, everything is good to go.
Here's what it looks like:
Profile: Display Off Wake On Ring (27)
State: Display State [ Is off ]
Enter: Display Off Ring Manager (52)
A1: Perform Task [ Name display Off Cpu Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq OFF ]
A2: Perform Task [ Name:Wake On Ring Priority:%priority Parameter 1 (%par1): Parameter 2 (%par2): Return Value Variable: Stop off ] If [ %PHONEWASRINGING eq ON ]
Click to expand...
Click to collapse
I tried it and it does work better. The wallpaper doesn't show any more before call. Great job, thanks

Unfortunately, there is no difference for me. I still get a 2-3 seconds delay each incoming call

nfl mobile app not working on cloudy rom g3/verizion lg g2
My nfl mobile app is not working on cloudy rom g3. I have the lg g2 verizon. Please help fix it

Try a different rom... I've had great success with the G3 ported roms... No wake up lag on either one of these

LockScreen ameliorations and corrections

Hello,
I'm just sharing my way to automaticaly "swipe to unlock", "show notifications", etc... when display turns on by only using Tasker (no Secure Settings, etc... needed)
Here is the tasker code to simply auto-swipe the screen if the phone is not in your pocket when display turns on :
Code:
Profile: Auto Unlock (25)
Event: Display On
Enter: Unlock screen (7)
A1: If [ %Proximity ~ False ]
A2: Run Shell [ Command:input swipe 560 1840 520 1000 250 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A3: End If
Profile: Proximity (2)
State: Proximity Sensor
Enter: Set Proximity (5)
A1: Variable Set [ Name:%Proximity To:True Do Maths:eek:ff Append:eek:ff ]
Exit: Unset Proximity (27)
A1: Variable Set [ Name:%Proximity To:False Do Maths:eek:ff Append:eek:ff ]
Here is the tasker code to auto-swipe the screen if the phone is not in your pocket when display turns on and display not unwanted notifications when unlocked :
Code:
Profile: Auto Unlock (25)
Event: Display On
Enter: Unlock screen (7)
A1: If [ %TIMES > %LastNotificationTime + 1 & %Proximity ~ False ]
A2: Run Shell [ Command:input swipe 560 1840 520 1000 250 Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]
A3: Status Bar [ Set:Expanded ] If [ %Notification eq True ]
A4: Variable Set [ Name:%Notification To:False Do Maths:eek:ff Append:eek:ff ]
A5: End If
Profile: New Notification (26)
Event: Notification [ Owner Application:* Title:* ]
Enter: Show/hide Notifications (8)
A1: Variable Set [ Name:%LastNotificationTime To:%TIMES Do Maths:eek:ff Append:eek:ff ]
A2: Variable Set [ Name:%Notification To:False Do Maths:eek:ff Append:eek:ff ]
A3: Variable Set [ Name:%Notification To:True Do Maths:eek:ff Append:eek:ff ] [COLOR="Green"]If [ %NTITLE !~R .*alarm.* ][/COLOR]
Profile: Proximity (2)
State: Proximity Sensor
Enter: Set Proximity (5)
A1: Variable Set [ Name:%Proximity To:True Do Maths:eek:ff Append:eek:ff ]
Exit: Unset Proximity (27)
A1: Variable Set [ Name:%Proximity To:False Do Maths:eek:ff Append:eek:ff ]
IMPORTANT NOTES :
- Please let me know if it works or if it is buggy on your device : nobody's perfect...
- This will swipe automaticaly each time anything is setting the display to "on" (double tap the screen, power button,etc... but also an app).
- Root is required but unlocked bootloader in not needed
- You can replace the If [ %NTITLE !~R .*alarm.* ] part of the code with something like If [ %NTITLE !~R .*ring.* & %NTITLE !~R . *mail.* ] to add/edit new notification title filters (regex).
- This code will work nearly every time but depends of you phone's velocity (no problem on my axon 7 A2017G)

News
25-10-2016 -> I'm currently testing a third release showing/hiding notifications by swiping your hand above the device ...

Reserved space

Thanks for sharing this!

toastyy said:
Thanks for sharing this!
Click to expand...
Click to collapse
My pleasure...

how to change dpi for cool 1 dual

i am finding reading text on main page and applications a bit difficult. i observed through hardware info application that dpi is 480(xxhigh, xxhdpi) where as on other 5.5" FHD mobiles its normally 401 dpi.
is there some setting procedure to change it to 401 or lower?

asharma7 said:
i am finding reading text on main page and applications a bit difficult. i observed through hardware info application that dpi is 480(xxhigh, xxhdpi) where as on other 5.5" FHD mobiles its normally 401 dpi.
is there some setting procedure to change it to 401 or lower?
Click to expand...
Click to collapse
- Download any Terminal Emulator from the market and install it - Open it, type "su" (no quotes) and confirm the popup of root permissions
- Type the string
/ system / bin / wm density 420 \ n
And press enter
To return to the zoom scale just type
/ System / bin / wm density 480 \ n