Related
I'd like either a locale plugin, or a standalone app, that will activate the GPS based on the sensor reporting that the phone (and therefore presumably I) am traveling at more than 5 miles per hour (or some measure that would indicate I am traveling faster than 'at a walk'). Does such an app exist? Is there a sensor readout that would work for this?
The only thing that can tell the phone how fast is going is the GPS, so you'd need the GPS to be on in order for the phone to know when to turn on the GPS.
Other than that, this is NOT development related. Please use the Q&A forum for questions.
I'm sorry. It seemed logical that the applications subforum was the place to ask if a specific application exists, since it's the place to request an application be created (judging by the requests thread).
Thanks for the info about the sensors tho. I didn't know if there was a sensor that could measure speed (other than GPS). I suppose in retrospect it's obvious, since if your speed isn't changing, there's no g-force on the accelerometer.
You did not post it in the application subforum. You accidently posted it in the Dream Development sub forum. If that was where you originally meant to post it, then you were in the right (had you posted it there.)
As far as the GPS issue, as long as you're not actively using a program that uses the GPS, it shouldn't really drain any battery.
Personal background: Associate degree in Laser Electro Optics. 12 years research and development semiconductor manufacturing, 15 years as an EMT, last 10 years as a 911 telecommunicator for Austin-Travis County Emergency Medical Services. 6 of those years as a Training Officer.
The reason for my (cough) resume is so everyone understands I have the technical background and experience to explain the differences between e911 and 911.
Public Safety Answering Point: the local organization tasked with answering emergency request phone calls and dispatching appropriate emergency resources. PSAP's are broken into two types, primary and secondary. The primary PSAP is typically the local police department for city's and the local sheriff's department for unincorporated areas. Some colleges have their own police department and may have their own PSAP. So realistically a person can connect to a different 911 call center depending upon their location within a small geographic area.
Large urban areas typically have secondary PSAP's. The secondary PSAP usually consists of public safety departments not related to law enforcement such as fire and/or emergency medical services (ambulance services) specially trained to send request specific resources dependent upon the emergency. In Austin and Travis County we run 120 thousand EMS 911 calls per year. The police department takes about 2000 911 calls per day.
911: a simple to remember phone number nation wide allowing everyone access to emergency services. No location information is transmitted or received. The PSAP is responsible for determining location by interrogation of the caller. This can a problem if the caller is altered or otherwise unable to give accurate information.
e911: Enhanced 911 was created to ensure location information was transmitted to the 911 call center regardless of the callers ability to give this information. The phone companies are responsible for ensuring this information is available and transmitted to the PSAP. Conventional e911 is effective for landline phones. Cell phones present a completely different problem.
Cell phones are required to meet two different location technology standards.
Phase 1 wireless data: as cell phone use skyrocketed in the nineties, legislation was passed requiring provider's to transmit location data based on the cell phone tower that the cell phone was connected to. While this is helpful, it is problematic due to the sheer size of the area that had to be searched if the caller was unable to give their location.
Phase 2 wireless data: legislation now requires GPS location data be provided by the cell phone company. This location information can be transmitted via the gps chip from the cell phone or via radio location triangulation using the cell towers in the immediate area of the caller.
So in a nut shell, my test of neobuddy's ICS indicated that 911 worked for a sim loaded phone. I did not test the phone with the sim pulled. I also did NOT verify that GPS data was being received by the PSAP.
If 911 works with your phone it should work in any area. I was connecting with two different PSAP's as I live right between two different area's and sometimes connect to one or the other.
Hope this clears some of the confusion. A good explanation is located at en.wikipedia.org/wiki/Enhanced_9-1-1.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Later tators
Sent from my Touchpad using xda premium
thanks a lot. i can confirm cm7.1 has 911 issue.
Sent from my SGH-T959 using XDA Premium App
Developers should also note that as technology continues to advance, video conferencing and text message 911 activation requirements will also be legislated in.
I firmly believe that Google should begin requiring manufacturers make their modem software and audio software open source. Manufacturers should also be required to provide detailed explanations of how the relevant library's interface with the operating system, modems and audio system when activating an emergency call. This is Androids achilles heel. All it will take is one national media event to slam the door on open source operating systems for cell phones. I love the freedom Android provides and the exceptional programing skilss of our developers.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Sent from a cell tower to the XDA server to you.
Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Click to expand...
Click to collapse
correct as none had the source code....but for 2.3 onwards rom.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Click to expand...
Click to collapse
made my day.....thanks a lot....will be keeping a close eye on this thread...
My understanding is the issue is only without a sim right?
The 911 issue is with SIM, i don't know about without and im not planning on finding out.
HaloMediaz said:
My understanding is the issue is only without a sim right?
Click to expand...
Click to collapse
It has to do with emergency mode (no dim) and when no compatible roaming network is around (no service) .
Sent from my HTC Sensation 4G
hmmm I havent called 911 in YEARS but it still feels nice to have the ability and this was a nice explantion thank you
MIUI 360 in Asheville NC works fine but not in other areas?
Hopefully they can test the cm9 test ports that are out now.
Sent from my SGH-T959 using xda premium
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Can we get independent confirmation of this? (not that I don't believe you)
Sent from my SGH-T959 using xda premium
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
You typed all that from your touch pad? props
Sent from my SGH-T959 using XDA App
Genesis3 said:
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
Click to expand...
Click to collapse
No, I get that. Just wanted to make sure he verified was all..
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Don't know who you are or where you came from but, you sir may have saved CM development for the vibrant community. Here's hoping and you're the man!!!
Sent from my SGH-T959
Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
I just downloaded your kang and running great so far, Thanks for you work !!
Question, is this 911 fix kernel dependent ? ie will it break if I flash another cm7 kernel ?
Thanks again for your hard work !!!
will replacing the kernel break both 911 and gps fixes?
I didn't save anything.
Here's the bottom line, if you're interested in it.
In the original Vibrant device directory there was a set of sources for libaudio -- one of the shared libraries that Android depends on to talk to the audio hardware in the phone. There was no documentation as to where this source came from, but I know where it didn't come from -- it didn't come from a public Gingerbread source for the Vibrant, because there isn't one.
It turns out the library this source builds does not work correctly but exactly why I'm not certain of. One of the problems with debugging this is that I have to have someone else test for me, which means I can't do the sort of testing I like to when I'm tracing things like this (a highly-iterative process that requires that I actually be staring at the debugging screen while doing the deeds that cause the bad behavior) since I can't call 911 myself.. Had the provenance of this code been documented originally (or lack thereof) I would have investigated this possible connection, as I knew the problem lay in the audio connectivity due to myriad kernel and application traces a couple of months ago. I didn't chase that library down and attempt to graft in other related versions because I assumed that the CM people knew what they were doing building that library from source rather than using a cribbed copy from, for example, Froyo or a different gingerbread build off a similar device.
Picking up a different shared library does work. Exactly what the provenance of that library is (e.g. was it grabbed from a binary, was it built from DIFFERENT source, where did it come from?) is also unknown.
Now that I have a working shared library on this device and a non-working one I'm going to compare traces. Maybe I'll get lucky and find the changes necessary in the source that's in the build tree and be able to fix that, at which point I'll know what I've got rather than having a "magic" library from God-knows-where.
Now here's the part that annoys me -- I was all over some of the CM guys about audio problems with other Samsung devices and tried to get access to the "not yet finished" repos because I expected that if I could run down the same sort of problem with ordinary calls in one of the OTHER Samsungs it was rather more likely than not that the same fix would be pertinent in some way on the Vibrant -- simply because manufacturers tend to use the same chipsets and bits, along with APIs, between different devices (it makes it easier for their coders and maintainers to do their jobs.) In addition when I started working one this one of the other protagonists didn't give me jack and crap about the provenance of anything in the device tree and, again, there's no docs embedded in the tree either. You can find the flamewar and slander aimed at me here if you'd like. It turns out I was on the right path; the problem this library allegedly fixed was having to hit <MUTE> twice to turn off and on the audio path. Sound familiar? Well, the pointer to the file that I found and integrated was from a bug logged against the I-9000, a similar phone to the Vibrant, and that library version works. What's changed in it? There's no set of commits logged against the ZIP file provided in that patch; is it a binary lift from a different build (e.g. some factory build) or did someone fix the source?
Who the hell knows because again, it's not documented in the bugtracker. Until I know where it came from and, if there's source, I have access to it, I won't support it. I don't play the "hide the sausage" game when it comes to alleged community coding projects.
I ran into something similar with the Triumph in that there was a different set of parameters coming up from the hardware when a wired headset was plugged in. That was easy to run down because I could do it and see what was going on; it was a literal couple of line change in the code once I found it. There are a couple of places in the libaudio source that might be the cause of this now that I have a reason to look in there, but without being able to easily reproduce the condition that creates the failure (e.g. call 911) it's a guess.
The ICS builds out at present have a different copy of the same compiled library and it also works. I bet that one works too on CM7 as it's fairly close to the metal and thus the API's probably the same (or close) on the Android side but I haven't tried it yet. I've got little reason to since I now have a libaudio.so that's functional on CM7 in any event.
While I've been working on the 911 issue (for a couple months on and off) I also traced down some actual working (properly) GPS libraries that handle the AGPS assist data in the correct way, something that other sets of them do not, and added those too. I also made a few other changes. The battery life is reported to be rather impressive, and the near-instant GPS locks most-definitely are. I can't speak much to the battery life view of the world as of yet but I will be looking at that; that's an area I know quite a bit about (getting these devices to properly go into deep sleep as they should) and the source tree I'm working with does have kernel source.
Any sideloaded kernel that leaves libaudio.so alone (check the zip file to make sure that /system/lib/libaudio.so is NOT present) should be ok, but no promises. Before you go screwing with kernels make sure you want to --you might break GPS performance as a number of the kernels have various attempts to get the GPS to work right and load various libraries along with the kernel itself with varying degrees of success.
I'd be willing to maintain this port but there are two conditions -- first, I expect apologies from the CM people who attacked me, in public, and second, I expect a formal commitment that there will be no more hiding of information. "I don't know" is an acceptable answer provided you run down the person who does -- someone does know because someone DID either import or code the material in question; silence and lack of documenting where things came from and how they came to be is not acceptable. When things go into the codebase through review they damn well ought to be documented. I played "talking to the brick wall" with the Triumph and now the Vibrant and I won't do it if I'm taking on responsibility for maintaining something.
If CM wants me involved in this that's the deal. If not I'll consider setting up a parallel build and set of repos for the bits that have to be changed from the base CM7 Gingerbread branch as I did for the Triumph if there are people interested in it, but my time is not unlimited and in all honesty my taste for working with the CM people and the CM code in general has been seriously damaged, never mind that what I have here seems to work just fine. As such the benefits of continued efforts are likely to be relatively small. If I decide against a continuing effort I will take the build environment that produced that I have now and attempt to set up a manifest so it can be cloned by anyone else who cares to do so, which should take care of others being able to build and run the KANGs from source if they wish. The latter may take a while as I need to find a day when I'm not busy and can put that together (again, lack of documentation doesn't help) and then pull a clean test from a zero base and make sure it builds and runs.
The Vibrant is no longer my daily device but I do still own one, and given its relatively modest resale value I'll probably keep it as a spare device -- it's a very credible phone and with working GPS code it actually locks faster and better than my Hercules does. It's biggest shortcoming is that it's relatively RAM-starved compared to more-modern devices.
Fancy that.
Hi all, I hope I can provide reliable good news: LG support says some providers made some changes to some repeaters (e.g. E-Plus in Germany). They have a solution and provide us with an update released around the end of October.
Now is probably a good time to point LG to some of the major problems introduced with the JB update (4.1.3), as the new Update will likely be a smaller improvement of the latter.
In my case:
- very slow return to home screen when closing apps and problems navigating the home screens, when some more icons and widgets are present
- can't write onto external SD with some backup apps (e.g. Super Backup)
EDIT: I would be totally happy about a way to port the updated system files, once they are out, to other Roms (e.g. the ICS Stock Rom).
I'm extremely skeptical that LG would release an update for our phone. Are you sure our model is on the list?
I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.
pegnose said:
I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.
Click to expand...
Click to collapse
Can you please point us to that article on androidpit.de. Thanks
I Tried to find but no result.
See here (look for "FETTES UPDATE" on top of the page):
http://www.androidpit.de/forum/562054/lg-optimus-4x-hd-reorganisation-interner-prozesse/page/2
Sorry, this is a German post. Although the writer confused repeater with router, P920 with P990, and another user confused software and hardware update.
EDIT: My support guy explicitly statet that this will be an OTA update. I am sceptical, as it happens often with LG that updates have to be installed manually/via PC. Very likely he meant that I won't have to "bring in" my device again.
I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.
pegnose said:
I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.
Click to expand...
Click to collapse
I just don't think that some repair guy from LG can do anything else then told you what you want to hear and mark it as solved. I think they are just waiting till you buy new device. I'm lucky because I have no such problems with RIL. I disabled PIN protection and installed Mahdi. Now I sometimes (once per day?) can see no signal for second or two but it's ok.. no problems (there is no way for no signal, I'm living next to the mobile transmitter and I usualy have full signal bar). There is only one thing which gets me so angry - lags, usualy when listening music from youtube on background and browsing the Internet. My friend with Galaxy S laughs when my phone gets his lucky mood and he sees it, his phone is more smooth then mine, it's crazy.
Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.
pegnose said:
Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.
Click to expand...
Click to collapse
Mahdi is mod like Cyanogenmod, we have unofficial support from alfsamsung (he's great developer) you can find the thread in Optimus 4x development section (without "original"). He did a lot of changes in baseband driver & ril. Btw that reorganising bug is only in stock isn't it? I think in CM based roms is only crashing ril and asking for pin again or full crash of ril and baseband driver so you have to reboot your phone.
When I was running stock I never saw it (that reorganising..) I only saw someone talking about it here on xda.
I'm not optimistic because LG said that our phone won't get any update in future. I just don't think that they changed their opinion because of few people crying to their hotlink.
I'm so sorry about my english, my skills are just terrible
An update for Germany is out:
http://www.android-hilfe.de/lg-optimus-4x-hd-p880-forum/623458-update-v20c.html
Looks like the problem is gone!!!
Hi all, I'm certain this info can be found in tons of places on this forum, but I'm brand-new (first post, woo!) and that amount of info here is a little overwhelming.
So, first thing's first: Pumpkin's forum is crap, the one moderator there either doesn't allow posts about android upgrades or flatly denies it isn't possible (I know they're lying).
I have a Pumpkin RQ0248, using an RK3188 cpu and still running Android 4.4.4. I've learned here that it's also known as "MTCB-KLD6-v2.85". It seems like my car radio CAN be upgraded to Android 5.1 (which is awesome), but I'd just like to check some facts with the experienced folks here:
- I download an "Update.img" file to a... microSD card? USB? (Does it even matter? Pumpkin's site says microSD in the maps slot).
- I run the System update button (or whatever it's called) and select the above image file. Let it do it's thing. It'll reboot, at which point I do a factory setting reset? I believe so.
- The file I've downloaded is "KLD_LP_rk3188_p_2016_05_11", I think it's the right one, but I want to be certain. Perhaps there's an even newer one?
- While poking around (and getting confused) I saw some people claim their radio app sometimes would stop working? Is that a regular thing? I know how to enter the "factory" settings (using PW 126) and saw that some people just had to change their radio chip version? Is that trial and error or is there a specific one I should use for mine?
Thanks for all the help in advance! And sorry for the newbie questions!
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
cmetaphor said:
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
Click to expand...
Click to collapse
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
halloj said:
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
Click to expand...
Click to collapse
ROM? I thought MCU was the important part that needed to be "flashed".
Can't post links to photos... not enough posts yet... Just tell me other info is required beyond what I posted originally?
I know my screen size is 480x800. Recovery mode, I don't know right now how to get enter it, but I know it exists (button combination held when booting).
Was the file I mentioned in my first post not the correct one to use?
The "official" response from the Pumpkin trash "tech" is that there is no real upgrade for my unit, but he provided a link for me to try it (aka removing any responsibility for bricking the radio). So full of crap, I've already seen RQ0248's being sold online with Android 5.1
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
dmband64 said:
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
Click to expand...
Click to collapse
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
cmetaphor said:
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
Click to expand...
Click to collapse
I'm not sure what the benefit is of the 2.96, but it's newer so it must be better! That was just the latest so that's what I used. THere are a ton of benefits so you should read the thread....but here are a few: Malaysk offers quite a few optimizations, built in root, customization including skinned apps and radios, and MOST importantly in my opinion is the FUSE support...which means the full 16gb of system space are available to use for apps. You won't run out of space again. Yes there are other music apps included in his ROM as well, but I haven't used them much so I can't really speak to their functionality...but I'm sure it's better than the stock app.
But, do the new music apps work with the steering wheel controls?
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
cmetaphor said:
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
Click to expand...
Click to collapse
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you havent bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
typos1 said:
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you haven t bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
Edit: Yay! This forum had an ignore button! Just learned that today too.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
Click to expand...
Click to collapse
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
cmetaphor said:
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
Click to expand...
Click to collapse
I didnt write anything that was unkind, snide, sarcastic rude or jerk, I simply gave you some information about where to look to avail yourself of some basic info about your headunit, I didnt have to, I wasnt paid for it, yet I did, in my book, thats "kind". What you require, it seems is someone to spend their time re-typing out whats already been written in other threads into this thread, because you cant be bothered to either look for it/read it yourself (known on xda as "spoon feeding").
It seems that you also havent bothered to read the post I just made properly either, because if you had, you would have seen me refer to "the wiki" (also linked to in the sticky in the very first post of this forum AND in my signature !) and would realise that you dont need any "magic" to learn what a "Klyde" is, you just need to read something mentioned TWICE on the screen in front of you !
In your previous post you also complained that "so few people reply here", if you read what I wrote in my reply, you ll realise why that is - theyve all read the basic info and are replying in threads that apply to ALL MTCB/C headunits.
On xda youre supposed to read stuff and find out for yourself and if you cant find the info you need or dont understand something or need help with something then there are loads of people (including me - look at my thanks meter) who will happily help you. But its clear that you havent read a thing, nothing, not one bit, not the sticky in the general section, not the Q&A section's first thread, not the wiki, nothing, diddly squat. So to help you in the way you want, I would have to write whats already been written and I aint doin that - you read at least the basics of it and ask questions if you dont understand something or cant find it.
Curtusz said:
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
Click to expand...
Click to collapse
Sounds like the ROM you were given was more up to date ROM - new features often have to be enabled by updating the MCU too, as that controls a lot of functions. Its also because you now have an MTCC MCU - 2.85 is MTCB, 2.91 is MTCC and older ROMs dont work with older MTCB MCUs.
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Curtusz said:
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Click to expand...
Click to collapse
I m using booroondook's ROM. When you say double booting do you mean it boots, shuts down then reboots ?
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Curtusz said:
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Click to expand...
Click to collapse
Thought so, not heard of that before, strange.
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Curtusz said:
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Click to expand...
Click to collapse
They get their ROMs from Klyde, the manufacturers of the units !
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
POMF2K said:
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
Click to expand...
Click to collapse
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
camaro322hp said:
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
Click to expand...
Click to collapse
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
I'm curious how do you keep the device from getting OTA updates without root access?
I'm really not okay with having a device without root access. The ability to make my own recovery images is an absolute must. I'm also too invested in tasker automation to stop now.
POMF2K said:
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
Click to expand...
Click to collapse
No, has nothing to do with picture quality. The camera either works or it doesn't. When you unlock bootloader, the camera stops working (solid green pictures). When you apply DRM fix, it starts working again as it did originally.
POMF2K said:
I'm curious how do you keep the device from getting OTA updates without root access?
Click to expand...
Click to collapse
I disabled the update centre and update service using this method - no root required.
Does anyone know if this method to keep the wifi calling and fingerprint reader simultaneously active works after recent ota updates?
Still searching for someone on T-mobile US with this device that can verify that I can achieve all 3 at once (Root, Fingerprint Sensor, T-mobile Wifi Calling).
Please help.