yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Immorten:
Hi!

I tried to replace a cracked LCD display on my Nexus One, but now the colors are all messed up. Have any of you had the same experience? It's like insane! The black is like grey, and there's like these horizontal lighter stripes across the screen. Could this simply be that the LCD connector is not properly attached to the motherboard? 'Cause it was kind of tricky to push it back in place. Had several tries where the screen was completely black, because of the connector not being attached properly..

Cheers!
[Nexus One General] dowmace:
There is a good chance you dont have the connector fully seated. There is also the possibility that you got a bad screen, where did you get the new one?
[Nexus One General] Immorten:
I bought it over at DHgate. I sent them an email, but they said they tested each screen before sending it out or something. But should it be THAT hard to press the connector into place? I've been struggling with this for a few days now.. :p I've also checked that none of the pins are damaged. Atleast what I can see without using some form of magnifying equipment :p
[Nexus One General] dowmace:
The connector on my phone just snapped in, as in you could feel it pop in and knew it was making contact, I really believe that if you could see a good connection you have a bad screen, try and take pictures of what it looks like when running
[Nexus One General] baseballfanz:
Did you get the right one?

AMOLED or SLCD?:D
[Nexus One General] Immorten:
Here are some images.

It doesn't look that bad on the images. Sometimes there's also flickering on the screen, but it stops after a few minutes of use.. Hehe.

I could feel the snap myself when i pushed the connector in, but it's still crap..
[Nexus One General] xdZKu7:
On my Dell laptop I have a similar issue where sometimes when the screen connector is pushed all the way in it shows weird colours just like in your pictures (sometimes also lines or other artifacts). For me the solution is to wiggle the contact with the laptop running until it is sufficiently loose where all pins make good contact.

I also remember similar artifacts when an iPhone I fixed had poor contact.

You could attempt inserting the connector with the phone running, but beware of static, and also note that not all electronics like being powered up that way (i.e. I'm not responsible if you break it more than it already is ;) ).
[Nexus One General] Immorten:
Thanks for the tip, xdZKu7, but no luck. It was either flickering/tweaked colors, or nothing.. I don't want to waste any more money on this phone now, so I'm thinking of investing in a DHD instead =) And this time with proper insurance! :D
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] stevehead:
A method to stop our WP7 Phones updating needs to be confirmed. I should imagine that with the first update our shiny new WP7 will be killed.

If this goes anything like iPhone we need to wait.... read & read some more... THEN flash the update at our convenience.

The Update could be triggered by Zune or the phone - I don't know, but it needs some investigation imo and quickly!
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] daz1uk:
I dont think Zune will force an update, but to be honest I'm not scared if it does. You got some info I dont know about?
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] jonas2295:
even they cant kill the activation codes we get from support because then they would have to kill all keys ....so i dont think there will be a issue
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] vista1984:
Actually I am looking forward to the update .:P
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] theickleone:
I'm pretty curious myself :D
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] DennisCSUF:
It doesn't I had my Zune pass for a little of two years along with my ZuneHD and fat brown Zune 32 gig and they never push any update on you. You have to go an actually hit the UPDATE under settings --> Phone ---> update ;)

to install any updates.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] makomek:
I'm waiting for the upgrade ,Let's bring it on !!!! **** who cares if they Lock it I'm going back to Android :D.

This WP7 really need an upgrade fast.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] jzack:
lol i can;t wait for updates for this wp7.. well if its not getting better with fixes or even if they block keys or anything that they could do, worst comes to worst we'll just go back to android.. at least its better.. for now~
[Captivate Android Development] loserskater:
Working Kernel thanks to xcaliburinhand!

He's pushed it to git so you should hopefully start seeing it in other kernels.

HERE is the kernel.

You will need THIS APP for it to work properly.

Google Car Home update.zip

Captivate Car Home update.zip

What's Left?

CM7 support

Want to include it in your kernel?

BOUNTY:

loserskater $20.00

alabamaroping $10.00

OVCArchion $10.00

mrcoolgli $20.00

lospulpo $10.00

ihalatci $15.00

delugeofspam $15.00

I would like to start a bounty on getting this to work.

THIS and THIS is the car mount I'm talking about. They're both the same.

It has a male usb that plugs into the phone and on the back of the mount there is a female usb (for charging) and a female 3.5mm line out (for audio). Once plugged in, all audio is sent through the rear speaker instead of over usb.

It states in the manual that it will work once the official 2.2 comes out.

I'm hoping that somebody can get this working before that.​
[Captivate Android Development] ady:
Have you tried the Rogers 2.2 update?
[Captivate Android Development] loserskater:
I have not tried that update. Does it work?

I tried Cog 3, and I thought it was using stock Roger's but now I think it might be using the old kernel from earlier Cog releases.
[Captivate Android Development] agentsmith5150:
I think this would be awesome if we could get it running. I bought the home dock with the intent of using the audio out for the home theater. Of coarse Samsung and their ever lasting "2.2 taunts".

_______

Phoenix 3.5 - Speed Mod - UGJL2 Modem

Tis How It Should Have Came From Samsung
[Captivate Android Development] wade7919:
Cog 3, is running the Rogers Rom & Kernel i do believe. it won't be running an older kernel that much i can tell you
[Captivate Android Development] cforsyth:
Rogers 2.2 update

I'm running a rogers captivate with the update, and the audio output from the car dock is still not working.

I have the desk dock as well, and the audio out from that dock DOES work.

I haven't ruled out a faulty car dock. Has anyone else had similar experiences?
[Captivate Android Development] alabamaroping:
I'll contribute $10

AlabamaRoping.com

Running Phoenix 3.5 & Lovin' It

Sent from XDA app on da' phone
[Captivate Android Development] neptronix:
All I9000 based ROM/KERNELS Ive ever tried do not work. Captivate kernels the USB Audio out works fine. Unfortunately, after running I9000 ROMS, I wont be going back to a Captivate ROM. So yes, same problem here. I also believe it is related to the Kernel and not the ROM itself.
[Captivate Android Development] Betray:
I was having this problem with the new rogers 2.2 update.

But i finally discovered whats wrong. First of all, i have only figured out to get the official Samsung apps to work (car home, desk home)

To get them to work, you attach the device, then look for the sound icon in the main menu. Press it until it turns into the mute button. For some reason, the sound the carries to USB.
[Captivate Android Development] GAMacky:
I can't find a main menu with either app. Are you talking about the notification bar?
[Captivate Android Development] Betray:
no you have to open either apps. and then that becomes your home screen. There should be an audio icon.
[Captivate Android Development] OVCArchion:
No workie on Phoenix 3.5. It didn't work on Cognition 3.03 either which is a captivate rom. I believe the car dock is keyed (resistance?) differently than the desk dock, as it launches the proper car app automatically, and not the desk app.

Put me down for 10 bucks in the pot.
[Captivate Android Development] loserskater:
Can you post a screen cap of what you're talking about?
[Captivate Android Development] OVCArchion:
Back to the front page we go...
[Captivate Android Development] loserskater:
OK, I figured out what you're talking about...

The Roger's Rom uses a different car dock app called CarCradle. I pulled it, deodexed it, put it in /system/app, ran out to my car to test, and nothing... it just muted the music.

I did this using Doc's 9.1.2 with GB latest kernel.

HERE is the deodexed CarCradle.apk if anybody else wants to try.

You'll need to uninstall car home and put this in /system/app
[Captivate Android Development] sold1erjjt:
not definite on this but especially since you said this is for a i9000 ROM, I saw Supercurio is taking requests for Voodoo Sound. I would check there

http://xdaforums.com/showthread.php?t=806195&highlight=voodoo+sound
[Captivate Android Development] ardyer:
Does the Rogers rom use a different desk app as well? dRop you know what it's called?
[Captivate Android Development] loserskater:
It's called DeskCradle.

HERE is a deodexed version of if. Again, put in /system/app
[Captivate Android Development] outcastrc:
I just used the audio out using the car dock today. Stock froyo on Rogers. The dock opened up the default car mode, I hit the music app, then hit the audio button and the stereo received the signal. I am pretty impressed! :D

Tried using it to make a phone call and it only used the phone speakers tho... :(
[Captivate Android Development] loserskater:
I guess it's a start... now we just need to see what the app is doing when that button's pressed and how the kernel reacts
[Captivate Android Development] grkmaster:
I installed the car launcher and yeah i been using suckerpunch for a while now with the dock and xcals redirector and never a problem. The car home wouldnt open. It just shows on the top of the notification bar to deactivate and i tried to use a music app to see if i can get it to work and it was a no go
[Captivate Android Development] 60hzrumble:
Sounds like we need to re-open the bounty! :) Just got my dock today, knew it wasn't working quite yet on CM7 but I have a lot of faith in XDA.
[Captivate Android Development] xcaliburinhand:
An update for those interested, I am now at the hazy part:

This is where it gets a bit more hazy:

Investigate and replicate how the Samsung framework interacts with the sound framework when using the dock.

-May require an update to the asound.conf (asound.conf is used by the ROM to identify the sound paths available)

-Definitely require a CM7 specific version of the dock sound redirector app

I added the dock stuff to the CM7 kernel, and as I suspected forcing audio to the dock results in bass loss. The previous method I used to switch to the dock was builtin to the audio framework by Samsung, which is difficult to replicate without modifying the entire audio framework. I have a few ideas on how to get past this, stay tuned.

-x
[Captivate Android Development] InsaneJester17:
I've said it before and I'll say it again, you rock X! I finally got my vehicle back so I was going to return to Cog4 for dock, but I think I'll wait it out a bit and see what you can do. Thanks so much!
[Captivate Android Development] ctleng76:
I currently have Cog4 installed and for me the car dock audio still doesn't work. So I definitely would wait it out and see what can be done here.
[Captivate Android Development] loraque:
Works fine on Cog 4 for me. Works fine on every ROM I have tried thus far, except for CM 7. Which is understandable considering what Xcal has seen from the code so far. I have faith.

Make sure you are using Xcal's app. Ever since I found that gem, no need for the car home hokey-pokey.
[Captivate Android Development] InsaneJester17:
Didn't work for me with just the app on Cog 4. Throwing Xcal's Reoriented kernel on top of it then using the app did work for me though.

Loraque, are you using a different Kernel with Cog4?
[Captivate Android Development] grkmaster:
Xcal, im on my third JS7 rom and same thing again. This time around the sound outputs but I need to put it on high volume but the output is reallly really low. Not listenable at all.

Also the car home launcher (googles), does not work right either. Just shows a notification on top and thats it. I really want to know if anyone else is having issues.

Im on Continuum 3.5 now and SP#59 - iv used suckerpunch with your redirector on js5 and worked like a charm.
[Captivate Android Development] loraque:
I recently flashed Js7 Phoenix Ultimate from Cog... I just read DG's change logs, and he did recently change his kernel. If you flash an older Cog, I think I was on 4.1 when I left, he still had his original kernel which I assume was just modified from stock (stock 2.2 works just fine with Xcals app).

I see now that he has added all the i9000 goodness, probably based on the kernel for that I saw around prior... I bet they stripped it out on accident.

Since it worked when you brought in a guaranteed compatible kernel, pretty sure that is the problem- DG's new kernel lost the support.
[Captivate Android Development] loraque:
I am using Google's car home 2.2.1 just fine on Phoenix JS7 with none of these problems. If you are only getting the car mode notification in the bar, then I would uninstall Google car home and re-install. Flash Xcals kernel specifically too, to rule out kernel problems- not all of them work yet with the dock. I see in the Suckerpunch thread that he has support for it, so I don't know. I have run into at least one version of a kernel that said it supported it, but did not. Flash Xcals and see what is what. Then you know for sure it is not kernel related.
[Captivate Android Development] grkmaster:
By flashing xcals kernel would i be losing all of suckerpunch features? Also when i installed Phoenix 7 a couple weeks back I had the same problem as now.
[Captivate Android Development] loraque:
Yes, there are some features that Xcal does not roll into his. You can always flash to something else however, or back to Suckerpunch, once you determine if that is part of the problem or not.

EDIT- I did have to flash a USB Audio compatible kernel on Phoenix to get it to work. It did not with what came with the ROM. Currently running Xcal, though DG's Firebird 2 worked fine, and has most/all the features that Suckerpunch does. If you want the OC, you might want to try Glitterballs instead.
[Captivate Android Development] grkmaster:
Ill flash another kernel. It just seems weird because I was using Suckerpunch on Continuum's JS5 rom with no issue. if it is suckerpunch kernel then something must've changed for this to happen
[Captivate Android Development] grkmaster:
now my dock works. I installed xcal's kernel and decided to flash the two car dock zips instead of using the one I had. It didnt work.

So i decided to flash the suckerpunch voodoo kernel and i noticed when i docked it it said something about the audio is not being redirected. It didnt show that before, but my dock was working but no bass. So i enabled the options in the redirector and now my dock works like it used to. Im a happy camper :-)
[Captivate Android Development] xcaliburinhand:
v1.2 of the app has been published to the market

If v1.1 is working for you, v1.2 won't add any benefit. Also, I had to change the application key to publish it to the market so you may have to uninstall v1.1 if you are going to use v1.2

I will be submitting the kernel changes to the Team Hacksung CM7 kernel today. Once they are accepted and a new build is made v1.2 will allow dock audio with CM7.
[Captivate Android Development] loraque:
Really!? I have been wanting to go back to CM7, and now there is light at the end of the tunnel. Seriously looking forward to checking this one out. Thanks for the update Xcaliburinhand!
[Captivate Android Development] loserskater:
I've been checking your github everyday and I'm glad it's finally done! I can't thank you enough!!
[Captivate Android Development] grkmaster:
Dude you are the man. Now I have a reason to use CM7.. will donate as soon as I get on a computer! Appreciate all the hard work!
[Captivate Android Development] loraque:
I am curious Xcal if perhaps the kernel portions you have been working on may hold the solution to another dock related issue with CM7.

While CM7 does recognize the dock and start to charge the battery, it does NOT pay heed to the STAY ALIVE option to keep the screen on. This works with normal USB and USB power ok... it is just with the dock that it forgets to keep the screen on. Is any of this pin re-direction you have going on perhaps toggle whether the phone realizes it is charging and should STAY ON?
[Captivate Android Development] loserskater:
I know this doesn't really help the issue, but a temp fix is if you use Tasker you can keep the screen on while docked.
[Captivate Android Development] xcaliburinhand:
I believe the keep alive is done within the ROM framework, since the ROM is controlling the lockscreen and the backlight timeout. Something may be missing from the framework to support this.
[Captivate Android Development] loraque:
Ok. Just a thought. It does keep it alive under all other circumstance, it is just while docked that it seems to forget. I have been thinking of trying out tasker for other things... this is just one more reason to check it out.
[Captivate Android Development] grkmaster:
Im still on a JS7 rom and i tried downloading from the market and had a problem when it was installing-- " Package file was not signed correctly "
[Captivate Android Development] xcaliburinhand:
I had to switch app keys when I added it to the market. You have to uninstall the previous non-Market version.
[Captivate Android Development] grkmaster:
For redirector 1.2 to work on CM7 they have to implement it into their kernel, correct/ someone in the forums who has created custom cm7 kernels implements it?
[Captivate Android Development] xcaliburinhand:
Yup, still hasn't been pulled into the main CM7 Samsung kernel. I have seen the code get incorporated into a few other gits, but not sure if they correlate to any of the current custom kernels available.

You may be able to nudge a custom CM7 kernel dev into incorporating it, should be a matter of cherry-picking three commits.
[Captivate Android Development] loraque:
Looks like the trident underclocked kernel had this added, and it does trip the dock app. I traded in my lease last week, and the new ride has bt audio to sync to now, so I have not tested the audio out yet.

fyi for those waiting to try this with 2.3
[Captivate Android Development] DocRawk:
any news on getting the call audio routed through USB?
[Captivate Android Development] xcaliburinhand:
It's possible, you just need to use a custom kernel that supports it. I published the code Feb 25.
[Captivate Android Development] DocRawk:
Some of ytt3r's kernels state that your audio fix is included. It's working great for media. Is there a setting or something I'm missing in the redirect app to get call audio redirected?
[Captivate Android Development] grkmaster:
Its been on and off for me but usually on the dock its defaulted to speaker when u answer. Sometimes just clicking speaker to turn off and then turn it back on might work.
[Captivate Android Development] Espaa Valorum:
Sorry to revive an old thread. I'm having the "no bass" issue, and tried to figure out what to do, but i'm lost. I'm hoping somebody can point me in the right direction.

I am running Serendipity 6.4 (Froyo 2.2.1). I was using the Speedmod kernel. Then i bought the car dock last week. I got no audio out with that combo :( Then today i flashed Onix, since that kernel was often recommended for Serendipity, and it is supposed to have the audio out code. No dice though with that. Then i installed Xcal's app. That worked! But no bass :( So that's where i am now.

I read most of this thread, but i'm confused on what causes this issue, and how to go about attempting to resolve it. Anybody have any suggestions on what i should do next? Thanks!
[Captivate Android Development] Espaa Valorum:
I do get the phone call to play through the audio out. I have my headset plugged in to test, and it works. But it looks like the headset microphone is not used? Is the phone's microphone always used?
[Captivate Android Development] loserskater:
If it's in the dock, then the phone's mic is always used.
[Captivate Android Development] owe2003:
I've been scouring google to find a way to play my music from my phone through my car's usb, and I finally found this post. But i can't seem to get the app to work. My car just won't recognize my phone. Not sure what I'm doing wrong. I checked all the boxes in the app. There's button that also says Redirection off, but it's grayed out and i can flip it to on. the usb mode is set to mass storage.
[Captivate Android Development] VentureForth:
I, too, want to resurrect this thread because it has the right title. I'm not on Rogers and I'm more concerned about the home dock.

I have AT&T running Apex 9.0 with DarkCore 3.0 xxjvr kernel.

I have been trying since I bought my HOME dock 9 months ago to be able to use the headset jack on the back. Before I started flashing ROMs from here, I was on 2.1 which Samsung said didn't work. Been flashing i9000 ROMs since. I see through this thread that I gotta go back to an i897 ROM, which I did, but it didn't seem to fix the problem.

I've never been able to download Samsung's Home Dock from the marketplace whether I had i897 or i9000 ROM installed. I have an .apk I sideloaded from somewhere. It doesn't work either. Currently my default dock screen is Alarm Clock Plus.

In my Dock settings, "Audio settings while docked" is greyed out.

When I have "USB Debugging" checked, it automatically launches Alarm Clock Plus when I dock. When it's unchecked, it asks multi media mode, kies, or usb storage mode.

I would really like to get this dock to work so I can listen to my music at work and plugged in at the same time while still being at an angle that I can see it at.

Is there an AT&T ROM, Kernel, Firmware version, ANYTHING or ANY COMBO where I can get this stupid dock to work right?
[Captivate Android Development] 305Freak:
All you h ave to do is change to the Talon kernel. Darky's, although runs great does not support in call sound redirection. Make sure you also have sound redirector from the market installed. An XDA developer made it :)

I'm running Mosaic and they provide the Darkcore kernel by default. I hate having to change it and wish they supported the above mentioned feature.
[Captivate Android Development] VentureForth:
Just so I don't have to go trudging too far down dark back alleys, is there a non-dev Talon kernel that is best? I can flash from recovery on top of Darky's?

Note: Can't find Sound Director in the market.... :(
[Captivate Android Development] 305Freak:
Sorry I typed from my phone and it auto corrected...It's Dock Sound Redirector by Xcaliburinhand. As for a non-dev Talon, that's a little harder. Just read Existz's forum. Many say some of the last few are very stable. I find most of them to work just fine for me.
[Captivate Android Development] xcaliburinhand:
Has anyone asked Darky to incorporate the fix lately, it is just a few lines of code to fix the usb controller to work with the captivate.

-x
[Captivate Android Development] VentureForth:
THANKS!!!!

Still seem to have the Bass issue. But since I don't have a reference point to pre v.1.2, I can't really judge other than plugging into my headset jack direct which has noticably more bass.

Thanks for the apps, the kernels, and tweaks. I hope all the dev's incorporate this in the future.

Thanks 305Freak & XCALIBURINHAND!
[Captivate Android Development] RTBee:
I'm using DlevRom 4.2 and a Talon kernel. I also use the sound redirect from the market and all works great. If you want the non-dev version of Talon it would be 4.3 otherwise the others have been working really good. I'm on 4.4.15 right now and it's very smooth and stable. Just my 2cents worth ;-)