Related
Every time i try to copy a piece of text from built in browser, GMail, Email and probably some more apps causes force close to the app. I already tried wiping caches, factory reset even clean install. I use johnnyslt's unofficial CM10.1 ROM with all recommendations. Any ideas? Thnx!
nikos_moi said:
Every time i try to copy a piece of text from built in browser, GMail, Email and probably some more apps causes force close to the app. I already tried wiping caches, factory reset even clean install. I use johnnyslt's unofficial CM10.1 ROM with all recommendations. Any ideas? Thnx!
Click to expand...
Click to collapse
Same problem here. I've tried a few different clipboard extensions (Clipper, ClipperPlus, andClip)
Great rom - everything else seems to be working fine.
Evo3D - GSM
johnnyslt's unofficial CM 10.1-20130430
BaseBand 11.77.3504.00U_11.25.3504.06_M
Ok! It's fixed by today's update! And the speaker loudness on call i think is fixed! Great rom! Thank you johnny!
"And the speaker loudness on call i think is fixed" -- No it isn't.. Hope it does!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?
The Unlegacy Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for flo/deb include:
- Linux kernel 3.4.y merged in (currently 3.4.108 - mostly security patches and minor bug fixes)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only!)
- SELinux in Enforcing mode
Installation
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- No known issues for flo/deb yet.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Information about our experimental builds and progress you may find here.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7 (2013)
Contributors
Ziyan, Clamor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 8.1
Stable Release Date: 2017-03-24
Created 2017-03-24
Last Updated 2019-04-05
Reserved
GApps
If you want to install GApps, we recommend Open GApps Micro.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Hello)
Please add a night mode, with the icon in the blind
boom1982 said:
Hello)
Please add a night mode, with the icon in the blind
Click to expand...
Click to collapse
I simply use Darker for night time playing in the bed personally, I reduce brightness to 65% and apply a slight yellow tint. When most websites are white, theming the framework wouldn't matter that much anyways... and we kinda want to feel like a factory image (no dark mode in them either)
@Ziyan
It's a pity)
The rom itself works fine. Good job)
@Ziyan Thanks for your efforts on these older devices. I've used your work on both Gtab 2 and Grouper before I sold them. I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match. I haven't tried flashing any of the roms yet but figured I'd let you know.
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Anyway, just wondering if "in your travels" you've heard of this Netflix issue and might possibly know of a proper fix. Thanks again.
Mike T
webdroidmt said:
I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match.
Click to expand...
Click to collapse
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
webdroidmt said:
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Click to expand...
Click to collapse
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Ziyan said:
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Click to expand...
Click to collapse
Thanks for your reply. Here's the D/L for the drmblobs zip if you decide to take a look. https://www.androidfilehost.com/?fid=529152257862690585
Very weird on the MD5 thing, as mentioned I downloaded it twice and on a desktop PC so it shouldn't be a mobile issue??? I'm gonna' flash it later, will report if there's a problem.
Mike T
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
have volume wake option?
edit: stuck at "patch image "Patching system image unconditionally..."
boom1982 said:
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
Click to expand...
Click to collapse
Our little build server likes overdoing its job and building even if the changes don't affect flo - until this is fixed, it's enough to update every 3-4 weeks or so to get the security updates, unless I make an announcement here about a change
About /cache f2fs: there's simply no point, as that partition isn't actively used by the system (other than maybe OTA updates). I usually don't support it, as it can lead to more complications than what it worth...
@Ziyan
Thank you for your reply)
I really like the way the rom works.
Only have to use a lot of additional tools to at least somehow expand the settings)))
Good work... but video recording with green lines in Google Camera 3.2, stock kernel, Nexus 5
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Mind giving me a bit more details regarding this? I can connect to a Wi-Fi Hotspot created with my Nexus 4 (also running Unlegacy Android 7.1) just fine, and can browse the internet with the Nexus 7 through it (mobile data activated on the Nexus 4)
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Alright. We'll be soon opening a Nexus 5 thread as well.
Ziyan said:
Alright. We'll be soon opening a Nexus 5 thread as well.
Click to expand...
Click to collapse
Good news! Thanks for your work!
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Where did you find this fix wi fi, give me a link?
Mayrbek86 said:
Where did you find this fix wi fi, give me a link?
Click to expand...
Click to collapse
Install via TWRP.
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Lyngze said:
Hello, I have problems with no audio and microphone activity when making calls or using Google Now/Assistant with a Bluetooth headset/car head unit.
The problem have persisted for some time now when making calls made via Bluetooth. At first it was limited to bad quality for recipients of my calls, and I blamed this on a new update to an unofficial Oreo ROM (Something PixelExperience).
However it has worsened, and now I cannot hear anything when making calls via Bluetooth, the microphone also seems to be cut off entirely, and the same is the case with Google Assistant.
Music and system audio seems to work just fine.
What I have tried without any luck so far:
A multitude of Oreo ROMS
Stock 26S chinese ROM (had to reinstall TWRP and everything)
Custom EUI 5.9 roms, based om 26S and 28S
A couple of different kernels
I am backup at running Resurrection Remix official Oreo atm.
I hope someone might have a clue at what to try.
If you need logs please let me know, however I am not an avid user of logcat/busybox(/others?) but should probably be able to use them og pointed in the right direction.
Click to expand...
Click to collapse
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
LameMonster82 said:
Maybe the mic is broken. If you tried with so much ROMs that's definitely a hardware problem.
Click to expand...
Click to collapse
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Lyngze said:
Thank you for the answer, the microphone is not the problem. I have tested the bluetooth headset using another smartphone with no issues.
The issue also persists with my car head unit, it might be a faulty bluetooth unit, however it works just fine when transfering data and listening to music.
I only experience the problems when trying to use microphone or call using the bluetooth headset.
Click to expand...
Click to collapse
I did the following:
Reset and begin from scratch....
-Install TWRP latest version if you have not.
-Make backup external of your data, media, etc.
-Wipe everything cach, system, dalvik, data, internal.
-Restart in recovery.
-Download a EUI 19s rom on PC and transfer to your TWRP map on your phone.
-Install trough TWRP the EUI Rom and let it boot.
-Make the minimalist settings, so the rom is installed on your phone.
-After that go to recovery, choose format your phone.
-Restart recovery.
-Transfer the modem firmware 26S, your choise Oreo rom, and Gapps arm 64, 8.1, nano to your phone.
( Advice: infrag AICP unofficial 20032018 version, bugless)
-install those together without reboot in between.
-After that Reboot system.
When making settings in the rom CHOOSE NEW PHONE, DO NOT DOWNLOAD YOUR SETTINGS TROUGH GOOGLE ACCOUNT and do not install other backups.
Then you will have a total clear phone.
Very much work but it helped me with camera and audio problems.
I hope it does for you too.
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Lyngze said:
Thank you, I will try that when I have some time at the computer, I did All og the above except for installing 19S beforehand.
I have read about another who had similar problems to med, and Foxes them by replacing a systems file. Is there any way of optaining this file without flashing the rom and extracting it? Can I open the rom file directly to extract the file? (Filename was Bluetooth-***.so or something)
Edit: This is the post I al talking about: https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635
Click to expand...
Click to collapse
It is the Bluetooth file of 15S....That's a very long time ago.
I'm not sure with compatibility.
Very much so, however a similar approach might work with say 19S.
But I don't know how to get the .so file without flashing the rom and copying it from the system directory...
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Lyngze said:
I have now tried installing both Chinese 15S and Indian 19S without any luck, I am still not able to use bluetooth for calling. No sound or microphone what so ever using the bluetooth headset.
Click to expand...
Click to collapse
Does your bluetooth status says connected (no phone)
in the same post https://forum.xda-developers.com/le-max-2/help/issues-bt-16s-t3543635/page2 pn #12 there is bluetooth so file
try that... it works on every EUI version... to verify .. try EUI 16s (Indian ver) and check your bluetooth device
Thank you for pointing that out!
I have tried with a clean install of the entire 15S ROM without any help.
I tried the .so file with my Oreo system, and now I cannot event turn bluetooth on...
Regarding bluetooth status it just says "connected" followed by battery percentage.
I can turn phone audio on or off without problem, but when turned on there is simply no sound in calls...
Hi Guys !
In this early stage we found out how to boot android Q (Erfan GSI) with a vendor/boot combo and some patches.
How to : file : https://mirrors.lolinet.com/firmware/gsi/
1. flash Q vendor/ boot combo. In fact it's latest Mokee vendor + los16 boot : https://androidfilehost.com/?fid=1395089523397937735
2. system.img (a only)
3. flash Permissiver_v2
4. flash FixZygote
5. boot
NOTE :
1. do select your SIM when it pops up the first time ! Calls should work and LTE should show up
2. a reboot messes up your APN and will disable LTE again - making a new APN will fix the LTE
What's working :
* BT working and can be toggled on/off
* NFC seems to be working but can not be toggled OFF - to be tested if it's indeed working when ON
* calls but laggy dialer - volume can be adjusted when calling
* LTE - but a reboot will disable LTE again - restoring to default or making a new APN and reboot will enable LTE again
* file manager works but very laggy sometimes
* stereo speakers
* magisk 19.0 (special one) root ok but manager crashes
What's NOT :
* wifi
* playstore : to be looked into / someone could login others couldn't...
* camera
.....
So for those who want to test, give it a try.
Perhaps some future patches will help on further development.
Thnx @yarecco
Man, is it possible to boot latest build? Or make data and some more works on April build from your guide?
HYPECUT said:
Man, is it possible to boot latest build? Or make data and some more works on April build from your guide?
Click to expand...
Click to collapse
It's not possible to get a fully functioning Android Q until Phh officially supports it into his AOSP builds, or we get a Pie vendor/kernel.
SOME MINOR UPDATE INFO ON BOOTING LATEST GSI 10
Latest GSI don't need additional files (like Permissiver or FixZygote) to boot properly. It's fairly easy to setup your phone.
Some files you might need :
1. vendor : Speedy A7 Vendor_Boot(Baddar RC1.1 kernel) Combo
2. GSI's : take a peek here :
https://sourceforge.net/projects/expressluke-gsis/files/
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
https://github.com/phhusson/treble_experimentations/tags
https://sourceforge.net/projects/developerluke-roms/files/GSIs/
...
3. gapps : https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/ tip : take the pico one otherwise, depending gsi size, you might have to resize system (error70 when gapps are flashed)
4. magisk : https://sourceforge.net/projects/developerluke-roms/files/phh-magisk/
5. button reverse if needed (flash in magisk) : A2017X_swap_button_Module_unity_key
....
Installation : starting from Pie
1. wipe system, vendor, data, cache
2. flash speedy vendor combo
3. flash rom img to system
4. boot phone ( if red light, no worries, just press power to boot ) (also no worries when no OS seems to be installed when trying to boot out of twrp)
5. reboot twrp
6. flash pico gapps (some gsi like PE10 have gapps included) and magisk 20.2 (note : if you get a gapps error70, you'll have to resize system after flashing the img)
7. reboot and enjoy
BUGS :
Have tested some gsi now and only major bug is the NFC.
Depending on the gsi you might have a non working camera, fp too.
After testing some gsi, imo these are worth a try : with working camera, wifi, calls, fp, BT, hotspot
* HAVOC 3.0 : https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/
* PE10 : https://sourceforge.net/projects/expressluke-gsis/files/PixelExperience/Ten/
* AOSP 10.0 v204 : https://github.com/phhusson/treble_experimentations/releases/tag/v204
* EvolutionX 3.3 : https://sourceforge.net/projects/expressluke-gsis/files/EvolutionX/Ten/
Feel free to comment on your personal use.
Ofc GSI are still to improve but worth a try.....till we have our own device specific Q roms
thnx @atakan33
why not using Speedy latest Combo with kernel RC1.2 ?
https://androidfilehost.com/?fid=6006931924117923540
Temporay fix for the CAMERA on LOS17
Just flash this in twrp ( do mount system ) : A2017X_LOS17_GSI_camera_fix
or manual fix :
search system/etc/ld.config.27.txt
change : namespace.vndk.links = system,default to namespace.vndk.links = system,default,runtime
thnx @AndyYan @phhusson
Hi raystef66,
I installed this a couple of hours ago. Installation was a breeze following your guide. I had a play services error but a wipe of data/cache fixed it. I installed the aosp 10 version. Bluetooth seems to not be working for me, it connects but does not play sound thru B/T speaker and WIFI doesn't auto connect after reboots. Everything else seems to work pretty well (I didn't try NFC) but the camera worked for me without flashing anything else. Really nice job, especially for first go round at 10.
Thanks a million.
tlarm said:
Hi raystef66,
I installed this a couple of hours ago. Installation was a breeze following your guide. I had a play services error but a wipe of data/cache fixed it. I installed the aosp 10 version. Bluetooth seems to not be working for me, it connects but does not play sound thru B/T speaker and WIFI doesn't auto connect after reboots. Everything else seems to work pretty well (I didn't try NFC) but the camera worked for me without flashing anything else. Really nice job, especially for first go round at 10.
Thanks a million.
Click to expand...
Click to collapse
can you log on matlog app while connecting and playing media and do adb shell dumpsys media.audio_policy and send it for txt
cant boot
hello
i installed the spuddy combo , gsi from havoc A only after wiping.
but the phone not booting just stack on the logo.
any suggestions?
ty
david
atakan33 said:
can you log on matlog app while connecting and playing media and do adb shell dumpsys media.audio_policy and send it for txt
Click to expand...
Click to collapse
Okay, I think I have the log, it's 7,000+ words long, do you want that posted on here?
tlarm said:
Okay, I think I have the log, it's 7,000+ words long, do you want that posted on here?
Click to expand...
Click to collapse
yes send it for txt file
atakan33 said:
yes send it for txt file
Click to expand...
Click to collapse
hopefully this worked
tlarm said:
hopefully this worked
Click to expand...
Click to collapse
p.s. prob should have noted I had flashed PE10 instead of the asop 10 I tried yesterday but the result is the same.
tlarm said:
hopefully this worked
Click to expand...
Click to collapse
one more log needed we need log from using matlog ( from playstore) .Send log while music playing on bt speaker .
atakan33 said:
one more log needed we need log from using matlog ( from playstore) .Send log while music playing on bt speaker .
Click to expand...
Click to collapse
That was while I was attempting to play on bt speaker. It connected but no sound came from bt speaker, intermittently the sound would come out of the phone speaker but for only a one second and then no sound at all.
tlarm said:
That was while I was attempting to play on bt speaker. It connected but no sound came from bt speaker, intermittently the sound would come out of the phone speaker but for only a one second and then no sound at all.
Click to expand...
Click to collapse
Here's from the matlog app. I had to zip the file because the txt file was to large to upload. This is prob more info than you asked for but wasn't sure how to do only adb shell dumpsys media.audio_policy from the app.
tlarm said:
Here's from the matlog app. I had to zip the file because the txt file was to large to upload. This is prob more info than you asked for but wasn't sure how to do only adb shell dumpsys media.audio_policy from the app.
Click to expand...
Click to collapse
thanks .Thats enough
Apart from unstable NFC in GSIs I've tried (Havoc 3.0 and EvolutionX 3.3) sometimes UI hangs and for now they are not as smooth as LiquidRemix (PIE) which is my favourite GSI (I'm using it till now).
In Evolution I've found option to wake phone by double tap which is something new in GSIs I've tried so far. Also Evolution comes with GApps so you don't have to flash it separately and worry about system partition being too small. Overall it's all going in good direction
^^Stable enough for daily use?
I'm really digging the battery life on android 10 on the 7t. I've had the set up in my sig for well over a year now. It's ok and works well but battery life could be better (esp considering new battery installed earlier this year).
Edit: I'll answer my own question. No. The nfc keeps cycling on/off. I think that's also what's introducing significant lag.
Hopefully this can be resolved to give this device a bit more life.
Nice, I wasn't sure if the Axon 7 will get some Q love.
Will try some of these ROMS.
Thanks OP