Hi there,
Is there anyone who has, or knows where to get the following cyanogem rom?
its needed for certain nfc functions.
update-cm-9-20120321-NIGHTLY-crespo-signed.zip
Its totally unfindable.
kabeen1 said:
Hi there,
Is there anyone who has, or knows where to get the following cyanogem rom?
its needed for certain nfc functions.
update-cm-9-20120321-NIGHTLY-crespo-signed.zip
Its totally unfindable.
Click to expand...
Click to collapse
Detail which functions you're talking about - any later CM9 nightly should have the same features, and if you're talking about Tapp's HCE implementation, that was also in CM10/10.1, and I believe also 10.2.
It is not in 11.0 as that was replaced with KitKat HCE - which unfortunately doesn't work on older devices like crespo.
Related
Hi,
I've been running cyanogen for awhile but I've been stuck on v10.0(android 4.1.2) because avrcp is not available on the new version...(audio track tags over bluetooth)
is this fixed now in the new version, as advertised by google?
can anybody confirm?
thanks
updating is useless without that feature, my car stereo doesn't have a usb port so I need bluetooth
After trying it out myseft
its working fine
but broken:
the data is sent, but it is sending the artist at the place of the album name andI always get no title as artist name
so it might only be the way the application is reading the mp3 tags that is faulty
hope this will get fixed
Update:
If anyone is interested...
I flashed CyanogenMod 10.2 Nighties (Android 4.3) on my device
All the issues I was having in the tryout of another version of 4.3 are fixed
it's working same as I had in 10.0
Thank You CyanogenMod :good:
prunn said:
Update:
If anyone is interested...
I flashed CyanogenMod 10.2 Nighties (Android 4.3) on my device
All the issues I was having in the tryout of another version of 4.3 are fixed
it's working same as I had in 10.0
Thank You CyanogenMod :good:
Click to expand...
Click to collapse
I can't get this to work, don't know if you (or anyone else reading this) might have any clue as to why.
I bought a brand new Ford Focus including the latest version of Ford Sync last month. I was on CM 10.1 so I obviously got no music metadata. Now I've upgraded to 10.2 (actually I've got a Xperia Ray so I'm not on official builds but on LegacyXperia ones) and still avrcp doesn't work except for the 1.0 stuff (play, pause etc). Shouldn't this work out-of-the-box? Or any special music player needed (I've tried with Apollo and Subsonic)?
/Daniel
edit: Apparently my ROM simply hasn't got support for this yet. Something with Bluetooth Firmware that is not yet upgraded. Explains...
DanielMalmgren said:
Apparently my ROM simply hasn't got support for this yet. Something with Bluetooth Firmware that is not yet upgraded. Explains...
Click to expand...
Click to collapse
I'm using the standard CM10.2 nightlies as well, and it's not working for me either. GNex Maguro build 20130826 was the last time I flashed, but I haven't seen any bluetooth changes made since then in the changelog so I'm assuming it's still not fixed.
Is the Bluetooth Firmware in the ROM? Or is that a part of the Radio that gets flashed separately?
frozen-solid said:
Is the Bluetooth Firmware in the ROM? Or is that a part of the Radio that gets flashed separately?
Click to expand...
Click to collapse
I think (but then again I'm no Android guru, so I'm not quite sure) that the Bluetooth firmware is one of the files in /sys/etc/firmware, in my case I think it's a file named TIInit_7.6.15.bts. But I'm not quite sure if this file is something that the person cooking the ROM fixes or a file that has to come from the manufacturer of the Bluetooth chip.
/Daniel
It looks like you can get the file from https://developers.google.com/android/nexus/drivers?csw=1#magurojwr66y
The tarbell has a .sh script in it. I have no idea if I can just run that .sh file on my phone and have it work. I've never dealt with actual drives before.
frozen-solid said:
It looks like you can get the file from https://developers.google.com/android/nexus/drivers?csw=1#magurojwr66y
The tarbell has a .sh script in it. I have no idea if I can just run that .sh file on my phone and have it work. I've never dealt with actual drives before.
Click to expand...
Click to collapse
You just run that file on a Linux computer and it will first ask you to accept the license and then it unpacks some files. One .hcd file and some .mk files. Not really sure what to do with them though
/Daniel
Hello,
I done everything. Installed BUSYBOX Pro . Tried DSPLOIT, ZANTI, WI.CAP. Any sniffers do not work on my device .
It is ROOTED 4.4.2 kitkat flashed wtih werewolf custom rom.
Can anyone help me to run apps like this?
Gradz,
Head16
Head16 said:
Hello,
I done everything. Installed BUSYBOX Pro . Tried DSPLOIT, ZANTI, WI.CAP. Any sniffers do not work on my device .
It is ROOTED 4.4.2 kitkat flashed wtih werewolf custom rom.
Can anyone help me to run apps like this?
Gradz,
Head16
Click to expand...
Click to collapse
Dude, seriously? If you don't see what's wrong with your question then you shouldn't be playing
with those things. Lot's of reading and learning must you do, hmmm?
Yoda
okay, slightly dickish answer sorry.
you need certain abilities enabled at the kernel/driver level for some of the things you want
to do. which maybe be as relatively simple as patching kernel source and rebuilding or may require
rev-eng'ing proprietary drivers/binaries additionally.
you may be better served to researched a device more naturally endowed with these capabilities,
alternately a device with usb-otg support so you can use a dongle device proven to be
capable of these tasks.
ommmm
So because i used custom rom, this apps does not working?
Head16 said:
So because i used custom rom, this apps does not working?
Click to expand...
Click to collapse
sort of yes/no because the custom rom contains the software and the kernel is a custom build
it does not necessarily mean that your hardware is capable [meaning the device's capability, the kernel
having the necessary code and if there are proprietary/prebuilt source code unavailable/ binaries and firmware
support files which need to be hacked/engineered.
find out the device id of your wifi hardware and search it's id/name along with the function you are trying to perform.
for example
bcm4334 monitor mode
use the search engine that works for you, read carefully and fully and get yourself trained to follow trails of related/seemingly related
information, no matter how obscure.
good luck, may the schwartz be with you ! :silly:
m
You may be wondering why these devices haven't received Lollipop yet. The issue is, yet again, the MT8389 processor, which is based off of the MT6589.
I.nfraR.ed posted yesterday on the main CyanogenMod on MTK devices thread:
I.nfraR.ed said:
Do you see anyone working on CM for 6589? Most of the people moved to other chipsets.
Maybe chrmhoffmann and DerTeufel are still working on this, but I don't know anyone else who has not moved to newer device.
I have moved to Redmi Note 2.
For lollipop there's no mt6589 source and although it might be possible, it would be enormous amount of work. I don't have so much free time and have a full-time job after all.
I can't leave my regular job just to work on side projects.
So, no...unless someone else is on to development for Lenovo A820/A830, then don't expect fully working CM or ROMs based on Android 5+.
If for some reason I leave my regular job and have some "free" months, then I will be able to work on this project, because I still have my A820 with me. Not likely to happen.
My KK kernel is public, so anyone can continue from where I left.
Click to expand...
Click to collapse
Development support for the MT6589 has been (mostly) lost, and consequently, so has support for the MT8389. This means that, until a compatible kernel for 5.x.x appears, the likelihood of both of the devices being upgraded to CM12 or 5.x.x is very low.
That doesn't mean it's not possible, however; simply unlikely.
According to the specs the A3000 has a MT8125. Is support for this also gone?
jayvl said:
According to the specs the A3000 has a MT8125. Is support for this also gone?
Click to expand...
Click to collapse
Yes, I'm afraid this is the Wi-Fi only version of the MT8389.
I was on it..but moved to another..not at all able to boot it up..now there is a hope because of 3.4.67 kernel..again working on it???
CM12+ for A3000-H
Looking forward to CM12+ on our beloved A3000-H:highfive:
Hi guys, I have just finished doing my A3300 with Cyan's 5.1.1, all is working except for camera
I've got a bit of a question about CM-based ROM's and NFC that I can't seem to find an answer to: Do the CM-based ROMs have the ability to use tap-and-pay NFC apps? I've tried installing from the play store but instead get a 'your device is not compatible with this app'. Similarly, if I restore from a backup made in a Sense ROM, the app won't run.
Is this just an issue with the ROM - it just doesn't have that capability - or is there some way to patch around this issue. This has me stumped - any help would be appreciated.
I'm so tired with Sense. Can't deal with it. I loved CM, and I want to try out LOS or LOS based ROMs...
But there is a catch. ALL of LOS ROMs I ever tried haven't had NFC working. Sense ROMs on the other hand seems to be fine with it.
Maybe I need to elaborate... I am using NFC for Mifare Classic cards. It's the cards used by the public transport system where I live, and they have an official application to refill the said card. Too bad, all of LOS roms seems to be unable to detect it.
After all, I am ready to kind of fiddle around with the ROM just to make it freaking work. Is there ANY way to make LOS happy with NFC after all?
PS: himaul EU version.
Did you try official LOS? If the official doesn't work I think none of the LOS based roms will work.
Yes I tried the latest LOS official nightly, it didn't work.
The actual question is "how do I actually make it working". Even if it involves recompiling etc. What is actually missing from LOS which Sense ROMs do have?
Evengard said:
Yes I tried the latest LOS official nightly, it didn't work.
The actual question is "how do I actually make it working". Even if it involves recompiling etc. What is actually missing from LOS which Sense ROMs do have?
Click to expand...
Click to collapse
Drivers. If a function isn't working it's because the drivers don't work.
If you don't like the sense interface, I think it's not very complicated to replace htc apps with google apps, most of them are in play store.
Settings app of Sense 8 is very appropiate to aosp, only icons are different.
Try ViperOneM9, you can install aosp theme from the "Viper hub" from what I remember for status bar and navigation bar.
And you'll have an almost aosp interface with all things working
I was actually on Viper before. First - it is way too "clumsy" with too much unneccessary apps and bells and whistles, and second - after a while I got (apparently some bug) a horrible battery drain (and it was not caused by 3rd party apps, triple-checked).
Is there a way to "backport" drivers from Sense ROM to a LOS one? I know it is about the kernel, but maybe it's possible after all.