yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] geoken:
I would go for the LG. I've had my HD7 for about a month and I hate the capacitive buttons more than I could have ever imagined hating them. I have to always be conscious of how I hold my phone because if your finger grazes the wrong part of the phone you'll get kicked out of whatever you were doing. I type way slower than I used to type on my much smaller iPhone because I need to be extra careful when I hit the space bar; if I overshoot it by a millimeter I hit the home key. I also type slower because I can't hold the phone with my optimal grip, the capacitive buttons force you to keep your hands clear of that area.

For the life of me I can't figure out why someone would prefer capacative buttons.
[Windows Phone 7 General] Zaslav:
I would go for the LG just because it feels better built the Samsung is all plastic and feels a little cheap.

Screen size I think is negligible in this case as .2 inches isn't really a big deal. At least I don't think so.
[Windows Phone 7 General] canadariot2312:
The size difference is about .5 I believe when you are comparing thinness.

I would say that the screen difference is neglectable at best.

Omnia 7 uses metal. Probably explains why it is 20g heavier than the Focus.
[Windows Phone 7 General] nrfitchett4:
yeah, first thing I thought of was the new Miller Light beer commercial.

:D

agreed, capacitive buttons do suck.
[Windows Phone 7 General] sure haven't:
Yeah actually at first I wondered why LG would make the home button on the quantum a physical button, but after reading about the sensitivity, and noticing how sensitive the back and search button on mine are, I'm glad they did. And I assume it was on purpose with this knowledge?
[Windows Phone 7 General] mcorrie1121:
You can use the iPhone as a comparison, assuming you've used one. It has a 3.5" screen, and I find it's big enough for most tasks.
[Windows Phone 7 General] nrfitchett4:
Big enough, sure, but 4.3in is better.
[Windows Phone 7 General] emigrating:
IMO 4" are better than 4.3" in this case :D HTC really has lost their way.

That said, I wish there was a Samsung device with a 4.3" (or perhaps even 4.5") screen.
[Windows Phone 7 General] evolutionqy7:
i wanted to get the Samsung Omnia 7 just for the amoled screen. But 8GB of memory is too little for me :) so i got the HD7. The screen wasn't as bad as i expected (coming from the HD2) its really nice and colourful.
[Windows Phone 7 General] webwalk®:
4,3? damn before i would buy that i would go for a 7" one

$10 credit card sized phone and serious touch tablet
[Windows Phone 7 General] mcorrie1121:
My point wasn't that bigger was too big, but that if 3.5" isn't too small, then neither will 3.8/4" be.
[Windows Phone 7 General] Freypal:
The Omnia 7 has a more or less complete metal casing.
[Windows Phone 7 General] kderh:
I'd get the LG Optimus 7. I compared it with the Samsung Omnia 7 in a store and I THINK THE SCREEN ON THE LG IS BETTER.

Why:

1)

Most OLED screens have a lower effective resolution than normal LCDs because they have fewer subpixels. If you compare both you will notice text on webpages etc is looking jagged on OLED displays and much smoother on normal LCDs.

Search for "pentile matrix" on google.

2)

OLED screens consume big amounts of power when the image is very bright (black text on white background like on most web pages). To reduce power the OLED is auto-reducing brightness if an image with many white areas is displayed. WTF! This would p*ss me off. At least the store units did this and changed brightness while scrolling from dark areas to bright areas on a web page.

3)

OK the black levels on OLED are better but the LG's arent that bad.

Viewing angles arent good on the LG but I dont notice this at all in daily use.

Other points:

4)

Hardware buttons instead of touch (though the buttons arent that great but they do their job).

5)

Many free LG exclusive apps available.

6)

Hacking: Integrated MFG-tool with many options like a basic registry editor without unlocking (unlock works fine btw).

I bought an Optimus 7 and its working quite well. Second on my list was the Mozart which is also very nice, but I activated the capacitive search button by mistake all the time while testing.

Optimus 7 downsides:

-Headphone out has sligtly audible background noise, even more when on an active GPRS connection

-My device creaks a bit if you press it in between your fingers with force

-Pinkish spot in center of pictures taken with camera

-Supplied headphones are a piece of **** at least compared to my Koss Porta Pro

-First unit had broken bluetooth, had to send it in for repairs, now its ok

-Ringer volume is kinda low (no secondary speaker)
[Defy General] lonest4r:
Hi,

is it possible to reinstall the Blur app on a deblured rom? I miss the facebook contacts feature.

Thx a lot!
[Defy General] hatemrt:
Hi, I also miss this feature.
[Optimus One, P500 Android Development] kpbotbot:
This thread has gone on a different approach on resolving this, so I'll be setting aside my old post (I wont be deleting them for some reasons). Everything under the hash army (###) in this single post is about getting the Spica stuff on the O1. We moved to focusing on the O1's ts driver itself.

Other note: Fixes are independent. Choose whichever works for you. A universal fix may come in the future though ;) (Tell me if this post still confuses you. I'll edit ASAP)

Multitouch axis inversion fix (First release: Feb 6, 2011): Forum member waleedq came up with a workaround that inverts the inversion. This seems very straightforward, and it works. Please note, however, that this is a workaround and not a fix. As always, do a backup.

Stuff you should know:

- Most of us who tried it (inc. me), lost our OC.

- mik_os' touchscreen lag fix is here. Tested it with Android Status while touching the screen.

- Axis inversion is still a problem. Check video 2.

Videos: http://xdaforums.com/showpost.php?p=11178060&postcount=67

Link to the download link: http://xdaforums.com/showpost.php?p=11166426&postcount=47

waleedq's source: https://github.com/waleedq/ThunderG-Kernel/blob/thunderg_oc/drivers/input/touchscreen/mcs6000_ts.c

Faster readout fix (First release: Feb 8, 2011) : Der_Caveman released for testing a kernel with some delay fix (modified from stock kernel). Apparent goals were to make touchscreen input readouts faster. Also, useless and non-working functions that doesn't work were removed. No CPU spike (somewhere around 30%cpu use when touching screen)

UPD: v3 is based on drellisdee's kernel source, so yes, it's OCable.

Link to download link: http://xdaforums.com/showpost.php?p=11195243&postcount=84

Link to download link(v3): http://xdaforums.com/showpost.php?p=11221504&postcount=126 or a forum upload http://xdaforums.com/showpost.php?p=11230915&postcount=137

Changes and stuff: http://xdaforums.com/showpost.php?p=11206827&postcount=91

Touchscreen optimization + axis inversion workaround(First release: Feb 10, 2011):

Der_Caveman

and

waleedq

's work combined by

Sippolo

.

Link to download link + source + details: http://xdaforums.com/showpost.php?p=11256797&postcount=198

Link to download link + source + details (v1.1): http://xdaforums.com/showpost.php?p=11270721&postcount=237

#########################################################

Okay, so I just recently found out that the Galaxy Spica (was supposed to choose it over the O1 --') -unofficially- supports multitouch.

A link to the driver's was PMed to me by adi4motion:

https://github.com/Gabriel-LG/i5700-multitouch-kernel

Anyway, is it possible that we could implement their method on our drivers? I understand that there might be some hardware differences between the two. I'm just trying my luck :)

Lastly, for sample videos, check YouTube. I have to say that the performance with those drivers really are impressive (well, I saw the axis invert once) :D
[Optimus One, P500 Android Development] Der_Caveman:
https://github.com/Gabriel-LG/i5700-multitouch-kernel/tree/master/drivers/input/touchscreen

I didn't find any melfas drivers in there- so I doubt that the Galaxy Spica has a melfas touchscreen controller in it.
[Optimus One, P500 Android Development] kpbotbot:
But it's possible that we could write a driver based on those, right?
[Optimus One, P500 Android Development] ccdreadcc:
only kpbotbot can do tht and i hope he does
[Optimus One, P500 Android Development] N3mesis:
What about O1 brother the LG Chic? Does it have the same issues?

Sent from my LG-P500
[Optimus One, P500 Android Development] kpbotbot:
Sorry, can't code. But I assure you, I'm trying my best not to just leech :P (And I'm still figuring out how to compile FroYo to learn how ROMs get born)

There may be a guy here in the forum that has the Chic. Maybe he can test out the inversion issues :D (If you're reading this and you have the Chic, please test if the axis inverts using a tool like touch test xD)
[Optimus One, P500 Android Development] Der_Caveman:
In the O1 a melfas MCS6000 touchscreen controller reads the capacitive touchscreen. The controller itself got a proprietary firmware in it (don't know if its from melfas or LG)- you can find that somewhere in the system folder (melfas.bin(?)). Then there is the LG kernel driver which "interacts" with the melfas controller ic- it also has the ability to flash the melfas controller.

So if there is a problem in the MCS6000 firmware- we're most likely screwed, because lack of datasheets.

Furthermore I want to know how android gets the multitouch data. Maybe the android interface itself is not that multitouch friendly?

The easiest way would have been that each finger represents a "mouse event", but I doubt that this way was chosen...
[Optimus One, P500 Android Development] kpbotbot:
I see. Is it possible to decompile that .bin somehow? I know, that question might sound stupid xD

I too did a search for melfas related stuff including source codes and the like. The only stuff I found was about Samsung phones having the same touch screen.

Let's just hope (for now that we cant do anything about it) that LG -at least- releases an improved version of their drivers for their 2.3 update :)
[Optimus One, P500 Android Development] kpbotbot:
Update: The Chic has the same problem :/

http://xdaforums.com/showpost.php?p=11014035&postcount=5
[Optimus One, P500 Android Development] Der_Caveman:
Maybe the axis inversion is somehow also android related.

Multitouch is something new for linux.
[Optimus One, P500 Android Development] kite86:
I think is just the crappy touch controller that's installed on our device; It can't spot more than 2 touches, and has got axis inversion. So I don't think there's so much to do with drivers
[Optimus One, P500 Android Development] Der_Caveman:
LG only implemented "two fingers"- one can read that in LG's sources.

Again: axis inversion could also be android related (if android only requests coordinates without "finger assignments" bugs are preassigned).
[Optimus One, P500 Android Development] kpbotbot:
I don't really care whether it would accept more than 2 presses :) That would be awesome for people doing extreme gaming with the phone, but with normal use it's awkward to use 3 fingers.

I bet the axis inversion issue is very much fixable. We just don't know how yet. But considering the fact that the Spica has less of this as a problem, we might fix it a bit, or completely fix it.

This is just my opinion though. I saw some guy explain multitouch with an illustration.
[Optimus One, P500 Android Development] Der_Caveman:
Wow, I have found this:

http://www.mjmwired.net/kernel/Documentation/input/multi-touch-protocol.txt

Just had to open my eyes :D

Let's see...
[Optimus One, P500 Android Development] Der_Caveman:
You are 100% sure that the Spica does not have "the axis inversion bug"?
[Optimus One, P500 Android Development] Kel_Sceptic:
I'm 100% sure.

[YOUTUBE]RPyRhBtKIRk[/YOUTUBE]

[YOUTUBE]5Wwl2QeF6vo[/YOUTUBE]
[Optimus One, P500 Android Development] kpbotbot:
I talked to a guy who used to own the phone. He said the drivers perform well.

I didn't say that there really was no inversion. It happens less (inverted once on the video I watched) :)
[Optimus One, P500 Android Development] Der_Caveman:
Ok, then I would say there is hope.
[Optimus One, P500 Android Development] Kel_Sceptic:
I sure do prey that someone will take this project and fix the driver or write it from scrath. As i can see the code is not that long :)

our driver

https://github.com/mik9/ThunderG-Kernel/blob/master/drivers/input/touchscreen/mcs6000_ts.c

spica's driver

https://github.com/Gabriel-LG/i5700...4461c4a3d4e2be0b5f4b1a94b451604c6541f1#diff-0
[Optimus One, P500 Android Development] kpbotbot:
I have 2 months of doing absolutely nothing at home (stopped this sem. doctor said i have to rest. and yes, I have a life xD), so I might be able to understand a bit of the code. It really isn't that complex, but my lack of programming knowledge hinders me from modifying the code.

However, I sure do hope that someone figures this out :)
[Nexus S Q&A, Help & Troubleshooting] psyclobe:
Is there a way for me to download the latest nexus s rom, from the same source google uses to build it, and build a completely stock nexus s rom? If so where are these repositories and how do you build it?
[Nexus S Q&A, Help & Troubleshooting] RogerPodacter:
Yes there certainly is. The source code repo is on github but I don't have the link with me. A thread already floating around here on compiling the kernel from source, search it out.
[Nexus S Q&A, Help & Troubleshooting] mazodude:
This site might help you :D

http://forum.androidcentral.com/sam.../48675-how-compile-nexus-s-kernel-source.html
[Nexus S Q&A, Help & Troubleshooting] psyclobe:
Perfect thanks.
[Nexus One Q&A, Help & Troubleshooting] mavers1985:
Does a2sd Darktremor work with Enomther's ROM?

I've installed a2sd darktremor via the zip file in recovery.

the sd card has an ext3 partition.

When in terminal emulator, typing /system/bin/a2sd check comes back with "not found"

Thanks
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
Enomther's ROM contains built-in support for A2SD. Absolutely no need to install anything else, just to look in the thread and in Spare Parts.
[Nexus One Q&A, Help & Troubleshooting] LFact:
You can simply check app2sd related options(including dalvik cache moving) in spare parts. However, since you flashed Darktremor's over, I don't know if it will work well. If not, you need to wipe all, then flash the ROM again.
[Nexus One Q&A, Help & Troubleshooting] mavers1985:
Thank you for the replies.

I've made a clockworkmod backup before I started tinkering, so everything is backed up.

The only changes i made, was to change my micro sd card from the standard 4gb FAT32 partition to a 8gb one (7gb FAT32, 1gb ext3)

In spare parts i then enabled oldstyle-extfs-apps2sd.

I noticed the free space on the internal storage increased from ~20mb to 60mb.

The a2sd storage 120mb has currently been used. My question is what exactly is in the ext3 partition and how do i move apps there ? (is it possible to individually move them)

Finally a bit OT, but a when doing a titanium backup i'm assuming this will still back up all system/user data?
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
If you check A2SD option - ALL your apps will move to EXT. Their data and Dalvik cache will remain on the phone.

If you check Cache2SD - Dalvik cache will also move to EXT.

You can't move the apps data to SD, unless you do it manually.

TB will backup everything.

All the rest you can read about in DarkTremor's thread.
[Nexus One Q&A, Help & Troubleshooting] tokenwoken:
Just got a 8gb Patriot microSD today (Class 4) in the mail today and wanted to partition it so I can use A2SD. But after I partitioned it using Clockwork Recovery, the transfer rate for transferring files is REALLY slow like ~50 kbps. Is it supposed to be like this after partitioning? And if not, is there any way to fix this??

P.S. I tried formatting the card after partitioning and it worked fine after that, just when I partition it goes slow.
[Nexus One Q&A, Help & Troubleshooting] tokenwoken:
Bump.... anyone? Preaaaseee
[Fascinate General] DarthCivicus:
Anyone else notice if the 250 characters limit went away with the update, or have my texts gotten shorter?
[Fascinate General] imnuts:
The texting limit is and always has been 160 characters per message

Sent from my Froyo Fascinate
[Fascinate General] tmlhodge:
Mine is 400,000 per message..............yeah........i feel like mine broken.

No but seriously, you could just...send another one if you run out of room.
[XPERIA X10 General] dmawer1974:
Hi, im using the default email client on the X10

Firmware version: 1.6

I want to know if there is a way of backing up the email messages?

I want to upgrade the firmware and then put the data back on. Stupidly I didn't use IMAP when setting up my profile, and I used POP3.

Any help would be greatly appreciated :)
[XPERIA X10 General] Buddha:
try post #6

http://xdaforums.com/showthread.php?t=681337
[XPERIA X10 General] roaringhere:
There's a free app on the Market that I use called My Phone Explorer, it backs up everything to your PC. Also you can try My Back Up from the Market. I used both for redundancy...
[Sony Ericsson XPERIA X10 Mini] omidchini:
SOLVED

______________________________________________

first for jumping out of flash mode, i used pc companion's repair, even though it didn't worked, but at least it kept my phone in the flashing mode

second, after the failure of pc companion, i opened flashtool and flashed a 1.6 one onto it.

third, my phone was running again!!

______________________________________________

hey guys,

i have bricked my phone

i have tried the solutions here, but none helped:

* seus said: the phone has already the latest version installed

* repairing said: there is no software available for your phone yet

* sometimes the going into flash mode doesn't work, it simply jumps out of it, but by pressing some buttons, it remains in there

[edit: now i can't make it to stay in flashing mode anymore]

* the combination back+home+power does not have any effect

* flashtool reaches to the end and says

29/044/2011 17:44:36 - INFO - Now unplug the device and power it on

29/044/2011 17:44:36 - INFO - Then go to application settings

29/044/2011 17:44:36 - INFO - turn on Unknown Sources and Debugging

though nothing happens afterwards (and by nothing i mean it still remains at the SE TEXT, not logo).

NOTE: I rooted my xperia before using flashtool, but i couldn't install recovery, and even when i was installing root with SuperOneClick, everything was smooth and said success except the test which failed.

PS: if i use a generic ROM, would that help? i flash this firmware with flashtool:

Generic 2.0.2.A.0.24[rooted]X10 Mini Pro (U20i)
[Sony Ericsson XPERIA X10 Mini] wiilweer:
You flashed with xrecovery ? Can you access it and fix permissions ?
[Sony Ericsson XPERIA X10 Mini] omidchini:
yes, the rom had xrecovery, but holding on back and power doesn't lead to the xrecovery, the text still shows up, though it has a delay and the grean light blinks once
[Sony Ericsson XPERIA X10 Mini] hurlof:
I´m dealing with the same issue. xrecovery was installed but I can´t even access it because the cell phone hangs on Sony Ericsson logo screen.

still unsolved. cant use usb- wont connect. green blink and thats all. logo hangs up all the time.
[Android Software Development] Luminger:
One of my current ideas require me to change the settings provider (the system one with the "settings" authority) or proxy it. I tried different things here and maybe someone has a great idea.

1) Patch the classes.dex

I managed it to patch the SystemSettings.apk with a modified version of its classes.dex. But this isn't a very efficient way and it it's quiet impossible to automate the process to do the following cycle on a phone:

deodex -> baksmali -> patch -> smali

This isn't very fault tolerant and on every stage it may fail badly. Also every SettingsProvider is a litle bit different from others which makes the patching process damn hard. But the good point in here is the system just accepts the modifed apk (I only swapped the classes.dex).

2) Patch the AndroidManifest.xml

Another aproach was to modify the AndroidManifest.xml and rename the authority to "originalsettings" and setup a proxy which is called "settings". At first this seems a litle bit smarter than patching the classes.dex but has more problems to solve (if they are solveable).

First problem: You have to decode the apk and pack it again. If you just replace the resulting AndroidManifest.xml into the old apk it will explode -> wrong signature. If you sign the resulting patched.apk with something other than the system signature -> boom. It seems the system doesn't except a package which requests android.uid.system to be not signed by the platformkey...

Second problem: What to do with the proxy? Has it to run within the systemservice? If yes -> same problem as above, it will run as android.uid.system... If no, okay -- good, but will this really work?

As mentioned, the first aproach may work but isn't very relieable... The second one would be more cool if it's working.

Does anyone have an idea how I may get this working?
[Android Software Development] Luminger:
Any idea how to solve the signing problem at least?
[Android Software Development] Luminger:
Nobody? :(
[Android Software Development] Chainfire:
It's simply not supposed to be possible if you're not the OEM.
[Android Q&A, Help & Troubleshooting] arminsoyka:
wondering if someone has a solution for the missing feature in the google calendar described or discussed here:

http://android.stackexchange.com/qu...gle-calendar-on-an-event-after-its-been-syncd

I find it very annoying since when I'm in a rush I'll just create the event and not so much care about the owner but later on I really need to edit it. so I was thinking maybe there was an app that could do that?

would be thrilling if we could come up with something!
[Android Q&A, Help & Troubleshooting] darinr80:
Was this fixed? It is SO annoying when it's not editable on the Android phone!!
[G2 and Desire Z Q&A, Help & Troubleshooting] mohsin125:
Hi,

ive tried searching for this but couldnt find anything...my question is that if i buy a g2 from america and ship it to UK, will it work with the networks over there? like with tmobile uk and orange?

(I couldnt find the network bands of UK networks)
[G2 and Desire Z Q&A, Help & Troubleshooting] ianmcquinn:
Once unlocked, it'll definitely work for calls/2G data. I believe those networks use 2100 for UMTS, so it should give you 3G as well.
[G2 and Desire Z Q&A, Help & Troubleshooting] jaoyina:
I did not unlock my G2, it works for other 2G network, but for 3G, you must unlock it.
[G2 and Desire Z Q&A, Help & Troubleshooting] LooieENG:
What good is a Desire Z without 3G :p
[G2 and Desire Z Q&A, Help & Troubleshooting] steviewevie:
The G2 supports Band I (2100) and Band IV (1700/2100). UK mobile networks use Band I for 3G so you'll be fine with UK coverage. Possibly not so fine in some parts of Europe though, some use Band I but also Band VIII (900) - the latter being supported by the European DZ.
[EVO 4G Q&A, Help & Troubleshooting] spalding1028:
I've had cyanogenmod installed for a day now and I've finally gotten all of my sms, apps, and launcher settings transferred over (thanks to everyone who helped me get it going). Everything is working fine except that after the first reboot after installing my apps, almost all of the apps that I had moved to the sd card are saying that they are no longer installed. I used astro to backup and restore them. Any suggestions?
[EVO 4G Q&A, Help & Troubleshooting] blakjak220:
There's a setting in Menu > Settings > CyanogenMod > Application Settings that is prolly you're problem.... try un-checking the "install to SD card feature and re-install them frm Titanium or whatever.... Just somethin to try
[EVO 4G Q&A, Help & Troubleshooting] spalding1028:
I've used titanium to install some of the other ones, but I don't have time right now to deal with nandroid and then reinstall my apps. probably tonight I'll give it another crack. I don't see why they wouldn't work though. For now I'm just gonna use the default sense rom.