yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z General] colonel:
I have never got on with the Desire. The case is really plasticy, emphasized by the difference in plastic type between the back, the front and the base.

Also the 4 plastic keys on the front are really tacky.

the Desire Z is all aluminium and just looks so much better + those horrible keys are gone.

The HTC Legend was always the best looking HTC phone, I am hoping that the Desire Z carries on that tradition

(just a non-technical viewpoint :) )
[G2 and Desire Z General] steviewevie:
You realise that the discussion was about processors and overclocking, not about custom ROMs, right ? :rolleyes:
[G2 and Desire Z General] p3eps:
I'm in a similar predicament to the OP in that I can't make up my mind between the Desire and the Desire Z.

I've owned several HTC phones over the last few years which have all been Win Mo. A Touch Diamond, Touch HD... and currently an HD2.

Ever since swapping to the HD2 about a year ago (release day) I've found the onscreen keyboard terrible. I've had it sent back to HTC twice and since the second time it hasn't been quite so bad. Although it has a 1ghz processor, I still find Windows gets quite laggy unless I reboot quite frequently. Sometimes I can type sentances before they appear on screen.

Anyway - I've been playing with Android quite a bit on the HD2 lately. I was hanging on for WM7 - but since all the phones have no SD support and aren't backwards compatible with the WM6.5 apps - I feel I have no need to stick with WM.

I had an iPhone 4 on release for a week - but didn't really like it. I then decided a Desire was the phone for me - but I'd wait and see what WM7 offered. Now that I'm ready to buy, the Desire Z is almost available. My only concerns are the size and the 800mhz processor. Having the iPhone 4 for a week made me realise that the HD2 is massive and there is no need for a phone to be that size! If it wasn't for the terrible screen resolution, I'd have probably gone for a Wildfire - but I like watching films on my phone.

The slide out keyboard appeals as I send a lot of emails / SMS from my phone and a real keyboard is a better option than a virtual one.

I guess I'll wait a week or two until the Desire Z is reviewed properly and see what the reviewers say... and how the battery life is.
[G2 and Desire Z General] Soaa-:
Same architecture as the 1GHz Snapdragon or the A4. Better graphics than first gen Snapdragons as found in the Nexus One or the Desire. Can be massively overclocked (though it can vary). You shouldn't be disappointed with it.
[G2 and Desire Z General] setspeed:
I have the original Desire and although I'm waiting for the Z to come out because I want a keyboard, I am hesitant because:

1. No permanent root/custom kernals/ROMS yet.

My Desire now runs almost exactly how I want it to, a good balance of battery life, speed and features which would not have been available to me without root.

2. The reports of dodgy hinges on the G2. Hopefully this will be fixed by the time the Z is out, in fact let's hope this is the reason for the delay (although I doubt it, as I have heard that some UK retailers already have the Z in stock and just aren't allowed to sell them yet - indicating perhaps a software issue that HTC is trying to head off by developing an immediate OTA to broadcast once the phone is released)

3. No physical buttons on the front of the phone :-(

I know it looks slicker with capacitive keys, but I like the feedback of real buttons, and the ability to operate without really looking at the phone :-)

4. 576MB of RAM on Desire vs 512MB on the Z - wtf? It was widely acknowledged that the Desire was given a bit more RAM (over the very similar N1) to account for the extra overhead of Sense. Yet they've gone backwards and downgraded the amount of RAM to 512MB? And I bet the new Sense doesn't take any less but MORE resources!

Tbh, I have problems with browser pages dropping out of RAM when multitasking, and I find this a real annoyance. This is only going to be worse with less RAM.

Obviously, the Z is going to be better in many other ways (I hope) than my old Desire, but the above reasons do give me reason to pause, and wait for the initial early-adopter reports to come in before I dump my current Desire.

Things that don't bother me:

AMOLED/SLCD screen. It's still only a poxy 3.7" anyway. Would prefer a 4".

Camera. It's **** on my Desire and will be **** on the Z as well.

Audio performance - bothers me a little on my Desire that the speakers are weak as f*ck, and I don't expect that to improve with the Z.
[G2 and Desire Z General] p3eps:
Pahh... just pre-ordered one!

Also ordered the slip carry case (which looks like my HD2 one) and a couple of screen protectors. They said 'shipping first week in November' - but its changed so many times already I'm not holding my breath!
[Desire Themes and Apps] ilya.glants:
I installed igo my way and when I lunch it, it tells: "program application database cannot be found".

If I understand correctly I need to modify the sys.txt file, but I don't know what to change in it.

can anybody help me?
[Desire Themes and Apps] mendozinas:
U have to have Igo folder in SD.

Sent from my pocket using pen
[Desire Themes and Apps] ilya.glants:
i have the igo folder there..
[Desire Themes and Apps] rolfd:
Thread closed pending verification of possible warez discussion.

Edit: OK, I've taken advice on this and would suggest that the OP email or make contact with Technical Support from iGo website.

I'll leave this closed, and if there is any problem with it, please PM me.
[Touch Diamond, MDA Compact IV General] kizzem:
I don't know if i can put this topic in this box:p

i bought a Softbank diamond (X04HT) three months ago and successfully unlock it after then. but the thing happened like I lost my silver sim and i only have black sim of an iphone which i could borrow from friend. i did a lot of searches and found that there were some folks using iphone's black usim for there G1 or HD but when i inserted the usim into my X04HT, it failed to recognize or function with that sim. is there any way to get that work?

need help :(
[Touch Diamond, MDA Compact IV General] kizzem:
can't anybody help?
[Android Themes] webstar1:
so this is my first attempt on creating adw theme from the directions given here but here is the problem:

ok so to start off i have downloaded the tools in the android-sdk

set up eclipse and have all the resources the need.

i start a new android project and choose to start from existing source and choose the adw template, but then in the window on the top it says : '! The API level for the selected SDK target does not match the min SDK version'

Ignoring that caution and go ahead starting the project choosing Android 2.2 Build target.

Now the problem starts here, when i go in file explorer and navigate to src/x.x.x to rename the package to what i want it in the anroid manifest, it gives me errors in the main.java (the file inside src/x/x/x)

When i open the java file it has 'x' on some strings in the right area and has errors in Mains/Icon Adapter on 4 strings.

I try to rename the folders the readme tells me to, i right click on x.x.x and refractor>rename, write the name i want it to be but errors errors errors and thats only step 2 of the process! ive been trying for 2 hours now and cant get it to work, ill go insane, im new to developing so help will be appreciated a lot :o
[Android Themes] JAguirre1231:
Here's what I normally do:

1. Import the package from existing source (Ignore the caution, it's not important).

2. Open the Android Manifest.xml and change the package name )In my case I rename it com.jaguirre.blah).

3. Now click the 'src' folder. Right-click > Refractor > Rename > Name it the same thing that you put in the manifest.

4. Now open the main.java. At the top it should say something like:

package com.jaguirre.blah;

If it doesn't say that, make it say "package <package you put in manifest>;"

And then mine is normally fine after that.
[Android Themes] webstar1:
Thanks I'll try that, and I love your sense launcher, using it right now :D

Might make a theme based on it

EDIT: ok i looked into the strings and all of them had 1 thing in common is that they all had @overide before it started while other strings didnt, so i removed the @overide and voila, no errors! :D :D
[Android Themes] webstar1:
ok just tried, everything is there as it says but is main.java theres a cross by icon adapter under main and has a cross all on the get strings, whats wrong with this crap! :mad:
[Android Themes] docsparks:
bump. im in the same boat, trying to get any theme example to work, and having same issues.
[Android Themes] despotovski01:
Having the same problems:mad::confused::mad: . Can someone please help us, I spent much effort drawing my custom icons, and I'm not going to just give up yet.
[Galaxy S I9000 Q&A, Help & Troubleshooting] iScream^:
Hey.

I noticed, that the Omnia 7's and the SGS's specs are just the same, and I wonder if it could be possible to port WP7 to SGS. What do you think? I'm not a programmer, so I can't do anything for it, just aksing.
[Galaxy S I9000 Q&A, Help & Troubleshooting] t1mman:
Android = Open source, developper friendy os

Widnows = Closed source, licensed used.

altouch might be doable, since phone with WM6 got 6.5 (HTC Vogue or the likes), I assume if all the drivers are available it would be.

BTW: Question already asked and answered many time, you can always use the "search" fonction
[Galaxy S I9000 Q&A, Help & Troubleshooting] blackstoneuser5:
A custom bootloader to start up WP7 would need to be created. You can start Android on Windows Mobile hardware because of Haret.

It also looks like Microsoft standardized the 1GHz Qualcomm QSD8250 Snapdragon chips for all WP7 hardware at the moment (yes, even Samsung's devices, you'd think they'd want to use their own Hummingbird) in order to reduce fragmentation. The S5PC110 in our Galaxy S's uses completely different hardware drivers and compiling them to be compatible with WP7 would probably be quite an effort or impossible.

If at at all possible development would begin on QSD8250 handsets like the HTC Nexus One or Desire. Maybe we'll see more developments as WP7 begins trickling out but I have my doubts.
[Touch CDMA Android Development] scooter1556:
I'm sure most of you guys follow the Kaiser thread also but for those that don't this build should work fine on your vogues too so hope you don't mind me posting in both threads.
[Touch CDMA Android Development] margosmark:
Awesome thanks, always forget to check the Kaiser thread for builds. Will try out when i get a chance!
[Touch CDMA Android Development] Barogi44:
This build is awesome! :) Works great with the latest kernel for vogue. Super fast and has working facebook sync. :D
[Touch CDMA Android Development] Does_It_Matter:
Ditto!

Before flashing, I would recommend adding Rogue Tools though if you don't have market.

Very nice fast build though!

Using the latest 10-24-10 Vogue NBH 2.6.32 kernel.
[Touch CDMA Android Development] Prowess:
About the port

scooter1556,

I get force close when in settings-ADWLauncher-UI Settings-Desktop dots is checked (show/hide the nexus style pagination dots). When I uncheck it and the recheck it, go back to desktop and try the dots, the Launcher force closes.

Any fix for this? Appreciated for bringing this great port! Thanks,
[Touch CDMA Android Development] solarpolitiks:
Very nice. I am digging it right now but installing apps to the SD card seems to be causing problems (the card unmounts and the app does not appear in the drawer) Boot speed is fast which is great as well. I use the spare parts app just to tweak the END button behavior (Home, then sleep) If there is another way to do this I wouldn't need it
[Touch CDMA Android Development] scooter1556:
I didn't include it because i assume that most people use NBH editor to set there preferred settings in the kernel before flashing.

I get this as well, it could be my fault, i'll check the setting that may be causing it and get back to you. If it isn't that it is a bug with ADW at the moment which i'm sure will be sorted soon.

I also has the same installing apps to sd in fresh-froyo. Haven't tried in this port yet but i guess nothings changed. It is probably a kernel/driver issue which i will certainly look into because it will be a nice feature to have. There is also a script i can try to get this working. I will include spare parts in the next build :)
[Touch CDMA Android Development] solarpolitiks:
Cool, I always thought it was a nice handy feature in Spare Parts to change the button behavior so it's great it it'll be in the next build. Once again, great rom. The only thing I changed was ADW Launcher as I prefer LauncherPro much more
[Touch CDMA Android Development] superman9379:
On the http://it029000.massey.ac.nz/vogue/files/?C=M;O=D site, I only see the latest kernel as 10.9.10. Where did you get the 10.24.10 kernel?
[Touch CDMA Android Development] superman9379:
Nevermind, I googled for it. I didn't realize there were to places the kernel was being worked on. I forgot to thank the OP for posting this in the Vogue forum. I do not visit the Kaiser forum, so I would not haven known about it otherwise.
[Touch CDMA Android Development] crobs808:
update first post with screenshots please. gotta have those before i will even click a download link. thanks.
[Touch CDMA Android Development] WnG88:
+1 Screenshots please
[Touch CDMA Android Development] scooter1556:
Screenshots

Screenshots added to first post :D
[Touch CDMA Android Development] kinners:
The apps2sd problem looks to be due to an incorrect path in the /etc/vold.fstab file. I commented out the existing line and changed it to use the path /devices/platform/msm_sdcc.1/mmc_host/mmc0 which seems to be working after a reboot. I've moved some apps, and also installed neocore which I couldn't do earlier. This is with a NAND install and a single 4GB FAT32 partition on the sdcard, I don't know if any changes would need to be made for other setups.

[Changed contents of /etc/vold.fstab file]

#dev_mount sdcard /sdcard auto /sys/block/mmcblk0/device/../

dev_mount sdcard /sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
[Touch CDMA Android Development] scooter1556:
I was playing with app2sd a few days ago and found the same thing, the line i used was slightly different so as to not mess up sd installs but it does appear to work. Works perfectly as long as the app is compatible.
[Touch CDMA Android Development] Does_It_Matter:
Anyone running this on the Vogue?

Only NBH I'm able to get this working with is the 10-1-10 2.6.32 NBH file

Any other NBH locks up Windows Explorer and never allow it to connect

Anyone using some other kernel for this build?

------------

Edit: the 10-1-10 2.6.32 NBH doesn't crash explorer - but still won't connect to see USB drive

Not a major issue as I usually carry a SD -> MicroSD USB card reader just in case
[Touch CDMA Android Development] scooter1556:
I can't get the built in mass storage to work either, adb works fine but i can't get access to the card from my pc while it is still in the phone. I have never got this working properly on any build that i can think of.

EDIT:

I will be releasing a new build later today hopefully with fixes to ADW, Music app, mp3 and other codecs working, apps2sd working and i have got the build in sd mount working (under ubuntu works flawlessly, i'll try windows in a bit).
[Touch CDMA Android Development] know.patience:
I'm running your release 2 build with the 10-24-10 kernel and everything is works super smooth. The camera app does see the sd card in the phone and the gallery app isn't working for me either. How are the cam and gallery apps different from the other cm6 build?
[Touch CDMA Android Development] scooter1556:
RLS3 Available

Links to new build in the first post.
[Touch CDMA Android Development] scooter1556:
As it says in the first post, the build doesn't work with 2.6.25 kernels so that won't improve thing i'm afraid..
[Touch CDMA Android Development] aceoyame:
Yep, it definately won't. I've not tested myself but i'm pretty sure you'll have boot issues before you even get into the build.
[Touch CDMA Android Development] Lintegras:
Scoot, are there any files you want for us to grab to help troubleshoot this? I know in my case it's likely not a 3rd party program as I am in the midst of a "don't install anything" test for this exact issue. Wiped and reloaded all from scratch ~48-72 hours ago, only installs have been Fancy Widget + GMail / Youtube auto-updates, used GPS 3-4 times, no camera, a couple of hours of bluetooth, ~500 GMail contacts + ~160 Facebook contacts, battery drained once...
[Touch CDMA Android Development] aceoyame:
You may have not installed anything but that is some heavy usage. It sounds like its just a data corruption issue. On the kaiser side of things we are testing a kernel that lets yaffs handle everything with the NAND. If you read our kernel development thread you can find out more. I am testing it on my barebones 4.5 re-release build atm and will let you know how that goes.

By heavy usage I mean adding those contacts would require a lot of writes.
[Touch CDMA Android Development] highhacker:
Well so far .25 is working fine on vogue.seems a bit more responsive.I only reloaded 56 apps instead of 80+ Everything i use is working..camera gps voice commands weather youtube spb tv email messaging calls in and out..Been up for one day and have restarted three times just to make sure data corruption don't occur.so the 25 kernal that is not supposed to work on n a n d does indeed work good on this build.
[Touch CDMA Android Development] aceoyame:
That is very odd. The build was developed specifically for the .32 kernel. Maybe enough changes from the .32 branch made it into .25 and thats why its working.
[Touch CDMA Android Development] scooter1556:
Glad to hear that, unexpected but glad it's working for you :)
[Touch CDMA Android Development] Lintegras:
I'll admit I don't know or feign understanding the science behind why this matters but I feel this may be of importance: using this ROM + kernel WITHOUT data being on is as stable as can be with no reboots/freezes or any sorts despite my large number of contacts. It's not until a few days of use that the rebooting comes into play and even then, that can be stopped by turning off data. Don't know if it will but hope that information helps pinpoint the issue.
[Touch CDMA Android Development] aceoyame:
A random reboot might be caused by the RILD. We are not using the HTC one but a generic one. Now if you get corruption then thats a kernel issue and we would love to know about it especially if your using clemsyn's
[Touch CDMA Android Development] Lintegras:
This isn't a random reboot, this is a consistent soft (only goes back to the CM boot logo, not a phone reboot) reboot that occurs ~every 1 minute after booting if data is enabled. The reboot cycle happens after a few days of normal use (GPS + bluetooth almost always involved.) Once the cycle begins, the only resolution is using the phone without data enabled or reinstalling the system (using an /data backup & wiping Dalvik does no good.)

Edit: Since you have the theory of the RIL, I am swapping in the libHTCgeneric-RIL.so from here and seeing if that makes any differences.

Edit 2: Didn't fix the currently broken install. Since this is getting some attention, I will wipe - install the SD update - install the RIL update and report back in a week or so.
[Touch CDMA Android Development] aceoyame:
Have you tried turning off gps? I have had people on the kaiser forums report issues having it on, some have fixed by changing their radios. Others are still trying to figure out wtf is going on.
[Touch CDMA Android Development] Lintegras:
Turning off GPS but leaving on data does no good in my situation.
[Touch CDMA Android Development] wondercow:
Yaffs block is bad

I had been using RLS 4c for almost a month, and the longer I had it, the more frequently it would randomly reboot or freeze and force me to reboot it with the reset hole. It always scrolled the yaffs error that block 920 is bad when restarting.

This weekend, I updated to RLS 5a and my kernel with it. I hadn't had any freezes or reboots (except a couple I did on purpose) for about 48 hours until today, when I received an incoming Gmail and it froze on me (green LED blinking, screen off, phone unresponsive, pressing back button lights up send and end buttons). Now, when I reboot, I get the exact same yaffs error about block 920.

My question is: what exactly does it mean for a block to be "bad"? Does that mean that the data was corrupted (presumably during the freeze), or does that mean that my NAND chip is physically unreadable? It's a 3 year old phone, and it wouldn't be terribly surprising if it's near EOL, but I still want to nurse my Vogue along as much as possible.
[Touch CDMA Android Development] aceoyame:
Think of blocks as sectors. Yaffs is marking the block bad to be skipped and not used. For a build to get less stable over time is due to corruption which we have a fix for in the kaiser kernel thread. See page 7 for clemsyn's experimental kernel. The changes have not been commited to git yet so you have to get it there.

Bad blocks will not affect your phone in any way, my kaiser has about 10 bad blocks on it and it works just fine.
[Touch CDMA Android Development] l1q1d:
wikipedia helps you http://en.wikipedia.org/wiki/Flash_memory
[Touch CDMA Android Development] tiagoclc:
Camera isn't working with clemsyn's nbh from post on page 7 of "kernel and bugs only" thread.

FC after couple seconds.
[Touch CDMA Android Development] wondercow:
Thanks! I have been watching that kernel thread the last few days with interest--everyone there keeps talking about corruption, and I didn't want to clutter the kernel thread with clarifications, but how are people diagnosing their problems as corruption as opposed to any other sort of error? In my particular case, I have never had an application fail to load or throw an error--the phone just randomly reboots or freezes silently. Either way, I'll be installing that update soon because it sounds like it can only be a good thing.

Interesting, I had Googled for "yaffs bad blocks" but found only very technical documents that ended up confusing me. I didn't realize that "bad block" was a specific term for all flash memory and not just a vague descriptor of some sort of data problem.
[Touch CDMA Android Development] aceoyame:
Did you set it to a vogue rather than a kaiser?I don't have a vogue so I can't test myself, but it should work for the others.
[Touch CDMA Android Development] wondercow:
Did you apply the Camera Fix from page 1? It will FC if you don't run that update.
[Touch CDMA Android Development] pabloq629:
has anyone had an idea how to fix the random reboot cycle i love this rom is my fav it was working fine untill suddenly it started rebooting after a couple of days of use. anybody has any ideas i do belive am using the lates kernel with it got it from DZO...
[Touch CDMA Android Development] aceoyame:
im amazed you got it to work at all with dzo's kernel. That kernel is ancient compared to what is out now. Upgrade to the experimental kernel from klemsyn in the kaiser kernel development thread on page 7. That fixes the data corruption that has been had.
[Touch CDMA Android Development] lerxst_x:
Turning on the GPS radio stopped the random reboots with my Kaiser.
[Touch CDMA Android Development] signupstuffid:
I'm having the same reboot loop if data is on with my Vogue.

I reported this in the Kaiser Kernel thread, since I also needed to ask for a precompiled zimage and initrd.lzma, since I'm running from Haret, and can't use the .nbh posted over there.
[Touch CDMA Android Development] highhacker:
So far on vogue using. 25 kernal i have no reboots at all. I use gps every day.i use bluetooth file transfer also. The camera crapped out again and caused a hard boot bit came back ok so far just no camera. Try the 25 kernal from atools the only thing i checked was diable data on boot in options.overclocking to 466 with rouge.