For rooted devices only
Update (Oct 20): Fixed a bug with busybox in the full version. This bug could cause booting problems because of a damaged build.prop file. Should be totally safe now when saving the density to the boot up density of the device..
(Lite version, see attachment, doesn't save the density setting and is therefore safe by definition)
App to change the density setting of the screen.
In short, by decreasing the density the display will create a high resolution effect by displaying more info on the screen. For example, with a density of 180 I get this on my Galaxy S screen:
{
"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"
}
or
There is a extensive help file "on board" with some (important) info.
Free version
Is also a lite version and fully sponsored by adds. The lite version only makes it possible to temporarily change a density setting. This setting will be undone when you reboot the phone. It uses "hot reboots" and no "cold reboots". It doesn't rely on the build.prop density parameter. Should in principle work on all devices. The free version is attached to this post
Full version
Full version (no adds + with the possibility to save the density and/or write it to the build.prop + desktop widgets for fast loading temporarily saved density setting) can be bought from from the Android Market (0.75 Euro). Search for "LCD Densitiy Changer" or scan:
Screenshot of the app itself (tada)
lite:
View attachment 403903
full:
View attachment 403901
Yeah, not shocking, but it is what is under the hood that makes it worthwhile
Tips
tip1: If the dialer doesn't scale well with other density settings try dialer one
tip2: It seems that ADW Launcher can get the most out of a density change. By changing the amount of colums and/or rows of the desktop one has a better control how icons and widgets will display. Also a smaller density will allow you to add more icons to the desktop without any clutter or overlap.
tip 3: Devices that run a default default density of 240 (Nexus, Droid, Galaxy S etc), a density of 200 gives the best result. It's the best compromise of having more info on the screen and readability of that info.
tip 4: Beautiful widget center problem: see here for a possible workaround.
Link to "app-site" with some additional tips, tricks, help and some frequently asked questions: http://densitychanger.blogspot.com/
Any other tips about getting the most out of this great "Density tweak" are very much appreciated. I will add them to the first post and, if possible, I will incorporate them in my app.
Note for developers
To make your app support all density values (and don't have any scaling problems, even when compatibility mode is on!), select SDK Version 4 as your minimal target and add the following to your AndroidManifest.xml file:
Code:
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true" />
-----------------------------------
Thanks to xda-member jdsemler who discovered this density tweak on his Samsung Captivate.
bratfink for giving some very useful input
Cutefox for noticing that deactivating the compatibility mode solves the scaling problem (in most cases).
No go on motorola Dext using android 2.1.
Congrats on this one.. very handy and ease of use.
I have tried on my nexus one with modaco froyo on it.
It work very well on most of the apps; When you have a list of information (like gmail, sms, setting, post on Facebook, etc ) is perfect, in other case the program looks a little weird.
Some app don't take the whole screen (Setting of Digital clock widget) and in other cases the graphics looks a little to small (dialer and Kit auto).
It would be great to have the text in the list smaller to see more information without the problem on other application.
I hope that i explain myself well!
Great app!
gfandrea said:
I have tried on my nexus one with modaco froyo on it.
... in other case the program looks a little weird.
Some app don't take the whole screen (Setting of Digital clock widget) and in other cases the graphics looks a little to small (dialer and Kit auto).
Click to expand...
Click to collapse
Did you disable "Compatible Mode" in the Settings screen? This will fix the scaling issue in most of the apps. (It's in the help )
Beackman said:
No go on motorola Dext using android 2.1.
Click to expand...
Click to collapse
That's a pitty. But maybe you can explain what exactly doesn't work. Does the app not run? Can't you manage to get another density setting running?
tids2k said:
Congrats on this one.. very handy and ease of use.
Click to expand...
Click to collapse
Thanks tids2k.. long time no see Also on Androids nowadays?
appelflap said:
That's a pitty. But maybe you can explain what exactly doesn't work. Does the app not run? Can't you manage to get another density setting running?
Click to expand...
Click to collapse
The app run ok's, show's the default density, but when i change the vallue and reboot the phone, they no apply the changed density and back to 160.
Beackman said:
The app run ok's, show's the default density, but when i change the vallue and reboot the phone, they no apply the changed density and back to 160.
Click to expand...
Click to collapse
Ok, thanks for the feedback. I first want to make sure that it doesn't cause boot problems on devices.
As for the density change, maybe it isn't possible to get lower than 160? Can you try a higher density like 180? (Not that nice... of course). If that doesn't work maybe your system files doesn't allow to set the density. If you can't manage to get in running on 180, maybe you can attach the build.prop from the system folder of your device. (maybe the problem can be found there).
appelflap said:
Thanks tids2k.. long time no see Also on Androids nowadays?
Click to expand...
Click to collapse
yah matey .. keeping myself busy here
Using Incredible - does not work for some reason. I changed it for 200, and rebooted. However when powering back up it goes back to default. I am ROOTED and SU popped up and granted permissions.
appelflap said:
Ok, thanks for the feedback. I first want to make sure that it doesn't cause boot problems on devices.
As for the density change, maybe it isn't possible to get lower than 160? Can you try a higher density like 180? (Not that nice... of course). If that doesn't work maybe your system files doesn't allow to set the density. If you can't manage to get in running on 180, maybe you can attach the build.prop from the system folder of your device. (maybe the problem can be found there).
Click to expand...
Click to collapse
i do the test and post the result and the build.prop.
thx mate.
cheers.
For those for which the tweak doesn't work some background info:
The app changes a parameter in the build.prop in the system directory. The parameter that is changed is ro.sf.lcd_density=xxx. If the app doesn't work for your device please check the build.prop file. If the value of the parameter is changed to the value you entered in the app then somehow this parameter is ignored by the system, or the parameter is changed back at boot-time. (To exclude the last scenario, check the build.prop after you changed it with the app and before you reboot, and again after a reboot)
Another scenario is of course that the app just doesn't change this parameter. In that case there can be a busybox problem or last and I of course least simply a bug in my app.
On the Sprint EVO it is not working;
i've attached my build.prop from after changing the setting, before rebooting, and the second from after the reboot.
i had tried to set the value to 180.
i would love for this to work, let me know if you need any other info from me to help you out.
elingreen said:
On the Sprint EVO it is not working;
i've attached my build.prop from after changing the setting, before rebooting, and the second from after the reboot.
i had tried to set the value to 180.
i would love for this to work, let me know if you need any other info from me to help you out.
Click to expand...
Click to collapse
Thanks, this is something I can work with!
elingreen said:
On the Sprint EVO it is not working;
i've attached my build.prop from after changing the setting, before rebooting, and the second from after the reboot.
i had tried to set the value to 180.
i would love for this to work, let me know if you need any other info from me to help you out.
Click to expand...
Click to collapse
EDIT: found the problem. I placed an update in the first post (version 2.1). This version should solve your problem.
Others who had used the the app without succes should try the new version also!
Man for my problem, i find a workaround, i add the line ro.sf.lcd_density=xxx at the end of build.prop, aplied the density usin your app and it works.
This is great, works well on my Vibrant using touchwiz launcher. However, some widgets are resized smaller or distorted. You probably know this already though ^^. Will make a donation in the market.
ElahC said:
This is great, works well on my Vibrant using touchwiz launcher. However, some widgets are resized smaller or distorted. You probably know this already though ^^. Will make a donation in the market.
Click to expand...
Click to collapse
Yeah the widgets .... I know. On the other side, it creates a whole new market for widgets Watch the market for some very expensive new widgets that will fit on displays with divergent density settings
Your donation is much apprectiated btw.
Beackman said:
Man for my problem, i find a workaround, i add the line ro.sf.lcd_density=xxx at the end of build.prop, aplied the density usin your app and it works.
Click to expand...
Click to collapse
use the new 2.1 version. This will parse all possible variations
Related
So, this is my first attempt at programming for android. Well, my first attempt at java as well. Regardless, I am pleased with the outcome and though I would share. As a father of four, I always like keeping a photo of my kids handy. The gallery is nice, but not for a quick, "Have you seen my daughter recently" situation. So I went to the market... Surprisingly I didn't find much. At least not much that did what I wanted. So, here is what I wanted and what I currently have.
Application Website is http://deanstudios.net/dev/frameme
Features:
1x1, 1x2, 2x1, 2x2 Widgets
full screen image when clicked
multiple widgets supported
selectable picture frames
Crop image when selecting
Full widget preview on your background
Click on one widget - Fling to the others
Click on widget and fling through images in user selected directory
timed rotation of widget image in directory mode
Reconfigure existing widgets
Atrix external SDCard support
Frameless image
Screenshots:
{
"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"
}
Current Frames:
Issues:
Test it out and let me know if you find something else.
ToDo's:
Add additional frames
Add better support for hdpi devices. Need something to test with though.
As you can see it is pretty simple and straight forward. For me, it also does the job well. I have other ideas for it, feature wise as well as new frames. I am hoping to have time to implement them. However, I do have four kids so we will see. If there is interest, I might throw it into the market as well. For now, you can download it at the links below.
If you enjoy this app and want to support me it is available in the market for $0.99. It will always be available here free so don't worry. The QR Code below will take you directly to the market page. If you have bought it and enjoy it please consider rating it.
I would love to hear what you think and what device you are using it on if you have something other than a Hero. As it is, it was designed to support mdpi and android 2.1. Enjoy!
Updates:
FrameMe 1.3.5 - Several other memory related issues have been corrected. There is also the addition of a "No Frame" option when choosing your frame. An about screen was also added and available from the app drawer as well as the full screen image menu. Support for the Atrix's external sd card was also included.
FrameMe 1.3.3 - Added additional work-around's for the "out-of-memory" issues. Should most of the FCs due to bitmap creation and use. Hopefully you notice a difference.
FrameMe 1.3.1 - I am sorry 1.3.1 took so long to get here. There are some serious bugs in the Droid X gallery that I found in the last release. It took me a while to find a solution that didn't break all the other phones out there. Now 1.3.1 works on Droid X as well. (at least with my testers). I also added three new frames including one to go along with HTC Sense or similar design. Hope you enjoy.
FrameMe 1.3.0 - Okay, so a lot of you have been asking for a 2x2 widget and cycling of the image in the widget. Well, 1.3.0 brings all that and a little more. Not only was a 2x2 widget added, but a 1x2 and 2x1 as well. For those widgets using the directory option you can also have the displayed image cycle through images in the directory at a user set interval. Under the hood there has been several performance optimizations and that pesky Galaxy S bug is now dead as well. It should work on all the phones in the series. Also, landscape images are shows in landscape mode so you don't loose half the image. For now, that is about it. Again, I am sorry you have to redo all your widgets but it was necessary to support different widget sizes.
FrameMe 1.2.0 - Version 1.2.0 has had quite a bit of code rewritten. For starters the configuration screen now shows a full widget preview on your own wallpaper. The frame selection is now graphical and pressing menu when a widget is clicked provides an option to reconfigure that widget. There have also been some minor bugs squashed in the directory mode functionality.NOTES: Database has changed, please remove widgets before upgrading.
FrameMe 1.1.2 - Addition of several new frames. Directory mode was tweaked to allow the thumbnail image to be used as the first image when clicked.NOTES: For Directory enabled widgets, the thumbnail image will be in the rotation twice if it was selected from an image within the target directory.
FrameMe 1.1.1 - Corrected the memory issues in the directory option. It now can support unlimited images in a directory.NOTES: Images are loaded and scaled in real time. To improve fling speed size your images appropriate for your phone. It will work regardless though.
FrameMe 1.1.0 - Added the ever requested directory option. Now you can bind a widget to a directory on your sdcard and when clicked it will fling between the images in that directory. Thumbnail image is not required to be in that directory and still shows in the fling list for other non-directory widgets. NOTES: This modifies the database so you will need to re-add you current widgets. Also, it is easy to run out of memory when pointing to a directory with lots of images. It does resize though to help with this.
FrameMe 1.0.1 - Added the Rustic Edge frame & code cleanup.
FrameMe 1.0.0 - Corrected a few bugs with canceling out of the config screen without selecting an image. Removed the fling action if only one widget (image) is available. Code cleanup.
KidFrame 1.3 - Added a few more frames. Also made it so if you click on an widget to get a full size image you can now fling (swipe) and it will cycle through all widget images without having to close and click again. First image delays a little while it is processing and I am not completely sold on it yet. Also added my icon in the correct place for hdpi devices.
KidFrame 1.2 - Created resized thumbnails for display on the widget. This should help with memory resources and allow the number of widgets to be almost unlimited. Also added a third frame (was just playing with frames).
1.1 - Link above has been updated with the newest version: Code has been rewritten to us a database back-end. Configurations now are kept after a reboot. The selected image is now user cropped and resized so it should not limit the number of widgets you can add. Hopefully there will be more to come.
Great app. Thanks. I had an idea to fill a 4x4 screen with images of my family for easy viewing but using ADW the 6th+ widget fail to load. So I will go with 4-5. Cant wait to see what other frames you have in mind.
okcnyyfan said:
using ADW the 6th+ widget fail to load.
Click to expand...
Click to collapse
Looks like this may be a memory issue. If you resize your images manually to around 600 on the longest side you should be able to use as many as you want. I played around and had issues with camera images (5mp) not loading but smaller (640x480) images would just fine.
I will look into actually resizing the images for the thumbnails. This should help. Thanks for the feed back. I am glad you like it.
I'm glad I stumbled across this! Thanks much!
Sent from my PC36100 using XDA App
PhilD41 said:
Looks like this may be a memory issue. If you resize your images manually to around 600 on the longest side you should be able to use as many as you want. I played around and had issues with camera images (5mp) not loading but smaller (640x480) images would just fine.
I will look into actually resizing the images for the thumbnails. This should help. Thanks for the feed back. I am glad you like it.
Click to expand...
Click to collapse
I went down to one widget and noticed it wouldnt reload after reboot. I will try a smaller image and see how it works.
okcnyyfan said:
I went down to one widget and noticed it wouldnt reload after reboot. I will try a smaller image and see how it works.
Click to expand...
Click to collapse
Same here, not showing up after reboot.
Sent from my PC36100 using XDA App
Yeah, I am working on the reboot thing. It is driving me a little nuts. I will update the original post once I have it figured out. Thanks for giving it a try.
I don't personally have a use for this sort of thing, but thought I would congratulate you on your foray into the Java/Droid world - keep up the good works, and enjoy raising them kiddos!
oneirosFade said:
I don't personally have a use for this sort of thing, but thought I would congratulate you on your foray into the Java/Droid world - keep up the good works, and enjoy raising them kiddos!
Click to expand...
Click to collapse
Thanks! It has been a hair pulling ride. I should start my 4 year old in java. That way it could be a family activity.
Nice! My mom will love this app. I will wait to tell her about it though until it resizes the pics to thumbnails. She'll want to dedicate multiple, full, screens to her niece and currently it looks like that's not possible without getting errors.
Jedis said:
Nice! My mom will love this app. I will wait to tell her about it though until it resizes the pics to thumbnails. She'll want to dedicate multiple, full, screens to her niece and currently it looks like that's not possible without getting errors.
Click to expand...
Click to collapse
The current file uses resized thumbnails. It was an internal change and I got it wrapped up last night. You should be good to go! Glad you like it!!
Man those kids are so cute with them fat cheecks
Sent from my HERO200 using XDA App
Just installed 1.2. I will let you know how it goes.
edit: It's working great. I have 7 loaded on one of my screens and no blanking out or losing images on reboot. Thanks. I love this app.
Any way you can make the crop box be the same dimensions as the screen so we can tell what will show up. with the current setup you have to center the image so it show when you open it.
okcnyyfan said:
Any way you can make the crop box be the same dimensions as the screen so we can tell what will show up. with the current setup you have to center the image so it show when you open it.
Click to expand...
Click to collapse
I can, and I had actually tested it that way. The problem is that if you select an image based on the portrait view it never works correctly in landscape. With the 1:1 square, if you center what you want to focus on it works in both modes.
I realize that many people never use a landscape home (many devices don't support it) but many of us do. If enough people make the request, I can change it though.... or if you device doesn't support a landscape home screen then maybe I could make you a custom build... It might be a few days though.
Thank you, great job, working great on the evo.
Sent from my phone.
PhilD41 said:
I can, and I had actually tested it that way. The problem is that if you select an image based on the portrait view it never works correctly in landscape. With the 1:1 square, if you center what you want to focus on it works in both modes.
I realize that many people never use a landscape home (many devices don't support it) but many of us do. If enough people make the request, I can change it though.... or if you device doesn't support a landscape home screen then maybe I could make you a custom build... It might be a few days though.
Click to expand...
Click to collapse
Good point. Personally I usually show off my images when in the portrait mode.
maxomus said:
Thank you, great job, working great on the evo.
Click to expand...
Click to collapse
That is great to hear! I was hoping it would work okay on the hdpi devices. I have limited ability to test outside of my own Hero. I am glad it looks okay. If you have the ability, I would love to see a screen shot from the EVO.
I am glad it is being enjoyed!
Hey, on you EVO does it have a custom icon or the little green android stock thing? I think I need to make an hdpi icon...
It is the stock icon, Here are some screens from the evo:
The only thing I noticed & im not sure if it is because of the evo's screen size or not, but some of the pic gets cut off, well not the full size pic you know, I have to stretch & center it when cropping...
Sent from my phone.
maxomus said:
It is the stock icon, I will up some screens shortly.
Click to expand...
Click to collapse
Hummm bummer, I will get an update up that has the correct hdpi icon. I also have a few new frames.
Any requests for frames? Can't promise I can make them, but I can try.
sent from my mobile brain (hero)
{
"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"
}
Will not be updated anymore.
Boarder is successor of Unlimited Soundboards.
Description
Now it's easy to create the most beautiful soundboard you have ever seen!
- Create soundboards
- Share soundboards
- Set sound as notification/ringtone/alert
- Launcher shortcut to soundboard
- Fast notification enabling and disabling
- Dropbox support
- Settings for each sound:
Name, name size and name paints
Image and active image
Sound volumes and second click actions
And more..
- Soundboard options:
Sound settings
Background file and/or color
Screen orientation
Auto-arrange options
Please read "Help" on soundboard menu.
If you have suggestions, feedback or anything to say then please leave post, I will listen.
Documentation
Unlimited Soundboards tutorial - Making your first graphical board
Help
About
Old downloads
Market
Screenshots
Changelog
1.14 - 10.7.2011
Fixed board context menu in the soundboard menu
Minor fixes
1.13 - 7.7.2011
Fixed Set as notification/ringtone/alert
Fixed duplicate layout on soundboard menu
Won't crash because of menu db updating failure
Added keyboard input types
Added trackball support for finetuning
1.12 - 7.7.2011
1.13 with an issue in the release package
1.11 - 4.7.2011
Duplicate soundboard option
Featured sound can pause other sounds
Filemanager will only try to access sdcard
Option to show a different image when sound is active
Fixed a saving bug when using resources from another board
Different actions when clicking a sound while playing
Fast notification enabling and disabling
Fast soundboard menu loading
Option to fade in and out on pause/resume
Notes: Create new shortcuts after updating
1.10 - 26.4.2011
Auto-align option for graphical board
New sounds will be placed on free space
1.07 - 1.4.2011
Fixed crash when turning off screen on graphical board
Fixed crash when adding non-image file as image
File browser shows full filename now
There are huge increase on apk size because of librarys needed for Dropbox.
I used ProGuard on 1.06, but never got it working the way I wanted it to work.
1.06 - 30.12.2010
Dropbox support
Board directory shortcut on file explorer
Bugfixes
1.05 - 27.11.2010
List board displayed only first row of sound name
List board corrupted when using line break on sound name
1.04 - 27.10.2010
Graphical sound font size changing
1.03 - 23.10.2010
Better CPU usage
Improved stability
Bad boardfile bugfix
1.02 - 19.10.2010
Resize images on scale
Copy colors
Changing background resets background position
Larger font on list board
Sorted file explorer
All images noticed on convert
Orientation selection
'Linebreak/space on name' bugfix
Improved stability
Reset position
Minor things
1.01 - 15.10.2010
Larger text on file explorer.
Set as ringtone/notification/alert on graphical. (Doesn't work on froyo yet.)
1.00 - 27.9.2010
Graphial soundboard
Something else probably too
0.10
Sound volume settings works properly
Board settings
Delete file option while removing sound
Minor fixes
0.02a - 26.8.2010
Image for soundboard
Launcher shortcut for soundboard
Fix - sounds weren't playing after playing sounds too many times
Better icon
0.01a - 19.8.2010
First release
Sounds Nice
Please feel free to tell your opinion/suggestions if you have tried it
Mikuz. said:
Description
Screenshots @0.2a
img651.imageshack.us/img651/9453/launchers.png
Application link and shorcuts at launcher
img826.imageshack.us/img826/3896/soundboardsmenu.png
Soundboard menu view
img225.imageshack.us/img225/2659/soundboard.png
Soundboard view
Sorry but can't post them properly *
Click to expand...
Click to collapse
*You can upload them to the post directly from your computer, you don't need to upload them on an external host-site.
Is this the same app as Custom Soundboard? Otheriwise I cannot find 'unlimited soundboards' anywhere..
thx!
waterbound said:
Is this the same app as Custom Soundboard? Otheriwise I cannot find 'unlimited soundboards' anywhere..
thx!
Click to expand...
Click to collapse
EDIT: Now you can find Unlimited Soundboars on market.
Luggruff said:
*You can upload them to the post directly from your computer, you don't need to upload them on an external host-site.
Click to expand...
Click to collapse
Thanks, attachments wasn't working for me probably because I had some problems with javascript on my browser.
Now it's better
Thanks for this great app!
The ability to play multiple simultaneous sounds is a must have feature.
On my unmodified HTC Incredible running 2.2 the text is larger than the horizontal bar it is supposed to fit in, so the bottom of the text gets cut off. Or maybe the horizontal area is too small vertically.
kenc3dan said:
Thanks for this great app!
The ability to play multiple simultaneous sounds is a must have feature.
On my unmodified HTC Incredible running 2.2 the text is larger than the horizontal bar it is supposed to fit in, so the bottom of the text gets cut off. Or maybe the horizontal area is too small vertically.
Click to expand...
Click to collapse
Row had accidentally fixed height. Also noticed that board got unreadable when using line break.
Thanks
Doing some relatively bad thread necroing here, but I don't know that I want to create a whole new thread just for a suggestion or two...
A couple bugs (at least on my Samsung Galaxy S running stock Eclair):
When the screen shuts off from idling and you have a graphical soundboard open, the app crashes. This also happens if you lock the screen by way of the power button. This happened with the graphical Soundboard I was working with, as well as with a brand new, freshly created graphical soundboard (no sounds added, completely default settings). This does not seem to happen with a List-style Soundboard, or when you're up one level looking at the list of soundboards you've created.
When selecting files for either new sounds or for the graphics of those sounds, the font is too large for the row height and gets cut off at the bottom of any text. It's not unreadable, but the individual rows are hard to select. In actuality, the font size is probably okay, and the row height just needs to be increased.
Some suggestions:
In a Graphical soundboard, have an auto-align function like the main app window; something where you can set up how many rows and columns you want, and then arrange the sounds by that layout, in a grid-style layout.
Options for both Auto-arrange and manual arrange of the above function.
Create new graphical soundboard objects in a fresh space away from other items, so you're not creating new ones on top of each other. Possibly requires auto-arrange to be turned on.
Allow a default setting for the Name, Image, and Sound settings for a particular Soundboard so you don't have to set each one every time you make a new soundboard item.
I just want to say how AWESOME this app is. It lets me create EXACTLY the kind of soundboard I want, with a background pic, images for each sound, individual volume settings, you can play sounds overlapping or choose not to... It's GREAT! ...I just wish it was a bit easier to create multiple soundboard objects, and didn't crash from graphical soundboards. XD
Hope this is helpful!
It's not necroing. This thread is alive as long as I am developing this app. I'm developing this app until I state that I am not developing this app (on this thread).
Also please don't expect me to update this app if there are no suggestions or bug reports.
All posts to this thread are most welcome.
ChromWolf said:
Allow a default setting for the Name, Image, and Sound settings for a particular Soundboard so you don't have to set each one every time you make a new soundboard item.
Click to expand...
Click to collapse
This is exactly why there are "Duplicate sound" feature on sound options. If you are sure that this feature doesn't fit your purposes please inform me and I will consider making "default sound" feature.
Notice that duplicating sound makes it exact duplicate, so you may not notice that there are two sounds one on top of the other.
I have both bugs fixed by now. I will get back to your other suggestions when I have more time. I will be updating my application asap.
Mikuz.;7749079[B said:
Changelog[/B]
1.07 - 1.4.2011
Fixed crash when turning off screen on graphical board
Fixed crash when adding non-image file as image
File browser shows full filename now
There are huge increase on apk size because of librarys needed for Dropbox.
I used ProGuard on 1.06, but never got it working the way I wanted it to work.
Click to expand...
Click to collapse
EEEEEEE!!!! So excited, and it looks GREAT, and doesn't crash! Thank you thank you thank you!!! *finds "Thank" button*
Mikuz. said:
This is exactly why there are "Duplicate sound" feature on sound options. If you are sure that this feature doesn't fit your purposes please inform me and I will consider making "default sound" feature.
Notice that duplicating sound makes it exact duplicate, so you may not notice that there are two sounds one on top of the other.
I have both bugs fixed by now. I will get back to your other suggestions when I have more time. I will be updating my application asap.
Click to expand...
Click to collapse
I think that particular one was just a "User Education" issue. XD I haven't tried seriously playing around with it yet since I'm at work (and already spent enough time the other day messing with it while at work, LOL), but even so.
For me anyway, my suggestions were just things I felt would make the experience even better, but since it's already GREAT, they're just kinda "meh, whenever you get to them." Very happy to see 1.07 so quickly though to fix the issues, I'm just beaming now, this app is entirely too awesome.
ChromWolf said:
For me anyway, my suggestions were just things I felt would make the experience even better, but since it's already GREAT, they're just kinda "meh, whenever you get to them." Very happy to see 1.07 so quickly though to fix the issues, I'm just beaming now, this app is entirely too awesome.
Click to expand...
Click to collapse
Well I appreciate your suggestions (and bug reports too) since I have ran out of ideas what I should add. Sure I could figure something out if I really tried but I'm not sure if that would make this app better or worse.
That said - thanks
need help posting soundboard on market
Hello I used Mikuz unlimited soundboard app creator to make a custom soundboard, i got everything created and sounds assigned and icons, and the project name is in green, and now I am not sure how to post it up for people to share and try out for free any help would be appreciated.
can this be uploaded to the market? or how does that step work?
shatdat7 said:
Hello I used Mikuz unlimited soundboard app creator to make a custom soundboard, i got everything created and sounds assigned and icons, and the project name is in green, and now I am not sure how to post it up for people to share and try out for free any help would be appreciated.
can this be uploaded to the market? or how does that step work?
Click to expand...
Click to collapse
Make sure to read "Sharing board" topics on help.
It can not be uploaded to the market.
To share your board on internet I would suggest you to make it zip file on computer or on your Android device.
(Make sure to zip folder named as your board, not content of it, to make this simpler for receivers.)
You can upload it to Dropbox (you can use Get Shareable Link feature), Multiupload or similar file sharing services.
You can also send it directly to friend using MSN etc.
If you are sure everything on it is 100% legal, you can post it here and ask me to include it on 1st post. (I will upload it to my server if I accept it.)
Mikuz,
This is a great app...really like it.
You asked for suggestions, so here are a few:
Include the ability to pause or stop a sound by touching the sound a second time, instead of having to hit settings, then pause.
Include the ability to create a "stop all sounds" button.
Include the ability to have different images for each state of the sound (stopped or idle, playing, paused)
Include ability to set additional sound preferences per soundboard (like a preference to pause/play on corresponding clicks, or stop sound on second click)
Anyway, thanks again for this cool app...I really, really, really like that I can use it to play entire songs, and not just tiny files.
Welcome to xda-developers wagman67 as well as shatdat7 whose post count I forgot to check
wagman67 said:
Include the ability to have different images for each state of the sound (stopped or idle, playing, paused)
Include ability to set additional sound preferences per soundboard (like a preference to pause/play on corresponding clicks, or stop sound on second click)
Click to expand...
Click to collapse
Good suggestions, thanks.
I'm wondering if it would be better to select if you want to always play, pause or stop sound on second click per sound rather than per board.
wagman67 said:
Include the ability to create a "stop all sounds" button.
Click to expand...
Click to collapse
I think you mean like a normal sound but it would stop/pause all playing sounds. Good idea.
Hi there, I was looking for an App like this a long time and now finally found yours meeting most of my need, so thanks a lot!
I played with it a little yesterday and came up with some ideas I would like to mention here in case it could be easily implemented.
First I was wondering if the already existing Dropbox-Implementation could be used for importing sound and images as well. Now I would put sounds into Dropbox, open Dropbox on Android, chose what I want dowloaded for the Soundboard, switch back to the Soundboard and then for each file click through to the Dropbox-Folder to add it... Using the internal Dropbox-connection this could be done much easier and faster... (Or am I missing something already there?)
Second about importing Images: I would like a button to automatically set the size to the original dimensions of the image instead of having to tap these in manually...
I was very happy to find, that I could switch to landscape, as I use a tablet that is not very nice to handle in portrait-mode... Really nice App
Ah, and are there any Soundboards shared by users yet?
Sorry it took some time to answer but I'm quite busy and probably won't develop until january. (Though you never know if I get excited enought about it.)
If you want to copy a file to a board using the current Dropbox implementation in the UnlimitedSb then you should: upload a board to the Dropbox, copy a file to the board's Dropbox folder and then download the board from the Dropbox.
The current implementation is ment to have a copy of a board in the Dropbox. Copying a file is possible but not handy.
Browsing the files in the Dropbox to copy a file to a board folder is an interesting idea. I don't use the official Dropbox app much but I think that it should be able to handle the same thing decently.
I will see what I can do when I have the time. I should also see if I can improve the Dropbox support at some point. I wasn't able to do everything I wanted since I was using an early version of the Dropbox client.
Nope, haven't heard of any publicly shared boards yet.
Good news soundboard enthusiastics, there's a huge udate coming!
I will rebrand this app since Android 4 will be required and the update will really impove this app and make it more useful.
It will take some time until it can be released. I feel like I should release it already since it's so much better than the current version but I really need to make the experience complete for a good new start.
You will notice when the new version is out if you take a look at the 1. post. Now let's all make sure we got some sandwitch prepared on our desks.
PS. If you figure out a good name for a soundboard app you can PM or email me. Just make sure it's something rather under 10 than 20
voom said:
First I was wondering if the already existing Dropbox-Implementation could be used for importing sound and images as well. Now I would put sounds into Dropbox, open Dropbox on Android, chose what I want dowloaded for the Soundboard, switch back to the Soundboard and then for each file click through to the Dropbox-Folder to add it... Using the internal Dropbox-connection this could be done much easier and faster... (Or am I missing something already there?)
Click to expand...
Click to collapse
This is made easier in Boarder. You can put a sound to Apps/Boarder/<board name> directory in Dropbox and then download it using Dropbox implementation for Boarder.
In Unlimited Soundboards everything that doesn't exist in board directory in Dropbox would be removed in download operation. This is optional in Boarder and there will be dialog promoting the cleaning operation.
voom said:
Second about importing Images: I would like a button to automatically set the size to the original dimensions of the image instead of having to tap these in manually...
Click to expand...
Click to collapse
Not sure If you refer to the last value of dimensions or bitmap size as the original dimensions.
However, I changed the values above text fields to represent the original size of the bitmap. I added a button after the fields for reverting the size to what it was when the dialog was opened.
This change will be included in following releases of Boarder.
voom said:
I was very happy to find, that I could switch to landscape, as I use a tablet that is not very nice to handle in portrait-mode... Really nice App
Click to expand...
Click to collapse
I'm planning to make it possible to choose hybrid mode (portrait and landscape). Hybrid board would react to changing the orientation of your device in listening mode.
Landscape and portrait would, however, be completely separated and only share the same board folder and listening session. This means both must be maintained by their own. There could be feature for copying sounds from orientation to other, making maintaining a bit easier.
This will not be included in a while and can be expected in Boarder after release in Android Play.
{
"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"
}
disclaimer:
it shouldnt be necessary to mention but well, Paranoid-Settings is meant for official paranoid android only or ports that stay true to our vision. it is not meant to be included in other roms or kangs - unless we give permission. this is our good name that people pull through the mud when they mix it with conflicting source like aokp. hybrid engine and dpi changer will only result in a crappy user experience for the end-user. Hybrid relies on a clean system and does not change its DPI, thats the whole point of it. furthermore hybrid engine is huge and complicated to kang because it grew over half a year and hundreds of commits, resets, reverts, rewrites. the only real hybrid engine is the result of a clean repo init and . rom-build.sh devicename.
kangs and roms that dont have our permission can either write their own implementation (its really just a text file reader/writer) or adapt on the old paprefs version in the ICS branch, which is 100% opensource. hybrid engine is 100% open source aswell of course.
Some of you may have heard of tablet mode and if you have tried it you know well that it smashes your phone. Apps are small, their layout is screwed, things overlap, crash or stop working, Google Play forbids you to download, if you tried AOKP you cant even use launcher and phone. In short, it is a mess.
PARANOIDANDROID changed that. It does not "heal" tablet mode, it obliterates the boundaries. You define how big or small apps are, you define in which UI they display, no matter if your phone runs in tablet or phone mode, which also you can define. Customize every single entity on your phone, lockscreen, navigationbar, system-components, widgets, apps. If you prefer stay with your three bearpaw buttons + drop-down curtain or switch to a combined navigationbar + drop-up notificationcenter, enjoy Youtube in 3D, Gmail and settings in 2-columns, Chrome in its better mobile UI, etc. Nothing overlaps, nothing crashes, everything works as you'd expect. This is completely new ground and has never been realized before, it is lightyears from tablet mode.
We created it to establish the idea that tablet/hybrid mode can indeed work and that is was an error on Googles side to use the same layout for high resolution devices that is used on tiny little things like htc wildfire. We saw how badly build.prop tablet-mode was milked so we decided to remain closedsource until the codebase is mature enough to publish. Our first repos went public last week and the rest will follow soon, i will personally commit the hybrid sourcetree into CM9. Until then, do not ask us for sources, we have good reason to do it like this and when it's out people will know why, they will see something that works, not features for show. We are still fully open to ports. As long as they stay true to our vision and base on CM9.
As the sheer amount of porting requests needed to be addressed somehow we open this topic so maintainers can help each other and it'll be easy for us to take a look once in awhile as our pm-boxes are exploding. We understand that setting up PA can be quite confusing since it introduces must-have configurations that are unique.
GUIDE FOR PORTING PA 1.6 and higher (JELLYBEAN/CM10)
the bad news is, everything has changed. the good news is, porting will be way less troublesome. (-;
look at the ICS guide for more info, this ones onna be straight forward.
1. pad.prop no more. you'll have to look in /system/etc/paranoid/properties.conf. dont forget to supply the same file twice, as backup.conf, its a sefety net for users who screw their properties.
you dont need to worry about this file anymore. rom_min/max are arbitrary values. choose something that makes sense for your device. the GUI will pick it up and load its sliders with these values.
rom default dpi is a simple fallback value, used by the GUI aswell. rom default mode is the same. notice though that modes are not hardcoded, Youre targeting the actual layout containers. the GUI can even extract them from any apk. layouts for sysUI are: 360 (phone mode), 600 (phablet mode) and 720 (tablet mode). apps can define these tresholds as they want. thats the reason you couldnt get tabUI for playmarket for instance, because its containers sits at 800dp. "tabletUI" was hardcoded to 720. so thats no problem anymore.
the rest is clear, find a couple of good values for standard apps. make sure you dont create a spotty experience. and do set tabUI for the interesting apps. i have seen PA reviews on youtube and the guy browses the phone and everythings stock ... that kinda sucks. you dont need to boot into tablet mode right away, but at least take the time to find good values for settings, gmail, etc.
Code:
###################
# PARANOIDANDROID #
###################
## CONFIGURATION
%rom_dpi_min=160
%rom_dpi_max=320
%rom_default_dpi=320
%rom_default_layout=360
## CONFIGURATION
%hybrid_mode=1
%system_default_layout=0
%user_default_layout=0
%system_default_dpi=0
%user_default_dpi=0
## WORKSPACE PREFERENCES
android.dpi=0
android.layout=0
com.android.systemui.dpi=%rom_default_dpi
com.android.systemui.layout=%rom_default_layout
## SYSTEM PREFERENCES
com.paranoid.preferences.dpi=270
com.android.chrome.dpi=%rom_default_dpi
com.android.chrome.layout=%rom_default_layout
com.android.contacts.dpi=%rom_default_dpi
com.android.contacts.layout=%rom_default_layout
com.android.settings.dpi=245
com.android.settings.layout=720
com.android.calendar.dpi=260
com.android.browser.dpi=260
com.android.browser.layout=600
com.android.calculator2.dpi=160
com.android.calculator2.layout=600
com.android.email.dpi=230
com.android.email.layout=600
com.android.vending.dpi=220
com.android.vending.layout=1000
com.google.android.gm.dpi=250
com.google.android.gm.layout=600
com.google.android.talk.dpi=260
com.google.android.talk.layout=360
com.google.android.youtube.dpi=240
com.google.android.youtube.layout=800
com.google.android.apps.docs.dpi=240
com.google.android.apps.docs.layout=600
## USER PREFERENCES
well, thats it. i told you it was easy.
for those who port for legacy devices, we included a hide softscreenbuttons option in settings/system/navigationbar.
and then theres the speed dial preferences in the PA panel. thats a little bit compliated right now because the xml files that drive it are in the app itself. im not sure if you can backsmali it, it has a rom fingerprint. i need to ask jesus. one thing more, then that is resolved you will be able to create your own configurations, and those can not only contain hybrid data but ANY setting you can make in the entire android system.
example: on nexus we dont have much space in portrait mode, so the android standard of 5 notificationicons in tabletUI overlaps. so in one of those prefs i simply say: sysUI.dpi=240, that makes the systembar pretty big, sysUI.layout=720, that drops it into tabletUI, clock=0, that hides the android clock, notificationnumber=2, that limits the icons to two. i guess most of you will switch off softbuttons, and with these prefs you can do it, or even create several and let your users choose.
i know jesus has already completed the code to load user presets, i will add the information when i have it.
and dont forget this in your build.prop
Code:
ro.cm.version=PARANOIDANDROID
ro.modversion=PARANOIDANDROID
ro.pa.version=PARANOIDANDROID-pa_YOURDEVICE-1.XXa-DDMMMYYYY
oh, and do not, under any circumstance, touch build.prop dpi. system dpi runs always in default dpi.
GUIDE FOR PA 1.5 and lower (ICS)
1. Unlock Tablet Mode for all devices
This has been already stuffend into the framework by us and if you use our files you wont need it, but i will include it nonetheless. Legacy devices crippled with hardware buttons need hacks to make tablet mode work. I dont know exactly whom to thank for this find, names that pop up in my head are Xylograph and evilisto. Ics compilant devices simply need one more entry in their build.prop: qemu.hw.mainkeys=1. You can include both, doesnt hurt.
Code:
--- a/services/java/com/android/server/wm/WindowManagerService.java
+++ b/services/java/com/android/server/wm/WindowManagerService.java
@@ -5962,7 +5962,7 @@ public class WindowManagerService extends IWindowManager.S
unrotDw = dw;
unrotDh = dh;
}
- int sw = reduceConfigWidthSize(unrotDw, Surface.ROTATION_0, density, un
+ int sw = reduceConfigWidthSize((int)(unrotDw / density), Surface.ROTATI
sw = reduceConfigWidthSize(sw, Surface.ROTATION_90, density, unrotDh, u
sw = reduceConfigWidthSize(sw, Surface.ROTATION_180, density, unrotDw,
sw = reduceConfigWidthSize(sw, Surface.ROTATION_270, density, unrotDh,
build.prop
Code:
###################
# PARANOIDANDROID #
###################
ro.sf.lcd_density=192
qemu.hw.mainkeys=1
2. Find out tabletmode DPI treshold value
Tablet mode is AOSP standard functionality. ICS is will drop into tablet mode if it acknowledges a certain treshold DPI, depending on your devices screen. Changing ro.sf.lcd_density in /system/build.prop will do. You can calculate that value as follows, here's a snippet of the ICS code that decides if your UI runs in tablet mode or phone mode.
Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;
mStatusBarCanHide = shortSizeDp < 600;
In short, you need to reach a short-side device-independend pixel number of 600. Example: Nexus has a width of 720 and a height of 1280, shortest side is 720, default density is 320. shortSizeDp = 720 * 160 / 320 = 360. lower than 600, phone mode. We need to lower the Dpi: shortSizeDp = 720 * 160 / 192 = 600. Thats it, tablet mode!
The formula is:
Code:
treshold_dpi = shortest-side-dp * 160 / 600
3. Setting up pad.prop and build.prop
/system/pad.prop is the file that defines how apps scale and in which UI they display. You should provide your users with a nice selection of everyday apps and define the system-apps well. Users should not be shocked when the phone boots up, what they are supposed to see is something that drops their jaws.
For Galaxy Nexus it looks like this:
Code:
###################
# PARANOIDANDROID #
###################
## DEFAULTS
%rom_tablet_base=192
%rom_phone_base=320
%rom_mid_base=260
%rom_mid_high_base=290
%rom_framework_dpi=250
%rom_systemui_dpi=220
%rom_launcher_dpi=290
%screen_default_width=360
%screen_default_height=567
%screen_default_layout=268435474
%screen_opposite_width=600
%screen_opposite_height=1018
%screen_opposite_layout=268435491
## CONFIGURATION
%hybrid_mode=1
%system_default_dpi=%rom_mid_base
%user_default_dpi=%rom_mid_base
%user_default_mode=1
android.dpi=%rom_framework_dpi
com.android.systemui.dpi=%rom_systemui_dpi
## PREFERENCES
com.android.phone.mode=1
com.android.inputmethod.dpi=%rom_phone_base
com.android.inputmethod.latin.mode=1
com.android.inputmethod.dpi=%rom_phone_base
com.android.camera.mode=2
com.android.camera.dpi=%rom_tablet_base
com.cyanogenmod.trebuchet.mode=1
com.cyanogenmod.trebuchet.dpi=%rom_launcher_dpi
com.anddoes.launcher.mode=1
com.anddoes.launcher.dpi=%rom_launcher_dpi
com.teslacoilsw.launcher.mode=1
com.teslacoilsw.launcher.dpi=%rom_launcher_dpi
com.android.chrome.mode=1
com.android.chrome.dpi=%rom_mid_high_base
com.android.calendar.mode=2
com.android.contacts.mode=2
com.android.email.mode=2
com.android.htmlviewer.mode=1
com.android.mms.mode=1
com.android.settings.mode=2
com.android.vending.mode=2
com.google.android.gm.mode=2
com.google.android.googlequicksearchbox.mode=2
com.google.android.talk.mode=1
com.google.android.youtube.mode=2
What is important here is that you need to set it up first with device specific informations. Here's a small rundown of these values:
%rom_tablet_base=xxx - table mode treshold dpi
%rom_phone_base=xxx - default device dpi
%rom_mid_base=xxx - a good middle value that works both for tabUI & phoneUI apps, for nexus its ~260
%rom_mid_high_base=xxx - a little bit higher than middle
%rom_framework_dpi=xxx - a good value for the lockscreen
%rom_systemui_dpi=xxx - good value for navigationbar
%rom_launcher_dpi=xxx - default value for trebuchet
%system_default_dpi=0 - sets the global density for system apps. 0 means undefined. We will probably make it obsolete soon.
%user_default_dpi=xxx - sets the global density for non-system apps, set it to default dpi as this will guarantee that all of your users apps will look stock
%user_default_mode=1 - sets the global UI for non-system apps. 1 = phoneUI, 2 = tablet UI. set it to 1, all user apps will display in mobileUI. If the user has tablet ready apps he can switch himself in the settings panel
## P.A.L PARAMETERS - these are extremely important. you get them by logging the output of Configuration in tablet mode (_opposite) and phonemode (_default) kevdliu wrote a nice little helper to make it easier for you, look here
make dead sure you get pad.prop right or you'll get bootloops or crashes!
notice that we use packagenames for apps, if you dont know the name of an app open up your shell and type:
Code:
adb shell
pm list packages -f
android - framework-res, applies to lockscreen, dialogs, powermenu, toasts
systemUI - applies to the navigationbar, makes it bigger or smaller. DO NOT APPLY an UI to these two apps. everything else is fine, set it to tablet or phoneUI all you want, but not these two!
Configuration in phone mode and tablet mode
build.prop needs to be configures like this:
Code:
###################
# PARANOIDANDROID #
###################
ro.sf.lcd_density=192
ro.cm.version=PARANOIDANDROID
ro.modversion=PARANOIDANDROID
ro.pa.version=PARANOIDANDROID-pa_maguro-1.5a-28JUN2012-180025
density to tablet treshold. versions to PA and version in that exact format because internal functions are relying on it (OTA for example). change the name of your device and the date. the last numbers, i have no idea what they are, came from the buildscript.
4. Check our sourcetrees
More and more source will be published soon. Right now we have three projects out, OTA, Backup and Trebuchet (optimized for tabletmode with cool features). Hybrid code will come out soon. Use what you can get from there: http://betadan.com/paranoid/sources/
5. Port the rom
You are ready to go. Do what you always do when porting roms. I have zero experience with that. Again, use CM9. Do not even think about using AOKP.
Check out Xylopgraph's PA porting guide
6. Link to our Google Apps
Google policy forbids you to use their market if you change your DPI. The only values allowed are 160, 240, 320. Why? No one knows why. There have been workaroundw, wiping cache, using a valid DPI, open market, reboot back, blablabla, forget it, its rubbish. It will work for a minute and then it will cease to. In our package Phonesky and GoogleServicesFramework were hacked. It has other additions aswell: http://4ndr01d.com/drcmda/common/
7. Post your port link and help out others
We will include you in our webpage and when our repo's are open you are invited to compile from source and/or submit patches and additions. We might even work together as theres still much to do. Be sure to help out others here.
-----------------------------reserved
Thanks Moles, this will continue to help us on the Vivow Port till we can build from source.
Thanks for this innovation. Salute!
I just thanked all post ,if yo had one more I woudl have thanked it to ,
in other words , thanks !
Awesome! Thanks for this awesome contribution!
Thanks for opening up this thread, I actually have a question for you professionals. I have been trying to figure out how to enable audio during the boot animation. I have been searching like crazy to figure it out. I have tried adding the following to /system/customize/CID/default.xml. And also ading a android_audio.mp3 to /data/local.
Code:
audio="/system/customize/resource/android_audio.mp3"
I have also tried placing the android_audio.mp3 and the bootanimation in /system/media but no love.
My buddy GROGG88 even made a zip file for me to flash that added some files to /system/bin but still no luck. Here is the zip if you would like to take a look at it.
I plan on making some more bootanimations for the Paranoid Android ROM for the Sensation and would really like to be able to include audio with them. Any assistance you can give will be very much appreciated.
What files does ParanoidOTA depend on, (/system/framework or others)? I get it copied over, but it crashes on me when I try to open it.
sgtkwol said:
What files does ParanoidOTA depend on, (/system/framework or others)? I get it copied over, but it crashes on me when I try to open it.
Click to expand...
Click to collapse
Only settings are used (but settings depends on OTA not OTA on settings), you must be sure the right intent is sent via Settings > About > Check for updates. Also we need first to setup environment if some device is gonna add OTA.
D4rKn3sSyS said:
Only settings are used (but settings depends on OTA not OTA on settings), you must be sure the right intent is sent via Settings > About > Check for updates. Also we need first to setup environment if some device is gonna add OTA.
Click to expand...
Click to collapse
I'm porting from Crespo4g to Epic4g which are very similar devices.
Paranoid OTA and Paranoid Settings showing in Settings.apk I pulled from Crespo4g must be different, then. Not seeing a ParanoidSettings.apk, am I missing something? I have "Paranoid Settings" showing, but clicking it or "System" crash Settings.apk that I pulled from Crespo. No Paranoid Settings when I compile from source. Unable to local pad or pal within existing builds, either.
made an app that displays the needed PAL information and tablet dpi threshold and thought i would share it here for other developers
its attached to this post
kevdliu said:
made an app that displays the needed PAL information and thought i would share it here for other developers
its attached to this post
Click to expand...
Click to collapse
thanks! is there a way to make it calculate the treshold dpi aswell?
molesarecoming said:
thanks! is there a way to make it calculate the treshold dpi aswell?
Click to expand...
Click to collapse
yup im going to update it shortly
uploaded
mole: ive got my port on i717 almost running flawlessly now, few minor issues
http://forum.xda-developers.com/showthread.php?t=1686320
Thinking about porting this..
I am ported it to HTC Desire HD..
http://forum.xda-developers.com/showthread.php?p=26929079
Sent from my Desire HD using Tapatalk 2
JamieD81 said:
mole: ive got my port on i717 almost running flawlessly now, few minor issues
http://forum.xda-developers.com/showthread.php?t=1686320
Click to expand...
Click to collapse
need your problems here dude, thats why i opened the topic.
if somethings not working post logcats, etc.
@molesarecoming
I totally forgot my skills of compiling kangs, can you guide me a bit through pm... Wifi Tethering is not fully working....
My computer specs, already had external HDD to compile...
-Intel i7-2760qm (8 cores, 2.4ghz)
-8 GB Ram
-1 TB HDD SATA (Internal HDD)
-500 GB HDD 3x faster writing...
DaXmax said:
@molesarecoming
I totally forgot my skills of compiling kangs, can you guide me a bit through pm... Wifi Tethering is not fully working....
My computer specs, already had external HDD to compile...
-Intel i7-2760qm (8 cores, 2.4ghz)
-8 GB Ram
-1 TB HDD SATA (Internal HDD)
-500 GB HDD 3x faster writing...
Click to expand...
Click to collapse
what i do is mostly hacking. i have never ported a rom before. i guess what i would do is taking a nightly or compiling a build, test if everything works and then add pa's additions. i cant remember all components but from mind they are: framework.jar, framework-res.apk, android.policy.jar, services.jar, maybe core.jar. the apps are not so important, you can compile our trebuchet fork from source, try making settings.apk run, if not i think that ones coming out today and if not today than very soon.
it would be cool if one of the guys who's made it writes a small rundown and i would put it up.
WELCOME TO PARANOIDANDROID
Noob's Guide to PA Settings
{
"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"
}
Integrated somewhere deep within the ParanoidAndroid source, is a Hybrid Engine. The Engine that makes PA stand out of the crowd. The feature of Per-App-Density & Per-App-Layout. (PAD & PAL)
Now, it has expanded beyond, & offers independent customization of even more visual elements, such as Lockscreen, Widgets, StatusBar/NavBar etc.
The Hybrid Engine, is the source that powers it all. But to implement it we need something much more simpler, something that allows High-Level Control.
This is where ParanoidPreferences app comes in. (Abbv: PAPref)
This handy app interacts with the Configuration files, & allows to control any & all elements easily.
This guide for those who might need it. The App in itself is pretty self-explanatory, but to make it easier to understand, I've made a visual guide, explaining each & every part of the app in detail.
Feel free to ask any questions that you might have
--------------------Jargons--------------------
You might come across some terms that are commonly used across the app, & all over the threads & blogs.
I'll try to explain them briefly.
DPI: Dots Per Inch. As the name defines, DPI is the number of dots per inch of a screen.
In PA, we can modify DPI of any & every app or service independently (PAD).
Lower DPI value, would cause a general shrinkage, & higher DPI value, would cause the app to get bigger.
In general, we have a few standard DPI values:
xHDPI: 320 DPI | HDPI: 240 DPI | MDPI: 160 DPI | LDPI: 120 DPI
DP: DP, or DIP, is Device Independent Pixel.
On an Android device of 160 DPI screen,
Code:
1dp = 1px (pixel)
Hence, for a 320 DPI screen,
Code:
1dp= 1/2 px
& so on.
DP (or px) can be used to customize the layout of the app used. PAL is where we make changes in px of any app or service, & change its layout to Phone/Phablet/Tablet or any custom layout (wherever applicable).
We use some standard px values as: 360px: Phone Mode | 600px: Phablet Mode | 720px: Tablet Mode
NOTE: The examples used below & in all subsequent posts is of a screen with standard 320 DPI (xHDPI). Some values might differ for other standard DPI screens, but the theory remains same.
To access the ParanoidAndroid Settings, Navigate to Settings -> ParanoidSettings
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--Move on to Post 2--
This is the main Interface of PAPref.
Lets explore the sub-menus in detail:
1)
2)
3)
4)
5)
For educational purpose, I'm selecting a random app, say 'GMail', to explain the available customization option to the users:
1)
2)
3)
4)
Example results of GMail modification:
The result of modifying Lockscreen Size:
PS: And no. Changing DPI does NOT change the time on the lockscreen.
The 3 standard Workspace UIs:
CREDITS:
molesarecoming
D4rKn3sSyS
First
Nice guide as always goku :good:
I will link it in my builds' thread, and I think every maintainer should do so
great guide
i was wondering if its possible to have a paranoid gb? my device already has ics and jb, but not gingerbread, which is the most stable, so im not sure if its possible
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
rashidshahzad said:
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
Click to expand...
Click to collapse
always compile paranoidandroid with . rom-build.sh devicename, or tell your dev to do that. make/lunch/brunch will not result in a functional rom. when youre done, try not to change your build.prop, the script does all that for you.
another thing is, hybrid engine needs a healthy system DPI. if you go and change ro.blabla.density it will simply shut down and refuse to work. this ones actually strange because i have seen many people so hung up on build.prop dpi they just cant stop themselves - hybrid engine can do all that regular tablet mode could in the past, even dropping all your apps into tabUI at once if you so desire - it does that without harming your system though (read, not changing the system dpi).
if its stillnot working then it can be fingerprint and signing issues. in that case only a fullwipe helps. when the rom is built clean from the beginning though all will work right out of the box, issues like that are born from wrong compiling.
Default size Default UI
Hi,
I am new to Paranoid Android but that hasn't stopped me from recognizing the innumerable possibilities it offers. I have a galaxy nexus International version and I was experimenting with almost everything, As you said, the Hybrid Engine needs a healthy UI rather than just any random number. Hence my launcher went into a crashloop upon changing orientation.
Another thing I would like to know is the basic difference between the System App Default Size and Default UI.
Also what are the safe values for the Galaxy Nexus.
What if I want to reset everything back to normal? I tried doing that through the given option but certain values remain overridden. Will I have to perform a full wipe?
molesarecoming said:
always compile paranoidandroid with . rom-build.sh devicename, or tell your dev to do that. make/lunch/brunch will not result in a functional rom. when youre done, try not to change your build.prop, the script does all that for you.
another thing is, hybrid engine needs a healthy system DPI. if you go and change ro.blabla.density it will simply shut down and refuse to work. this ones actually strange because i have seen many people so hung up on build.prop dpi they just cant stop themselves - hybrid engine can do all that regular tablet mode could in the past, even dropping all your apps into tabUI at once if you so desire - it does that without harming your system though (read, not changing the system dpi).
if its stillnot working then it can be fingerprint and signing issues. in that case only a fullwipe helps. when the rom is built clean from the beginning though all will work right out of the box, issues like that are born from wrong compiling.
Click to expand...
Click to collapse
Thanks for your reply but all above is very technical information can u please guide me that except full wipe how can i restore to noram phone mod and laso please check attached screenshot for better understanding of the current status of the issue.
YouTube app can't go any higher than 600px without crash
Hi
Thanks for the guide.
However, something disturbes me a bit when I use my Nexus 7 tablet. I have seen all those cool reviews with the YouTube app in tablet mode 800px-1200px, but mine can firstly only go to 800px - and when I choose it or 720px, it crashes!
600px is the only one I can choose - the phone app, which kinda sucks.
Can someone help me?
Nice guide Bidyut! Will help many first timer PA users!
Orr.Penn.18 said:
Nice guide Bidyut! Will help many first timer PA users!
Click to expand...
Click to collapse
Being a first time PA user - this did help me a lot and I am quickly realizing just how powerful this hybrid engine is.
I appreciate the examples of how changing UI settings per app can change the layout (gmail, youtube).
Is there an ongoing list of apps that are affected by particular layout settings AND what the "recommended" or common UI settings per app are?
Thanks!
Try this
Ham duden said:
Hi
Thanks for the guide.
However, something disturbes me a bit when I use my Nexus 7 tablet. I have seen all those cool reviews with the YouTube app in tablet mode 800px-1200px, but mine can firstly only go to 800px - and when I choose it or 720px, it crashes!
600px is the only one I can choose - the phone app, which kinda sucks.
Can someone help me?
Click to expand...
Click to collapse
Hey! i had the same issue and I know how frustrating it was. Here's what to do. Go to Settings;Paranoid settings;INTERFACE...and on the right hand side you'll see:- Workspace UI, System Apps UI, User Apps default UI,...all of them being "Phone Mode". You have to change the last one, "User Apps Default UI" to TABLET MODE and reboot. Voila! Youtube in 3d!!
rashidshahzad said:
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
Click to expand...
Click to collapse
having the exact same issue on 2.54 ! :S
Was ok on 5.52 !? why ?!
if anybody can tell !
Thx
Hello, I love this ROM but I am trying to fine tune a little. I have everything in tablet mode, which works very well for me and I have my System apps default size DPI set to 196. This makes the icons a good size and fits them nicely on the screen but, I am not able to take advantage of all of the usable space on the screen. There is area at the top and bottom that I am unable to use, how can I maximize the space of the entire screen in tablet mode?
I've attached a pic to show the range of where I am allowed to place apps. There is a whole unused space at the top and bottom.
Great, great guide...
A must read to all who uses this rom.
Description:
UI Tuner is a small app that can alter your phone's default window settings like density, screen size and overscan area without rebooting.
For overscanning, this picture from developer.android.com may help you understand what it is if you're not familier with it:
{
"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"
}
It's equelivant to setting overscan like this: 96, 54, 96, 54 [LEFT, TOP, RIGHT, BOTTOM]
Note:
Changes persist after rebooting!
Based on Android Open Source Project (AOSP), this app works only on 4.3+
Changes cannot be reverted unless you reboot your phone and use this app or adb commands:
Code:
adb shell wm density reset
adb shell wm size reset
adb shell wm overscan reset
Tested on:
HTC ONE M7
HTC Wildfire S [CyanogenMod 4.4.2+]
Lenovo S820 (ROW_4G) [4.4.2]
Nexus 7 2012 [CayanogenMod 11 m9]
OnePlus One (bacon) [4.4.2 XNPH25R]
Samsung GALAXY Ace Plus GT-S7500 [SpeedMod 4.4.2 Build 2.5] [Stock 2.3.6]
Samsung GALAXY S2 Plus
Samsung GALAXY S3 [CayanogenMod 11]
Samsung GALAXY S5 [stock]
Samsung GALAXY Tab 2 (7) P3100 [CyanogenMod 11 4.4.2]
Sony Xperia Z-Ultra
Screen shots:
Change log:
Version 2.7:
(FIXED) Per app settings on Lollipop 5.0+
(NEW) Visual overscan chooser
(FIXED) Current overscan not showing properly
Version 2.6:
(ADDED) Material design for Android 5.x+
(NEW) Visual overscan chooser
(FIXED) Current overscan not showing properly
Version 2.5:
(FIXED) A problem with applying settings
Version 2.4:
No root: changing Density, Screen size and Overscan no longer needs root access on any device running Android 4.3 or later versions!
Faster effects: Since we no longer use root mode except for restarting / rebooting.
Version 2.3:
Added density and screen size presets (long click their text boxes).
Optimised per app settings display and service persistence.
Version 2.2:
Fixed: force close issue in start up if Set on boot option wasn't ticked.
Reduced apk file size a little bit.
Version 2.1:
Fixed: force close issue in start up if Set on boot option wasn't ticked.
Version 2.0:
Added auto start service option.
Renamed to UI Tuner
First release on Google play.
Google play link
Version 1.2 Beta:
Added some animations (Fade in and out).
Added per app settings which needs the newly added GET TASKS permission, click START to monitor running apps. .
Added Russian and German translations, thanks to @pavik62 and @w0rinal
Version 1.1 Beta:
Supports Android 4.3+.
Added XDA Thread link.
Added Set on boot option.
Added Keep Settings dialog.
Added Auto SystemUI (and other apps) restarter.
Added Reboot (Soft, Normal, Recovery, Bootloader)
Version 1.0:
Initial release.
Download:
Google play link
Donation version
Thanks for sharing! Works well on my S3 with CM11.
Works on an S5 running stock
A video showing this off would be awesome!
I'll give it a try on my Shield. Thanks for sharing your app.
Thanks!
HTC ONE M7 works fine.
Add the Russian language.
What about the permissions? Can anybody explain that?
Overall great app but I'm missing two things you could add:
1. Something that will restart systemui after applying settings
2. "flash-to-disable" zip would be also nice
[!] Belive me you don't want to set resolution to more than GPU can do :silly:
[Q] How to disable this from recovery?? I already removed it from /data/app and /data/data. I also wiped and reflashed system
Does it have a "Keep Settings" popup window (like windows etc) in case someone really screws up overscan?
EDIT:
Looking at the post above mine maybe it really needs something?
not for sensetion
not for now.
whats the difference between changing the DPI and changing the resolution???
you can't really change the resolution...
and it works fine on S2 Plus
ehsan.gdrzi said:
whats the difference between changing the DPI and changing the resolution???
you can't really change the resolution...
and it works fine on S2 Plus
Click to expand...
Click to collapse
of course u can.
Works on Lenovo S820 (ROW_4G) running 4.4.2 but why i set up a higer resolution then native i can't use my hardware keys (menu, home and back). Any idea why?
Nice work! Thanks for sharing app
Thanks everyone for your replies. ?
v1.1 is on its way.
Magicman500 said:
A video showing this off would be awesome!
Click to expand...
Click to collapse
It would be a bit hard with my accent but I'll try once I implement some other changes.
pavik62 said:
HTC ONE M7 works fine.
Add the Russian language.
Click to expand...
Click to collapse
Added, thanks.
Eleo said:
What about the permissions? Can anybody explain that?
Click to expand...
Click to collapse
Only one permission for now, which is ACCESS SUPERUSER.
v3n0m93 said:
Overall great app but I'm missing two things you could add:
1. Something that will restart systemui after applying settings
2. "flash-to-disable" zip would be also nice
[!] Belive me you don't want to set resolution to more than GPU can do :silly:
[Q] How to disable this from recovery?? I already removed it from /data/app and /data/data. I also wiped and reflashed system
Click to expand...
Click to collapse
Both options added, thank you.
blueether said:
Does it have a "Keep Settings" popup window (like windows etc) in case someone really screws up overscan?
EDIT:
Looking at the post above mine maybe it really needs something?
Click to expand...
Click to collapse
Added, it will remain for 15 seconds before reverting back to previously applied settings, thanks.
M3n0 said:
Works on Lenovo S820 (ROW_4G) running 4.4.2 but why i set up a higer resolution then native i can't use my hardware keys (menu, home and back). Any idea why?
Click to expand...
Click to collapse
I have no idea, setting my phone's density from 150 to 75 or 200+ didn't cause any problems, but I'll look into it, thanks for your feedback.
very interesting app
It also needs a help section where explain differences between overscan, screen size and resolution it also needs a option that we can decide if we want changes persist or not so we can play safe with the settings
M3n0 said:
Works on Lenovo S820 (ROW_4G) running 4.4.2 but why i set up a higer resolution then native i can't use my hardware keys (menu, home and back). Any idea why?
Click to expand...
Click to collapse
I'm having the same problem on my OnePlus One (bacon), running 4.4.2 XNPH25R. It happens only when I change the resolution (when changing DPI or overscan the buttons still work). It's not really a huge problem for me because I can just enable softkeys, but it would be nice if you could look into it.
mudkip908 said:
I'm having the same problem on my OnePlus One (bacon), running 4.4.2 XNPH25R. It happens only when I change the resolution (when changing DPI or overscan the buttons still work). It's not really a huge problem for me because I can just enable softkeys, but it would be nice if you could look into it.
Click to expand...
Click to collapse
It looks like the same symptoms. I dont have a problem either. I pull down notifications, go to settings and launch my home launcher from there and everything works. It's just that in the Window Manipulator the keys are disabled.
Bassel Bakr said:
Thanks everyone for your replies. ?
v1.1 is on its way.
Click to expand...
Click to collapse
So can you tell me how to disable it if I can't enter system. I don't want to wipe data. I'm using Nexus 7 2012 with cm11 m9. I'm able to use adb and fastboot it's just that my screen is black after boot only with statusbar and I can't do anything.