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?
Related
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
I have snooped around for a while in the development part of this forum, but it seems like either A2DP is listed as non working, or it's just not mentioned. Are there any KitKat ROMs with it working? I would like to upgrade my wife's phone to something better than the last official ROM, and I'm very satisfied with KitKat on my own devices, but she uses her phone in her car to play music through the BT enabled stereo, so it needs A2DP. If none are working now, is there a chance to get something that's working with A2DP in the near future?
Mastiff said:
I have snooped around for a while in the development part of this forum, but it seems like either A2DP is listed as non working, or it's just not mentioned. Are there any KitKat ROMs with it working? I would like to upgrade my wife's phone to something better than the last official ROM, and I'm very satisfied with KitKat on my own devices, but she uses her phone in her car to play music through the BT enabled stereo, so it needs A2DP. If none are working now, is there a chance to get something that's working with A2DP in the near future?
Click to expand...
Click to collapse
There is not KitKat ROM with working A2DP. It will be fix but not in the near future.
OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?
Mastiff said:
OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?
Click to expand...
Click to collapse
Hi,
percy wrote in his thread, that he's working on A2DP,wifi direct and other stuff and only problem will remain FM radio. But he also wrote that he's now busy with studies till 10th of april or so. After then he will release new kernel with dual recovery and maybe weekly 5 release ...
OK, then I'll wait a month or so for that. Thanks!
Mastiff said:
OK, thanks a lot! Then I won't have to look in vain. Any idea how far that future is?
Click to expand...
Click to collapse
Some, or maybe all, CM KitKat ROMS use Bluez for Bluethooth. At present, bluetooth is working fully on these roms, except music streaming through A2DP. Exactly what you need.
I assume it'll be fixed in next release of Bleuz, which will be version 5.17 (yo can follow this on www.bluez.org). A week after the release of this version from Bluez - we'll most probably have the first KitKat Roms with bluethooth fully operational.
Beverke said:
Some, or maybe all, CM KitKat ROMS use Bluez for Bluethooth. At present, bluetooth is working fully on these roms, except music streaming through A2DP. Exactly what you need.
I assume it'll be fixed in next release of Bleuz, which will be version 5.17 (yo can follow this on www.bluez.org). A week after the release of this version from Bluez - we'll most probably have the first KitKat Roms with bluethooth fully operational.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-u/general/aosp-xperia-p-sola-t2684583
Your only solution but you have to wait some weeks!
Thanks, mate! Thread subscribed. I'm sure my wife can wait a few weeks, especially since I haven't told her about it yet. Much easier to tell her "time to update your phone, honey" than "in a few weeks or months it may be possible to update your phone, honey".
Mastiff said:
Thanks, mate! Thread subscribed. I'm sure my wife can wait a few weeks, especially since I haven't told her about it yet. Much easier to tell her "time to update your phone, honey" than "in a few weeks or months it may be possible to update your phone, honey".
Click to expand...
Click to collapse
Hahaha you are always welcomed! You did the best thing :good:
@Mastiff
Go to bluez.org
All KitKat roms on this forum use it as their Bluetooth stack. When they list a2dp as working it will work.
Thanks! But according to them, on the 11th of March:
"On the Android side by far the biggest feature addition is full support for A2DP 1.3 and AVRCP 1.5. Several other profiles, such as HFP and GATT have continued receiving a fair amount of patches as well, but they are not considered complete yet."
So that should mean that it's already working and has done so for almost a month. Or do I misunderstand it?
Our plaform is tricky. Is not enought BlueZ support (they work on Nexus devices) we need adapt our platform to BlueZ, because old Sony code is deprecated
OK, thanks. A bit more complicated than Hamza thought, then. Well, I'll probably just have to wait a bit longer.
Any news after 2 months?
Sent from my Xperia U using XDA Free mobile app
Yeah, one month ago I got tired of waiting and bought an Xperia Z1 Compact for my wife... She actually took to the size quite easily, I thought it would be too big for her, but I guess the P had sort of primed her for it. Unlike the the P om it's final stock ROM the Z1 Compact on KitKat is very stable.
Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
mario24601 said:
Im not positive but I thought both versions have different hardware. If so then the us would not have it?
Click to expand...
Click to collapse
My understanding was that the hardware is still present in the US version, but it was disabled for legal reasons. Could be wrong though.
msamuels0 said:
Apologies in advance for noobish questions...
I bought an unlocked Z5C (US version) at Best Buy a few weeks ago, and have been happy with the phone, even though the fingerprint sensor has been disabled for the US.
I had been hoping for the possibility that when 6.0 was released for the phone, because of the new framework having more fingerprint-related libraries baked in, that the sensor would be enabled. No such luck.
So, my question is, how easy/difficult would it be to somehow enable the fingerprint sensor on the US version of the Z5 Compact?
I've never really gotten too deep into rooting, building, etc., but I am a software developer, so I'd be comfortable with development tools, build environments, modules, etc., but I just don't know where to start with something so specific, having never done it for this platform before.
I'd have to think that there would be some way to do a custom build, either importing fingerprint libraries into a US build, or importing US radio libraries into an international build that has the sensor enabled, or some combination like that?
I'm really just looking for someone to hopefully point me in a direction to try to do this. If there's already a solution, even better, but I'm not holding my breath for that one.
Thanks in advance for any info!
-Mark
Click to expand...
Click to collapse
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Pakman123 said:
try this method in this thread might be able to activate it if its software locked
http://forum.xda-developers.com/xperia-z5/general/e6653-flash-e6603-firmware-enable-t3307158
Click to expand...
Click to collapse
Exactly what I was looking for, thanks!
We'll see how it goes!
msamuels0 said:
Exactly what I was looking for, thanks!
We'll see how it goes!
Click to expand...
Click to collapse
no problem good luck
Let us know if it works, I am curious.
DAVe3283 said:
Let us know if it works, I am curious.
Click to expand...
Click to collapse
Quick update...
I finally got a chance to mess with this over the weekend. There is not yet a Custom UK E5823 release for MM, so I tried copying the files from another MM non-us release, and it didn't appear to work. However, I did go and revert back to Lollipop with the latest available UK release, and can at least confirm that the fingerprint hardware is indeed present, as the fingerprint manager then showed up, and the sensor worked. I went back to the latest E5803 Custom US Marshmallow, and will wait until MM is available for UK, and try to copy those files and rebuild again then.
Interesting... that is good to know. It seems that we could buy the US version to get the warranty, then just flash an international firmware to unlock all the functionality. And hopefully down the road, do the mash-up firmware for the best of both worlds!
I'm just surprised they disabled the sensor in the US, especially with the sensor still present in the phone!
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Fantastic work!
Sent from my SM-G850M using Tapatalk
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
AnandRajaguru said:
Congrats!! Wat about cellular reception and call quality, any glitches?? (like echo troubles...)
Click to expand...
Click to collapse
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Woo! This makes my day!
runningwarrior08 said:
I don't have a US model but an international model, running on Nordic using att and have no issues other than signal bars displaying less signal than i have. I'll show no bars at the same db rating my other phone shows 2 bars. No big deal phone still works fine.
Click to expand...
Click to collapse
Yeah, I noticed the signal meter reading lower than it should on the Nordic firmware on US T-Mobile. Getting 20Mbps on 4G with no bars is fine with me.
Amazing news for US version owners
msamuels0 said:
Another update...
I tried copying the files from a few other MM builds and repackaging, but none allowed the fingerprint sensor to work on my phone.
However, since people in some other threads had been talking about the Nordic Combined version of firmware, I figured I'd give that a shot without any modifications. And... everything works!
So just to reiterate, I have a US version of the Z5 Compact (E5803, purchased at Best Buy), and updated with the Nordic Combined firmware (1298-7782, Customized NOBA, 32.1.A.1.163/R9C) with no modifications, and everything works perfectly on my phone (registered on T-Mobile), including the fingerprint scanner.
The phone now reports itself as E5823 instead of E5803, but I can live with that!
Click to expand...
Click to collapse
You don't have volte though right?
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
Sony phones have always reported lower signal than actually present. No idea why
Possible to revert back?
This is great news. Is it possible to revert back to make it report as the right model for warranty purposes?
Of corse, just flash back US firmaware and it'll be ok.
just flashed "customized uk" version and got my US z5c fingerprint reader up and running. wonder what, if any, issues might arise from running a firmware for a different model, e5823 vs. e5803.
this thing is nice, but man , it does get pretty hot in the back top center. yowza.
Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Good job dude.
you need to check the call volume, make a phone call and see if you can hear or the other person can hear you.
Lloir said:
Good job dude.
you need to check the call volume, make a phone call and see if you can hear or the other person can hear you.
Click to expand...
Click to collapse
Thanks alot and Yes !!! But call-in-audio is very low... I didn't found mixer_paths.xml to incerase it. I set minimum cpu at 700mhz and max at 1000mhz no heating issues or Battery Drain too.
Well, I have a question I repo sync the cm-11.0 but while compiling there is error related to awesomeplayer.cpp audio.cpp which is basically related to audio files.
Error was something like "warning initializers failed (wreoder) error 1".
I think vendor is cause. Can You give some tips or help me? Or I have to do any commits?
veer.killerboy said:
Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Click to expand...
Click to collapse
I'm with you if you happen to get your work back. (Stolen laptop, sucks.)
I have a 32gb international HOX but bought this HOX+ recently because camera and sim werent working.
Plus, the 62gb is better.
There is android 5.0 development for the internation 32gb
So I think it would be great for anything 4.4 or higher for the HOX+
Even finding a decent 4.2 for the ATT seems difficult
International versions were hard to find in the states.
Thanks!
Ever get this out:?
veer.killerboy said:
Going to upload latest build of cm10.2
I made this rom for myself because Llior has removed his cm10.2 work. So, I started to compile again and made it again through sources. But I am going to upload soon. I want to see who are interested in this rom. By the way dont ask for eta. Well, I will make cm11 though too after this in my free time. Thanks Llior for device & kernel sources.
Known Issues:
Yes !!! They are still there -
1. No front camera
2. No led notification
Semi Working -
1. Wifi need workaround
2. Camera no gps error at all.
All other things are perfect.
Click to expand...
Click to collapse
Got link for the rom and what was the wifi fix again?
Tmobilefan906 said:
Got link for the rom and what was the wifi fix again?
Click to expand...
Click to collapse
Check 2nd post...
veer.killerboy said:
Check 2nd post...
Click to expand...
Click to collapse
Tried that. Didn't work
Tmobilefan906 said:
Tried that. Didn't work
Click to expand...
Click to collapse
WiFi can be used only through static IP or make your router IP static. Sources are not up to date so WiFi was never solved. This is the only work around. Change last 3 digit of IP. Count how many devices are connected if there is already 3 then make yourself 104 or 105... 101,102,103 is already allotted.
veer.killerboy said:
Check 2nd post...
Click to expand...
Click to collapse
Too bad you couldn't have made an updated rom for att
There was no need to escalate this with racial offenses by the OP. XDA will not tolerate any abuse from anyone in any form.
I did a thread cleanup and OP was temporarily banned.
deleted
Do you mean RR.O hellsgate fixes the issue?
I do not understand your post.
nfsmw_gr said:
Do you mean RR.O hellsgate fixes the issue?
I do not understand your post.
Click to expand...
Click to collapse
OP updated.Not only flash Hellsgate.
hello all, i tried the fix on my RR-O 20180422 with hellsgate 2.1 from kraoner, it isn't still not working for me, i don't have any audio using the second sim.
del_piero3 said:
hello all, i tried the fix on my RR-O 20180422 with hellsgate 2.1 from kraoner, it isn't still not working for me, i don't have any audio using the second sim.
Click to expand...
Click to collapse
This isn't the bug you are thinking of.
The bug you have is related to dual sim.
Right now on oreo you can only make a call to the sim you are currently using data with. It is a separate bug.
Dodgexander said:
This isn't the bug you are thinking of.
The bug you have is related to dual sim.
Right now on oreo you can only make a call to the sim you are currently using data with. It is a separate bug.
Click to expand...
Click to collapse
hello,
thanks for your answer, then i didn't understand what the fix was made for.
Do we know already when the bug i am talking about will be fix roughly ? It is pretty annoying because the rest of the ROM works really good ...
Can anyone confirm if the OP's fix (Kernel and Mixer.zip) works for fixing the call bug? I previously tested a few of the common Oreo builds on my A2017U and ran into the 'call bug' with just about every build. It happened to me most often with incoming calls where I had to turn the speaker on and off to workaround it. I just finished flashing my Axon 7 or I would test this myself.
del_piero3 said:
hello,
thanks for your answer, then i didn't understand what the fix was made for.
Do we know already when the bug i am talking about will be fix roughly ? It is pretty annoying because the rest of the ROM works really good ...
Click to expand...
Click to collapse
No one seems to be able to fix it. All you can do is pray there is an official release from ZTE and someone is able to source a fix then. I have same problem as you and I hate it but there is nothing that can be done. Best to assume there will be no fix.
2000impreza said:
Can anyone confirm if the OP's fix (Kernel and Mixer.zip) works for fixing the call bug? I previously tested a few of the common Oreo builds on my A2017U and ran into the 'call bug' with just about every build. It happened to me most often with incoming calls where I had to turn the speaker on and off to workaround it. I just finished flashing my Axon 7 or I would test this myself.
Click to expand...
Click to collapse
I don't have any problems even without this zip using the latest AEX on oreo but as far as I know this has never been announced as being fixed so it wouldn't surprise me that it still exists.
Dodgexander said:
No one seems to be able to fix it. All you can do is pray there is an official release from ZTE and someone is able to source a fix then. I have same problem as you and I hate it but there is nothing that can be done. Best to assume there will be no fix.
I don't have any problems even without this zip using the latest AEX on oreo but as far as I know this has never been announced as being fixed so it wouldn't surprise me that it still exists.
Click to expand...
Click to collapse
As far as i know, the A2017G was supposed to get an official Oreo rom by end of this month, should arrive quite soon. The thing is that A2017 from China already have an official Oreo Rom, and i don't think these 2 phones have such different hardware component in it, don't you think ?
del_piero3 said:
As far as i know, the A2017G was supposed to get an official Oreo rom by end of this month, should arrive quite soon. The thing is that A2017 from China already have an official Oreo Rom, and i don't think these 2 phones have such different hardware component in it, don't you think ?
Click to expand...
Click to collapse
Yes but it's not really easy for someone to use the phone in Chinese and see if these bugs are there. If there is any chance of them being solved having an official English release will help more than an unofficial Chinese one.
With things to do with mobile networking this is even more the case which the dual sim bug is probably related to. (There are different basebands that the U & G models work with for example).
Dodgexander said:
Yes but it's not really easy for someone to use the phone in Chinese and see if these bugs are there. If there is any chance of them being solved having an official English release will help more than an unofficial Chinese one.
With things to do with mobile networking this is even more the case which the dual sim bug is probably related to. (There are different basebands that the U & G models work with for example).
Click to expand...
Click to collapse
i don't really understand what you're saying..?
The A2017 build obviously comes with other languages, why would you think otherwise (or not even check before saying that)? ?
Now, it being crap is beyond the scope of this comment of course
Choose an username... said:
i don't really understand what you're saying..?
The A2017 build obviously comes with other languages, why would you think otherwise (or not even check before saying that)? ?
Now, it being crap is beyond the scope of this comment of course
Click to expand...
Click to collapse
That's okay, I have yet to grasp what you are saying either.
Dodgexander said:
That's okay, I have yet to grasp what you are saying either.
Click to expand...
Click to collapse
all right, let's help each other
The Chinese ROMs come with English language, so nobody needs to use their phone in Chinese
Your dual sim statement is pretty weird