yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] chadouming:
My phone is acting exactly like the i9000. I didnt knew that verizon was CDMA, but flashing a verizon modem would'nt work ?
[Fascinate Android Development] thefunkbot:
yea but your thread has an attractive title and a lot of text that a lot of people wont read as thoroughly as they should, no matter how colorful you make it.

And yes, verizon is CDMA. Flashing this rom on a verizon fascinate is a brick. No ifs ands or buts.
[Fascinate Android Development] kennydied23:
The VZW fascinate and Telus fascinate are completely different in terms of hardware and software. One of the biggest differences is that VZW fascinate has a CDMA radio and the Telus fascinate has a GSM radio.

If it is just a I9000 rom with the hardware keys changed to work with the Telus Fascinate, then it won't work for the VZW fascinate (without a lot of hacking) because of the differences in hardware and software.

This.
[Fascinate Android Development] bobloblaw1:
I'm far from any sort of expert so please don't take what I say as gospel.

But I don't think that would work based on what the devs have been doing. I know that we have some hardware differences including radio, memory size, and partitioning. Also, I think SirGatez has been busy porting a kernel over from the i9000 so there are at least some incompatibilities there too I'd imagine.

Again, this is my own guesswork and from seeing people flash i9000 ROMS to their Verizon Fascinates and ending up with temporary paperweights. Maybe you have made a breakthrough...I certainly wouldn't be opposed to seeing the rest of what you have to say.

Regardless of the outcome, thank you for the effort and attempt at getting us GB.
[Fascinate Android Development] chadouming:
Changed it to let people know it won't be working on verizon, sry all.
[Fascinate Android Development] bobloblaw1:
Thanks for the efforts regardless. At least you Telus folks have something fun to play with :(
[Fascinate Android Development] chadouming:
Would have liked to help you out guys.
[Fascinate Android Development] BlackHoleSlam:
thank you for trying
[Fascinate Android Development] daoom:
DO NOT DO WHATEVER IS DESCRIBED IN THIS THREAD UNLESS YOU DON'T CARE ABOUT BRICKING YOUR PHONE

DO NOT FLASH BOOTLOADERS, YOU EVENTUALLY WILL REGRET IT

Remember people flashing ROMs which updated sbl.bin and bricked ****? Well, it's highly likely the same will happen if you follow the instructions posted by the OP. Not only that, but with download mode disabled after flashing there is no easy way to recover.
[Fascinate Android Development] SirGatez:
There is actually a keymask for Fascinate it is 0xFFFF & for most GSM SGS it is 0xFF, I figured it out when having issues with reversed back/home keys on my I9000 compile for Fascinate about 2 weeks ago. That is why back and home acted odd on Fascinate with an I9000 kernel. :-) If I remember right I think it is located in s3c-keypad.c or s3c-keypad.h enjoy!
[Fascinate Android Development] SirGatez:
Your right alot of things that fail to work because a few bytes of code or a flag missing, overall everything works source to source but there are lots of seemingly unimportant and small changes that are the difference between it works, and it.works great the way it is suppose to work.
[Fascinate Android Development] bobloblaw1:
Yup that seems it might be the case on jt's kernel built from mes source. Some people have working buttons and others have two back buttons.
[Fascinate Android Development] snufy99:
how am i suppose to flash this with jvk..no cwm..and this is a zip. not a tar.? for odin
[Fascinate Android Development] chadouming:
This is made to be flash with CWM and it is ONLY for telus SGH-T959D phone with a GT-I9000 Gingerbread rom installed on it. I'd suggest to not flash those rom, since as stated on first post, this will break your Bootloader making you unable to get into download or recovery by holding key at boot. This will NOT work on froyo as home key is seen as back key (ID 158) and not as another unused key.
[Fascinate Android Development] snufy99:
Ive found most I9000 and vibrant roms work, the issue with I9000 is the missing home key it usually acts as another back, With the vibrant roms just flash a I9000 kernal and modem and it works perfectly. The only other issue is sometimes with the I9000 some of them wont pick up wifi. I also use non boot loader versions so no trouble there. I had gingerbread working perfectly on the phone with everything working... I just didn't have this file as a .tar to flash through odin to get the home button. Currently I'm running a darky 9.3, stock+froyo+voodoo kernal, and i9000zsjpe modem...works great, quadrant scores in the 1500s. Anyways... do you have the file that i can flash through odin?
[Fascinate Android Development] chadouming:
Darky's 9.x rom series are froyo rom. This trick cannot be used with froyo rom. You would need to use darky's 10.X beta or another rom wich is gingerbread. This does not modify the key ID but the way the keys are being used by the rom. Currently, these file can only be flashed under CWM, which is added to voodoo gingerbread kernel. I'll leave the files to enter recovery the easy way on first post.
[Fascinate Android Development] madizmo:
chadouming, I love you.
[Fascinate Android Development] kenyloveg:
Anyway to make this work on latest MIUI build?
[Fascinate Android Development] chadouming:
This ain't gobna change anything, the keylayout is "included" in CM7 kernel. You need to build the kernel with a patch included. Try glitch kernel for telus fascinate. It will have all the button mapped and it work on miui :D
[Fascinate Android Development] raffness:
YES! Thank you. I've been looking for a solution for this forever. I didn't flash the zip, but I edited the left/right home/search key mapping as you suggested and it worked great.

Great tip!
[Fascinate Android Development] Grondinm:
so this is a shot in the dark. but would this work with the CM9 beta builds? I miss my home and search buttons?
[Fascinate Android Development] krarvind:
It should work. All it does, is replace a couple files under system/usr/keylayout. you don't have to flash the zip file in cwm, you can simply extract those two files, use root explorer to push and set permissions to rw-r-r, then reboot.I am assuming you flashed a GB I9000 rom ( before cm9) on it which messed up your key combo.
[myTouch 3G Slide General] Ekorshus:
Anyone else have problems w/ inop volume rocker buttons after installing CM7 or any other rom for that matter?
[myTouch 3G Slide General] sryan1983:
I noticed it not working on my wife's slide. Thought it was just me because I bought it off ebay.
[myTouch 3G Slide General] Ekorshus:
Yeah, weird.... See, if I sit there & jack around w/ 'em long enough, they'll eventually come back to life & then be really responsive for a while thereafter...

But if I leave 'em alone for an extended period of time... I have to jack around w/ 'em again to get 'em to respond...
[myTouch 3G Slide General] krapt0:
The only problems I have been having with cm7 is buggy wifi.
[Captivate Q&A, Help & Troubleshooting] Deviver:
Brand new captivate that is i896 (not sure if this matters) and is running on froyo. Today i noticed when updating my Beats songs. that the amount i could put on the internal sd card was limited to approximately 2Gb while the sd card still had 10 gb free. anyone know how to fix? thanks in advanced.
[Captivate Q&A, Help & Troubleshooting] mechanical tool:
Its a bug in the rogers 2.2 froyo release, heres a thread about it:

http://xdaforums.com/showthread.php?t=907854

There are no perfect solutions there, but there are some work arounds. If you want to flash a new ROM that will also fix it.
[Captivate Q&A, Help & Troubleshooting] Deviver:
ah tyvm ;] i searched for about 30 minutes before i posted but i guess im just bad xDDD

im a bit worried about failing at flashing the phone (dont want to do anyting without reading ALOT about it but i currently have no time for that) so i'll just be using kies for now =\

thankyou once again
[Droid X General] V1215:
So I've noticed recently that my screen on my CPO X has gotten a faded spot about an inch from the bottom of the screen. It hasn't reduced functionality or anything, it just... urks me, lol. Anyone else have this, and do you think Verizon might help me out? It makes the device significantly less attractive.

D: Also, only visible when the screen is on on a white page, but still.

Haven't over heated the phone once nor dropped it, running SetCPU at 1000 max 600 min.

Running on rooted stock, also.

Sent from my DROIDx
[Droid X General] beepbloop:
had this on my original and refurbished droid x, quite strange
[Droid X General] V1215:
Think I could get a new one if I ***** about problems with responsive problems? XD
[Droid X General] jenna728:
I have this same problem in the same spot. Its really annoying lol
[Droid X General] V1215:
*problems with responsiveness?

Sorry, typo. Anywho, yeah, very annoying. It's only my second Android device, too- I came from the HTC Eris. :P Probably no way I can fix it, either.
[Droid X General] Jmoney47:
You might as well talk to Verizon about it. There's nothing you could lose from that
[Droid X General] jenna728:
The screen works as it should, theres just a bright spot on white or light colored backgrounds.

I just traded my Incredible for the X. I really like this phone but this spot is driving me crazy! I wish I could fix it somehow.
[Droid X General] V1215:
I may have just found your post on DroidForums about the same issue.

Did you ever contact Motorola, by chance?
[Droid X General] chbennett:
Same exact problem here. I talked to my guy at verizon and he saidd it for sure falls under a warranty replacement for a refurb phone. But it doesn't bug me enough yet to make me do that. I'll wait until my one year is almost up then replace it.
[Droid X General] jenna728:
Yes I did but I don't have the receipt, the guy I traded with said he will take care of it. Hopefully they'll replace it for me. Its not a huge deal but it gets on my nerves.
[Droid X General] zwade01:
I have what appears to be a dead pixel at the top right of my screen. It's a CPO and I received it this way. It has bugged the **** outta me since I got it. It was a replacement phone because the first one wouldn't stop rebooting. I think I'll call and complain as well, but I don't want my third X to have some other problem lol.
[Droid X General] tyvallely:
That's what I do and it seems to work. :D :p
[Droid X General] rocko73:
Where exactly is the spot? Can you post a pic?
[Droid X General] V1215:
About an inch from the bottom of the screen in the center. And I will try to get a picture as best I can.
[Droid X General] jenna728:
Try Jscreenfix, its free on the market, let it run for like 30 minutes... It fixed a dead pixel on my Droid 1.
[Droid X General] V1215:
Will try, but I don't think its a dead pixel. It just looks like a half inch wide faded spot.
[Droid X General] jenna728:
Oh I was replying to zwade... Jscreenfix won't work on the spots:(

I'm sending mine out to Motorola soon.
[Droid X General] V1215:
Was gonna say... good thing I'm not epileptic! :D
[Droid X General] V1215:
Sorry, double post. Can't seem to get a picture of it... but by god it's there. <_<
[Droid X General] jenna728:
I hope they fix mine or give me a replacement.

I was playing with my friends new DX today and his screen looks so much better than mine for some reason, my screen looks really washed out and it has the ugly spot. Maybe by the time I get it back Gingerbread will be out:-)

Are you gonna send yours in?
[Droid X General] zwade01:
Thanks for the awesome referral, I had no idea such an app existed! Unfortunately, I am thinking it may not actually be a dead pixel though... it didn't work and I've noticed that when I turn my phone on an angle, the black spot moves on the screen as I tilt it (like maybe it's a needle-tip-sized scratch).
[Droid X General] V1215:
Suppose I should, lol.

Can I get some instructions? Would research, but I'm kind of lacking in free time anymore (damn you, full time!). I'm assuming I have to contact Motorola somehow first.
[Droid X General] jenna728:
I just went to Motorola.com/repair
[Droid X General] dsims91:
I think that it is a manufacturing flaw i have the same thing, and also observed it on two other DX's, a guy at work look like he has something pushing on his screen from behind in the very same spot.
[Droid X General] V1215:
Yeah, I kinda thought the exact same thing.
[G1 Android Development] jianC:
Downloads here: http://www.neopeek.com/viewtopic.php?f=14&t=6507

Pretty much as stock as you can get it, if you want to create your own line of roms based off this.. Doesn't seem like that google supports these old roms anymore for the sake of server space (the sources seem to be deleted)
[G1 Android Development] Effdee:
since dalvik-cache is stored on /data , how do you go about not wiping dalvik-cache but still wiping data ?

wiping data will wipe

dalvik-cache

rotate-settings

battery-stats

since they are all stored on data
[G1 Android Development] jianC:
See: http://xdaforums.com/showthread.php?t=637419

I understand what you mean, but the recovery "wipe dalvik-cache" function wipes more than it needs to (the dex files), and causes the rom to crash. This often occurs on 1.6 roms, but not in 2.1+.
[G1 Android Development] edward0119:
can it be run on 2708? just no 3d?

For use with 2708 RADIO

See this post: http://xdaforums.com/show...3&postcount=43

the link can not be opened
[G1 Android Development] jianC:
yes, it can run 2708, just flash kernel after install and it will work.

Link here: http://droidbasement.com/db-blog/?p=1563
[G1 Android Development] Effdee:
ahh I see

it is not a problem at install time, and is only a problem if lame symlink hacks have been used to redirect the dalvik-cache from cache to some other place, instead of using the dex to data only prop

you don't link any of your source as per http://xdaforums.com/showthread.php?t=755506

well, dex never goes to /cache, so symlink hacks are not required, so wiping dalvik-cache with RA will not be an issue

problem doesn't exist
[G1 Android Development] ezterry:
Why is hw3d broken I know not.. least if you use a 2708 kernel.. you can use the original 10mb hack on the 2708 kernel with broken 3d but working camera but that seems silly.

You can go back to my 2708+ kernel thread and look up the old builds kernel.. in theory hw3d+camera will work unless you are having other issues with newer kernels and hw3d on the older rom.

FYI the old builds kernel has an alternative memory map that correctly maps hw3d for 2708, and maps 8mb for camera rather than the 5mb in froyo. (This is needed for the older libcamera's.. if you are re-building from source you may want to see if you can shim in the froyo libcamera)
[G1 Android Development] Effdee:
I think he is just getting things confused, like with the dalvik-cache wipe thing.

saying that problems exist when they don't

to clarify I'm reffering to this

unless I missed something and there are 2708 kernels which give extra 21mb ram?

from what I understood your 2708 kernels for older 1.6 builds gains 11mb instead of 14 with 2.2+ ( due to the required cam mem,as explained above )

and the 10 mb ramhack is completely different where memory allocated to the gpu is mapped to system instead, so it makes sense that 3d would not function (the gpu has no memory )
[G1 Android Development] ezterry:
I've been a bit too lazy to create/release it .. but in theory I could make a build with

15 + 5 + 8 =28mb on top of a regular 1.6 stock kernel by breaking both hw3d and camera

15 = 2708 ram changes (I say 14 elsewhere because newer froyo kernels have another ram hack to regain 1mb on all ebi0 radios/spls..

5 = camera ram

8 = EBI video region (hw3d)

This may need 1.6 but be interesting for the ram.. or those wanting more of just a embeded linux device
[G1 Android Development] Effdee:
the camera is interesting, the cam on the g1 is awful anyway so this ram might be put to better use as system ram.

I'm just wondering how much ram the cam would need for barcode (QR) scanning, as I would miss that ability.

might have a poke around myself and see what I find
[G1 Android Development] R3N0V4D0:
omg ive been asking for this for a while now.. but nobody answered... would love to see this get done :)) i wish i know how though.. :/
[G1 Android Development] nagash91:
A good think would be 15 + 8 = 23mb with camera working and 3D broken :D
[G1 Android Development] jianC:
apps2ext seems to be broken in R1. Update soon.
[G1 Android Development] jianC:
Hmm.. I see, although it has proved problematic for me to wipe dalvik-cache via recovery, so let's just leave it at that..

The source is obviously from google, as it is "AOSP" Android Open Source Project, which is from google.
[G1 Android Development] Effdee:
so you made no changes?

guess we are better off using an established 1.6 in the rom bible then
[G1 Android Development] Infinimint:
Some people prefer "pure" AOSP.
[G1 Android Development] Effdee:
when it comes to donut it seems most prefer cm4 or superd
[G1 Android Development] Infinimint:
Whats great about this is that it gives users more options to choose from when selecting a ROM.
[G1 Android Development] jianC:
Its the community's choice, I won't get butt-hurt if no one downloads my rom. I *know* that there are CM4 or SuperD roms out there, and I have tried them all, and they are good and fast, and I'm not ashamed to say that my rom is rather basic/buggy. If you want to continue trolling this thread to make yourself feel better, and make me look like an idiot, you are more than welcome to...
[G1 Android Development] Effdee:
trolling?

I just pointed out that your advice on not wiping dalvik-cache was contradictory as you said you *must* wipe data which will also wipe dalvik-cache.

I wasn't trying to make you look like an idiot. That would be a waste of time as you are doing that all on your own.

and if I *really* wanted to troll I would sign up to the competing forum you advertise in the op

I note you have asked for the thread to be deleted, which is probably a good idea as you violated the rules regarding source code and gpl

but would be a little unfair as the thread evolved, as a result of more miss information from yourself, into a think tank regards memory in the different kernels.
[G1 Android Development] R3N0V4D0:
omg please anyone?!?
[XPERIA X10 General] sharathx10:
Hello everyone

I know this thread has not important purpose.

But I just wated to ask some of the XDA members who are also working in SE development team.... what was their and their colleagues' in SE team reaction to the bootloader being bypassed...

Was there any blame naming or a solution finding tasks....

As in total was there panic or were they prepared that this day would come?
[XPERIA X10 General] caifanX10:
As SE is technically deprecating X10 and the other first Xperias, and they're focusing in Arc/Neo/Play, they shouldn't have a negative reaction about it, unless they're afraid that ppl is not going to buy the new Xperias just because bootloader is bypassed, but thinking in that way would be a mistake (one more...), particulary if they stated that the new phones are good and fast enough; under that point of view, a custom ROM won't be needed, so bypassing the bootloader shouldn't be necessary and there should be nothing to worry about, new Xperia owners would rather to stick with SE stock ROM.

So, I believe that the reaction from SE shouldn't be hard, they will only say something like "we encourage people to keep using stock ROM because is better, improves a lot the UXP and blah blah" or something like it.
[XPERIA X10 General] admartian:
So has the bootloader been bypassed?
[XPERIA X10 General] The Gingerbread Man:
Read here http://xdaforums.com/showthread.php?t=726813 but don't post on this thread unless you know what you are talking about and are a dev. Go here http://xdaforums.com/showthread.php?t=1001308 for discussion.
[XPERIA X10 General] MJ_QaT:
Why would they be annoyed or bothered?

Every developer knows that there is no 100% security on software world. The bootloader will be solved sooner or later and they know that :)
[XPERIA X10 General] pngface:
What can be locked can be unlocked :) or in this case, bypassed
[XPERIA X10 General] fiscidtox:
I don't understand threads like this yet. It is still in a very early stage, will probably be months at least before we can really benefit from it. By then the arc/play/neo will probably be orphaned just like the x10...
[XPERIA X10 General] agentJBM:
What is with other members creating threads attempting to get attention from SE for other dev's work, or representing themselves like they are embassadors for xda?

Did you even think to ask Bin4ry if he wanted their 2 cents yet? It seems to me that calling out the SE devs like this can only insult their pride leading to even deeper security measures in the future making things harder for the devs. Think about it! Don't instigate them.

On top of that, let the devs get it working even a little bit before you start advertising it, or trying to rub it in SE's face.

Total panic? It's not like we broke the launch codes for a nuclear weapon.
[XPERIA X10 General] Bwyan Benton:
+1 i agree

However, when this does get working id love to hear what SE think.
[XPERIA X10 General] aroutis:
What I think is we should be grateful to the guys that spend endless hours to do what they do for this cell phone ( I am talking bout the xda guys ) and as others said , rubbing things like this to SE makes no sense.

And no, I don't care to listen to what SE has to say bout it. If I were SE, I would not like it and from SE's perspective it makes perfect sense. So, the less people rub things like that to them , the better.
[XPERIA X10 General] Vito Andolini Corleone:
+1
[XPERIA X10 General] icet925:
Of course SE is not going to like it.

It's kind of like locking something in a safe and some guy crack the code for it breaking in. I agree with the posts above, no need to rub it in their face.

I don't understand why they lock the phone potential in the first place?
[XPERIA X10 General] shahkam:
By the time we get 2.3.3 gingerbread released and confirmed by se i guess they will be done cracking it or at least lets hope! ;)
[XPERIA X10 General] Hobbes2099:
I'm just waiting for GeoHot to upload a YouTube video explaining how they same encryption key he found in the PS3 is the same used on all SE phones.

cut scene to: every SE Employee doing a *facepalm* at the same time.
[XPERIA X10 General] s4linux:
I like that xD
[XPERIA X10 General] mister-g1:
perhaps hacking the bootloader made SE a bad consience about their user support so that they decided to bring gingerbread to the x10 now... who knows^^
[XPERIA X10 General] truefat:
You really need to get a grip on reality. The idea that a stupid thread would have such an impact is preposterous
[XPERIA X10 General] DeViL_DiCe:
Although i understand why Sony is pissed at GeoHot for unlocking the PS3 (since it provides access to piracy), i can´t understand why SE would be as pissed with the X10. Unlocking the X10 doesn´t allow us to pirate software. We´re all using free software or pay for the apps, and we would still do it in the future.

Geohot discovered the keys to the PS3 (money, money, money.... ups the key got leaked... i mean, i discovered it!), but the same will not happen with the X10. Not only is the process quite different, but after what happened with the PS3, i can guarantee that the key won´t be leaked (or found by a famous hacker).

This thread doesn´t even tickle SE (nor the hundreds of threads about progress on the bootloader). What causes an insane itch on SE, is the fact that the dev's are going in the right direction. I know that the unlocking of the X10, or the Arc, Neo, etc, doesn´t cause any serious problem. I cannot say the same about Xperia Play. If this phone is developed the same way as X10, Arc, etc, piracy will be again enabled on the Play, therefore causing huge losses on the software houses.

Eitherway that´s my point of view...
[XPERIA X10 General] Pawnty:
Our devs are great :p They worked so hard at finding the key to unlock the door, and stumbled upon a way to go through the window XD