yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Fit GT 5670] -HellRaiser-:
First of all i didnt understand what you meant by mentioning me and aspire in your description.i cant figure out if its positive or negative.....but if its something negative and if i may have hurt your feeling in any way then i m sry for that.....
[Galaxy S II Q&A, Help & Troubleshooting] Mafiatounes:
Good news guys here is the link to the source code of the SGS 2 (ICS)

Just type i9100 in the searchbar and it's the forth link from above!

https://opensource.samsung.com/index.jsp;jsessionid=2BEF00E835DF113376066DE8FDD377E7
[Galaxy S II Q&A, Help & Troubleshooting] crachel:
This isn't original development.

Closed.
[Samsung Epic 4G Touch] nabbed:
Well, maybe two and a half.

I was using FB17 on my old black ET (bought on launch week), before it was bricked.

GPS would not connect. Vlingo was very broken - would not work with a bt car kit unless you manually unlocked the screen.

It was very snappy in my testing though.

I now have a brand new white ET, and I tried FC14.

Exact same problems. None of those were fixed in the last 3 1/2 weeks.

Thank god someone has figured out that you can simply remove vlingo garbage and replace it with a number of dialing apps like google voicedialer. I don't know if it can be done on ICS, but it works very well in EL29 gb roms.

So, GPS is a deal breaker right now, possibly on two somewhat different versions of hardware (old black et vs white new et.) What the hell are the developers thinking not fixing gps?

Also, FC14 was noticeably choppier than both EL29 and FB17. Maybe it was because of the particular widgets/software I used, I don't know. Could be a problem too.

Anyway, any thoughts?
[Samsung Epic 4G Touch] ronny71:
When I started flashin ICS Roms...Couldn't get a lock or very spotty coverage...I tried all the Apps out there for GPS...None worked...What worked best has been used by many people on here...for me it worked the first time and I always get a lock...Here's the deal...

If you are willing to take the time to do it, this seems to work for everyone:

Odin one click back to Gingerbread

Odin flash kernel w/ recovery

Restore nandroid (optional)

Get GPS lock on Gingerbread and keep it on.

Boot to recovery and flash format all zip and ROM.

So Odin one click back to el29 GB...

get CWM there as well...Get your lock...leave it on...Go to CWM...restore your ICS Rom of choice...Reboot...ICS will open up and you will have GPS lock...works everytime...At least it has for me and a lot of people on here...

GPS was the Deal breaker for me as well...I use it a lot...Now I have an ICS Rom for my Daily Driver...:cool:
[Samsung Epic 4G Touch] coiledwire:
Well GPS hasn't been a strong point for Samsung in general. The devs your referring is Samsung, right? They have the necessary tools, like source code and non-gpl drivers. I'm pretty sure Samsung will get GPS better on ics at some point.

El29 is very refined. I would totally expect it to run smoother than any ics leak at this point.

I don't use any car/voice mode, so I cant comment on that.

Sent from my SPH-D710
[Samsung Epic 4G Touch] nabbed:
It works for a while. Then you lose gps again. It's too much trouble flashing and reflashing, whereas it should just work.

EL29 calks roms is very nice and smooth. Everything works, with a proper theme it looks a lot like ICS. It's just not worth it putting up with ICS bugs right now.

The only thing I'm really missing from ICS was the browser.
[Samsung Epic 4G Touch] Esoteric68:
In the two days I've been running FC15 I've experienced none of what you mention. I think it's the luck of the draw with hardware/software and sprint service in your area. Are you updating your profile and PRL after flashing new modems?

FC15 is the smoothest build I've experienced since EL29 (which remains my goto version if the current ICS build doesn't do the job).

Did you do a complete wipe before installing? Did you make sure to flash the full rather than the nodata version if going from GB to ICS?

I'm certainly not insinuating you are incapable of knowing how to flash new builds but sometimes we overlook the simplest steps which leads to major complications.

If you've done all the above (including using Calkulin's format all) and still experience these issues then I'd definitely stick with EL29 for awhile longer.
[Samsung Epic 4G Touch] The Root:
My gps locks faster than ever. It's insane. I used gps all over CT, RI, and MA this weekend and was perfect. Didn't even get confused by 95 exchange in Providence.
[Samsung Epic 4G Touch] nabbed:
Yeah, I've done all those things and even more you never heard about.
[Samsung Epic 4G Touch] musikalharmony:
Of course el29 will be smoother it's an official release. It isn't the developers fault GPS is goofy on ics either they been working hard to fix it... maybe you should read the bug list before you flash anything. Nothing will be completely stable until an official release is out thank the devs they got us this far and at least we can use most ics roms as a daily driver... a couple months ago no one can even get ics to function now look were we Are.
[Samsung Epic 4G Touch] nabbed:
I was talking about Samsung developers, not xda developers. Maybe I should have clarified. But I thought it was self-evident, since there's no source code for ICS available yet (and probably won't be for months.)

As for bug lists - ICS roms threads simply don't have them. So please don't patronize and act all butthurt for no reason.
[Samsung Epic 4G Touch] Esoteric68:
Well if you've tried all those and many you 'assume' I've never heard of then I think you've answered your own question.

Stick with EL29 until the official ICS is available. With any luck we aren't far off.
[Samsung Epic 4G Touch] nabbed:
It's hard.

The flashaholic in me wants to try fc15. I know gps wont work in it, from the review qbking77 posted. But maybe it will be as snappy as FB17 was...

BTW, when is the official Sprint ics release due?
[Samsung Epic 4G Touch] The Root:
FC15 gps does work. I'm getting a lock right now on 8 satellites.
[Samsung Epic 4G Touch] nabbed:
It doesn't work for qbking77, so I assumed it won't work for me.
[Samsung Epic 4G Touch] Esoteric68:
It is hard to not flash and I'm only a recent flashaholic (boy do I wish I'd paid more attention to XDA when I had my EVO 4G, would've saved me the mistake of buying the POS 3D).

After FC07 I was going to stick with EL29 until the official release came out but then the 13, 14 and 15 leaked builds came out with overall good reviews so I dove in again and so far I haven't regretted it.

Official release date, who knows, this is Sprint after all but with the leaks coming fast and furious common sense would dictate it can't be too far off (at least we hope).
[Samsung Epic 4G Touch] ronny71:
Believe me mine works...EveryTime...Im runnin on FC14 at the moment ...didn't think there is a need to update to 15 since 14 is runnin fine...Everything runs on My Rom...But like I told ya if GPS didn't work Id be back on GB...Right now Im runnin an EL29 Modem on MIJJz BLEND ICS "THE GOODNESS" 2.3...IMO its the hottest ICS Rom out there hands down...Its smooth quick snappy...uou name it...With functioning GPS for me...But if you think you'll be happy with GB go back...Im stickin with the ICS leaks till the final and I think they are Damn close...:cool:
[Samsung Epic 4G Touch] Toleraen:
You are aware of the difference between "unknown dev-state leaks" versus "official releases", right? Also that devs post leaks for us to test and report back bugs, of which there are multiple threads containing these lists, right? The issues you report have been answered in several threads, several times.
[Samsung Epic 4G Touch] Compusmurf:
My gps has worked in every FC ICS build so far. (Lucky me I guess)

Few things that don't work, error out.

Accuweather daemon sometimes FC's.

Moving apps to SD card a bit wonkey. Currently doesn't move them to the ACTUAL SD but to "usb storage" on the phone. FC15 only.

A handful of apps still aren't compatible with ICS. (NOT the rom fault).

Signal bar info isn't correct on any build pre FC15.

Market sometimes takes awhile to actually start downloading apps.

GPS sometimes doesn't turn OFF. <- eating your battery VERY quickly.
[Samsung Epic 4G Touch] nabbed:
I wasn't reporting anything. I was just reflecting on how in 3.5 weeks of my absence, the most blatant deal breaker bugs have not been fixed.
[Samsung Epic 4G Touch] I_FLY_Z3R0:
I've never flashed an ICS rom but I use FC15 modem with blazer 4.0 and It's possibly the best modem I've used with this phone. Smooth as can be and what seems to be better data speeds than the other modems.
[Samsung Epic 4G Touch] ronny71:
Im on an ICS Rom...just flashed FC15 for test run...

I see 17 and 19 are due out soon...:eek:
[Samsung Epic 4G Touch] I_FLY_Z3R0:
Sounds good! Hope it works good for you

Sent from my iPhone killer.
[Samsung Epic 4G Touch] luckychef28:
I get the OPs frustration, but we're all guinea pigs in the ICS game right now. And this little piggy has fleas. I am honored and thankful to Sextape, Sfhub, Calkulin, QBKing77 and all the others who have made it possible for me to experience some ICS awesomeness months before the official release.

1. Assuming because something didn't work for one user, doesn't mean it won't work for you. On one build QBKing didn't have notification sound, but it was never a problem for most, including myself.

2. GPS is s persistent bug, but mostly functional (even without a workaround) by account of many users.

3. A thread search for "xxx bugs" will pull up dozens of threads on all the issues in all the builds. Some have remedies, some don't. Rather, some people have had luck with remedies, some will just be SOL.

4. Search. Read. Search. Read. Search. Read.

5. It's beta. Love it, like it or skip it.
[Samsung Epic 4G Touch] iSaint:
There's a reason why these are leaks and not the final OTA build.

;)
[Samsung Epic 4G Touch] nabbed:
So they'd better get cracking.

My biggest concern right now is what the hell they broke between FB17 and FC14. I installed FC15 last night, I played with it for a few hours. I was able to get GPS fixed by using the trick (don't know how long that will last). I was able to get vlingo removed and replaced with voice dialer.

Now, I still couldn't get FC15 running smoothly like EL29 and FB17. Both FC14/15 are now noticeably choppier than those other builds...

Grrrr!

Had to nand restore back to EL29.
[Samsung Epic 4G Touch] Epix4G:
No these are not OTA releases these are leaked builds go freaking complain to Samsung not the devs here that are working on these for FREE ....you don't bite the hand that feeds you....you need to be more respectful and appreciative ...you would not have any ics except for the great people here .... Samsung hasn't given you anything
[Samsung Epic 4G Touch] iSaint:
They're getting close but I wouldn't expect a final build from them soon honestly.
[Samsung Epic 4G Touch] RainMotorsports:
So what bugs on 2.3.6 are you looking to have fixed? That's what you are entitled to. The free upgrade to a new operating system has not even been offered for your device at this time. No bugs to be fixed there.

Personally GPS has been working since FC06 and FB15 definitely works well. Calk has FB18 at the moment it will probably drop soon.
[Samsung Epic 4G Touch] nabbed:
I don't quite understand the purpose of this type of posts?

Are you people happy with how fast things progressing and you wouldn't even want things to get moving faster?

What are you saying exactly? Are somehow worried about the feelings of Samsung developers, who by the way get paid to fix things from the money we paid to use their products?

Now, if you were talking about unpaid volunteer work of people here on XDA, I'd understand. But that's not the case here...
[Samsung Epic 4G Touch] nabbed:
I wasn't talking about XDA developers, you wonderful person. They don't have the source to work with. What are you on about?
[Samsung Epic 4G Touch] Epix4G:
Of course they don't have the source you wonderful person Samsung doesn't have to release it until after they have released a OTA and then they have a certain time But its generally quick...the only ones that will see you exclaiming are the free xda devs that you continue to ostracize... Done with this..have a good day may you learn something
[Samsung Epic 4G Touch] :
Calkulin has FC18 just not released it to the forums.
[Samsung Epic 4G Touch] nabbed:
Did he ever say anything about adding bling to any other ics test builds like he did with fc07?
[Samsung Epic 4G Touch] atlantadude1972:
I'm on Calks FC15 stock rooted deoxed ROM...and it's smooth as butter...I have no GPS issues...But I never had GPS issues like many others...

I find it much smoother than EL29...

I do have the notification issue...Where if you go silent and then turn the sound back up you need a reboot in order for notification sounds to come back...And my voicemail is messed up...It didn't seem to like google voice and I uninstalled and my voicemail is wonky...But I feel FC15 is a great daily driver for me...as I feel we're close to an official update...

jb
[Samsung Epic 4G Touch] nabbed:
Hmm, interesting.

I forgot to mention that I was using an ics stock launcher on aospmod version of FC15 when I noticed lag. Were you by any chance using TW launcher and it was smooth?

P.S. I haven't tried going silent and then back. But Google Voice worked just fine on that rom.
[Samsung Epic 4G Touch] jerdog:
Guys the immaturity here is really getting annoying. Why people feel the need to be abusive and argumentative on the Internet is just mind boggling. Don't feed trolls; be respectful.

Now the complaining about things not working in leaks - you have the right to complain. But you also have the right to sit down, be patient, and flash whatever you want. YOU accept the risk of messing with your device and deciding not to use it in the way Samsung and Sprint intended you to. Don't blame anyone else but you. You want to get support from Samsung for their release? Go back to the OFFICIAL release.

Any more trolling or abuse and I will shut this thread down and hand out short vacations.
[Samsung Epic 4G Touch] d.e.beatup:
I can't speak for anyone else but I can confirm for me personally my GPS issues were 100% hardware related. I only was able to get a lock on my first E4GT literally 2 or three times since getting the phone in November. After I bricked it earlier this month, I got a brand new, non-refurb replacement and immediately got a lock with 11-14 satellites in GB or ICS. While I do get the lock before flashing ICS to be safe, I'm sure it would lock even without the "trick".

I think a lot of us plain & simple received phones with less than stellar GPS chips, but that's just my opinion.
[Samsung Epic 4G Touch] RainMotorsports:
Seems to be the case for a moderate percentage. These builds did have GPS issues, FC06 was the first one to me to work out of the box but the previous ones all did as well as FC06 using the GB trick.

FC13 and up don't seem to have the issue with continuously trying to lock if it fails. I justs did FC18 my last couple hours at work so played with the GPS on the way home. Seems to be another winner for those who had luck with FC06/FC07.
[XPERIA X8 Q&A, Help & Troubleshooting] estonia1:
Can someone shere offical kernel and rom?
[XPERIA X8 Q&A, Help & Troubleshooting] Saipro:
A search within the forums usually yields good results but since Matt 7:7 says it, here:

X8 ROMs & Kernel repertoire
[XPERIA X8 Q&A, Help & Troubleshooting] TSSICU:
Saipro

WOOOOOW

This is not only a stock rom

But this file contain a great collection also

Thanks
[Sony Xperia P, U, Sola, Go] piflechien:
Now that I have root, i would like to be able to unlock the screen with the menu button, just like I did on the xperia Ray or Arc by using the menu unlock (for root) application: https://play.google.com/store/apps/...wsMSwxLDEsInRlYW1kb3VjaGUua21vYnMudW5sb2NrIl0.

But it doesn't work, it's like the capacitive button are inactive until the screen is unlocked, so the mod doesn't work.

I heard that we can place an empty file somewhere to enable the menu unlock, but i'm afraid that's already what the menu unlock app is performing.

Has anyone an idea on how to make this work (without using a lock replacement application that never works properly).

I tried to replace the WAKE_DROPPED to WAKE on the menu button but still no success.
[Sony Xperia P, U, Sola, Go] footyfanatic:
Hi guys, I have found a workaround for those having trouble with installing drivers for fastboot in Windows7. This process requires you to do things in the right order and to be quite fast during some steps, so it may take a couple of goes to understand what you are doing before you nail it. First let me explain what seems to be the problem, to help you understand the method I about about to share with you:

It seems that if the drivers aren't installed in Windows7, the Xperia S will disconnect from fastboot mode, and go back to charging. What we need to do is install drivers in this small time period it does connect to your computer.

The solution to this problem will involve being quick at two stages of this process and I will note where these times are as best I can.

Both these stages are when we connect the phone to the computer in Fastboot mode.

Steps to install drivers:

1. Open device manager

2. Connect you phone in fastboot as normal

3. As soon as you plug your device in, ignore any messages stating the driver did not install and look in device manager for the new device 'S1Boot Fastboot' . Right click this and click 'update driver'. This is the first stage you need to be quick at. As soon as you click this and the update driver window pops up you can relax! You can let go of the volume up button now also, as the device will disconnect in the background anyway! You can also unplug the phone now too.

[NOTE: If windows is still trying to install this device, you won't see update driver until it stops/fails. This is when you have a few seconds to click update driver, so be quick!]

4. Click 'Browse my computer for driver software'

5. Click 'Let me pick from a list of device drivers on my computer'

6. Click next with 'Show All Devices' highlighted

7. Click 'Have disk'

8. Click 'Browse'

9. Go to the the .inf file and open it

10. Click 'ok'

11. You will now have a list of three models. Select 'Android Bootloader Interface'. (It is easy to miss this step out and accidently choose the default model so make sure to select it correctly!)

12. BEFORE you click next, we need to get the phone connection ready again, this is the second stage where quick actions are required.

Disconnect you phone if you already haven't. Connect the phone once more in Fastboot mode. As soon as it is connected click next on the window to install drivers

13. If you followed this right you will have installed drivers before the phone had time to disconnet

14. Now that the drivers are installed for the Xperia S, it will no longer disconnect from fastboot mode and work as it should! :D

Now contiune to follow Sony's guide ;)

I hope this helps you fellow Xperia S users that have problems!
[Sony Xperia P, U, Sola, Go] shmoejoe:
The solution has already been found and posted. I know you mean well, but use search :)

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

For Win7 x64, the Arc drivers are needed otherwise it appears the drivers aren't read properly.

For Arc drivers see last page as the first post isn't updated yet.
[Sony Xperia P, U, Sola, Go] Efe64:
Thanks! Was looking for this
[Sony Xperia P, U, Sola, Go] xach:
Also, for 64bit system, make sure in the android_winusb.inf you have the following entry under

[Google.NTamd64]

.

; SonyEricsson

%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE

%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE

Apparently some versions of the inf only have that under

[Google.NTx86]

.

You can copy and paste it in the same format as the rest of the entries.
[Sony Xperia P, U, Sola, Go] footyfanatic:
Sorry. I don't need to use search as I already read (and just re-read) this post and still had problems.

And seeing as this is a different solution, and quite detailed for those not too familiar with Windows, it may help.

Even means users can use the files all from the official sites. If users search for this in the future, member posted files may be deleted, like I have found on numerous occasions.

Next time, I'll keep it to myself
[Sony Xperia P, U, Sola, Go] shmoejoe:
No reason not to share it. it is a bit easier to read through than dooms instructions, just don't open threads when it could have been easily put in the existing thread :-)
[Sony Xperia P, U, Sola, Go] footyfanatic:
I see :)

I guess I should have stated, but I couldn't reply to the thread as it is in the dev section and I have less than 10 posts :(

I would usually help more, but usually with the amount of time I have to browse the forums and after searching, someone already has a solution! I guess this is only a good thing!

Maybe it could be added or linked to if necessary
[Sony Xperia P, U, Sola, Go] Sorel7:
Thank you footyfanatic:

Do you mind if I translate your solution and I post it in HTCMania? a user of that forum is having problems to install his phone's drivers.
[Sony Xperia P, U, Sola, Go] footyfanatic:
Yes this will be fine:)
[Sony Xperia P, U, Sola, Go] Evil_Sephiroth:
Not work for me..phone continue to disconnect on my eeebox (work percect and bootloader unlock on my main PC) WHY ,_;

On eeebox Win 7 home premium 32 bit

On main Win 7 ultimate 64 bit

EDIT UPDATE

Worked for me if I select Android ADB interface and not Android Bootloader Interface
[Sony Xperia P, U, Sola, Go] Efe64:
You saved my life! Many thanks!
[Sony Xperia P, U, Sola, Go] ariparx:
Thanks a lot! been trying for days and i dont have any XP machine,

Regards! ^_^
[Sony Xperia P, U, Sola, Go] moonset:
Yes sir! you are right! ADB interface worked :D
[Sony Xperia P, U, Sola, Go] sandydude:
Best Answer

I have searched for this answer all over the net and no one has answered this problem to install fastboot better than this person.

Thanks a lot.
[Sony Xperia P, U, Sola, Go] Matt1408:
I can't seem to get it. Under what category in device manager does it appear on when you plug it in?
[Sony Xperia P, U, Sola, Go] sandydude:
Small Info

I followed all the steps and I thought the drivers installed properly but after getting the key and trying to get into fastboot mode, I faced same problem it went into charging. then I tried repeating the same steps but with one change.

I selected Android ADB interface and not Android Bootloader Interface and it worked like a charm.
[Sony Xperia P, U, Sola, Go] Griggs88:
Sorry if this is dumb (probably is as others have had no problem) but I am attempting this and am stuck on step 9. When I click browse, the System32 folder opens and I dont know which .inf to open. Is there a specific location and filename.
[Sony Xperia P, U, Sola, Go] footyfanatic:
Before you got to my walk through, you would have been following this guide from Sony: http://unlockbootloader.sonymobile.com/instructions

It is at step 10 which mentions the .inf file

I guess I should have made it more clear and told you to refer back to the Sony guide and where you have that file stored :)
[Sony Xperia P, U, Sola, Go] matrix hh:
it really works, I really thank you
[Sony Xperia P, U, Sola, Go] RavingManiac:
I'm having a problem here. Mine is x64

Whichever option I select it says Windows cannot find the file specified, what do I do?
[HTC Sensation] AssimoF:
[noob] I am now able to update to Sense 4.0 from 3.0 with my rooted Sensation XE still using stock ROM. Can I safely update to 4.0 or will that break or mess anything up?