Database Info

Ok this is geared to the Devs, about the 2.1 lockscreen

Ok after checking out my brothers droid with factory 2.1 he can set a lockscreen wallpaper from the android photo album. Now my question would be we can remove the htc lockscreen and recover the factory 2.1 lockscreen can we get the factory photo album ( not the htc one) in our phones, guessing a possible apk. if so we may be able to set the wallpapers for the lock screen in this manner. I am a newb, just got the cdma hero 3 weeks ago and have spent the last 3 weeks reading these forums. (I think my brain is going to explode at some point.... LOL). I am hoping that this may be an easy fix for what so many are asking for.

The problem is, our version of the vanilla lockscreen has no provisions in the lockscreen itself, that I can see, for using / referencing a wallpaper set at the system level (which we can do / is used by the HTC Locksceen).
Thus, the current process we have in place is to hack the XML that controls the formatting / display of the vanilla lockscreen. We hack the XML by replacing the value in the XML that specifies a background color, by having it point to a fixed background image, to use as the wallpaper, instead.

JsChiSurf said:
The problem is, our version of the vanilla lockscreen has no provisions in the lockscreen itself, that I can see, for using / referencing a wallpaper set at the system level (which we can do / is used by the HTC Locksceen).
Thus, the current process we have in place is to hack the XML that controls the formatting / display of the vanilla lockscreen. We hack the XML by replacing the value in the XML that specifies a background color, by having it point to a fixed background image, to use as the wallpaper, instead.
Click to expand...
Click to collapse
Easy for you to say.......ROFL

chfields said:
Easy for you to say.......ROFL
Click to expand...
Click to collapse
It is easy. Its not rocket science. Anybody can figure it out if you at least try...

[Q] Raise the dpi

halo
i don't see so well and the Resolution in the one s is to high to me
i raise the DPI Through rom toolbox to 260
but i get some error of the system ui "Unfortunately system UI has stopped"
for example when i enter to "recent up" i got this erorr and i can't enter there....
there is a way to fix it ??
thanks

If I'm not totally wrong raising the resolution will result in smaller letters. You should lower it instead. So please try it.
And you can change letter size within settings -> display & gestures -> font size. By default it is medium, so you can change to large or extra large.
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!

rootrider said:
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
Click to expand...
Click to collapse
I just checked that out.
What's with the notification about it "collecting" info? Collecting it where? And what? I didn't go any futher.....

Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.

Haven't tried it on this phone, but at least on every sense Rom I've used for the hero changing LCD density has always messed up everything. One of the reasons I allways used aosp
Sent from my HTC One S using XDA

usrbrv8 said:
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Click to expand...
Click to collapse
as i said i did it with romtoolbox. it is the same , i raise the dpi to 260....
it makes some problems with system ui and i got some errors
i now replace the rom to miui and the dpi change doesn't Affects the system ui
dpi change can be on a rom without htc sense ui and i think even regular ice !
but..... now there is some problem with the market because Resolution Compatibility i think... there is some app i can't download .....
for now i need to come back to 240 dpi for download some apps and its Annoying
maybe if could change the Resolution to Exactly 800\480 i wouldn't get the market-app-Compatibility issue but i dont know how... maybe someone know how to do it?
my vision isn't so bad and i know the regular options aka font enlarger Etc ...
dpi change is the best choice for me .

[Q]Am I missing something? bootanimation jpegs not work after editing?

EDIT!!! F*&% photoshop defaults to background again when I save! This is ****ting me to tears.
EDIT: Just had a read of this articleabout photoshop background layer being saved by default after reading this guy's thread here
Short answer is that Layer 1 is an arbitrary assigned value to any layer above the background. Layer 0 is what your image needs to be so simply renaming the default value of 1 to 0 works AFAIK. I will be testing this in a couple of minutes.
Will leave the rest as a reference for everyone else. They may learn from my stupidity. I did use the search button though it just took searching and searching till I found that guys thread above that had something specific that applied to my situation.
Hi,
I have am a confident at Android, I have build ROMs and I have a great deal of knowledge and for some reason the most simplest thing stumps me and that is getting bootanimations to work. I understand how they work and I know its not the frame rate or anything like that it has to be something to do with my export settings? Can someone here point me in the right direction?
I will give you a scenario here and why I have mentioned the above. I can get an existing boot animation that is 100% functioning and working and then I might edit the images, say for instance I am changing the colours. I don't change their size or physical dimensions in any way shape or form (they will even play in the preview emulator perfectly), I flash them to the device and nothing? Blank screen on boot up. It completed the boot and opens the OS, but for teh duration of the boot sequence when there is usually a boot animation working it shows completely blank?
Surely it has to do with my export settings? I'm competent with use of GIMP and Photoshop, I have GIMP 2.8 the latest and PS CS6.
Can someone with some knowhow here PLEASE help me with supply "secret settings" for their export of images?
I read somewhere that the images need to be reindexed? I don't know how to do this? I have edited other PNGs that are non-bootanimation PNGS and I knew I had to uncheck indexing and check the box for R,G,B and that allowed me to edit the image.....but if I check the box for an boot animation image (set to R, G, B) back to indexed; when I close the image and re-open it again its back as a R, G, B image? WTF?
I have heard somewhere they need to be 24bit? I have NFI what that means or where to change it? My version of photoshop only has listings for 8bit, 16bit and 32bit?
Yes my kernel allows for bootanimations. Yes a boot animation was working on my phone!
I can change nothing except the colour of the images; package them in the same location in the zip; Test on the previewer for Windows; load it to the phone -> nothing!
EDIT: YES Permissions are set correctly. I can even change back to the boot animation that I changed the colour and it works perfectly

I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.

Jarmezrocks said:
I read now 8 bits per channel. And there is 3 being that they are RGB, which makes them 24bit anyway? WTF is wrong. I fail hard if I can't get a boot animation working LOL.
Click to expand...
Click to collapse
you should upload here that bootanimation.zip file

[Q] Tilt sensor is off for some apps, possible fix?

Before my Asus tf700 Infinity, I owned a Samsung Galaxy Tab. I purchased some programs and games for it, and all was well until it was stolen. The problem? Now I've downloaded and used those same apps on my tf700 Infinity, and the orientation is off by ninety degrees on quite a few. It has to do with Android's API and Honeycomb, and how the default base orientation is set in the framework policy. Before tablets, the default orientation for the Android API was portrait, but tablets made landscape defaults a possible better default. Apps not written to accommodate this would have the sensors read 90 degrees skewed for landscape default devices (like my tf700), because the sensor data is being read from landscape (regardless of orientation), but interpreted as portrait by the app. Even though my Galaxy Tab was a tablet, it's default orientation was portrait, so there was no 90 degre skew. I have read enough to know that it's possible to change the Android system default value, but it has to be changed in the framework . . . No easy task, especially if the rom is ODEXed.
So . . . anyone have any advice or fix so my paid apps aren't wasted money? I don't think emailing every single developer is the key, when I could modify a single system value to fix the problem for all apps. Thanks in advance, any help is appreciated.

Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2

GrayHat137 said:
So . . . anyone have any advice or fix so my paid apps aren't wasted money?
Click to expand...
Click to collapse
You could try Ultimate Rotation Control. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).

ShadowLea said:
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
The problem is that the data the app is getting is from the sensors is rotated 90 degrees. For example, if the app assumes the tilt data it is getting is from the left and right: tilt left, go left. On my tablet, it's default boot state is landscape, so if the app is asking for the sensor info the wrong way (a deprecated way - from before the Honeycomb API), it's getting the tilt axis from the top and bottom, so: tilt up, go left. I can calibrate, but I still have to tilt up to go left.

Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?

HeartWare42 said:
You could try Ultimate Rotation Control[/URL]. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
Click to expand...
Click to collapse
I had hoped it would override the default framework, but apps were still polling the sensors wrong no matter which orientation they were displayed in. The sensor data was rotating the same amount as the app, but the original sensor data was still originally off by 90%.
Thanks for the tip; Ultimate Rotation Control is a good app that solved another issue I had, just not this one.

sbdags said:
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
Click to expand...
Click to collapse
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:

GrayHat137 said:
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
Click to expand...
Click to collapse
Which part of the framework do you need to change?

sbdags said:
Which part of the framework do you need to change?
Click to expand...
Click to collapse
Navigate to the androidpolicy\com\android\internal\policy\impl folder and open PhoneWindowManager.smali in your favorite text editor (Notepad++ is my favorite)
Search for the method "rotationfororientation"
(Picture of code here)
Make note of the variables (v#) for portrait and landscape (in my case portrait is v5)
Scroll to the end of the method and you should find something like:
"move v2, v5" (make sure it's the last move command before the end of the method)
Change the second variable (in this case v5) to whatever orientation you wish to be default. In my case I have set portrait as the default orientation.
Click to expand...
Click to collapse
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.

Eureka!
GrayHat137 said:
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Click to expand...
Click to collapse
Dear friends,
As I was also facing the same problem in my Ubislate 7C+(EDGE) tab by DATAWIND. While reading your post an idea struck to my mind. With the help of Root Browser app I navigated to /system/build.prop, opened it in text editor and in "ADDITIONAL_BUILD_PROPERTIES" changed the value of "ro.sf.hwrotation=270" 270 to 180 saved it and rebooted the tablet. Yes! the problem was solved but it created a new problem that the orientation of animation while boot and camera orientation has changed now but in order to rectify it I pulled bootanimation.zip to my computer and after unzipping it changed the orientation of animation files from portrait to landscape. Changed the orientation in 'desc.txt' from 480 800 to 800 400 and zipped both without any compression. Pushed it back to /system/media and changed the permission, user,group to original one with the help of root browser. Then for camera orientation with the help of root browser I navigated to /system/etc/camera.cfg opened it in RB text editor and changed camera orientation from 90 to 0, saved it and rebooted my tablet and now all the games using gsensor tilt are working fine.
Thanks,:good:

rotation gyro off
I had the same problemen, i resolved it by going to setting, location and then status (only GPS) then i started GPS tools , just waited a min or so . now everthing is oké again.
I hope thuis helps you

Changing resolution properly (rounded corner, UI scaling etc)

It was supposed to be just an experiment, but now I'm spend.
Basically, I can perfectly well change the resolution on my a22 4g, which was what I wanted, but certain elements, like the rounded corners and notification bar, or what it's called, are not handled. The radius is not scaled, which looks horrible. It can be changed manually, from what I've tried, but the change is not persistent. All it takes is a single rotation of the phone, and we're back to scratch, and besides, the other issues aren't solved, even if it worked.
I've tried numerous helper apps, just for kick, but they don't seem to be able to do a better job than myself, so what's the game here? Is it simply not possible, or am I missing something?

Zacariaz said:
It was supposed to be just an experiment, but now I'm spend.
Basically, I can perfectly well change the resolution on my a22 4g, which was what I wanted, but certain elements, like the rounded corners and notification bar, or what it's called, are not handled. The radius is not scaled, which looks horrible. It can be changed manually, from what I've tried, but the change is not persistent. All it takes is a single rotation of the phone, and we're back to scratch, and besides, the other issues aren't solved, even if it worked.
I've tried numerous helper apps, just for kick, but they don't seem to be able to do a better job than myself, so what's the game here? Is it simply not possible, or am I missing something?
Click to expand...
Click to collapse
if you want to lower resolution , use gl tool

Guan Yu said:
if you want to lower resolution , use gl tool
Click to expand...
Click to collapse
Although interesting, the name rather imply that it is not a general solution, and besides, it basically requires root, which really shouldn't be necessary. I will look into it, however, so thanks for the reply.

Zacariaz said:
It was supposed to be just an experiment, but now I'm spend.
Basically, I can perfectly well change the resolution on my a22 4g, which was what I wanted, but certain elements, like the rounded corners and notification bar, or what it's called, are not handled. The radius is not scaled, which looks horrible. It can be changed manually, from what I've tried, but the change is not persistent. All it takes is a single rotation of the phone, and we're back to scratch, and besides, the other issues aren't solved, even if it worked.
I've tried numerous helper apps, just for kick, but they don't seem to be able to do a better job than myself, so what's the game here? Is it simply not possible, or am I missing something?
Click to expand...
Click to collapse
changing resolution was never great because android not officialy support it , thus creating anoying visual bug .And what is your ploblem when using native resolution outside gaming?

Guan Yu said:
changing resolution was never great because android not officialy support it , thus creating anoying visual bug .And what is your ploblem when using native resolution outside gaming?
Click to expand...
Click to collapse
No problem. As I said, it was an experiment. How low can you/I go, without it being too low, and what will the impact om battery life be?

IMO to change appearance of some System UI elements you've to use System UI Tuner app