Related
I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
tomween1 said:
I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
Click to expand...
Click to collapse
So just to be clear, you now have a Aria that has the official HTC Froyo 2.2 ROM installed, correct? The symptom would point to faulty proximity sensor.
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
If the problem still exists, you may want to consider it a hardware problem and take it back to AT&T.
tpbklake said:
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
Click to expand...
Click to collapse
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
tomween1 said:
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
Click to expand...
Click to collapse
So have you tried a hard reset as suggested? If that didn't work, you might want to run the Froyo 2.2 RUU again and reflash the image.
Since it is an official AT&T update, you should be able to call AT&T and report the issue.
tpbklake said:
So have you tried a hard reset as suggested
Click to expand...
Click to collapse
No, sorry, could you run these steps by me?
tomween1 said:
No, sorry, could you run these steps by me?
Click to expand...
Click to collapse
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
tpbklake said:
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
Click to expand...
Click to collapse
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
tomween1 said:
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
Click to expand...
Click to collapse
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
tpbklake said:
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
Click to expand...
Click to collapse
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
tomween1 said:
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
Click to expand...
Click to collapse
Yes, you would be reflashing the 2.2 upgrade over itself.
tpbklake said:
Yes, you would be reflashing the 2.2 upgrade over itself.
Click to expand...
Click to collapse
I'll give that a try, thank you.
I had to make sure it was an upgrade issue so I went back to 1.6 and I haven’t gotten no network coverage, and the battery last a whole lot longer…. I don’t know why but 2.1 is pretty bad, sure its faster, but if you have no reception and has to have a charger at hand, it defeats the purpose of upgrading.. I would like to know if this is because of flashed rom, or this is an issue with all 2.1’s?
Sounds like an isolated problem. It's been six months since the 2.1 update, and I have not heard this. Did you try repair software via SEUS or PC Companion before going back to 1.6?
try to use Flashtool to make a new fresh 2.1 may fix your issue
agentJBM said:
Sounds like an isolated problem. It's been six months since the 2.1 update, and I have not heard this. Did you try repair software via SEUS or PC Companion before going back to 1.6?
Click to expand...
Click to collapse
I didn't try that, because I thought for some reason if you use SEUS it will block you from downgrading to 1.6 if have a need to go back.
gabnj said:
I didn't try that, because I thought for some reason if you use SEUS it will block you from downgrading to 1.6 if have a need to go back.
Click to expand...
Click to collapse
I think it already will block you, because your CDA number has changed and unbranded to global generic. In order to flash back to 1.6 with flash tool, you need to use root explorer or adb to edit the build.prop file back to AT&T branded 1.6.
Try using some of the custom roms - I always found battery life greatly improved (2.1 & 2.2) not to mention the speed and feature improvements.
Give it a go, it's not difficult and you may get a pleasant surprise.
Hey bro u have to let the upgrade settle in for a couple of days. That's stupid to flash it then ten seconds later say this sucks.
Sent from my x10 on gingerbread
Lion3494 said:
Hey bro u have to let the upgrade settle in for a couple of days. That's stupid to flash it then ten seconds later say this sucks.
Sent from my x10 on gingerbread
Click to expand...
Click to collapse
Exactly.
@gabnj -After one day of use and you are giving up? Android needs to build up its cache and everything will be good after a few days. Go read 2.1 after effects thread found here:
http://forum.xda-developers.com/showthread.php?t=824721&highlight=after+effects
You will see that a lot of people had the same issue(s) as you. As for poor reception, I don't know. Like the Agent says it might be isolated. Your phone should still be under warranty with AT&T, take it to their repair service location and have it checked out.
Hello, Im about to upgrade my x10a to 2.3 using the flashtool. And i was wondering if everything works correctly and if it works with the x10a U.S.
Thanks A lot
Yes it does. It is working for me.
But I saw a post that someone in New York area is having difficulty to get the radio working.
hasei said:
Yes it does. It is working for me.
But I saw a post that someone in New York area is having difficulty to get the radio working.
Click to expand...
Click to collapse
Thanks, and what do you mean radio? Like the fm/am radio, because if its that,then im gonoing to that since i wont be using that.
no... it means gettign the signal!
reboot while getting signal found to be a little common happened to x10a user
me included
oh alright. Does it happen to you? or does it happen to everyone?
Don't worry, you can always go back to where you were if it doesn't work out, which I doubt will occur.
thanks a lot. I will be doing this soon. this is the official update? and is everything else working smoothly, example: the transition between pages and the touch?
Yes this is the official update. You would be the only judge to make sure everything works smoothly.
I'm glad that I upgraded!
Yeah, I did it and everything seems to work correctly. Now im going to root it. I just need find a way.
As far as I know conventional ways to root don't work.
http://forum.xda-developers.com/showthread.php?t=1196421
You may want to take a look at it. Or flash prerooted one like I did.
Does your phone customization version has the update released? If yes, update it through SEUS or PC Companion. FlashTool is just used for backup, I will not recommend to use it to upgrade OS.
Brunop10 said:
Yeah, I did it and everything seems to work correctly. Now im going to root it. I just need find a way.
Click to expand...
Click to collapse
I've found a better thread that shows how to root the official 2.3.
http://forum.xda-developers.com/showthread.php?t=1196808
I have flashed to 2.33 and my biggest complaint is that the phone reboots after using google navigation after about 10 minutes, and poor bt profiles, making my older se stereo headset unrecognised.
Sent from my X10i using XDA Premium App
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Not positive but fc'ing cam is a sense 4 bug.
Sent from my ADR6425LVW using xda app-developers app
adamsaur said:
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Click to expand...
Click to collapse
If you have face detection on, it could crash the camera.
adamsaur said:
Hi I have a s-off, rooted rezound. I never actually put the ics firmware onto it (still not exactly clear on how to do it). However I installed a few sense 4 roms and while most worked perfectly fine, all of them had the issue with the camera fc and crashing. I installed the camera that was posted as a fix to no avail. Do I need to update the firmware and how (detailed please, sorta new at this), or will I be stuck using desensed roms till the devs fix it?
Click to expand...
Click to collapse
The camera seems to be an issue. Some say to uncheck face recognition and then it works...I don't know. Mine works when I've needed it. Some also have had luck with 3rd party apps. Eventually it will get fixed. You don't have to 'fall back' to a desensed rom, there are several good roms out there not using sense 4.0.
Update the firmware..? Well, there is a post today hinting at something coming in the next two weeks. Perhaps the long awaited OTA. So you should update to the new firmware. Either with the update or with one of the leaks. NilsP has some instructions on running the RUU in post #3 of one of his ROMS...the sense 4 one I think. Check it out if you want.
That's odd. I've ran all the sense 4 roms here and the only one that gives me problems is one xxx but is rare.
Sent from my ADR6425LVW using Tapatalk 2
I'll have to check the face recognition, I wasn't using it but it's worth a shot.
Anyone know of any hq camera apps to use if the default fcs again?
FYI - Since you're s-off, you don't need to flash a whole RUU to get the latest firmware, take a look at this thread - http://forum.xda-developers.com/showthread.php?t=1614366&highlight=firmware
Since you are running ICS on GB firmware, if you update, you need to flash the New firmware patch afterwards to revert what the old firmware patch does.
It won't help with your camera most likely cause as others has mentioned, it's a issue with Sense 4 roms for now, this makes it easier to upgrade though.
thanks mjones finally updating the firmware
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...