{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.x (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
ROM Downloads
<< Stable >>
20151129 Build: https://www.androidfilehost.com/?fid=24269982087007316
SuperSU Flashable ZIP (needs to be installed separately): https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Previous Releases:
20150816 Build: https://www.androidfilehost.com/?fid=24052804347795005
20150814 Build: https://www.androidfilehost.com/?fi...ww.androidfilehost.com/?fid=24052804347792055
Google Apps (add-on)
https://www.androidfilehost.com/?fid=95916177934548318 <== Avoid to install any Google Apps, but if you really need them this is the recommended package
Installation
3-button-combo = "Volume Up/+" + "Home/Center" + "Power/Lock"
- First time flashing GearCM 11 to your Samsung Wave (or coming from other Android ROMs, including older GearCM releases)?
Download and flash latest available Bada 2.0 for your device (Google will be your best friend in this case)
Download BOOTFILES, Kernel and FOTA for your device
S8500:
BOOTFILES => https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel => https://drive.google.com/file/d/0B-2dpW_lpZCPNWtxVnRVdUVTcVE/view?usp=sharing
FOTA => https://yadi.sk/d/OtpVoaXpfNggE
S8530:
BOOTFILES => https://yadi.sk/d/cBPD41VEbP2od
"start" kernel => https://drive.google.com/file/d/0B-2dpW_lpZCPT0VCS0tINHU5cnc/view?usp=sharing
FOTA => https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader
After Reboot device will automatically boot into recovery
Follow this procedure: Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait until on screen you see "Partitions had been prepared"
Follow this procedure: Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
After Reboot, device will boot again into recovery
Now you can copy GearCM Flashable ZIP & SuperSU into Internal or External Storage using MTP (Internal/External) or using USB Storage (Only External) <= Check if USB Storage/MTP is enabled in "Mount" menu.
Install the ROM from Internal/External Storage (via "Install" menu)
Wait for about 10 minutes until "Reboot System" button is showed
Install SuperSU from Internal/External Storage (via "Install" menu)
Optionally install Google Addon ("Go Back", "Install"....)
Done! You can now reboot the phone to enjoy the rom
- Upgrading from another build of GearCM 11? (not valid if upgrading to 20151129 build)
Reboot into Recovery using 2-button-combo [Volume Up + Power/End]
Do a Nandroid Backup!
Install the ROM from Internal/External Storage (via "Install" menu)
Wait for about 10 minutes until "Reboot System" button is showed
Install SuperSU from Internal/External Storage (via "Install" menu)
Wipe Dalvik & Cache.
Done! You can now reboot the phone to enjoy the rom
Differences from Standard CyanogenMod
ROM & Kernel are compiled using newest sources and improvements
Removed Useless and RAM-Hungry apps such as VoicePlus & CMUpdater
Optimized Dalvik VM for low-ram and uniprocessor devices
Optimized system DBs access (SQL Optimizations)
System & Userdata partitions are using F2FS instead of EXT4 to get maximum performance from NAND Storage
Device Tree and Kernel have been enhanced and corrected in order to obtain maximum performance from our device
SELinux has been disabled to avoid issues
Pre-Odexed to reduce first boot time
Removed TV Out support (RAM-Hungry and hacky)
Many other performance improvements that i don't remember
Known Issues (regarding latest available Stable build)
Please do not report bugs if it is already listen in the list of known issues
Built-in Sound Recorder crashes if File Type is set to WAV (seems CM sources bug)
Bad Call Quality while on 2G (GPRS & EDGE) Networks (probably related to AMR_WB)
Dynamic Switching between 2G (GPRS & EDGE) & 3G (UMTS & HSDPA) doesn't work (it is recommended to use 3G Only mode)
Rarely, some SIM Cards won't be able to register any network
GPS isn't 100% reliable due to experimental implementation
Conference Calls feature doesn't work yet
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband) version:
GearCM version:
GearCM download url:
Google Apps version:
Did you--
wipe data/factory reset:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance Settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Changelog
20151129:
CLEAN INSTALL (first procedure) REQUIRED
Updated CM Sources
Switched to CM12.1 boot animation
Improved Performance here and there
Fixed Dialer issues
Restored some little animations
Reduced RAM Usage
Optimized KSM (still not enabled by default)
Removed useless buttons backlight option
Added GearCMParts to manage mDNIe Screen Options
Switched to ondemand CPU Governor to avoid performance issues
Improved Boot Time
Removed useless notification lights path to Lights HAL (probably cause of memory leaks)
Added Regulatory Info (SAR) to Settings app
Enabled screen dim to save battery
Optimized RAM management for low-ram devices
Restored Themes support
Fixed SetupWizard with Google Apps
"start" kernel: updated to latest version with new GearRecovery base
RECOVERY: switched to new GearRecovery base, newer and with better UI. TWRP Based
KERNEL: added lots of updates to fix memory leaks and minor issues
Previous Releases:
20150816:
Fixed Random Shutdowns when Battery Temperature is too high
Improved Performance & Smoothness
20150814:
Fixed Random Reboots
Improved Performance & Smoothness
Reduced RAM Usage (just a bit)
Disabled KSM by default
Improved Screen-On/Screen-Off latency
20150811:
First Release
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[GearCM][NAND|S85xx][4.4.4] Optimized CyanogenMod 11 for Samsung Wave I/II, ROM for the Samsung Bada OS
Contributors
Alberto96, Volk204, Rebellos
Source Code: https://github.com/GearCM
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 20151129
Stable Release Date: 2015-11-29
Created 2015-08-11
Last Updated 2015-11-30
Reserved
Reserved
Great Job Alberto!
Will try to install on my wave soon)
volk204 said:
Great Job Alberto!
Will try to install on my wave soon)
Click to expand...
Click to collapse
Thank you, it's a pleasure for me that you try my rom
If you find something that needs to be enhanced/fixed, let me know
Great man , testing .......
thank you
thank you man i just install it istead of 5.1
(wave 2 s8530)
setting crash when entering THEMES: theme-pack bootanimation icons font sound-packs
i really hope to get them work in other versions
sound recorder crush when using wav extention
when i choosed wallpaper system restartbut it continue to work normal
apps working fine and very smooth like no other rom (and tried every rom in forum) :good:
as first release it is great can't wait for other releases
ps: i didn't use gapps when i used it went a liiiitlle laggy but not bad
I'm using wave 1 ( gt-s8500)
clean install with no Gapps
-this is maybe be a random bug but when system booted for the first time , i Signal lost and phone rebooted , than shutdown it self ??
nothing when executing
Code:
/proc/last_kmsg.
/system/bin/sh: cat: /proc/last_kmsg: No such file or directory
Click to expand...
Click to collapse
-I took a logcat for this
DIRAR11 said:
sound recorder crush when using wav extention
when i choosed wallpaper system restart but it continue to work normal
Click to expand...
Click to collapse
-i noticed this line in logcat that probably isn't related to the above reported issue
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
-Some error in media scanner , i checked the files ,and they are corrupted on my sd card
E/MediaScannerJNI( 1333): An error occurred while scanning file '/storage/sdcard1/music/11 - Hooverphonic - Jackie Cane.mp3'.
E/MPEG4Extractor( 957): No width or height, assuming worst case 1080p
Click to expand...
Click to collapse
-When installing the ROM i noticed this 2 lines in the log :
mount: failed to mount /dev/lvpool/userdata
/data: device or resource busy
Click to expand...
Click to collapse
is it related to using F2FS , and there is no reason to worry about
- in anycase the ROM is amazing , very fast comparing to Omni 4.4 ;
Thank you :good:
DIRAR11 said:
thank you man i just install it istead of 5.1
(wave 2 s8530)
setting crash when entering THEMES: theme-pack bootanimation icons font sound-packs
i really hope to get them work in other versions
sound recorder crush when using wav extention
when i choosed wallpaper system restartbut it continue to work normal
apps working fine and very smooth like no other rom (and tried every rom in forum) :good:
as first release it is great can't wait for other releases
ps: i didn't use gapps when i used it went a liiiitlle laggy but not bad
Click to expand...
Click to collapse
1) Themes support has been removed.
2) Sound Recorder doesn't work on my Galaxy S4 too with WAV format, so i'm starting to think that it is an app's bug.
3) Working fine here
ice_ice said:
I'm using wave 1 ( gt-s8500)
clean install with no Gapps
-this is maybe be a random bug but when system booted for the first time , i Signal lost and phone rebooted , than shutdown it self ??
nothing when executing
Code:
/proc/last_kmsg.
-I took a logcat for this
-i noticed this line in logcat that probably isn't related to the above reported issue
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
-Some error in media scanner , i checked the files ,and they are corrupted on my sd card
-When installing the ROM i noticed this 2 lines in the log :
is it related to using F2FS , and there is no reason to worry about
- in anycase the ROM is amazing , very fast comparing to Omni 4.4 ;
Thank you :good:
Click to expand...
Click to collapse
1) Uhm...this is interesting. Unfortunately i can't test SIM Card because i only have a secondary Micro SIM.
2) Oops...seems that i forgot to enable last_kmsg support in kernel
3) This error:
Code:
E/audio_a2dp_hw( 957): adev_set_parameters: ERROR: set param called even when stream out is null
is normal. It is a fake error.
4) It's normal, because files are corrupted
5) That's another fake error.
You're welcome
Alberto96 said:
You're welcome
Click to expand...
Click to collapse
No; thank you
I only used this ROM for a couple of hours , but i think it is the best one at the moment .
ice_ice said:
No; thank you
I only used this ROM for a couple of hours , but i think it is the best one at the moment .
Click to expand...
Click to collapse
And new version is coming, probably tomorrow, with more performance and fixes.
Sent from my Nexus 4 using Tapatalk
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
tofifo said:
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
Click to expand...
Click to collapse
It's nice to see someone spamming on XDA, almost every thread on XDA has at least one spammer, so this isn't uncommon to me.
Thank you then, your congratulations are appreciated
Sent from my Nexus 4 using Tapatalk
tofifo said:
This ROM is s h i t, s h i t
With this ROM the phone is turned off at every turn
When an application apk is installed manually or when installed using the google store, to after open application the phone goes off
Not so with a single application, it happens with many applications.
Too many restarts every few minutes.
I am grateful job to any developer, but to make rom full of mistakes failure is better to do nothing.
I lost my time installing and uninstalling your rom
Click to expand...
Click to collapse
Blame your ignorance
"this is a fresh and green teenager comment on youtube . go there for your people , you can understand each others "
Wow! Very nice to see that there are still people willing to dedicate their time to these kind of projects (making a ROM for Samsung Wave is not something that will reach a big audience...).
I have a great respect for you, Alberto96! And also for ice_ice, who keeps giving support for everyone around here (I think he's the only one helping the noobs, such as myself).
I am quite curious to try this ROM, but my question is: is there any chance a SD-ROM version will be released? I am currently using Omni 4.4 from my SD card, which is working fine. I like to keep Bada for emergencies, since many times I found myself traveling somewhere with 2G-only, and in those times Android on Samsung Wave has tons of problems (signal is bad, call quality is bad, etc...). So Bada comes to the rescue.
Anyway, if it's too much trouble porting it to SD-ROM, I might also take a chance with this NAND version, but I just thought I should ask first...
ZephonWave said:
Wow! Very nice to see that there are still people willing to dedicate their time to these kind of projects (making a ROM for Samsung Wave is not something that will reach a big audience...).
I have a great respect for you, Alberto96! And also for ice_ice, who keeps giving support for everyone around here (I think he's the only one helping the noobs, such as myself).
I am quite curious to try this ROM, but my question is: is there any chance a SD-ROM version will be released? I am currently using Omni 4.4 from my SD card, which is working fine. I like to keep Bada for emergencies, since many times I found myself traveling somewhere with 2G-only, and in those times Android on Samsung Wave has tons of problems (signal is bad, call quality is bad, etc...). So Bada comes to the rescue.
Anyway, if it's too much trouble porting it to SD-ROM, I might also take a chance with this NAND version, but I just thought I should ask first...
Click to expand...
Click to collapse
No sorry, I don't have enough time to make two versions.
Sent from my Nexus 4 using Tapatalk
*Mr alberto96 , i tested the ROM with Opengapps . and you may recommend not installing it at the moment . device get short on RAM . and if you just stressed it a little ; apps will crash
I took a logcat while playing with apps and stressing them to crash ,
*i disabled the services not needed in Google play service ;( like fitness and ads ..... ) . more than 150 services that made the wave slow down
*i disabled KSM ; and there is slightly better performance (Less work on CPU )
Here are some interesting line from the Logcat :
-Log has many ANR and APPs not responding
[
Code:
E/ActivityManager( 434): ANR in com.android.systemui
E/ActivityManager( 434): PID: 499
E/ActivityManager( 434): Reason: Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
E/ActivityManager( 434): Load: 14.51 / 9.76 / 5.41
E/ActivityManager( 434): CPU usage from 0ms to 56196ms later:
E/ActivityManager( 434): 9% 2553/com.mxtech.videoplayer.ad: 6.7% user + 2.2% kernel / faults: 6004 minor 198 major
E/ActivityManager( 434): 6.5% 434/system_server: 3.7% user + 2.7% kernel / faults: 6935 minor 183 major
E/ActivityManager( 434): 3.5% 19/ksmd: 0% user + 3.5% kernel
E/ActivityManager( 434): 3.2% 499/com.android.systemui: 2.5% user + 0.7% kernel / faults: 7036 minor 64 major
E/ActivityManager( 434): 2.2% 64/mmcqd/0: 0% user + 2.2% kernel
E/ActivityManager( 434): 1.7% 3031/com.android.vending: 0.7% user + 1% kernel / faults: 3435 minor 132 major
E/ActivityManager( 434): 1.6% 2522/com.google.android.gms: 0.5% user + 1.1% kernel / faults: 4930 minor 382 major
E/ActivityManager( 434): 1.1% 111/rild: 0% user + 1.1% kernel / faults: 25 minor
E/ActivityManager( 434): 0.5% 116/debuggerd: 0.2% user + 0.3% kernel / faults: 1758 minor 213 major
E/ActivityManager( 434): 0.9% 666/com.cyanogenmod.trebuchet: 0.5% user + 0.4% kernel / faults: 2776 minor 33 major
E/ActivityManager( 434): 0.5% 3094/android.process.media: 0.1% user + 0.3% kernel / faults: 2167 minor 71 major
E/ActivityManager( 434): 0.4% 56/irq/121-s5pv210: 0% user + 0.4% kernel
E/ActivityManager( 434): 0.4% 117/surfaceflinger: 0.1% user + 0.3% kernel / faults: 3355 minor 1 major
E/ActivityManager( 434): 0.2% 628/com.android.phone: 0.1% user + 0% kernel / faults: 434 minor 4 major
E/ActivityManager( 434): 0.2% 18/kswapd0: 0% user + 0.2% kernel
E/ActivityManager( 434): 0.1% 6/rcu_kthread: 0% user + 0.1% kernel
E/ActivityManager( 434): 0.1% 15/cfinteractive: 0% user + 0.1% kernel
E/ActivityManager( 434): 0.1% 606/com.google.android.gms.persistent: 0% user + 0% kernel / faults: 447 minor 4 major
E/ActivityManager( 434): 0% 3/ksoftirqd/0: 0% user + 0% kernel
E/ActivityManager( 434): 0% 69/dhd_dpc: 0% user + 0% kernel
E/ActivityManager( 434): 0% 641/com.android.incallui: 0% user + 0% kernel / faults: 332 minor
E/ActivityManager( 434): 0% 770/com.google.process.gapps: 0% user + 0% kernel / faults: 381 minor 4 major
E/ActivityManager( 434): 0% 5/kworker/u:0: 0% user + 0% kernel
E/ActivityManager( 434): 0% 634/com.bel.android.dspmanager: 0% user + 0% kernel / faults: 253 minor
E/ActivityManager( 434): 0% 106/f2fs_gc-254:1: 0% user + 0% kernel
E/ActivityManager( 434): 0% 109/servicemanager: 0% user + 0% kernel / faults: 29 minor
E/ActivityManager( 434): 0% 115/netd: 0% user + 0% kernel / faults: 95 minor
E/ActivityManager( 434): 0% 123/sdcard: 0% user + 0% kernel / faults: 17 minor
E/ActivityManager( 434): 0% 407/flush-254:1: 0% user + 0% kernel
E/ActivityManager( 434): 0% 579/sdcard: 0% user + 0% kernel / faults: 21 minor
E/ActivityManager( 434): 0% 586/com.android.inputmethod.latin: 0% user + 0% kernel / faults: 351 minor 3 major
E/ActivityManager( 434): 100% TOTAL: 15% user + 16% kernel + 65% iowait + 2.3% softirq
Code:
I/ActivityManager( 434): MemInfo: 12952 kB slab, 568 kB shmem, 32 kB buffers, 71792 kB cached, 2616 kB free
I/WindowState( 434): WIN DEATH: Window{421e9798 u0 Keyguard}
I/ActivityManager( 434): Process com.android.systemui (pid 499) has died.
Have a nice day
That's why I say "avoid to install Google apps" 283MB of Total RAM are just enough to run Android.
Sent from my Nexus 4 using Tapatalk
Could you give "call forwarding" and " caller ID" a look . the two were working in CM9 and the earlier builds of CM10 . i don't know what did change
But since then ; Dialer.apk crash when ever you try to access the two in dialer setting
Gapps on 283MB/RAM are for with no question to avoid , even in the days of cm9 when Gapps had less services ;
Kind regards
Thank you so much for this ROM, Alberto! I've been hoping for someone to go back to 4.4 instead of focusing on new features with 5.1 when we dont have enough ram for that and here you are releasing this. Im downloading and installing atm, will report back on the performance.
UPDATE: It seems to run smoothly however, like some people have previously reported, every now and then the phone freezes and restarts randomly as well as when changing the wallpaper. The network works fine (after a few restarts) and we'll see how it performs with use. Also, i keep losing my network connecting after a few minutes of uptime and i have to restart the phone every time that happens.
Related
Thanks to @rdlejo for this wonderful app for workaround the problem some of us are having with the wifi to data connection in some roms. Ive tested it on several ROMs and there is no danger in trying new ones. You will be asked for root acces.
I leave the two links for the compiled apk and the source code:
APP (last v1.32 24 May 2015) : http://www.enpalermo.com/Gsm3gCheck.apk
Sources : http://www.enpalermo.com/Gsm3gCheckSrc.zip
App log is in : /sdcard
Changelog:
24 May 2015 :
-Less wakelocks
-Less time for 3g operation check (8 to 7 Minutes)
-Forced refresh period 45mins to 7hs
BTW. Here is the link to GITHUB so you can see its a development: https://github.com/rdlejo/Gsm3gCheck
Credits: @rdlejo
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.*/
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
What's working
Mostly everything except for those mentioned in Not working list.
What's not working
Video Recording.
Mobile data on one of the SIMs when using dual SIM.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation Instructions
If you are flashing from stock :
You need to have an SELinux enabled recovery. Use TWRP or CWM 6.0.5.1. Use the CWM which is in the downloads section below.
Download the CM11 zip and put in phone.
Reboot to recovery.
Wipe data/factory reset.
Wipe cache.
Install the CM11 zip.
(Optional)Flash Gapps (find it in downloads section).
Reboot.
If you are upgrading from CM11 (Assuming you have a SELinux enabled recovery):
Download the CM11 zip and put it in phone.
Reboot to recovery.
Simply flash the CM11, no need to wipe anything.
Reboot.
Todo
If you want to use dual SIM, open terminal emulator and execute following:
Code:
su
setprop persist.radio.multisim.config dsds
reboot
Troubleshooting
Visit this thread and post your queries there, and you may well be replied.
Download
CyanogenMod 11 - Beta 5
Gapps
Source
Device Tree
Kernel Source
Vendor Blobs
Patches (Copy Paste files)
Credits
@Unjustified Dev and @Doc_cheilvenerdi.org - For starting the CM project, initial tress and stuff.
@psych.half - For his fixes in CM10.1, ideas and ofcourse for his kernel.
@Dreamstar - For his SELinux enabled recovery, without which CM11 was not possible.
@andii_nr - For fixes.
@doesntexits and @ngoquang2708 - For their works in SGV, patches and their help.
@DigiGoon - For his highly compressed CM11 sources.
@dhinesh77 @pawitp and others - Various fixes and references have been taken from their work.
XDA:DevDB Information
CyanogenMod 11, ROM for the Samsung Galaxy Star
Contributors
corphish, Dreamstar, psych.half
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Current Beta Version: 3.0
Beta Release Date: 2016-01-24
Created 2015-12-18
Last Updated 2016-05-25
Changelog
Code:
[B]Beta 4_r2 - 9 March 2016[/B]
-It fixes all the stuff which broke in beta4, but were working in beta3.
--Fixed in call audio volume.
--Fixed WiFi tethering.
-Source underwent major cleanup again, we have eliminated most of the source patches, which are now device specific units.
--Compiled Camera, HWComposer from source.
--Detached MemoryHeapIon from binder and compiled it as separate unit.
--We now have our own RIL class. No source hacks to get RIL working.
-Fixed the weird 'No resources found' like message in recovery while flashing.
-Added WiFi direct permissions.
[B]Beta 4 - 20 February 2016[/B]
-Fixed Bluetooth.
-Fixed Bluetooth tethering.
-Fixed Offline charging.
-Fixed Dual SIM.
-Fixed data subscription (2nd SIM mobile data)
-Fixed reboot to recovery.
-Fixed more dalvik VM related memory issues (like app crashes).
-Fixed artifacts observed while screen rotation.
-Fixed black preview in Camera app, glitches in dialer app.
-Activated HW Rendering.
-Fixed audio recording.
-Audio HAL is compiled from source, is AOSP compatible, but may have limitations because all Samsung's optimizations (if any) in Audio HAL is gone.
-Added more SPRD specific OMX libs.
-Compiled various EGL related blobs from source, updated some of them.
-Compiled sensors HAL from source.
-SELinux is enabled and is now enforcing.
-Picked various critical fixes in kernel from @psych.half 's kernel.
-Switched to GCC 4.7, which is the default toolchain in CM.
-Removed various debugging in kernel.
-Implemented @psych.half's CPUFreq driver (min - 1000Mhz, max - 1200 Mhz).
-Enabled ondemand and powersave governor.
[B]Beta 3 - 24 January 2016[/B]
-Fixed Mobile Data.
-Fixed WiFi tethering.
-Fixed USB Tethering.
-Fixed audio routing to loudspeaker and headphones during call when switched to.
-Fixed various app crashes, app installation issues and memory related issues.
-Updated kernel to latest of works by @psych.half
[B]Beta 2 - 18 January 2016[/B]
-Fixed External storage (thanks to [user=220904]@andi[/user]i_nr)
-Switched to updated kernel (updated meaning updates from both stock and kernel patches) by @psych.half. This should fix the brightness bug and the battery bug that some users face. WiFi driver is also updated.
-Fixed IMEI for good. IMEI is now detected the way it is done on any android phone. No need to use any apps for that.
-Fixed USSD dialing/receiving.
-Switched to single-SIM mode (because dual SIM is broken).
-Remove loads of unneeded services.
[B]Beta 1 - 12 January 2016[/B]
-mint -> mint2g
-Fixed battery, its status and everything related to it.
-Fixed Web Browsing and related stuff.
-Updated ramdisk.
-Enabled CPU frequency scaling in kernel.
-Enabled KSM (Kernel Samepage Merging).
-Applied fixes for external storage by [user=220904]@andi[/user]i_nr (Needs confirmation)
-Initial fixes for RIL.
[B]Alpha 2 - 25 December 2015[/B]
-Fixed audio (both from speakers and headphones).
-Fixed HWComposer.
-Fixed EGL crashes and random reboots.
-Fixed camera to some extent (it starts, but cant save pics).
-Camera HAL included is new one compiled from source (BETA version, some more features than the stock HAL).
-Fixed microphone to some extent (it starts listening, but does not record anything).
-Switched to de-odexed builds.
-Updated blobs.
[B]Alpha 1 - 18 December 2015[/B]
-Initial release.
Tracker
Its hard for me to remember all the stuff I fixed in the meantime. So I will update this post (hopefully) with the stuff that has been fixed and will be available in next update.
Following things have been fixed and will be available in next update :
Re-fixed WiFi tethering.
Fixed in-call loudspeaker volume.
Support
F.A.Q
Q. I have faced some issues, which is not mentioned in the 'Not Working' list........?
A. For bug reports, the least we can expect from you is a logcat taken during the issue. Or atleast, you could tell us how and when did you face the bug, how can we reproduce the bug to fix it. Reports without any of these will be ignored.
Q. I got a status 7 error when flashing the CM11 zip...? / My device is stuck at boot logo after flashing CM11...?
A. Please use the recovery that is mentioned in the downloads section. It is recommended to use TWRP as it is known working for all.
Q. I put the ROM zip in internal memory while I was in stock ROM, but when I go to TWRP and try to flash it, the zip is not there, help!
A. TWRP uses psych.half's storage hack that he did in CM10.1. You will need to mount /data (its generally done by default), and then go to /data/media and there you can find the zip.
Q. I successfully flashed CM11, but all my data in internal memory is gone!
A. It hasn't, you can still find them in /data/media.
Q. Can you add XYZ feature to the ROM?
A. No!
Q. Can I use your ROM/any part of ROM and modify it and release it separately?
A. Yes you can. But please mention proper credits.
Q. I flashed this ROM, but I dont find any Google App, where can I find it?
A. Flash gapps mentioned in OP.
Q. Are any 3rd party utilities/kernels/themes/mods supported?
A. No, not yet. If they are supported, it will be clearly mentioned in their respective threads.
Q. If no mods are supported, how can we customize our experience?
A. This is CyanogenMod, a completely different ROM from stock. As of now, no kernels are supported, but you can customize the looks using CM11's highly customizable theme engine.
Bug reporting
How to report a bug?
First off all, check the 'not working' list and see if the bug you are facing is already mentioned or not. If it is, stop right away because the concerned people working on the ROM are aware of the issue.
If the bug/issue is not mentioned in 'not working' list, check the Frequently Asked Question (F.A.Q) and see if issue is resolved already.
If the issue you face is not in FAQ either, you would probably post a reply in this forum, and not PM anyone, about the bug.
Attach a logcat.
If not possible, mention a proper way how you encountered the bug.
Also mention any 3rd party stuff you installed. (Like mods, themes, kernels etc)
Following things WILL NOT be considered as bugs. So please do not post such bug reports, they will be ignored.
Low benchmark scores. Even if Stock results better.
Poor performance in gaming. Even if Stock results better.
High RAM usage/low RAM available.
Various kernel control app crashes.
Crashes of various UI elements when a custom theme/mod is applied.
Random reboots, and other issues caused by flashing custom kernel.
cool.
Dark Knight Begins said:
gonna try now.
Click to expand...
Click to collapse
Try and report back
And one more thing dont quote whole op
SG3 said:
Try and report back
And one more thing dont quote whole op
Click to expand...
Click to collapse
Random reboots all over.
Waiting for next update.
Waw .. great cm11
Great work bro
Waiting for cm without bug
bvrraju said:
Great work bro
Waiting for cm without bug
Click to expand...
Click to collapse
its real hard to make it without bugs.
I just want the ril fixed ..
thats all.
I know C nd D r really working hard to make it.
but we also shud knw that we own a really low end device.
Status Update
We have been working, and... :
Audio -Its fixed, both audio from speakers and headphones.
HWComposer -Its fixed too, patches to libbinder worked.
Camera - Umm, its broken. Problem is, I expected Camera to be fixed by patching libbinder, but it didn't, camera HAL was not loading at all. I eventually got the HAL to load, but it would then cause various system instabilities, so its still broken.
Microphone - Well, microphone does listen to when any respective app is started, but won't record anything (unlike last time, where it won't listen and start recording at all).
RIL - Well, that's really a tough one to fix.
Random Reboots and Freezes - Random reboots are gone, but freezes (caused due to EGL issues) still persists.
P.S : Sources are constantly being updated, patches will only be released after a next release is made. As of the current released build (Alpha 1), not much patches are used, except for those which are mentioned in the device tree.
corphish said:
We have been working, and... :
Audio -Its fixed, both audio from speakers and headphones.
HWComposer -Its fixed too, patches to libbinder worked.
Camera - Umm, its broken. Problem is, I expected Camera to be fixed by patching libbinder, but it didn't, camera HAL was not loading at all. I eventually got the HAL to load, but it would then cause various system instabilities, so its still broken.
Microphone - Well, microphone does listen to when any respective app is started, but won't record anything (unlike last time, where it won't listen and start recording at all).
RIL - Well, that's really a tough one to fix.
Random Reboots and Freezes - Random reboots are gone, but freezes (caused due to EGL issues) still persists.
P.S : Sources are constantly being updated, patches will only be released after a next release is made. As of the current released build (Alpha 1), not much patches are used, except for those which are mentioned in the device tree.
Click to expand...
Click to collapse
just the ril
Alpha 2 is up
Changelog
-Fixed audio (both from speakers and headphones).
-Fixed HWComposer.
-Fixed EGL crashes and random reboots.
-Fixed camera to some extent (it starts, but cant save pics).
-Camera HAL included is new one compiled from source (BETA version, some more features than the stock HAL).
-Fixed microphone to some extent (it starts listening, but does not record anything).
-Switched to de-odexed builds.
-Updated blobs.
Download updated in OP
This build is intended to see how our phone runs kitkat, explore kitkat's new features (if you haven't already), in a decent, less-annoying way. This is not intended for daily use.
About RIL?
That's all I get. We have fixed baseband too, but not included in this release.
Perks of the new camera HAL?
Well, camera might not be fully functional, but that is not because of the new HAL being used, things are same even with stock HAL. This HAL works perfectly with CM10.1. Only bug is the camera preview format has weird colours (just like what we have in recovery, blues look orange and all that). Anyway,
cool!
Great Surprise On Christmas!!
Downloading!!
Good.Now Build CM12
Pratik Mandi said:
Good.Now Build CM12
Click to expand...
Click to collapse
its really hard work.
let them make stable kk 1st.
Dark Knight Begins said:
its really hard work.
let them make stable kk 1st.
Click to expand...
Click to collapse
Oh!!
psych.half said:
Ah GT-S5283 is qcom, I just saw it in download when searching opensource.samsung.
mfserial looks like code for AT/UART for baseband.
Samsung has it disabled cause it wrote their own mfserial.
Yup I checked the RIL implementation in stock. I havent had time to fully reverse eng the stuffs. But heres what I found.
Check the last blocks of code in stock 'init.sp8810.rc' , you see the #datarouter. Thats where the RIL is.
The DR,SMD,DTT,BCS,mobex daemon are responsible for parsing the raw UART, setting up CSC and sending data to framework.
So first try adding those and see.
And if that doesnt work they are using broadcasts to these apps, so you might need to hack on these.
com.sec.app.RilErrorNotifier
com.android.samsungtest.RilDTTCommand
Click to expand...
Click to collapse
Well, adding those surely did 'something' to RIL. Well things went worse, but atleast now we know they are related to RIL.
Like, initially, sim0 radio was off, but sim1 radio was out of service, now both are off.
Anyways, I was comparing the radio logs of stock and cm11, let's take IMEI for instance, and see how it looks like :
Stock:
Code:
D/[B]RILC[/B] ( 102): [0021]< GET_IMEI [COLOR="SeaGreen"]{35**************}[/COLOR]
D/RIL ( 102): put Channel ID '4'
I/RILC ( 102): -->CommandThread [1020] free one command
D/RILJ ( 823): [rild1] [0021]< GET_IMEI
And in CM11:
Code:
D/use-Rlog/RLOG-[B]RILC[/B]( 92): [0023]< GET_IMEI [COLOR="Red"]fails by E_GENERIC_FAILURE[/COLOR]
Any ideas?
We are using SamsungBCMRIL (which is the extension of AOSP RIL itself) in the framework side. PS : That RIL class is fix for dialing, manual network mode etc, basic stuff like signals and imei should work with default setup.
And we are using all the ril blobs from stock ROM
Also, the have you checked the following scripts?
ext_data.sh
ext_kill.sh
They override props by getting original props using getprop, but when I try getprop in terminal emulator, nothing is returned
Edit : @psych.half
After a bit more debugging, I found the reason why IMEI detection fails, radio fails to turn on etc.
it is due to the fact that, respective AT Commands are failing, not all commands fail, but critical commands fail :crying:
Here's how AT commands are handled in stock:
Code:
D/AT ( 102): Channel4: AT> AT+CGSN
[COLOR="SeaGreen"]D/AT ( 102): Channel4: AT< 35**************
D/AT ( 102): Channel4: AT< OK
D/RILC ( 102): [0021]< GET_IMEI {35**************}[/COLOR]
And in CM11 :
Code:
D/use-Rlog/RLOG-AT( 92): Channel4: AT> AT+CGSN
[COLOR="Red"]D/use-Rlog/RLOG-AT( 91): Channel2: AT< ERROR[/COLOR]
So any ideas? How ATs are parsed?
All we can do is in framework level, and add/remove blobs. We can't do anything with ril blobs.
corphish said:
Well, adding those surely did 'something' to RIL. Well things went worse, but atleast now we know they are related to RIL.
Like, initially, sim0 radio was off, but sim1 radio was out of service, now both are off.
Anyways, I was comparing the radio logs of stock and cm11, let's take IMEI for instance, and see how it looks like :
Stock:
Code:
D/[B]RILC[/B] ( 102): [0021]< GET_IMEI [COLOR="SeaGreen"]{35**************}[/COLOR]
D/RIL ( 102): put Channel ID '4'
I/RILC ( 102): -->CommandThread [1020] free one command
D/RILJ ( 823): [rild1] [0021]< GET_IMEI
And in CM11:
Code:
D/use-Rlog/RLOG-[B]RILC[/B]( 92): [0023]< GET_IMEI [COLOR="Red"]fails by E_GENERIC_FAILURE[/COLOR]
Any ideas?
We are using SamsungBCMRIL (which is the extension of AOSP RIL itself) in the framework side. PS : That RIL class is fix for dialing, manual network mode etc, basic stuff like signals and imei should work with default setup.
And we are using all the ril blobs from stock ROM
Also, the have you checked the following scripts?
ext_data.sh
ext_kill.sh
They override props by getting original props using getprop, but when I try getprop in terminal emulator, nothing is returned
Edit : @psych.half
After a bit more debugging, I found the reason why IMEI detection fails, radio fails to turn on etc.
it is due to the fact that, respective AT Commands are failing, not all commands fail, but critical commands fail :crying:
Here's how AT commands are handled in stock:
Code:
D/AT ( 102): Channel4: AT> AT+CGSN
[COLOR="SeaGreen"]D/AT ( 102): Channel4: AT< 35**************
D/AT ( 102): Channel4: AT< OK
D/RILC ( 102): [0021]< GET_IMEI {35**************}[/COLOR]
And in CM11 :
Code:
D/use-Rlog/RLOG-AT( 92): Channel4: AT> AT+CGSN
[COLOR="Red"]D/use-Rlog/RLOG-AT( 91): Channel2: AT< ERROR[/COLOR]
So any ideas? How ATs are parsed?
All we can do is in framework level, and add/remove blobs. We can't do anything with ril blobs.
Click to expand...
Click to collapse
On closer inscpection the datarouter is for another functionality. You know in stock ROM we can use select which SIM to use mobile data from.
Afaik, BCMRil is for Broadcom ones Spreadtrum doesnt seem to need a seperate RIL class
So maybe we need to take libreference-ril.so and libril_sprd.so from another sprd which doesnt depend on samsung's stuff. Samsung made a lot of modification on libril on this one.. Heck there isnt even telephony framework, ril is handled by its own apps..
Update @corphish
after some log digging, AT commamds are handled by at_distributor.. but it only setups socket... and executes "am broadcast com.sec.atd.request_reconnect"..
Yup its handled by samsung's own app
psych.half said:
On closer inscpection the datarouter is for another functionality. You know in stock ROM we can use select which SIM to use mobile data from.
Afaik, BCMRil is for Broadcom ones Spreadtrum doesnt seem to need a seperate RIL class
So maybe we need to take libreference-ril.so and libril_sprd.so from another sprd which doesnt depend on samsung's stuff. Samsung made a lot of modification on libril on this one.. Heck there isnt even telephony framework, ril is handled by its own apps..
Update @corphish
after some log digging, AT commamds are handled by at_distributor.. but it only setups socket... and executes "am broadcast com.sec.atd.request_reconnect"..
Yup its handled by samsung's own app
Click to expand...
Click to collapse
Alright!
RIL is connected though. Never had that problem of it failing to connect.
So what's the next thing we should do? Try adding apps from stock?
Let`s emphasize that-- [highlight]THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT`S TO COME. AND SOME THINGS DOESN`T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.[/highlight]
Code:
[B]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/B]
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Some SIM cards may not be recognized as the Lollipop more capricious in this regard.
- Conference Calls
- Some problems with audio codec settings, but generally it should
- After Recovery time to time incorrect capacity of battery
- disabled SELINUX
- Camera key don't start camera app
- TV out removed, because it is not working yet
- many custom features from omni is still not merged
UPDATE from OMNI 5.1.1 from 27.12.2015 to 03.06.2026
ATTENTION! Since version 27.12.15 and ending 06.03.2016 F2FS used file system. Therefore, when flash on earlier versions and later, you need to follow the instructions from scratch. Also use these "start" kernels. This will remove your current rom and files.
f2fs "start" kernel is here: s8500, s8530
ROOT
Omni is without root support from default
To activate root flash zip via Recovery UPDATE-SuperSU-v2.46
Downloads
GApps: Download
Installation
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES: https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel: https://yadi.sk/d/ilhyKTaEfTo6L
FOTA: https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES: https://yadi.sk/d/cBPD41VEbP2od
"start" https://yadi.sk/d/wVGzUA96fGW55
FOTA: https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type sh partition.sh -> press Enter"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
HOW TO UNINSTALL
Just reflash bada via Multiloader
CHANGELOG:
14.02.2017 https://yadi.sk/d/BdsM-5VO3E5FS9
- Omni sources 14.02.2017
- Fix issue with not working partition.sh
11.02.2017 https://yadi.sk/d/yJaeiEZt3DvPAH
- Omni sources 11.02.2017
- Big update kernel from Coldwindofnowhere
Added CMA. Now, it is stable. This option allows you to have more available RAM as in BigMem.
Big thank's for Coldwindofnowhere and xc-racer99
- Update power management
- Added SQL optimization
- Added some RIL, ART tweaks
- Feedback from testers increased search speed of GPS satellites
- ROM compiled with Uber Toolchains 4.8 and 4.9 kernel, with the addition of optimizations ArchiDroid
arm-linux-androideabi-4.8
arm-eabi-4.9
11.01.2017 https://yadi.sk/d/FB2yJPyz38Ssx4
- Omni sources 11.01.2017
- Update kernel from Coldwindofnowhere
- Reworked RAM management and return to the ext4 file system to increase space and reduce lag
- New power management chipset and reduced display voltage
03.06.2016 https://yadi.sk/d/wFB7zDA0sCweM
- Omni sources 02.06.2016
- Small changes on kernel. Disabled volume tweaks.
- Small changes on RAM managment
- Set zRam zise to 128 Mb
09.05.2016 https://yadi.sk/d/YUx6MYyBraaUt
- Omni sources 09.05.2016
- Reworked ART parameters
- Disable the Battery Life Extender and Fast charging (not quite work correctly)
- Reduced zRam size to 96 Mb
- Added the latest fixes for GPS from Volk204
- Improved deep sleep the device
- Enabled hardware UI acceleration
- Some tweaks and fixes for RIL from Alberto96 and fire855
- Added settings for the stability of receiving 3G (experimental)
- Set the correct values of sound in the advanced settings
- Fixed lag after the call
- Fixed rewind the video in the player
- Big update kernel with latest changes from @Coldwindofnowhere https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/tree/android-5.1
14.01.2016 https://yadi.sk/d/MeqfNujemzK7J
- Omni sources 14.01.2016
- Added porting applications to SD-card with support for memory selection
- Added some options ART from aries
- Added Bigmem support in Advanced settings
with default settings we have 270 mb RAM with working 720p video recording
with Bigmem we have 283 mb RAM without working 720p video recording(as was by default in previous versions)
with Max RAM we have 315 mb RAM and camera, video playback and torch is not working at all
- New features in the kernel : Battery Life Extender, dynamic synchronization of files , dynamic control and fast charging . All of this can be found in Settings - Performance
- Added optimization zRam swap and support for the exFAT file system
- Added new planners SIO plus and BFQ, and new TCP algorithms
- Changed CPU frequency : min = 200 MHz , max = 1200MHz . Max can be reduced to 1000 MHz for energy saving
- Also enabled boost for incall volume in Advanced Settings
- Big kernel update from https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/tree/android-5.1
Big thanks to @Coldwindofnowhere
27.12.2015 https://yadi.sk/d/tyEMtPVHmXAVD
- Omni sources 27.12.2015
- Switch to f2fs file system (system partition increased by 100 MB to install GApps on a new file system)
- Minor optimization of ART and other kernel optimization for speed and stability
22.12.2015 https://yadi.sk/d/faohzx6CmRCRH
- Omni sources 22.12.2015
- The camera can shoot 1280*720 ( -10 MB of available RAM)
- Added new Governors and I/O planners to the kernel
- Changed minimum screen voltage ( 3.0V was - became 2.8V )
- Other kernel optimization for speed and stability
- Added support for TRIM
- Disabled menu button on the lock screen
14.12.2015 https://yadi.sk/d/NTt8Y6zymFAYu
- First release
THANKS TO
Special thanks to volk204 for their help to build this project.
Thanks to Alberto96, Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen, Benzox, fire855 and many others.
OMNI team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
sooti & Coldwindofnowhere for kernel and rom patches (Galaxy S I9000)
and many other who help us.
XDA:DevDB Information
[ROM][NAND|S85xx] OmniRom 5.1.1 Lollipop, ROM for the Samsung Bada OS
Contributors
djkoloda, volk204
Source Code: https://github.com/AMD-Grifon
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Abandoned
Created 2016-04-17
Last Updated 2020-09-06
Good job bro.
Can u post some screenshot?
3. Advanced -> Terminal Command -> Select -> write sh partition.sh, press Enter
Thang Trinh said:
Good job bro.
Can u post some screenshot?
Click to expand...
Click to collapse
Thank`s! Screens will later.
@djkoloda When can we expect an update? Your ROM is awesome. Thanks a lot dear friend.
docamr said:
@djkoloda When can we expect an update? Your ROM is awesome. Thanks a lot dear friend.
Click to expand...
Click to collapse
@docamr Thank you for your kind words. The update will be today or tomorrow if there is no technical problems.
Before I publish the release, I have to check it thoroughly. So it will have to wait a little longer.
Take your time to polish your rom. If you need help for testing purpose you can count on me
barbe31 said:
Take your time to polish your rom. If you need help for testing purpose you can count on me
Click to expand...
Click to collapse
Thanks. I sent you a PM the build for the tests.
Please Update the ROM @djkolada
Dear @djkoloda
Please update the ROM bro. I am waiting eagerly.
docamr said:
Dear @djkoloda
Please update the ROM bro. I am waiting eagerly.
Click to expand...
Click to collapse
I finished the test and tomorrow will post an update. If there are any problems - write, so how on s8500 and s8530 results may vary and I can not detect all bugs.
Waiting to download and test update today.
djkoloda said:
I finished the test and tomorrow will post an update. If there are any problems - write, so how on s8500 and s8530 results may vary and I can not detect all bugs.
Click to expand...
Click to collapse
Please give us update today. I will test and give you feedback. Thank you djkoloda :good:
docamr said:
Please give us update today. I will test and give you feedback. Thank you djkoloda :good:
Click to expand...
Click to collapse
Given my "perfect" online, the build can push at the night ...
djkoloda said:
Given my "perfect" online, the build can push at the night ...
Click to expand...
Click to collapse
Bro can modified device tree omni to run on cm?
thinhx2 said:
Bro can modified device tree omni to run on cm?
Click to expand...
Click to collapse
In principle, not so difficult, but will take enough time for this.
djkoloda said:
In principle, not so difficult, but will take enough time for this.
Click to expand...
Click to collapse
Yes,wait bro build cm13
the update is delayed , OP busy at work, and then holidays.
Rom is finally ready! Enjoy!)) If there will be any problems with the battery drain, then send reports.
https://yadi.sk/d/mTSgRb2krUoGK
gapps
Hi,
looks good, what about some minimal gapps?
@djkoloda : good job. Couldn't try the version last week. Really faster than before. Now we can use it normally.
I tried to install pico gapps but it's insanely slow.
I will perform much deeper test but it is quite good a version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 12.1 for Samsung Galaxy J5
DISCLAIMER
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
--------------------------------------------------------------------------
Bugs and changelogs are in 2nd post !
--------------------------------------------------------------------------
Real Battery Life Calculations
Talk Time: Aprox. 18 hours (3G)
Music Playback: Aprox. 62 hours
Video Playback: Aprox. 13 hours
Screen On Time (Idle CPU): Aprox. 20 hours
Screen On Time (Full load CPU): Aprox. 6-8 hours (user-dependent)
Deep Sleep only: Aprox. 70 hours
--------------------------------------------------------------------------
Installation
1. Make sure you have updated to stock 5.1.1.
2. Download the ROM from the link below.
3. Download 5.1.1 ARM GAPPS.
4. Transfer the zip files to your SD card.
5. Reboot to recovery mode. ( Vol UP + Home + Power )
Note: It is highly recommended to use TWRP Recovery.
6. Optional: Do nandroid backup.
7. Full wipe /system, /internalsd, /data, and /cache.
8. Install CM zip and GApps zip.
9. Reboot to system.
10. Setup your device.
Enjoy!
------------------------------------------------------------------
Downloads
SM-J500FN
SM-J500F
SM-J500G
SM-J500M
SM-J500H
SM-J500Y
SM-J5007
------------------------------------------------------------------
SourceCheck out the ROM Source available on GitHub.
Feel free to submit any fixes, Just remember to give proper credits when using other people's source.
Kernel Source
---------------------------------------------------------------------------------------------------------------------------------------
Credits
@jackeagle for kernel maintaining.
@TheWisp for the awesome InputDisabler.
@aapav01
@ganesh varma for helping when development needed support.
And last the awesome J500H testing team we have in Hangouts, for being there all this time.
XDA:DevDB Information
CyanogenMod 12.1 for Samsung Galaxy J5, ROM for all devices (see above for details)
Contributors
Nick Verse, ganesh varma
Source Code: https://github.com/Galaxy-J5
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop Modem/Baseband
Version Information
Status: Stable
Current Stable Version: 4.0.0
Stable Release Date: 2016-07-23
Created 2016-06-23
Last Updated 2016-09-23
Bugs and Issues
Code:
- No audio through FM Radio.
Let me know if you find other bugs!
--------------------------------------------------------------------------------------------------------------------------------------------
Submitting Bug Reports:
If you find some bugs, report it with logs and detailed information of the issue.
Do not report bugs if custom tweak is done.
Do not report bugs if Xposed is installed!
---------------------------------------------------------------------------------------------------------------------------------------------
Changelog:
Code:
[B]September 23, 2016[/B]
- Fixed reboot issues.
- Fixed lags from not needed libraries and kernel commits.
- Added IMS and VoIP support. (Needs testing)
- Fix rmnet (data) issues.
- Dalvik/ART optimizations. Now ROM is more smooth.
- Removed extra governors/io schedulers.
(The provided governors in OC kernels for J5 are for Exynos devices,
so they need extra configuration to be adapted to Snapdragon devices.
Until then, we will use the stock and trusted ones,
but keep overclocking to be enabled by a userspace application).
- Many kernel fixes.
- Framework fixes.
- Audio enhancements.
- Added audio echo cancellation support (AEC) for in-calling audio.
- Added Wifi-Direct and Screen Cast/HDMI support in kernel. (Needs testing)
- Added Volume wake and Home button wake support.
(You can enable/disable these features from Settings->Buttons)
- Merged with latest CM Changes.
[B]September 8, 2016[/B]
- Removed On-Screen-Buttons implementation.
(Currently we don't have an implementation for hard disabling touch-keys in kernel.)
- Kernel fixes.
- Attempt to fix reboot issues and data problems for [B]G[/B] and [B]H[/B] variant.
- Removed KernelAdiutor
[B]September 2, 2016[/B]
- Added OC in kernel and fixes for frequency ladder. (0.2 to 1.8 GHz)
- Added a lot of governors and I/O schedulers.
- Added KernelAdiutor as a built-in application for tweaking parameters.
- Added DayDream support by default.
(It is a screensaver feature for Android.
You can choose your preference in Settings -> Display & lights -> DayDream)
- PowerHAL fixes.
- Disabled compression of camera images, set quality of Encoder to 100% and increase memCap *4.
(Image sizes are larger, and have better quality)
- Added On-Screen-Buttons implementation similar to qemu.hw.mainkeys=1.
(You can use software keys for Back/Menu/Options, by enabling it on the first setup screen.
Main keys will be permanently disabled)
- Merged with latest CM Changes.
[B]August 20, 2016[/B]
- Excluded InputDisabler from build. (Not needed from now on as we found the root of the cause)
- Screen on/off lag reduction. (WIP)
- Fixed SD Card issues and corresponding folder creations on boot.
- Added option to secure unmount external SD before removal.
- Added option to record in-call voice for all regions.
- CPU speed/responsiveness optimizations.
- SELinux denial fixes for other variants too.
- Switched to SELinux enforcing, minized kernel messages and ADB secure (needs su command from now on).
- Optimized latency for audio HAL. No drop-outs from now on.
- Audio effect optimizations. Sound is more crisp.
- Excluded zRAM.
(zRAM caused not needed CPU overhead and heat issues when on Full Brightness+Mobile Data+GPS)
- TWRP bug-fixes.
- Kernel fixes.
- Merged with latest CM Changes.
- Updated stable release name to 2.0.0
[B]July 22, 2016[/B]
- Fixed small freeze on screen unlock.
- Fixed Auto Display Color Calibration.
- Disabled Auto Brightness feature. (No light sensor for J5)
- Raised the perceived loudness by 4db on headphones, and 4db on speaker output.
- Fixed audio minor drop-outs when exiting deep sleep.
- Fixed some firmware link typos.
- Enabled zRAM. (512MB)
- Merged with latest CM Changes.
[B]July 15, 2016[/B]
- Fixed NFC.
- Fixed Keymaster firmware detection.
- Merged with latest CM Changes.
[B]July 14, 2016[/B]
- Fixed moving apps to external SD.
- Added option to choose the default install location of applications in Settings.
- Optimized haptic feedback.
- Fixed front flash camera latency.
- Merged with latest CM Changes.
[B]
June 23, 2016[/B]
- Optimized CPU usage.
- Fixed SELinux Denials.
- Fixed audio latency and quality.
- Fixed QR Scanner display errors and camera related problems.
- Kernel updates.
- Merged with latest CM Changes.
--------------------------------------------------------------------------------------------------------------------------------------------------
Tips :
To activate Developer settings : Settings -> About phone -> press Build number 7 times.
To activate 3-way reboot go to Developer settings and select "Advanced reboot".
Root is included and disabled by default, enable it from Developer settings - Root access.
BusyBox is included.
LiveDisplay is a feature for adapting display colors for night usage.
You can enable it by turning on GPS and data/wifi for some seconds.
Then go to Settings -> Display & lights -> LiveDisplay -> Display mode and change from off to automatic.
Then your phone will know when to adjust your display for night usage through your local GMT zone.
You can also adjust Color Temperature for Day/Night modes.
Reserved.
Reserved :fingers-crossed:
@Nick Verse Very good work and thanks to the update several bugs were fixed, but something happened, flash of the camera does not work well. Taking photo with flash front dark leaves that mistake but I could see in the build 9 of vaserbanix. I hope this report will help to upgrade future and thank you again for the good work. Sorry for my bad English translator use. Regards
Awesomeness
Great work! Keep it up.
Bro will test it tommorrow.
That calling bug is fixed or not?
Active touchpad during phome call.? @Nick Verse
Sent from my SM-J500F using XDA-Developers mobile app
In order to prevent touch during calls, press the power button and it should keep your phone locked until you finish your call. It works for me.
Sent from my SM-J500F using Tapatalk
@Nick Verse your md5 files still have full path, you can try the following command to generate md5 files recursively:
in zsh
Code:
for i in **/*(/D) ; do ( cd $i ; for j in *(.D) ; do md5sum $j > $j.md5 ; done ) ; done
in bash run this script
Code:
#!/bin/bash
if [ $# -ne 1 ] ; then
echo "Usage $0 [directory]"
exit 1
fi
find $1 -type f -print0 | while IFS= read -r -d $'\0' file; do
(
cd "$(dirname "$file")"
filename="$(basename "$file")"
md5sum "$filename" > "$filename".md5
)
done
Source
Which you recommend gapps?
1szymon4 said:
Which you recommend gapps?
Click to expand...
Click to collapse
open_gapps-arm-5.1-nano
1szymon4 said:
Which you recommend gapps?
Click to expand...
Click to collapse
I use gapps micro.
how do I flash this if I got an older version of this cm?
What about j500h ??
Is it safe to install test version ??
Ahmed SD said:
What about j500h ??
Is it safe to install test version ??
Click to expand...
Click to collapse
Still testing not booting so dont
Sent from my SM-J500H using Tapatalk
i use j5007. it had error 7. i removed asserts after that installed it but it cant boot and stuck at boot animation.
---------- Post added at 08:40 PM ---------- Previous post was at 08:11 PM ----------
i flashed the rom with an other kernel. it started but systemui force closed and i cant do any thing.
American_Jesus said:
@Nick Verse your md5 files still have full path, you can try the following command to generate md5 files recursively:
in zsh
Click to expand...
Click to collapse
Thank you for your report. The .md5 files are generated from the CyanogenMod source build itself.
Avi gupta said:
Bro will test it tommorrow.
That calling bug is fixed or not?
Active touchpad during phone call. @Nick Verse
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Touch during call is fixed.
soso90 said:
i use j5007. it had error 7. i removed asserts after that installed it but it cant boot and stuck at boot animation.
i flashed the rom with an other kernel. it started but systemui force closed and i cant do any thing.
Click to expand...
Click to collapse
You must have Lollipop baseband/modem, otherwise things won't work. Make sure you have updated to official 5.1.1 first if you are on Android 6.0.
Nick Verse said:
You must have Lollipop baseband/modem, otherwise things won't work. Make sure you have updated to official 5.1.1 first if you are on Android 6.0.
Click to expand...
Click to collapse
i used cm12.1 before
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
@Androbots
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_a7xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2022-06-15
Changelog:
Changes 09-04-2023:
Synced to latest LineageOS source (including March security patch)
Changes 18-01-2023:
Synced to latest LineageOS source (including January security patch)
Included patches missed in last build
Changes 19-08-2022:
Synced to latest LineageOS source (including August security patch)
Changes 15-06-2022:
Synced to latest LineageOS source (including June security patch)
ZRAM now mounted with discard option (thanks @JPCastillo2000 for the link)
Changes 26-04-2022:
Synced to latest LineageOS source (including April security patch)
Changes 15-03-2022:
Synced to latest LineageOS source (including march security patch)
Spoiler: Older changelog
Changes 20-01-2022 (all devices):
Synced to latest source (January security patch)
Enable WiFi display
Switch to GNSS HIDL service (improves GPS stability, thanks @retiredtab @impasta)
Fixed power profile switching (restores correct CPU speed when going back to balanced mode)
Changes 20-01-2022 (A510F/A710F):
Enable fastcharge hal (allows disabling fastcharge)
Changes 19-10-2021:
Synced to latest Lineageos (October security patch)
Changes 25-09-2021:
Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)
Changes 21-09-2021:
Resysnced source (includes updated webview)
Fixed Wi-Fi hotspot (broken in last build)
Added slow/fast charging detection (indicates on lock screen)
Changes 16-09-2021:
Synced LineageOS sources (includes September security patch and AOSP WFD)
Fixed WiFi direct
Added further ZRAM improvements (thanks @alexax66)
Changes 28-08-2021:
Updated ZRAM implementation from Linux 4.1.52
Switched to LZ4 ZRAM compression (should be faster and better)
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Hi,
A search on XDA reveals this write up:
LineageOS 18.1 based on Android 11 is here for nearly 60 devices
LineageOS 18.1 builds based on Android 11 are now available for dozens of smartphones. Here's the changelog and supported devices list!
www.xda-developers.com
On top of this we have a lot of fixes for our devices from security to ram management. The list is too long, if you are interested take a look at the device trees and kernel source on GitHub.
With regards to app compatibility, Android 11 has been out for nearly a year now. If an app you use isn't compatible then to be honest it isn't worth using.
Kind regards,
Danny
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
kurtn said:
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
Click to expand...
Click to collapse
probably because the Email app is broken?
I've been using FairEmail since I've spotted this problem: https://forum.xda-developers.com/t/...7-1-for-a5-2016.4036151/page-35#post-85302601
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
danwood76 said:
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2020-08-20
Click to expand...
Click to collapse
Hi
Why was it not Build for (a7xelte) A710 2016?
setecastronomy said:
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
Click to expand...
Click to collapse
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
mihancad said:
Hi
Why was it not Build for (a7xelte) A710 2016?
Click to expand...
Click to collapse
I will add the a7 on Tuesday, although I am not the maintainer of that device.
kurtn said:
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Click to expand...
Click to collapse
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Thank you, my brother, I look forward to it
Thanks a lot for developing new OS for our A310f, Dan. Great work, I runs fine, flowing perfect!!
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card.
Click to expand...
Click to collapse
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
danwood76 said:
You are much better off switching to exfat.
Click to expand...
Click to collapse
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
setecastronomy said:
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
Click to expand...
Click to collapse
Try formatting the card from the phone. I have had issues formatting using Linux and Windows before, even for my stock S9.
Kind regards,
Danny
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
I will add the a7 on Tuesday, although I am not the maintainer of that device.
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Click to expand...
Click to collapse
Will it be ready for download for A7 (a7xelte) today?
mihancad said:
Will it be ready for download for A7 (a7xelte) today?
Click to expand...
Click to collapse
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
setecastronomy said:
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
Click to expand...
Click to collapse
I have just done this on my test A5 and everything worked perfectly, I downloaded 300MB of maps of my region and it all works well. There was a permissions pop up when I first opened the app which i accepted.
The card is my old Samsung 64GB, I wiped the card in my desktop and then allowed the phone to format it, I think Windows/Linux sets some exFAT options that android doesn't like so it is best to let the phone do it.
Kind regards,
Danny
I have just uploaded a small update and added the a7xelte build.
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Kind regards,
Danny
danwood76 said:
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
Click to expand...
Click to collapse
I'm sorry, I'm using Google Translate, I just informed you as a reminder.
Thank you very much for your kindness, dear Danny
Just wanted to say that the A510F works very well, except that sometimes the camera doesn't connect.
Thank you for your effort @danwood76 (and maybe others )!