Related
CyanogenMod 7.2.0-RC2+ Galaxy 5 Port
Latest release: v2.4 [20120518]
Latest Google Apps package: 20110828
Hey folks,
This is a port of CyanogenMod 7.2.0-RC2+, a community-developed Android ROM based on Gingerbread 2.3.7, for the Samsung Galaxy 5 I5500 (Europa) phone. The current port status is stable - most hardware is working correctly, but see post #2 for known issues.
Special thanks to Motafoca for starting CyanogenMod development, DrMacinyasha for the hosting, OuNao for the fake dual-touch module, sensor work and general assistance, mikereidis (author of Spirit FM Radio app) for helping with FM audio issues, and of course, thanks to all of you for testing!
Pre-requisites:
Visit the Basebands thread and make sure that you are using a baseband that is recommended for CyanogenMod. If you are still using an Eclair ROM, you must update your baseband or you will experience boot loops.
Visit the ClockworkMod thread and install the latest ClockworkMod build via Odin.
Install the GooManager application from the Google Play store.
Installation (updating from older CM7 build):
Open the GooManager application.
Select the Check for rom updates option.
Click on the notification for the available update and then click the Download button.
When the download finishes, enter recovery and install the update package followed by the Google Apps package.
Installation (first time/new users):
Open the GooManager application.
Navigate to psyke83 -> roms -> galaxy5.
Click on the build you wish to install from the list.
If needed, click the Download Gapps button to download the Google Apps package. The most recent (and most suitable) version will always be selected for you automatically.
Click on the Download button to download the rom.
Once the download(s) are complete, reboot into recovery and install the update package, followed by the Google Apps package.
Important: if you are updating from a stock or custom ROM, choose the data wipe option before rebooting.
Latest Changelog:
20120518 [v2.4]
Updated CyanogenMod source - version 7.2.0 RC2+ (pre-release).
Various improvements to libaudio: updated to Adriano Carrata's rewritten libaudio code (with my Samsung customizations re-added), added user-adjustable audio attenuation (disabled by default - see post #2), implemented Samsung's proprietary snd_set_extamp ioctl to improve audio quality, reduce in-call volume on headsets & fix FM radio background hiss.
Updated kernel with KSM (Kernel Samepage Merging) support - disabled by default, see madconfig documentation in post #2 for details.
Switched to wpa_supplicant v5 & awext driver. This fixes the issue in which wifi didn't connect properly either on first boot, or when activated via the notification bar/widgets.
Switched to libjpeg-turbo for better performance in Gallery & other apps making intensive use of jpeg images.
Switched to CM7 version of libgralloc & libcopybit, updated libcamera source.
Added support for automatic ROM re-odexing to madconfig (recommended only for people not using an app2sd method).
Small change to fake dual-touch driver to slightly improve touchscreen edge sensitivity.
Added support for ROM downloads/OTA updates via MAD Manager. Note: GooManager is still supported - it's your choice which application to use.
20120401 [v2.3]
Hotfix 3 [18th April]: kernel: fix shutdown issue.
Hotfix 2 [16th April]: kernel: enabled CGROUPS + CFQ IO scheduler (seems to reduce lag), various patches to improve performance/stability; g5sensord updated to v3.4 (low pass filter to reduce compass needle dancing).
Hotfix 1 [10th April]: kernel: fix headset detection problems, experimental change to improve stability when rebooting to recovery; g5sensord updated to version 3.3 (corrected bug in calibration file, hack to stabilize compass on high pitch)
Updated CyanogenMod source - version 7.2.0 RC1.
New kernel (label: gio2europa). Based on Samsung Gio Froyo source, updated to latest Code Aurora froyo_almond revision. This kernel has a more accurate battery driver, more efficient power saving for the mmc (wifi/sd) interface, and includes many fixes from Samsung and Code Aurora Forum in contrast our original kernel source.
New wifi driver + firmware (3.0.70.23, from Samsung Gio Froyo system image). This wifi driver is more recent than our official source, has better mmc power management code, and appears to be more stable. The minimum CPU frequency also set to 122Mhz (really). This frequency usually caused sleep of death issues, but this new driver may be immune.
Various patches for memory leaks and minor bugs from gerrit.
Updated sensor daemon (g5sensord) to latest revision (v3.1) - adds calibration data persistence, calibrated data and magnetic z-axis, saving of hard and soft iron calibration data. Should fix the Google Sky sensor issue. Thanks OuNao!
Enable setup_fs tool by default. This tool will check /data and /cache on each boot, ensuring that they are formatted properly as ext4 filesystems. If not, the partitions will be formatted automatically. This should make upgrading from Froyo more painless, and also fixes a common issue in which /cache corrupts randomly (perhaps due to unclean dismounts when the phone is not rebooted properly).
GooManager support now working correctly, which allows for future OTA updates.
20120317 [v2.2]
Hotfix 1: changed kernel config (to test for battery improvements), re-enabled WOW suspend in wifi driver
Updated CyanogenMod source - version 7.2.0 RC1.
Cherry-picked various patches from gerrit to fix issues with core binaries/libraries (dalvik, bionic, zlib, etc.).
Kernel: updated europa-battery, pmem, fsa9280, android staging drivers.
Kernel: reduce minimum CPU scaling frequency to 122Mhz (to see if sleep of death occurs with the new wireless driver).
Wifi: using AR6kSDK.3.0_RC.298 source with patches to allow usage of Samsung's firmware blobs, disable WoW (Wake on Wlan), and fix a certain case in which the driver blocks suspend. Note: the newest driver from freescale (AR6kSDK.3.1_RC.563) is not stable with our phone. This can't be fixed easily, as the problem appears to be within the new proprietary firmware blobs, which is something I can't fix. In the meantime, this driver should work well (and hopefully without any sleep of death issue).
dhcpcd: patches to optimize dhcp requests for Atheros AR6003. This improves connection/reconnection speed and reliability.
libhardware_legacy: increase wifi loader timeout from 1 second to 5 seconds. This ensures that the wireless driver is given time to settle before the first scan occurs.
wpa_supplicant_6: wait for control interface monitor to be brought up before starting. Improves reliability of wireless when reconnecting from idle.
libaudio: fix for minimum in-call volume being incorrectly muted in certain cases (including on speakerphone); fix FM audio when using no-microphone headphones.
Switched to OuNao's open libsensors - completely fixes accelerometer lag.
Switched to "g5sensord", Ounao's open memsicd replacement based on freescale's eCompass code - more battery efficient than proprietary memsicd daemon.
GPS: use worldwide SUPL server by default. Initial reports indicate that people are having better connectivity with this setup overall.
Compcache: back to 18%.
ADWLauncher: lock action buttons by default (helps avoid cases in which users accidentally detach the icons for these buttons).
Change scrolling cache setting to further improve scrolling speed.
Disable automatic brightness setting by default. Our phone has no light sensor, and I suspect that the software implementation may be causing battery drain.
20120305 [v2.1]
Hotfix 2test3 [10th March]: Kernel: reverted all changes since v2.0 release (to hopefully prevent battery drain); ar6000: avoid setting refClock rate (may improve wireless stability); reverted to CyanogenMod wpa_supplicant v6.
Hotfix 2test2 [8th March]: Same as hotfix2test1, but using stable kernel instead. Please compare against hotfix2test1.
Hotfix 2test1 [7th March]: Reintroduce CodeAurora kernel with fixes for battery usage (but further testing is needed by the community); updated new ar6000 driver to match suspend/resume/bluetooth coexistence behaviour of stock driver; switched to wpa_supplicant & hostapd 0.8.x from Atheros SDK to improve wireless behaviour; fix FM audio when using no-microphone headphones.
Hotfix 1 [6th March]: New wireless driver (AR6kSDK.build_3.1_RC.563) from Freescale i.MX53 source release - wireless is now stable. Modified source is available on github (freescale branch).
Updated CyanogenMod source
New ar6000 driver (adapted from AR6kSDK3.1 source package used by the Sony PRS-T1/JP e-book reader); enabled combo scanning in wpa_supplicant_6.
libaudio: fixed combo device issue (ringtone in speaker + headset/headphone)
libsensors: using OuNao's libsensors with change to further reduce battery consumption during idle. This completely fixes sensor lag. Thanks to OuNao.
Adjusted smartassV2 CPU scheduler to idle at lower frequencies
Enabled CGROUPS in kernel to minimize data starvation issues.
Updated fake-dualtouch module to v9.1 (fixed).
Enabled Goo-inside.me OTA update support (requires Goo-inside.me app)
20120206 [v2.0]
hotfix 2 (6th February): more fixes for microphone and headset routing. I can't reproduce call echo, so it may or may not be fixed.
hotfix 1 (6th February): due to popular demand, the microphone has been enabled to allow voice calls. [sarcasm]In future releases this will be a paid feature.[/sarcasm]
Updated CyanogenMod source (almost 7.2.0-RC1).
Kernel: updated OuNao's dualtouch module to the latest version (v9.1, which also has edge sensitivity fix).
Kernel: updated android staging kernel drivers from 2.6.35 kernel (notably bringing improvements to the lowmemorykiller driver).
Kernel: audio driver patches to prevent rare blackscreen during incoming calls from idle/low memory conditions.
Framework: disable scrolling cache (prevents lag in certain apps).
Framework: switched to stable copybit version with blending bug fix.
Audio: further updates to latest CAF libaudio version with FM support added. Bluetooth calling needs testing (I don't have a peripheral to test).
Camera: fixed force close error during zoom.
Mobiledata: added 2g/3g mobiledata switch option (you can set the mobiledata button to switch between 2g/3g mode instead of simply turning on/off data)
FM: Fix audio routing (where headphones sometimes stopped working after closing the radio app); respect upper and lower frequency limits; looping between low/high frequency limit during manual seek is now possible.
Network: SIM lock messages will no longer be ignored. This may help people who have problems using SIM cards that require a PIN unlock (note: this is not related to the reboot problems with certain SIM cards).
Updated USBController.cpp (tethering) code to possibly prevent reboots after extended use.
Refreshed ClockworkMod Recovery official build to 5.0.2.8 (thanks to koush)
Moved to new hosting on goo-inside.me (thanks to DrMacinyasha), which allows for better ROM Manager integration. This also means no more weekend download restrictions!
Improved LatinIME key sensitivity (key presses are recognised with better precision than before).
Settings -> About phone -> Mod version will now show the exact build date, which helps you to know exactly what version you're running.
Update notifications & automatic ROM updating now available (ROM Manager Premium users only).
Increased compcache to 26% (may be useful for those who have no swap).
Decreased wifi scan interval to 45 seconds to help with reconnection problems if you use hidden SSIDs.
Switched to US GPS servers by default.
???
v1.9 - DepositFiles, Mediafire, HotFile - 25 January 2012:
Hotfix 3 - DepositFiles, Mediafire, HotFile [26 January]: libaudio: updated code based on rmcc's geeksphone zero version, fixed no mic headsets (including FM routing).
Hotfix 2 [bad, please wait for newer hotfix] [26 January]: libaudio: updated code based on rmcc's geeksphone zero version. May help with some routing problems.
Hotfix 1 - DepositFiles, Mediafire, HotFile [26 January]: Kernel: disable samsung's drop_caches hack (may help reduce lag related to paging of swap). libaudio: fix for headphones issue (thanks to kingmaya & OuNao for troubleshooting).
Data wipe?: only if you have problems.
Updated CyanogenMod source (7.2-RC0)
Now using ICS transition and rotation animations
Fix for "stuck" notification items
Kernel: remove SCHED_HRTICK patches due to instability
Kernel: tweak smartassV2 scheduler to use more appropriate CPU frequencies for idle and awake states
Use safer mount options to reduce chances of data corruption
Reduce default compcache usage to 10% of memory
Tweaked TCP buffer for wifi device to improve performance
Improved Bluetooth reliability (enable HFP, increase max connections 1 -> 3).
v1.8 - DepositFiles, Mediafire, HotFile - 6 January 2012:
Hotfix 1 - DepositFiles, Mediafire, HotFile [7 January]: Kernel: back to original europa_battery.c driver from 2.6.32 kernel, with fix for 99% charge issue (should now stably charge to 100% and discharge without any erratic jumps); fixed video encoders and decoders (more efficient decoding of Youtube, etc., and now video recording is as fast as the stock ROM); libcamera: tweaked default exposure settings to slightly darken video recording; Boot: disabled setup_fs service (just in case it's causing a random /cache corruption issue).
Data wipe?: only if you have problems.
Updated CyanogenMod source (Android version 7.2-RC0)
Kernel: rebased on updated Samsung source.
Kernel: rebuilt using latest stable linaro gcc release: 4.5-2011.11
Kernel: removed mmc31xx axis orientation hack
Kernel: added new interactiveX CPU governor
Kernel: stability/performance patches added
Using new memsicd daemon which doesn't require mmc31xx kernel driver hack
Renamed usb tethering device from usb -> rndis (cosmetic)
New wifi module built from updated Samsung source; the only change is that Wireless-N mode is enabled.
Using wpa_supplicant_6 with ar6000 supplicant driver.
Updated adreno200 libraries (from latest Callisto Gingerbread ROM).
Tweak LatinIME keyboard (more compact)
Enable surface dithering by default (it improves font rendering quality without much performance drop)
v1.7.2 - DepositFiles, Mediafire, HotFile - 7 November 2011:
Data wipe?: only if you have problems.
Hotfix 1 [7 November 2011] Fixes wireless hotspot mode. Note that the hotfix is on ROM Manager (but I don't want to be releasing hotfixes any further).
Updated CyanogenMod source.
Removed optimization from framework that causes split video issues on our phone.
Added brightness and vibration presets - should fix notification icon issues.
v1.7.1 - DepositFiles, Mediafire, HotFile - 1 November 2011:
Data wipe?: only if you have problems.
Now distributed via ROM Manager.
Updated CyanogenMod source.
Using stock ar6000 driver & new wpa_supplicant_6 with awext emulation (patch thanks to Nicu Pavel) and fix for wifi hotspot mode.
Swapped volume controls when phone is at 90 degree anti-clockwise orientation.
v1.6 - DepositFiles, Mediafire, HotFile - 7 October 2011:
Data wipe?: only if you have problems.
Hotfix 4 [fixed2] - DepositFiles, Mediafire, HotFile [16 October 2011]: Fixed random disconnect issue with wifi driver; updated wpa_supplicant_6. Note: please report if you can't scan for access points correctly (should only happen if you do a data-wipe/fresh install). If this happens to you, be patient and wait 1-2 minutes for the list to appear properly.
Hotfix 3 [fixed] - DepositFiles, Mediafire, HotFile [15 October 2011]: [Fixed: MAC address problem with Google Sync] Using CM7 wpa_supplicant v6 with patch to fix wifi-hotspot activation; downgraded to slightly older wifi driver based on 2.6.35 kernel source (should be more stable, prevent sleep of deaths, and has working ad-hoc networking); fixed lense lockscreen text position; fixed problem with "split" video; fixed rendering effects. Note: You should wipe your dalvik-cache to avoid any problems.
Hotfix 2 - DepositFiles, Mediafire, HotFile [13 October 2011]: Reverted to v5 CyanogenMod wpa_supplicant driver (to fix ad-hoc networking); updated wifi driver; new kernel battery driver; decreased lockscreen bottom dip; some optimizations to framework code for increased performance. Note: your dalvik cache will be regenerated (i.e. first boot will be slower), and you may want to clear your battery stats due to the new battery driver. If you have problems, manually clear the dalvik cache.
Hotfix 1 - DepositFiles, Mediafire, HotFile [12 October 2011]: New hotfix to celebrate 800,000 CyanogenMod downloads & 1 million total MADTeam downloads! Fixed compass orientation, changed to newer wifi driver due to sleep of death issues with stock version.
Updated Gingerbread 2.3.7 / CyanogenMod source - no longer marked as Release Candidate code.
Due to reported problems, reverted to stock wifi driver - the only change is that wireless-N mode is activated.
Replaced CyanogenMod's v5 wpa_supplicant with Samsung's v6 version. This should improve wireless signal with the stock driver.
Fixed light toggle button in notification menu.
Optimizations: reduced VM heap size to 24m, disabled surface dithering.
Small tweaks & fixes.
v1.5 - 1 October 2011:
Battery stats wipe?: You must wipe your battery stats in ClockworkMod for this release, since we are using a modified kernel battery driver (and your existing stats file may be invalid).
Data wipe?: A regular data-wipe is only necessary if you have problems (as usual).
Hotfix 2 [5 October 2011]: Kernel: Bluetooth initialization fix; enabled compatibility with new basebands - you are now free to use any Froyo-based baseband with CyanogenMod. Framework: enhanced dual-touch compatibility (enabling/disabling dual-touch will now change the touchscreen permissions to the proper type). If you're using dual-touch, please re-enable via madconfig after installing this update.
Hotfix 1 [5 October 2011]: Kernel: kernel source re-patched from vanilla to avoid unnecessary/unstable patches; fixed reboot/reboot to recovery hangs; optimized size of kernel modules to free extra RAM; upgraded to newer FSR drivers from I5500XWJQ3 ROM; reverted to stable version of compcache (ramzswap) driver; removed OuNao's dualtouch driver from kernel, but re-added as an optional kernel module. Framework: added new "madconfig" script to configure swap and dualtouch activation; various small fixes and hacks removed.
35% extra trololo.
Updated CyanogenMod source - Gingerbread version 2.3.7.
Fixed audio routing when headphone/headset is connected. You can now force ringtones to speaker - just remember that you need to change this in Settings -> CyanogenMod Settings -> Sound -> Always play on speaker.
Fixed FM Radio seek (left/right arrows) - thanks to OuNao.
Now includes fake dualtouch driver by default - see OuNao's Fake DualTouch thread for more details.
Now using improved ar6000 wireless-N wifi driver (based on Linux compat-wireless-20110329 ath6kl driver, with Samsung's patches for the G5).
Small tweaks to the new battery driver's voltages.
S2E corruption issues should now be completely solved. If your existing /sd-ext partition is corrupt from previous usage in older ROMs, see post #2 for instructions on how to manually format your partition (this is the only way to clear the bug).
[I5508] Touchscreen driver for I5508 now partially working. The x/y axis orientation is correct, but the accuracy is not good. I will try to fix this in future releases/hotfixes.
v1.4 - 23 September 2011:
Battery stats wipe?: You must wipe your battery stats in ClockworkMod for this release, since we are using a new kernel battery driver.
Data wipe?: A regular data-wipe is only necessary if you have problems (as usual).
Hotfix 1 [24 September 2011]: Fixed wifi tethering (reverted to v5 supplicant - should not reduce wireless quality as we are still using the newer WEXT driver); fixed stock FM radio; improved FM radio volume code (thanks to OuNao); improved FM audio quality (reduced hiss sound).
Updated CyanogenMod source.
Deodexed ROM: you can now install the full Google Apps package if you desire. Keep in mind that your first boot after upgrade/fresh install will be slower compared to previous versions, but regular boots will continue to be fast.
Patch to prevent S2E from applying bad filesystem tweaks (won't interfere if you don't use S2E).
Linked /cache/download -> /data/download by default (so all users can download large apps from Market, even if not using an app2sd method).
Kernel: Updated battery driver (based on tass_battery.c 2.6.35 kernel driver) - this should reduce battery drain and prevent the phone from staying stuck on 99% battery for extended periods. Note: your battery stats will be erratic for one or two charging cycles - make sure to wipe your battery stats to help this process.
Wireless: new driver with Wireless-N capability & better signal (based on Atheros source from Samsung I5508, with patches from 2.6.35 kernel).
Updated to wpa_supplicant v6 (awext -> wext driver) & reverted to CM7 dhcpcd. This restores wireless signals to Froyo levels.
Kernel: Updated fsa9280 USB switch driver (from 2.6.35 source).
Kernel: change default TCP congestion control method to "veno" - should improve wireless reliability, especially if there is wireless congestion in your area. It can also improve wireless throughput under normal wireless conditions.
Enabled hardware-accelerated 2D rendering (note: this feature wasn't working properly in the previous test hotfixes - it's working now, and there is no graphical corruption).
Various small bugfixes.
v1.3 - 10 September 2011:
Data wipe?: only if you have problems.
Updated CyanogenMod source.
Hotfix 2 [18 September 2011]: Boot: removed custom lowmemorykiller tweaks; kernel: various updates (smartassV2, TinyRCU, Simple and V(R) IO schedulers), bugfixes and optimizations, changed default scheduler to Simple IO; libaudio: code cleanup and reduced overall FM volume; Framework: enabled hardware-accelerated 2D rendering.
Hotfix 1 [10 September 2011]: Fixed volume controls on stock FM app (thanks again to OuNao and Mike).
Stock FM Radio app now working! Huge thanks to mikereidis and OuNao for the assistance. Note: the volume will be stuck at 100% in the stock app, so take care not to blow out your speakers (will be addressed in a later hotfix). Alternatively, you can use Mike's excellent Spirit FM application which has working volume controls (as well as many other features not present in CyanogenMod's stock FM app). See this thread and Mike's thread on XDA. Be sure to show your appreciation for Mike's work by purchasing the unlock key for his app.
Boot: small fix to /dev/log/* permissions (was causing log errors).
Graphical tweak to improve GUI performance.
Source Code:
Kernel: https://github.com/psyke83/kernel_samsung_europa
Device: https://github.com/psyke83/android_device_samsung_galaxy5
Known issues (any assistance on the following items is welcome)
The FM app will make a loud "pop" noise on first start after Bluetooth activation.
FM audio requires Bluetooth to be activated. This is how the CM7 FM app works, so please don't ask me to "fix" something that is not broken. Alternatively, you can purchase the Spirit FM app which can activate the FM radio without the need to fully enable the Bluetooth stack.
The Camera app does not properly save "zoomed" images at the highest resolution (WXGA). Note: the zoom function would only apply cropping to the image, as our camera does not have hardware zoom capability.
Rebooting into recovery can cause the phone to freeze sometimes. This seems to be a bootloader bug, so it's not something I can fix. To minimize the issue, make sure to remove the USB cable each time you want to reboot to recovery, as it reduces the chance of the bug occurring. If your phone gets stuck, use the hard reset key combination (volume up + power on for 10 seconds).
Some SIM cards seem to be incompatible with CyanogenMod. Please provide a radio logcat to help diagnose these problems.
Kies will not work properly on CyanogenMod. This is not a bug - it's a feature
Battery drains. If you don't use mobiledata at all, using the Use only 2G networks option in the Mobile network settings will significantly improve your battery life. If you use mobiledata, I recommended that you make use of the mobiledata 2G/3G switch. This downgrades the cellular network to 2G when you turn off mobile data, thus allowing battery savings without forcing you to use the slower EDGE mobiledata speed.
Erratic compass. Recent releases are using OuNao's g5sensord daemon. Its behaviour is not completely accurate yet, so if you wish to revert to the proprietary memsicd daemon, run these commands:
Code:
adb remount
adb shell mv /system/bin/g5sensord /system/bin/g5sensord.old
adb shell cp /system/bin/memsicd /system/bin/g5sensord
How to use madconfig:
The below text is the exact output shown when you run madconfig:
Code:
Code: [Select]
Usage: madconfig [option]
Options:
* dton - enable dual-touch
* dtoff - disable dual-touch
* ksmon - enable Kernel Samepage Merging (KSM)
* ksmoff - disable Kernel Samepage Merging (KSM)
* odexon - enable automatic ROM re-odexing
* odexoff - disable automatic ROM re-odexing
* swapon - enable swap
* swapoff - disable swap
In order to use madconfig from the Terminal app, make sure to switch to superuser by executing su before running madconfig.
A few notes on some of the above options:
The ksmon option will activate a kernel driver that allows the dalvik interpreter to share memory between processes when possible (via Kernel Samepage Merging). This dalvik interpreter feature has been backported from ICS, and is not enabled by default due to the possibility of causing problems or battery drain.
The odexon option will activate automatic ROM odexing. This will move the dalvik cache for system apps/components to the /system partition, which should free about ~32MB from your /data partition. Once activated, this option will automatically re-odex your ROM when you update to a later release of my ROM (not an official build from the CyanogenMod server, or any other builds). I don't recommend using this option if you already use an app2sd method that moves your dalvik cache to the SD card.
Audio attenuation:
There are now three system properties available to control audio attenuation:
Code:
persist.sys.speaker-attn - speaker
persist.sys.headset-attn - headset
persist.sys.fm-attn - FM audio (speaker & headset)
Example usage - set 6dB attenuation on speaker:
Code:
su
setprop persist.sys.speaker-attn 6
Technical details:
Kernel 2.6.32:
CPU & AHB overclock supported up to 768Mhz, but a safe frequency range (245-604Mhz) is used by default for safety/stability reasons
Backported KGSL drivers from 2.6.35 kernel, so we can use the newer Adreno200 libraries that support OpenGL ES 2.0 (faster 3D).
Built-in support for CIFS, TUN, compcache (ramzswap)
Added extra CPU schedulers: interactiveX, smartassV2 (default)
Added extra IO schedulers: Simple IO scheduler 0.2
Updated Android staging, pmem drivers from 2.6.35 kernel
Patches to improve CyanogenMod compatibility (e.g. USB tethering)
Various other stability & performance patches.
Before you ask...
I have no interest or intention to further "mod" the ROM with any kind of hacks or customizations (like custom apps, themes, Swype, etc.). My only aim is to have a 100% stable port of Cyanogen code. Any such requests will be ignored.
Reporting bugs
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:
The version of the ROM you are using (to confirm that you have the latest release)
Report any customizations you have made to the ROM (themes, system apps, etc.)
Describe the problem clearly, including steps on how I can reproduce the issue.
Provide a logs from your system taken just after the issue has occurred. I usually need two logs - dmesg and logcat, but if it is a telephony problem, a radio logcat may also be needed.
Code:
Logcat: adb shell logcat -d >c:\logcat.txt
Radio logcat: adb shell logcat -b radio -d >c:\radio-logcat.txt
Dmesg: adb shell dmesg >c:\dmesg.txt
If I ask you to re-test the issue after a data-wipe, do the following: reboot into ClockworkMod, perform a full backup, then data-wipe, reboot and retest the issue, giving a new log if necessary. You can then reboot into ClockworkMod and restore your data backup.
Alternate download location: Using the GooManager application to download & install my ROMs is recommended. If you want to download via the PC, however, you can use this link.
Reserved for future use #2.
guyz the cards unmounts n mounts although I haven't taken it out and also I can't decrease the call sound when on Samsung earphone. And there's a notification dat my card has been removed unexpectedly. plz fix it!!! and great work from you guyz!!!
i have the same card problem. the mod runs great, i don't want to downgrade. please fix it soon
alifie said:
i have the same card problem. the mod runs great, i don't want to downgrade. please fix it soon
Click to expand...
Click to collapse
u wil find v7 in MAD forum. As I m new I can't post a link. go to the forum and read the installation process carefully b4 flashin ROM. I m usin v7 n the card problem has been solved n battery lasts longer as well.
great, thanks
welcme man!!! m on twitter as well. feel free to ask 4 any kind of Galaxy 5 related question. my twitter username: coolabhinesh .
So far 0.7+update5 has been really stable for me, best of the series so far. 0.6 was a nightmare (hangs while idle, ran very hot, battery life extremely short, sd card disappearing, etc.).
yup 0.7 is very stable
Version 0.8 hotfix 3 is out and it's not posted here how come?
Yes it is relesed..
You can find the new update in this blog
galaxy-5-updates.blogspot
update-cm-7.1.0-RC1-MADTEAM-v0.8-signed
v0.8 works great
Hi all,
Just wanted to know if u can share bugs, issues on this builds, what may no work, for now....
smilewithakash said:
You can find the new update in this blog
galaxy-5-updates.blogspot
update-cm-7.1.0-RC1-MADTEAM-v0.8-signed
Click to expand...
Click to collapse
Instead of going to that phony site, why don't you go to the official MadTeam site?
http://www.madteam.co/forum
Sorry guys, I neglected the XDA topics for a while because my post on the MadTeam forum (where the development happens) had lots of incompatible BBCode formatting due to a forum software upgrade. It's fixed now, and I'll keep my topics updated here on XDA more frequently.
The latest version (0.9hotfix1) is highly recommended .
P.S. Please don't download my releases from unknown sources (e.g.: smilewithakash) - only use the links I provide.
Yeah, 0.9+hotfix1 is insanely fast. On a screen that size scrolling feels subjectively as fast as my Galaxy S II.
Still having issues with BT though. I can pair with my other phones, but on the I5503 side the other phones don't show as online, even though I can see the I5503 fine from the other direction and send files to it no problem.
subpsyke said:
It's fixed now, and I'll keep my topics updated here on XDA more frequently.
Click to expand...
Click to collapse
Great !
Someone has asked me if I can get my FM app running on your port. I've looked at your libaudio code and see the analog FM audio enabling code isn't there yet.
Do you have any idea if or when that might be done ?
Thanks !
mikereidis said:
Great !
Someone has asked me if I can get my FM app running on your port. I've looked at your libaudio code and see the analog FM audio enabling code isn't there yet.
Do you have any idea if or when that might be done ?
Thanks !
Click to expand...
Click to collapse
Hey, I'd be happy to add the code, if you can give me a little advice.
My phone is using the regular msm7k qdsp5 libaudio code (the same as e.g. Commtiva Z71), with some custom patches for the microphone/latency. I'm not sure what routing code needs to be added?
I've looked as some other ports' libaudio such as the Blade ZTE - they have code for si470x radio chips, but the Galaxy 5's FM radio uses the BCM2049B0 chip.
I've checked the strings of the proprietary "btld" daemon from my official ROM and all the I2C calls seem to match the BCM432X calls that you can see in CyanogenMod's broadcom radio code. My port is compiled to try and use this same Broadcom FM radio code, but it doesn't seem to work.
Source: https://github.com/psyke83/android_device_samsung_galaxy5
Hi, subpsyke!
Maybe you know me as OuNao on MadTeam forum...
The spirit FM radio app can use de hci interface of the bcm2049 driver to tune radio, but can´t route the analog input to the sound driver.
here h**ps://github.com/mik9/android_device_lge_thunderg/tree/gingerbread/libaudio you can get a modified version of libaudio com FM routing...
Maybe this solves the problem...
Regards.
Hi,
I wonder why Jide hasn't included BlueZ stack as default - it supports much more devices and is more stable. Whats more weird - it is included in official Android-x86 builds, so why isn't it in Remix?
I tested my Asus T100 with Remix Phoenix and Android-x86 and only Android-x86 builds let me use Bluetooth - they also handle sleep state and sound better.
Please add BlueZ bluetooth stack
@RemixOS_Cameron @RemixOS_Jason @RemixOS_Joshua please answer my question.
Thanks,
Karol
@Ventricle - I just talked to our PM and he's told me that we have included BlueZ Bluetooth because Remix OS for PC is based on Android-x86. If your Bluetooth doesn't work with Remix OS, does it work with Android-x86? Please let me know as it'll help our PM troubleshoot your issue. Thanks!
@RemixOS_Jason thanks for the reply.
I thought you didn't include it because BlueZ's basic commands don't work; like hci or hciconfig.
And please read my whole post - I said BT works fine on Android-x86 builds (and do do hci or hciconfig commands).
Remix and Android-x86 init.sh files are pretty much the same, but the bluetooth part operates in many cases on BlueZ commands which simply don't work on Remix. That is why I think you didn't include it - or you devs didn't merge the repos correctly or they based Remix off old Android-x86 builds which don't use BlueZ.
@Ventricle - My apologies for not fully understanding your point the first time. I'll pass your comment along to our PM and give you feedback asap. Thanks!
Hi,
I'm trying to figure out if the hardware for my oneplus X onyx supports ant+
The specs I'm getting is SoC Qualcomm msm8974 (pro) aa
The "ANT Tester" says:
ANT Capable: YES
Built in ant YES
USB OTG YES
ANT USB Service YES
ANT support version info:
Built in firmware: AVN1.01B04
ANT HAL: 4.0.0
ANT Radio service: 4.14.0
ANT USB service: 1.4.0
ANT+ plugins: 3.6.0
I'm running Lineage OS 14.1, android 7.1.1 nightly 2017 march 23
Is this hardware capable of ANT+ ?
I'm not picking up the device I'm trying to connect to.
oneplus X onyx with LineageOS 14.1 supports ant+
I'm posting this as info to help others.
After putting fresh batteries in my ant+ sender, I was able to connect to my
oneplus X onyx with LineageOS 14.1 supports ant+
i have gt-i9301i running resurrection remix 5.1.1 .currently my kernel doesnt have usb hid emulation support to run badusb type attacks .
i found pelya's keyboard app.but my device dont have prebuilt kernel to flash and use hid emulation.but he has a kernel patch in github repo to add support for more devices.
question is how can i apply patch to my current kernel.do i need source code of kernel and recompile it or backup of my kernel and then patch it.if you know how to apply this patch please teach me i need it .
This is LineageOS 17.1, which is based on Android 10, for the WiFi-only variant of the Samsung Galaxy Tab A 10.1" (2016), codenamed gtaxlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
I started these builds because the LineageOS builds from @Valera1978 had 2 particular significant bugs in them that were always being mentioned in posts in that thread: display backlight brightness not changeable from full brightness and the touchscreen appearing to not respond after putting the tablet to sleep. Those bugs had existed for quite a long time. @followmsi has some changes in his 17.1 device tree that fixed those 2 bugs.
These builds really became a continuation of Valera's builds after he unfortunately discontinued work on this device due to an (understandable) lack of interest, with many improvements and additional features.
I've now discontinued these 17.1 builds.
I've long ago moved onto LineageOS 18.1 and 19.1.
Very important note for those upgrading from the releases from 20210523 and 20210413 in this post: https://forum.xda-developers.com/t/lineageos-17-1-for-sm-t580-gtaxlwifi.4059571/post-85106105
Note: I've never had any builds for the LTE variant. However, builds for the WiFi-only variant boot and work on the LTE variant, only without mobile networking (of course), GPS and vibration, so since I've allowed installation on the LTE variant in the last several builds, you can try to use my builds on it if you can go without any of that functionality.
Downloads:
Latest build from 20211116 (with security patch level 20211105):
https://drive.google.com/file/d/14ZCYYcT5b6E9zWiFNgwUP3Kxlvf-dyVn
Folder for these builds (which includes text files with MD5 and SHA256 checksums for the final build, and another folder within it containing some previous builds): https://drive.google.com/open?id=1UiUlSbfj3agDvt-4f_YLIS0Xyuz5RtFC
Changelog:
Final release for 20211116:
Latest updates from LineageOS, including the 20211105 Android security updates.
The WiFi driver has been switched from being a kernel module to being built into the kernel. This may improve reliability for enabling and disabling WiFi and the WiFi hotspot very slightly.
The rewrite of the sepolicy containing all of the SELinux rules that I did for 18.1 has been ported over to 17.1, and so it's now of much better quality.
The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed.
The ZRAM size has been increased to 768MiB.
The BSP sources have been redone to closely match what has been done with the new exynos7880-specific part of Lineage's BSP sources, and with that, there are now more exynos7870-specific changes to the open source gralloc that is in use.
Some miscellaneous cleanups have been done.
The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
The system image size has been increased from 3072000000 bytes to 3145728000 bytes, which is the size of the system partition on Korean and Chinese variant T580s and T585s, and the smallest system partition size out of all T580s and T585s.
Some proprietary blobs have been updated as follows:
WiFi and Bluetooth firmwares from Samsung's T390XXS9CUG1 firmware
libexynoscamera3.so library from Samsung's P580ZSS1CTI1 stock firmware - This improves the situation with the issues with stretched/squashed camera previews for images and stretching/squashing in videos at some resolutions
MFC (Multi-Format Codec) firmware from Samsung's A305FDDU6CUI3 firmware
sensors.universal7870.so library from Samsung's P580ZSS1CTI1 stock firmware
As the oldest proprietary blobs are now as in Samsung's P580ZSS1CTI1 stock firmware (with a few exceptions), the vendor security patch level has been increased to 2020-09-01, which is the security patch level that firmware has.
The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
Configuration files for media codecs and profiles have been updated from Samsung's T580XXS5CTK1 stock firmware.
There are many (final) updates from the (unfortunately now deprecated so no longer updated) 3.18 Android common kernel, many updates from Linux 4.4, and some updates from a few of Samsung's newer kernel sources to the kernel, and also some other various changes.
A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel sources that specifically fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
Some unnecessary drivers have been disabled in the kernel.
The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
Previous releases:
Release for 20210530:
Latest updates from LineageOS.
File-based encryption has been disabled after I left it enabled by mistake after testing FBE before moving onto LineageOS 18.1.
Release for 20210523:
Latest updates from LineageOS, including the 20210505 Android security updates.
Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf (same as branch lineage-17.1-caf).
The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
Release for 20210413:
Latest updates from LineageOS, including the 20210405 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Release for 20210313:
Latest updates from LineageOS, including the 20210305 Android security updates.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, many changes to the rcu, locking and btrfs code from 4.4, and a few changes from Samsung's M105GDXU6CUA1 kernel to the kernel.
The exynos part of the BSP has a few changes from Lineage's 18.1 branch for HWC and memtrack.
Release for 20210207:
Latest updates from LineageOS, including the 20210205 Android security updates.
SELinux denials that caused the torch feature to not work have been addressed.
The issue where videos that are recorded have a duration that is lengthened by the time spent in deep sleep has been worked around - It looks like Samsung did something wrong in the camera HALs for Exynos 7870 devices.
There are some more updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, and a few changes from Samsung's M105GDXU6CTL3 kernel.
Release for 20210116:
Latest updates from LineageOS, including the 20210105 Android security updates.
The custom camera provider HAL has been removed, and the camera provider HAL has been binderized - this fixes camera glitches when there is motion.
Quota support has been enabled on userdata, so that storage usage statistics can be gotten more quickly.
The Widevine DRM blobs from the Pixel 3 XL's last Android 10 firmware are now used.
The MFC (Multi Format Codec) firmware has been updated from Samsung's M105FDDU3CTK3 firmware, and the camera.vendor.universal7870.so library has been updated from Samsung's latest stock firmware (version T580XXS5CTK1).
There are some more updates from Linux v4.4 and the 3.18 Android common kernel to the kernel.
Release for 20201223:
Latest updates from LineageOS.
Address hal_graphics_composer_default SELinux denials on video_device - fixes issues with video playback with SELinux set to enforcing. (Thanks to @Kostareka for providing logs with the SELinux denials)
Release for 20201221:
Latest updates from LineageOS, including the 20201205 Android security updates.
I've prepared new BSP sources, based on Lineage's SLSI BSP sources, and the BSP libraries are now built from those sources. (Thanks to @Valera1978 for providing his old BSP sources! Without them, this wouldn't have been possible.)
Samsung's proprietary audio libraries, adapted by @Valera1978, are now used, to workaround an issue where audio will be outputted to both the 3.5mm audio jack and the speakers quietly when something is connected to the audio jack.
The build fingerprint has been changed to an older Android 8.1 fingerprint for the Google Pixel C. (For information on why we can't use the fingerprint from the stock firmware, see: https://github.com/TALUAtGitHub/android_device_samsung_gtaxlwifi/issues/1 )
Installation on the LTE variant (SM-T585, codenamed gtaxllte) is now allowed - apparently, builds for the WiFi-only variant boot and work on the LTE variant, only with no mobile networking (of course) and GPS.
There are a few minor cleanups.
Version 2 of the AOSP bluetooth audio HAL has been enabled.
FIFO UI scheduling has been enabled.
The camera libraries have been updated from Samsung's latest stock firmware, version T580XXS5CTK1.
There are a few other miscellaneous improvements.
There are some updates to the kernel from the Android 3.18 common kernel and Linux v4.4, and there are updates to some of the drivers from Samsung's M105GDXU5CTI3 kernel.
Release for 20201121:
Latest updates from LineageOS, including the 20201105 Android security updates.
The sepolicy has been improved - many unnecessary SELinux rules have been removed and a few SELinux denials have been addressed.
The init.power.rc script is now actually used to set some parameters for the interactive CPU governor to make it less aggressive.
The GNSS and sensors HAL are now compiled from source in the device tree with necessary modifications. (Thanks to @followmsi for some very useful information regarding this!)
As many vendor blobs as possible have been updated from Samsung's T580XXS5CTD1 and A520FXXUGCTI9 stock firmwares, the gpsd shim has been removed as it's no longer necessary after updating gpsd from T580XXS5CTD1 and a few unused vendor blobs have also been removed.
cbd/cpboot-daemon has been removed, because it, along with the modem_v1 driver in the kernel, no longer works with the latest bootloader and spams the kernel log with error messages, I have very little idea of what it does for the WiFi-only variant and it's unnecessary.
Made a few other miscellaneous improvements.
Many more updates to the kernel from Linux v4.4 and the 3.18 Android common kernel, some miscellaneous improvements and many changes to the f2fs filesystem driver from newer Android common kernels and mainline Linux.
The kernel is now compiled using the clang compiler after having applied the many necessary changes to it to do so.
Release for 20201022:
Latest updates from LineageOS, including the 20201005 Android security updates.
Enable config_setColorTransformAccelerated - LiveDisplay colour calibration and reading mode is now available. (Thanks to @followmsi for finding this fix.)
Add FlipFlap for flip covers. (Note that FlipFlap only works if the timeouts in Settings -> Connected devices -> Connection preferences -> Smart cover are set to 'immediately')
Fix a typo in the power profile.
More updates to the kernel from Linux v4.4 and the 3.18 Android common kernel.
Apply/backport some changes to zram and the lz4 compression algorithm from mainline Linux for faster compression and decompression, and add a backport of the zstd compression algorithm from the 4.9 Android common kernel which can be used as the compression algorithm for zram (lz4 is still the default compression algorithm).
Release for 20200915:
Latest updates from LineageOS, including the 20200905 Android security updates.
Increase microphone gains.
Many more updates from Linux v4.4 and android-3.18 and a few improvements to the kernel.
Release for 20200821:
Latest updates from LineageOS.
A few more updates from Linux v4.4 and android-3.18 and improvements to the kernel.
Revert 2 changes to the kernel related to hotplugging - should fix an issue where the device doesn't wake up after a while of deep sleeping in certain cases, and a hard reset is needed.
Release for 20200814:
Latest updates from LineageOS, including the 20200805 Android security updates.
Update the Mali graphics blob to r28p0 from r22p0.
Make a few changes for GPS that fix Assisted GPS, and switch to different XTRA servers with HTTPS.
Fix OpenCL.
Symlink libGLES_mali.so to libOpenCL.so, libOpenCL.so.1 and libOpenCL.so.1.1 instead of copying - saves a significant amount of space in /system and makes the installation zip slightly smaller.
Change media volume control to be in 25 steps rather than 15 steps.
More updates from Linux v4.4 and android-3.18 to the kernel and some improvements.
Release for 20200711:
Latest updates from LineageOS.
Android security updates from 20200705, manually applied to skip the wait for them to be merged. ('repopick -t android-10.0.0_r40')
Disable window rounded corner animations.
Reduce ZRAM size to 512MB.
Enable debug.sf.disable_backpressure.
A few more updates to the kernel from Linux v4.4 and android-3.18.
Port over/import zsmalloc, zram, zswap, zbud and zpool from Linux v4.4.
Fix the issues with hanging/freezing that were present in the previous release.
Release for 20200703:
Latest updates from LineageOS.
Enable support for using USB for MIDI.
Fix/workaround issues with USB tethering.
Remove sswap and use ZRAM.
Latest update from @Valera1978 - "update audio_policy_configuration.xml from SM-A600FN q stock"
Many more updates to the kernel from v4.4, android-3.18 and a few from v3.16.
Disable the Exynos hotplug governor again. (in the kernel)
Release for 20200608:
Latest updates from LineageOS including the 20200605 Android security updates.
Use userspace lmkd.
Enable Always On Display. (Thanks to @followmsi)
Address a few more SELinux denials.
power_profile: change names as per pie naming changes.
Switch to [email protected]g. (Thanks to @followmsi)
Fix freeform window moving/resizing doesn't work (In my new fork of LineageOS' android_frameworks_base repository).
Add back support for Miracast using the changes from https://review.lineageos.org/q/topic:%22ten-aosp-wfd%22 (In my new fork of LineageOS' android_frameworks_av repository).
More updates to the kernel, including many updates from Linux v4.4 and v3.16 and general updates. There are also improvements to downstream drivers.
Release for 20200512:
Latest updates from LineageOS including the 20200505 Android security updates.
Address more SELinux denials.
Remove the ro.enable_boot_charger_mode property and revert "gtaxl: workaround for offline charging".
Remove some useless services for non-existent binaries in init files.
Hide sRGB toggle in developer options.
More updates to the kernel, including many updates from Linux 4.4 and to the kernel-based wireguard implementation.
Release for 20200411:
Latest updates from LineageOS including the 20200405 Android security updates.
Update the cpu.speeds array in the power profile for 1.69GHz, 449MHz and 343MHz frequencies.
Make the power profile aware of the big.LITTLE cluster.
Address more SELinux denials and remove duplicate rules.
Use an up-to-date Samsung hardware repository based on LineageOS' repository, and make changes to the device tree for it. ((Thanks to @followmsi for changing the sepolicy to accommodate for modem/macloader having been moved to /vendor and mentioning that the Exynos hidl power HAL has to be used after the old power HAL was removed)
Enable secure ADB and set persist.sys.usb.config to none.
Use pool.ntp.org for the NTP servers.
ramdisk: cleanup the init files and fstab for readability.
ramdisk: init.samsungexynos7870.rc: only start gpsd after booting - fixes GPS when encrypted.
More updates to the kernel, including many updates from Linux 4.4, general updates (such as updates to the wireguard kernel module) and fixes.
Use sdfat for exFAT support.
Add toggle for disabling newly added USB devices.
Release for 20200309:
Latest updates including 20200305 security patches
Upgrade android.hardware.keymaster to 4.0.
lineage-gtaxlwifi_defconfig: disable CRYPTO_FIPS to get encryption partially working.
sdfat: update to version 2.3.0.
Update the BFQ IO scheduler to v8r12 using a port.
Release for 20200303:
wireless: add back Samsung's 'temporary' workaround due to qcacld-2.0 page allocation errors. Looks like this is actually necessary. Works around issues with WiFi not being possible to be enabled after some time again due to page allocation failures that still exist.
Revert duplicate "signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO". We already had this commit as in Linux v3.18, the content of this reverted commit are useless.
Release for 20200301:
Fix a few SELinux denials. (including app_zygote denials, sepolicy in post 5 no longer needed for this build at all and also shouldn't be used anymore as more denials beyond just the app_zygote denials have been fixed)
Release for 20200229:
Initial release.
Known issues and workarounds (if any):
Issue 1: adoptable storage is reported to not work correctly.
Somewhat of a workaround to issue 1: format and use your micro SD card with the exFAT filesystem.
Issue 2: Camera previews for images to be taken at resolutions with aspect ratios other than 16:9 using the rear camera are squashed from 16:9 (while final saved images at any resolution are unaffected by any squashing), and videos taken at some resolutions are affected by similar issues with squashing in previews, and, in a smaller set of resolutions, also in final saved video files. (Note that these issues don't affect the front-facing camera)
Somewhat of a workaround to issue 2: Use resolutions at which there are no issues with squashing from 16:9.
Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.
To report issues, get a log from logcat and dmesg. If you are unsure of how to get both, there is good documentation out there for how to do so.
Sources:
A manifest containing all of the necessary repositories to make a build is in this repository on branch lineage-17.1: https://github.com/TALUAtGitHub/gtaxlwifi-manifests
Thanks to:
@Valera1978 - for all of the previous work for these devices, and for providing his old BSP sources without which the previously used open BSP sources wouldn't have been possible.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
LineageOS - for the Android distribution itself.
...and everyone else who's worked on anything that is in use.
No build for sm-t585?
Echo_2000 said:
No build for sm-t585?
Click to expand...
Click to collapse
Unfortunately not, as I mentioned in the original post.
Sorry.
Edit on 2020/12/22: for anyone who is reading this post and has missed my new note in the original post, installation is now allowed on the LTE variant in my latest build, so you can try my build on it.
TALUAtXDA said:
Unfortunately not. As I mentioned in the original post:
Sorry.
Click to expand...
Click to collapse
Too bad, bad no problem.
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Glenn2 said:
I installed this, mostly seemed to work OK, but although I could install Chrome from Play Store it would simply disappear (no error) every time I opened it. Tried Chrome Beta instead and same issue.
I don't know if Gapps related. I used Bit gapps for what it's worth.
Gone back to old build.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
The issue was caused by SELinux denials. I've fixed these denials in this commit: https://github.com/TALUAtGitHub/and...mmit/0ec43a448795230a3d2d8576cd93c5b156468e21
I was able to get the SELinux denials you were experiencing as you told me how you encountered them. Attached is a zip archive named 'sepolicy_and_precompiled_sepolicy.zip' containing 2 files: 'sepolicy' and 'precompiled_sepolicy'. This is a new sepolicy containing the rules to fix the denials. If you decide to use my builds again, extract the zip archive and copy the 'sepolicy' file to /system/ and 'precompiled_sepolicy' file to /system/system/vendor/etc/selinux/ in TWRP with system mounted. You may want to run SELinux as permissive for now, though keep in mind that this will ignore denials. To set SELinux to permissive, run:
Code:
setenforce 0
I never caught these denials as I don't use Chrome, and use Bromite web browser which doesn't seem to trigger these denials. I'll probably upload a new build tomorrow containing a sepolicy with the new rules. Also, I've put this in the original post for reporting SELinux denials:
TALUAtXDA said:
There maybe more issues due to SELinux denials. If something doesn't work, test it with SELinux set to permissive:
Code:
setenforce 0
If the issue is no longer reproducible, it's due to SELinux denials. Get logs by running:
Code:
dmesg | grep "avc: denied" > dmesg_selinux_denials
logcat | grep "avc: denied" > logcat_selinux_denials
while SELinux is permissive after doing whatever triggered the denials in a shell and upload the files 'dmesg_selinux_denials' and 'logcat_selinux_denials'. It would also be preferable to report what triggered the denials. In some rare cases, SELinux has to be set to enforcing to get certain denials, which would unfortunately mean that every denied action isn't logged and it takes multiple tries to get every denied action causing issues. Don't report any random denials that don't cause any issues. I won't fix some denials (such as proc_version denials, which should be denied and it causes no real issues) and I'll only fix denials that cause unintended issues.
Click to expand...
Click to collapse
Thanks I will try it again soon.
Did as suggested, seems ok now! Thanks.
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Thanks for building a rom with selinux enforced. I used encryption on 14.1 but it doesn't seem to work here. Some more denials to add, or maybe I need a newer recovery to format data with first?
Jet T said:
Good evening,
God bless you and thank you very much for fixing this beautiful rom.
I have a request and a question.
Request: I am using sm-t580. When I was using stock rom, I was able to cast my screen to my Samsung TV. I am aware that LOS and Pixel have removed this ability. Would you consider please to re-enable "smart cast". I would love to enjoy your ROM on my sm-t580 and be able to cast to Samsung TV.
Question: I am unable to edit build.prop or other system files. I tried to re-mount root but probably doing something wrong. Not very good with this. Could you walk me through how to remount and what do I need to use (what terminal inside your rom). I have root access with Magisk and in twrp used shell terminal with your command "mount -o rw,remount /" without success. Then I downloaded some some terminal app and tried. No use... I get "/dev/block/platform/13540000.dmmmc0/by-name/system" not user moutable in fstab. Thank you.
Click to expand...
Click to collapse
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite.
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
I had another device where encryption didn't work. Turned out to be twrp writing incorrect (encryption?) footer when formatting data partition. But here encryption on 14.1 worked. Maybe encryption changed 14.1 to 17.1 with different footer, or maybe encryption on the los 17.1 base is broken on all devices. Difficult.
TALUAtXDA said:
Hi,
You're welcome, though kudos to followmsi of course.
Smart cast seems to be a Samsung specific, proprietary feature. But we do have the generic casting feature available in Settings -> Connected devices -> Connection preferences -> Cast. Casting to wireless displays can be enabled through the 3 dot menu and then the "Enable wireless display" option and your TV should be detected. However, this doesn't work. A TV either doesn't connect or there's a soft reboot. I also have a Samsung smart TV with which I could test it with. The TV gets detected as "[TV] Samsung", and selecting it makes it say that it's connecting but it either stops trying to connect or it soft reboots and the TV displays an "loading" message that's infinite. I captured a logcat at a time when it soft rebooted:
I found this while searching for "MediaPlayerService: listenForRemoteDisplay is no longer supported!" (this seems to be the main error): https://pastebin.com/s4utSi6c It seems like this issue has been reported before and existed at least a few months (though most certainly more) before my builds. I'll try finding a way to fix this, but my knowledge is unfortunately quite limited at this moment.
To do a mount command like that, you need to be root. To get a root shell, run "su", grant your terminal app root access and then run any commands needed to be run as root in that shell, such as that mount command.
EDIT: found this: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t4006261/post81782081#post81782081 The replies say that you need to go back to Android 8 to use Miracast. I'm not sure if that's true but that's apparently how it is. There's probably nothing that can be done. Since smart cast is proprietary and Samsung specific, you'd only find it in Samsung ROMs. Also found this: https://forum.xda-developers.com/showpost.php?p=81369313&postcount=143 saying that support for Miracast is no longer available in Android 9 and 10.
Click to expand...
Click to collapse
I appreciate your answer!
I have now installed EX Kernel Manager as I had previously purchased it anyway when I (briefly) used the ElementalX kernel on my Pixel 3a.
I can see that we lose half the CPU permanently after the device goes to sleep, as you described, by looking at the dashboard.
Under Tools/User Settings I added a setting for /sys/devices/system/cpu/cpuhotplug/enable with a value of 0 as you suggested (to apply on boot) and this has cured the issue. It explains why I sometimes had smooth and sometimes not so smooth performance on the old rom! Now it's just always smooth.
Interestingly, I could not write to this value once the problem had occurred and the CPU was half disabled. The '0' value would not save, it stayed at '1'. It was not writable - is that a clue to the cause? I had to reboot and put the setting in EXKM before the device had been to sleep. Now it is fine even after reboot.
Thanks.
Thanks for your work and contributions to this device.
Many thanks for your work. Your ROM is working perfectly. No screen freeze.
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Jamess27 said:
Thank you for the rom!
I flashed it because it should have signature spoofing, but actually microG self-check doesn't tick signature spoofing permission and correct signature for play services and play store. Can anyone help me?
Click to expand...
Click to collapse
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
TALUAtXDA said:
Hi,
It should be possible to select the "System grants signature spoofing permission" option in the MicroG self-check menu to get a dialog asking if you'd like to allow signature spoofing. Otherwise, you can grant the signature spoofing permission using a root shell or ADB with these pm commands:
Code:
pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Click to expand...
Click to collapse
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Jamess27 said:
Thanks for the fast response! I got the permission with the dialog in MicroG, but apps still don't find google play services
Click to expand...
Click to collapse
You're welcome. Now, the signature spoofing permission is granted to microG, but from what you describe, it's likely that play store (or fake store) doesn't have the signature spoofing permission. You can check if this is the case by opening the MicroG self-check menu and checking if the "Play Store (Phonesky) has correct signature" item is checked. If play store doesn't have the signature spoofing permission granted, you need to run this one pm command in a root shell or using ADB:
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE