That's a driver issue. Reinstall drivers for your phone in Windows. ADB works in recovery. ADB Push feature has been my best friend for so long.
[ROM][M7][KK][4.4.4] CyanogenMod 11 Official Nightly Builds
- Thread starter tiny4579
- Start date
That's a driver issue. Reinstall drivers for your phone in Windows. ADB works in recovery. ADB Push feature has been my best friend for so long.
Thanks. Tried to resinstall, but still not working... Do you have a link to the exact driver I should install for W8.1?
Weird, I just installed this http://xdaforums.com/showthread.php?p=42407269 in to my computer at work. It's a new computer so I have never connected my phone to it. After the installation I ADB in to my phone and worked. So, I "ADB Reboot Recovery" and it rebooted to recovery. Than I "ADB devices" and it showed my phone.
I am running Windows 7 64bit. I did not install any driver except ADB/Fastboot from the link provided. I don't know what else to say.
Last edited:
Cheers man, but still when you want to receive MMS you have to turn on Mobile Data
so it's solving only 50% of my problem...
Thanks, but still having issue...
In fastboot mode, the phone is recognized as an "Android USB Devices" and fastboot is working properly. But in TWRP mode, the phone is not recognized properly anymore by Windows (listed in other devices). So it is a kind of driver issue, but only in recovery mode... Any idea? I will anyway try to find an USB OTG cable.
Finally got it to work... I tried reinstalling, manually pointing to the the right drivers (extracted them manually) until phone was also correctly seen by Windows, also in TWRP mode and not only in fastboot mode. Still not fully sure what/why it did not work properly without those manipulations.
Thanks all for your support!
Which camera are people using with CM11? Google's or CM11? I saw a bunch of camera commits a few days ago.
H
Heinz Ketchup
Guest
Me 2
Today I installed since a long Time CM11 ( 20140227 ), i do an absolutely clean Flash,
i am getting a tremendous amount of restarts while configuration of the System...
Last edited:
A simple build.prop edit fixes it.
Sent from my One using xda app-developers app
---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------
Do you know if it was working in M3?
Sent from my One using xda app-developers app
I believe it was. It was just a week ago where art was broken and m3 was built about two weeks ago on the stable branch.
Sent from my One using Tapatalk
is there cm11's own camera app or it's just google's stock camera app? i have Android 4.4.2 Camera v2.0.002 (937116-30).
Gesendet von meinem One mit Tapatalk
So far so good, using teamseven CPUQUIET kernel & TWRP recovery.
0 day Gapps from http://xdaforums.com/showthread.php?t=2397942
Sent from my One using xda app-developers app
Last edited:
ART is working great for me so far minus some slowly updated apps. No conclusions about battery life or performance, however.
Quick question, it seems that tap to pay in conjunction with Google Wallet is not working on CM11. As some of you may know, KitKat no longer requires a secure element to allow paying with NFC anymore because it has host card emulation built in. This is the most exciting thing about upgrading to KitKat in my opinion!!
I remember tap to pay being available for CM11 nightlies way back in January... Why is it gone? Was it ever working in the first place? How can I get it working again? Why is it that when I boot into Sense 5.5 (ViperROM 5.0.0 w/ ElementalX Kernel), tap to pay is available, but it is not on CM11?
At first I thought it's because Google Wallet thought that my phone and CM11 were international variants and therefore unusable (US Only), but it doesn't seem like that's the problem.
Can anyone possibly give me some answers?
Quick question, it seems that tap to pay in conjunction with Google Wallet is not working on CM11. As some of you may know, KitKat no longer requires a secure element to allow paying with NFC anymore because it has host card emulation built in. This is the most exciting thing about upgrading to KitKat in my opinion!!
I remember tap to pay being available for CM11 nightlies way back in January... Why is it gone? Was it ever working in the first place? How can I get it working again? Why is it that when I boot into Sense 5.5 (ViperROM 5.0.0 w/ ElementalX Kernel), tap to pay is available, but it is not on CM11?
At first I thought it's because Google Wallet thought that my phone and CM11 were international variants and therefore unusable (US Only), but it doesn't seem like that's the problem.
Can anyone possibly give me some answers?
The AOSP NFC statck doesn't have the proper code for HCE. GPE and sense have it since they don't use the open source NFC NXP code.
It was removed because it was determined it doesn't actually work in AOSP. Can you confirm that Tap and Pay actually worked on earlier builds and not just showing up in settings?
Thanks for a prompt answer. That's a real shame to hear. From the sounds of it, it looks like they won't figure out a solution any time soon. I hope they figure it out. I assume the issue with the open source stack is that I causes problems with aosp roms. That or in typical cm11 fashion, they want to code their own solutions.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
Frankly if that's the attitude you have about Android development you should stay on stock because there's always the chance for something to break. Especially when you're talking Cyanogenmod nightlies. So take your bad attitude elsewhere it will not be missed.
Sent from my One using Tapatalk8Have just submitted my first patch. I have found little mistake in our amp code that made left channel not being played at all. Instead we had right channel played through two speakers.
http://review.cyanogenmod.org/#/c/57093/
Hope it will be merged8
The speakerphone mic issue is subjective in the sense that people who rely on speakerphone say it's broken and those of us (like me) who rarely use it, except to listen to voice mail, say it works fine. My testing shows that only the rear microphone is used for speakerphone, so depending on how you hold the phone it's easy to cover the mic in a way that it doesn't pickup correctly and the remote party cannot hear you. It's flaky, at best.
Proximity sensor work fine on my device (screen goes off with my hand about 2" from the sensor), by I remember a bunch of tweaking on 10.2 because the correct values vary among devices and their sensitivity.
Haptic feedback does occasionally stutter since the switch to msm8960 kernel. I only have it enabled for hardware keys, but those that have it enabled for keyboard use notice the stutter more frequently.
Also, since msm8960 kernel the notification LED sometimes get stuck on solid amber vs flashing, unlocking the device gets it flashing again.
As for support, until M5 the stable builds were based on m7 kernel, so it wasn't possible to report these msm8960 bugs on JIRA.
Also, I'd say that it would make sense to frequent XDA more often if you are a device maintainer because 99% of the casual CM users are going to come to these forums to report bugs and resolve issues, most will never open a bug on JIRA or hop on the IRC channel.
I agree with @sabret00the regarding the development model for CM, it has worked in the past but there's much room for improvement if CM wants to make a move to a widely used product. A wide tester base that includes many casual users is key, so there needs to be a (user friendly) mechanism for those users to report issues on incremental builds. Maybe that means abandoning nightlies for weekly builds that are more stable and feature targeted so that users can report issues.
Maybe an app built into CM to report issues directly from the device, uploading logcat and last_kmsg and other state that's helpful to debugging the issues.
We do appreciate the work you and other's have put into CM on m7 to bring it to this point, but I'm sure you can see the frustration that exists from long standing issues which are known to the user base but the maintainers aren't aware of or have the appearance of being ignored.6
Yup, I'm working on a fix. Hopefully will commit in the next couple days.
