Wrong Bluetooth mac-address (00:00:00:00:5a:ad) - Lenovo P2 Questions & Answers

Hi,
I have a bluetooth mac-address problem.
I use the custom rom dotOS1.2 with my Lenovo p2a42
(I don’t wont to change my rom.)
I have a bluetooth mac-address issues and the thread of the dotOS-rom is closed.
My bluetooth mac-adress is: cc:61:e5:49:a3:81 and this mac-address wont be read right. Instead of the right address it takes 00:00:00:00:5a:ad
I found the following link: r e v i e w . l i n e a g e o s . o r g / # / c / 1 8 3 0 2 1 /
But I dont know how to fix my dotOS rom.
It works with the aokp rom correct, but I need fingeprint gestures and I wont change my rom.
I tried to take some files from the aokp rom like: hci_qcomm_init but it does not change anything.
I tried to install xposed framework to change my mac-address, but … it does not work either.
My wife uses the same dotOS ROM with another device,but the mac adress is the same, so we have a problem to connect our devices to the car via bluetooth.
Thx

Speedy10061975 said:
Hi,
I have a bluetooth mac-address problem.
I use the custom rom dotOS1.2 with my Lenovo p2a42
(I don’t wont to change my rom.)
I have a bluetooth mac-address issues and the thread of the dotOS-rom is closed.
My bluetooth mac-adress is: cc:61:e5:49:a3:81 and this mac-address wont be read right. Instead of the right address it takes 00:00:00:00:5a:ad
I found the following link: r e v i e w . l i n e a g e o s . o r g / # / c / 1 8 3 0 2 1 /
But I dont know how to fix my dotOS rom.
It works with the aokp rom correct, but I need fingeprint gestures and I wont change my rom.
I tried to take some files from the aokp rom like: hci_qcomm_init but it does not change anything.
I tried to install xposed framework to change my mac-address, but … it does not work either.
My wife uses the same dotOS ROM with another device,but the mac adress is the same, so we have a problem to connect our devices to the car via bluetooth.
Thx
Click to expand...
Click to collapse
Are you flashing magma kernel with it,
if yes then that's the problem.
i had the same problem

No, the kernel is: 3.18.31 lineageos-ge72c5036 [email protected] #1
I have found a Lineage OS Update dated on february. Now it works.
There was a bluetooth mac issues solved.

Related

Working 100% - [ Updated Patch ] Enable ad-Hoc Networking htc Incredible 2 VIVOW

Working 100% - [ Updated Patch ] Enable ad-Hoc Networking htc Incredible 2 VIVOW
this updated Patch will enable ad-hoc 100% steady connection for both ( WEP and open Networks ) , Also Hotspot WPA2-PSK is still able to connect
what is new in this Patch is it does not affect the ability to connect to hot spot WPA2-PSK networks ( i.e you can connect to both types on the fly ) , i tried a lot of Patches , ( usually in Sense 3.5 Roms when you apply an ad-hoc Patch you loose the ability to connect to Hotspot WPA2-PSK )
Android does not show this Ad-hoc networks ( it Finds them in the search , but filters them out of the shown results ) , this patch prevent that filtering and shows those ad-hoc networks
i am running Ginger Bread 2.3.4 with sense 3.0 , tested also with Virtuous Affinity v1.48 sense 3.5
DISCLAIMER
I am not responsible if flashing this Mod results in bricking your phone
for Rooted devices
​ Important tip
i am using GSM network only
if Hotspot WPA2-PSK is working fine and later on it is disconnected ( usual with a lot of sense Roms ) , just turn WiFi off and on , it will connect on the fly with this Patch .
if Hotspot WPA2-PSK ( during first use ) is connected but not transferring data ( this happened with Affinity 1.48 Sense 3.5 , BUT my other sense 3 Rom didn't had that problem ) , then use APN manager and choose your APN and activate it , this immediately solved the Problem for me
( NOT related to the Patch ) , in some cases data transfer is blocked due to Firewalls , Please note that for some firewalls it not enough to disable it , BUT you need also to check the firewall Rules
There are two types of WiFi Networks :
Infrastructure ( Hotspot ) WPA,WPA2-PSK which is the most secured connection , usually routers broadcast this
Ad-hoc it is either WEP or open network which is less security , usually issued through a laptop connected to a DSL line to broadcast a temporary WiFi connection
Almost all Sense Roms wifi use ( Hotspot ) WiFi , for Sense 3.5 the Base of the custom Rom ( ie Sensation , Runnymede , ...etc ) affects WiFi behavior and connectivity
Updated Patch
it is always good to do a Backup for your data , Or Just Backup the original file " wpa_supplicant " located in System\bin .
to restore the original file " wpa_supplicant " any time :
just open the Patch in a winrar window and navigate to System\bin and over-right the one in the Patch with the original ( you can get the original from your Rom zip ) . apply the modified Patch from recovery and you are back to the original
if you use Root Explorer to restore the original file ,make sure to set the correct permissions and ownership values
http://www.multiupload.com/Y6WTVE0WTQ , thanks and Credit to daveba who Posted the file included in that Patch
[FONT=&quot]https://rapidshare.com/files/2831506439/wpa_ad-hoc_Patch_VIVOW.zip[/FONT]
[FONT=&quot]http://www.mediafire.com/download.php?wvnc6v966x4jsvq
[/FONT]
hope some one will benefit from it
Please Press thanks if you find that Post Useful
Broke WiFi
I rebooted into recovery, wiped dalvik, and installed the file.
After I rebooted I couldn't connect to ANY WiFi source.
I think I'm going to have to restore a backup to fix it.
tested again Working
Spookymyo said:
I rebooted into recovery, wiped dalvik, and installed the file.
After I rebooted I couldn't connect to ANY WiFi source.
I think I'm going to have to restore a backup to fix it.
Click to expand...
Click to collapse
tested again Working , After i read your Post i tested the Patch with Virtuous Affinity v1.48 sense 3.5 to double check
Ad-hoc both ( open and WEP ) working fine , Hot Spot connected WiFi but no data transfer , my guess that this is what you mean by Broken WiFi ( Solved for me )
if Hotspot WPA2-PSK is connected but not transferring data ( happened with Affinity 1.48 and a lot of sense 3.5 Roms even before using the Patch ) , then use APN manager and choose your APN and activate it , this immediately solved the Problem for me , i am only using GSM network
Also in some cases data transfer is blocked due to Firewalls , Please note that for some firewalls it not enough to disable it , you also have to check the firewall Rules
Please note for some people enabling ad-hoc is important for some reason ,
otay
So far so good for me. Very nice.
wowens0822 said:
So far so good for me. Very nice.
Click to expand...
Click to collapse
thanks , now almost 200downloads without complaints except for the above one which is solved , ( only two members Pressed my thanks Button !!!!!!! )
i will now stop reviewing the number of downloads , cause now it is proved working without complaints
I read that both HTC Incredible 2 and HTC Incredible S have the same hardware. Would the above patch work on HTC Incredible S from Bell Mobility Network? Has anyone tried to confirm it?
Thanks.
albundy9999 said:
I read that both HTC Incredible 2 and HTC Incredible S have the same hardware. Would the above patch work on HTC Incredible S from Bell Mobility Network? Has anyone tried to confirm it?
Thanks.
Click to expand...
Click to collapse
i guess the Patch should work with Incredible S
Desire HD , Incredible S , Incredible 2 are Almost identical
i managed before ( after some trials ) to install an Incredible S Rom on my Incredible 2 and every thing worked perfectly ( Including WiFi ) .
i also installed before an older ad-hoc Patch for Desire HD on my Incredible 2 and it also worked fine for me
trkaaa said:
Working 100% - [ Updated Patch ] Enable ad-Hoc Networking htc Incredible 2 VIVOW
this updated Patch will enable ad-hoc 100% steady connection for both ( WEP and open Networks ) , Also Hotspot WPA2-PSK is still able to connect
what is new in this Patch is it does not affect the ability to connect to hot spot WPA2-PSK networks ( i.e you can connect to both types on the fly ) , i tried a lot of Patches , ( usually in Sense 3.5 Roms when you apply an ad-hoc Patch you loose the ability to connect to Hotspot WPA2-PSK )
Android does not show this Ad-hoc networks ( it Finds them in the search , but filters them out of the shown results ) , this patch prevent that filtering and shows those ad-hoc networks
i am running Ginger Bread 2.3.4 with sense 3.0 , tested also with Virtuous Affinity v1.48 sense 3.5
DISCLAIMER
I am not responsible if flashing this Mod results in bricking your phone
for Rooted devices
​ Important tip
i am using GSM network only
if Hotspot WPA2-PSK is working fine and later on it is disconnected ( usual with a lot of sense Roms ) , just turn WiFi off and on , it will connect on the fly with this Patch .
if Hotspot WPA2-PSK ( during first use ) is connected but not transferring data ( this happened with Affinity 1.48 Sense 3.5 , BUT my other sense 3 Rom didn't had that problem ) , then use APN manager and choose your APN and activate it , this immediately solved the Problem for me
( NOT related to the Patch ) , in some cases data transfer is blocked due to Firewalls , Please note that for some firewalls it not enough to disable it , BUT you need also to check the firewall Rules
There are two types of WiFi Networks :
Infrastructure ( Hotspot ) WPA,WPA2-PSK which is the most secured connection , usually routers broadcast this
Ad-hoc it is either WEP or open network which is less security , usually issued through a laptop connected to a DSL line to broadcast a temporary WiFi connection
Almost all Sense Roms wifi use ( Hotspot ) WiFi , for Sense 3.5 the Base of the custom Rom ( ie Sensation , Runnymede , ...etc ) affects WiFi behavior and connectivity
Updated Patch
it is always good to do a Backup for your data , Or Just Backup the original file " wpa_supplicant " located in System\bin .
to restore the original file " wpa_supplicant " any time :
just open the Patch in a winrar window and navigate to System\bin and over-right the one in the Patch with the original ( you can get the original from your Rom zip ) . apply the modified Patch from recovery and you are back to the original
if you use Root Explorer to restore the original file ,make sure to set the correct permissions and ownership values
http://www.multiupload.com/Y6WTVE0WTQ , thanks and Credit to daveba who Posted the file included in that Patch
[FONT=&quot]https://rapidshare.com/files/2831506439/wpa_ad-hoc_Patch_VIVOW.zip[/FONT]
[FONT=&quot]http://www.mediafire.com/download.php?wvnc6v966x4jsvq
[/FONT]
hope some one will benefit from it
Please Press thanks if you find that Post Useful
Click to expand...
Click to collapse
does this work on ICS?

[Help & Temporarily fix]can't use wifi / usb / bluetooth tethering when data is on

[Help & Temporarily fix]can't use wifi / usb / bluetooth tethering when data is on
hi
I have this problem for a long time but i found some new things about this problem that want to share it with everyone , so i decide to create a new thread , so you can share your ideas to fix it also i found a way to use it Temporarily
my device info:
lt18i , android 4.0.4 , build number 4.1.B.1.13
rooted , bootloader unlocked
installed UHDv4 ROM and UHDv4.8 MOD with LuPuSv16
who have this problem ?????
my problem is :
i want to use (wifi/usb/bluetooth) tethering , everything is good just after removing wifi modules from lupus menu ( just for a minute )
after a while i can't use wifi tethering when data is enabled
*****The only thing that I did not notice, it was option 3 , you will read it in the following*****
so i decide to use another kernel : so i should to flash a wifi module from CWM but after boot up i don't have any wifi but (usb/bluetooth) tethering works good
i also tried to remove lupus wifi modules before flashing new kernel
So I went back to LuPuS
***** i found a new feature i should do the following to make wifi hotspot works when data is enabled ******
i have 3 options:
1 = first enable data then enable wifi hotspot ***in other words*** enable wifi hotspot when data is enabled = works
2 = first enable wifi hotspot then enable data ***in other words*** enable data when wifi hotspot is enabled = this will make the problem
i should just do option 1 to make it work , if i do option 2 , the problem starts and i can't make it work with option 1
after that the problem starts :d i can't use it again to solv the problem , for example
but i found a new option for make it work
3 = enable data then reboot ***in other words*** reboot when data is enabled , without removing wifi modules
if i do option 3 , i can use option 1 again without problem
uuuhhhhhh so strange problem
i think my phone have problem with set the internet ip address for tethering
here is the logcat when i did option 2 and wifi hotspot don't work with option 1 :
View attachment 2013-08-18-09-39-35.txt
here is the logcats when i did option 3 and wifi hotspot work with option 1 :
View attachment 2013-08-18-09-42-50.txt
here is the logcat when i did option 2 and wifi hotspot don't work with option 1 :
View attachment 2013-08-18-09-44-04.txt
Never heard about this problem !
I have this problem at Legacy 4.2.2 and 4.3.
Sent from my Xperia Arc S using XDA Premium 4 mobile app
Prider555 said:
I have this problem at Legacy 4.2.2 and 4.3.
Sent from my Xperia Arc S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what about option 1 & 3 , can they help you ? do you think it is from "set the ip address ?
EAGLEBOOY said:
what about option 1 & 3 , can they help you ? do you think it is from "set the ip address ?
Click to expand...
Click to collapse
When I use option 1 & 3 then is all working fine. I dont really now what this mean "set the ip address". Im not a developer!
hi , please someone help
devs please say something , just what you know and ways that can help
please help , thanks
finaly the problem is fixed now
hi
finaly the problem is fixed now
you can't solv it by changing a rom or kernel , you should flash a FTF with flashtool to solv it
here is what i did :
i flashed LT18i_4.1.B.1.13_Vodafone DE.ftf with flashtool and it works now
after that i flashed LuPuS kernel and UHD ROM and UHD MOD
it is still works very good , now i can turn on wifi hotspot when data is enabled whithout any problem , everything is good now
i suggest you flash LT18i_4.1.B.1.13_Vodafone DE.ftf For increasing system and data memory for Arc user and latest BB
Hi I think I find how to fix it
You can flash a ftf via flashtool to fix it but this way will wipe all your data
we can flash a ftf but without flashing system, kernel, baseband and without wipe data
You can choose which one you want to flash
So select what you don't want and leave unselected which you want in flashtool
Sent from my LT18i using Tapatalk 2
hi EAGLEBOOY,
I have moved your thread from General section to Q&A, Help & Troubleshooting section. This maybe useful to others so if it is in Q&A it will be easier to find. Please use the correct sub-forums when posting.
--wedgess
Forum Moderator

Any solution for bluetooth connection problems?

I have a Joying car radio RK3188 1024x600 and it works fine till I got laast week on my Oneplus One smartphone Marshmallow update (Cyanogen OS 13).
Now I can't connect my device anymore via bluetooth.
I can see that the two devices are paired but the letters on the radio screen are still white an phonebook is not available. On my smartphone I see under bluetooth settings that there is a connection but without phone funktion.
I contact manufacturer and he offered to go into recovery and wipe all data/ factory and cache reset and then install firmware. I did this exactly two times with firmware JY_rk3188_h(20160222) RK3188 1024*600 from february and the latest firmware JY_rk3188_h(20160328) RK3188 1024*600. But I still can't connect phone with bluetooth, has someone an idea and maybe the same problems?
MueKo said:
it works fine till I got laast week on my Oneplus One smartphone Marshmallow update (Cyanogen OS 13).
Now I can't connect my device anymore via bluetooth.
Click to expand...
Click to collapse
Well known problem with CM13 and HU bluetooth...
Apparently no other solution than going back to CM12, at least for Oneplus smartphones.
themissionimpossible said:
Well known problem with CM13 and HU bluetooth...
Apparently no other solution than going back to CM12, at least for Oneplus smartphones.
Click to expand...
Click to collapse
Thanks for your answer. Is it known where the problem comes from, CM13 or HU?
MueKo said:
Is it known where the problem comes from, CM13 or HU?
Click to expand...
Click to collapse
My speculation is that there might be some incompatibility between the 2 Bluetooth stacks profile implementation... as the problem is only with CM13, this incompatibility should be mostly ascribed to CM13.
Same issue here
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
But my phone is not rooted
This is interesting, maybe someone has a rooted OnePlus One and can test this?
Tested and Working well
Tested and making no difference. Still no phone BT connection to my car hands-free head unit.
PAPPAFRITAS said:
Tested and Working well
Click to expand...
Click to collapse
Can you specify which OS do you have used.
Same issue here, now on CM13-20160415-NIGHTLY-bacon... I hope in the near future it will come fix... (MCU KGL5 2.55)...
ranmic said:
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
But my phone is not rooted
Click to expand...
Click to collapse
Worked like a charm for me!
OnePlus One on Android 6.0.1 - first time Bluetooth is actually working with that unit.
Fixed in nightly 2904 and working perfectly since.
Sent from my Bacon via XDA free
Today I checked this solution. I rooted my OnePlus One with CM13.0 and edit init.qcom.bt.sh file like this:
ranmic said:
Does anyone know if this will be resolved in an update to CM13?
I found a thread saying this:
open the /system/etc/init.qcom.bt.sh and edit the following line:
Setprop ro.bluetooth.hfp.ver 1.7
... To:
Setprop ro.bluetooth.hfp.ver 1.5
Click to expand...
Click to collapse
And I can confirm that it works.

Help for Bluetooth

Hello,
I have a Zenfone 2 Z00A (ZE551ML - 4Gb), i have a weird problem, i have no bluetooth on any Marshmallow Rom.
It makes always the same thing : "Connected" for 1sec then disconnected
I tried several ROMS :
-Cyanogen : UNOFFICIAL / OFFICIAL : March and April Nightly
-[ROM][BUILD-6][6.0.1r16][INTEL-OPTIMIZED] AOSP-CAF for Zenfone2 [18/04/16] -> With or without this kernel : [KERNEL]FlareM[LINARO]
-I am actually on [ROM][OFFICIAL][6.0.1r22]Resurrection Remix-MM 5.6.6 and i have no bluetooth again.
I change the recovery too : TWRP 3.0 > 2.7.8.2
The roms works perfectly (a little bit buggy but nothing strange on "Nightly")
In my Logcat, i made several test :
-PAIRING a Samsung S3 with my zenfone 2
-PAIRING my zenfone 2 with a Samsung S3
I don't want to go on Asus Rom..
I put a logcat but i don't understant how to read it, any help will be greetly appreciated :
Thank You
Alexei
EDIT : Can't attach document or add external link...
HD2_Lover said:
Hello,
I have a Zenfone 2 Z00A (ZE551ML - 4Gb), i have a weird problem, i have no bluetooth on any Marshmallow Rom.
It makes always the same thing : "Connected" for 1sec then disconnected
I tried several ROMS :
-Cyanogen : UNOFFICIAL / OFFICIAL : March and April Nightly
-[ROM][BUILD-6][6.0.1r16][INTEL-OPTIMIZED] AOSP-CAF for Zenfone2 [18/04/16] -> With or without this kernel : [KERNEL]FlareM[LINARO]
-I am actually on [ROM][OFFICIAL][6.0.1r22]Resurrection Remix-MM 5.6.6 and i have no bluetooth again.
I change the recovery too : TWRP 3.0 > 2.7.8.2
The roms works perfectly (a little bit buggy but nothing strange on "Nightly")
In my Logcat, i made several test :
-PAIRING a Samsung S3 with my zenfone 2
-PAIRING my zenfone 2 with a Samsung S3
I don't want to go on Asus Rom..
I put a logcat but i don't understant how to read it, any help will be greetly appreciated :
Thank You
Alexei
EDIT : Can't attach document or add external link...
Click to expand...
Click to collapse
Have you tried connecting to another Bluetooth device such as a Smart Watch or a Bluetooth audio system.
If the above steps work, try pairing with a different phone, maybe your Galaxy S3 could be the problem.
Sent from my ASUS_Z00A using Tapatalk
GroveStreetHomie said:
Have you tried connecting to another Bluetooth device such as a Smart Watch or a Bluetooth audio system.
If the above steps work, try pairing with a different phone, maybe your Galaxy S3 could be the problem.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Hello,
Yes i forgot about that...
I tried : my car / Another Zenfone 2 Stock .... Always the same problem : it connects 1s then disconnect.
You have the external URL in the reason for editing if you want
Thanks for the answer,
HD2_Lover said:
Hello,
Yes i forgot about that...
I tried : my car / Another Zenfone 2 Stock .... Always the same problem : it connects 1s then disconnect.
You have the external URL in the reason for editing if you want
Thanks for the answer,
Click to expand...
Click to collapse
I don't know to read logcats sorry.
But assuming you clean flashed all those ROMs, and the Bluetooth bug still persists, try flashing stock ROM then try Bluetooth, then clean flash back (not restore from TWRP backup) to a custom ROM of your choice and try it again.
If that still didn't work, I think you would need to do a factory reset (delete /data as well)
Sent from my ASUS_Z00A using Tapatalk

LINEAGE 13 MM LeECO 1 PRO CN and US-test only (yet)

I decided to open a new thread for Lineage 13 MarshMallow for LeECO 1 PRO.
The Lineage 14.1 Nougat remain in its own thread
Mainly it will be for CN version that i own, but I will try to find some solution for US model also, maybe will get some succes.
Everything work except IR blaster.
Download CN Version:
Ver. march10:
http://www.mediafire.com/file/fzpq2dc53hyxkz8/CM13_X800_CN_ABM30_10-mar17-02.zip
Ver. 2017 jun 04
https://mega.nz/#!twVXBQjZ!6m9CdTMgWq91emxqCr0L8YYujl_mEQ0BnF7rjpGr-Ms
[URL=http://www.mediafire.com/view/fndjsikn4een632/X800-LinOS_13_-_Android_6.0.1._2017jun4.jpg]
[/URL]
DOWNLOAD US Version
Ver. march11: give a try:
http://www.mediafire.com/file/995cs583q09x4m6/CM13_X800_US_ABM30_11-mar17-01.zip
ver. 2017jun12
http://www.mediafire.com/file/5361ukny8i41s6u/X800_US_linOS_13_2017jun13_ABM30-x1.zip
Do you have any issues my friend?
How do you compare to CM14?
Camera works OK?
I can install on US version, or wait ?
freiserk said:
I can install on US version, or wait ?
Click to expand...
Click to collapse
You can install, but I think the sound problem will be there. The kernel is the Crisbal one but the Ramdisk in boot.img has some changes so, let see....
THX
There is problem with Samsung camera - the same as in 14.1. But I've found, that standard camera app in 13 works OK. The problem is with Open Camera and Google Camera (this three apps I've tested so far).
Maybe there's no camera v2 support? It should just take a prop file edit, probably build.prop IIRC.
did anyone tests the CN version for daily use?
Kaizen_pl said:
THX
There is problem with Samsung camera - the same as in 14.1. But I've found, that standard camera app in 13 works OK. The problem is with Open Camera and Google Camera (this three apps I've tested so far).
Click to expand...
Click to collapse
Standard camera in Lineage OS 13 MM in camera2, it seems that samsung camera need camera2 api to be activated.
Open camera has a switch in settings with this you can activate cam v2 api. Try and tell me if something goes better.
You can try also this:
How to enable Camera2 API?
1) install buildpropeditor
2) Open build.prop, make string 'persist.camera.HAL3.enabled=1' (without cotes), save, reboot.
has this helped somehow?
P.S. BTW how is the sound on this latest MM 13 ROM?
@ABM30 , did you receive message from me? It could help with camera (i am not sure if in this ROM too, but..who knows)
ABM30 said:
Standard camera in Lineage OS 13 MM in camera2, it seems that samsung camera need camera2 api to be activated.
Click to expand...
Click to collapse
No change. Neither switching in Open Camera camera2 helped, nor editing build.prop and restarting. Nothing changed.
KUKU159 said:
@ABM30 , did you receive message from me? It could help with camera (i am not sure if in this ROM too, but..who knows)
Click to expand...
Click to collapse
Yes, I received your message, thank you.
Any help is welcomed!
Good job!
So no sound in the phone speaker too?
Dual tap to wake don't work?
I activated both options and only dual tap to sleep in notification bar worked.
Cagixxx said:
Dual tap to wake don't work?
I activated both options and only dual tap to sleep in notification bar worked.
Click to expand...
Click to collapse
Unfortunate DTW not working, yet
ABM30 said:
I decided to open a new thread for Lineage 13 MarshMallow for LeECO 1 PRO.
The Lineage 14.1 Nougat remain in its own thread
Mainly it will be for CN version that i own, but I will try to find some solution for US model also, maybe will get some succes.
Everything work except IR blaster.
Download CN Version:
Ver. march10:
http://www.mediafire.com/file/fzpq2dc53hyxkz8/CM13_X800_CN_ABM30_10-mar17-02.zip
DOWNLOAD US Version
Ver. march11: give a try: http://www.mediafire.com/file/995cs583q09x4m6/CM13_X800_US_ABM30_11-mar17-01.zip
Click to expand...
Click to collapse
Is there any chance to get the sound working on the US version?
galulex said:
Is there any chance to get the sound working on the US version?
Click to expand...
Click to collapse
We need a new kernel, the Crisbal one used in previous attempt for CM13 US (AND ANOTHER ROMs to) have the speaker problem.
question, have you tried the version from march 11, it is booting up? what is working and what not (including GPS, SCREENCAST, WIFI TETHERING)?
A new try for US VERSION: http://www.mediafire.com/file/lavevxn25ief5d2/CM13_X800_US_ABM30_21-mar17-01_-_noROOT_-.zip
Install in TWRP after wiping cache, Dalvik/ART, DATA and system. (AT YOU OWN RISK AS USUAL!)
After flashing wipe cache and DALVIK/ART
Let see if it is booting up!
Tested on my X800 CN since you created this thread. This ROM can be used in production ! Well done ABM30 !
- WiFi : Ok
- 4G : Ok
- GPS : With LineageOS 14 I thought I had a hardware problem. With this version, it's perfect (5 to 10 sec to get a clear signal in my car)
- Phone Call : Ok
- Tethering : Ok ! That's a great news !
- Sound : Ok. Tested with internal, external (perhaps too loud), bluetooth and wire headphone
- Bluetooth : Ok
- Battery consumption : Ok
- Camera : Ok
- Automatic on/off while covering screen : Doesn't work
- Other sensors : As usual
ABM30 said:
A new try for US VERSION: http://www.mediafire.com/file/lavevxn25ief5d2/CM13_X800_US_ABM30_21-mar17-01_-_noROOT_-.zip
Install in TWRP after wiping cache, Dalvik/ART, DATA and system. (AT YOU OWN RISK AS USUAL!)
After flashing wipe cache and DALVIK/ART
Let see if it is booting up!
Click to expand...
Click to collapse
Hi.
The system flashed well but remained in the circular logo and did not start.
Thank you for trying to make it work.
EDIT
I'm looking at recovery and it does not install system.
The installation process does it in a few seconds
I have installed this ROM at my Le One X800 US but I have no information abou the battery. It is 0%.

Categories

Resources