yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] syeager:
works well, mostly. still one of the best and fastest i have seen

First, let me say that this is a good build. Everything (or most everything) works, which has never happened with any other andriod i have tried.

I am using the sdcard install, not nand. As much as I do not like windows mobile, i cannot yet bring myself to abandon it until the bugs are worked out.

I would like to report the successes and defects for this android, that is if anyone is trying to resolve any remaining bugs/issues. Please let me know if I should be submitting these somewhere else.

What works:

internet

google maps

google voice search (much of the time)

google voice dial (although it is has serious problems with my daughter's name)

weather

imaps

movies

gps

bluetooth (although i have not tested using bluetooth to connect to my notebook)

most everything else.

What fails:

voice search works most of the time but sometimes it fails to initialize. this will persist and can either correct itself over time (after sleeping a while) or by restarting android.

audio for music player stops in the middle of a song. no error is reported. if i pause and play repeatedly, it seems to have no effect. pause and wait for several seconds, then play and it usually works.

audio was playing a song when i received a call and the phone locked up and had to be reset (by removing the battery)

audio was playing and i received a call. it paused the song but i could not hear the phone call (the person on the other end later told me they could hear me). i hung up the call and tried to call them back but still had no sound and could not hear them. i tried to resume the song, but there was still no sound. i restarted the phone and android, and all sound worked.

song playing again, when i received a call. tried to answer it but just after i pressed the talk button on the screen, and put the phone to my ear, i heard nothing. looking at the phone i realized it was restarting android. once restarted, everything seemed to work.

once tried to access the web, and the phone said i had no network available. phone service showed a couple of bars. no 3g icon. would not work even after several tries and several minutes. reboot resolved it.

occasionally, the screen is powered down and i press the menu button to wake it up. no results. i press it again, and still nothing. i press it again, and it actually responds. this happens intermittently but never twice in a row.

others say i missed phone calls that never appear on my history

voice text will download and install, but is not available on the keyboard.

Random and maybe not repeated bugs:

rebooted after trying voice search (has not happened again after first time)

rebooted after first try of google maps (has not happened again)

reboot after phone call (only once)

Again, this is a wonderful build and i am almost ready to rely on it. i look forward to hearing any thoughts or ideas on how to make it better.
[Touch CDMA Android Development] plemen:
Are you using a Vogue or a different phone?
[Touch CDMA Android Development] syeager:
yes vogue. sprint touch. i can get you the phone specifics, if you like.
[Touch CDMA Android Development] plemen:
New maps (4.0 with Buzz!) available here:

http://xdaforums.com/showthread.php?t=630887

Direct link to apk:

http://ul.to/1ofshq/maps4.0.0-brut4.apk
[Touch CDMA Android Development] plemen:
Very odd... I have been using the nand boot without any of those issues other than the wake up from sleep occasionally taking more than one press of the power button. What zimage/rootfs combo are you using?
[Touch CDMA Android Development] m4f1050:
I am testing this build, my APN no longer works (metropcs) I get "Web page not available" on browser (only thing that was working before now doesn't work.)

I tried the "fix" I used on Ion (setting proxy 10.223.2.4 instead of wap.meropcs.net) but no matter what I setup it doesn't want to turn on my "G" icon (data)

Any suggestions? (I managed to run the terminal and su, run vi and set key shortcut to ^[ so I could exit i mode in vi but how do I exit vi???) :D
[Touch CDMA Android Development] iseeka:
Hello

DZO managed to make a working nomorerootfs WIFI for polaris and I guess kaiser too

The rom has to load the correct module in order to work

Is it possible to have a WFI enable version for polaris?

thanks a lot
[Touch CDMA Android Development] plemen:
I haven't been able to find anybody who's had success running Donut with metropcs so this doesn't seem to be ROM specific; if you find any relevant information on what it takes to get metropcs going let me know and I can look into it.
[Touch CDMA Android Development] plemen:
The nomorootfs 253b is intended to be a universal build and already has support for loading wifi modules, etc. I only have a vogue so I'm relying on Polaris/Kaiser users to test and report back.
[Touch CDMA Android Development] m4f1050:
My observations:

1. The "G" icon and arrows light up like it's transfering. Metro uses PROXY, it's "wap.metropcs.net" port 3128, that DNS translation is 10.223.2.4

2. I tried all ways (wap.metropcs.net and port 3128, 10.223.2.4 and port 3128, wap.metropcs.net:3128 no port entry, 10.223.2.4:3128 no port entry) with no success. Wonder if compression has anything to do with it? Is there any way of setting more stuff on APN (via editing conf files or scripts?)

3. I checked resolv.conf and it's using 4.2.2.2 and 4.2.2.6 maybe setting these to mpcs dns might help? Don't know yet. I can SU and run VI even set shortcut to down volume to ^[ so I can exit I mode but I can't figure out how to save and/or exit VI.
[Touch CDMA Android Development] plemen:
To exit vi press Shift Z, Shift Z.

If you are going to modify any system files make sure you set system to rw. Like this from terminal:

1) su

2) mount -o remount,rw /system
[Touch CDMA Android Development] plemen:
The APN on my vogue shows one preset for my data connection. I can delete this and add new one, or just add a new one. Once I've added a new one, I can click on it to open it, and then click on any field (like APN) to edit it...

You have two preset APN's? That's interesting because I haven't had more than one in any build I've tried. Of course I don't have a Kaiser so I can only give you encouragement rather than actual testing :)

Is your data working ok? Are you able to connect with wifi?

Thanks for the compliment - I've using 253b with the "Bluest Day" theme and am very content... for now :)
[Touch CDMA Android Development] m4f1050:
Interesting.... Thank you. I was SUDOing to modify files but I never got to exit or save changes so it would probably have not worked anyways.
[Touch CDMA Android Development] adrenalynik:
Hello everyone, I explain how you could test the file. Sqlh for wifi Polaris? Thanks
[Touch CDMA Android Development] syeager:
Wow, do I feel ridiculous. Sorry for my confusion. My previous comments were completely off. I have been trying so many different builds, I have become confused which one I had installed. The comments were for a different build.

Your build here, one of the ones I wanted to use, is excellent. It is stable and I have never had a lockup or reboot. There are literally few problems. Here are the few I found:

when the system first starts up, the audio is unresponsive. i can play a song, or attempt to change a ringtone, but no sound. I put it to sleep, wait a while, restart it, and the audio works.

i wanted to install the voicespeechwithkeyboard app, but I cannot. It is not in the market, and I can neither copy it not install it. It also seems to be called the voice search, which is the same as the standard google voice search. I look forward to resolving this.

speaking of voice search, it works, mostly. Many times, the first few sounds are not recognized correctly. Most of it is recognized.

and voice search sometimes will not start, and i get a prompt that voice search is not available.

rotation. many times, when I want to switch the orientation, I long press the menu button, but nothing. If I put it to sleep, then restore it, it changes the orientation.

Wonderful build. These issues are minor and I am enjoying android. Keep up the good work.
[Touch CDMA Android Development] stickus:
.conf files in androidinstall.tar?

I've been trying to run this build with compcache and backing swap on the SD (to keep the home app in memory). I made the appropriate changes to the partitions and the appropriate file in /conf on my sd card. Not so much with the actually making is work yet. Are the .conf files now located the new androidinstall.tar?

I love this build I keep coming back to it. The ability to close the browser between sessions is great. Only gripe is that I love the way things look at 120 rather than the 113 or 110 that is set by default. Keep up the fantastic work tho!
[Touch CDMA Android Development] Reddog80p:
Installed this Rom to NAND last night works great and is very snappy. I ran neocore with volume on and got 21 fps and 23.8 without sound. The graphics and fluidity was the best I've seen on a android vogue Rom to date! I also downloaded armadillo roll and it too looks amazing without any graphics glitches. I've just noticed one thing. Just prior to getting to your android splash screen I got a message that reads.. "Init-prop messages size expect 128,etc" a few times but after a few reboots it seems to have gone away. I installed this clean after re-formatting my 8 gb sd. No partitions. I'm using 240x320 nbh from dzo's site dated 2-11-10. Great work keep it up.:)
[Touch CDMA Android Development] tatnai:
hope that helps
[Touch CDMA Android Development] egzthunder1:
Hey Plemen,

I wrote this in Myn's thread earlier today, but I figured I would ask you as well since someone else in this thread was asking about MetroPCS. I had the ability to at least surf the web with myn's build, but I couldn't with yours.

A few things that I noticed (after reading a bunch of forums for a few days):

*APN disappears if you try to change MNC (seems to happen even with "real" Androids)

*MNC for your build was 210 (no internet/apps working at all) and for myn's was 995 (internet works but no apps). The MNC that I have for MetroPCS (based on my EPST settings) is 00. I have read a few posts where it says to use 027, but since I cannot change it without erasing the APN, I cannot test if they work or not.

I have no clue whether this makes sense or not, but the only thing I know is that the APN that myn's Android is showing is wrong and that using a different one (your Android) actually made it worse. Can the APNs be "cooked in somehow?"

Anyways, let me know if this can give you some insight as to why in the world us Metropcs users cannot connect... I will test for you if you have any "fixes" (since I read about your Vogue's accident)
[Touch CDMA Android Development] mrkite38:
My MCC reads 310 (USA, good), MNC reads 995, like yours. From some simple googling it appears that 995 is some generic android internet apn, so I'm not sure where you'd look (adb shell getprop) for the 'real' values in question.

Look here:

http://en.wikipedia.org/wiki/Mobile_Network_Code

There's no MetroPCS in the list. There's no 995, either. I don't know anything about them, maybe you can find the correct number? 310/00 corresponds to nTelos. No clue who that is. Maybe try 260? That's the actual tmobile MNC.

Edit: Ok, I figured out where it is in the props.Run

getprop | grep -i operator

. gsm.sim.operator.numeric and gsm.operator.numeric are concatenated 'MCC'+'MNC'. So you could try

setprop gsm.sim.operator.numeric [i]value[/i]

and / or

setprop gsm.operator.numeric [i]value[/i]

and see what happens. :D
[Touch CDMA Android Development] Reddog80p:
I seen something about Metropcs MMS APN on another forum dunno if it will help you or if you have already seen it..

http://www.howardforums.com/showthread.php?t=1614355
[Touch CDMA Android Development] m4f1050:
Subscribed. Also looking for APN / MetroPCS solution.
[Touch CDMA Android Development] egzthunder1:
Hey mrkite!

I tried your idea yesterday night, but after changing the numbers with the setprop command, I decided to check if the changes had been applied... they came back being the same!! Also, I can't help to notice that this describes the operator as a GSM provider (I know this is pulled from the MyTouch), but our phones operate on CDMA networks. By the way, the MNC=00 that I posted earlier, I pulled that from the settings that I have in my EPST configuration in the WM section of my Vogue, so whether right or wrong, my device is using that and it connects fine to the internet (all apps including Google Maps)... which pushes me even more towards the idea that the GoogleApps in Android are somehow hard-coded to connect to whatever the hell they want, regardless of your internet connection status. Do you think that having it flashed to NAND will make a difference? Maybe since the options that you stated above cannot be changed (or at least I can't), maybe it can be cooked in the tar with all the correct carrier settings.
[Touch CDMA Android Development] plemen:
In this build I am enabling the market by setting the operator to T-Mobile via a script during bootup. Here is specifically what is being set:

setprop gsm.sim.operator.numeric 310260

setprop gsm.operator.numeric 310260

setprop gsm.sim.operator.iso-country us

setprop gsm.operator.iso-country us

If you want to change that, modify the script called /system/bin/marketenable.sh and reboot.

Let me know how this works out for you and I can take look at some options. This script is doing the same thing Market Enabler does when you select T-Mobile USA as the market source.
[Touch CDMA Android Development] dzo:
CDMA doesn't use APNs, the APN setting is only there so you can enter a password so it doesn't matter what the MNC is.

It may be that some carriers use a proxy, I don't think this is fully supported yet.
[Touch CDMA Android Development] mrkite38:
And dzo ftw as usual.
[Touch CDMA Android Development] egzthunder1:
I was afraid you would say that...

I believe I asked myn a few days ago how is it that the google apps connect to the google server, but he couldn't give me an answer. I asked particularly because it is entirely possible that MetroPCS is blocking whatever port the apps are trying to use to connect.

EDit: Upon a little search, I found that google Marketplace uses port 5228 to connect to their servers. Does this help

In fact, in order to establish an internet connection under WM with MetroPCS, you have to set up 4 different proxys

HTTP wap.metropcs.net:3128

WAP wap.metropcs.net:3128

SecureWap wap.metropcs.net:443

Socks wap.metropcs.net:3128

What still bothers me is that I can browse the net with this thing. This is the limit of my knowledge on the subject. I usually don't like to give up on these kind of things but unless you guys can come up with something, I am SoL.

Thanks for the insight there, dzo! :)
[Touch CDMA Android Development] egzthunder1:
Ok,

Here is the other thing I don't get. We all have Vogues here (except for a few people from the Polaris and Kaiser forums), which are CDMA devices. In order to set up internet on other CDMA networks such as Sprint and Verizon, you have to set up the connections as well, do you not? (and please correct me if I am wrong on this one). There is a config file or something somewhere inside this OS that will tell us how the hell these apps are trying to reach the Google servers and that they can do it with phones that are made for Sprint and Verizon, whose internet settings are stored elsewhere.

...my head hurts :confused:
[Touch CDMA Android Development] egzthunder1:
I didn't find marketenable.sh where you suggested (and something tells me that even if I had, I would not know what to do with it anyways :D)
[Touch CDMA Android Development] MrLogical:
Hi

After installing this version, I noticed that Google Maps is entirely missing. I did a clean install running from my SD card using HaRet. Can anyone explain why Maps is missing?
[Touch CDMA Android Development] tatnai:
download from market if in US, download from nav launcher if outside of US.
[Touch CDMA Android Development] m4f1050:
They made a GSM "Vogue" phone, which has WiFi. :( I wish they would have made the CDMA Vogue include WiFi, that would have been very very sweet!!! :) At least with Wifi you can connect to hotspots (like mickey-d or starbucks) if you are in desperate need of using Android at it's best...

I personally own the Vogue, Diamond (has wifi), Touch Pro (also wifi), Imagio flashed to MetroPCS (wifi) and Touch Pro2 (wifi as well...) I am about to give up on the Vogue and look for Diamond and/or other devices ports...
[Touch CDMA Android Development] acegolfer:
2 questions.

1. How do you rotate the screeen? Holding the power button doesn't always work.

2. How do you get back to home quickly? Holding the camera button doesn't work.
[Touch CDMA Android Development] tatnai:
except that the gsm "vogue" (the elf) does not have gps . . . between the two, i prefer gps.
[Touch CDMA Android Development] tatnai:
see "android buttons" in my faq, and also see the lanscape faq. see my sig.
[Touch CDMA Android Development] tatnai:
plemen,

do you know if this theme will work over your build? love the look, if the top bar is colored rather than transparent that would suck, but otherwise it looks sweet.
[Touch CDMA Android Development] m4f1050:
Yeah, I prefer GPS too but if GPS doesn't work (because you have Metro and APN doesn't provide internet to GoogleMaps) then you are stuck without it anyways... :(

I found the solution to the screen rotation. You need to disable the gyro rotation on settings, then you long press camera, then short press camera and it switches.
[Touch CDMA Android Development] acegolfer:
Thanks.

Unchecking "Orientation" fixed both issues.
[Touch CDMA Android Development] plemen:
Myn and I have both been porting different themes over - I've been meaning to check to see if his themes will work with my build. Honestly I wouldn't be surprised if they did - I'll try when I'm back at my computer in a few days - or if you try before me let me know and I won't bother porting the themes he's already ported and do new ones.
[Touch CDMA Android Development] tatnai:
a market observation:

last time I refreshed my market to get 320x480 apps back (using the create new data image method at 320x480, and logging into market, then reverting to my old data.img) was using your original "full market" version (remeber, the one that blocked google voice?). anyways, I think that was about two weeks ago. afterwards, I changed my build.prop to myn's 110, to get google voice working. since then, I my market has remained the FULL market (ALL resolution apps). this is the longest it has remained like this EVER, and I think it was the settings in that first build.prop that are responsible.

I know you changed some of the settings to fix the google voice setting. what I am wondering is, are the newer "full market" settings having the same effect for everyone (i.e. if you refresh your maket using by booting a new data.img in 320x480, then reverting back to your old data.img at 240x320, has your market remained showing apps like google listen, pandora, pdanet, the weather channel, dual mount sd widget - all apps that typically only show at res 320x480)?

this could be the fix - just boot your first data.img at 320x480, then change resolution, and that data.img is set for it's lifespan. the longest i've ever kept all res apps after a refresh before is 1 wk, when I really wasn't using the market that much. now i'm using it at least every day with these results, i'm pretty hopefull.

EDIT: we might just be able to provide a data.img backup that has already booted 320x480 with the prior settings and logged into market, then had the google data cleared. people could just start with that, and be set.
[Touch CDMA Android Development] plemen:
I'll test this out and see if I can replicate.
[Touch CDMA Android Development] sshark:
Good observation, Tatnai.

Few days ago, I changed my lcd_density from 120 to 113 on Msmison's Eclair build and promptly reverted back (may be within an hour) to 120, when using this build on 320 x 240.

So even after reverting back lcd density to 120, I still have all apps including Listen showing up in market.

Does this mean that just by changing lcd density, we can have full access to Market?
[Touch CDMA Android Development] tatnai:
to my knowledge and testing, lcd.density does not affect the market.
[Touch CDMA Android Development] plemen:
New base build up - all of the themes will work with this base as is. This is basically a clean-up build - this ROM is where I like it now. Post any issues you run into.

PS tatnai - I'll port that theme over soon - working on a completely seperate build has me distracted.
[Touch CDMA Android Development] krwilson:
Hey Plemen, thanks for updating this and hope to try it soon. BUT, I have downloaded it 3 times and it keeps coming up with this file is corrupt??!! Is this just me, can anyone else report on this, thanks.
[Touch CDMA Android Development] plemen:
The other tar file seems fine - I'll re-upload the sqsh?
[Touch CDMA Android Development] Prowess:
No it's the tar. Thanks,
[Touch CDMA Android Development] plemen:
Re-uploaded and tested tar file.
[Touch CDMA Android Development] krwilson:
Thanks, I should have been more specific, it was the tar I was downloading. It is good now, thanks again.
[Touch CDMA Android Development] catfishkempster:
Installed and runs great - I can't download Google Voice app...

Hello and thanks for the awesome build.

I have just one problem, and that is I cannot seem to be able to download the Google Voice app from the Market. Does anyone have any sugguestions?

Thanks in advance!

Catfishkempster
[Touch CDMA Android Development] catfishkempster:
Well, I found a solution easily enough: I searched for, found and downloaded the torrent for the Google Voice apk. Works great now!
[Touch CDMA Android Development] berardi:
Plemen! what resolution / density do you have on this? I think this is as close to perfect as it's going to get!

also what do you mean by improved task management?
[Touch CDMA Android Development] plemen:
I'm running at 320x240 with lcd.density at 110 - and thanks!
[Touch CDMA Android Development] incubus26jc:
i wouldnt mention that in here about warez
[Touch CDMA Android Development] berardi:
Hmm I seem to have broken my bluetooth - I tried to apply the change DZO recommended by changing the androidinstall.tar since my ADB doesn't work. Now when I try to turn on bluetooth, the blue LED starts blinking but the bluetooth never actually turns on.

is it not possible to update the sysinit.rc before installing?
[Touch CDMA Android Development] bri3d:
You can just update the sysinit.rc in the androidinstall.tar, then repack the tar. Or make yourself an androidupdate.tar containing only the new sysinit.rc in a system directory and install that.
[Touch CDMA Android Development] plemen:
I love the updates coming so quick from dzo! Well we're at revision "C" right now - I have version "D" with his mod which I'll post up now.
[Touch CDMA Android Development] berardi:
I tried doing it by the first method you mentioned, I'll try with the second method or just wait for Plemen's new version :) Thanks for the tip

Me too he said it would be a few weeks, and it happens the next day... you devs are too great :) thanks
[Touch CDMA Android Development] plemen:
253d is up!
[Touch CDMA Android Development] berardi:
awesome thanks so much plemen!
[Touch CDMA Android Development] tatnai:
keep coming back to your builds, plemen, it is just plain solid for me. thx for the update.

btw, as far as I can tell, you don't have the accelerometer faking code in; easy enough to add oneself, but if you are releasing another update, maybe add for the noobs ;)
[Touch CDMA Android Development] krwilson:
Just a small note, AlarmClock.apk is missing from this build............minor, but I do like the clock. I fixed it myself at my end but just commenting that it is not in the build 253d.