Hey there,
First, I have to say hello to this nice community. I'm using this great ROM mentioned in the topic and everything seems to work very smooth.
But I have a problem with Bluetooth. For access authorisation my Device has to be visible all the time. There is also an option in Bluetooth-settings for this and this seems to work.
But, something is wrong with the visible-option. My device is identified by other Bluetooth-devices but not as a phone (see attached file). I think this is the reason why I can't authenticate with my smartphone.
The screenshot was made from another Android phone. The Bluetooth name of the Desire Z is "dev"
p.s. maybe someone can put this issue to the right thread. I don't have permission to write in the dev-forum.
http://forum.xda-developers.com/showthread.php?t=1492461
EDIT 2012-02-17: Seems that this problem occures in every ICS-Release for our Desire Z.
It might just be a driver issue. Most phones nowadays have issues with getting Bluetooth working actually so its hard to say
Sent from my HTC Sensation using Tapatalk
The rom is still pre-Alpha. Also I'm sure it has already been reported as a bug by someone. Wait for the CynogenMod team to work out the more major bugs first.
I have another problem
Text gets "fussy"
h t t p : / / db.tt/1tCz8Jj6
hywelmartin said:
I have another problem
Text gets "fussy"
h t t p : / / db.tt/1tCz8Jj6
Click to expand...
Click to collapse
This is an issue which is very much discussed in ICS ROMS for Desire Z.
In the thread about this ROM it's written:
- No more Graphical Glith - Report : Still there but i tink this is rarely
Seems that this problem occures in every ICS-Release for our Desire Z.
Just tested with Andromadus Alpha v12 and had the same issue.
EDIT: Same with Burstlams ROM on ZTE Blade.
But with the ALPHA 6 of CM9 it worked - it was recognized as a phone.
Same issue on "Andromadus Alpha v13 [ICS]"
Related
When i make a call the call is immediately interrupted (after a short *bleep). Getting called works though.
I have done a full-wipe and using:
- LeeDrOiD V2.3.4 BETA 4 R2
- Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2
After some simple tests i found that wifi was interrupting the call. When disabling wifi i can make calls again.
I think i have the corresponding logfile (using adb logcat).
I am aware that the rom i am using is still a beta, but since i haven't (yet) found any other user having the same issues i decided to create this question thread. Who can give me some advice to fix this problem? Thanks!
When wifi is on, but not connected to a wifi-network i can make phone calls. Only when connected to a wifi-network, the call immediately gets disconnected after a short bleep.
Found only a single user having simular issues, only he runs on another ROM:
http://code.google.com/p/cyanogenmod/issues/detail?id=2732
E-mailed this person but we both came to the conclusion his problem was different and solved by a ROM update.
Attached is the logcat output. Three lines got my attention:
Code:
D/CallNotifier( 7167): - onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1300277007142
D/CallNotifier( 7167): - DisconnectCause is ERROR_UNSPECIFIED: play TONE_CALL_ENDED!
D/InCallScreen( 7167): onDisconnect: incoming: false state: DISCONNECTED post dial state: NOT_STARTED, cause=ERROR_UNSPECIFIED
Full-wiping again and installing LeeDrOid again didn't fix the problem. Installing CoreDroid V4 didn't fix the problem either.
Anyone got some advice how to fix this problem on the Gingerbread beta releases?
Just letting you guys know my issue is resolved, maybe it will help anyone later on experiencing same issues.
I found out not only disabling wifi will make outgoing calls work again, also changing the network settings from 'gsm / wcdma automatic' to 'only gsm' and reverting back again temporarily fixed the problem (outgoing calls were allowed again while wifi was enabled).
I Just flashed a new radio: Radio_12.41.60.19_26.06.04.14_M_Test - HTC Ace Gingerbread S Generic 2.16.0.0
Now everything is working as it should be! I thought it wouldn't be the radio as the issue was solved on an older rom with the same radio.
Edit: The problem persists. At first it seemed to work, but later on the problem came back. It looks like the Gingerbread beta contains a bug, but strange enough not effecting much people... Comparing the dmesg log with a dmesg log of a successful call pointed out that the next few logs are missing on a interrupted call:
Code:
[10894.955902] wds: 0020 @ 01
[10894.956024] qmi: wds: got handle 0x02a73d58
[10894.956542] wds: 0022 @ ff
[10894.956665] qmi: wds: CONNECTED
[10894.957977] wds: 002d @ 01
[10894.958068] qmi: got network profile
[10894.959259] rmnet_open()
Can anyone figure this out?
Isn't there anyone that can help me find out what is wrong or how to troubleshoot this furthermore? Can someone help me analyze the log files. The last thing i want to do is revert to stock and send the phone back for repair . Please advice!
I think it is a kernell/radio issue....
Yes it really looks like a kernell thing, now running excellent on LeeDroiD HD 2.2.2 with LeeDroiD's kernel 2.2.8 using radio 12.28e.60.140fU_26.04.02.17_M2. Still find it strange i am one of few experiencing it. That's the only thing that makes me uncertain about this being a kernell issue, as others should then have experienced simular problems wouldn't they?
I think i will just have to wait for a new (major) kernell release of GB.
Hey,
I am using CM7 and get this issue as well.
Sometimes when I call people all I get is a beep and it disconnects.
Switching to 2g works for me but that is not a good solution imo.
Wish I could get this fixed.
I am glad to see I'm not on my own on this one! 2g isn't a fix for me either, its a not-so-pleasant workaround. Temporarily disabling wifi was a faster workaround, maybe this works for you too. I went back to 2.2.1 because of this problem, maybe you should too.
Please keep me updated!
I always have wifi off when out and about.
Did you get stock rom or something? Post a link to the rom please.
I am just about to try cm7 rc3 - out today.
I installed RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed.exe from http://forum.xda-developers.com/showthread.php?t=824357
After that i gained root and ENG S-OFF again, did a full-wipe and installed LeeDroiD HD 2.2.2 with LeeDroiD's kernel 2.2.8 (http://forum.xda-developers.com/showthread.php?t=842802) followed by radio 12.28e.60.140fU_26.04.02.17_M2 (http://forum.xda-developers.com/showthread.php?t=877295)
So what do you think I should do?
Go back to stock and stick with it?
That depends... I am no expert on this as I am on the same boat as you are. If this is disturbing you as much as it disturbed me you could give the ROM I am now using a go, that's LeeDroiD HD 2.2.2.
Sent from my Desire HD using XDA Premium App
Well I am using CM7 rc3 for now with the latest radio.
I have also changed to GSM auto (PRL).
Will report back tomorrow.
did you set up an voip-account with your cellphone?
I am imagining a scenario like this: voip-Account set up and the option "use internet calls" set to "for every call" (may be called differently, my rom is set to german).
Now, if you enable Wifi, your phone would try to connect to your voip provider and if that fails for whatever reason you should be getting error messages...
If you have your phone sync your settings through you google account, that would explain the error reappearing after full wipe, new radio software and even on a new rom. Flashing a 2.2 rom would make the issue disappear though, as 2.2 doesn't support voip...
Thanks for your reply! Unfortunately this was not the case. There weren't any SIP-accounts configured. I also tested this by not configuring any synchronization accounts after fully wiping and installing a Gingerbread ROM.
Sent from my Desire HD using XDA Premium App
HamsterHam said:
Well I am using CM7 rc3 for now with the latest radio.
I have also changed to GSM auto (PRL).
Will report back tomorrow.
Click to expand...
Click to collapse
Yesterday-evening i installed CyanogenMod 7.0.0-DesireHD and I did not have any issues. After that i installed CoreDroid HD GB 2.3.3 V5.1 but with that rom the problem came back. How did it go for you, you didn't report back.
So does anyone know what the similarities and differences between those two roms are? Both are running on Android 2.3.3 (Gingerbread). CM is No-Sense while CoreDroid is Sense. Are both using the same kernel? Could a difference in drivers be causing our problem? How can i find the drivers that are being used?
Have u checked your apn settings? I had to manually enter proxy and port after cm7 stable install for my phone to work.
Sent from my DHD
Yes, checked those too. At the moment happily using CM-7 without any problems, so as long i stick with this rom everything is fine. Not really a solution but at the moment very happy with this ROM.
hey whats up ..... guys i just want help from you guys if you can tell me the solution , the problem is at first my CWM ( latest ) when installed visualize anything except for the 4 keys of HTC wildfire s i managed to get rid of that with a software called [email protected] somehow but now even when i installed the Cyanogen mod 7 its still doesn't shows up the screen and 4 keys are lightning helpp pleaseeeee :'(
mindfreak62 said:
hey whats up ..... guys i just want help from you guys if you can tell me the solution , the problem is at first my CWM ( latest ) when installed visualize anything except for the 4 keys of HTC wildfire s i managed to get rid of that with a software called [email protected] somehow but now even when i installed the Cyanogen mod 7 its still doesn't shows up the screen and 4 keys are lightning helpp pleaseeeee :'(
Click to expand...
Click to collapse
Hello there. If you'll follow me over to this thread and read for a bit you'll notice there are other users with the same issues and that it is due to some change in devices manufactured after the first quarter of this year.
For a currently unknown reason these new devices are incompatible with the kernel used by CM builds and thus recovery images. CM7 and CM9 kernels fail to properly handle the displays in these devices. ROMs based on stock kernels for gingerbread appear to lack the flaw an will initialise the display correctly.
If you could grab some logs from your broken CM7 install and post them it would REALLY help track down the issue and give the developers something tangible to fix. Ciao!
Hello,
I detected the following systematic problems of cm9..11
1.) Skype cannot be started at all. It does not even react on a click of its icon. And no error message appears.
2.) the akku load status is shown incorrect during load process. E.g. after 4 hours load it shows 37% instead of true 100% (which is shown after reboot).
3.) The wonderful app 'lgCamera' runs very slow and jerky. This was fine in Android 2.x versions.
4.) the FM radio app for the WFS radio tuner (no internet radio!). How can I find it (and flash it into the system folder as a system app)?
I suppose that everybody can confirm my problems!?...
Are those already known by the development team? Cause I wonder that they are not fixed in ALL CyanogenMod versions yet!
Will there be a chance to expect their fix soon?...
5.) Furtheron I have big compatibility problems when flashing cm9..cm11 ROMs and others. Error message: "cannot load volume /misc. Can't partition non-vfat: /storage (vfat)". For nearly each ROM I have to change the recovery. Currently I change between the following recoverys (one of them allways works):
twrp-2.2.2.0, twrp-2.7.1.0, Phil-Z 6.43.7, cwm-5.0.2.8, cwm-6.0.5.3. Nobody else having that problem?...
Is there any recovery version that can read all 'formats' of zip files?...
Will there be compatibiliy at least at the backup files between all of them?...
Thank you VERY much for a quick help!
1.) not compatible anymore, say Thanks to Skype
2.) This is probably problem with battery not reading voltage correct anymore on charger (happens) for me on all roms even stock. (After 100000 of flashes and almost 3years old down sucked battery
3) ics and up isn't made for this phone, slow downs and other incompatibility can happen.
4) There is a solution called spiritfm(free) Google it, you will find the xda thread.
5) twrp 2.2.2.0 and cwm 5 is working on all ROMs beside newer kk builds (needs recovery compiled with TLS support, newest ones available)
Greetings Kevin
Hallo Kevin,
I am so glad that you answer! Thank you very much!!
to 1.) Yes, I realised meanwhile that Skype 4 ist still running fine. So the reason why the new Skype 5 version does not work on Wildfire S (or even on all CM versions of all devices??) you don't know!?...
to 2.) So this is a general Andrid 4.x problem of Wildfire S device only?... (cause e.g. on Galaxy S4 stock (of my girl-friend) it works fine!...
to 4.) Thank you. I installed this free version '0918fr.apk' but I get the error message (su rights confirmed): "Error: No FM accessible. SU: 0 Fm:BC2 SU:0 Bt:3 Ht:0 Mo:BCU". It does not seem to be compatible although I have read everywhere that it should work. Is this maybe antoo old version? Or what can be the reason?...
to 5.) So I used newer version 'cwm-6.0.5.3' and 'twrp-2.7.1.0', as I mentioned, but then these versions do not support older version than KK. E.g. 'CronMod-INT2EXT+_signed.zip'. This is the problem. Any solution?...
Is TLS ment as 'Thread-local storage'?...
Another short request:
a) Video recording with cm11 on Wildfire S works now without any patch. But if I record a video longer than about 5 seconds and I want to watch it directly after having stopped recording (timeframe about 7 seconds) then the camera app crashes. Can you confirm that on Wildfire S? What can be the reason?...
If Olivier's camera patch will help here as well I have not tested yet...
b) Management of Launcher and App screen is somehow circumstancial or not even possible. This is why the option 'Homescreen' is missing in 'Personalization' ('cm-11-20140816-Nightly') although the related screenshots of cm11 in XDA show this option!! E.g. App icons cannot be sorted alphabetically or cannot be manually moved within the screen. Or the home panel is the most left one instead of the middle one. Etc.
Any reason why the option 'Homescreen' was deleted (in XDA cm11 screenshots for Wildfire S still show it!! S. http://forum.xda-developers.com/showthread.php?t=2735775 )?...
c) CM11 OTA update suggests me 'cm-11.0.0-RC9' as the first in the list. Is this really more actual than the installed 'cm-11-20140816-Nightly' (version 11.0-20140816) ?...
d) In this version the Email system app is missing. Why?
Any zip to flash it anywhere? Or do I have to use one of the market?...
e) No warm reboot option available anymore in cm versions?...
Thanks for your help again, Kevin!
Many greetings, Falk
to 5.) I could solve that problem meanwhile by myself. I downloaded a modified version of cwm 6.0.5.3 here:
http://click.xda-developers.com/api...5.0] - Post #52 - XDA Forum&txt=the new build
But I still do not know what was modified! You?...
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Beeefalo said:
6.) you forgot the ever present mobile data bug at least for cm9 and cm10. Which no1 evens bothers to mention
Click to expand...
Click to collapse
Because it does not exist? I never faced any bug like that.
aWFSuser said:
Because it does not exist? I never faced any bug like that.
Click to expand...
Click to collapse
oh, its super present .
It was a "common" problem in cm9, cm10 based roms, at least judging from the various threads dating back to 2013. And as I discovered yesterday its also present in CM11 RC9 for me.
Occurence of the bug is very random and seems to be bound to certain providers which makes it hard to debug/fix i guess.
Sadly, from what I've read "deal with it and toggle airplane mode when you need mobile data" or "install cm7" are the ways to handle this bug.
cheers
Beefalo
Q&A for [ROM][4.4.4][TeamCanjica] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
question
Hi guys, i have a bug: calling history not show
Problem
It repeatedly giving error com.android.phone has unfortunately stopped . And the ROM is able to search the mobile networks but there is bar in signal strength . Means it not getting the signal .
Rest everything is ok .
PLease help me ASAP .
Does video recording work on your phone? Because I have camera app crashing all the time after switching to video.
Some Question about this ROM
Hi,
my Ace2 is still running under Stock Android 2.3.6. and I would like to Upgrade to CM.
For me stability and a working phone are more important than having the latest android Version, so my question is - which CM Version would you recommend? CM11 or is CM10.2 more stable? And is the latest version also the most stable one?
Is it correct that the only issue with CM11 is the Live streaming problem and with CM10.2 the memory leaks reported by some users- or are there more problems with these ROMS? A well working GPS is also important for me - is this the case?
And how difficult would it be to go back to stock 2.3.6. if CM is not working well for me?
Sorry for all the question and thanks in advance!
bootloop on the latest build from Rox
stuck on boot loop as is:
http://forum.xda-developers.com/showpost.php?p=56027724&postcount=5377
cm-11-20140807-UNOFFICIAL-codinap from @ace2nutzer
Install the firmware, reset the smartphone, then GAPS. If all at once, when you start on selecting the language setting is not. This, in my case, I tried several times. @ace2nutzer when to expect an update of your firmware
Hello
i have the i8160L,are the links you gave working on that version?
also if its working and i root that cm11,can i get back to my original firm later?
thanks
Bootloop
Rox, are you going to be fixing teh bootloop in the last build?
Also: the call log is empty, is there any fix for that?
Blackscreen
I want to record a logcat showing a black screen ocurring on wake up, with the s6d driver, in order to help in the resolution of the bug...
What's the priority level I should set for the catlog? Verbose, Debug, Info, Warnings, Errors, or Fatals?
Reboot loop with 1014 update
WARNING: I'm stuck in a reboot loop after updating to the recent 1014 version. Can't even get into recovery mode anymore. Flashed stock rom, installed CM again: same picture.
Grmblprmf said:
WARNING: I'm stuck in a reboot loop after updating to the recent 1014 version. Can't even get into recovery mode anymore. Flashed stock rom, installed CM again: same picture.
Click to expand...
Click to collapse
Flash chrono kernel..1014 build got a kernel broken...
@hackstorm1989
I have the GT-I8160L too.
This ROM specifically i haven't tried yet, but I've installed 2 different builds of NovaFusion CM11 (http://forum.xda-developers.com/showthread.php?t=2568105) and now I'm running J-TEAM AOSP (http://forum.xda-developers.com/showthread.php?t=2588054).
As TeamCanjica, both these ROMs are for the GT-I8160, but can be installed on GT-I8160L by changing the lines in the updater-script of the ROM (META-INF/GOOGLE/ANDROID/) where it checks the model of the device. I also read that the tee folder (system/lib/) of the ROM must be replaced by a copy of a tee folder from a running GT-I8160L firmware with SIM and carrier services properly working.
I've followed this guide:
http://brasildroid.com.br/showthread.php?t=23729
So, just by checking the updater-script of teamcanjica CM11, i GUESS it could be installed on GT-I8160L through the same 2 steps that i did with the other cited ROMs.
Also, I remember seeing other members running these ROMs on the L version while reading these 3 threads. I really wanna know what exactly differences are between these 2 device versions.
Please anyone let me know and correct me if I've posted any wrong information.
@soraxx
I can´t post in the main thread yet (10 post treshold), but maybe you read this or someone can copy this into the main thread.
I had exactly the same problem (audio but no video picture) and a simple change from stock browser to firefox solved it - Maybe it works for you too.
This should be main thread from now on
Same problem
Bootloop
14.10 bootloop
@ace2nutzer
I don´t agree with your statement that everything is working with the 07/08 build. I am using that build and the camera video recording is definitely bugged.
Elder666 said:
@ace2nutzer
I don´t agree with your statement that everything is working with the 07/08 build. I am using that build and the camera video recording is definitely bugged.
Click to expand...
Click to collapse
read this carefully:
http://forum.xda-developers.com/showpost.php?p=56171431&postcount=5436
Hi guys,
In stripped versions I notice camera quality and time of battery are worse... I'm going to try the build made for ace2nutzer 07-aug-2014 and stay on it by now.
Did anyone of you guys have the LCD-wakeup problem with horizontal grey lines? (it fixes itself after couple of attempts to unlock the phone and mostly occurs after probably deepsleep OR if there is cold (?) outside ;]
IT DOES NOT occur on CM10 by dr.harald or ANY stock Samsung firmware (also Gingerbread is NOT affected).
But occurs on any 10.1, 10.2 and 11 by anyone (so far ;/
My Ace2 is using pri_lcd_ws2401 driver
Never happened to me and I used many roms, including CM11 by team canjica now.
However I don't know how to check my driver
You can check this under
/sys/devices (you can browse there using Total Commander or any other file manager capable of browsing the whole filesystem on the rooted phone)
Here you should have either :
PRI_LCD_WS2401.0 (like I have)
or
PRI_LCD_S6D27A1.0
Currently I have installed (for testing as usual before restoring the CM10 from backup) CM11 from Team Canjica with the following kernel by PolishVodka :
http://www.mediafire.com/download/yie7ps4irxz5zbl/KERNEL_KK.zip
(I've found it on the following thread : http://forum.android.com.pl/f696/po-wgraniu-cm11-paski-na-szarym-ekranie-481605/ , however it does concern the S6D27A1 and I'm kind of confused now... as it seems to work (at least it does for one-two hours since I loaded the new kernel well... for sure I WILL BE CONFUSED if it woud work longer than one day without "black screen bug" since I am pretty confident that I have WS2401...
Maybe I do something wrong while checking the driver, etc?
One way or another the device drivers available in the filesystem are in :
/sys/devices/pri_lcd_ws2401.0/subsystem/drivers and I have there
pri_lcd_s6d27a1
and
pri_lcd_ws2401
so... since the ONLY driver entry in /sys/devices
is pri_lcd_ws2401.0
it suggests that I am using the WS2401 one
Anyway... I will post later some more info on this
Ok, it seems to work fine - no issues so far. hail to PolishVodka!!!
P.S. However I thought that the kernel from http://forum.xda-developers.com/galaxy-ace/ace-2-develop/kernel-ace2nutzer-kernel-20141027-t2920365 will be working fine, unfortunately for my WS2401 still the "black screen bug" ;/