Bluetooth address CM7.2 beta - Samsung Galaxy Gio GT-S5660

Hi, I have 2 samsung gio, both flashed with the beta
update-cm-7.2.0-02242012-gio-KANG.zip
I've noticed that both phones have the same bluetooth address ( 20:78:0B:0B:00:00 ), i suppose this is a bug because i can't send files between them. How can i report it to the modders? i can't write in devs forums yet.

Guess this is enough
Sent from my GT-S5660 using xda premium

confirmed.
i'll try to fix it in new build (friday)
----- edit -----
on JOYOS my bluetooth address also 20:78:0B:0B:00:00
i was thinking its kernel fault because im changing method to generate BT & Wifi address
but, when i restore my latest cm7.2
i got actual my BT address

Hi, i've updated to update-cm-7.2.0-03092012-gio-KANG-AROMA.zip using the new kernel, without wipe data and the address is still 20:78:0B:0B:00:00.
Had you already fixed the bug and i have to wipe data or i'll have to wait next update?
Thank you
Jack
-- edit --
i've tried to run bdaddr newaddr on terminal and to find anything to try to edit in /proc but without luck

Related

[Q] Can't make outgoing calls

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.

[CM 7.1-11] [ALSO CM 7.2-RC0] wifi problems with peap-mschapv2

Hi,
it's a lot of time that I'm lurking the forum, especially the cm7 and ICS cm9 thread. Thank you developers!
I was using cm7 rc 1.5 and everything was just fine. Finally I decided to try the latest stable. Wipe cache and installed. Restart (and pull out the battery ).
Everything it's working fine, but the wireless, that was working on the previous version. Here at the university I have to use peap/mschapv2.
I try to deleted the /data/misc/wifi/wpa_supplicant.conf but nothing change. Actually after putting the information it looks like as before (but the priority):
Code:
ctrl_interface=tiwlan0
update_config=1
device_name=Motorola phone
manufacturer=Motorola
model_name=TI1271
model_number=1271
serial_number=012345
device_type=1-0050F204-1
os_version=80000000
network={
ssid="Wi-Fi_UniNa"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="password"
phase2="auth=MSCHAPV2"
priority=1
}
The result is that under the settings --> wireless it just says "connecting" but it does not connect at all.
Catlog reports a lot of
Code:
wifi doCommand: ret=-1
I googled it, but I didn't find anything interesting.
Don't know if it works with other kind of connections. I will try as soon as possible and post the results.
Going back to rc 1.5 with a nandroid backup works good.
Here a full catlog (cannot put directly the link, new user)
pastebin.com/Hv1KWWVK
Do you have any kind of suggestion?
Thank you,
Peppe
Don't know if it works with other kind of connections. I will try as soon as possible and post the results.
Click to expand...
Click to collapse
So, the wifi works on a wpa-psk. Again, in the catlog there are lots of
Code:
wifi doCommand: ret=-1
so I guess this is not the problem.
Thanks,
Peppe
So it seems to be solved.
Yesterday, I first tried to copy the wpa_supplicant binaries from the rc 1.5, but nothing changed.
Then, I also copied the tiwlan_drv.ko (i.e. the driver of the wlan) and its firmware from Rc 1.5 and WORKED.
So to me it seems a bug of the wlan driver, though I didn't try to copy only the driver without copying the wpa_supplicant binaries.
I'd like to point out this to developers, but I don't know if they read this board (I cannot post on the dev board). What do you suggest?
Or should I use the github commits system?
Thank you,
Peppe
Could you maybe post a Link to the files from RC1.5 that you mentioned? Thanks
Nvm: I found a mirror: www.multiupload.com/217FS9PYDC
My wifi seems crappy though with RC1.5 :/...it sort of disconnects or loses activity (even though the wifi signal shows it's good)... It's very annoying when i play Modern Combat 3 multiplayer online --'
Sent from my 1Ghz CM7 + CM9 Defy
I found another website about that topic:
www.gnuyork.org/de/eduroam-android-2-3.html
Unfortunately it's in german, but maybe you can have a look at it with Google Tranlsate.
There is a zip archive, that contains different versions of wpa_supplicant. I didn't test that yet, but I think it could be worth trying which one works:
www.gnuyork.org/download.php?file=wpa_supplicant.zip
dd23 said:
There is a zip archive, that contains different versions of wpa_supplicant
Click to expand...
Click to collapse
To me, it does not seem a problem of wpa_supplicant. Or at least, the driver has something to do with peap/mschapv2, since it was working with rc1.5 and not with the stable.
Though we have eduroam in our university, it never worked (with laptop too). I've never investigated really, since I don't use it.
Bye,
Peppe
crakeron said:
My wifi seems crappy though with RC1.5 :/...it sort of disconnects or loses activity (even though the wifi signal shows it's good)... It's very annoying when i play Modern Combat 3 multiplayer online --'
Sent from my 1Ghz CM7 + CM9 Defy
Click to expand...
Click to collapse
I gave my Defy to my gf recently so I had extra motivation to fix those little annoyances. I found out that if you switch WPA settings from AES (or auto) to TKIP it doesn't disconnect like that anymore.
Sent from my HTC Desire Z using xda premium
Hi,
this is just to say that the problem is still in CM 7.2 RC-0. This time I *just* copied the driver and the firmware from CM7 RC 1.5 and now it works.
Can someone test the peap-mschapv2?
If the bug is real, and to me it seems, can someone post this in the dev section / cm7 dev thread? I cannot (low number of posts).
Bye,
Peppe
dd23 said:
I found another website about that topic:
www.gnuyork.org/de/eduroam-android-2-3.html
Unfortunately it's in german, but maybe you can have a look at it with Google Tranlsate.
There is a zip archive, that contains different versions of wpa_supplicant. I didn't test that yet, but I think it could be worth trying which one works:
www.gnuyork.org/download.php?file=wpa_supplicant.zip
Click to expand...
Click to collapse
Hello everyone, I just tried this, and non of them work, the wifi just turns its self off after about 15 seconds with these wpa_supplicant-s. When I put the original back, it works just the way it always has.
My problem is that eduroam and the university wireless which uses almost the same protocols as eduraom just don't work. Its constantly connecting and disconnecting.
The wpa_supplicant.conf has nothing to do with this because i tried copying it form a friends phone which also has android on it (can't remember which phone it was), the bottom line is: it works for him, and not for Defy users.
Could someone please upload the rc 1.5 wpa_supplicant and tiwlan_drv.ko, because the link for rc1.5 is dead.
Also could you mention where to place tiwlan_drv.ko
Hi gmcgmc,
I can confirm the PEAP/MSCHAPv2 issues.
Beingi able to use my universities EDUROAM-network stopped when I upgraded from stock firmware to CM7. With CM9 it doesn't work, too.
I checked the different wpa_supplicants available via the link DD23 posted, with no success. With one supplicant it didn't even try to connect, 'cause it didn't store the entered settings. With some of the other supplicants it began to connect, but got an error during authentification. Maybe next week I'll be able to post a log.
I will give the driver/firmware thing a try.
Regards
kadolf
Me too having a wifi issues with CM7.2 RC2, it was working with my CM7.1 RC1.5 but i installed CM9 after that and it stopped working...Can someone help me fixing this please.
Just to make a resume.
Stock rom and CM 7.1 RC 1.5 work good with mschapv2 (at least for me ) while CM 7.1 stable and CM7.2 RC* don't work.
To my experience wpa_supplicant has nothing to do with this, as copying the driver from RC 1.5 works.
The last time I copied the following files (my guessing is that actually just the first file is needed. But anyway I copied all of them)
tiwlan_drv.ko --> /system/lib/modules/
fw_tiwlan_ap.bin --> /system/etc/wifi
fw_tiwlan_ap_rfmd.bin --> /system/etc/wifi
The right procedure (for me) was:
Turn off wifi
Delete (or rename to keep your passwords) /data/misc/wifi/wpa_supplicant.conf (rename e.g. to wpa_supplicant.conf.bak)
Rename the old files you are going to write
Copy the files (I used adb, you can use whatever you like)
reboot
Now it should work. If you want use the old wpa_supplicant.conf just delete the new one and revert the ".bak" while the wifi is off.
By the way, the last trick works always when the wifi is stuck (i.e it doesn't see any network):
turn off the wifi
rename the wpa_supplicant.conf
turn on wifi and check that it sees networks
turn off wifi
revert wpa_supplicant.conf
turn on wifi --> finished
No need to reboot!
I've two questions:
1. Can someone test if it is needed just the first file? If so, we may (actually I don't know how...) create a flashable zip
2. Can someone post this on dev thread?
Bye,
Peppe
PS: I've uploaded the files.
Hi gmcgmc,
thanks for the files.
Unfortunately I can't test them until next monday.
If I have some results (may they be good or bad ones) I'll post it.
Greetings,
Kadolf
Ok.
I've made a bur report through cm bug tracker
http://code.google.com/p/cyanogenmod/issues/detail?id=5313
So I confirm the bug/issue under CM 7.2 RC3. Copying *just* tiwlan_drv.ko works.
Bye,
Peppe
wpa2 issue
solved
I tried it with just copying tiwlan_drv.ko - behavior like before.
Then I copied the two other files, too - doesn't work for me and it stopped working with open networks.
I'll try to restore the original WPA-Supplicant, because I've overwriten it a half year ago (while trying to solve the problem) and lost my backup.
kadolf said:
I tried it with just copying tiwlan_drv.ko - behavior like before.
Click to expand...
Click to collapse
How did you copied it? I tried with RootExplorer and it didn't work. I had to use adb (after remouning system in rw). Something like that
Code:
./adb push "tiwlan_drv.ko" /system/lib/modules/
And yes, restore the original wpa_supplicant.
Bye,
Peppe
The issue is still present in CM 7.2 Stable.
gmcgmc said:
By the way, the last trick works always when the wifi is stuck (i.e it doesn't see any network):
turn off the wifi
rename the wpa_supplicant.conf
turn on wifi and check that it sees networks
turn off wifi
revert wpa_supplicant.conf
turn on wifi --> finished
No need to reboot!
I've two questions:
1. Can someone test if it is needed just the first file? If so, we may (actually I don't know how...) create a flashable zip
2. Can someone post this on dev thread?
Bye,
Peppe
PS: I've uploaded the files.
Click to expand...
Click to collapse
hi , n yes iv tested this on my htc status : it did find networks in range , but when I reverted the renamed file it stopped again , just FYI .
+ it didn't need no files n no reboot or wtsoever , anyway thanks a million , it did the trick , long live droid

[Q] Problem: ICS-Releases and Bluetooth

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]"

[Q] kernel(s) with wifi N support?

at firts i am running cm7.2_rc_buzz_kang(03-14-2012),with original radio(never had to flash another,just few times sometimes reflashed to make gps work),custom mtd
i would like to ask devs for this question, but i cant, so i try at least here...
some time ago our router at home has been changed and so has wlan...and that started to cause me problems,because i cant set router up for my phone to provide "g" wifi which works flawlesly..(actually,discovering,that everything is caused by "n" wifi provided by router was very funny,because it was the last thing i thought i could be ) however..after some googling and much xda reading i found app called Wifi fixer,which in most cases fixes my problem,but it doesnt work in 100% cases,and its not the "coolest" solution
few days ago i found Sympnotics kernel,and flashed it,one of reasons was its declared "n" wifi fix,which didnt work...i know,its beta,im not complaining,just saying what i found...btw thats the only thing,that is not good FOR ME on that kernel
so i thought to look for another...
i found infinityplay,which didnt work in "my" way,neither did "official" arco68s,neither last hcdr.kernel_v4.2...
the only one i found working is HCDR.Kernel_v4..
my next idea was (i am noob,so sorry... ) to copy bcm4329.ko (which should be wifi module of kernel) from HCDR.Kernel_v4 to SympKernV4.1..that (surprisingly ) didnt work...at least i tried...
so there is my question...(in this moment,youre the only person who i know is developing kernel,most for Sympnotic) would it be possible to have your kernel with hcdr.kernel_v4 wifi module??
if i have known to do this on my own,i wouldnt bother to ask here, but i have no idea how to build my own kernel,even how to take one,change wifi module and again make flashable zip...
sorry for my english,its not my native language
thx you all here
edit:i have the same problem with cm9,bulit does not matter...btw with hcdr.jacobs v4 wifi does not work...

Evervolv KK 4.4 on HTC Desire

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

Categories

Resources