[Q] Gingerbread dialer (phone) and pixel density 160 - Android Software/Hacking General [Developers Only]

Not sure if this is the best forum (please direct me to the most appropriate one if not), but I am using LeeDroid's GB ROM on HTC desire HD. All lovely expect that I use a pixel density of 160 (cos I like normal not huge icons ). Problem is that in GB this breaks the dialer - the numbers are all on top of each other. With the Froyo ROM it's fine. It's not a LeeDrOid problem. I did try posting over there but it's a more general GB issue.
Third party dialers do work fine, but I prefer the stock one. It's no big deal therefore, just a minor annoyance.
Anyone else noticed this?

Related

Mod for changing size of dialer on HD2??

Hi, I am currently using HD2 with an officall WWE ROM.
As things are working alright to me so far, I have no intention to get into the business of flashing just yet (not until a year of play around with it before i feel bored~! lol)
However I found the built-in dialer of this offical ROM abit too small, causing wrong dialling sometimes. I have aware that there are a few clever guys who worked on diallers with a much user-friendly interface (such as bigger keys for the number pad, idialer to name one), I found that most of them require to install the whole thing replacing the old, therefore losing the original layout from the offical rom (such as the call history + phonebook interface), which i am quite please with.
So I am here to ask, as I aware that the number pad on the offical dialler could be hidden and I though there must be some setting that limiting it to such a small size, is there any mod or registry setting that I could do or change to make the dialling pad/number pad (whichever why you call it) full screen size, while maintaining the ability to hide inside the offical dialling interface?
THX very much!
You might have better luck in the HD2 forum section. There's probably a thread on dialers there already.
Thanks for your reply, will also try over there~
cheers

Anyone interested in a near-working Wildfire S "port"?

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?

[REQ] HTC_IME mod for AOSP on qHD devices

I would love to offer any help I can to make this mod a reality. So far, I have gathered the following links that will surely be helpful in making this mod.
There are many users on the different individual rom threads, especially in senseless and aosp/cm9 roms, who are requesting to install HTC_IME (Touch Input), as it is the best input option around for some languages. I can attest firsthand to the fact that the Chinese handwriting input is by far the best handwriting input available for android (HTC is a Taiwanese company), so please don't suggest that everyone who wants htc_ime just go and download some other keyboard. They really did a good job with it, and people want to use it on AOSP!
The work done so far:
Jonas made the mod for gingerbread and devices with lower resolution screens. There is a lot of information about it here and links to downloads. It works on non-htc android devices.
http://www.linux-wizard.net/2011/02...c-ime-keyboard-under-a-non-htc-android-phone/
Original HTC_IME mod thread by jonas. The last page or so of the thread is full of posts of people saying please make this mod for ICS/qhd. So far, no one has done it...
http://forum.xda-developers.com/showthread.php?t=624416
This is a HTC_CIME mod for qvga screens. You can see in the screens that it works on MIUI and with multi-language support. This seems like a very good lead, as it may possibly work on our device if scaled up!
http://www.miui.com/thread-109295-1-1.html
A way to get touch input back into virtuous inqusition rom:
http://forum.xda-developers.com/showthread.php?t=1462460&highlight=with+libs
And finally, from our very own device theme forum, there is of course the package done by MichaelM. I think this is going to be our best shot at getting this working in aosp roms. I triead flashing the file "with libs" (should include multi-lang) on Vorbeth's rom, but it just continuously FCs with u select touch input (but touch input does show up!).
http://forum.xda-developers.com/showthread.php?t=1384640
As I said, I am willing to learn as much as I need to to help make this mod, I just need someone with a bit more experience than me to offer some help! Can someone please give even a brief overview of how to do this. Do we need to run logcats to find out lib dependencies? I'm sure the whole process can't be all that difficult (well, one can hope!).
Thank you in advance, sensation community!
p.s. if I forgot to give credit to anyone else who has done work on htc_ime mod please forgive me. Post the info in this thread if you find it so we can get this going!
2 things, 1, I would love to see this mod happen, I've gotten used to the ics keyboard but would still love the HTC one. 2, if possible, the latest HTC_IME keyboard would be best in my opinion because I love the swipe gestures that you can turn on and off without actually using the Swype keyboard because the Swype keyboard isn't something I am entirely fond of anymore
WyldOne91 said:
2 things, 1, I would love to see this mod happen, I've gotten used to the ics keyboard but would still love the HTC one. 2, if possible, the latest HTC_IME keyboard would be best in my opinion because I love the swipe gestures that you can turn on and off without actually using the Swype keyboard because the Swype keyboard isn't something I am entirely fond of anymore
Click to expand...
Click to collapse
latest is usually best! sounds good to me.
I would love to see that... I am starting to like CM9, but the keyboard just isn't good enough no matter which one I try... I will try gimpsta.com to create one and hopefully will have it working
good luck to you, sir!
BUMP! I really wanna see this happen too! But maybe we are looking at it from the wrong angle? I'm no dev, not in the slightest, but the HTC_IME that comes on the stock sensation is already qHD formatted. Would it be possible/easier to port jonasl's mods to the newer HTC_IME rather than trying to scale up the old one and fix it to run on ICS?
http://forum.xda-developers.com/showthread.php?t=1844512
a MOD for HTC IME on QHD resolution is out.
Now all we need to do is to put CIME back to it.

[Q] how to resize dialer when dpi is lowered from 240 to 192 (via build.prop)

how would i do this?
i know i had it fixed on my hd2 that the roms dpi was set to 192 by the dev and i changed it to 160, and the dialer fit.
The problem is the dialer looks small.
so does anyone or any themers know how to fix this? i'm accustomed to having android at the lower dpi and that is the only problem i encounter with the changed dpi.
help would be appreciated, thank you.
ooohhaaahh said:
how would i do this?
i know i had it fixed on my hd2 that the roms dpi was set to 192 by the dev and i changed it to 160, and the dialer fit.
The problem is the dialer looks small.
so does anyone or any themers know how to fix this? i'm accustomed to having android at the lower dpi and that is the only problem i encounter with the changed dpi.
help would be appreciated, thank you.
Click to expand...
Click to collapse
Ive been lookibg into this as well try ex dialer from market this is how i have.my phone :/
if you ain't first you're last
so i looked into it and whatever i did to do that was a fluke -.-
i was on an older version of pongster's rom and haptic feedback didn't work for the lockscreen, i then just upgraded to a newer release and haptic feedback worked, i had to reset my dpi back to 160 as the update put it to 192, and i had a full size dialer.
i have to see if i have a backup to on my computer and i'll restore it and if the dialer is there i'll tell pongster to take a look and see if he can re create results.
We don't have a pongster ROM. Do you have an SGS 4G SGH-T959V?
yes, i did it with my hd2, and from what i read he doesn't know how to fix the dialer issue either. so if i can find a backup that will restore the dialer to a phone, i'll contact him or his team and see how to replicate that.
then everyone can benifit

[Q] Stock Email App after increased dpi

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.

Categories

Resources