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.
any hope of getting FM radio support on roms (I'm mainly using cyanogenmod, usually sportsstar's). I've tried the port of the apk for the fm radio (wouldn't run) and some spirit radio apk (loud static all channels). Thanks.
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
yeah. ok thanks, I guess I will try again.
your welcome
reebokhcfr said:
yeah. ok thanks, I guess I will try again.
Click to expand...
Click to collapse
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
chevycowboyusa said:
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
Click to expand...
Click to collapse
Sense Apps do not work on AOSP roms. And can't be made to work...
FM Radio
dcacklam said:
Sense Apps do not work on AOSP roms. And can't be made to work...
Click to expand...
Click to collapse
Hi Dave! Thanks for the response
I thought there was an FM radio app in the CM Builds??
There are people using Spirit on CM10 (other devices) and I have got Spirit working on Sense 4 (even though the built in one doesn't work)
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
mgp53 said:
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
Click to expand...
Click to collapse
I couldn't get it to work either on the PacMan rom
I just flashed SpeedRom 9.0 Beta 1 and the FM Radio app works because SpeedROM is still a sense based ROM but looks like JellyBean.
Viper Radio
chevycowboyusa said:
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
kodunmit said:
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
Click to expand...
Click to collapse
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Firmware
JimDandy68 said:
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Click to expand...
Click to collapse
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
chevycowboyusa said:
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
Click to expand...
Click to collapse
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
JimDandy68 said:
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
Click to expand...
Click to collapse
Just want to ask again on this thread, has anyone ever gotten Spirit FM or another FM radio apk to work on a JB ROM (non-sense-based)? Chevy mentioned the Spirit FM 3rd beta, but not sure whether he was talking about having it work on a JB ROM or on Viper. ICS ROMs mostly have the stock radio app working, so not an issue there.
Thanks.
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Odysseus1962 said:
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Click to expand...
Click to collapse
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
JimDandy68 said:
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
Click to expand...
Click to collapse
I know what you're talking about. I think many here, myself included, wish that development was further along. Frankly, I find it sad and ironic that my old HD2, which was a Windows phone, has had fully functional usable stable Jellybean ROMs for a well over a year and it never had any sources released to develop from.
The sad truth is that the Amaze is a great device that wasn't marketed well, so few units were sold. Too few at least for it to have developed a devoted loyal following. If you follow the threads you see that there was never a large volume of development for it and that most of the early adopters have long since moved on to other devices. I'm just glad that we're now experiencing a second wave with new folks stepping up and trying.
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Odysseus1962 said:
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Click to expand...
Click to collapse
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
JimDandy68 said:
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
Click to expand...
Click to collapse
I wouldn't be so down on HTC. They may not have been the most supportive manufacturer when it comes to outside development, but they've also produced some of the most groundbreaking innovative products. They're in financial trouble now, as their market share has eroded, and haven't had a breakout device in some time. They realize this and have begun making incremental improvements within the development community in an attempt to improve it's perception. The thing is who are you going to jump ship to? Samsung is already undermining android by developing Its own market place for apps that can only run on their devices and has announced It's developing its own proprietary OS. Since they're the biggest player in this device market, they could easily splinter Android and force other manufacturers to do the same to compete.
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Odysseus1962 said:
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Click to expand...
Click to collapse
Point taken. I'm 45 and evidently haven't learned anything. :cyclops:
Time to go back to a landline.
Guys,
EU version started shipping with ROM Omate_TrueSmart_20140328.182336_V2.0 build
Are the sensors working? if so, can anyone upload the ROM for all the poor people with dead sensors.
NB. i tried every single ROM available in this forum and no luck.
Thanks
my watch is Omate 2100mhz 1/8GB from china with Chinese ROM
That's actually a great question.
Could anyone write some feedback for 2100 1/8 - what are your impressions, something is fixed (we all know what are TS problems, so are they fixed?
And really, what about sensors and BT?
Companion mod is working?
Sent from my C6903 using Tapatalk
Received mine on Friday, not had time to really play with it yet but I can confirm that BT and Companion are working. What sensor issues are there?
I have not even lurked on these threads so please feel free to ask questions and will answer as soon as I can.
chippyuk said:
Received mine on Friday, not had time to really play with it yet but I can confirm that BT and Companion are working. What sensor issues are there?
I have not even lurked on these threads so please feel free to ask questions and will answer as soon as I can.
Click to expand...
Click to collapse
What version is your ROM? try to download ocompass from the ostore if it is working than the sensors are working.
azizbouharb said:
What version is your ROM? try to download ocompass from the ostore if it is working than the sensors are working.
Click to expand...
Click to collapse
It is 20140328.182336_V2.0. Omate version is OUI 2.1. Kernel is 3.4.5
OCompass works fine and in Android Sensor Box, Accelerometer, Orientation Gyroscope and magnetic all work, Sound causes the app to FC.
chippyuk said:
It is 20140328.182336_V2.0. Omate version is OUI 2.1. Kernel is 3.4.5
OCompass works fine and in Android Sensor Box, Accelerometer, Orientation Gyroscope and magnetic all work, Sound causes the app to FC.
Click to expand...
Click to collapse
Great , i'll be looking forward to have the ROM, thanks
azizbouharb said:
Great , i'll be looking forward to have the ROM, thanks
Click to expand...
Click to collapse
I am away on business at the moment but will see if I can get some time to dump It and upload it for you very soon. Please let me know if you manage to get it in the mean time.
Thanks.
I just need to verify a few things before I upload it. If everybody will be patient, I will be able to prepatch it as well.
Also, just because it's newer doesn't mean anything. 0328 may have more issues than a merged firmware based on something older or based on something that doesn't even come from Omate. The 512/4 working sensors is a perfect example. That doesn't even use Omate's kernel but a kernel from a different brand.
chippyuk said:
I am away on business at the moment but will see if I can get some time to dump It and upload it for you very soon. Please let me know if you manage to get it in the mean time.
Thanks.
Click to expand...
Click to collapse
Thank you
azizbouharb said:
Thank you
Click to expand...
Click to collapse
Think it best we wait for Lokifish to do his magic, no point in me putting the base version up, doubt I would be able to until the weekend anyway. It will be worth the wait!
Full 20140328 firmware for those that need it.
And by need it I mean you messed up your device and need a way to get back to stock.
Lokifish Marz said:
Full 20140328 firmware for those that need it.
And by need it I mean you messed up your device and need a way to get back to stock.
Click to expand...
Click to collapse
Not that it matters but is this the one that ships with EU 1/8/2100 devices with OUI 2.1?
Well sort of. Its based of slimkat which is aosp. I'm just sharing the link, I'm downloading it now but a few sprint users claim it works.
http://forum.xda-developers.com/galaxy-note-3/development/rom-miui-v5-galaxy-note-3-t2816410
Saw the release
Yeah, I saw that, does anyone know if the sprint version is based on the N9000 and N9005 version on MIUI's site?
RigorousNinja said:
Yeah, I saw that, does anyone know if the sprint version is based on the N9000 and N9005 version on MIUI's site?
Click to expand...
Click to collapse
Not positive, but I think 9005. Anyway I could not get a signal at all. Have you tried it?
Modem
drunkensunday said:
Not positive, but I think 9005. Anyway I could not get a signal at all. Have you tried it?
Click to expand...
Click to collapse
I believe that if it will flash that you will have to flash a modem since it would contain the international modem pre installed, but I haven't tried the install yet, I may soon though.
It should work out the box. But it's not detecting our sim cards. It's based on the slim rom hlte device tree, which will work on our phones
Sent from my SM-N900P using Tapatalk
I am looking forward to a port of the tw version of MIUI.
Tried it
I tried it on our device, and it seems to work ok. It is definitely not a daily driver, but runs smooth. The mobile data doesn't work, but calls and texts come through. The rest of the bugs are true, where vibration on touch doesn't work. other than that it seems to work.
Is anyone having problems with their phone service? I can't text or call D;
kittyfantastic said:
Is anyone having problems with their phone service? I can't text or call D;
Click to expand...
Click to collapse
After setting network o can make calls but not disconnect from them. The dev seems to say it works but its not. Whish more devs would get active in porting it. It seems so close to actually working finally.
I've bought a Kindle Fire HDX 7 thor and it was pre-installed a CM11 by the shop and back then it CAN connect with my Samsung level U bluetooth headset but after installing four different roms on the page https://forum.xda-developers.com/kindle-fire-hdx I found out that my bluetooth and my front camera are all unuseable.
I just want to ask why and how I can use bluetooth on it?
Thankyou.
BTW I'll upload the zip file I got from the seller online and post link later.
THANK YOU
Now I am using Aosp from https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-aospextended-t369113
The file that seller gave me is on MEGA https://mega.nz/#!5CQQXbia with no password.
BobLao said:
Now I am using Aosp from https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-aospextended-t369113
The file that seller gave me is on MEGA https://mega.nz/#!5CQQXbia with no password.
Click to expand...
Click to collapse
Me thinks that ain't gonna work. If it were that simple the ongoing BT issues with this device would have been solved long ago. The same core developers have been working with both HDX variants since the Jelly Bean days. Up until recently BT was unreliable on all non-KitKat based custom ROMs. A lot of work went into resolving the issue w/o success. Some Kernel tweaks that came along with LOS seemed to improve things; now *most* devices will pair although it's not always a smooth experience. Not sure what the issue is with your Samsung headset.
Front camera is a different issue as that has not proven to be problematic once a 3rd party camera app is installed...at least on 7" models (thor). Possible you have a hardware issue.
Davey126 said:
Me thinks that ain't gonna work. If it were that simple the ongoing BT issues with this device would have been solved long ago. The same core developers have been working with both HDX variants since the Jelly Bean days. Up until recently BT was unreliable on all non-KitKat based custom ROMs. A lot of work went into resolving the issue w/o success. Some Kernel tweaks that came along with LOS seemed to improve things; now *most* devices will pair although it's not always a smooth experience. Not sure what the issue is with your Samsung headset.
Front camera is a different issue as that has not proven to be problematic once a 3rd party camera app is installed...at least on 7" models (thor). Possible you have a hardware issue.
Click to expand...
Click to collapse
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
BobLao said:
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
Click to expand...
Click to collapse
Apparently on *your* HDX with a specific BT device. Most are reporting good BT pairing results with the latest Nougat ROMs. Given the front camera also has issues you may have scored a defective device.
BobLao said:
So there is no way for me to use bluetooth on my non-KitKat custom rom right?
Well thanks mate
Click to expand...
Click to collapse
Davey126 said:
Apparently on *your* HDX with a specific BT device. Most are reporting good BT pairing results with the latest Nougat ROMs. Given the front camera also has issues you may have scored a defective device.
Click to expand...
Click to collapse
FWIW - you might find this post helpful: https://forum.xda-developers.com/showpost.php?p=74757593&postcount=88
Davey126 said:
FWIW - you might find this post helpful: https://forum.xda-developers.com/showpost.php?p=74757593&postcount=88
Click to expand...
Click to collapse
Thank You