yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] SilentBob:
I had been eagerly following WP7 news in the run up to release, and despite there being several areas that narked me, I really liked the look of it. Anyway, those areas that were/are a problem will no doubt get dealt with in future updates.

So, I am now pretty much at the end of my current contract and was getting quite excited about the prospect of getting a shiny new WP7. I have been into the O2 shop with my wife to have a play with the HD7 (they are the only shop that have real working handsets for you to try). We BOTH love it. And by it, I mean both the WP7 OS and the device itself. This is where the problems begin... network exclusivity.

O2 have the HD7 (16GB).

Orange have the HTC Mozart (8GB)

Vodaphone have the HTC Trophy (8GB)

and I believe that the Samsung Omnia 7 (8GB) & LG Optimus 7 (8GB) are available on various networks.

I have had HTC Windows based phones since the original SPV. I both really like & trust HTC devices. The Samsung looks and feels cheap & tacky. The LG is just plain ugly. The HTC Trophy & Mozart only have 8GB storage and are both too small for what we want. So the only option for us is the HD7 and we both love it!!!

So, no problem then? Think again. O2 exclusivity is the problem. I cannot use either O2 or Vodafone as both networks have sub-standard coverage where I live. To the extent where it is a real no go. On top of that, as there is no competition for this handset, O2 just do not offer a good tariff/ handset price deal. I will not spend over £35 a month, but may consider spending a bit (but not a small fortune) on the handset. I must also have reasonable data allowance. In fact, WP7 demands this too. 500MB? Just doesn't cut it anymore.

Long story short, as a result I now have to turn to Android and the HTC Desire HD, which is available from all networks on some really competitive deals. This is a real blow considering how much I have been looking forward to WP7. :(

I just hope that there aren't hundreds of thousands of other people who have had to make the same decision. I hope that a couple of years down the line that WP7 is going strong & that there will be a good variety of handsets available on all networks, so as to give the consumer real choice, and to allow me to finally get the WP7 handset I want on the network of my choice.
[Windows Phone 7 General] MartyLK:
Actually, from my experience with DesireHD on my HD2, I would say you are coming out of it on top by going with the DesireHD. This is an Android version like no other. It's gorgeous and offers excellent customization features like the skins and such. Plus the actual DesireHD hardware is also purely gorgeous.

You may think you are losing by not being able to go with WP7, but I see it the other way. You get so many features with DesireHD that WP7 doesn't have. And if the actual DesireHD UI is anything like the HD2 DesireHD ROM, the UI is silky smooth and a luscious. It's as smooth as WP7.
[Windows Phone 7 General] brummiesteven:
I know this is not what you want to hear but the HD7 is only £360 on Pay&Go I bought it on pay & go and now use my T-Mobile sim in it.

You'd be looking at a £30 a month contract anyway so that's the equivalent of 1 year so you'd save £360 which can be used to get a cheap sim only deal.
[Windows Phone 7 General] paperclips:
No... it isn't. Don't get me wrong though, the Desire HD is a very capable phone and with Sense 2.5 it provides what I think is the best Android experience but it isn't quite as smooth as WP7 or iOS yet.
[Windows Phone 7 General] MartyLK:
Like I said, I don't know about the actual DesireHD, but my HD2 with DesireHD is. And I do have an HD7 to compare it to.
[Windows Phone 7 General] SilentBob:
TBH, I have been keeping an eye on what's happening with Android too. You know, just in case WP7 completely failed. I understand it is better for customisation (which I am used to on WM). However, I get the feeling that with WP7 I wouldn't feel the need to customise beyond wallpaper & ringtone. It looks like it just works so well.

I realise how similar the hardware of the HD7 & Desire HD are, hence why this seems to be the sensible alternative. The DHD even has some advantage, such as Alu-body & SLCD screen.

It seems that (unless you are loaded) there always has to be compromise. In this case:

- Handset/hardware

- Network (and therefore service)

- O/S

And unfortunately it seems that O/S is the one to give. Although, as you said, I am sure it won't be a disappointing experience.
[Windows Phone 7 General] SilentBob:
I had considered this...

but only for a couple of seconds. :)

Unfortunately I do not have the £700+ needed to buy one for me & one for the wife outright. Hence why there always has to be compromise somewhere.
[Windows Phone 7 General] SilentBob:
Perhaps what it needs is a custom ROM to get the best experience? But, despite not having any experience, I certainly feel that HTC are doing some good stuff with Android. Just as they did with WM. It is a shame though, 'cos the short while I spent playing with WP7 was pretty amazing.

Damned network exclusives! That's exactly why I ended up back on Orange (for the original HTC Touch HD). :(
[Windows Phone 7 General] brummiesteven:
Another option is the HTC Mozart. Like the HD7, the SD Card in the Mozart can be replaced.
[Windows Phone 7 General] SilentBob:
Yeah, I have looked at that. It is good looking & very well built, but...

- After trying out the HD7, the screen just seems too small (hard to think that 2.8" was the norm just a couple of years back).

- The storage upgrade would immediately invalidate the warranty.
[Windows Phone 7 General] brummiesteven:
I would assume it is possible, albeit tricky, to do it without voiding the warranty. If it broke you'd just pop back the original SD card in.

It does suck, there should be more with 16gb storage or even 32gb. The Samsung Omnia 7 is an awesome phone btw and far better than any of the HTCs (although it's 8gb anyway).

I don't know what else to suggest though :( when is your contract up? If it's not for a while you could wait a bit for the Dell Venue Pro. 4" screen, Micro SD Card slot, Gorilla Glass. Shouldn't be too long for that.

Edit: Turns out you don't have to wait, buymobilephones has it http://www.buymobilephones.net/mobile-phones/Dell/Dell-Venue-Pro/108,56273

I would seriously consider getting that phone, I wanted it but it was delayed so just went with the HD7
[Windows Phone 7 General] SilentBob:
Now that is interesting! I do really like the look of that phone. It would be nice if I could see it in person somewhere, as I am concerned that it could be a bit chunky. But it is certainly classy looking. May have to see if I can track one down somewhere so I can size it up.
[Windows Phone 7 General] FL5:
Being limited by carrier coverage and subsidies is a pretty lousy situation, but all we can do about it is make the best of it. Due to the coverage where I live, I've signed my life away to AT&T, and thus was able to get the Samsung Focus, which I enjoy very much. If I had the option, though, I think that I'd have held out for the Venue Pro. +0.1" on the screen and a physical keyboard? Yes, please.

Either way, best of luck on your hunt!
[Windows Phone 7 General] brummiesteven:
I don't think you will find one, Dell released the Venue Pro via Dell.com, buymobilephones obviously bought a bulk of these and is selling them with contracts.

My best advice to you would be to phone BuyMobilePhones and talk about their cancellation policy. I'm fairly sure they need to give 14 days to return the device under far distance regulations, confirm this with them. Then, go and order the phone. Use it, see what you think and if it's for you.

If not, send it back and cancel the contract. Although, I'm fairly certain you will have found your new phone ;)

Edit: Also, if you're willing to consider o2, they have a pretty good deal on the HD7, compared to o2's contracts anyway:

http://www.buymobilephones.net/mobile-phones/HTC/HTC-HD7/O2/O2-25-(24mths)-Free-Internet/7479785

I've used this site before and didn't have any problems btw.
[Windows Phone 7 General] nrfitchett4:
if android is an option, I'd wait a couple more months. Lots of android devices being released with tegra 2 processors that should finally smooth android out (maybe).
[Windows Phone 7 General] N8ter:
It jas worse hardware than a desire hd and I installed the nand android yesterday to try it out. No, doesnt even compare. And it still had a crappy battery.
[Droid Incredible Q&A, Help & Troubleshooting] cam30era:
I have been using PDAnet for USB tethering, and it has worked fine. I am now running CM7, and it has functional, native USB tethering. I decided to thy this instead of PDAnet. However, when I connect to my PC, I get a Windows dialog box (on my PC) titled "Connect Broadband Connection", which requests a username and password for the connection. I have not set anything up for this, but I tried all of my normal combinations without success.

If anyone could offer any tips on this, it would be much appreciated.
[Nexus One Q&A, Help & Troubleshooting] midyat47:
hey guys,

i installed gb om my N1, but navigon crashes, won't open.

can someone fix it pls?

thanksss
[Nexus One Q&A, Help & Troubleshooting] baseballfanz:
You should email the developer of Navigon, maybe it's not update for GB yet
[Nexus One Q&A, Help & Troubleshooting] disgustip8ted:
i lold fer shur
[Nexus One Q&A, Help & Troubleshooting] plerzelwupp:
Navigin is definitly incompatible with Gingerbread-roms. The navigon-support told, that they are working hardly on it.

Meanwhile you can read the following thread: Navigon Select on Gingerbread

Maybe that helps ;-)
[Nexus One Q&A, Help & Troubleshooting] midyat47:
I did that 2, still thesame.

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

Sent via the XDA Tapatalk App
[Nexus One Q&A, Help & Troubleshooting] midyat47:
http://xdaforums.com/showthread.php?t=901405

yessssss i tried it again and it's working. Working MM Gingerbread ROM. Use Es file explorer.
[Nexus One Q&A, Help & Troubleshooting] tillort:
I also tried with es explorer but with no luck. Could you please specify what you did.

thanks
[Nexus One Q&A, Help & Troubleshooting] gpfeil:
you need to patch libmedia.so to make navigon work on CM7

search for:

navigon_fix_vendor_20110212.diff

navigon_fix_libmedia_20110212.diff

Sorry, I can't post links
[Nexus One Q&A, Help & Troubleshooting] robbo81:
navigon- running on gingerxperia 2.3.7

wel after flashing to gingerxperia v11 (2.3.7) i realised that navigon would force close. i was devastated because i love this rom it way outperforms the sony rom. anyway heres a fix. start navigon, and before it even has chance to boot quickly press and hold the home button to bring up the app switcher- select the phone icon and wait for 5 seconds... then hold the home button again and bring up te app switcher again, select navigon and it should work!. seems now after doing this once, my navigon app sparks up straight away every time. strange but true. im going to test this on a long run, but ive demo ran a 10 mile journey and the app has stayed on for the duration.

all i need now is a root method that works so i can install backtrack legacy.
[G Tablet Android Development] Chenglu:
My English is poor, so I only give the code, without more explanation.

code modiy from ownhere's data2ext

create 3rd ext4 partion for loopback device.

Please note '-o sync,commit=5',This will enhance the stability.

$BUSYBOX mknod /dev/loop0 b 7 0
$BUSYBOX losetup /dev/loop0 /dev/block/mmcblk3p3
$BUSYBOX mount -t ext4 -o sync,commit=5,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/loop0 /mnt/asec/extdata

you can turn off journal for speed：

/system/bin/tune2fs -O ^has_journal /dev/block/mmcblk3p3

busybox ls -lL /dev/loop*
brw------- 1 0 0 7, 0 Jan 9 19:17 /dev/loop0
brw------- 1 0 0 7, 1 Jan 9 19:17 /dev/loop1
brw------- 1 0 0 7, 2 Jan 9 19:17 /dev/loop2
brw------- 1 0 0 7, 3 Jan 9 19:17 /dev/loop3
brw------- 1 0 0 7, 4 Jan 9 19:17 /dev/loop4
brw------- 1 0 0 7, 5 Jan 9 19:17 /dev/loop5
brw------- 1 0 0 7, 6 Jan 9 19:17 /dev/loop6
brw------- 1 0 0 7, 7 Jan 9 19:17 /dev/loop7
[G Tablet Android Development] Chenglu:
Scoring won't be so high, but stability will increase a lot
[G Tablet Android Development] rcgabriel:
Hi Chenglu, I've actually already tried to modify your original data2loop script to use ext4 and run it with a kernel with ext4 built in. It actually benchmarks great on first boot, somewhat better than the original ext2 data2loop version, but the tablet won't boot again, it crashes sometime during boot and I have to wipe data and restart.

Not sure if the sync,commit=5 options will make a difference - maybe I'll give that a try and see if it helps...

EDIT: No, it still pukes out on reboot, those options don't make a difference. I've attached my inandop.sh file here. If you diff this with yours, there are only a few changes, and I'm just not sure why it doesn't work. Any ideas?
[G Tablet Android Development] stanglx:
Chenglu...

Thanks... this should help... but I am still very concerned with this approach..

Even though you are performing a sync you still can not guarantee that the data has been flushed out.. Flushing will depend on what other operations are in queue within the I/O sub system. In addition, right now you have a commit of every 5 seconds which honestly again leaves room for possible corruption. Again should help as this setting is meant for removable storage...

Lastly DO NOT turn off the Journal. yes it will speed up the file system BUT at a HUUGE risk of data loss in the event of unclean shutdown. This is your only fail safe that ensures filesystem consistency even across unclean shutdown.

Generally I agree with this approach for many situations but NOT your entire system partition or critical data partitions...

These devices are too portable with unreliable power sources (not the battery but the ability for it to reboot on its own and the ability for you to accidentally power it off)..

I for one am against this performance boost...
[G Tablet Android Development] Chenglu:
Fast internal storage and ext4 partion is the fundamental solution.

loopback device In some respects have an advantage.
[G Tablet Android Development] stanglx:
I dont dispute the performance gain... but at a risk. Everyone should be aware of this and accept the risk... If you do then thats fine...

I guess I'm more conservative when it comes to my data.
[G Tablet Android Development] Chenglu:
your busybox support ext4?
[G Tablet Android Development] rcgabriel:
good point, that was a mistake. I am now using a statically compiled version of mkfs.ext4 that seems to work. Mount doesn't need explicit ext4 support in busybox, should just work. And I think I'm using a version of fsck that supports ext4.

EDIT: Okay, I'm using mkfs.ext4 which I've tested from the command line and it is clearly making a real ext4 filesystem. Also using a version of es2fsck that ought to work with ext4. These are both from the Desire forums, but seem to be generic ARM binaries so they seem to run on our G Tablet.

Still same result - works on first boot, not thereafter.

Maybe I need to use a version of busybox that explicitly supports ext4? Trying that next.

BTW, I got the binaries I'm using from the data2ext.zip file here: http://xdaforums.com/showthread.php?t=859419

Also - ownhere's script looks pretty badass. We should consider using something based on that. :)

EDIT2: I am using busybox, mkfs.ext4 and e2fsck from the Desire forums, so it should support ext4 fully. Nonetheless, the exact same screen flicker followed by screen shutting off occurs with this. Attached is my updated inandop.sh. This is just baffling.
[G Tablet Android Development] anlog:
I'm working on this as well...

Took a look at your script. It looks like you've put everything (including busybox) into /system/bin instead of /system/xbin? Your environment variable for busybox shows /system/bin...

Just wanted to confirm...
[G Tablet Android Development] anlog:
I'm unable to get the loop file to mount as ext4 with ADB after it fails...

I'm not sure if/why it actually mounted in the first place, but I'm thinking this is a kernel issue. Are you positive that your kernel supports ext4? Also, I'm thinking ext4 might need to be compiled into the kernel instead of a module.

I could be wrong, though....
[G Tablet Android Development] anlog:
Also check which mount binary you are using. Busybox has one, but there is also a "mount" sometimes linked to the "toolbox" binary in /system/bin.
[G Tablet Android Development] anlog:
Ok so I (sort of) got it working.

After getting a kernel that is known working with ext4, the system was able to mount the partition again. I was getting the vegan "loop", so I went in with ADB and saw that the partition was mounted but all of the files were gone.

I then booted into CW and mounted USB, and at the same time on my PC I extracted my /data/data folder from a recent clockwork backup and copied it to /sdcard. I then unmounted USB and mounted /system and /sdcard from CW. Then from ADB I copied the data folder over to /mnt/asec/extdata and fixed the perms. I created empty folders for app-private and anr because they were empty on my backup (other than a traces.txt file in anr).

After bouncing the tab it booted up, but some of my settings were blown away. No big deal. Quadrant crashes at the I/O test part, but it might be because I don't have an Internet connection. The wifi is broken with the kernel I'm using.

Let me know if you still can't get things mounted. I'll test this more tomorrow when I get a fixed kernel.

I'm going to start working on the alternate approach of adding a 3rd partition...
[G Tablet Android Development] rcgabriel:
The kernel should support ext4, I built it myself with ext4 enabled in the config file. And yeah, I put the busybox executable in /system/bin so it wouldn't conflict with the one in /system/xbin that Vegan already has. I also dumped mkfs.ext4 in /system/bin.

What I realized is that busybox has a nasty habit of failing partially at doing things - I keep assuming that it's exactly like the stock Linux command line tools, and it's not always identical. I ended up tearing out the important stuff and running it as a standalone test script from the command line to see what was happening.

Mkfs.ext4 runs with no obvious issues (I see it creates a journal at the end, so I know it's creating an ext4 filesystem now).

But then I got an error:

mount: mounting /dev/loop0 on /mnt/asec/extdata failed: Invalid argument

followed by:

umount: can't umount /mnt/asec/extdata: Invalid argument
e2fsck 1.41.6 (30-May-2009)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /data/ext4 is mounted.
/system/bin/e2fsck: Superblock invalid, trying backup blocks...
/system/bin/e2fsck: Bad magic number in super-block while trying to open /data/ext4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

mount: mounting /dev/loop0 on /mnt/asec/extdata failed: Invalid argument

So mount failed to mount the file device that was created - that would seem to be a big issue. And then e2fsck failed to fsck it that one I'm baffled by.

I don't really understand how this "partially works" when it runs from inandop.sh but seems to fail entirely when I run it from the command line, but I sense that it "works once" because something it's getting sometimes written as ext4 sometimes as ext2/3 and that's leading obviously to corruption. Will figure more out later when I have time. I may just try adapting ownhere's script directly, he's obviously put a ton of thought into filesystem stuff and I'm not an expert in that area at all.
[G Tablet Android Development] anlog:
I was able to reboot 5 times and it kept the settings for me. I just couldnt test all apps because wifi was broken with the kernel I was using. I can test more today.

Are you sure that your ext4 format is completing? I got an mtab error when first trying to create the journal, so I just changed the script to format it with the -O ^has_journal option and it competed.

Vegan runs fine for me with latest busybox...
[G Tablet Android Development] Chenglu:
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /logodata yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mmcblk3p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback 0 0
/dev/block/mtdblock0 /misc yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/loop0 /mnt/asec/extdata ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=writeback 0 0
/dev/block/mmcblk3p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback 0 0
/dev/block/vold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=07
02,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmas
k=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard2/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:25 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=070
2,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:25 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmas
k=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[G Tablet Android Development] anlog:
chenglu can you post the instructions on how to create a third partition and mount that instead of creating a loop file? I want to test that today.

Thanks,
[G Tablet Android Development] Chenglu:
busybox fdisk /dev/block/mmcblk3 -l

Disk /dev/block/mmcblk3: 16.0 GB, 16097738752 bytes
4 heads, 16 sectors/track, 491264 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk3p1 1 397087 12706776 83 Linux
/dev/block/mmcblk3p2 397088 458497 1965120 83 Linux
/dev/block/mmcblk3p3 458498 491264 1048544 83 Linux

reboot into recovery mode

busybox fdisk /dev/block/mmcblk3

The number of cylinders for this disk is set to 491264.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): m
m
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

"d" delete a partition 1 and 2

"n" create primary partition 1 2 3

busybox mkdosfs /dev/block/mmcblk3p1

mkfs.ext4 -b 4096 -m 0 -F -L userdata /dev/block/mmcblk3p2
[G Tablet Android Development] anlog:
In your instructions it looks like partition 3 isn't referenced, but instead you're formatting /data as ext4 instead of ext3? Or am I missing something???