yashsingh1/xdaforums huggingface dataset:
[Galaxy Spica General] deltree:
The issue faced by opening poster is the same faced by me, I just noticed this problem cuz this is the 3rd day on the spica and 1st battery run on the cyanogen froyo 8.1 battery went from 40 ish to 15 ish in less then 10 mins!
[Desire General] subharmonic:
Ok, sorry for the double post (I started another thread, but pred text screwed up the title which (for some reason?!?!?) I can't edit?).

Anyway, if I add a new contact to my phone as a Google contact, it won't save, or rather, it initially appears to save, but then for some reason is removed from the contacts list.

I'm also unsure as to when the problem originated, but I have a feeling it's been happening for at least the lat 6 weeks, but unless it's a new contact which will be used frequently, it won't be spotted for a while, which is shy int's only recently I've noticed the issue.

so, any help would be great - this is a very infuriating bug.

Edit: I should add - I have upgraded to Froyo (Tmobile OTA - initial german!?!?! release for UK market).

Cheers!
[Desire General] church473:
Go to people>menu>view and see if Google contacts are set to visible. maybe that's the issue
[Desire General] samsanchez88:
I actually have a similar problem i hope somebody can hel with; i have 2 google accounts, one work and one presonal and even though i can save contacts to both accounts, and both are set to sync contacts, i can only see the contacts of one of my accounts, the other just won't show. I have set the "view" settings in contacts to show eveything but still, the contacts from one of my accounts just won't show.....!

Is there any possibility there is some setting in my google account that is not allowing it to share the contacts with my phone??

Thanks in advance
[Desire General] samsanchez88:
I have found a solution that will probably work in the cases stated above: in your google account go to contacts, and move or copy the contact you want on your phone from "my contacts" to "starred in Android", that did the trick for me!!!

Best of luck!
[Desire General] subharmonic:
But the problem for me isn't adding contacts via a website - it's inputting them into my phone, and them staying there in the first place.

I don't know if it's random contacts that aren't storing because I've no idea how long the problem has actually been prevalent.

In People/Menu/View - I have SIM ticked (0), Google (364) ticked, Show auto Gmail contacts not ticked, Myphonebook (0) ticked, Phone (4) ticked (I'm not sure why I have 4 phone contacts as I don't recall entering any in as phone contacts), and Twitter (0) not ticked.

I've now ticked "show auto Gmail contacts".

I've just remembered something - I changed over from Googlemail to Gmail as my email address - could this be affecting things? Gmail addresses were only made available (allegedly) to UK users recently.

So, any thoughts on this people?

Cheers!
[Desire General] subharmonic:
Just synced my gmail version of my account to my phone (I think) and no change.

Anyone know if the UK gmail email addresses are .com, or .co.uk?

ie me@gmail.com, or me@gmail.co.uk?
[Desire General] subharmonic:
I've been on quite a comprehensive "google" and from what I've found, it sounds as though this problem has arisen from the Froyo update.

I have tried various things to fix it - dumping caches - exporting contacts to csv - clearing all contacts - syncing to clear - and then reimporting contacts into gmail, and the syncing again.

Again, this hasn't solved the problem...

Still at a loss.
[Desire General] GANJDROID:
I had mine changed from googlemail to gmail and it stayed as .com

Heard somewhere you can change it to .co.uk be that's not the default change.

Sent from my HTC Desire
[Desire General] subharmonic:
Solved the problem, but it took a factory reset to do it.

That being said, Froyo now seems a good deal quicker.

After reset, I had over 100 meg phone storage left (can't remember the exact number).

Any ideas what should be the phone storage on a just "cleaned" phone?

I've still got the dodgy german apps that I can't use on the phone, and these can't be installed from the phone.

What's the best idea?
[Hero CDMA Q&A, Help & Troubleshooting] bso44:
I've been informed that I can store apps on my sdcard since I'm running CM6. Is there an advantage to doing so over storing them on the internal memory? Would my phone run faster?
[Hero CDMA Q&A, Help & Troubleshooting] metal666fukhead:
i think it will actually make your apps load slower depending on what class your sd card is
[Hero CDMA Q&A, Help & Troubleshooting] ranger61878:
If you can keep them on your phone, you would want to do that.
[General Topics] azzarati:
hey guys.. just asking if you think the best buy product replacement plan is worth it when buying a new phone.. apparently if anything goes wrong.. u can just get a replacement? and there is no limit?? something is bound to go wrong in 3 years and i figure by then theere would be wayy better phones that cost around the same as the phone im buying now.. so lets say something goes wrong every year i would get a new phone every year.. just being cautious i gues.. ive never had a phone last me over like a year and a half.. and would hate to pay full price for the phone at that time since im signing a 3 year term..
[General Topics] azzarati:
any one? is it worth it?
[General Topics] labellee25:
They can be worth it for phons that are worth a lot but you have to read the fine print because most of the time what kills cell phones like dropping them and watter is not covered but the this. You don't want to pay 50% of the price of the phone ether. They can be usefull. My brand new Samsung Galaxy S is now dead and I have Bell and Bestbuy arguing who will replace it. I've had it for 29 Days. Best buy will only trade them befor 14 days but bell stated they have to take back DOA SGS's up to 60 days for a trade. If I would have had this plan, I would have my phone back allready.
[Captivate General] p4ranoid4ndroid:
how can i avoid being redirected to wap websites? i tried the about:debug command in the browser but didnt see the setting to set to desktop. Also tried dolphin HD and set the user agent to desktop but Im still being routed to wap websites when i want to access the full version.
[Captivate General] erezak:
1. Which APN are you using? Is it a WAP one or an Internet one?

2. Which sites?
[Captivate General] p4ranoid4ndroid:
Im not sure how to check my APN settings. Sites like southparkstudios.com, crackberry always loads as m.crackberry, and a few other sites. Mostly I'm just curious because with flash now I wanna get the full internet experience.
[Captivate General] alphadog00:
technically it is not WAP - that is even worse. You just want the full site, not the mobile version.

I would try another browser that lets you change the user-agent string. It has nothing to do with your APN settings; it is the web server looking at your user-agent string and saying "android - send over the mobile page".

BTW - the setting is in our browser:

about:debug

Settings->more->settings all the way at the bottom is UA settings (User agent) - you can change it to desktop or iphone.

All i get though is a force close, and you have to clear browser cache and data (manage apps) to get it working again.

Others have had luck with xScope Lite browser in getting full sites.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
This was the kernel thread but it is so full of question that it was renamed to Question and answer!

before ask search in the forum.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Guide to install:

http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)

http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)

If you have "install module error" please install the android update on sourceforge. Read more here:

http://xdaforums.com/showthread.php?t=848921
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time :-) Thanks for all your efforts.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
[Tilt, TyTN II, MDA Vario III Android Development] cnigro1279:
Here for testing...

Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please :-)
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Ok scratch that looks like the problem has been caused by having data on ext2 partition.
[Tilt, TyTN II, MDA Vario III Android Development] Rondador:
The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?
[Tilt, TyTN II, MDA Vario III Android Development] MTom:
Hi

the problem is I do not belong here

I tried several variants android

the Caller ID does not work

basic configuration of network settings, but it is not good

if you want to set up an error message is incorrect sim, and it is no longer a network

something that is not a solution?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.

I'm thinking two changes for battery code:

a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.

b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.
[Tilt, TyTN II, MDA Vario III Android Development] mt1976:
@L1q1d

This is a nice idea to make this thread for kaiser users.

Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.

Keep going on your nice work for kaiser
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.

Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.

I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.

About the 4th partition....you mean swap, right?

When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.

I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.

An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Bug: white screen, Android still alive

How I got a white screen:

AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.

I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.

Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.

Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.

That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.

Edit: can recover by using Fn- keypad right soft key.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Battery issues?

If anyone has battery issues, please open a terminal, and type this:

> dmesg | grep ds2746 > /sdcard/dmesg.log

and send the dmesg.log file.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] ndnesh:
Kernel Issues or Rom Specific?

I have been using Fresh froyo Latest release and the latest kernel by l1qu1d for almost 5 days now, and have tried many builds and many kernels before. Its working smoothly, though i do find an odd screen calibration issue that is irritating. The touch screen calibration settings get messed up and it does not recognize my touch correctly. If i touch somewhere, it recognizes as being touched somewhere else and i have to recalibrate every few hours.. Would appreciate if someone could provide some help in this and if this is rom specific or kernel specific.

I had not got this calibration error before, and i have searched through the forums but i couldnt find any reference to this error.

This is really annoying when i am trying to text with the onscreen keyboard.

Please advice.
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
Make sure you have the keyboard closed when you calibrate.

When you think you need re-calibrating, close the keyboard and do a calibrate test so that you get an idea of how far out things are getting.

Look for fluff for dirt stuck between the screen and the case around the screen.

A hook cut out of paper may be good at cleaning that.
[Tilt, TyTN II, MDA Vario III Android Development] ndnesh:
Thanks for the reply samjam! I have checked that, and have cleaned the dirt stuck between the screen and the case around the screen. I had completely ignored the fact that this could also be because of the dust! i have done that and yes the screen does seem to be more responsive and accurate.

I did do the tests few times and always it was a few mm above or below where i was touching the screen. Would this only be because of the dust or any other issue?

Edit: still facing the same issues :(
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
I had that this afternoon as well!

Have had to restore twice now over the 3 days I've been running the latest kernel/build.

I've also lost the Exchange account once or twice and one widget won't work anymore, since I had to do the first data restore.

Still not exactly what I'd call reliable :S

When it works, it's great though. Way better than WM6.x

My next phone won't be a WM one for sure!

So it's been great getting to experience Android, before deciding on the next unit to buy.

Thanks guys! keep trying! Maybe you'll find these last bugs in the end.
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
To be honest, I've not seen a problem through "nice" rebooting on the combo I'm running so far (liquid-10-24/thoughtlesskyle-lite-10-22) so far.

Only when I had to press reset, due to non-responsive unit, did I get filesystem problems.

Even if there are still issues with the shutdown itself and you fix them, the underlying problem of non-flushed writes is still there -> reset is still an issue

I've read that the filesystem in use with our unites is not a logging one. Such a logging FS would offer protection from data loss through reset. However for whatever reason it's not being used with our phones.

So what do all the real Android phones use then?

Or can NO Android phone ever be reset without the risk of (severe) data loss??
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
I've had the white screen lockup twice, usually after charging all night. I believe that unlocking then locking the sim door is the same as removing the battery. That is what I use to power off when locked up. Using the reset button has corrupted my /data many times but the battery/sim door does not. Maybe it is because I have the /data on ext2 partition or I'm just lucky.
[Tilt, TyTN II, MDA Vario III Android Development] obso:
Real android phones have proper nand memory drivers to work with the Linux kernels*.

*my best understanding of the cause of the data loss issues. Someone more knowledgeable correct me if I'm wrong.
[Tilt, TyTN II, MDA Vario III Android Development] Restorer:
My feelings exactly. The guys here have done an amazing job in developing this stuff. I know for sure now my next phone will be Android. And if they ever get these last bugs tracked down maybe I will save myself a few hundred quid and stick with my old Kaiser for a while yet :D.

But oooh I do like the look of that Desire HD :D. I wonder if in 3 or 4 years time we will be looking at ways of eeking another few years out of that :).
[Tilt, TyTN II, MDA Vario III Android Development] ndnesh:
New Kernel?

We got a new kernel?

Sorry for asking a noob question, how do i look at the changes that the new kernel has in the git?
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
This git tree contains the binary NBH uploads.

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

This git tree contains the source commits, and the shortlog or summary explain what was done.

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

(See the HEAD's at the bottom of the page)

I *THINK* this is the HEAD used for us:

http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
[Tilt, TyTN II, MDA Vario III Android Development] samjam:
However the mention of the "logging yaffs" seems relevant. Either we are missing a regular periodic sync (which only merely shortens the window) or we are not supporting some file system transactional API (so the applications take a strong role in avoiding corruption) or maybe, as said, yaffs logging isn't working
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
Or even Desire Z :D
[Tilt, TyTN II, MDA Vario III Android Development] flinx42:
Hmm, but unless these real phones use proper nand memory drivers that are implemented in hardware, I do not see why such a proper driver can't be ported to the Kaiser.

If it isn't a lack of whatever hardware component, then what else makes the Kaiser unable to use nand memory the way that real android phones do?
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
It isnt that its impossible its just that we don't know how to get it working proper yet.
[Tilt, TyTN II, MDA Vario III Android Development] ndnesh:
Boost in development?

Hi all,

First of all, a heartfelt, warm thanks to all the devs who made and continue to make android possible on our "legacy" devices.

I have been using android on my kaiser since 8 months now, been watching all the spaces and have downloaded around 70 builds(various versions). For the past two months i have been using fresh froyo and just today have tried the Cyanogen mod 6.1 by scoot. Its really good, and the various options in the settings are truely wonderful! Awesome stuff!!

Anyways, what i wanted to share with you is that HTC just released the kernel source codes for many of its devices. I do not know much about this, but there are kernels there ranging from desire HD to HTC Magic.

Here is the link:

http://developer.htc.com/

Cheers! and hoping that this source code provides us the missing pieces we need to fix our devices!!
[Tilt, TyTN II, MDA Vario III Android Development] ndnesh:
Agreed! We just need to figure out how to get it working :):)
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
The probably won't help too much but it would be good to take a look at the G1's kernel given that our devices are very similar.