Related
Hi, today im trying for the first time to root my galaxy apollo(galaxy 3)
i downloaded the dutchmod 4.0 with all associated files on its forum thread:
here
but when i try to do it by reading the instructions, it says that i need to load the .tar file, but there is no tar file.. .
can anyone help me?
once again, im very new newbie
Rick
p.s. I post it here because i cant post on the dev thread
try to unpack the .zip file it should be in there
I really cant find,
can u pm me your MSN adres please?
thats easier (im dutch too BTW, but ill talk english on the forum)
Rick
pmmed you my msn
I have 2 problems
1) Cant change theme in 4.0(both ways either in recovery or by using root explorer) . After changing theme if i rebooted , the boot logo and the home screen goes in a loop.But this does not occurs in 3.2 version.
2)When i watch videos for more than 15 minutes the phone automatically switches off..Then i have to remove battery and switch it on again..
Other than this I like the rom very much....Very stable and blasting speed....
Please fix the above 2 problems.
It is very unstable with ADW Launcher!!Keeps freezing and rebooting!!
Hi,
i using DutchMod 4.0 with Hillbeast's CM bins v 0.3.0 without any single problem but one thing which i miss is use my own songs as ringtones. I tried create media/... folder on SDcard or set it via music player but without success. So is there any other way how to get it?
darrcafel said:
Hi,
i using DutchMod 4.0 with Hillbeast's CM bins v 0.3.0 without any single problem but one thing which i miss is use my own songs as ringtones. I tried create media/... folder on SDcard or set it via music player but without success. So is there any other way how to get it?
Click to expand...
Click to collapse
Problem solved!
muruga said:
I have 2 problems
1) Cant change theme in 4.0(both ways either in recovery or by using root explorer) . After changing theme if i rebooted , the boot logo and the home screen goes in a loop.But this does not occurs in 3.2 version.
2)When i watch videos for more than 15 minutes the phone automatically switches off..Then i have to remove battery and switch it on again..
Other than this I like the rom very much....Very stable and blasting speed....
Please fix the above 2 problems.
Click to expand...
Click to collapse
the first one is becouse youre not using a 9 lockscreen theme i will create an update.zip soon wich will delete the miui launcher so you can use 5 lckscreen mod themes
the second problem i will test etc
andreaschrys21 said:
It is very unstable with ADW Launcher!!Keeps freezing and rebooting!!
Click to expand...
Click to collapse
?? i dont have a problem with adwlauncher?
Hello,
I have CM11 installed on my htc one s, but the front camera doesn't work in snapchat; It does work in other apps, so is this a problem related to cyanogenmod not having the htc drivers or is this snapchat's fault? More importantly, is there a fix or a snapchat replacement app of some sort which enables the front camera?
Maybe try a newer release of CM 11
Sent from my HTC One S using xda app-developers app
I'm on the latest nightly and it's still broken
Same issue
My camera is stretched and sometimes freezes but only in snapchat. Any ideas?
nikkarus said:
My camera is stretched and sometimes freezes but only in snapchat. Any ideas?
Click to expand...
Click to collapse
Bro same problem and it lags...I hope they can fix it!!!!!!
http://forum.xda-developers.com/showpost.php?p=50728759&postcount=1116
This is happening since 4.3.
phoenixita said:
http://forum.xda-developers.com/showpost.php?p=50728759&postcount=1116
This is happening since 4.3.
Click to expand...
Click to collapse
is there any fix available?
speedfreak007 said:
is there any fix available?
Click to expand...
Click to collapse
Unfortunately not yet.
phoenixita said:
Unfortunately not yet.
Click to expand...
Click to collapse
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Why don't they include this file in official cm11? is it HTC owned (not opensource) or something?
darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Sorry @darrendm
what is a Gummy Rom ? (i'm french sorry)
And what about CM team ? Why don't solve this problem ?
darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Not sure if this is still an issue for the One S, but it still is for the S4. I just did this and it worked, but I wanted to mention I had to use the camera file from a 4.1 ROM to do so. Hopefully that helps someone else.
spyder91 said:
Not sure if this is still an issue for the One S, but it still is for the S4. I just did this and it worked, but I wanted to mention I had to use the camera file from a 4.1 ROM to do so. Hopefully that helps someone else.
Click to expand...
Click to collapse
I am having this issue as well. Is there a way you could zip up the file as I don't know how to extract the file from a different ROM. Thanks
Edit: I think it may just be a Snapchat issue, as my front camera works for the regular camera app
th3pr1nc30f3gypt said:
I am having this issue as well. Is there a way you could zip up the file as I don't know how to extract the file from a different ROM. Thanks
Edit: I think it may just be a Snapchat issue, as my front camera works for the regular camera app
Click to expand...
Click to collapse
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
I tried this, restarted my phone, and neither Snapchat or the regular camera app would work. I put the original backup file back in and my regular camera app works again, just not Snapchat front camera
darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
SERIOUSLY. WHAT. THANK YOU SO MUCH
I have been looking for a fix for sooooo long. And thank you for providing the file!
Worked like a charm
Galaxy S4 cm11 4.4.4
Snapchat 5.0.27.1
:good::good::good:
darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
Hey man. Any chance you could re-upload that file or provide intel on how/where to extract it myself?
Ojive said:
Hey man. Any chance you could re-upload that file or provide intel on how/where to extract it myself?
Click to expand...
Click to collapse
https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
This file works for me on my S4. I paste it into the /system/lib/hw directory after flashing the latest nightly. (you must DELETE the existing file manually as pasting this file into the directory DOES NOT delete the other file of the same name but in capital lettering)
Also, this does not a complete fix for the Snapchat camera issues. I am now able to record video with the front camera however a lot of the time it will still cause the app to freeze or camera to lock up - requiring a phone reboot. HOWEVER this is a lot better than not being able to record ANY videos at all (as it is normally with the CM11 ROMS)
EDIT: the file is extracted from an old GUMMY ROM nightly in the system/lib/hw directory. If this file doesn't work for you, you could try extract the file from other non CM based ROMS and see if if your problem is fixed.
darrendm said:
https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
This file works for me on my S4. I paste it into the /system/lib/hw directory after flashing the latest nightly. (you must DELETE the existing file manually as pasting this file into the directory DOES NOT delete the other file of the same name but in capital lettering)
Also, this does not a complete fix for the Snapchat camera issues. I am now able to record video with the front camera however a lot of the time it will still cause the app to freeze or camera to lock up - requiring a phone reboot. HOWEVER this is a lot better than not being able to record ANY videos at all (as it is normally with the CM11 ROMS)
EDIT: the file is extracted from an old GUMMY ROM nightly in the system/lib/hw directory. If this file doesn't work for you, you could try extract the file from other non CM based ROMS and see if if your problem is fixed.
Click to expand...
Click to collapse
Thanks <3
darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Thanks man it really works for me after some tweaks :highfive:
I don't think you need the file "camera.msm8960.so" from another ROM :angel:.
Here is how I did it:
1) In the path system/lib/hw, there is two files "camera.MSM8960.so" (13KB) and "camera.vendor.msm8960.so" (210KB)
2) delete the file "camera.MSM8960.so", but copy its exact name with the capitals. This is important cuz I believe it is case sensitive.
3) rename "camera.vendor.msm8960.so" to "camera.MSM8960.so" which is the exact name of the deleted file
4) make sure the permissions are set as follows: "rw- r-- r--" which is short for read/write OWNER, read GROUP, read OTHER
5) open snapchat and go for video setting change qualiy to low. after that, record a video with front camera and send it to urself.
6) finally put the video quality back to standard and ENJOYYYY it should work for u.
:victory:
Let's keep all cm12 preview discussion in here please.
Cm12 preview builds.
http://downloads.codefi.re/jrior001/cm/evita
Warning!! These are still in early development and any build could be highly unusable!! If you dare continue, have a backup ready and Good luck.
Thanks for the build jrior!
I've been running 11/27 for a day now, very smooth and fast - too soon to say about battery life.
Just a heads up for anyone flashing - 11/28 and 11/29 the SD card doesn't work. On 11/27, you can't answer incoming calls and can't music over Bluetooth.
EDIT: No SD on 11/30 either.
Glad to see android lollipop on beautiful evita, thanks jrior001 ?
Would you like us to report what's working and what's not ?
Working Dialer and SD
This information is for those who are having dialer force close issues with 27/11.
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Also, the latest Google Camera works great on this ROM, and fixes the 'squashed' preview when taking 16:9 photos.
http://www.apkmirror.com/apk/google-inc/camera/camera-2-4-024-1564481-30-apk/
00Scott00 said:
Hi all,
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Click to expand...
Click to collapse
So you're in 27/11 and everything is working?
I just flashed 1st 29/11 and later 27/11 and I just get everything working.
Working.
Mexickano said:
So you're in 27/11 and everything is working?
I just flashed 1st 29/11 and later 27/11 and I just get everything working.
Click to expand...
Click to collapse
I also flashed 27/11 and all seems good so far. Been up for almost 5 hours. No glitch to report so far.:good:
Hey dudes, any feedback on latest build 12/01 please?
azirgi said:
Hey dudes, any feedback on latest build 12/01 please?
Click to expand...
Click to collapse
Remember that is only an Alpha release, dont expect that everyone here try the new releases for you, you always can do a backup of your actual ROM and install this one if something goes wrong you always can comeback.
I will test the 12/01 version I used the 11/27 version and only notice one bug when receiving whatsapp on my lock screen went crazy shaking and disappearing background if I try to view the notification if I just went home and open the application this problem didn't occur.
12/01 Sdcard still broke, testing a pending fix from cm crew shortly
tested 12/01 version external storage is not mounted
00Scott00 said:
Hi all,
I was playing around this morning, and noticed on 20141130 the dialer was working fine, but the SD was not accessible.
I rolled back to 20141127 and installed the dialer from 20141130, and it worked! So far everything is working great.
On 20141127 in settings->apps->all->Dialer you will see version 5.0-20f4e4c951. 20141130 has version 5.0-e46feea897. This one works.
You need to backup and replace 2 files to do this:
Dialer.apk in /system/priv-app/Dialer.
libvariablespeed.so in /system/lib
Replace the files and fix permissions to -rw-r--r-- (same as replaced file). Reboot and try it.
Files are included in the zip, don't try to flash it.
Thanks jrior for bringing this awesome ROM to the Evita. If I am out of line here, just say so.
Scott
Click to expand...
Click to collapse
My dialer appears to be working on 11/27, what issues did you come across that you needed the 11/30 dialer?
buradd said:
My dialer appears to be working on 11/27, what issues did you come across that you needed the 11/30 dialer?
Click to expand...
Click to collapse
I had FC every time i recieved a call. Did you make and receive calls?
00Scott00 said:
I had FC every time i recieved a call. Did you make and receive calls?
Click to expand...
Click to collapse
Ive been on the 11/27 build last couple of days and have been able to receive and make calls without any issues.
OK, then ignore my post
frozenreality44 said:
tested 12/01 version external storage is not mounted
Click to expand...
Click to collapse
This:
jrior001 said:
12/01 Sdcard still broke, testing a pending fix from cm crew shortly
Click to expand...
Click to collapse
Hboot ver problem :|
hi dear developers :
i have a htc ONE XL (UTL) With CIDNUM: HTC_J15 and ModelID : PJ8350000
for CM 12 I need to upgrade my hboot to at least 2.14 version
for Evita UTL i cant find Newer HBOOT With This CID And Modelid
Please Help What can i do quickly ???
Is there any changelogs for these builds?
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21
Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!
Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.
Reserved2
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!
jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.
Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!
shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.
silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Would you be open to posting your sources for these builds?
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol
jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk
silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM
LineageOS 13 for Life One X2 Mini
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org
Screenshots:
Changelog
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
reserved 4
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)
srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"
mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.
debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.
Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing