Is it just me, or Samsung removed XWKE2 from Kies? Could anyone confirm that?
uskr said:
Is it just me, or Samsung removed XWKE2 from Kies? Could anyone confirm that?
Click to expand...
Click to collapse
KE2 is not on my kies aswell, they must of took it off for some reason?
Maybe a KE3 on the way
Check my thread. They confirmed to me today on the phone that the upgrade can cause serious damage to some phones so they have pulled it.
http://forum.xda-developers.com/showthread.php?p=13885491#post13885491
Although I said it was KE1, I meant KE2...
Strange indeed.
Looks like unbranded xeu guinea pigs are to receive updates quite often.
Good
Sent from my GT-I9100 using XDA Premium App
I just checked the FUS server and it's been pulled, the latest available is XWKE1.
So what kind of damage can it cause? Because I am running on KE2 already
I'm running XWKE2 too and well and it's perfect. I'm guessing it was pulled because of the compatibility issue with Orange's network. If you're worried and want to flash back to XWKE1 then the files and instructions are in a thread in Dev Forum.
Intratech said:
I'm running XWKE2 too and well and it's perfect. I'm guessing it was pulled because of the compatibility issue with Orange's network. If you're worried and want to flash back to XWKE1 then the files and instructions are in a thread in Dev Forum.
Click to expand...
Click to collapse
Not worried, just curious if it is an instant problem or one that develops in time while running KE2. I have no issues either, everything runs well and battery is ok too. Only thing that annoys me a bit is the message in Kies: "This version of the device cannot be updated", But i am sure that will go away when a new version will appear.
btw, I have an unbranded phone from clove.
I connected my phone to kies since you guys says it´s been pulled, KE2 is still availible here
Ah, no wonder. I updated yesterday and after a bit of buggering around to get Kies to see my phone it upgraded smoothly. Only later I found I had KE1 & not 2. Thanks for clearing that up, I'm not going mad after all.
yeh i upgraded to ke2 the other day and now im waiting for ke3, but i have not had any force closes or sudden shut downs.
Also my battery is doing ok, and not the best but ok i watched a 80min stream over wifi on the deadly dir655 router and i lost 16-20% so not good but not bad.
I just tried updating with Kies and XWKE2 is not there.
Maybe its only the debranded one thats not there. Maybe the o2 one is still there
I just updated my phone through Kies a few hours ago. No problems whatsoever.
Hello
My phone originally had a Middle East gingerbread version and I recently upgraded my gs2 to ICS.
First incident
Product Code: GT-I9100LKAXEO
PDA: I9100XXLPQ
CSC: I9100OXALPQ
Phone: I9100XXLPQ
Phone was working fine Except seldom call drops and taking some time to lock my position when I use GPS.
Second incident
Samfirmware has released a Sri Lankan version of ICS (I'm from Sri Lanka)
For the best, I've reodined the phone to below
Product Code: GT-I9100LKASLK
PDA: I9100XXLPQ
CSC: I9100ODDLP7
Phone: I9100DDLP8
ever since I updated phone to Sri Lankan version it generates heat when send or receive calls and when I listen to music (using both Cloudskipper and stock music player) Will check with the other software too.
This could be due to some bug in Sri Lankan version of ICS?
Any thoughts?
Anyone else having this heat issue?
Any solution?
Please help...
Did you have the problem with GB ? If not then there's clearly something in ICS causing the issue. Maybe some processes aren't shutting down or looping & hammering your CPU causing the phone to get hot.
When it gets hot, check the running processes.'
Obviously another test would be to go back to GB & see if you can reproduce the problem. If it does happen with GB, then it might be a problem with the phone. but it doesn't sound like it.
Obviously this 'Sri Lankan version' is not an official Samsung release, so you've got to expect problems. My advice would be to go back to GB & wait for an official ICS release for your region.
MistahBungle said:
Did you have the problem with GB ? If not then there's clearly something in ICS causing the issue. Maybe some processes aren't shutting down or looping & hammering your CPU causing the phone to get hot.
When it gets hot, check the running processes.'
Obviously another test would be to go back to GB & see if you can reproduce the problem. If it does happen with GB, then it might be a problem with the phone. but it doesn't sound like it.
Obviously this 'Sri Lankan version' is not an official Samsung release, so you've got to expect problems. My advice would be to go back to GB & wait for an official ICS release for your region.
Click to expand...
Click to collapse
Thanks mate.. I had no probs with GB. But I dont want to go back to GB. I'd rather prefer polish version of ICS.
Can you tell me how to check if it's a official Samsung release or not?
just updated to ics 4.0.4 on galaxy s2 and keeps randomly dropping the wifi any ideas for a cure :good:
ICS 4.0.4 - wifi dropping randomly
adderxp said:
just updated to ics 4.0.4 on galaxy s2 and keeps randomly dropping the wifi any ideas for a cure :good:
Click to expand...
Click to collapse
mine 2, after upgrading from 4.0.3 to 4.0.4 today (norwegian, LQ6). have no idea why. might try elixir2/alogcat, but dunno what to look for. anyone else got an idea?
br
Svein Idar
Bump, same thing. Was fine with the stock gingerbread and seemed fine with ICS 4.0.3 (though many people have been reporting problems)
After updating via kies to 4.0.4 yesterday my wifi is nulled.
Wifi analyzer is reporting great signal strength but it hardly loads any pages/apps and cuts out in under 40 secs.
*Want to downgrade back to 4.0.3*
Edit: I have a Virgin Superhub if thats a common denominator with you guys
joshwuk said:
Bump, same thing. Was fine with the stock gingerbread and seemed fine with ICS 4.0.3 (though many people have been reporting problems)
After updating via kies to 4.0.4 yesterday my wifi is nulled.
Wifi analyzer is reporting great signal strength but it hardly loads any pages/apps and cuts out in under 40 secs.
*Want to downgrade back to 4.0.3*
Edit: I have a Virgin Superhub if thats a common denominator with you guys
Click to expand...
Click to collapse
In my case, this problem persists on every wifi access point I connect to: work, home, train, supermarket... this is not related to router/hub brand.
snebop said:
In my case, this problem persists on every wifi access point I connect to: work, home, train, supermarket... this is not related to router/hub brand.
Click to expand...
Click to collapse
I haven't tested mine on any other network so i assume its not functional anywhere,
I don't have the first clue about how to downgrade it back to 4.0.3 though I would love for that to be an option in Kies, 'flash previous Rom'
It might be, as I say I haven't looked into it yet, give it another week with no Wifi and I'm sure it'll be bugging me though. This could be a blessing in disguise, I might end up with a bloatware free cooked rom, yey!
http://forum.xda-developers.com/showthread.php?t=1792463
This thread may assist those who wish to 'solve it themselves'
Try another kernel.
Ok I went to the official firmware section : http://forum.xda-developers.com/showthread.php?t=1544487
Downloaded android I9100XWLPT (4.0.4) [the same version which was already installed]
Reflashed with odin (make sure kies is closed or it won't work) now my Wi-fi is working perfectly with 4.0.4.
weird.
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
FistFull95 said:
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
Click to expand...
Click to collapse
The problem might occur because of memory which one of my friend had earlier. Can you tell me how long copying files into phone storage takes?? Do you feel like ROMs are geting installed slowly than previous, slow copying of files?
ASOP Roms like CM never come with baseband. they use the same baseband that you already have in your phone. Only Stock based comes with baseband in their firmware. Sometimes(not most of the time) it can be if you are using different baseband than the one of the firmware, like if you have 4.1.2 and installed baseband of older version like of 4.1.1 but this is exceptional..
Thanks for your reply!
I don't think the internal sd has gotten slower tbh. I tried to copy an 2gb dummy bin from the extsd to my infernal sd, which copied with an average speed of 9mb/s.
I have tried experimenting with different TW based roms in the past, so I might still have a wrong baseband / ril. Is there a way of checking this?
Sent from my GT-I9300 using XDA Free mobile app