yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] wombling:
Hello,

My wife recently had the misfortune to drop her newish HTC Desire A8183 on the kitchen floor, thanks to my daughter's over eager grab. The digitizer has some lovely cracks all over it now... :-(

Needless to say, my wife is dismayed, and my daughter (she's only 3 and didn't mean it) is very sorry.

I thought I'd try replacing the digitizer myself, having read many tales of repairs taking 3 weeks and costing 300+ dollars.

Bought a new digitizer, took phone apart (even had a handy little "oven" that I could set to 60 degrees to melt the glue).

Phone taken to pieces quite happily.

Put in new digitizer, reassemble.

Now start up phone, all looks good.

BUT... only a small section of the screen is responding to touch (where the 7,8,9) keys are when entering SIM PIN. The row below has also worked (although intermittently) and the emergency call button too...

So my question:

Is this a problem with the digitizer I bought? Is there a particular model number of digitizers that I should be using? I note that the old digitizer had an "I2" printed on the pcb, whereas the new one has an "E5", the old one has a sticker with SHAB1 on it whereas the new on has SHABN...

I'm not sure that this is important - but given that the thing only partly works, I think it might be.

Anyone got any ideas/hints for me to try... I'll phone the supplier tomorrow and suggest to them that the part is faulty, as I can't see any threads out there where this has happened to someone else.

EDIT: I thought I should add that the old digitizer despite looking like a spider's web, still actually works - which really make me think it is a problem with the new one...

Thanks for any help!

Chris
[Desire Q&A, Help & Troubleshooting] mr_norris:
I can't really help you from experience all knowledge.

But I did read somewhere that you have to use specific digitizer for specific Desires.

I could be wrong :)
[Desire Q&A, Help & Troubleshooting] endrus:
Did you work out any solution for your replacement digitizer issue?

I have a similar problem and I just realized the different ghost pattern of the screens (original has diagonal, new has square arrangements of dots) and also the electronics of the digitizer is slightly different (Original: Synaptics 940-663-1R1, replacement: Synaptics 940-682-1R2)
[Desire Q&A, Help & Troubleshooting] ketaponk:
Hello,

I'v got the same problem, i even bought two digitizers from different sellers. I thought that it is because i did something wrong when I disassembly and assembled the phone but I put my old digitizer again and it works ok ( except the corner where it's crashed ).I asked my sellers if there are some different digitizers and they replayed that no and the one I'v got are checked and ok ( the electronics is identical, the only difference are white big number E2 and G2 ). What can I do more to repair my poor thing?

Stan
[Desire Q&A, Help & Troubleshooting] lufc:
Please use the Q&A Forum for questions Thanks

Moving to Q&A
[Android Themes] Igotno:
How do you take screen shots?
[Android Themes] ExMM:
Download from market "screenshot" or "shoot me", otherwise just search the market, there are quite a few..
[Android Themes] Igotno:
Ok cool ty for the quick response
[Android Themes] ExMM:
No problem! :D
[Atrix 4G Themes and Apps] Dillsnik:
I like the actual dialer itself, the buttons are nice and big and easy to hit, but there are a few things about it i wish were a bit more intuitive. For one, i believe on my old phone, when you start punching letters/numbers it would tend to pull up the most expected result...so if you call a number a lot that would be above say someone you don't ever call. but this doesn't do that so i am constantly seeing the same random contact at the top when i punch the first FOUR digits for one of my top dials. Which brings my next point, i don't like that you only get one choice to start, my old phone i could see like 4 or so contacts then touch the one in the list from there. on this dialer, i always have to hit the thin bar where it tell how many matches you have, and it's easy to miss that with your finger. I also wish that when you come into the dialer it listed more than just your last single connection.

I may try out something else, any suggestions?
[Atrix 4G Themes and Apps] live4nyy:
Try typing the digits that correspond with the first few letters in the name of the person you are trying to call
[Atrix 4G Themes and Apps] Dillsnik:
That is what I am doing now
[Atrix 4G Themes and Apps] txtsd:
I hate the stock dialer bc it ONLY shows ONE name/number when you start dialing. I'm used to seeing at least 4 names/numbers on that screen. I use GO Dialer instead. It's an ugly shade of blue, but the keypad is transparent translucent, and also goes away when you scroll the list of names/numbers.
[Atrix 4G Themes and Apps] Sebring5:
I like the stock dialer

I looked at some alternatives but I like the stock one better.
[Atrix 4G Themes and Apps] henryher:
The only gripe I have with the stock dialer is that I can't get it to work in landscape mode. Any one out there know how to get it to rotate automatically. I can't find any settings for it to make it rotate.
[Atrix 4G Themes and Apps] lsxrx7:
the only dialer that i consider very good is the one from MIUI

everything else doesnt compare in my book
[Atrix 4G Themes and Apps] SpeeDemon:
Go Dialer is pretty good. First one I actually find acceptable. All of the "Go Dev" apps are quite good, and updated constantly. Plus they actually tell you what they updated, and on what date.
[Atrix 4G Themes and Apps] lsxrx7:
I found Go contact right b4 I saw your post too lol

I was going to come here and update this thread

but yea

Go contact + sms + launcher has been awesome
[Atrix 4G Themes and Apps] joeryu:
I can't use the stock dialer cause I changed my LCD density (210) and that breaks the stock dialer. Was trying to get used to go dialer but it doesn't transfer numbers from Google maps, ie if I do a search on maps and click the dial button, go dialer comes up blank. That alone was a dealbreaker for me. I use dialer one, very functional, fast, and looks like stock. I also was not a fan of the weird blue shade of go dialer.
[Atrix 4G Themes and Apps] Diviance:
Newest update is supposed to fix the numbers from other apps thing in Go Contacts.
[Atrix 4G Themes and Apps] lsxrx7:
nope

didnt fix it

uninstalled
[Atrix 4G Themes and Apps] y2whisper:
I don't mind the stock dialer, I only mind that the stock contacts app doesn't allow you to filter your contacts at least to phone only on the bell version. the contacts tab does that for you (for obvious reasons) but it makes the contacts app useless to me as it shows everyone I have emailed on gmail as a contact.
[Atrix 4G Themes and Apps] riotburn:
I use dialer one. Its very good and similar to sense dialer
[Atrix 4G Themes and Apps] tuantuti:
i was about to post a thread looking for some dialer and contacts app. i gave up on the stock one, so not intuitive. my last phone was windows mobile, and the way you find contacts using the dialer is so much better than the stock android. so i tried Go Dialer and Dialer One as suggested here to test both. any more options out there is appreciated :D
[HD7 General] cubanaso:
Can someone try and give me the carrier value for Bell Mobility. You can find it with your registry under HKLM\system\platform\devicetargetinfo

I used the chevron method to debrand it but foolishly forgot to look at the orginal value. I am trying to rebrand it because aparently this can have adverse affects down the road during future updates.

"Tip: If you unbrand your #wp7 device, restore it afterward otherwise you may get updates not applicable to your device in the future. (Bad). @WITHINRAFAEL"

Thanks!

**edit**

Through some searching I was able to find that the carrier value is BEL-CA. So if anyone wants to revert back there you go.
[Galaxy S I9000 Q&A, Help & Troubleshooting] mgianni19:
Before you guys kill me for starting a thread, I am doing this for my co-workers who just got the I9000 and rooted it. But for some reason I am helping him with installing a new ROM but whenever I use ROM Manager it says Clockwork is installed but I still get to the stock Samsung recovery.

Any idea's how to get rid of this? I would appreciate any help!

Thank you!
[Fascinate Android Development] hetaldp:
From = oss.request@samsung.com

[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]

Dear customer,

We''re pleased to provide you the Froyo update source code of SCH-I500 USC (Mesmerize).

You can download the source code from the site below:

http://opensource.samsung.com.

Public firmware for Froyo update version about SCH-I500 VZW (Fascinate) is not announced yet on the outside.

After public release, we''ll publish open source code of SCH-I500 VZW (Fascinate) on website.

Please wait until early April.

Thank you.

Sincerely yours,
[Fascinate Android Development] sreymj:
Yes indeed... pulling it down now. It's time for some more home cooking.
[Fascinate Android Development] kvaughan:
Does GB use the .32 kernel?
[Fascinate Android Development] jiggaman508:
Nope, .35
[Fascinate Android Development] bobloblaw1:
For some reason Samsung has put the Mesmerize updater (Kies mini) on the Fascinate software update page...... mistake?

http://www.samsung.com/us/support/do...SCH-I500RKAVZW

The potential incompatibility and typos scare me.
[Fascinate Android Development] rushfanx1:
In the zip file... There is a notice.txt ... In the file, it has this

"This sourse is Kernel code."
[Fascinate Android Development] rivaaaa253:
You can run GB on a .32 kernel tho, like the moto droid.
[Fascinate Android Development] preymond:
Its what Kaos has been doing with his CM7 releases
[Fascinate Android Development] turtleman2008:
believe so
[Fascinate Android Development] Zacisblack:
Couldn't have said it better myself! +1
[Fascinate Android Development] joshnichols189:
Key words: "Right now"
[Fascinate Android Development] imnuts:
The Mesmerize Froyo went live last night, and source for the kernel is already out. The Thunderbolt was released last Thursday, where is your source for that?
[Fascinate Android Development] SirGatez:
Gripe: same story as always alot of unneccessary changes to the source code making it appear to be incompatible with the other handsets. Sorted out a good portion of it this morning. Top of list once working...make a universal GalaxyS kernel....progress is I've been working on it for a week already minus the fascinate specific stuff, btw it appears the Fascinate I-500 4G is on the way because this source has wimax and a dsim drivers in it..
[Fascinate Android Development] adrynalyne:
Yeah but we don't use wimax ;)
[Fascinate Android Development] Terror_1:
Don't care, now back to what Adryn said?
[Fascinate Android Development] suppliesidejesus:
...the Fascinate.
[Fascinate Android Development] ataranine:
Not a big fan of the screen on my Fascinate..

The greys look all purple, especially on low brightness settings.
[Fascinate Android Development] sunder74:
Unfortunately that's the trade off for pure blacks and deep greens,reds and blues...Amoled doesn't due pure whites and the pinkish tint to greys is a known issue since the technology came about.
[Fascinate Android Development] ataranine:
So I don't get why everyone drools over the screen.

It's not that great.

Anyway, I'm definitely switching to an HTC phone soon...just as soon as the Merge comes out. :D
[Fascinate Android Development] spenceuiuc:
I can't wait for the AOSP Froyo, GB potential, and a fully functional MIUI on the Fascinate. Perhaps Froyo source will get us a step closer...
[Fascinate Android Development] GizmoDroid:
Were you running a stock kernel on dj05/dl09?

If you were running a custom kernel on eclair and a stock kernel for froyo, then its like comparing apples to oranges on battery life. Once the custom froyo kernels start getting released and any remaining bugs worked out, you will see battery life comparable or better than the eclair kernels.
[Fascinate Android Development] lane32x:
Oh yes, I'm quite aware of this. Sorry, didn't mean to make you think that I was complaining. I was just responding to the statement that he/she hadn't had any problems with Froyo so far and it's been smooth sailing.

That's really the only reason I've been looking forward to either source code, or an official release was because originally everybody said that froyo improved battery life and responsiveness (on other phones). Although how it accomplished both was beyond me. I always wondered if it was placebo effect.
[Fascinate Android Development] SirGatez:
I pretty much finished merging into my source tree about 4am, going to proceed with test compiling late tonight. Merge broke overclocking, bln, voodoo sound, and a few other tweaks due to the relocation of files by Samsung. I hope to have a compiled kernel in two days if all goes well and I am not going to speculate on a release due to how coding can be hit or miss sometimes :-) but I will keep everyone up to date!
[Fascinate Android Development] s44:
Great! I'm sure you're switching to the Froyo versions of BLN and Voodoo Sound, but would it be hard to port over the Voltage Control-compatible OCUV setup used on all the GSM kernels (including your i9000 test base)?

Swyped from my Voodoo-powered Fascinate via XDA
[Fascinate Android Development] lucas.scott:
Thanks so much man .. really feel like your work is going to make the difference we have all been waiting for since we "got" 2.2 . Don't get me wrong, I've been happily running superclean, but this is going to make it that much better. Thank you.
[Fascinate Android Development] GizmoDroid:
Well froyo brought about a more efficient dalvik engine with JIT support, allowing applications to run sometimes 20-30% faster. If an application can get done sooner, with less overhead, it will use less battery too. I'm sure they also made some improvements to power management (though I think there was more work done for gingerbread, possibly).

So even on a stock kernel there is a small potential for better battery life, but it doesn't compare to what the kernel tweakers can do when they start fine-tuning the voltage/cpu frequency/sleep levels.
[Fascinate Android Development] GizmoDroid:
"UV Support using VoltageControl version >= 2.0" is listed among the features for the tweaked i9000 source base he pulled from. Is that the same as what you were referring to?
[Fascinate Android Development] s44:
Yes. I think he's merging into the Blazed source tree, though, which had a different setup.
[Fascinate Android Development] SirGatez:
Nope merge is of I9000 with that custom I9000 source merged in, some Blazed features already merged, some Eclair Blazed merging left will require fine tuning. So yes it will be UVOC and I intend to eventually backport upgrades to Eclair once Froyo is stable and we will have Gingerbread shortly as well because of the efforts of others who are strongly focused on it atm.
[Fascinate Android Development] jearl75:
Kaos tweeted the kernel is coming along nicely. Can't wait!
[Fascinate Android Development] ashasaur:
Please remain on-topic people. No speculation, no "what is coming outta this" and certainly no Thunderbolt vs. Fascinate discussion.

I have just cleaned this thread SUBSTANTIALLY.

Please let this thread just be an update thread for what is ACTUALLY going on with the 2.2 source. Further people spamming +1's and speculation will be issued warnings.
[Fascinate Android Development] gsharpshooter:
Wait a minute early april? ? Is this an april fools joke....
[Fascinate Android Development] bL33d:
I will def throw him some cheddar for gingerbread like i did jamezelle for miui :)
[Fascinate Android Development] ataranine:
Definitely got 10 bucks waitin' on him when he gets it done. :D

May not be much..but..meh. I'm broke. :(
[Fascinate Android Development] khanable:
I'm probably going to go broke donating to various devs in the next few weeks

totally stoked

good thing I like ramen noodles :D
[Fascinate Android Development] ataranine:
I got one pack left... crap...

Time to go get another box of Beef and Shrimp ones fo like two dollars. :D
[Fascinate Android Development] dandog96:
I like chicken.
[Fascinate Android Development] iofthestorm:
Out of curiosity, is there any reason Eclair can't run with a 2.6.32 kernel?
[Fascinate Android Development] TheSonicEmerald:
It can, its just insanely hard.
[Fascinate Android Development] SirGatez:
Yes for one the Froyo video handlers for the PVR gfx chip are.not compatible with Eclairs kernel driver and likewise the Froyo kernel driver is not compatible with the Eclair video handlers, the drivers use binary blobs and are not fully opensource hindering transparency in our graphics driver progress. As the blobs are only compatible with their respective kernel drivers which are only compatible with their respective android graphics libraries which are only compatible with specific versions of android. I had no luck compiling and testing various combinations about 6-8? weeks ago.
[Fascinate Android Development] GizmoDroid:
Is this anywhere near the realm of tom3q's project? I know his is working with s3c6410, but more specifically, is this a completely separate problem then what you are referring to? (seems like it might be different, but I remembered this and started wondering if it might have any helpful info)

http://github.com/tom3q/gles6410

edit: I now know a little bit more about it. Looks like we *might* get an open source driver... 6 months from now, if they feel like it.

http://www.phoronix.com/scan.php?page=news_item&px=ODk4Ng
[Fascinate Android Development] SirGatez:
I knew about the "we might get source" part but I didn't.know about tom's work, source pulled and I will see if this helps us :-) Thanks giz!
[Fascinate Android Development] iofthestorm:
Cool, exactly what I wanted to know. Thanks!
[Fascinate Android Development] Domush:
So, has anyone managed to compile from source yet? Are we dealing with a bad source like last time or is this simply a case of devs not getting around to it?

I was under the impression once we got this source it was trivial to compile an AOSP Froyo and Gingerbread ROM.. Is this somehow no longer the case? What changed?
[Fascinate Android Development] bobloblaw1:
Kaos has been making progress on the kernel. Check out his twitter to keep up to date. It's punkkaos.

And remember, our devs are people too. They have families, jobs, classes and many other things that compete for their time. This is some thing they do for free. They are working on it, but hacking and coding for the fascinate is rarely priority number one for them.
[Fascinate Android Development] SirGatez:
Not trivial but it does help in figuring out what in this blackbox was not working, I have not gotten a clean compile yet, still debugging and I have finished about 3/4 of it and it is compiling with tons of warnings. I should have more info to share tomorrow because I hope to be done debugging by then to the point where I can get a kernel out of it bootable or not. Then I have to fix all the things that the code merge broke :-P and be careful not to merge back in outdated routines I have already snipped from my tree that could break things again.

Maybe it would compile as Samsung provided (or maybe it needs just as much work as if I just merged it or like their Eclair code drop needed) but either way I'm not interested in riding in on Samsung's mediocrity (you can flash a leak for that), check my work with Blazed-Eclair to see how I roll. I wouldn't be a kernel dev if all I did was recompile other people's work :-)

So yes we're ahead of where we were before the drop but we are not sure how far ahead or whats left, plus things like this take time and many of us are in school or work or like myself I work full time and am also working on my degree and I have a family to spend time with as well, so the fact I ever get.anything done is in itself a miracle.
[Fascinate Android Development] kidserious:
Hey Sir Gatez, I just want to say thank you for what you do. I am grateful for all of you devs. Adryalyne, Jt, punk kaos, SOS3 and if I left someone out I appreciate your work too. Thank you for taking time to make this phone Awesome!!! I apologize on behalf of anybody and everybody who cops an attitude or isn't grateful or has an attitude that y'all are supposed to do this for us. Not that I am saying the guy above had a bad attitude but I am just saying in general. We don't derserve anything!! Thank you for being gracious. Forgive us if we get impatient. Thanks man!
[Fascinate Android Development] 4GivenByChrist:
Well JT tweeted that the source kernel is booting on the fascinated and it is time for some hacks...
[Fascinate Android Development] SirGatez:
Well that sounds very promising :-)
[Fascinate Android Development] chrisexv6:
Excellent news!

Its been so long since I flashed a new kernel or ROM and had an updated version released as I was flashing it.
[Fascinate Android Development] gfosco:
I was able to compile the source tonight as provided (lots of warnings, but they're ok).. I haven't flashed it yet because I'm waiting for a phone call :)
[Fascinate Android Development] kidserious:
Can you give us some details? How did you customize it? Thanks bro.
[Fascinate Android Development] gfosco:
I didn't do any customizing yet, just compiled it as it came from Samsung, hoping it works :)
[Fascinate Android Development] kidserious:
Awesome!! Keep us posted please. Good work!
[Fascinate Android Development] gfosco:
I should have realized that the stock source wouldn't be Voodoo compatible, so it causes a boot-loop if flashed on top of a voodoo system. So, I pulled down jt1134's git repo and compiled his newest kernel. That compiled and flashed just fine. I think I might work on his source instead. :p I'll disable voodoo and try the stock one, just to see.
[Fascinate Android Development] kidserious:
Of course I don't know ANYTHING about kernel hacking but what are the possibilities of adding color enhancements and OC to Jt's kernel?
[Fascinate Android Development] kidserious:
And can you do it to the Aosp vanilla kernel? Thanks bro, running vanilla and LOVING IT!!!
[Fascinate Android Development] gfosco:
I'm kind of a noob, but I'll look into it.
[Fascinate Android Development] gfosco:
I disabled voodoo, waited for it to change the partition (love that voice!) and then flashed the kernel I compiled from samsung mesmerize source using SGS Kernel Flasher (on the market), same outcome: boot loop on the SAMSUNG title. /shrug Switching back to voodoo and jt1134.

Was anyone able to compile this from Samsung and have it work?
[Fascinate Android Development] SirGatez:
If you build stock source for voodoo you need ext4 and jdb2 at minium either compiled in or as modules. I just go ahead and include jdb and ext3/2 incase.
[Vibrant Q&A, Help & Troubleshooting] jamesd86:
My wifi tends to drop from a solid connection (50-65 mbps) to a crappy connection (2-5 mbps) no matter what rom I am running. Was wondering if anyone else has this problem? Possible fix?

It will constantly drop data connectivity...market will give error, browser gives error.

Connection starts at the solid levels then within 1 minute or so drops to the crappy level, with excellent signal. that's what makes me really mad..it's got perfect signal and **** connection. any help appreciated.
[Vibrant Q&A, Help & Troubleshooting] spurwonof:
Hi,

What ROM are you using?

I think you should first check your wireless LAN/router location, modem and LAN setup through yr desktop. Check if it is any enable firewall in yr setup, try to disable it. Test wifi connection using yr laptop, check it any drop or not. Try again at same time using laptop and yr vibrant in several distance from wireless router. Try also WPS if you have it.

If your laptop no problem, and phone wifi drop, you might to try reflashing ROM.

Before that, you may try also Wifi analyser, install it from Market.

Good luck.