yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] samjam:
In the UK, Orange is selling the Motorola DEXT for 150.00 - if it's not locked to orange (I don't know) you might chose to buy online. It is Android 1.6 but I'm told there is an update to 2.1 (but you should check).

It's not the most modern phone, as far as I know it doesn't have a compass or accelerometers but it does have a physical keyboard.

Sam
[Touch CDMA Android Development] samjam:
I think this is the case. I'm wondering what is missing here that official android handsets have.

Sam
[Touch CDMA Android Development] dwmz:
I also have these wakeup-problems with white/black screen as described from some other users.

Sometimes I think this could be related to how much work the phone has to do in background, because this happens often to me when any background-tasks are running with display off (e.g. GPS-Tracking). Then the phone won't wake up.

But the task itself seems to be running.

Some days ago I did some GPS-Tracking with the phone in my pocket, so display was off. When I tried to wake it up the screen was white (or black? can't remember, sry).

But I didn't reset the phone, instead I went on on my way. Later I made a reset and looked at the recorded track.

The phone was tracking my way till the place I hit the reset-button. So it was definitely working after I noticed the not waking up screen.

Sometimes it even happens to me that it stays black after doing a reset with stylus. Then I have to remove the battery for some seconds. But most of the times the stylus is enough.
[Touch CDMA Android Development] flinx42:
Yes, I'm starting to think the same re background tasks, which I suppose includes widgets. My freezes have been very erratic in regards to how soon they happened from last time working.

In most cases after at least a couple hours, but at times also after just some minutes.

With my last hanger it was just about 15min and the phone was definitely not hot at the time, so I don't believe anymore it's due to (self-inflicted) overheating. So I'm ruling out the keyboard light on while closed and I guess it can't be CPU running at full tilt either. Maybe something with the process prioritization just goes wrong, but then I'd expect your GPS tracking to suffer from that.

Maybe it's simply the display driver that is not perfect in regards to wakeup sequence - regardless of panel type!

I've had a number of self-build PCs using various ATI graphics card, which did pretty much the same when I tried to wake them up from suspend i.e. noise and power light, but no picture. So I gave up using suspend on the PCs, which unfortunately isn't really an option with the mobiles I guess :)
[Touch CDMA Android Development] n2rjt:
I'm thinking it's the flush/sync on the way to sleeping that is missing.

At first, I thought that the death-in-sleep was due to SD Card being powered off when the system was trying to get to the /system partition. But if that were the case, NAND installs wouldn't be affected.
[Touch CDMA Android Development] Joe1981AL:
Ok after a few screwups I managed to make the correct build that seems stable at this point with cell location working.

I did edit userinit.sh because a new script added was not working properly. You can change userinit.sh line wiith default_network.sh to one of the following or comment it out:

http://www.multiupload.com/H776K4JUFR
[Touch CDMA Android Development] n2rjt:
Cell location working?!? Are you sure?
[Touch CDMA Android Development] -Arturo-:
Joel, we are talking about fresh froyo build, right? And the cell location is really working???
[Touch CDMA Android Development] Joe1981AL:
yes, its mentioned a few post back that it was updated in source but dzo didn't have time to compile, but may hold off on download that compile...
[Touch CDMA Android Development] Joe1981AL:
Yes, used "Antennas" from market to test it out while installed on sdcard,

also made sure wifi was off, had false hope once from wifi on gmaps

but thats before I changed default_network.sh setting in userinit.sh, now I get no data so trying something else to see what happens. I commented it out since so I don't see the error since I did have working data on my kaiser when the script was failing.

edit:

the uploaded file was fine, I had extracted it on my windows system made mods and repacked, it was late and I wasn't thinking about windows breaking the symlinks, but the uploaded one is straight off my linux system and is fine, I just downloaded it from site and installed to make sure :)
[Touch CDMA Android Development] n2rjt:
I was curious because I also rebuilt from the repos around the same time you did, and cell location doesn't work for me. I'm installing your build now, and kicking off a build-from-scratch on my netbook.
[Touch CDMA Android Development] alexinc:
its english only release... :(

cell-tower-id still not working for me!!! disabled gps. after activating location service, its still not asking for permission (like in cyanogen) and opening browser waiting for google determining your location wont show the excpected hint either. so still now cell tower id on fresh froyo i'd say. i did a clean install!!!
[Touch CDMA Android Development] samjam:
Is sleep mode controlled by user-space or kernel, do you know?
[Touch CDMA Android Development] McDogger:
I have installed Joe's Froyo compilation and cell tower not working. Maybe because, I didn't wipe data.
[Touch CDMA Android Development] -Arturo-:
N2rjt, any luck with cell tower location?
[Touch CDMA Android Development] Joe1981AL:
ok I got over excited, the LAC and CID are being returned properly now, but there is still a problem somewhere...

Antennas app returns proper location, but other google applications are not getting the location for some reason. But it is a step forward, and a fresh update :)
[Touch CDMA Android Development] -Arturo-:
Booooo Joel:) I was as excited as a little girl who just got her first barbie doll....such a disappointment. :) joel what is this antennas app that you have mentioned? Since it returns the location then we are probably just a step away from getting it to work with google apps.
[Touch CDMA Android Development] kallt_kaffe:
This problem is really weird. I wonder perhaps if the AOSP by default isn't built for integration with GoogleApps and NetworkLocation.apk is a Google App. I can't see that dzo has turned this off actively so perhaps it needs to be turned on before compiling.

What we might need to do is too look at other projects that use the AOSP source and compare their setups with ours (assuming network location works on their builds). A good place to start would be to have a look at the CyanogenMod project which also is based on AOSP. I'm bit short on time right now but that is the course I would take if I had time to look more into this right now.

EDIT: And one more thing to try that I have tried. Replace the build.prop with the one from the CM6 build. I haven't seen anything in it that I "feel" could be related but it could be worth a shot.
[Touch CDMA Android Development] Joe1981AL:
I believe he followed some online guides I've see to directly pull cell tower location from googles online api, some like this example:

http://www.anddev.org/poor_mans_gps_-_celltowerid_-_location_area_code_-lookup-t257.html

so we are getting the data, but an application or a setting is not letting location service contact the server and pull data

see attached screen of "Antennas" (can be downloaded in market).
[Touch CDMA Android Development] n2rjt:
Maybe we need to add these to device/htc/vogue/overlay/packages/apps/Phone/res/values/config.xml?

<!-- Component name of the service providing network location support. -->

<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>

<!-- Component name of the service providing geocoder API support. -->

<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>​

Building, but it will take a while on this slow netbook ;-)
[Touch CDMA Android Development] -Arturo-:
Fingers crossed.:)
[Touch CDMA Android Development] n2rjt:
Okay, so that was the wrong file. Core, not phone. Waiting...
[Touch CDMA Android Development] deadpig:
Fix for cell tower location seems to work

I just added a overlay/frameworks/base/core/res/res/values/config.xml with the mentioned changes and as far as i can see... cell tower location now works with google maps (checked that wifi is off, and gps is off... :) )

Git-patch created (http://android.orson.at/htc-kaiser/...e/004-fix_cell_tower_location_for_froyo.patch) and as soon as i finished this post sent to kallt_kaffe for inclusion into upstream git (androidhtc).

Big thanx to you (n2rjt) and Jr33 for the research and fix!

*oink*
[Touch CDMA Android Development] SuperJMN:
He grunted!! Oh mamma!
[Touch CDMA Android Development] deadpig:
Grunting and other piggy things

:) That's what pigs do *grunz* (Austrian (german speaking) dead pigs slang) :D

PS: I've put an androidupdate.tar with the cell tower location fix on my page (rebuild did change quite some files... so i included them all.. and the update now is bit more than 5,6MB sized). Maybe someone wanna try it (but i don't feel responsible for bricked mobiles, earthquakes, black holes and other things this update _might_ do to you (or other people)):

http://android.orson.at/htc-kaiser/...ocation_fix_for_fresh_froyo/androidupdate.tar

Plain patch for androidhtc_device-vogue:

http://android.orson.at/htc-kaiser/...e/004-fix_cell_tower_location_for_froyo.patch

*quiek*
[Touch CDMA Android Development] blahblah2000:
is this in addition to the rom you had posted earlier, or can we just update an existing rom like incubus's?
[Touch CDMA Android Development] deadpig:
Sorry... but i never published any ROM nor NBH or anything else like these :)

It's meant to be an update to dzo's Fresh Froyo build, with recent kernel.

I've build this update on basis of the origin-source of dzo+co which you can find in the first post of this thread (http://xdaforums.com/showpost.php?p=6942151&postcount=1)

As far as i know Incubus26Jc ROM and many other have very different setups and other fixes (and even other versions of android) included, so i would strongly suggest to NOT apply this update to anything other then 'Fresh Froyo' ROM.

If cell tower location is not working for you (and/or the ROM that you use) currently, better wait for an official update from 'your' ROM supplier (aka Incubus, cyanogenmod ports, and others)

Still... have a nice day/night :)
[Touch CDMA Android Development] kallt_kaffe:
Excellent work guys... it's in the repo now. :)
[Touch CDMA Android Development] -Arturo-:
christmas came early this year:)

Great work guys.

A small issue, after applying the patch android stopped recognizing my sd card. (I'm using Kalt's script which moves app folder to sd....could that be a problem?)
[Touch CDMA Android Development] akmalxxx:
cell tower doesn't work and i lost astro after the update.

(dzo's fresh froyo latest)
[Touch CDMA Android Development] alexinc:
not working for me either on latest fresh froyo... or i'm i getting any trouble applying 2g/3g-pin-fix after this update???

just applied the patch again after disabling pin... still no cell tower id. also confirmation-popups arent shown...
[Touch CDMA Android Development] -Arturo-:
Ok I think something is messing up the compcache script it's either cell location patch or Kalt's move apks to sd script. After restart my sd card is unrecognizable by the system with compcache enabled.

Of course cell location is working fine.
[Touch CDMA Android Development] averestefd:
Regarding this new update from patch and other questions..

Would this be meant strictly for vogue or alo for gsm kaiser/ and polaris? How is patch applied?

Does touch pro 2 cell location info play any role to figure out our devices since they have cdma or gsm?

Also about adhoc connections.. I had noticed szym.net on augentech forum under vogue... is this something someone has tried here?
[Touch CDMA Android Development] Joe1981AL:
I compiled after update to repo today, and it is working good this time in all applications :)

I did not install from the update, so not sure how well it works.
[Touch CDMA Android Development] endersm:
DZO, any chance of getting CONFIG_NETFILTER_XT_MATCH_STATE=y as well as the existence of /sys/devices/virtual/net/usb0 in the kernel for vogue? what needs to be done? how can I help?
[Touch CDMA Android Development] mrkite38:
I assume this would be for usbnet? We are lacking drivers ATM but that might change under the new kernel port.
[Touch CDMA Android Development] alexinc:
so could someone plz be so kind to upload a recent compilation (preferred multi-language ;) ), as dzo seems quite busy with working on the new kernel!? thx i.a.!!!
[Touch CDMA Android Development] Joe1981AL:
ah sure, just for you :)

http://www.multiupload.com/NI9MUYLDPI

(ok and for anyone else who wants it)

built from repo this morning, no changes made, not odexed...

I've setup an old laptop with broke screen as my compile machine, so its easy for me to repo and turn out a new build, now if I can just figure out how to pre-odex...
[Touch CDMA Android Development] kallt_kaffe:
Thanks, I've uploaded it to the usual place: http://sourceforge.net/projects/androidhtc/files/system-unodex-2010-08-14.tgz/download
[Touch CDMA Android Development] alexinc:
thx sooo much guys! :) getting a fresh polaris done now...
[Touch CDMA Android Development] carlitos36:
help

i install Foryo on a HTC Tilt on sd card but i am having the problem that gets very slow and some times its freezes is there a way can be fix??
[Touch CDMA Android Development] SuperJMN:
Thanks dzo, you totally rock. I think Vogue and the other similar phones would be dead if you didn't have made such a great progress.
[Touch CDMA Android Development] kallt_kaffe:
Uploaded an odex:ed version here: http://sourceforge.net/projects/androidhtc/files/system-odex-2010-08-14.tgz/download
[Touch CDMA Android Development] alexinc:
:) now there is only one more thing left missing in this beautiful fresh froyo... working facebook-account sync. i notice that it runs without any problems in cyanogen, but fresh froyo is still missing this feature, even after installing latest facebook 1.3.2! you can select adding a facebook account, but nothing will happen. and the possibility to sync after installing facebook and setting it up, is missing too. any ideas anyone? :)
[Touch CDMA Android Development] incubus26jc:
Can someone tell me what all has been changed in the repo since dzo's last release? I know cell tower location and some mdpi graphics. Anything else? Thanks

Does cell location work for the vogue or just kaiser and polaris?
[Touch CDMA Android Development] pentagramII:
- Better GSM signal reporting

- Fix for default network switching

- Fixed typo (whatever it is ;p)
[Touch CDMA Android Development] kallt_kaffe:
Cell tower location is just for GSM phones. But hold it just a little bit more. I'm about to upload a new version that has three updated Google Apps .apk's.

I found them in the CM6-DS thread that was just updated and the new Gmail app fits much better, the new VoiceSearch has VoiceActions and the new GenieWidget... well... no idea what's different but the size had changed.
[Touch CDMA Android Development] n2rjt:
Thanks! My netbook built me an english-only version, but it took overnight.

Out of curiosity, How did you odex?
[Touch CDMA Android Development] kallt_kaffe:
Oh, that's a secret voodoo ritual that involves sacrificing lambs. I can tell you but then I'll have to kill you( and bring you back as a zombie). ;)

.

.

.

.

But seriously, I have no idea how to do it automaticly like dzo does so I do it manually with a script dzo posted long ago and then I copy the odex:ed files to the SD-card and put them into the archive.

btw, here's the one with updated google apps: http://sourceforge.net/projects/and...yo-all-languages-odex-2010-08-15.tgz/download

A non-odexed one is on it's way...
[Touch CDMA Android Development] alexinc:
great to see, thx! if only the facebook-sync could be solved... searching the whole day already for an solution! hopefully it has nothing to do with identifiying our device to facebook, as it seems that cyanogen had to get in contact with app-developer for getting it to work!? does it work in incubus-version which is mostly based on fresh froyo?
[Touch CDMA Android Development] kallt_kaffe:
Try the things I suggested here: http://xdaforums.com/showthread.php?t=731188

It's just a guess but it could be worth trying.
[Touch CDMA Android Development] kallt_kaffe:
Here's a new unodexed version. Or actually it's the one Joe compiled but updated with the latest changes to the repo. It should be the same you would get if you recompiled it right now. http://sourceforge.net/projects/and...-all-languages-unodex-2010-08-15.tgz/download
[Touch CDMA Android Development] Barogi44:
Whats the difference between odexed and unodexed?
[Touch CDMA Android Development] incubus26jc:
Thanks man, i appreciate it. :)
[Touch CDMA Android Development] kallt_kaffe:
The odex:ed boots faster (first boot at least) and uses less space as it pre-uncompresses and optimizes the .dex files from the .apks. The only drawback is that if you change anything in the framwork, ALL apps will stop working. So if you want to make a build where you can release different themes as updates (where you modify graphics in the framework) you want it unodexed. So basicly the unodexed versions are for those who want to build upon it like Incubus and his Super Froyo release. If you want to more vanilla Fresh Froyo then you should go with the odex:ed version.

The speed after some use should be the same with both builds. The reason the unodexed version is slower in the beginning is that the dex files are uncompressed and stored in /data/dalvik-cache. Something that isn't needed on odex:ed apk's.
[Touch CDMA Android Development] Barogi44:
Ahh ok thankss :)
[Touch CDMA Android Development] Joe1981AL:
kk, with some research looks like a script "build/dexpreopt/dexpreopt.py" uses an emulator to create the odex files pull them out of emulator and attach put in build.

but still researching this :)
[Touch CDMA Android Development] bkrodgers:
Ahh, so CDMA Vogue users shouldn't expect the cell tower location to work? Is that the way it's always going to be, or is there hope for it working at some point?
[Touch CDMA Android Development] n2rjt:
Someone with a vogue needs to look into this. I think it's harder than it was for GSM, where the htcgeneric-ril.so gets the needed info. Searching other phone forums might help ... that's how I found the missing pieces for GSM.
[Touch CDMA Android Development] -Arturo-:
and new brut.all maps.
[Touch CDMA Android Development] loserskater:
With the new voice search, is it one with ldpi? because the one from the market only has hdpi and mdpi, so when you open it there's still part of it cut off. I talked about it here:

Here's a rough picture to help clarify
[Touch CDMA Android Development] -Arturo-:
Great tips i was just going to post this issue thanks for sorting it out.
[Touch CDMA Android Development] Joe1981AL:
dzo,

love this build, and have learned a bit just learning to compile it from repo and such. appreciate all of your hard work.

I've just went out and bought a AT&T Captivate, but I will be keeping my trusty kaiser around but on wifi only now.
[Touch CDMA Android Development] incubus26jc:
im not getting a lockscreen or long holding the back button isnt functioning with this build.
[Touch CDMA Android Development] dzo:
This is the script I use to odex:

rm out/target/product/vogue/obj/PACKAGING/systemimage_unopt_intermediates/system.img
ONE_SHOT_MAKEFILE=~/android/mydroid/build/tools/dexpreopt/Android.mk make -C ~/android/mydroid/ files
make
mkdir /tmp/system-odex
rm -rf /tmp/system-odex/system
cp -ra out/target/product/vogue/system /tmp/system-odex
dexpreopt.py --outsystemdir=/tmp/system-odex/system
for i in /tmp/system-odex/system/app/*.apk; do zipalign -f 4 $i /tmp/zip; mv /tmp/zip $i; done
tar -C /tmp/system-odex -czvf system.tgz system

It's a bit convoluted because the dexpreopt tool isn't build by default and it needs some stuff in the system image, I may have had to change other things but this should get you going.
[Touch CDMA Android Development] n2rjt:
Thanks, DZO, for the odexing commands.

I did it, installed it, and cleared the jalvik cache. Everything works except the "Earthquake" app I had installed from the market. It now crashes. I re-installed but it still crashes. I haven't found any other apps that crash now but worked before.

The new voice search needs the "down down down down left enter" dance to get started the first time, and it crashed once after that, but then ran just fine.
[Touch CDMA Android Development] kallt_kaffe:
With so many QVGA devices on the market it is surprising that Google releases a new VoiceSearch that doesn't take that into account. But with a little luck and the help of apktool we may be able to fix it.
[Touch CDMA Android Development] alexinc:
is it just me or doesnt gallery3d get installed properly? tried it manually using astro, but getting "app not installed" msg!?
[Touch CDMA Android Development] kallt_kaffe:
Hmm... the config.xml we modified to get network location running holds some more secrets. I looked at the dream-sapphire repo and they use the following:

<!--
List of regexpressions describing the interface (if any) that represent tetherable
USB interfaces. If the device doesn't want to support tething over USB this should
be empty. An example would be "usb.*"
-->
−
<string-array translatable="false" name="config_tether_usb_regexs">
<item>"usb0"</item>
</string-array>
−
<!--
Regex array of allowable upstream ifaces for tethering - for example if you want
tethering on a new interface called "foo2" add <item>"foo\\d"</item> to the array
-->
−
<string-array translatable="false" name="config_tether_upstream_regexs">
<item>"rmnet\\d"</item>
<item>"tiwlan\\d"</item>
</string-array>

This might enable USB and/or Wifi tethering on our Froyo. I know we have wifi tethering allready but we're not using the one that is supposed to come built in with Froyo.
[Touch CDMA Android Development] scooter1556:
Good find K_K.
[Touch CDMA Android Development] kallt_kaffe:
I've pushed these changes (and some other stuff) to the repo but I can't compile it myself at the moment but perhaps someone elso would like to give it a go?

EDIT: Pushed a new version that should be a bit more correct than the first attempt.
[Touch CDMA Android Development] n2rjt:
In the dev tools I disabled sleeping when usb connected. I haven't seen it die in its sleep since doing that.

Am having much more problem with apps thinking SD card is not installed. I boot from haret with partitioned SD card. Need to understand why apps think there is no card when it is still mounted as /sdcard. Any way to fix without rebooting?
[Touch CDMA Android Development] Joe1981AL:
Did yours just run correctly without any real mods? I tried it but it gave me error for "read only" file system. I modified dexpreopt.py to remount /system rw in the emulator and its running now..
[Touch CDMA Android Development] kallt_kaffe:
I just uploaded a freshly compiled build (english only) here: https://sourceforge.net/projects/androidhtc/files/

For the new VoiceSearch, just switch to landscape mode to be able to bypass the first dialogue.
[Touch CDMA Android Development] dertester123:
Hey i will try it now.

Somewere in the past you uploaded a nbh for polaris ( and the other devices).

Is there something newer/other that should go with froyo? I ask because i actually use polaimg-panel3-320-froyo-26-07-10.nbh from http://it029000.massey.ac.nz/vogue/files/?C=M;O=D.

But going with neocore i get really bad results and in the gpu overclocking thread dzo told me to look if im using the right nbg....