Database Develop

closing/opening hinge SFX...?????

Aight. I did a thorough search and couldn't find anything... most likely because it's not a current element of the system but I have a question for you savvy individuals on here who are able to dive REAL deep (deeper than me @ any rate).
I have the Transform open/closed FX from generation one Transformers that I used w/ my MotoRizr and Wing as a sliding sound previously.
I know there's no active feature currently implemented in Android that would allow us to set any kind of system sound for the opening and closing of the hinge... but is it somehow possible to write this into a build/program the phone to somehow do this? Seems that the sky's nearly the limit w/ android so I figured there might be someone on here savvy enough to pull it off.
I'd LOVE to implement these sound effects for my G1... and if we were able to create this capability that'd add yet ANOTHER awesome dynamic to creating skins/themes as devs could include related opening/closing sounds (kinda the way the sidekick themes, as nausiatingly proprietary as they are, change the open/close sound when you switch them up). Just an idea I thought I might throw someone's way. Thanks =)

I would say it is definately doable. Just as in programs you can override any of the android processes and controll what happens you could add an event for this. It would have to be built into the system for it to work properly which is well beyond my abilities.
Heres an Idea though, what about the home screen replacements, I assume that they must override these processes to work properly and handle their own events. Maybe you could e-mail the devs and suggest it as a feature.

Baldyman1966 said:
I would say it is definately doable. Just as in programs you can override any of the android processes and controll what happens you could add an event for this. It would have to be built into the system for it to work properly which is well beyond my abilities.
Heres an Idea though, what about the home screen replacements, I assume that they must override these processes to work properly and handle their own events. Maybe you could e-mail the devs and suggest it as a feature.
Click to expand...
Click to collapse
Good idea =) Don't know what to do next... hoping this thread will catch somebody's attention. Cuz I'm an avid user of Openhome and have e mailed betterandroid on several occasions already =)
I'd be tempted to post this on the themes and wallpapers forum but would thus be breaking the rules by multi-posting. I'll give it a few days, then PM killa_tattz who created the X-Men skin I'm currently rockin to see if he knows/would know anyone =)

What, you don't like the squeaky creak and *kschuck* when you open the screen now? lol

AndroidAutobot said:
Aight. I did a thorough search and couldn't find anything... most likely because it's not a current element of the system but I have a question for you savvy individuals on here who are able to dive REAL deep (deeper than me @ any rate).
I have the Transform open/closed FX from generation one Transformers that I used w/ my MotoRizr and Wing as a sliding sound previously.
I know there's no active feature currently implemented in Android that would allow us to set any kind of system sound for the opening and closing of the hinge... but is it somehow possible to write this into a build/program the phone to somehow do this? Seems that the sky's nearly the limit w/ android so I figured there might be someone on here savvy enough to pull it off.
I'd LOVE to implement these sound effects for my G1... and if we were able to create this capability that'd add yet ANOTHER awesome dynamic to creating skins/themes as devs could include related opening/closing sounds (kinda the way the sidekick themes, as nausiatingly proprietary as they are, change the open/close sound when you switch them up). Just an idea I thought I might throw someone's way. Thanks =)
Click to expand...
Click to collapse
I can say for sure it's doable. I would attempt it but I've had enough problems with my music player to know that it's not for me. But basically some1 would just have to make a broadcast receiver/service combo that plays the sound on the open keyboard event and the closing sound on the close keyboard event. It doesn't even seem like it'd be that difficult for the right person(someone with enough experience with the sound api to get this to work)

polaris0352 said:
What, you don't like the squeaky creak and *kschuck* when you open the screen now? lol
Click to expand...
Click to collapse
Frickin hilarious!
Must note that I seem to remember seeing a post somewhere on how to tighten up the hinges or something to prevent the squeaking. I'll look around for it... If anyone knows where it is PM me and I'll update this post with the link.
I think the open/close sound option would be great!

shaneaus said:
Frickin hilarious!
Must note that I seem to remember seeing a post somewhere on how to tighten up the hinges or something to prevent the squeaking. I'll look around for it... If anyone knows where it is PM me and I'll update this post with the link.
I think the open/close sound option would be great!
Click to expand...
Click to collapse
Actually, it's that there's a little nub of plastic right next to where the hinge is on the top part of the chin. If you cut it off with an etching knife or something it'll stop squeaking.

Guys moving from the sidekick would go APE**** over this... I suggested my dev friend make a app for this, he'd make millions. Ok, not millions.. but at least a quick $5.

This would be an AWESOME feature! If we could get this and typing sounds for the hardware keyboard, my OCD would be 100% completely satisfied!
[highjack]
This is why I want typing sounds for the hardware keyboard-
{
"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"
}
My thumbs are waaay to big for the virtual kb...sounds on the hardware kb would help soooooo much!!!!!! (excuse my dirty fingernails...I'm an active duty army heating/ac tech)
[/highjack]

GODDAM!!! Your thumb is almost half your keyboard

FuMMoD said:
GODDAM!!! Your thumb is almost half your keyboard
Click to expand...
Click to collapse
That's one thing I miss about my old Wing. MUCH bigger keyboard/keys and typing sounds. It helped sooo much.

The trick with the pen knife didn't address my squeeeking! LOL
But, I'll agree... Some dang large hands and a sound effect for the open/closing of the screen would be sweet!

i also really really really desire the sounds for keypresses
like the same sounds that come with the vk in haykuro h!
different sounds for keypress and backspace and space
so entertaining...
some one please do thisss

I have also ben looking for a way to add sound to the opening and closing of my keyboard. Anyone out here willing to try and tackle this idea? If anyone, I know an xda dev can do this....

KidJethro said:
This would be an AWESOME feature! If we could get this and typing sounds for the hardware keyboard, my OCD would be 100% completely satisfied!
[highjack]
This is why I want typing sounds for the hardware keyboard-
My thumbs are waaay to big for the virtual kb...sounds on the hardware kb would help soooooo much!!!!!! (excuse my dirty fingernails...I'm an active duty army heating/ac tech)
[/highjack]
Click to expand...
Click to collapse
I call photochop... that is WAY too big of a thumb.. j/k.. but really, I lined up my thumb on the W like yours and I can still see most of the T key.
I have a glitch that might help you. For some reason, if I have the physical open but I touch the text box, it starts up the auto-complete and I hear the sounds every time I type. I have to close the screen and re-open to get that DAMN sound to go away. (I don't like it on the physical)

KidJethro said:
That's one thing I miss about my old Wing. MUCH bigger keyboard/keys and typing sounds. It helped sooo much.
Click to expand...
Click to collapse
o.0 OMG DUDE WHO ARE YOU
I have a glitch that might help you. For some reason, if I have the physical open but I touch the text box, it starts up the auto-complete and I hear the sounds every time I type. I have to close the screen and re-open to get that DAMN sound to go away. (I don't like it on the physical)
Click to expand...
Click to collapse
That's probably because you're using HTC_IME. cyanogen said he would try to fix that //EDIT: its fixed!

landscape mode
Not sure if this would work but perhaps linking the sound to part of the system that tells the screen to go landscape when the keyboard is opened

Than it would do it whenever you rotate your phone.

maybe
Maybe not when the keyboard id open there is something telling it not to rotate so maybe linking it to that part is the key

It seems it would be easier just to tie the sound to the keyboard opening than to make it play when switching to portrait but only when the keyboard is open lol.
I think it disables autorotate when the keyboard is out btw.

Lower Auto-Brightness Settings for DEODEXED FROYO / GINGERBREAD Sense ROMs

Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"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"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)​
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.

Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........

Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>

UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?

Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........

UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either

Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.

Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!

So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go

slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol

Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!

HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813

What about Kalagas theme...i would be very appriciate

Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk

Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App

Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,

hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them

kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!

slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!

hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...

Tablet UI on Nexus 7 [How to / Video / Build.prop Modification]

So tablet ui is possible by a simple editing of the dpi of you Nexus 7.
Here's how you can do it yourself with an file explorer of your personal preference of file explorer.
For those wanting a explanation of what dpi does for your device read below
SilentMobius said:
You are lowering the _value_ that Android _reports_ as it's DPI, you are not changing the screen at all. In effect you are lying about the physical size of the screen
The default is 213dpi with a resolution of 1280×800 hence it's claiming that the display is 6in x 3.75in (7 inch diagonal)
If you alter the DPI to 160 you are lying to the system (and apps) and claiming that the 1280x800 display is actually 7.5in x 4.7in (8.8 inch diagonal)
When the apps think the screen is bigger they make the icons smaller and enable extra features (like multi-pane UIs)
Click to expand...
Click to collapse
Requirements
1. Rooted Nexus 7
2. Have a nandroid backup and a backup of your original build.prop(just in case)
3. Any file explorer that has root access to your system files
4. A bag of jelly beans for a few snack moments
Note: i'm not responsible if your Nexus 7 explodes into a bunch of jelly beans.
Tip: once you have tablet ui change you font size by going into display settings to your preferred size.
Video Guide i made, late at night from a busy day...so if i talk funny blame the lack of nutrition and sleep
Method 1(Recommended)
1. Get Rom Toolbox Lite or Pro if you want to support awesome app
2. Swipe to performance and press build.prop editor
3. Now scroll down to ro.sf.lcd_density
4. Press on it and change the dpi to 160 dpi
5. After doing that press ok and back out
6. Reboot your Nexus 7 and enjoy some tablet ui goodness.
Method 2
Note: I'll be using ES File Explorer as my file explorer in this method
1. Get a file explorer such as MIUI File Explorer, File Expert, ES File Explorer
Note: For ES File Explorer go to settings allow mount rewritable and root access
2.Then go to system
Note: ES File Explorer just go to the star button on the top left hand side and click on the phone button and you will see the system folder
3.You will find a build.prop file make sure to make a copy of it and save it somewhere just in case for a backup.
4.Then click on the build.prop and open it with a text editor. (ES file manager has its own text editor called ES Text Editor...go figure )
5. Now scroll down to "ro.sf.lcd_density"
6. Now the original lcd density is 213 so the best result for tablet mode is 160 dpi
7. Save the file by press the menu button.
8. Reboot your N7 and then you got Tablet UI.
Method 3
1. Get Buildprop Editor
2. Navigate to system and find the build.prop
3. Then find the line with "ro.sf.lcd_density"
4. Now the original lcd density is 213 so the best result for tablet mode is 160 dppi
5. Now save the file and reboot your device. Enjoy
Update 07/05/2012 In my personal experience with LCD Density Modder, changing dpi works and will cause you issues(lost root, bootloop, softbrick). Will update if the app gets updated for support.
Update 07/18/2012 Working on a way to get tablet ui without touching the build.prop. Its going to take some time with my tight schedule but i'll do my best. For those that experienced no boot, or lost root
To gain root access / obtain clockworkmod / unlock bootloader with toolkit
To return to stock / unbrick you device
Now all thats left is to edit the systemui to get a more clean result. That will come soon.
If there's others ways to do this without causing harm to our tablets shoot me a pm and ill post it in the first post. Hope you guys find this helpful.
Enjoy some screenshot of tablet ui.​
{
"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"
}

Awesome. I know many of us will be wanting this when the 7 ships. Is the text still large enough to be easily read?
sent from my evo 3d

Try 160? That is the default, maybe it will look better.

How it should have been in the first place, probably one of the first things I will do when I get my 7 through the post.

SladeNoctis said:
Just change the density to 170- in the build.prop and you got yourself Tablet UI. May need a bit of a System UI modification do to the previews in certain things dont look right. [/IMG]
Click to expand...
Click to collapse
May I ask how you go about changing the dpi?
Sent from my HTC One S using xda app-developers app

iwantanandroid said:
May I ask how you go about changing the dpi?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It's in /system/build.prop
ro.sf.lcd_density=
I bought an app called LCD Density Switcher because it cracks the market to still show all the apps that disappear when you mod the density.

How do u have the nexus 7 already
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

Awesome.

I would suggest ROM Toolbox over LCD density due to it having more options in controlling aspects of your phone

brokentoaster24 said:
Awesome. I know many of us will be wanting this when the 7 ships. Is the text still large enough to be easily read?
Its pretty good but in some cases..due to some apps not ready for tablets you make have to look a bit closer. Changing the font size will fix most thing just haven't had the chance to dig deeper yet.
sent from my evo 3d
Click to expand...
Click to collapse
CiDhed said:
Try 160? That is the default, maybe it will look better.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Tried it, both are pretty much the same with 160 being a bit smaller in text.
iwantanandroid said:
May I ask how you go about changing the dpi?
Click to expand...
Click to collapse
1. Get a file explorer such as root explorer or es file manager(go to settings allow mount rewritable and root access)
2.Then go to system(es file manager just go to the star button on the top left hand side and click on the phone button and you will see the system folder)
3.You will find a build.prop file make sure to make a copy of it and save it somewhere just in case for a backup.
4.Then click on the build.prop and open it with a text editor. (ES file manager has its own)
5. Now scroll down to "ro.sf.lcd_density", or something with lcd density(sorry im at work so i dont have my n7 with me)
6. Now the original lcd density is 213 so the best result for tablet mode is going 170 and below.
7. Save the file by press the menu button.
8. Reboot your N7 and then you got Tablet UI.

h3r3tic said:
How do u have the nexus 7 already
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Went to Google I/O

CiDhed said:
It's in /system/build.prop
ro.sf.lcd_density=
I bought an app called LCD Density Switcher because it cracks the market to still show all the apps that disappear when you mod the density.
Click to expand...
Click to collapse
where do i do that process? sorry im new to this all
do i not need to do the first step if i get the app?
if i dont get the app i cant use certain apps?

Here's how you can do it yourself with a file explorer
1. Get a file explorer such as root explorer or es file manager(go to settings allow mount rewritable and root access)
2.Then go to system(es file manager just go to the star button on the top left hand side and click on the phone button and you will see the system folder)
3.You will find a build.prop file make sure to make a copy of it and save it somewhere just in case for a backup.
4.Then click on the build.prop and open it with a text editor. (ES file manager has its own)
5. Now scroll down to "ro.sf.lcd_density", or something with lcd density(sorry im at work so i dont have my n7 with me)
6. Now the original lcd density is 213 so the best result for tablet mode is going 170 and below.
7. Save the file by press the menu button.
8. Reboot your N7 and then you got Tablet UI.
Now everything is not in excellent state, some font sizes need to be adjusted as well as the preview shots for the multitasking. But in due time we will have the perfect Tablet UI most of us actually wanted.
If there's others ways to do this without causing harm to our tablets shoot me a pm and ill post it in the first post. Hope you guys find this helpful.

Wish you could do this without rooting, wasn't going to root mine straight away but I want the tablet UI

RMXO said:
I would suggest ROM Toolbox over LCD density due to it having more options in controlling aspects of your phone
Click to expand...
Click to collapse
Ill try that out after work, and see if its friendly with my N7

SladeNoctis said:
Tried it, both are pretty much the same with 160 being a bit smaller in text.
1. Get a file explorer such as root explorer or es file manager(go to settings allow mount rewritable and root access)
2.Then go to system(es file manager just go to the star button on the top left hand side and click on the phone button and you will see the system folder)
3.You will find a build.prop file make sure to make a copy of it and save it somewhere just in case for a backup.
4.Then click on the build.prop and open it with a text editor. (ES file manager has its own)
5. Now scroll down to "ro.sf.lcd_density", or something with lcd density(sorry im at work so i dont have my n7 with me)
6. Now the original lcd density is 213 so the best result for tablet mode is going 170 and below.
7. Save the file by press the menu button.
8. Reboot your N7 and then you got Tablet UI.
Click to expand...
Click to collapse
Awesome.... Thanks so much :good:
---------- Post added at 07:54 PM ---------- Previous post was at 07:49 PM ----------
SladeNoctis said:
Now everything is not in excellent state, some font sizes need to be adjusted as well as the preview shots for the multitasking. But in due time we will have the perfect Tablet UI most of us actually wanted.
If there's others ways to do this without causing harm to our tablets shoot me a pm and ill post it in the first post. Hope you guys find this helpful.
Click to expand...
Click to collapse
Sorry to bother you I know your at work, have you managed to adjust the font sizes and preview shots? if so how?
Thanks again dude

Woah!?!? So this is native in JB? Just changing the pixel density will auto switch to tablet UI on reboot?
Oh and I was your 100th thanks

lhayati said:
Woah!?!? So this is native in JB? Just changing the pixel density will auto switch to tablet UI on reboot?
Oh and I was your 100th thanks
Click to expand...
Click to collapse
Well yes. If they didn't keep the old tablet UI, there would be immense backlash from ICS tablet users.

lhayati said:
Woah!?!? So this is native in JB? Just changing the pixel density will auto switch to tablet UI on reboot?
Oh and I was your 100th thanks
Click to expand...
Click to collapse
yes, this is essentially the same way ICS works as well, getting a certain pixel density kicks in the tablet UI
the padding on the bottom (in portrait) and sides (in landscape) is kind of annoying, going to try nova launcher to see if it can be lessened.
edit: nova set to a 10x10 with horizontal padding set to small and vertical set to none fixes that
tablet ui seems much more efficient use of screen space compared to the phone UI

Do the new expanded notifications work in the tablet ui? Could you take some screenshots?

[Android 2.1+] SIP HorsePower Dyno - measure your performance

Playstore Link:
https://play.google.com/store/apps/...siphorsepowerdyno&feature=more_from_developer
Updates in second post: http://forum.xda-developers.com/showpost.php?p=29938013&postcount=2
{
"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"
}
This is a dyno app, for scooters, motorcycles or cars.
I have only tested it on my vespa, but people told me it works good on other vehicles, aslong the engines sound can be recorded and IT IS NOT AN AUTOMATIC SCOOTER !
Unlike all other dyno apps, I don't use the GPS signal or the accelerometer to measure your speed, but i use the sound.
Ok, I know what you are thinking:
"Dude this wont work or do you really think: The louder the faster ?"
Here is how it works:
Each sound has its specific frequency, consider someone whistling low or high.
The frequency is always the same, let's say you run your engine at 2000 RPM or 2100 RPM, i can measure 2 different frequencies there and i can exactly say at which RPM the engine runs.
From the RPM i can calculate the EXACT speed (GPS or accelerometer just isn't exact, it's a mess).
From the speed difference at 2 points of time i can calculate the power that is needed to get from speed1 to speed2.
Done, thats it.​
There are a couple of important things you should be aware of, before you download the app:
1. Not all devices support the recording quality, therefore i uploaded a test app. Please download it, record sound (speak or something else, doesn't matter). Then replay the sound. If it doesn't force close, you are good to go. Link: https://play.google.com/store/apps/...29tLnBsZWRsc3RlZmFuLmhvcnNlcG93ZXJ0ZXN0ZXIiXQ..
2. In order to get the measurement right you need to know these values (it is a very technical app):
Overall Weight (vehicle + you + gas + backpack + helmet + trousers + shoes ...)
Gear Ratio (this needs to be as exact as possible as well, i use the overall gear ratio, which is your gear ratio divided by your tire-circumference in meter, i have an option to calculate the gear ratio by using the GPS speed, but as said before the GPS isn't exact enough)
Cw-Value (if you dont know what this is, please google it. I could fill a whole thread with information on this. If you don't enter the exact value here, you will still get comparable results for different dyno runs and engine setups aslong you leave this value the same)
Frontarea in squaremeter: (either measure it, or just leave the value, like the Cw-Value to get comparable results)
Temperature + air pressure: (can be get online, within the app)
One thing i didn't consider yet is how the tire changes during the run, the faster it spins the higher the tire circumference gets.
I compared my measurements to real dyno runs and its usually only about 0.5 horsepower off.
The displayed horsepower is "power on the ground". I know americans have some other fancy methods to measure this, but to be honest, "power on the ground" is the only measurement that is worth measuring.
Unlike power on the crank it is the real value which your engine has on the street.
Maybe you might have noticed that i am not native english speaking, so here are a couple of copy/pastes from other users, which i think help to explain what is going on:​
I tried a couple of more runs with this app. I'm really fascinated by your app. This time I tested mypinasco 225cc Vespa GL.
I still can't find a big enough road for that 3rd gear run, but I did ride on and off the motorway a couple of times in 2nd gear. Both runs gave me the same result within 0.5hp
Click to expand...
Click to collapse
it would be power at the ground. The sound frequency gives you the RPM of the engine, knowing the gear ratio and tire size gives you speed. The rate of change gives you acceleration.
Power = Force * Velocity
The forces that we care about are due to acceleration (f=ma) and drag (f=1/2*roh*A*C*V^2).
We know the mass, acceleration we got above, roh is constant and known for air at a given temp and pressure, frontal area*drag coefficient can be estimated, and velocity is known from above as well.
So, as long as you are not doing a burnout, it can measure the power at the ground.
Click to expand...
Click to collapse
Text Tutorial which i wrote here:
http://modernvespa.com/forum/topic101980?page=1
1. Go to “Settings”
Here are 2 options:
a) Calculation by Overall Gear Ratio
From the RPM/min the Speed is calculated by the overall gear ratio which you can enter below.
Overall Gear Ratio: “Primary Gear Ratio” times “Secondary Gear Ratio” devided by “Tire Circumference in meter”
E.g.rimary : 60/20=3
Secondary: 50/20 = 2.5
Tire Circumference in meter: 1.3
Overall Gear Ratio: 3 * 2.5 / 1.3 = 5.769
b) Calculation by Maxspeed
If the GPS was on during the run I record the speed and look for the max speed. Then after editing the frequency spectrum I look for the max RPM and calculate the Overall Gear Ratio. The GPS signal is sometimes unreliable so I recommend using option a.
If you have a digital Speedometer you can also check the max speed and enter it at “GPS TOP Speed in km/h” with option “b” checked.
All other settings are pretty obvious, just enter them as precise as possible.
If you don’t know the Cw-Value just leave the predefined value in there,
In order to compare different scooter setups, please keep in mind that these values should not change (unless they really changed, e.g. you lost 20kg or dismounted a windshield or whatever) and that you should keep the same position on the scooter for all dyno runs
Save the settings.
2. Go to “New Record”
Find a place where no other vehicles are. Best is a street which has a minimal gradient upwards.
If you want to record the GPS Speed hit the checkbox in the bottom right, enable the device’s GPS if it is not already (a popup will show up if it is not enabled) and wait for a GPS Lock.
Hit the Microfon-Button. The record is now started and the Buttons are locked. Locking the Menu Button is not possible, so don’t touch it. Power Button will shut the screen off, but the record will keep going.
NOW PUT YOUR DEVICE IN A BACKPACK!
In your pant’s pocket the airstream will be too loud, thus making it harder to find the right frequency.
Get on your scooter and start driving slowly. Shift to 2nd ord 3rd gear and from lowest RPM possible full throttle to max speed and hold max speed for a bit.
Stop your vehicle, get your phone and slide the ring from right to left to unlock the buttons.
Hit the microfone button again.
3. Find the run
Here you can see (easy put) the volume of your record. By pressing the Menu Button (^) you can replay the record, where the white area shows the replayed part. Move the red bars until the record of the run (from low rpm to high rpm) is in-between the red bars. Hit menu(^)-> Trim. The red areas will be cutoff, the green part will stay. Replay the record and see if all went fine or continue editing the now zoomed in part.
When done hit > to go to the next screen.
4. Find the right RPM curve
Usually our scooters have their max RPM at around 8000-9000 rpm. So your first look goes to the left side to find these rpm. Then look at the right side which curve has its max rpm at 8000-9000.
You should now know which curve is the correct one. Unfortunatly its not that easy to find the right curve programmatically, so what you first do now is:
Menu(^) -> Snap
Snap: This function starts looking on the very left side of the spectrum to find the signal with maximum strength. Then it looks in a small range heading right for the next max strength signal. Please keep this in mind !
Start removing the false signals from the very left and eventually “Snap” will snap to the right curve.
If snap wont find the right curve, because on the very left side it finds a curve under the real one, then you should either go back and cut the record a little earlier, so there is a signal of your run with lower rpm
Or
Disable snap ad completely edit the spectrum by hand, removing all false signals.
The white line shows the signals which will be used for calculation.
The green line is the smoothed signal, smoothing the signal is necessary. You can play around with the filterlength on the “Edit Spectrum” screen and on the “Result” screen. The larger the filterlength, the smoother the signal will be. But unfortunately too long filterlengths will lead to a wrong result. Play around with the filter on the spectrum screen and the result screen to see what it actually does.
5. Result
Well this is your result. You can save it and compare it to other results or you can share it with your friends.
Will this text tutorial work without pictures for you guys ?
If something isnt clear, just let me know, maybe suggest a better wording
I was asked what some permissions do or why the app needs them, so:
This application has access to the following:
Hardware controls
record audio
->well, no need to explain this i guess
Your location
fine (GPS) location
-> ... GPS
Phone calls
read phone status and identity
-> if a call is incoming i have to handle the current app state, for example stop the record, or stop the "data transforming" and so on
modify/delete USB storage contents or modify/delete SD card contents
-> save record to sd card/delete the record
Network communication
full Internet access
-> just needed to get the weather online
System tools
modify global system settings
->i am kinda confused why google makes this sound so bad, this is the permission to save private app settings (i use this to save weight,gear ratio, temperature...)
in code all permissions look like this, with the bold being this permission
uses-permission android:name="android.permission.PREVENT_POWER_KEY"
uses-permission android:name="android.permission.RECORD_AUDIO"
uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"
uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"
uses-permission android:name="android.permission.READ_PHONE_STATE"
uses-permission android:name="android.permission.INTERNET"
uses-permission android:name="android.permission.WRITE_SETTINGS"
uses-permission android:name="com.android.vending.CHECK_LICENSE"
Click to expand...
Click to collapse
Either watch this thread or follow me on Google+ for updates:
https://plus.google.com/105280101829289526269/posts
or:
https://plus.google.com/109720416927515295704/posts
If there are apple fanboys around here:
I am working on an iphone version.

Changelog:
06.09.2012:
Added "SHARE" at compare results
03.09.2012:
Jelly Bean related fixes
16.08.2012:
Mean of results can be build
13.08.2012:
Files go into different folders now
fixed a couple of typos and missing translation
The only problem right now is the filterlength, which i use to smooth the curve.
The automatic detected length is usually too short, so please change the value on the result screen.
I saw at least one word in the english version which was german, this is because the new eclipse version somehow doesn't handle files with the same filename right.
To come:
An option to rename the record straight after recording.
An option to build the mean of different results.
A better filter, without the need of chossing the filterlength.
I am pretty busy with my tests at University, so please dont expect any update before the 16th of August.

Wow! Very cool app! How goes the progress on it? I always wanted to make a measurement of actual power of my Vespa but the costs of diagnosis on the dyno seem to me to be too expensive. I hope that in two days there's an update to the application.

Version 1.5 is out, with the long awaited option to build the mean of different runs!

Version 1.6: jelly bean related fixes

1.61: Added "share" button to compare results.
Gesendet von meinem Nexus 7 mit Tapatalk 2

Very cool, and I want to get distance. As you say, f =ma,time can be recorded, the distance between two positions could be culculated.
Sent from my SHW-M250S using xda app-developers app

Sure, i will add that later.
I released a Free Version:
https://play.google.com/store/apps/...sZWRsc3RlZmFuLnNpcGhvcnNlcG93ZXJkeW5vZnJlZSJd

Updates in 2.03:
- The spectrum is visible at the "Trim Screen". This means it is lot easier to find the right positions to trim the record.
- Edit Spectrum: it is no possible - by turning "change snap area" on to tell the algorithm where it should look for the right signals. So instead of wiping the wrong signals you chose where the curve should be. This makes the editing much easier.
- Added the option to chose between DIN and SAE climate correction factors.
- Added the option to display the torque in NM or ft-lbs.
- Added a reminder to update the weather when a new record is done.
- The last two locations are saved at the Update Weather screen.
- lots of bugfixes
- details are attached to the email message and are inserted into the jpg when a result is shared
- UI changes: the navigation bar at the bottom is gone and was replaced by an ActionBar,

Some people still seem to think that this is something like a burp app.
->
http://www.scootering.com/Current-Issue/
94 Tech Tips – A Dyno in Your Pocket?
Yes it’s true, and Sticky checks it out.

Android Auto Prompt Freeze

I have Nexus 5 with Chroma installed and Pioneer 4100NEX.
I plug in my phone into USB port 2, go thru setup process on my phone, then I get to this screen on my head unit. I can't seem to get pass it. Anyone have any ideas? I tried restoring my head unit and phone, but I haven't tried a different ROM yet. My head unit detects the AndroidAuto device, but I can't get pass this "Drive safely..." prompt.
Well, I cannot post any links yet, but I'll do my best to explain the screen I see. The bottom half of screen is sky blue with a checkbox and "do not display this notice again." I have seen other videos where this sky blue portion is only along the bottom of the screen, but mine takes up half the screen. The checkbox to accept the prompt overlap with "do not display this notice again," so I can't get pass it...
http: //i60.tinypic.com/154blfc.jpg (get rid of the single space)

Hiya
Are you using cm 12.1 nightly? Looks like the density / resolution is off so the button you need is hidden.
They changed something in one of them which mucks up the screen density / resolution.
I found the 22nd nightly for one plus works at the right resolution which will allow you to click the buttons you need.
Check your devices cm change log for density and goto the night before.
Andy
---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------
Sorry just saw chroma mentioned in your post... Stand by that the density is wrong as such would try a different room. Shouldn't look like that.

Appreciate the tip. I found the density setting. Mine is currently at "480 DPI (device default)."

namiam said:
Appreciate the tip. I found the density setting. Mine is currently at "480 DPI (device default)."
Click to expand...
Click to collapse
Hiya
I don't think that makes much / any difference, didn't for me, that changes the density on the phone but not on android auto.