Weird connectivity issue in Marshmallow - Nexus 7 (2013) Q&A

Hi, I've been using lolipop (CM12) for quite a while in my N7.
Recently I've upgraded to marshmallow.
But I'm facing two problems.
1. I can not find any other device In SHAREiT send mode.
2. I can not find any other device in KOF 98 bluetooth multiplayer mode.
I've tried CM13 latest stable,beta and pureNexus (AOSP based) marshmallow rom.
This happens in both firmware. Tried pureNexus stock kerner, cm stock kernel and ElementalX kernel.
However this problem doesn't occur if I use Lolipop (CM12 or any other lolipop).
I'm totally clueless as why this is happening.
can any one please help?

Related

OTG Wakelock Problem

Hi Everyone,
I have constant kernel wakelocks from :
1. fusb301_otg_wl
2. 6a00000.ssusb
This happens only when I use CM13, CM14.1, OOS Nougat Beta
It does not happen when I use Oxygen OS 3.2.4, 3.2.6, 3.2.7
It drains battery constantly and is making the phone unreliable
I recently formatted the entire storage/system/data partitions and flashed the Nougat Beta but still the same issue.
Any help would be greatly appreciated.

LG G3 D855 custom Rom??

Is anybody still using a LG G3?
I love mine, I rooted it recently and install Lineage 15(android 8.0)
I keep getting the Magisk safetynet fail.
Should I flash a different Rom?
Is there a better Rom?
Or can anybody help me with the safety net?
Thanks
Maybe try flashing latest version of magisk if you already hadn't?
I had resurrection remix for a day or two which is pretty similar ROM but I forgot if I had any problems with safetynet.
I have Magisk 16.0 installed and it says it is upto date.
Someone told me, it should be 16.1.
Mgisk 16 is the latest version as of today.
The only thing I can tell you is to download a bunch of top roms and try each one...
I'm using fulmics, which is based on stock rom and is outdated af, but SafetyNet is passing.
I just want to have everything run as its supposed to and be able to delete blot wear etc.
The stock Rom was OK, but I thought I'd give a custom Rom a go and see what it's all about.
The safetynet is the main problem I've found so far.
If you want a debloated stock based MM ROM, I recommend CleanROM, works great - fast, debloated, choice of kernel and which apps to install or not and more in aroma installer. Magisk is included.
About safetynet: as others have recommended, use magisk 16. Works with every ROM I tried, Fromm MM to O.
I'm on Lineage 15.1 now, with CleanROM as secondary via multirom (for the stock camera, but safetynet won't work on secondary). But the other Oreo ROMs work nicely, too.

headphone bug in Lineage ROMs.

I recently installed the Lineage ROM and then the Pixel Xprience Unofficial ROM. I faced this problem that whenever I connected earphones, there was no output via the earphones.Youtube videos even lagged when playing with earphones on but was fine with speakers in the Pixel Xprience ROM.
Did anyone else face this issue?
breakingbot said:
I recently installed the Lineage ROM and then the Pixel Xprience Unofficial ROM. I faced this problem that whenever I connected earphones, there was no output via the earphones.Youtube videos even lagged when playing with earphones on but was fine with speakers in the Pixel Xprience ROM.
Did anyone else face this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/sho...665&p=75020309
Flash 5.1.1 stable OOS firmware and flash in twrp and reboot
Done
Let me kn if it worked
sauaditi said:
https://forum.xda-developers.com/sho...665&p=75020309
Flash 5.1.1 stable OOS firmware and flash in twrp and reboot
Done
Let me kn if it worked
Click to expand...
Click to collapse
I currently am on limited data plan so it will take a while for me to download 5.1.1 stable OOS.
But I observed that the above errors were not present on MoKEE ROM and AOSP Extended ROM or when I went back to OOS Open Beta 9. Tried dirty flashing Lineage over both AOSP Extended and MoKEE but the issue persisted.
Just the firmware is 60mb. Type docs oneplus 5t firmware xda into google. They are flashable zips
Solved.
Flashing the OOS 5.1.1 ROM helped. The earphones problem appears solved in Lineage ROMs. Thankyou for the guidance.

Samsung Galaxy A5 2017 Custom ROM and Issues with Fixes

So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.

NO Sound NO USB Detection after reverting back to oreo based rom from PE

Hello,
Hope you guys are doing well!
Guys i require some help. Yesterday i have flashed pixel experience latest CAF rom and today I reverted back to Havoc OS Mod but unfortunately i am not getting sound output and not even my device is detecting in PC. Only charges. Also pen drive via OTG is not being detected.
Please help.
Flashing Method of PE:
Pie Firmware
Compatible TWRP
ROM
Reboot
Flashing Method Havoc OS Mod:
Oreo Firmware
Official TWRP
ROM
Reboot
Please help.

Categories

Resources