Related
Hey guys,
First post here,
i was searching around for my problem, and i haven't found an accurate answer so thought to share my problem and hopefully find an answer.
i am from Canada, Edmonton, and i am with Rogers.
First problem,
i run CM 10.1 and Most the NIGHTLY updates they were butter smooth and works great, until Update number CM-10.120130317 till the current update. All the updates i download, my phone freezes LOT! example of how it freezes , i try to unlock my phone, it freezes . I try to write something it freezes . and sometimes when its on sleep it freezes i can't turn the screen on again! so i always downgrade to CM-10.120130316 to have that stable ROM.
I did the wipe date /factory reset from the ROM manager, and wipe cache and dalvik. and yet the problem is not solve.
So my question is, dose anyone facing the same problem? or it's just me?
Second Problem
am having this beyond annoying notification, where it says my message has not been sent! but my message get's sent and all acts normal. But i always get notification and its never gone. I have screen shoot the problem. Is there a way i can fix this? i've have attached in the thread.
if you guys have any questions or want me to provide some information please do ask.
Looking forward to hear the feedback.
Cheers,
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
xBeerdroiDx said:
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
Domoo said:
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thank you guys for the time to post in my thread. Alright, i will stick with update that runs well in my cellphone..
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Thanks in advance!
xBeerdroiDx said:
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
MH_91 said:
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Click to expand...
Click to collapse
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
xBeerdroiDx said:
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
Click to expand...
Click to collapse
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
MH_91 said:
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
Click to expand...
Click to collapse
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
xBeerdroiDx said:
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
Click to expand...
Click to collapse
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
MH_91 said:
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
Click to expand...
Click to collapse
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
xBeerdroiDx said:
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
Click to expand...
Click to collapse
Will do mate! Thank you so much for your kind help! i really appreciated it. i will for sure share the results with you very soon.
Have a good one.
Q&A for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
bmx26 said:
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
Click to expand...
Click to collapse
Inside of drive, Try long pressing on it and clicking "download copy" it should download a copy to the downloads folder on your internal sdcard
using this rom cm12.1 for s3 sprint and its working great so far, only noticed two things........ camera not working and Battery but im going to see after a day or two if the battery last the same as the previous rom i was on cm12 (camera was working sort of with the camera zoom fx and viva video work around but i used high speed camera plus instead of camera zoom fx with viva video and it was good)............. so cant wait for a working camera or some kind of work around for this rom cm12.1 s3 sprint.......
Silly mod question.
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
brad2512 said:
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
Click to expand...
Click to collapse
The google drive link has the file
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Brisky86 said:
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Click to expand...
Click to collapse
it might. I was reading about some commits on github that broke cameras across the board, stock or from the play store. I tear laptops apart regularly enough to remember how, it's the process itself that sucks
After messaging mastamoon, "I imagine all the stuff that's being worked on is basically in d2-common, msm8960-common and d2kernel which d2spr shares with d2vzw. I would just make sure whoever is building for d2spr is pulling in all the necessary hacks needed at the moment. Honestly I'm not sure what isn't committed at this point, but check out commits by Dave Daynard (nardholio) & Dan Pasanen (invisiblek) and make sure you're using that stuff."
The kernel (within this ROM) he's speaking of might help with the issues revolving around the camera.
Camera Works
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Good to know thank hou
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
ChangeOfJinzo said:
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
Click to expand...
Click to collapse
Make sure you have the latest cwm recovery and you should be fine. I'd recommend flashify, I liked it better and seemed to function better then twrp manager. Also once you install twrp there's a method to update the recovery without a computer or making a recovery updater zip, which can also flash custom kernels. Though I recommend sticking with the stock kernel untill cm12.1 becomes more stable
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can anyone else confirm? I've yet to get this build in particular to boot...
iBlowpot said:
Can anyone else confirm? I've yet to get this build in particular to boot...
Click to expand...
Click to collapse
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
ChangeOfJinzo said:
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
Click to expand...
Click to collapse
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
iBlowpot said:
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
Click to expand...
Click to collapse
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Lrs121 said:
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Click to expand...
Click to collapse
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
iBlowpot said:
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
Click to expand...
Click to collapse
Probably a bad upload. I recommend using the new build.
FatalIll said:
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
Click to expand...
Click to collapse
also what bootloader and firmware version
Lrs121 said:
also what bootloader and firmware version
Click to expand...
Click to collapse
Hell, just give us your phone
Also, Lrs121... You had mentioned that you may try and cherry pick updates from other builds where the camera is working. I don't know much about cm source or building but have you considered using something like 'kaleidoscope git diff' to compare builds and see maybe where the camera fix is hiding?
Edit: not necessarily kaleidoscope, but git diff in general.
Hi,
I have searched for an answer but could not find anything as a solution.
My home button works on neither viper nor leedroid; it simply does not respond. Is there a known solution? I reflashing does not work either.
If you are on the N versions of either of those roms it depends on what Firmware you have installed. If you are on M Firmware you need to install the fix for Viper from the hub, unless they changed that on the newest version. As for Lee's rom during the aroma installer it will ask which Firmware you are on and it should work from there if you select the correct setting.
lightweaponx said:
If you are on the N versions of either of those roms it depends on what Firmware you have installed. If you are on M Firmware you need to install the fix for Viper from the hub, unless they changed that on the newest version. As for Lee's rom during the aroma installer it will ask which Firmware you are on and it should work from there if you select the correct setting.
Click to expand...
Click to collapse
Thank you for the reply! I installed leedroid with the N based firmware. Can you tell me how to proceed without losing my apps and data?
RootMaster2016 said:
Thank you for the reply! I installed leedroid with the N based firmware. Can you tell me how to proceed without losing my apps and data?
Click to expand...
Click to collapse
You could use a tool like Titanium Backup and make sure it is on your SD card or move it over to a PC after the backup. You could also try a dirty flash depending on what ROM you are on right now.
lightweaponx said:
You could use a tool like Titanium Backup and make sure it is on your SD card or move it over to a PC after the backup. You could also try a dirty flash depending on what ROM you are on right now.
Click to expand...
Click to collapse
OK I'm on leedroid beta 2 right now. So basically reflash with no wipe?
RootMaster2016 said:
OK I'm on leedroid beta 2 right now. So basically reflash with no wipe?
Click to expand...
Click to collapse
That should do the trick but it would still be wise to have some sort of backup somewhere.
lightweaponx said:
That should do the trick but it would still be wise to have some sort of backup somewhere.
Click to expand...
Click to collapse
Ah of course forgot to mention that. Should I select anything special in the options menu during installation? Thanks
lightweaponx said:
That should do the trick but it would still be wise to have some sort of backup somewhere.
Click to expand...
Click to collapse
Dirty flash did not work
At that point it sounds like you might need to do a full wipe. There should be some good instructions in that thread.
when it asks you for the firmware you are using during the installer, you need to choose the old one...else your fingerprint is broken.
You are obviously choosing the wrong option during installtion.
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Here is a video I made
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
thanks
MarJava said:
thanks
Click to expand...
Click to collapse
for what? :|
XDRdaniel said:
for what? :|
Click to expand...
Click to collapse
不错啊
MarJava said:
不错啊
Click to expand...
Click to collapse
what's nice?
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
是不是底包问题
MarJava said:
是不是底包问题
Click to expand...
Click to collapse
it isn't? do you know what's causing the problem? did it ever happend to you?
XDRdaniel said:
it isn't? do you know what's causing the problem? did it ever happend to you?
Click to expand...
Click to collapse
我没用MIUI啊
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
pedrosantosobral said:
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
Click to expand...
Click to collapse
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
XDRdaniel said:
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
Click to expand...
Click to collapse
No I had a different issue but I'm 100 sure that problem comes due to your file system...the versions u using is adapted to f2fs so it works but unmodified versions have a lot of issues and some of them doesn't even boot on f2fs
Sent from my OnePlus 3 using XDA Labs
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Diaze said:
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Click to expand...
Click to collapse
Still mm based. It has the firmware included, so you can flash it over any rom.
https://www.androidfilehost.com/?fid=961840155545570150
Hello Guys,
I need help regarding the issue that I'm facing. What happens is ROM get installed properly without any error but not boots up. It get stuck at boot animation screen. I tried lots of ROMs including DOT OS, C droid, AICP, TOXYC OS. Facing the same issue to all of the ROMs. I followed the below steps to install.
1. Download the ROM file
2. Download the GApps.
3. Booted into TWRP Recovery Mode.
4. Backup done (optional)
5. Wipe all the 4 partitions except Internal Storage.
6. Then install the ROM file and followed by GApps
7. Installation successful for both ROM & GApps.
8. Reboot.
I tried installing the ROM only but result was same.
I'm currently running on Oxygen OS Open Beta 10.
PLEASE HELP. THANKS IN ADVANCE.
Which TWRP do you use? Personally, I recommend this one by codeworkx: https://sourceforge.net/projects/ch....1-0-20180309-codeworkx-dumpling.img/download
Some roms require you to be decrypted; others don't. Most roms require the latest firmware (5.1.3) to be flashed before the rom, gapps, etc. Read the installation instructions carefully. Use the recommended firmware and gapps package linked to the rom. Before you start flashing roms, you should wipe your phone in fastboot mode: fastboot format userdata. This will wipe your phone clean; all your data will be gone. So, backup all your data to your PC before proceeding. After format, reboot directly to TWRP and move your firmware, rom, gapps, etc. to internal storage; follow the flash order and procedures exactly as outlined for the rom you want to try.
I tried installing latest TWRP (3.2.1-2) for my OnePlus 5T but no luck. Please suggest.
KDPalekar said:
I tried installing latest TWRP (3.2.1-2) for my OnePlus 5T but no luck. Please suggest.
Click to expand...
Click to collapse
The link to a working TWRP is in the post above; it's not the latest or official TWRP, but it works. Also, please read through this thread if you haven't already: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592.
Did you try to format data (after wiping the partitions) ?
bud7dha said:
The link to a working TWRP is in the post above; it's not the latest or official TWRP, but it works. Also, please read through this thread if you haven't already: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592.
Click to expand...
Click to collapse
Read the whole instructions and installed it but no luck .
Zark0s said:
Did you try to format data (after wiping the partitions) ?
Click to expand...
Click to collapse
sorry.. i didn't get u.
KDPalekar said:
sorry.. i didn't get u.
Click to expand...
Click to collapse
In twrp, when you go in the wipe tab, there is a "format data" button. It will wipe the data and internal storage partitions and remove encryption. But don't worry, depending of the ROM you flash it will encrypt again.
Zark0s said:
In twrp, when you go in the wipe tab, there is a "format data" button. It will wipe the data partition and remove encryption. But don't worry, depending of the ROM you flash it will encrypt again.
Click to expand...
Click to collapse
so do i need to do that as well?
KDPalekar said:
so do i need to do that as well?
Click to expand...
Click to collapse
I format data everytime I do a clean flash lol, so yeah just give a try and let us know if it works ^^
Hi,
It worked. I format the data and install the clean flash. Thanks a lot. One more thing can u please suggest custom ROM with ANDROID P notification panel.
KDPalekar said:
Hi,
It worked. I format the data and install the clean flash. Thanks a lot. One more thing can u please suggest custom ROM with ANDROID P notification panel.
Click to expand...
Click to collapse
Idk if a custom rom exists with that feature but there is a xposed module which does that and works on any custom rom (aosp 8.1 based at least) : https://forum.xda-developers.com/xposed/modules/xposed-android-p-ify-features-t3764556
Zark0s said:
Idk if a custom rom exists with that feature but there is a xposed module which does that and works on any custom rom (aosp 8.1 based at least) : https://forum.xda-developers.com/xposed/modules/xposed-android-p-ify-features-t3764556
Click to expand...
Click to collapse
I installed the Lineage OS, rooted, installed the xposed module, installed the android P fy module but still I'm not getting the exact look like android p notification panel. Can you suggest me ROM that works fine with Android P-fy module to get the exact Android p notification panel.
Please find the attachment. This is what I'm getting with Lineage OS.
KDPalekar said:
I installed the Lineage OS, rooted, installed the xposed module, installed the android P fy module but still I'm not getting the exact look like android p notification panel. Can you suggest me ROM that works fine with Android P-fy module to get the exact Android p notification panel.
Please find the attachment. This is what I'm getting with Lineage OS.
Click to expand...
Click to collapse
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Zark0s said:
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Click to expand...
Click to collapse
I tried AOSP Extended before a week ago. Everything was working fine except headphone Jack. Sound was not coming in my earphones. Sound from speaker grill was coming, even I tried with connecting to Bluetooth speaker, that's also working fine. The only issue I had with that headphone Jack.
Please suggest if you have any solution for that then I'll surely try it again.
Thanks
Zark0s said:
Did you check the module settings ? You can tweak some stuff.
Or maybe it didn't works because of Lineage (but it should, idk why not), but you can try aosp extended, which is closer to aosp.
Click to expand...
Click to collapse
Oh. How unlucky I'm. I just checked the headphone Jack with this ROM. Here also headphone Jack is not working. This is very unlucky. Do have any solution for this?
KDPalekar said:
Oh. How unlucky I'm. I just checked the headphone Jack with this ROM. Here also headphone Jack is not working. This is very unlucky. Do have any solution for this?
Click to expand...
Click to collapse
I think you didn't flash the latest firmware available (5.1.3), which you can find here :
https://forum.xda-developers.com/showthread.php?t=3728665
Zark0s said:
I think you didn't flash the latest firmware available (5.1.3), which you can find here :
https://forum.xda-developers.com/showthread.php?t=3728665
Click to expand...
Click to collapse
Thanks a lot Buddy. Flashed the latest firmware and now headphone Jack is live more. Thank you do much Buddy.