Related
Hi,
I'm now trying to use Android on HTC fulltime (way too many crashes in WM6.5+HTC Sense, phone becomes unusable) but I'm having some trouble with the microphone when someone calls.
I've read the problem is solved in the latest build of Froyo, but that is the one I have installed.
Is there a difference between the "Reference version" and the "BLAZN version" found on this page: http---sites.google.com-site-androidport-downloads ?
I have installed the "BLAZN version" of Froyo 2.2, which has a different update date.
Can someone recommend installing the "Froyo Reference version" to solve the microphone issue?
You can try updating to the newest kernel to try & fix the mic issue.
I thought this was resolved for everyone, but evidently not. Can you try the newest kernel and post back your results?
arrrghhh said:
You can try updating to the newest kernel to try & fix the mic issue.
I thought this was resolved for everyone, but evidently not. Can you try the newest kernel and post back your results?
Click to expand...
Click to collapse
I don't follow... :$
What do you mean with "try the newest kernel"?
I have copied the contents of the Froyo BLAZN 2.2 - cab to my phone SDcard and installed the cab. Previously I have updated the phone with all the patches and fixes HTC made available for download.
Did I miss a step in the installation process?
Some more information that might be useful:
Belgian bought HTC Touch Pro 2 (no sim-lock, no fixed telecom provider),
now running the AndroidonHTC Rhodium - Rhod100_UK (to have the correct keyboard mapping) installation with maximum overclocking and HW3D unchecked (read the updates list today and should have checked it, I know )
Thanks for your quick reply btw
ps: I didn't find anyone else with this problem, so it is probably resolved,
I think it's a small missing update in the Froyo BLAZN pack, but wanted to verify before having to reinstall the whole thing again (takes quite some time for sth stupid like importing my contact list from my SIM, linking FB contacts,... not sth I like to do on a daily basis )
Uhm... update using the kernel autobuild service?
The issue is certainly kernel related, and I know the 'newest' blazn uses a kernel that's quite old (nearly a month!)
The new reference build is quite new, but still is behind several kernel commits.
There's a new kernel out all the time - I've said it before, sometimes there's several daily patches to the kernel, sometimes there's a week between commits. Just depends on what's going on in the developer world.
arrrghhh said:
Uhm... update using the kernel autobuild service?
The issue is certainly kernel related, and I know the 'newest' blazn uses a kernel that's quite old (nearly a month!)
The new reference build is quite new, but still is behind several kernel commits.
There's a new kernel out all the time - I've said it before, sometimes there's several daily patches to the kernel, sometimes there's a week between commits. Just depends on what's going on in the developer world.
Click to expand...
Click to collapse
http-//forum.xda-developers.com/showthread.php?t=788837&page=5[/url]
Found this using google and does seem like a kernel update could do the trick, but I still don't get where I could do a "kernel update" or the "kernel autobuild service".
I have never used such function, so I'm sorry for the newb-question...
Could you hand me some more keywords/hints to find the most recent kernel build for my phone?
Is this kernel you're talking about some kind of update for the radio? As far as I get it now, it is some sort of unofficial update/patch provided by (open-source) developers?
RealReality said:
I don't follow... :$
now running the AndroidonHTC Rhodium - Rhod100_UK (to have the correct keyboard mapping) installation with maximum overclocking and HW3D unchecked (read the updates list today and should have checked it, I know )
Click to expand...
Click to collapse
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
bogdan_wrc said:
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
Click to expand...
Click to collapse
Correct key mapping is a setting in your startup.txt/default.txt file OR when you use the XDAndroid Starter application in WM, you just have to select "Rhod100_uk" (in my case, I don't know your keyboard layout?)
The latter is the easiest solution btw.
Kernel Autobuild
RootFS autobuild
Initramfs autobuild
Alright,
thank you for your help, the problem is solved!
Solving process:
1) Android Startup app didn't want to update
2) Downloaded the newest Android Startup app (version 1.3)
3) Hit "update"
4) Found new Kernel > installed
5) Working microphone with incoming calls...
bogdan_wrc said:
same microphone issue, but with the 14. Oct energy ROM.
Can you please help me ..where to find this program for the correct key mapping?
thank you.
Click to expand...
Click to collapse
For the keymapping thing, if you look in the startup.txt file on the sim card, look for: "physkeyboard=Tilt2" (minus quotes). Change "Tilt2" to "tilt2". I've found that by changing the capital T to a lowercase t, it fixes the key mapping issue. It's worth a shot.
Solving the microphone problem has triggered another one...
I had Launcher Pro Plus installed and could use the "Home key" to show an overview of my different homescreens...
Now the Home key doesn't work anymore...
Most recent builds etc are installed now, so I have no idea what to do to solve this issue.
RealReality said:
Solving the microphone problem has triggered another one...
I had Launcher Pro Plus installed and could use the "Home key" to show an overview of my different homescreens...
Now the Home key doesn't work anymore...
Most recent builds etc are installed now, so I have no idea what to do to solve this issue.
Click to expand...
Click to collapse
Check this
Best thing to do otherwise is to wait for a fix.
contributor_M said:
Check this
Best thing to do otherwise is to wait for a fix.
Click to expand...
Click to collapse
Thank you
Quite a relief it's just a minor bug,
I can live with the workaround you suggested,
instead of "Home" for the End Call button, I choose "Home, Then Sleep"
RealReality said:
Correct key mapping is a setting in your startup.txt/default.txt file OR when you use the XDAndroid Starter application in WM, you just have to select "Rhod100_uk" (in my case, I don't know your keyboard layout?)
The latter is the easiest solution btw.
Click to expand...
Click to collapse
thank you! that worked. Now, i am still fighting to solve the microphone problem...because this:
"1) Android Startup app didn't want to update
2) Downloaded the newest Android Startup app (version 1.3)
3) Hit "update"
4) Found new Kernel > installed
5) Working microphone with incoming calls..."
did not help
Hey guys, I have the same problem with the mics. I am running the newest kernels on Rhodium 400. I updated everything with the startup utility. It only is a problem when someone calls me, I can't hear them but they can hear me. If I disconnect and then call them, it works fine. Just recently, I had the problem of my mic not working in a call.
I have just been keeping my head down because I really appreciate what the developers are doing, but I figured if I don't say anything, they won't know there are still problems. Thanks again for everything you guys are doing!!
OK can we all ignore the update utility for the time being, go and grab the newest kernels and let us know if it's solved? Supposedly the newest kernels solve this issue, but I personally never experienced it on my RHOD, so I'm not a good test...
minikirchner said:
Hey guys, I have the same problem with the mics. I am running the newest kernels on Rhodium 400. I updated everything with the startup utility. It only is a problem when someone calls me, I can't hear them but they can hear me. If I disconnect and then call them, it works fine. Just recently, I had the problem of my mic not working in a call.
I have just been keeping my head down because I really appreciate what the developers are doing, but I figured if I don't say anything, they won't know there are still problems. Thanks again for everything you guys are doing!!
Click to expand...
Click to collapse
I tried pressing "Volume Up" when I picked up a call today and sure enough it worked. I previously experienced the same issues you describe. When pressing volume up I did it quickly about 3-4 times.
arrrghhh said:
OK can we all ignore the update utility for the time being, go and grab the newest kernels and let us know if it's solved? Supposedly the newest kernels solve this issue, but I personally never experienced it on my RHOD, so I'm not a good test...
Click to expand...
Click to collapse
for beginners, just like me, how and from where can we take the newest kernels?
bogdan_wrc said:
for beginners, just like me, how and from where can we take the newest kernels?
Click to expand...
Click to collapse
The search is not strong with this one...
Kernel Autobuild
RootFS Autobuild
initramfs Autobuild
The kernel by far gets more updates than any of the other two.
arrrghhh said:
The search is not strong with this one...
Kernel Autobuild
RootFS Autobuild
initramfs Autobuild
The kernel by far gets more updates than any of the other two.
Click to expand...
Click to collapse
sorry....but i still can not understand what i have to download can you please more specific?
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.
I have tried the Kitkat ROM of Evervolv and I want to report my experience.
You can find the ROM here:
http://nikez.nu/Download.php?getFile=dlc/ev_bravo-4.0.0p2-turba.zip
I found the ROM very reliable. No crash no reboot no SOD. There are 2 main bug:
1) The hotspot doesn't work.
To fix this problem is sufficient to replace the file hostapd and hostapd_cli with those in this ZIP:
http://forum.xda-developers.com/attachment.php?attachmentid=2434441&d=1386246859
as reported here:
http://forum.xda-developers.com/showpost.php?p=48161953&postcount=128
2) The browser has flickering screen. You can disable it from Settings->Apps->All->Browser and try another browser. I use Opera because is lightweight and usable. Try it out: https://play.google.com/store/apps/details?id=com.opera.browser
Without a2sd the system is very fast and fluent. If you want to use it would suggest to use at least a Class 10 sd card otherwise the app loading and even the screen unlock can take more than 5 seconds.
If you want to install a2sd DO NOT put the dalvik cache on the sd card unless you have a very fast sd card. Otherwise this will slow down your phone. I've installed 15 / 20 app and I have about 30 MB left on the internal storage, so I think this is enough. To install app data only to sd card install the script in this way:
a2sd install
N
Y
Y
There is a feature that i liked of the previous Evervolv JB and was the home screen rotation. In this ROM there isn't such feature. In my opinion is very frustrating to have the screen rotated back to the portrait mode when in landscape mode i press the home key. To enable home screen rotation I installed Nova Launcher app and enabled screen rotation by: Nova Settings -> Look and feel -> Screen Orientation -> Auto Rotate
Thank you again to the Evervolv Team.
It's 2 week that I installed this ROM and still no problems.
The olny thing I noticed sometime is a delay in the screen power on when you want to hang up a call. The screen remains black for 3-4 seconds and then if you press the power button again it work. I think this could depend on the number of the apps opened on the phone indeed this doesn't happen every time.
VPN - Another Kitkat bug with evervolv?
Hi,
currently I'm running the ev nightly-2013-12-15. Since yesterday I tried to activate a VPN connection into my home lan (connected with an AVM Router). It does NOT work. While the "internal" VPN Software does not tell me some interesting information a second try with VPNCilla shows:
--- cut here ---
Error on establish:
command '693 interface fwmark rule add tun0'
failed with '400 693 Failed to add fwmark rule (File exists)'
Possible reason: invalid server parameter or TUN device unavailable
---cut here ---
With this error message I find in google some information about a VPN problem in 4.4. BUT: my wife's brand new nexus 5 with Kitkat connects without trouble immediately with the same login data.
So what's the problem with ev here?
Any ideas?
Thanks in advance
I have never tested VPN with android though I had problems getting hotspot to work. I had to substitute the hostapd and hostapd_cli file to fix the problem (I posted how to achieve it in the previous post).
Have you tried the turba release ? Maybe the problem is related to a nightly bug.
However It is true that the Nexus 5 has a 4.4 too but the kernel version is different. The evervolv version run with the 2.6.37 kernel version because probably the driver (or kernel modules) of the HTC desire are not available for the new kernel version 3.x.x that is the version used for Nexus 5 and other official release.
So different hardware and software can lead to different behavior of the software.
The only thing that come into my mind is to try with a shell (adb shell) to manually create a VPN connection to see what specific errors are showed up.
I think this is a great rom, which runs very smoothly.
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip from yesterday on my desire.
But I have a problem using Wifi connection. At first it worked, but now Wifi wont turn on. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
It would be great if anybody knew, how to fix it.
I have not tried connecting to a VPN so far.
ProDC
Hi,
I'm running Nikez's 4.0.0p2 version and it's great! No JB rom is such stable and fast. For me, there are no bugs, but I don't use hotspot feature. Is it worth to upgrade to nightly versions? I'll maybe wait until Nikez releases next version with stable 3.0 kernel .
Do MMS work?
Sent from my HTC Desire using xda app-developers app
I haven't already tried the new nightly but I guess that it is not as stable as the 4.0.0p2. I prefer stable ROMs because I use my Desire daily. This is the most stable and faster ROM I found among Evervolv ROMs. So I would suggest you to keep the 4.0.0p2 unless you have a blocking problem with this ROM.
SemaiCZE said:
Hi,
I'm running Nikez's 4.0.0p2 version and it's great! No JB rom is such stable and fast. For me, there are no bugs, but I don't use hotspot feature. Is it worth to upgrade to nightly versions? I'll maybe wait until Nikez releases next version with stable 3.0 kernel .
Click to expand...
Click to collapse
For quimbexa :
I've tried two times but the screen only show "SENDING...". I waited for 2 hour and then i deleted the messages. So this feature could be buggy.
Why do you need this feature ? Using whatsapp or similar app it's faster and cheapest than using MMS today.
Prodc said:
I think this is a great rom, which runs very smoothly.
I have currently installed the ev_bravo-nightly-2014.01.22-squished.zip from yesterday on my desire.
But I have a problem using Wifi connection. At first it worked, but now Wifi wont turn on. It also says MAC-Adress is unavailable. What I have done was to delete the app2sd script from init.d and to install Int2ExtV2 (runs perfectly). I don't know if this can cause the interference? I have not made any other changes.
It would be great if anybody knew, how to fix it.
I have not tried connecting to a VPN so far.
ProDC
Click to expand...
Click to collapse
Are these nightlies KitKat or ...?
---------- Post added at 05:01 PM ---------- Previous post was at 04:06 PM ----------
vixx1978 said:
Are these nightlies KitKat or ...?
Click to expand...
Click to collapse
Just installed it, yup, it's KitKat
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
miir01 said:
Hi all,
I have had used CM on my z1c since August 2014 and did updates with nightlies quite regularly without any issues. But last Friday, after I updated from
cm-12.1-20150925-NIGHTLY-amami to
cm-12.1-20151002-NIGHTLY-amami
my wifi problems started. Whenever it reconnects to the wifi I see the exclamation point next to the icon, then it disconnects again. It also shows the exclamation point next to the mobile reception icon. But I seem to have mobile data connection via the mobile phone provider. However, wifi is broken, resolving domain names doesn't seem to work.
I cannot downgrade to the last working version either because whenever I try to do that using Cyanogenmod recovery, the phone is stuck in the boot animation for hours so I had to give up.
In addition, I cannot activate bluetooth anymore. Whenever I switch it on, it switches itself off after a few seconds.
Does anyone have an idea what the problem might be and how to fix/debug/investigate this any further? Where do I start looking? Any help would be greatly appreciated.
Thanks!
BTW: forgot to mention: I'm on cm-12.1-20151004-NIGHTLY-amami now but problem remains the same.
Click to expand...
Click to collapse
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
levone1 said:
You didn't happen to flash M5 kernel, did you? I've read that it breaks WiFi on latest night lies. Besides that, I've read about various people having troubles with WiFi and BT on some CM Roms, but I haven't experienced it myself. Look through the CM 12.1 thread in 'original development' forum for fixes, etc.
Click to expand...
Click to collapse
Thanks for the hint. Will search for more info in the forum. :good:
However, how would I know if I flashed a M5 kernel? I definitely wasn't aware of flashing it. My current kernel version is 3.4.0-cm-g1e19761
pr3ddi said:
I can confirm that all nightlies from cm-12.1-20150929-NIGHTLY-amami.zip to cm-12.1-20151004-NIGHTLY-amami.zip have issues with wifi and bt.
Currently it is not possible to get an older version than 20150929 from CM servers.
Does anyone have a link to cm-12.1-20150925-NIGHTLY-amami.zip ?
pr3ddi
Click to expand...
Click to collapse
I still have the package for cm-12.1-20150925-NIGHTLY-amami.zip on my phone. But can't downgrade to it because after flashing it, my z1c is stuck in the boot animation. I have waited at least 3 hours before I gave up and reflashed the newer version.
EDIT - sorry, link's dead. I should've checked it first. I would also be interested in trying an older build.
Does this help?
https://download.cyanogenmod.org/get/jenkins/127851/cm-12.1-20150928-NIGHTLY-amami.zip
Did anyone test cm-12.1-20151008-NIGHTLY-amami.zip ?
Changelog says that wifi and bt problems have been fixed.
www . cmxlog . com/12.1/amami
jira . cyanogenmod . org/browse/NIGHTLIES-1877
Giulio Cervera added a comment - Yesterday 4:28 AM
this was 2 issue:
1) the channel bonding
2) taimport was running with wrong timing, and BT and wifi mac address was not exported in /data/etc
fix for both is merged
Click to expand...
Click to collapse
pr3ddi
Just installed 20151008, I had been having major issues with wifi EAP previously (think i was on a MAY2015 build), this build's looking a lot better. The app launcher is alphabetized, and toast notifications have an icon from the app that generated them. I haven't tried bluetooth yet - my previous build was very bad with BT, I'm hoping this one's better.
Running 20151010 for over 6hrs now ...
wifi and bt are running stable and it looks like the issues have been resolved
pr3ddi
same problem
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
iSpammer said:
Same problem on my z1 with latest 20151010 any help please ? am using the normal z1
Click to expand...
Click to collapse
Not sure, no idea if they share the same hardware etc?
I've found battery life is a LOT better in this build too. AudioFX still having its moments though.
---------- Post added at 11:27 AM ---------- Previous post was at 11:25 AM ----------
ULT][MO said:
Good morning guys, I'm Italian and I'm new on the forum. I'd like to flash the cm12.1 on my device but i can't find a changelog about bug. Can you tell me the usual bugs or if I can use safely this rom without problems? Thank's a lot, and excuse me for my bad english
Click to expand...
Click to collapse
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.[/QUOTE]
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed
ULT][MO said:
So far, I'm only seeing AudioFX (equaliser) issues (which are a known bug). I haven't tested Bluetooth, but there have been issues with previous builds. Just take a full backup and then try it out.
Click to expand...
Click to collapse
I saw a new build released today and yesterday, but I haven't rooted my device and can't install twrp or cwm.
I tried to install "XZDualRecovery] PhilZ Touch & CWM & TWRP" with no root mode, but nothing is changed[/QUOTE]
I'm using TWRP for my recovery. I believe you'll need to get an unlock code from the sony website for your phone before you can start rooting/flashing.
How to install (and root) Z1C
known issues for CM12.1 on Z1C
Note that my phone has experienced random reboots, about once or twice a day with CM21.1-20151008.
I tried to flash recovery in every mode God has invented but nothing: when I open flashboot i have evry time the same fu**ing message
"sending 'recovery' (8778 KB)...
OKAY [ 0.557s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.561s"
bootloader is unlocked, installed flashtool and relative drivers
Please guys help!
Sorry if I've posted in wrong place
Solved: I've repeated bootloader unlock procedure reported by Sony. Seems ok now
Has anyone trie 10132015 build if wifi is fixed?
amnher said:
Has anyone trie 10132015 build if wifi is fixed?
Click to expand...
Click to collapse
I tried, not fixed. For me wifi it's essential
Hi,
first of all thank you @chrmhoffmann for your work and providing us with this. Due to the fact that the board software says I am a new member I can not reply in the correct thread or post links: [ROM][MTK][STOCK] fairphone FP1 kitkat 4.4.4 - http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623
Please forgive me for that.
I think I found a serious issue with the version 0.4 (MD5: 6ffe81f45278f7c9c93a592c5622d48d), I verified the MD5 and think that no transmission errors occured. You can access apps from a pin-secured (not encrypted) FP1 (not U) without entering the pin by starting the Camera and exiting it through holding the home-button down. After that one can use the unlocked home-screens but can not open the quick-settings. This works even directly after unlocking the sim-card without an initial login.
I made a sloppy video showing the issue: http://www.youtube.com/watch?v=wevclmbicVg
Strange, I don't seem to be able to reproduce the problem. Not sure what or if it is fixed. The video is a bit too blurry to see the exact things you do. Mind doing a better one? Have you tried 0.5, too?
Chris
Still an issue with 0.7?
Chris
Sent from my ahong89_wet_jb2 using Tapatalk
No, 0.7 works perfectly. The issue has been resolved. I want to apologize for the silence from my side. Thank you again for your work!