yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] incubus26jc:
i think its related to the later nbh's. If you flash an earlier nbh like 3-31, it might help you.
[Touch CDMA Android Development] take1mike:
thanks I flashed with the newest nbh and its working fine now.
[Touch CDMA Android Development] rawQ:
just wondering for an fyi before I update to rls5 I have wiped my phone with a previous release of android using nand, now that winmo is gone do I follow sqsh method? just looking for clarification before I try

*edit*lol nevermind
[Touch CDMA Android Development] roberto188:
Also noted:

In the menu screen if an application has a very long name for example baseball allstars 2009 Lite....the menu can't show the entire name...so it shows the text, an ellipses, and then a close bracket. Kinda funky looking.
[Touch CDMA Android Development] CyCLoBoT:
I copied the Adroid folder on the sdcard and ran haRET and when I click run, it just goes to a black screen and nothing else happens. I tried using both Default.txt files but nothing. Any idea what I'm doing wrong?
[Touch CDMA Android Development] cbaty08:
Right there with you..

I used my previous default for 320x240 though
[Touch CDMA Android Development] krwilson:
set cmdline "ppp.nostart=0 mddi.width=240 mddi.height=320 lcd.density=120 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=3 no_console_suspend"
boot

Unless you are a Sprint user, set the panel_type to 1 (3 is for Sprint, different type). This will fix the issue, I think, for I am learning too. This is in your Default Text.
[Touch CDMA Android Development] cbaty08:
Worked like a charm, thanks for the quickness!

For what it's worth, this is the best build of android I have tested out so far... REALLY, great job.
[Touch CDMA Android Development] myn:
Thanks for the kind words.

I should have mentioned in my original post that the default.txt included is configured for sprint users (panel set to 3). And if you are on another carrier (verizon) should change panel to 1. I have updated the first thread accordingly.

Sorry for the confusion.
[Touch CDMA Android Development] sparky101747:
has anyone tried this on nand yet? would like to try this one out.
[Touch CDMA Android Development] grktaurus83:
So just loaded this up and it's not only snappy, but looks fantastic as well...

Personal Issues:

============

1) Seems like the fonts are a bit blurry compared to other builds (using 240x320@120)... strange...

2) I despise rounded corners... feels like it wastes screen space and it doesn't work well with different parts of the UI (most notably is the contacts screen)

3) Not sure why the notification bar fonts are set to black, but I need to figure out how to change the font to white also... Time to dig through some of the Q&A's

4) Interesting that the battery drains from right to left... I think I prefer the opposite... totally a deal breaker [/sarcasm]

Other than my personal gripes, this is a great build... congrats!
[Touch CDMA Android Development] Psycoboy15:
Loading it as we speak. I'll let ya know
[Touch CDMA Android Development] Psycoboy15:
Using in Nand, the android.process.acore keeps force closing
[Touch CDMA Android Development] myn:
I should have been a little more considerate with my design decision to remove the titlebar clock (or to conseal it by making it the same color as the titlebar background (black)).

I think I made some assumptions about people using weather widgets that include a clock. I personally didn't like the redundancy but I completely see now that I should have included it. The next version will include a very visible white clock titlebar.

Here's what mine looks like:

In the mean time, if you want to change the clock titlebar color yourself you can use these 2 resources:

colorChange.jar v3.1: http://xdaforums.com/showthread.php?t=535630

Great Q&A On themes thread: http://xdaforums.com/showthread.php?t=468254

Sorry for any inconvenience.
[Touch CDMA Android Development] Psycoboy15:
I just reloaded again to nand and same issue android.process.acore keeps force closing. Which makes it so I can't use it. Every time it tries to load the desktop it crashes. I am using this in 240X320. I havn't tried the other resolution. I can if you think it make fix the issue.
[Touch CDMA Android Development] detour522:
myn, thank you for so responsive to the community! this is a great build and i am really enjoying it testing it out on my vogue right now.

everything is running fairly well but i still see some lags here and there compare to the droid-ion donut build. one thing that's really noticeable is when i try to launch the dialer. it sometimes takes about a full second for the dialer to appear.
[Touch CDMA Android Development] grktaurus83:
I remember being annoyed by the double display also. The best solution to this would be to be able to toggle the clock off (meaning the icons would all slide to the right where the clock usually is). I hate having a gaping space on the right hand side of the title bar more than having a double display, but maybe that's just me.

No need to apologize... It's your build so you don't need to accommodate everyone's personal request on style (though it would still be appreciated~).

Yet again, beautiful build.
[Touch CDMA Android Development] bblount:
Bluetooth?

does it work on this build? or only on 1.5?
[Touch CDMA Android Development] detour522:
has anyone tried using widgets? i just tried using the calendar widget and some free weather widgets and they are all having trouble displaying information.
[Touch CDMA Android Development] myn:
I am really unfamiliar with the nand boot process. I've never actually gave it a try :/. I really should get up to speed on this to accommodate NAND users.

To other ROM builders: Is there something special that needs to be built into these SQSH's to support nand?

Thanks
[Touch CDMA Android Development] Psycoboy15:
I got it working on Nand
[Touch CDMA Android Development] CyCLoBoT:
How did you do this? So far I have not been successful in flashing any ROMS to NAND.
[Touch CDMA Android Development] sparky101747:
what was the problem? just so i know when i try it.

Thanks
[Touch CDMA Android Development] tatnai:
320x480 is the wrong aspect ratio for our phones. pictures viewed and icons (well, everything) is slightly off-ratio. also a little blurry as a result. hero roms tend to require this res.

240x320 is the correct resolution for our screen; donut and up can use it properly (with cupcake, not all programs will function correctly). crystal clear. however, it gives problems with the market (AFAIK, this is the only downside). just like the tattoo phone, if you boot a new data.img in 240x320, you will not see all the apps in the market (google's server or something marks your account with the resolution you booted, and limits the apps to ones that have been marked as approved for the smaller resolution - search for pandora, pdanet, google listen, weather channel). if you first create your data.img using 320x480, and after logging into google services and market and the like, you then flash 240x320 and keep the same data file, and you are good to go. after a few days to a week or so of using the market regularly, it will somehow sense that you are at the smaller resolution again, and revert back. If you lose the full market again, you have to backup your data file, flash back to 320x480 and boot a fresh data.img. after signing into google services and entering the market, if you then delete the new data.img and revert back to your old one at 240x320, you have the full market back. tattoo roms require this res. NOTE: the market problem has been fixed, see here.

320x428 is something we used to use, right aspect ratio, but cuts off the bottom of the screen in some programs. not blurry. I don't think many people use it anymore, i could be wrong. it also has the market problem if used with donut and above, but not with cupcake of course.

bottom line: 320x480 if you don't mind a little bit of blurry and wrong aspect ratio, 240x320 if you want crystal clear and correct aspect ratio and don't mind messing with the market problem every once in a while.

lcd.density is a whole other discussion. . . suffice to say, for this rom if using 240x320 110 seems to work best (particulary with the dialer, and with text input in messaging), some people like 120 or in between. use 160 if using 320x480. smaller lcd.density means everything looks smaller on the screen (scales down).
[Touch CDMA Android Development] Carrick1973:
If you're on the vogue, try 240 x 320 nbh, but set your density to 110 instead of 120 (per my above post). The change in density was the perfect compromise for me. Set at 120, the icons were too large, but set at 110, they are just right, without being tiny like they are when the resolution is set to 320 x 480.
[Touch CDMA Android Development] berardi:
Ok I'll try with 7-zip when I get back home the windows standard zip is giving me corrupted message, same on Androzip. Thanks again!
[Touch CDMA Android Development] gila.monster:
I think what he is saying is that you need to right-click and 'save target as' then rename it from .zip to .tar
[Touch CDMA Android Development] berardi:
OOPS I thought I was supposed to unzip and then change the resulting file to .tar :)

Will try it as advised tonight when I get home... thanks guys :)
[Touch CDMA Android Development] anonymous13:
Thanks for the files - is there any way to update if my volume button is broken that you know of?
[Touch CDMA Android Development] gigermunit:
I see you fixed the bug I saw, nice release, running it currently, quite nice.
[Touch CDMA Android Development] detour522:
what exactly is not working for you?
[Touch CDMA Android Development] Carrick1973:
You can read through this thread starting here: http://xdaforums.com/showpost.php?p=5521914&postcount=122

The Kaiser and Nike users aren't able to use the volume button either and are figuring a way out around it.
[Touch CDMA Android Development] Carrick1973:
No, it is able to connect to the google servers and login, but after hitting the skip button on setting up my voicemail, it get's a F/C. The strange thing is I can see the messages behind the F/C message, but every time I open voice, it F/C's on me.
[Touch CDMA Android Development] detour522:
myn, this build is really by far the best build out there. i love it!

but... i do have one complaint. is it possible to display your contact's phone number when adding a "direct dial" link to the home screen? i have contacts with multiple numbers (work, cell and etc...) and the "direct dial" screen only shows me names without the numbers so i get multiple entries of the same contact name and i need to guess which one is the number i want to use. its not a deal breaker or anything but slightly annoying if you have multiple numbers associated with the contacts.

thx for listening to my request in advance!
[Touch CDMA Android Development] crackeyes:
This build is by far the best. I too do not have a Work email. Any one have the pk file for it
[Touch CDMA Android Development] myn:
Are you running the sqsh or tar?
[Touch CDMA Android Development] myn:
I just received a message from a great helping hand, mrkite38:

He's right ;)

Expect to see some device specific updates that change out the sysinit.rc tonight.
[Touch CDMA Android Development] mrkite38:
kaiser/polaris wifi

**SEE NEW POST HERE**

http://xdaforums.com/showpost.php?p=5542799&postcount=533
[Touch CDMA Android Development] myn:
Thank you :). I do really appreciate your kindness. I will take out my persevering wife who has put up with alot of my "I'm busy, gotta get this Android rom out" this weekend with your kind donation. Thanks again.
[Touch CDMA Android Development] myn:
Oh Sorry,

Please do post :)

I would love to know if this is the root cause.

Thanks.
[Touch CDMA Android Development] detour522:
i just assumed "work email" was never included... i am running the tar build.
[Touch CDMA Android Development] stopthebus:
Thanks for the update.

This is what I've have observed so far (running from SD TAR).

1. Weather on the Clock app does not work, Weather Widget works. Known Problem.

2. The Clock app graphic is chop off, landscape works a little better but still chop off.

3. Voice recognition in the Car Dock always go to web search.

4. Lost alarm when reboot (both icon and lock screen) even though it's set. Have to go into alarm, unchecked and checked the box again.

5. Lost animation effect and icon on the Android Beautiful Widget weather. Could be something else, just checking to see if it works for other folks.

Again Thanks for the hard work.
[Touch CDMA Android Development] ryomahino:
please can you post your file, for try.

Another questions:

Anyone using the system.sqsh in Haret Method can make work the bluetooth like the screenshots?
[Touch CDMA Android Development] sumedh_vsk:
wow so many skins.....:D:D:D...how are we supposed to make our minds decide which one to select .....:confused::confused::confused:.......lol....great work...
[Touch CDMA Android Development] LordXeth:
Very nice;-]

mfg LordSeth
[Touch CDMA Android Development] lgt2000:
I am attempting to download the SQSH package here but it does not seem to be working. Is there a mirror available?
[Touch CDMA Android Development] take1mike:
Is there anyway to change genie widget from transparent back to the black background?
[Touch CDMA Android Development] mrudzik:
Echange contacts and Calendar

What are you guys using to sync Exchange contacts and calendar data with Myn's Rom?
[Touch CDMA Android Development] b.mann:
Can anyone help me figure out what is causing my resolution to not fit my Vogue screen? I have flashed the vogue 240-320.nhb yet my dialer is cutoff and the apps on the homescreen overlap each other. Do I need a different base nbh for the Vogue?
[Touch CDMA Android Development] sadoway:
use roguetools and change your densitity to 110 first.

then reset your phone. hope that helps
[Touch CDMA Android Development] djnamit:
got it working but some probs...

hi

i use a niki100 (Dual Touch)

i got the android working and its nice n smooth but 2 probs.

1. how do i get internet to work? Im using Airtel in Indore (Madhya Pradesh) India

2. Very very frequently its gives me a message that screen locked. Press menu to unlock, where as there seems to be no particular button. No matter what i press it does not unlock the keypad.

frrequently the device gets locked in boot up..

help pls...

Cheers

Namit

PS: Just to tell u all im using the SQSH package install
[Touch CDMA Android Development] ThomasHW:
I keep getting a message saying "Phone storage space is getting low." I've uninstalled a ton of applications and it's still there.

How can I uninstall applications that came with myn's ROM (like work email, etc.)?
[Touch CDMA Android Development] b.mann:
That worked perfectly, thanks!
[Touch CDMA Android Development] Andrewwelton:
Anyone else randomly getting texts that are nothing but japanese characters?

Or is it just me :S

EDIT: It seems to happen when the screens on when I recieve the text.

EDIT 2: Nevermind, happens regardless... it does seem to happen on the longer texts though...
[Touch CDMA Android Development] jondixon:
I also have had this problem, but it seems to only come from 1 particular person. I had assumed it was their issue, is it mine?
[Touch CDMA Android Development] Jiggity Janx:
Someone speak up if they think I'm off track here, but I did find that I received that message a lot more frequently when I had swap and/or compcache enabled. Check in the new spare parts and try disabling those if you have them enabled.

If you do want to remove some of the default build apps, I found them using Root Explorer in the /system/app folder. May/may not have to clear your Dalvik cache after that... (?) I removed them from that folder as well just in case.

Forgive me if I'm off base, but trying to help as I feel I can.
[Touch CDMA Android Development] Andrewwelton:
I've gotten it from two people.

So honestly i dont know if its the build or them :S
[Touch CDMA Android Development] JM-PDA:
I've never received any texts with odd looking characters.
[Touch CDMA Android Development] Andrewwelton:
I wish I knew why it does it for me... Didnt do it on RLS4, and its seemingly random. Length doesnt matter, and having the screen on or off doesnt matter.

I really dont know whats causing it :S
[Touch CDMA Android Development] myn:
I've gotten some random IM spam here and there but never Japanese characters.
[Touch CDMA Android Development] adriandd:
I've been getting several texts like this as well.
[Touch CDMA Android Development] Outmannov:
This rom works well on my phone, but it still has a problem. The battery information shows it still has about 40% energy, but it will shutdown in several minutes. Are there some methods to fix this problem?:)
[Touch CDMA Android Development] dzo:
If you get a sms with strange chars open a console and type:

su

logcat -b radio > /sdcard/smslogcat

Then post the smslogcat file here (take out any phone numbers first) and I'll see what I can do. There are lots of different sms encodings possible and my code only deals with the most common.

It could be that the sms is actually an mms, mms isn't supported at all.
[Touch CDMA Android Development] my2sense:
app2sd

I'm just started reading about app2sd and wondering if anybody has successfully done it on this release yet? It looks like a great way to overcome the 256MB storage limit that I seem to have. I have a 1GB ext2 partition and have selected "data on ext2" but am quickly running out of room. thanks
[Touch CDMA Android Development] WnG88:
Anyone have a non-mediafire (public download type) site where I can download RLS5 again? At work and no access to these types of sites. Looking to go back to default theme / setup with the hopes of getting better battery life.

Thanks.
[Touch CDMA Android Development] slow88lx:
Wait until you get home?
[Touch CDMA Android Development] mikevillarroel:
RLS4

Message deleted.
[Touch CDMA Android Development] mrkite38:
or download from your phone?
[Touch CDMA Android Development] CasopoliS:
Switched to Release 5 with the default theme, 120 density, and with 500 mHz clock.

Runs snappy, decently well... but battery life is much worse. Not sure if its Release 5 or if its the over clocking.

Definite loss of battery life though.

EDIT: I went back to Rogue tools and it looks like 110 density and 400 mHz. I thought I changed it?? Does it snap back when you restart?
[Touch CDMA Android Development] rainmakerrc:
Work email sending issues?

Using RLS5 on a Sprint Touch. Very nice build! I really want to stick with this build, but I am having issues with Work Email. I can set up my exchange account just fine and can receive emails.

However, I cannot send mail from my exchange account from my phone. I type up an email, and send. No errors. The emails show up in the sent mail folder on my outlook at my desktop at work, but the emails never get to their destinations. For frame of reference, I have used incubus26jc's Eclair lite 2.1 build, and the email app there worked with my exchange account just fine (both receiving and sending mails).

Anybody have any similar issues. I don't know if it's a phone issue or an issue with the exchange server here at the office.

Thanks.
[Touch CDMA Android Development] dmx0:
Myn, I've got to tell you - I am really impressed with the work you've done on this build. I just installed Racing Thunder 2, which is a 3D racing game with what I estimate to be Playstation 2-quality graphics. To my astonishment, it runs really, really well on our 3 year old device. It obviously doesn't run as smoothly as it would on, say, an N1, but it runs at a very respectable level. I'm very surprised to see the vogue even load a game of this caliber, much less in a fully playable form and at a decent frame rate. Truly a testament to your work as well as how far along Vogue-Android has come thanks to the effort of members such as dzo, msmission, vilord, zenulator, and countless others. Thanks for bringing new life to my Vogue, guys (and helping to prolong my inevitable switch from SERO lol).
[Touch CDMA Android Development] shadoslayer:
First of all, fantastic build, great job Myn!

I do have a question though, I'm running it at 240x320 @ 120 density, and the first row of numbers in the dialer are mostly chopped off. Whats a good dialer I can use that wont chop the top?

Thanks

Shado
[Touch CDMA Android Development] Alex-V:
the warm donut is the only good working on polaris i think.....but have 2 small problems:

1. warms donut run with 110 dpi but any htc_ime [htc ezinput] (all i can find...about 6 versions) run with 120 dpi...and look wired with 110 if i change the system to 120 dpi...the dialer and so on is to big...any solutions for this..?? please

2. sometimes i can not charge under android...if i change back to wm all is ok...whats wrong...??

the rest of warm´s donut is very good stable and fast...

with kind regards Alex
[Touch CDMA Android Development] JM-PDA:
Good question!

I just checked mine and noticed the same.
[Touch CDMA Android Development] Alex-V:
if you change to 110 dpi...the dialer looks correct :)
[Touch CDMA Android Development] kalmenchia:
hi , i hv changed to density 110 but dialer still the same problem with 1st line chopped off. but SpellDial looks ok , but how to set it as the default dialer ?

(please note that i changed the default.txt , i did not apply the update http://download566.mediafire.com/mztkjdkqaotg/ji1azdni2my/androidupdate.tar )

But this a very good build for my polaris100 with all the features require for a day to day use for myself, well done.

Thanks.
[Touch CDMA Android Development] ericbond:
Overclocking

i was just wondering while looking into rogue tools, is there any negative "side effects" of overlocking?
[Touch CDMA Android Development] slow88lx:
It's not exactly time tested as far as wear on the processor or anything. But I've been running at 450-500 since he released the app and I have yet to notice a drawback. Maybe it kills the battery faster, but remember the phone underclocks itself when it is sleeping.
[Touch CDMA Android Development] Alex-V:
mmmhhh...don´t know sorry...maybe what you said...perhaps a new dialer... :)

i also have 2 little problems:

the warm donut is the only good working on polaris i think....

1. warms donut run with 110 dpi but any htc_ime [htc ezinput] (all i can find...about 6 versions) run with 120 dpi...and look wired with 110 if i change the system to 120 dpi...the dialer and so on is to big...any solutions for this..?? please

2. sometimes i can not charge under android...if i change back to wm all is ok...whats wrong...??

the rest of warm´s donut is very good stable and fast...

with kind regards Alex
[Touch CDMA Android Development] mrkite38:
Hey, myn - just curious, the installer supports gzipped tars for installs / updates... any reason no one's using them?
[Touch CDMA Android Development] luvtorev:
hey, just wanted to say that this is a great build and i have it running on my sprint vogue with no problems at all. I would like to know where I could find a dockrunner app for vogue?? Can anyone help me with it? Thank.
[Touch CDMA Android Development] myn:
Yeah that's a very very good point.

Next release I should gzip the tar. Should save people some transfer time to their device.
[Touch CDMA Android Development] dzo:
I tried this a long time ago and found that the busybox gzip was very slow. It may have changed but do some testing first.
[Touch CDMA Android Development] scottter:
I have the phone recognized by my comp(win7x64) using android.modaco.com/usbdrivers, but I don't get a mass storage device with either clicking mount when prompted, nor do I when using automount.

Any Ideas?
[Touch CDMA Android Development] Alex-V:
ok...

1. have anyone a other dialer...maybe

2. i only can charge if wifi is active...Strange.......have the wifi bt fix installed....anyone have a tip ...?

edit: if i end wifi it will also charge...but i must start it before

Kind regards...Alex