Related
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
I have same issue with CyanogenMod in all versions include M8
some discussion about this problem is here http://forum.xda-developers.com/find-7/find7-development/tutorial-how-to-install-cyanogenmod-t2801982 but I still can't find solution
All the CM11 based ROM has the black screen issue. Only Gummy ROM doesn't at the moment. I'm not discouraging anyone to use CM11, but for now, use Gummy ROM if you really don't want to use ColorOS and also don't want the black screen issue.
Same Issue on PA 4.4.2
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
... it would help if someone could give me a last_kmesg and logcat
ayysir said:
... it would help if someone could give me a last_kmesg and logcat
Click to expand...
Click to collapse
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Gummy rom does not have this issue.
Sebring5 said:
Gummy rom does not have this issue.
Click to expand...
Click to collapse
thats swell
Entropy512 said:
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Click to expand...
Click to collapse
my mistake
dmesg: http://pastebin.com/XVEszqrJ
logcat: http://pastebin.com/SDH7FXQv
I think it has something to do with thermal throttle and screen dim.
This logs are from CM.
rroohh93 said:
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
Click to expand...
Click to collapse
http://www.oppoforums.com/threads/rom-aosp-find7a-find7-team-gummy-rom.15593/
Problem Fixed!
mestermagyar said:
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
Click to expand...
Click to collapse
So CM pushed some fixes to address this black screen issue, a friend of mine already compiled them into a kernel, this kernel is compatible with any CM based ROM like PA or Cyanogen.
Just flash it and goodbye to black screen issue.
http: // aospal.hostingsharedbox. com/ayysir/find7/ kernel/ParanoidAndroid-find7-kernel-signed. zip
Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex
nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM
I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.
I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.
Is it fixed yet? Any news on this?
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
I installed the stock rom after this issus. I think the stock rom has a good battery life.
cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!
Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?
Hi all, I'm just wondering if there are others that have similar issue than mine?
The problem is that after updating my phone to CM13 20160922 version and any newer version, the touch screen would not work anymore on the ROM. Touch screen would still work in recovery.
I've tried to clean wipe before installation of ROM and the same problem persists.
If it helps, when I tried to install a new kernel (Xcelerate one) on the working ROM, the touch screen would also break.
Any help would be appreciated.
Do a clean install (by wiping cache, system, data) if you havent, and see if it helps. Can only suggest to take full logs (incl dmesg, and lastkmsg) and fetch it to fefifofum on the respective thread. Is the behaviour consistent or random? I face it randomly but I guess mine is a hardware fault.
The behavior is consistent. It always breaks the touch screen on the newer roms. I'll try to fetch the logs and maybe it would help. Thanks.
Anyone can help me with getting logs without a touch screen? ADB can't seem to connect and the device is unauthorized. Thanks for any help.
Well you are not the only one. Its all about drivers in kernel. I changed my digitizer and then with 6 or 7 touchscreen does not work although all fine in TWRP 3.0.2 Someone has to port those drivers to new kernel used in Android 6. i have little knowledge about it but i will try to fix it and if it works i will post it here-
mobaddict said:
updating my phone to CM13 20160922 version and any newer version,
Click to expand...
Click to collapse
wait do you mean it was working on cm13 before those versions ???
bauuuuu said:
wait do you mean it was working on cm13 before those versions ???
Click to expand...
Click to collapse
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
... i will check
mobaddict said:
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
Click to expand...
Click to collapse
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
bauuuuu said:
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
Click to expand...
Click to collapse
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
mobaddict said:
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
Click to expand...
Click to collapse
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
bauuuuu said:
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
Click to expand...
Click to collapse
Thank you. I'll try to check if this would work.
mobaddict said:
Thank you. I'll try to check if this would work.
Click to expand...
Click to collapse
I'll just wait for a kernel build since I don't know how to do this hehe
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
debasarkar said:
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
Click to expand...
Click to collapse
I think we just need to wait for a new build of the kernel and test if this solves our problem. I'm also waiting for a kernel build and will test it out if this would fix the issue. :good:
I don't know if the commit that was made by @bauuuuu was used in the new build of CM14.1 but the latest rom still has the touch screen issue. The new TWRP 3.0.2-1 is now also facing the same problem.
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
mobaddict said:
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
Click to expand...
Click to collapse
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
bauuuuu said:
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
Click to expand...
Click to collapse
Oh, wow! Hope that the 100Hz does the trick for my touchscreen and for others that are facing the same issue as me. Thank you for posting that. :good:
TWRP test build
Here is a test build for those with touchscreen issues. Please let me know if it works:
https://www.androidfilehost.com/?fid=313042859668276642
LineageOS 14.1 has been started.
https://download.lineageos.org/d2tmo
I'm running latest nightly with no problems so far.
Sent from my SGH-T999 using XDA-Developers Legacy app
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
toro143 said:
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
Click to expand...
Click to collapse
For Gapps: http://opengapps.org/
Lineage OS community: http://lineageos.org/community/
So far I'm loving it! Tried to dirty flash from CM but got an error.
So clean install and so far so good, must play with it some more and feels familiar
Thanks!
Camera crashes when going to movie mode. Open camera works fine.
Today weekly it's not installed. It gives an error code 7...
This problem was on cm roms before i ran linageos on my t999, usb tethering this service doesnt work when i turn on the wifi but when i restart my device and active it emediatly it works ,is there any solution ???
hi guys, i install this rom in my t999, and now i have a very rare problem ... i can't call, and no show signal ... (look the image), the problem become rare because i can recieve calls (says call from emergency service) and SMS ... i'm looking for this problem in google .. and nothing...
https://drive.google.com/open?id=0BxMZVpOD7gCdeWVEbHJjRlZ4UW8
https://drive.google.com/open?id=0BxMZVpOD7gCdd3FINWdEUUNnSDQ
what modem and nightly?
No sound at all
I recently experienced a problem after using CM 13 for quite a while on my S3 T-999. The phone doesn`t make any sound at all. Neither the speaker nor the microphone. I flashed LineageOS a few days ago but the problem still persists. I also tried Mokee rom but it also couldn`t get rid of this issue. I finally flashed stock rom and the sound is back. I can make calls and use youtube, the audio is just fine on stock rom.
The only problem is jellybean is too slow and battery consuming for my aging S3. Guy do you have any idea how can I make the sound work on this rom ? Any help would be appreciated.
What are the best custom Kernels to go with this ROM ???
is there any news about supporting d2 verisons or say goodbye to this device
hasan.sy said:
is there any news about supporting d2 verisons or say goodbye to this device
Click to expand...
Click to collapse
Support is discontinued.
hudson: Pull d2
* I don't have time to maintain these anymore
Click to expand...
Click to collapse
This device is still Rock solid and it's a shame we don't have support on this device anymore. I understand the developer though and I thank him for all his effort up until now. I hope someone else could continue his work on this great phone
pcaseiro said:
I hope someone else could continue his work on this great phone
Click to expand...
Click to collapse
Mokee rom updated every day. Carbon rom supporting too.
Hey, guys. Autocorrect for me isn't working even though it's on. When I type text in the virtual keyboard, it doesn't correct misspelled words. Any way to fix this?
I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
I'll try in the bext days....
a05haiji28 said:
Root first, then go to Vendor/Overlay/BluetoothResCommon.apk
delete it,then reboot,
Click to expand...
Click to collapse
Hi, I've tried today but in my elephone u pro there isn't a Vendor/Overlay/BluetoothResCommon.apk
Other ideas?
Laptapper said:
I've tried all treble pie roms and in all are the same problem with Bluetooth in call sound. First I thougt it's a problem with my elephone u pro, but in the meanwhile I've recognized that the same problem exist in many phones.
I'll hope that we can support the developers with a payment if they fix this problem.
I am willing to pay up to 50$ if someone is able to fix this problem for the elephone u pro.
If there's someone else who wants to get the problem solved then please write here your payment offer.
But it would be a shame if people make an offer here and do not stick to it later.
Click to expand...
Click to collapse
1. You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
2. You also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.
AndroPlus said:
You have to extract stock /vendor/etc/audio/audio_policy_configuration.xml and delete A2DP related section like this:
https://github.com/PixelExperience-...mmit/977444af69f10fc135d07e19f1e5f1183e73e9ff
then replace it (by root explorer or creating magisk module).
Click to expand...
Click to collapse
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?
Laptapper said:
Hi
I've tried, but the changed and saved file
/vendor/etc/audio/audio_policy_configuration.xml
will be automatically deleted at restart.
The folder is empty after restart.
Any ideas?
Click to expand...
Click to collapse
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?
[email protected] said:
By any chance did you get fully functional Bluetooth on the gsi rom or anyone else?
Click to expand...
Click to collapse
I'll hope so.
@AndroPlus has already fixed in call and may be he's on the way to solve audio also.
Has it been rectified in all builds
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march
Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
[email protected] said:
so is it safe to say that we can install the latest version of GSI provided by rom providers made in and released in march.
I would like to know that before i go ahead and transition over from stock to custom rom... mainly called PixelDust Pie rom version march
Click to expand...
Click to collapse
No, the fix needs device specific path and not all GSI has it.
I have the Razer Phone and have got either audio working or in call but never both... I am in the process of going through both audio routing files and see if I can combine them to get it to work, but I haven't messed with Android in years so it's taking more time than I anticipated to get caught up on all the changes you guys have made. The last time I built a rom was when treble was just on the discussion table. It really amazes me this bug has gone on this long, but maybe there's more to it than I'm seeing so far. I have seen some good devs working on this.
Enlighten me Please
AndroPlus said:
Thank you, but BT music works fine on my phone (Mi 9).
I don't know how to fix it...
No, the fix needs device specific path and not all GSI has it.
Click to expand...
Click to collapse
Hey @AndroPlus , could you possibly explain how to go about it. I would appreciate the help. I have got a nokia 7 plus with pixel dust pie rom on latest version running. Where and what do i need to do to get it up and running on my phone. I need to get in call bluetooth running. Thats the only thing stopping me from using this amazing blazing rom
Bluetooth music also does not work with me. However bluetooth calls work, so its weird that music/audio is not working.
Bluetooth music also does not work for me, but bluetooth calls work fine. I'm using Arrow GSI with Mi Mix 3.
Laptapper said:
Great job! Bluetooth In call is working.
I'll think it's not your development but for your know how to, I've send you 15 Euro.
Do you know also how to get Bluetooth audio music working?
Click to expand...
Click to collapse
That's on my AOSP ROM?
phhusson said:
That's on my AOSP ROM?
Click to expand...
Click to collapse
It's on resurrection remix pie, also headset over usb c is working. Only audio sound over Bluetooth is a problem. Do you've got a solution ir an idea what should I can try?
Btw do you have any idea how to control the led colours?
i still have no bluetooth calling on Mi Mix 3 on the @AndroPlus rom's so his solution definitely doesn't work for all devices.
furthermore there is still a bounty to get bluetooth working perfectly on vanilla android gsi's
AndroPlus said:
Oops, you also need to change /system/bin/rw-system.sh.
Please delete
Code:
mount -o bind /mnt/phh/empty_dir /vendor/etc/audio || true
and save.
Click to expand...
Click to collapse
Thank you sooo much! That´s all, I needed to do to fix my incall audio problem!
No changes in audio_policy.xml were needed - only removing this line from rw-system.sh