Can any dev help me with that, What changes do I have to make in a 4.3" screen Rom(custom) to fit a 3.7" screen device, I tried to change the dpi and that was in vain the Sense started crash, so is their any other way to do that
Librastar said:
Can any dev help me with that, What changes do I have to make in a 4.3" screen Rom(custom) to fit a 3.7" screen device, I tried to change the dpi and that was in vain the Sense started crash, so is their any other way to do that
Click to expand...
Click to collapse
try to search about resizing- that is what you have to do in order to fulfill your wish
changing the screen resolution may ussualy multiply the problems only...- and is used for different purpose...
search tutorials about..... 9.png`s and/or tools to automate their processing...
when you`re asking about resizing rom - i assume it has been built for another device,
so, to make everything fuly working- i think the rom ought to be ported
Resizing an app is not an easy task- doable but time consuming ( and your nerves sometimes )
so people in the rom threads, complaining about small resizing issues do not fully realise the depths
the dev has to dig to in order to have everything polished without a glitch
edit: To simply change the resolution only, you may wish to try < blade buddy > app from the market
Related
Google's already indicated that tablets and smartphones won't be sharing the same Android build until Ice Cream Sandwich in Q4, though interestingly enough, it turns out that the tablet-friendly Honeycomb actually has Gingerbread's interface quietly tucked underneath. According to modder Graffix0214, all you need for making the jump is one simple tweak in a system file: assuming you already have root access, use your preferred method -- Pocketables recommends the LCDDensity for Root app -- to change the LCD density value to 170 or higher to emulate a smaller, denser display. After a reboot, you should then see some Gingerbread love as demoed by Graffix0214's video after the break; and likewise, set the value to 160 or lower to roll back. It sure is nice to have an option, eh?
http://www.engadget.com/2011/05/20/android-honeycomb-has-hidden-gingerbread-interface-enabled-by-h/
I am curious if this works... if it does then maybe full screen apps and video players will not have the status bar.
oopsallberrys said:
I am curious if this works... if it does then maybe full screen apps and video players will not have the status bar.
Click to expand...
Click to collapse
I didnt see this until I arrived at work so I couldnt try it. Just wondering if anyone has. I saw that Zoom supports it.
I am sure that it will work- It is not really a surprise to me.
I remember messing around with the density setting and, even on my HD2, the icons and everything would completely change depending on what the density was set to.
That was a far back as 2.2.
dbiggss said:
I am sure that it will work- It is not really a surprise to me.
I remember messing around with the density setting and, even on my HD2, the icons and everything would completely change depending on what the density was set to.
That was a far back as 2.2.
Click to expand...
Click to collapse
Different RES images for LDPI, MDPI and HDPI.
plz delete
dcmtnbkr said:
Not working on the TF. my guess is 3.1 is the key.
Click to expand...
Click to collapse
Same.
10char
Can't you just edit build.prop whic lcd density app does?
plz delete
I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
--(New)GPS doesn't work - need to mess with GPS libs when I have more time
--(New)The FM Radio app's graphics are messed up
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
good attempt! nice to see to back into work. May be some developers can help you out.
I would like to apologize first, as it is 08:19 in the morning and I'm already drunk. lol.
Well, let's start with the easy bits:
1. --Keypad backlights don't turn on
Mainly the thing is that the Wildfire S ROM does not have support (or it is not activated) for a physical keyboard; therefore the need for backlight is redundant. To fix this you will either have to manually add the code lines or un-comment them. I suggest talking with adlx or xdbg since both of them have implemented this feature in the two custom ROMs.
2. --Facebook button doesn't work (duh)
As above, the ROM doesn't know (or doesn't want to know) about the physical keyboard. Same suggestions as above.
3. Landscape/portrait issues.
Well. The main problem here is the android system. By definition it detects the longest size on the display and sets it as the height. Therefore you'll have a tough time fixing the standard display to landscape. As above, I suggest speaking with the devs that worked on these roms and implement the ChaCha kernel files into the Wildfire ROM.
Aaaaaand that's about it I guess. I wish you good luck!
Drunk, this early??
Good effort!
Sent from my A810e using Tapatalk
qzfive said:
I found a guide that mentions basic Sense porting to another Sense device. I tried this with this Wildfire S ROM for a few reasons:
--I prefer the "standard" HTC Sense as found on any other device (ie. Black status bar, black apps, etc.)
--I wanted to see how well it'd run
--I wanted to see if there'd be any problems with anything
After following the above guide, I notice only the following bugs:
--Camera is upside down
--Rosie keeps force closing because of forced landscape orientation so I have to use an alternate launcher
--Lockscreen is always in Portrait no matter what
--Keypad backlights don't turn on
--Facebook button doesn't work (duh)
To try and fix the Rosie problem, I tried copying over the Rosie.apk and Rosie.odex from the Chacha's 2.3.5 OTA, but no dice, the system doesn't even see it.
Anyone have any tips on how I could fix any of the above? I'm no dev, and I only tried this for (basically) the fun of it to see how it'd turn out and my "experience", so to speak, only goes as far as swapping files here and there - I felt like the Development forum was the best place to post this. Apologies if it isn't.
Click to expand...
Click to collapse
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
adlx.xda said:
Nice!
For the backlight, maybe you could try using system/lib/hw/lights.msm7k.so from the stock Chacha rom, or even from SuperOSR...
You cannot copy/paste an apk+odex file, it will probably never work. Try deodexing it first, then copy it.
I guess this is the right place to ask
Click to expand...
Click to collapse
I copied lights.msm7k.so from SuperOSR, and the keyboard backlight works now.
I used an application on my laptop called xUltimate to deodex both this ROM and Chacha 1.54 stock, and the only things that wouldn't deodex are the Lockscreen and Rosie :/
Camera appears right-way round/up if a 3rd party camera app is used
Additional bugs I've noticed after trying it out a bit again:
--GPS doesn't work - I'll mess around with gps libs tomorrow when I have a bit more time
--The FM radio app's graphics are messed up
For gps try also to use stock chacha libsensors (or something like that)
the right names for the files are:
/system/lib/hw/gps.chacha.so
/system/lib/hw/sensors.chacha.so
try using the one from SuperOSR.
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
TechMayhem said:
Is this ROM going to be official released anytime soon because I am working on a ROM from another HTC device aswell and was wondering if you needed any assistance on final touches?
TechMayhem
Click to expand...
Click to collapse
Tbh, I haven't done anything on this for a while because I started flashing CM7/SuperOSR.
From what I can remember, the following things wern't working:
-Lockscreen - Always in Portrait, won't rotate
-Rosie - Force-close loop, had to replace with an alternate launcher
-GPS - Icon doesn't appear in the status bar
-FM/Dailer/maybe others - Graphics messed up due to forced landscape resolution
That's all I managed to check before I got caught up in crackflashing XD
I am by no means a dev - all this was done by replacing files in a Wildfire S ROM with ones from SuperOSR/stock Chacha
Atomix86 said:
This would interest me greatly, as I really love the "standard" sense and was quite disappointed with the amount of white/light colours used in the ChaCha's version, and how it just doesn't seem to fit in very well at all with the HTC family. Would it be possible to use the Desire Z's rosie? As that supports landscape natively.
Click to expand...
Click to collapse
Precisely why I tried this in the first place - I wasn't expecting all this white, which doesn't make the Chacha feel like an HTC as much to me - I already tried the Desire Z's Rosie - while it did work, all the icons were huge (because of it being scaled for HDPI screens). Dunno about widgets.
Once I find it amongst all the crap I have on my laptop, I could upload it if anyone might have an idea how to fix what's left and to see what else is broken?
Ok, so I picked an Atrix 2 when I jumped ship from Sprint, and I have a question about making custom wallpapers for this device. If I remember correctly, having a qHD screen means the wallpaper size is 1080x960, but please correct me if I'm wrong. I'd like to create a custom static wallpaper out of smaller images so that when I change screens between the five available each picture is different. I can't seem to find the right resolution balance to make it happen, so I thought I'd see if anyone can point me in the right direction. I was under the assumption that if I used 216x960 pictures that it would work, but I'm having issues. Thanks in advance.
The resolution on the atrix2 is 540x960.
I'm aware of that, but if you pull a default wallpaper, you'll find it's 1080x960. I think I may have found the answer though. Apparently Android doesn't allow for separate wallpapers on each home screen using the default launcher. Only way I can find is using an app on the market. Kind of a clunky way to do it, but it's working so far.
Guys, I am a novice here and keep reading the posts on XDA frequently but posting a query first time.
I have installed pimp my ROM on my Galaxy R and changed the screen density which made me to utilize the real estate on my screen efficiently. The standard UI never helped me so opted for GO launcher and its working like a charm now inspite of a few delays.
The problem I am facing now is with the stock Email app now. Its not utilizing the new screen size and is cramped in a portion of it.
Can someone here help me to find out a way out or a tweak to make use of it. I know there are third party applications available which may help me but I really want to stick to the default app.
I have attached the screenshot which will help to understand the problem.
Thanks a lot!
I don't think it has layouts for another size and DPI, so this cannot be easily fixed.
Yes, But When you use PimpMyRom then you can save a zip file for reverting back as Update.zip.
BTW, as we always say, do have backup first while applying such changes in mobile.
Hello Devs,
To begin with I have HTC One V (using shpongle 4.2.2 rom) whose bottom ~50px (full width) are not working properly and to make it worse, somehow the rotation sensor is not working. So, I would like to restrict the display from original resolution 480x800 to say 480x750. I tried using apps like "Resolution NoMone" but many applications are crashing with that and it vertically centers the screen wasting 25px at the top.
Would modifying any system properties manually help me achieve what I want?
A simple grep shows /system/build.prop has "ro.device.screen_res=480x800". I tried changing this to 480x750 (taking ideas from this post) but it didn't work
I would really appreciate any help in this.
jatiniitdelhi said:
Hello Devs,
To begin with I have HTC One V (using shpongle 4.2.2 rom) whose bottom ~50px (full width) are not working properly and to make it worse, somehow the rotation sensor is not working. So, I would like to restrict the display from original resolution 480x800 to say 480x750. I tried using apps like "Resolution NoMone" but many applications are crashing with that and it vertically centers the screen wasting 25px at the top.
Would modifying any system properties manually help me achieve what I want?
A simple grep shows /system/build.prop has "ro.device.screen_res=480x800". I tried changing this to 480x750 (taking ideas from this post) but it didn't work
I would really appreciate any help in this.
Click to expand...
Click to collapse
Just so I'm clear on what you're actually trying to do, are you actually trying to just change your dpi? Or who suggested it to be a wise idea to try and change your resolution?
Keep in mind tinkering with your build.prop can be dangerous if you are not certain of what you're doing.
markbencze said:
Just so I'm clear on what you're actually trying to do, are you actually trying to just change your dpi? Or who suggested it to be a wise idea to try and change your resolution?
Keep in mind tinkering with your build.prop can be dangerous if you are not certain of what you're doing.
Click to expand...
Click to collapse
No I am not changing DPI. Keeping DPI same, I want to discard the bottom 50px of my screen and make the system behave as if the screen is of size 480x750px. Well I have passed through the phase of screwing up my mobile and recovering it (thanks to XDA) and I am willing to take all risks to fix this. Worst case I will need to flash the rom again and thats welcomed
OK well all I can suggest is you post your question here and wait for someone to give support
http://forum.xda-developers.com/showthread.php?t=2259645
Good luck
Thread closed