Hello!
Well I've reading the build.prop and find out that my current ROM has a value of 150. I can't remember where i read that the recommended value was 90 because above that we were not going to be able to note a difference.
I understood that that value was like a refreshing rate of the screen to detect touches.
Is that true? Or what does that option do? If i lower the number will i save battery or anything?
Note: I'm running Nottachtrix GB ( discontinued now )
Related
hi guys,
there is an app (or a method) to change the auto brightness level? something like in CM 6.1...
loscassapalle said:
hi guys,
there is an app (or a method) to change the auto brightness level? something like in CM 6.1...
Click to expand...
Click to collapse
Which rom you are using ?
Froyo, the Blayo one
no one knows?
i found a solution, but i don't know how to do it.
framework-res.apk. It's resources.arsc. If you want to mess around with the brightness levels yourself, you can open it up in a hex editor, and the following values seem to be the brightness levels:
Offset 0x71E20: Minimum brightness
Offset 0x71E2C: Next level of brightness
Offset 0x71E38: Next level of brightness
Offset 0x71E44: Maximum brightness
Click to expand...
Click to collapse
i think it could be a good improvement for our batteries.
someone can tell me if to install the modified apk i have to reflash the rom or there is a faster way?
EDIT: i'm trying to modify it, i found 71E20, but not the others.
Hey, I know this is from a long time ago but did you have success making your changes? If not I made the required changes for blayos 0.84 framework-Res.apk for auto dimming. I can post it if you want.
sent from my legend, currently using extream legend fuse™
Not sure if this can help, but an app on market could help you. It is named "Lux", I heard about it. I tried on zeubea's CM9 Beta0, and it didn't worked, because if not on app's main screen, it detects no light. Maybe on other ROMS it does.
Tested on Devils CM7.1
It almost works on CM7.1, but doesn't respond dynamically (i.e It doesn't adjust as soon as the ambient light level changes, it changes as it feels, kinda randomly). Therefore... not really working - sorry.
cyanogenmod -> display ->automatic backlights -> use custom(check) after that edit other levels and on the third colum make this changes
20 35 50 65 80 110 130 160 180 200 then go to the bottom on the screen and press 'set number of levels' after that go to the top and press 'Save and apply ' and you are done you dont need any app
Modifying the LCD density of your screen will provide HUGE REACTIVITY GAIN to the tablet
We can also tweak Dalvik heapsize for large application
Both are editable using software but they're also properties on the build.prop :
- dalvik.vm.heapsize
- ro.sf.lcd_density
Does editing this properties is enough for the Folio follow or do we have to make much complex operations ?
I there, is this fix already implemented or has to be done manually?!?
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Click to expand...
Click to collapse
I dont understand what u mean.
ps: have u read my pm?
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Click to expand...
Click to collapse
density of 120 works quite fine here now.. with old market app, there was a problem with 120 but that seems resolved now with new market app..
and yes, somehow screen and browsing seems to work better? or is it just the bigger picture giving a nicer resolution of browsing?
All resolution are good. If you have a lot of items on the screen lower density is best.
But by using something like 180 you get a lot of visibility. Since i've developped a lot of complex widgets, it's my favorite one.
Using a density >120 will get you less data to manage on the screen and you can feel the gain ! i'm using multipicture and a lot of complexes widgets and there's not fillrate lag at all.
I was quite surprised with this benefits.
My purpose is that those options can really feet somes users needs. VM heap tricks like the one you found on cyanogen helps on huge application like PDF readers.
But even after editing those properties on the build.prop they are not taken into account. Maybe because of the previous installation i've done. So i'm looking to better understand how to override android properties.
I'm not sure how android handles non-default values for this property.
You should try with one of these:
120 (low-density)
160 (medium-density, Folio default)
240 (high density)
Depending on how this is handled, setting a density different than that may result in broken applications (depending on how the layouts are coded)
Using the LCD DEnsity application i confirm that all resolution are compatible with the folio
Maybe some application will have a bad behavior ! so we've to be able to change the density
metuskale said:
I there, is this fix already implemented or has to be done manually?!?
Click to expand...
Click to collapse
This is no fix, as there are no real issues with these things. Its only a matter of tweaking the folio to your best personal use. They have to be implemented manually.
Shouldn't the dalvik heapsize fix the sound problem with some avi files?
I'm using the foliomod 1.3d, foliowidget works, but some avi files arn't giving me sound
Hello, could someone tell me how the default value for the heapzize is, please? There is only 16, 24 and 32 to choose, but I read something about 64!? How can I choose this value or get back to default?
Thx
Tom
Edit: solved!
Hey guys! Today I have a quick question regarding scripts.
Happens that I just flashed ICS Stock V2 and noticed that it includes both: TurboBoost and LagFree scripts. Well, I decided to dig into them and I realized that both have many common lines (yes, I know you already know) but they're set to different values. It will be usefull for me to know if this scripts are "really compatible".
I also see that Max Events Per Seconds are set to 60, 55, 60 (those are just some of the lines I saw) instead of 150. I would like to know which value is better wether 60 or 150.
Thanks for your brilliant answers
jrxtepan said:
I also see that Max Events Per Seconds are set to 60, 55, 60 (those are just some of the lines I saw) instead of 150. I would like to know which value is better wether 60 or 150
Click to expand...
Click to collapse
I guess, after reading around, that lower is preferred because in stock roms Android wanted to support lots of apps running together and switching between them but often times more excessively than was required which led to decline in task and battery performance. But if you particularly want 'lots' of apps running at once then more is more...
Hello Tablet Z community,
This is my first post in this devices forums since getting mine last week. It's a great device, love it, etc.
I've never owned an Android device with a screen resolution this high so I've yet to encounter this problem - some of my games (specifically the emulator PPSSPP) have relatively low framerates (compared to my less powerful Samsung P6810 @ 800x1280). I know with computers in particular it's trivially easy to change resolutions in games/the OS, especially to increase FPS but I've never seen a method to do this on Android and Google searches turn up people mentioning device resolution without changing them.
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change but I would be willing to endure temporarily to increase FPS.
Any advice and suggestions would be greatly appreciated
I would be interested to know about this, iv just loaded ppsspp however havent been able to play any of the playable games listed, I did see a few videos of the xperia z playing well, however that has the same resolution and specs.
juzza87 said:
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change
Any advice and suggestions would be greatly appreciated
Click to expand...
Click to collapse
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Cat McGowan said:
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Click to expand...
Click to collapse
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
daveid said:
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
Click to expand...
Click to collapse
Heh. Thanks for the schooling, but it was unnecessary, I didn't just fall off a turnip truck.
Thanks for the replies guys, at least now I know for sure..
For those who don't know you can change DPI in the dev menu under "Minimum Width" (not taking any responsibility if you mess something up lol there is a reason it is hidden in the dev menu). The default is 411.
So far I have tried 10 different settings but due to the aspect ratio of the screen I cannot find the perfect DPI for games but also for everyday use. Not a fan of changing DPI just to play a game when I have a few minutes to kill. Any one have better luck?
Mine is currently at 441 (which means it must have adjusted itself from the 440 I set it to), and I think it's pretty good for daily use.
Can't really speak for games though.
Yep I'm using 480 at the moment and games seem to fit great but some apps don't like it
I've had mine set to 530 (it defaults to 533 after exiting settings for some reason) for a while. I found that setting it to anything above 550 results in a misaligned finger register where taking one place registers about 4mm above it. As much as I'd love to set it to 570, doing so results in this misalignment.
I haven't noticed any issues with 530. Only thing that messes up is Samsung's keyboard, but I use the AOSP Android L keyboard with the symbols.
Could you please post images of these gaming issues you are referring to?