yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] karlosreza:
srry :D

HI yes i dont post any information about my device srry my device is a kaiser whith wm 6.1 oficial i never touch the operative system only update it to 6.1 and thnks for the answer "If it is the way that I did it, then despite that the Android installer tells you that this will erase you current system, that only goes for the previously installed Android that you have on the SD card, not the Windows" that was my question :D i think that will delete wm thnks for all :D
[Touch CDMA Android Development] Rondador:
Thanks for the suggestion, but the problem persists, i tried powering off, remove battery, hold power button, putting back the battery and power on, but the error do not go away.

But a disturbing fact(at least for me) is that when i power off and i plug in the charger the ambar lights first light on for about 5 seconds, lights off, a white flash on the screen and after a minute or so the boot animation appears followed by the android desktop(magical boot), and the touchscreen keeps no responding. ¿Does this happens to anybody also?

EDIT: The "magic boot" also happens when i simply poweroff the phone with the battery on it, after a couple a minutes. ¿Bad battery?
[Touch CDMA Android Development] flinx42:
No, that's the workaround for the problem that you can't charge the phone at all when it is switched off (as opposed to WM).

So as a "safety net" it switches the phone on, just in case the battery is empty, rather than have a totally dead phone that you can't charge as it's not running...

But this should only happen when you've got it on a charger.
[Touch CDMA Android Development] thoughtlesskyle:
if you don't have enough power to boot, if you atleast go into the bootloader you can charge from there
[Touch CDMA Android Development] arvinchugh:
no one replied to my questions? :confused::(
[Touch CDMA Android Development] despou:
If you're asking how to sync your messages, calendar, etc. there are lot of apps to do this. I personally use gmail for contacs syncing.

If you're trying to browse your sd card with pc, there is so called SDShare app. It's paid, but does the work.
[Touch CDMA Android Development] arvinchugh:
no i was talking bout sd card sync.. thanx for ur reply.. also question to adding sence ui and bit and other questions still remain.. also i recently started facing this probs.. phone rolls back to default settings.. installed apps get uninstalled after reboot of phone.. and battery suddenly drops and phone shut down.. (from 80%-15% and phone shuts down at 15%) after installing some app frm market.. on holding power button.. in phone options only shut down comes.. (sound and other option no longer comes).. even when phone wakes up no more lock screen.. :| i dono wat i did wrng.. if anyone have any solutions to this probs? wud be appreciated thanx..
[Touch CDMA Android Development] duansindo:
we need have a try。。。
[Touch CDMA Android Development] sergey1369:
Hello, looks like SD CARD mount/umount support is broken in fresh froyo.

Using SD-configuration.

part 1 - fat32

part 2 - system

part 3 - data

part 4 - swap (unused currently)

Settings->SD card &...->Unmount SD card

OK

Settings->SD card &...->Mount SD card

OK, for 3 seconds, than grayed out.

UPD. I guess all haret-based install have this problem. Can't install SVOX langpacks from Market until fixed.

Here is the fix (checked only on my HTC TyTN II).

Correct /etc/vold.fstab

*msm_sdcc.2 was used on october's 2.6.32 kernel.
[Touch CDMA Android Development] n2rjt:
Cell Tower Location?

Has anyone with GSM (Kaiser) had trouble recently with cell tower location? I build "Fresh Froyo" from the repo sources often, and about two days ago stopped being able to acquire location through the cell towers. This would not be a problem if you use the system androidinstall file provided by dzo, since his latest is older than when the problem occurred. I am looking through the logs trying to find what changed.
[Touch CDMA Android Development] thoughtlesskyle:
if you want to post those builds from like he did with fresh froyo in the kaiser forums i would love to do what incubus did
[Touch CDMA Android Development] n2rjt:
New build

I uploaded a build, since some things have changed in the repo over the past week or so. I don't know if anything actually makes a difference to us, but there are changes down in Dalvik and other low-level areas.

Since this is the first build I have uploaded, please let me know if it is annoyingly different from those that dzo uploads.

At first I thought that this update broke cell tower location on my Kaiser. But when I did a fresh install, it works just fine, so I am assuming that something had gotten clobbered on my phone.
[Touch CDMA Android Development] SuperJMN:
Hi n2rjt! thanks for the new build. It seems it's fast at least after the first boot, but I think that something is broken with Wifi: If DHCP is enabled, it tries to connect but it never gets an IP. It stays saying "Obtaining IP address from 'wifissid'". I forced the connection entering the connection data myself to avoid the use of DHCP. It connects, but it isn't able to resolve any address, and every app that use the network fails to connect. I double checked the DNS, network mask, gateway and IP: everything is OK.

By the way, the update that I apply to get wifi working for Polaris was working in every DZO release (and others like Not So Super Froyo).
[Touch CDMA Android Development] thoughtlesskyle:
thanks for uploading it man, do you think you could do all languages next time? if not is their any easy way to add them in without having to recompile it, other than that its awesome
[Touch CDMA Android Development] n2rjt:
That is interesting. Wifi works for me. I don't think a DHCP issue would be related to the kernel module. It should work the same on Polaris, Kaiser, or Vogue, right?

Oh, silly me! I originally put together my build script solely for myself, and I only speak English. Sorry, I will fix that.
[Touch CDMA Android Development] thoughtlesskyle:
i only speak english too but i know some people in the kaiser forums dont
[Touch CDMA Android Development] n2rjt:
The euro version is uploaded, and the all version is on its way.

I have been researching, and discovered that Android doesn't unmount /data /cache or /system at shutdown. That may be contributing to data corruption, especially with ext2 such as we use when we put data on sdcard.

Cyanogenmod does unmount all partitions at shutdown, by invoking a shutdown.sh script such as the one l1q1d contributed a while ago. I am downloading cyanogenmod current sources, and will do some exploring.

And, if anyone with GSM has trouble with geolocation, please let me know. Mine has been working only intermittently.
[Touch CDMA Android Development] alexinc:
wow, nice to see another one who seems to know what he's doing working on this beast! ;) thx i.a.! i know its not the main focus, but as you mentioned the cyanogen mode, could you plz try to search for the difference between our fresh froyo and cm related to facebook account sync? in cm its working for quite a while now, but i didnt find the solution, as just changing some strings in build.prop didnt work and switching to complete build.prop didnt work either... i was also playing around with switching between the accountsync.apk, framework, etc. but yet i always failed. :(
[Touch CDMA Android Development] thoughtlesskyle:
yea i have included l1q1d's shut down script in not so super froyo for a while

now, i just like being able to actually power down my phone without having to pull the battery
[Touch CDMA Android Development] SuperJMN:
I don't know why, but I did another fresh install a it went OK! Maybe a problem with permissions... uh :S

I'm testing it and it runs FAST, at least from now. Really good build! You're doing great, really.
[Touch CDMA Android Development] n2rjt:
I did nothing but build the repo dzo points to in the first post. I posted it because there was an update from Google.
[Touch CDMA Android Development] SuperJMN:
Running smooth so far and it's stable. I've made some call, browse Internet and synced like always, but it seems to be more somewhat faster than the latests build. Is it just me?
[Touch CDMA Android Development] Barogi44:
+1 speed seems a tad bit faster :)
[Touch CDMA Android Development] waterpolo:
SuperJMN,

1) did you try to connect pc with adb?

-> is use android-sync to sync my contacts with outlook, but it seems that this isn't working anymore with the latest kernel .32.

2) is wifi working without fix for Polaris?
[Touch CDMA Android Development] clemsyn:
Hi, I made an androidinstall.tar made from the Tmobile OTA 2.2 from G1 forum. It installed fine and boots up fine. It's very responsive but it doesn't have any wifi, cell, bluetooth and camera connection. No splash creen. Any help from devs would be appreciated. Thanks.

OK, got wifi working at the moment

Got cell working and looks like GPS is OK.

SD working, shut off working.

Camera working.

Seems like audio is an issue. A lot of crackling sound :)

I got everything working in Kaiser. Posted it on Kaiser Android thread
[Touch CDMA Android Development] guerchele:
I installed system-froyo-all-unodex-16-10-10_16.tgz using Haret and zImage (in /andboot) from xdaforums.com/showthread.php?t=724231 and everything worked fine except for the video recording which stops working all the time and no matter what I choose (data on nand, data on sdcard or data on data.img) during install, /data is always created on same partition /system is created in (I am using kaisimg-panel2-240x320-2.6.32-tilt-froyo-09-09-10_21.nbh flashed in NAND prior to installing fresh froyo).

I am quite sure I mixed many parts from many places (nbh, haret, zimage, androidinstall.tgz, etc). So what best way to flash system-froyo-all-unodex-16-10-10_16.tgz on nand and having data on sdcard partition, since my phone does not have much spare memory? Any tool to convert tgz to nbh? In case there is no way of converting, what nbh to flash (since I am getting error when I run haret under windows mobile) and which haret, initrd, zimage, etc to put together to androidinstall.tgz in /andboot folder?

--

spl-3.56.hard

radio 1.71.0.9
[Touch CDMA Android Development] thoughtlesskyle:
the video camera is a known issue, im just glad we have a camera at this point since we didnt have that for a while too
[Touch CDMA Android Development] n2rjt:
Is anyone else with Kaiser having trouble with cell-tower location service? It stopped working for me on 10/8. I have explored and found nothing I updated on that day that should have caused any problems. A few days ago it started working for a few hours, but then quit again. I see nothing helpful in logcat.

Looking for any clues or pointers. If it works for anyone, please let me know.

In "News and Weather" app, do you see your local weather without having to configure it? In maps, do you see your location without using GPS?
[Touch CDMA Android Development] samjam:
Doesn't work for me, but it's not been working for weeks (maybe months) for me.

Sam
[Touch CDMA Android Development] n2rjt:
Stopped working for me on October 8th. I don't see anything in the repo logs that was even close to related or that was even close to that date. Maybe Google changed something in their network? I was starting to debug that last night when my phone broke.

I know that the October 1st build made by dzo worked fine for geolocation, at last during the first week in October. Can somebody re-test it, to see if it still works today? Sorry but I can't.
[Touch CDMA Android Development] lerxst_x:
Still works for me, currently using l1qu1d's 10-19 nbh and the cyanogen mod 6.1 that was posted last night....on my tilt on tmobile usa.
[Touch CDMA Android Development] thoughtlesskyle:
the CM 6 builds are built off a differnt tree of the soruce if i remember right
[Touch CDMA Android Development] n2rjt:
Yes but that's still a good data point. Thanks.
[Touch CDMA Android Development] lerxst_x:
It was working in thoughtleskyles builds too. In fact I've never not had it work since sometime in august.
[Touch CDMA Android Development] solarpolitiks:
For some reason it says I am roaming on boot. I have always had this rom (and same version) working before with no problems but now I boot and am instantly roaming and data doesn't work? Should I just try a fresh download and reinstall?

EDIT: Nope I tried a different rom with the same results. An nbh problem maybe? I'll check.

EDIT2: Very strange... flashing a new nbh file and rom version changes nothing. I am pretty sure I am not really roaming as I have used my data connection in my apartment before

EDIT3: Seems to be a problem with my line on verizon xD
[Touch CDMA Android Development] samjam:
Done that, where does it dump the install image?

Do I tar up out/target/product/vogue ?

Although I note out/target/product/generic has more in it,

but:

$ file out/target/product/generic/system.img
out/target/product/generic/system.img: VMS Alpha executable

makes me wonder what sort of img it is.
[Touch CDMA Android Development] n2rjt:
I use this script to build:

. build/envsetup.sh

lunch us_vogue-userdebug

make

timestamp=`date -u +"%d-%m-%y_%H"`

tar -C out/target/product/vogue -czf ../system-froyo-en-unodex-$timestamp.tgz system

Change the lunch option and filename for euro or all languages.

Dzo also posted a script to odex the image, but I never use that.

My development machine is a litle Asus netbook, running Ubuntu 10.4.
[Touch CDMA Android Development] thoughtlesskyle:
how exactly do i set up the repo the google details are vague at best
[Touch CDMA Android Development] samjam:
See this page: http://source.android.com/source/download.html near the bottom for installing the repo tools.

Then follow the instructions on post one of this thread.
[Touch CDMA Android Development] ebautista:
Do you use the latest kernel from dzos kernel site? http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
[Touch CDMA Android Development] uncynd:
dzo, u are the man
[Touch CDMA Android Development] sparky101747:
Did you have bluetooth working in previous build, I can't seem to pair with handsfree. Any ideas?
[Touch CDMA Android Development] Barogi44:
Yeah i got it now :)
[Touch CDMA Android Development] plemen:
Good eye - this worked for me - using the latest build from dzo (30_06_15) I replaced the zero byte files in bin with the files from your RLS2 and data is up.

DZO - thanks for everything!! Having Froyo fully functional and stable (well, with 2 hours testing :D) on our devices is amazing - gallery app is amazing in itself. The stock camera works but the picture view screen gets funny lines through it after taking a picture - the picture taken is fine but the camera app shows funny lines after every picture. Restarting camera clears it up until the next picture is taken. I can live with it just fyi.
[Touch CDMA Android Development] dlepage:
This is a known issue with libcamera under Eclair. Since Dzo ported/recompiled Eclair libcamera to Froyo, it must be the same issue.
[Touch CDMA Android Development] odz:
Stock cam app still broken on kaiser =[ it works for a few seconds than FC.
[Touch CDMA Android Development] dzo:
This problem happens because I saved some memory by sharing the camera platform memory with the gpu memory. This works on donut because the camera app doesn't use the gpu.

I've changed the kernel by moving the cam platform memory towards the end of the gpu memory and this fixes it (on vogue anyway) because the cam only needs the first 1M of gpu1 memory.

Try an NBH from today.
[Touch CDMA Android Development] odz:
Wow the NBH from today offers dramatic improvement in speed on kaisers! i gotta say i was a bit disappointed when i flashed froyo and noticed everything was super slow. The NBH from today finally allows my tilt to run froyo at the speeds vogue users are getting. GREAT! Your the best dzo :=)

EDIT: CAM works with the NBH from today no more FC's but the distortion problems after u take a pic is still there.
[Touch CDMA Android Development] *M*:
New JIT gets ~1200 in caffeine mark vs stock ~400
[Touch CDMA Android Development] BottleB:
Holy ****tttt
[Touch CDMA Android Development] jin5:
i wonder if this froyo will benefit from Odex'ing?
[Touch CDMA Android Development] BottleB:
*M* is it the same JIT than incubusjc26's build?
[Touch CDMA Android Development] *M*:
incubus's build is this build with a few apks/fixes added so yes.

I had a similar reaction haha

I've tried but some of core apps get errors when they are odex'd and constantly FC
[Touch CDMA Android Development] dzo:
Here's a new build with all the languages and fonts added.

It also has an improved ril, this should work better on kaiser/polaris. On vogue you may have to change your apn setup because it now reports the t-mobile settings. This is what the donut ril was doing.

https://sourceforge.net/projects/androidhtc/files/system-froyo-01-07-10_12.tgz/download

I enabled live wallpapers but most of them need openGL 2.0 hardware which we don't have so they won't work.

I'm making a repo manifest so if people want to compile this themselves it won't be too hard.
[Touch CDMA Android Development] thoughtlesskyle:
i never had to change my APN in donut so i dont see it being an issue
[Touch CDMA Android Development] dlepage:
Camera noise when taking shots

I tried the latest (01-07-2010) zImage on Vogue but there is still an issue with noise when a picture is taken. And this kernel seems less stable to me. CAM preview usually stops working after 2 or 3 shots. Last time it happened, adb logcat was full of "W/AudioTrack( 141): obtainBuffer timed out (is the CPU pegged?)"

Anyone else noticed that the noise issue with the CAM isn't random? At least on my Vogue running VaniljEclair RLS6, the top part shows the current 'shot' but the bottom part is from the previous shot. On my end, it is systematic except for the first shot following a reboot. I see this behaviour with the latest kernel (01-07-2010) and the one shipped with VaniljEclair RLS6.

For this reason, I wouldn't rule out an issue with libcamera. It looks like a memcpy with wrong size and/or a timing issue (sensor still capturing?). Problem is, I don't know enough about the Android framework yet and I am totally lost with all these MemoryHeapBase, MemoryHeap, MemoryHeapPmem and MemoryEtc and can't find any quick link to doc about them. Maybe Android NDK ?!?!
[Touch CDMA Android Development] dzo:
Here's an odexed system with some google apps:

https://sourceforge.net/projects/androidhtc/files/system-froyo-01-07-10_18.tgz/download
[Touch CDMA Android Development] kallt_kaffe:
:) I odex:ed the old release yesterday and saw today that a new one was out and realized I needed to redo the whole thing, then scrolled down to find out you saved me the work.

Btw, I left my Kaiser in the charger with GPS Test running and with Eclair it ALWAYS turns the GPS after 4 hours or less (the GPS code is told to turn off the GPS by the operationg system for some strange reason) but now with Froyo it was still running when I got out of bed this morning.

btw, I've done some QVGA adjustments to DeskClock.apk and Music.apk and also resized bootanimation and Launcher2 wallpapers for QVGA. Would you like me to send them over? I suppose you would want the source .xml files for the QVGA adjustments?

EDIT: I'll mail it
[Touch CDMA Android Development] dzo:
Great, I've made a git repo for this sort of thing here:

http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/device-vogue.git;a=summary

Just put your xml files in the correct overlay directory and the build system will fix everything up.
[Touch CDMA Android Development] mrkite38:
You want to get the fresh froyo repo or set one up for yourself? Dzo put instructions for fresh froyo in the first post... I've built it, it's not hard.
[Touch CDMA Android Development] thoughtlesskyle:
so he already built the repo, so in order to build i just type those commands in to build it?

it sounds like it should be harder than that
[Touch CDMA Android Development] n2rjt:
To build Fresh Froyo

Prerequisites: Ubuntu, etc: http://source.android.com/source/download.html

Download the source files: As stated in Post #1:

Build them: as stated in post #1:

Create the non-odexed androidinstall.tgz:

ODex them (optional, and needs work) http://xdaforums.com/showthread.php?p=7689917&highlight=dexpreopt.py#post7689917

To periodically update, do "repo sync" and start at step 3.

Of course, you can tweak the build with just a text editor and the ability to modify a tar.gz.

Others like thoughtlesskyle can help with that, I don't do it.

To install and use without building, just go to the SourceForge link in the first post (http://sourceforge.net/projects/androidhtc/files/) and choose the recent one with the languages you want.
[Touch CDMA Android Development] samjam:
Thanks for the extra notes.

I've got my image building fine; now I'll be looking at the bootup and shutdown procedures to see where to stick the unmount (or remount-ro, sync)
[Touch CDMA Android Development] matcha20:
Geolocation is broken for me, i've tried clean installing three times now, and it just isn't working for me. Oddly enough, it WAS working for me in thoughtlesskyles latest NotSoSuper (I think rls 17), which is based off of your 10-16-10 build.

Also, NSS corrupts for me every time after a shutdown, requiring a clean install, whereas 10-16-10 Fresh Froyo, which I assume is without l!q!d's shutdown script, is rock solid. Dunno if it's just me who is experiencing atypical behavior or if this is a common issue.
[Touch CDMA Android Development] n2rjt:
The geolocation is strange. It stopped working for me on Oct 8, worked on the 16th, then stopped again. When I drove to the next county, it worked until I drove home. Two days ago it started working again. I think it is the network not our code.

Regarding corruption, I have seen that too. I dont think the shutdown script is called at shutdown. I have been busy at work but slowly I am experimenting in this area with no breakthrough yet.
[Touch CDMA Android Development] matcha20:
I don't know whether the wonky geolocation is a network issue. From what you describe, it definitely seems that way, but for me (I'm currently in India, atm) I have seen working geolocation on a friends phone who is using the same network as myself as well an android based phone (nexus1) while my geolocation is broken. Also, when I revert back to my safety setup (Kalt_Kaffes kaiser nbh [.25] with Fresh Froyo 08-26-10) the geolocation works just fine. To me it seems that it is most likely some change that occurred in the builds after 10-08. There also seems to be some way to activate it, because like I said it is working in Not So Super 17, which is based off of the 10-16-10 Fresh Froyo, I'm just don't possess the skill set to figure out how ;).

On a seperate note, is there anyway we could get the mods to take the vogue forum out of the legacy devices section, or perhaps merge it with the kaiser forum? I feel like condemning the whole forum to legacy devices while there is so much ongoing development is prematurely sounding the death knell...
[Touch CDMA Android Development] n2rjt:
Geolocation workaround

I have read that sometimes when the cell companies add a tower or upgrade to 3G or HSDPA, the Google Location Service has to learn about the new tower. If you enable GPS and get your location, Google Location Service can learn too. I have NOT found that to be the case, though. I enable GPS, get my location in Maps. Then I turn off the GPS, and maps does not know where I am anymore.

However, this works for me:

Menu -> Settings -> Wireless & networks -> Mobile Networks -> Use only 2G networks -> YES

Then, geolocation works. Maybe because 2G towers are older.

Please let me know whether it helps you.
[Touch CDMA Android Development] thoughtlesskyle:
i feel really dumb that i cant get building from source set up, i ran that whole long command on the google site and like nothing installed, and its not letting me repo sync

haha so if somebody wants to just upload system images like has been happening its going to keep me from going gray by the time im 23