Related
OmniROM for P900 Only
installation:
install custom recovery TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
install omnirom with recovery
install gapps (optional): http://forum.xda-developers.com/showthread.php?t=2397942
for root flash zip file with recovery: http://download.chainfire.eu/589/SuperSU/
Changelog:
R2:
-improve overal stability
-bug fixes
known issues:
camera is not working
buttons backlight is not working
download links:
R2:
P900 https://yadi.sk/d/SUn2aByFcaEAM
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
bonuzzz, Valera1978, arcadia2uk
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-04
Last Updated 2014-11-20
Reserved
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Latest update: 11082014 2.30pm EST
Thank you bonuzzz and Valera1978. This OmniROM directly built from source is out of the box the smoothest and reactive ROM I've seen on the T-900. I have been fortunate to run this version in alpha and beta over the past 4 or 5 days and I have not seen any extraordinary issues with the release.
Note for v.2 - Be very patient in flashing v2, from that system format starts in TWRP until extraction kicks in there's currently a delay of up to 3 minutes
Just as under the SM-P900 cm11 tread, I have performed some functionality testing of the device and some extra features, they are shown below as working, not working or not tested. The functionality grid was developed based on weaknesses in earlier AOSP builds and ports for the large format Samsung Tab/Note Pro family:
- mtp - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/ activated. Check mark USB debugging notify.
- adb
- External SD - working out of the box
- Ext4 SD card mounting on external SD - Auto-mount does not work, tested on Sandisk 128Gb SD
- USB OTG including USB storage
- Off-mode charging
- Encryption tested on backup restore in TWRP 2.8.1.1 restore failed in data, but must be related to a TWRP error Encryption process in ROM takes about an hour to perform, if someone is interested in performing the test and report back it would be great, but theoretically it should work.
-----------------------------------------
- Lid sensor
- IR blaster - worked by using IR 2.0
- OC settings - located in Settings/Performance/ if you click the 3 dots in upper right corner you can chose a toggle, or a drawer mode where a multitude of performance settings and information is available, most of them are currently not used.
- Advanced reboot - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/. Check mark Advanced reboot.
- Screen rotation specific issue with T-900
-----------------------------------------
- Play Store
- Google Play movies download and playback
- Google Play streaming Movies & TV
- DRM - tested with Audible, Google Books and Amazon Kindle
-----------------------------------------
- Zona
- Popcorn Time - need upgrade to latest version 2.3 beta, includes built-in VPN and Chromecast support with subtitles, earlier version timed out
- YouTube 1080p playback - 1440p will work w. v5.9.0.12, but I believe this to be a false positive.
- Netflix
-----------------------------------------
- Chromecast with #MirrorEnabler hack, allowing for screen cast
- MHL connector
- Miracast
-----------------------------------------
- Capacitive lights - I assume this is the backlights for the capacitive buttons
- Capacitive keys
- Home button - correct function performed
- Brightness manual + auto
- Vibrator
- S-Pen according to OP only available on P-900
-----------------------------------------
- GPS lock and voice directed navigation
- WiFi both 2.4 GHz & 5 GHz are working
- Bluetooth
- Microphone
- Audio on both speakers
- Headphones
-----------------------------------------
- Camera - in progress; the camera "works", but does not allow for single shots to be taken, and crashes in video mode, but panorama shots are working
- Torch as of v2
- Camera Sensors as of v2
-----------------------------------------
- Xposed Framework and modules - need re-initialization after each boot (common to all AOSP ROM's)
- Superuser - installation of latest flashable version SuperSU through TWRP is recommended - make sure to enter into SuperSU settings and execute "Install SuperSU backup script" under the CUSTOM ROM label before re-flashing a ROM update.
- Hangouts Dialer phone calls via Hangouts
-----------------------------------------
The following are standard limitations and options for OmniROM:
Write access to your external SD-card works out of the box, but just in case i suggest to d/l JRummy's SD KitKat Fixer
init.d support also works out of the box, otherwise d/l Uni-init by Ryuinferno.
If you think to much heat is building up use Performance/Governor set to ondemand, or conservative and I/O Schedduler to bfq, in addition to increase battery time you can set Wi-Fi/Advanced/Keep Wi-Fi on during sleep/ to Only when plugged in and make sure the Wi-Fi/Advanced/Wi-Fi optimization/ is checked and reduce Display/Sleep/ to below 1 minute. You can also use some apps to improve battery eg Easy Battery Saver, or the more sophisticated AutoCon+ Save Battery & Data and and to put hanging apps to hibernation Greenify that I believe require Xposed Installer. To improve charging time, you can use an app eg Faster Charger. Finally, I have also used PurePerformances in order to further improve the performances and VIPER4AndroidFX to allow for louder speaker sound and enhanced listening experience.
Stevethegreat said:
To anyone who flashed this, can you do the following immediately after installation?
1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.
2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).
Thanks.
Click to expand...
Click to collapse
1.1Gb RAM used, but I'm running MultiROM, besides that I had only installed SuperSU and Pico gapps, I have exactly the same usage displayed with cm11.
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
bonuzzz said:
IR port is working. Tested with smart ir
flip cover is working also
I dont understand issue with screen rotation
Click to expand...
Click to collapse
The screen doesn't automatically rotate when turning the device, although I have automatic rotation enabled in System/Display/ with values 0/90/180/270. However, with some apps a forced rotation arrive that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. Anyway, blocking the screen in landscape, or in portrait with the apps I mentioned in my post works perfectly well, but it's a forced rotation, not automatic. It could be device specific? - note issue only concern T-900, not P900/901
I retested IR and Lid and they worked when flashing the ROM with TWRP 8.2.1.1. This was either a glitch, or the fact that I flashed in MultiROM.
arcadia2uk said:
For me the screen don't rotate automatically when turning the screen, although I have automatic enabled in System/Display/. However, with some apps I have automatic rotation that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. However, blocking the screen in landscape, or in portrait with mentioned apps works perfectly well, but it's a forced rotation, not automatic. It could be device specific?
Click to expand...
Click to collapse
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
bonuzzz said:
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report
multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
Click to expand...
Click to collapse
That kernel use can explain some of the oddities I've experienced.
On the T-900 I had the screen rotation issues as well, along with other users, so I believe it's a T900 issue. It works with stock ROM though. Also, I just forwarded some screen shots.
Hey guys thanks for yet an other custom rom you sure have been working hard! I did some reading about this omnirom and i conclude imo it is prefereable to cyan, is valeria working only on omni now i noticed she released a new cm. Thanks again looking forward to next release.
Hi friends, I wanted to thank you for bringing OmniRom to the Note Pro 12.2.
I will be sure to install it this coming weekend when I have some time
I'm currently on CM and it's very nice, but I like the idea of Omni being truly open source.
Your efforts are greatly appreciated.
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
rkirmeier said:
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
Click to expand...
Click to collapse
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
arcadia2uk said:
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...
However, the best way is to try it out and judge for your self.
On the other hand, if you really want to read up about it, check out this article
Click to expand...
Click to collapse
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Thanks for the info and that is an interesting read. I'll probably give OmniROM a try...
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
I don't believe it is implemented. But, the split view feature in the video exist as the xposed module: XMultiWindow. This was Omin's first release of the multi-window feature, and the development is still ongoing for a more feature packed floating window solution. See for example this concept idea.
notspike said:
Where is the multi-window support as shown in this vid?
https://www.youtube.com/watch?v=f5bcccyBPsU
Click to expand...
Click to collapse
multiwindow had been removed from omnirom in spring 2014.
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
bonuzzz said:
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
Click to expand...
Click to collapse
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
francesco totti said:
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
Click to expand...
Click to collapse
https://yadi.sk/d/xTQ0HUhocaBpC
no. camera is not working yet
Q&A for [ROM][Development][ODIN] CM12.1 / CyanogenMod 12.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Development][ODIN] CM12.1 / CyanogenMod 12.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
qsnc said:
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.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Why another thread? Because fuison3 is in a complete rework process, and I am the actual device maintainer, so I need your feedback to verify everything is working, before the new stuff will be added to the official CM12.1 repositories. So, by testing this, you help CM development for odin. I have no interest in providing daily builds or anything of the sort.
Also, there are sister threads for working on pollux, yuga and dogo.
Changes:
- Jan 30: Initial release
- Feb 5: kernel updates, audio HAL modernization
- Feb 9: WiFi updates
- Feb 13: volume rocker wakeup, sdcard hotplug, camera focus changes, cleanups
- Feb 16: new call fix
- Feb 27: F2FS support
- Mar 1: audio update
- Mar 3: smooth boot animation
- Mar 6: more audio updates
- Apr 3: first 12.1 build
- Apr 20: radio fixed
- Apr 22: Android 5.1.1
- Aps 27: tons of cpu and gpu governor updates/fixes, wifi updates
- May 1: gpu gov and wifi updates
- May 7: app2sd fixes, selinux updates, fixed power hal, OSS THERMAL MGMT, wifi fixes
- May 10: plethora of core kernel and platform updates, init changes
- May 22: scheduler and platform updates, reworked kernel configuration
All builds are synchronized with the latest CM tree. For the specific updates to fusion3 and yuga, see the source link below!
Download:
cm-12.1-20150523-UNOFFICIAL-odin.zip
Installation:
If you have anything other than CyanogenMod 12.1 on your device, do a full wipe, and get Android 5.1 compatible gapps!
Testing:
Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least. I will have to ignore all other "problem reports" as they are essentially useless.
If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
Convert to F2FS:
I merged F2FS support into the official CM repositories, so all recent nightlies support this as well.
Be aware that this needs some understanding of how to use ADB and the conversion process will DELETE all you user data/settings!
This is how you convert to F2FS:
- Reboot into recovery
- Flash the ZIP linked above
- ADB Shell onto the device
- mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/cache
- mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
- Reboot
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also pollux, odin, and so on).
http://review.cyanogenmod.org
Click to expand...
Click to collapse
When are the chances or possiblities for getting official nightlies for odin????
Can i change the selinux to permissive or disabled?
firstly,thx for the build
i had used the other cm12.1 by other dev but the selinux seems to fail to set using apps or commands(it ll shutdown immediately after set the selinux to permissive)
sry for my bad english
VOICE_CALL audio source is unaccesable!
qsnc said:
new build available. been off on holidays for a while, and working on pollux and yuga.
what is the status quo of this release?
Click to expand...
Click to collapse
I've make clean install of this release (07-07-2015) and found that any sound call recording application doesn't work. "ACR call recorder" as example.
Qsnc, please make the VOICE_CALL audio source work, this is very useful feature!
It works fine on stock lollipop and on CM11 official build.
Thanks.
Build 20150707 works perfectly on my ZL. No bugs found so far. Would be happy to get an official CM12.1 for the ZL
On build of July 7 I faced the following problem: sometimes at when pressing power button, the screen doesn't turn on and after a while bootanimation begins.
Because I have less than 10 post I can't answer in the main thread
With Nightly from 11.07. i cant use GPS. If i start a GPS App, the Phone makes a cold Reboot.
First dirty flash, and then alsp with fresh install.
Click to expand...
Click to collapse
No problem here with GPS and build 11.07. on the ZL. GPS works fine with all installed GPS apps like GPSstatus, OSMAnd, Oruxmaps, Here, Mapfactor Navigator.
Guido
Thanks for the amazing ROM but..
FIrst of all thanks for the CM 12.1 ROM
I have been following this thread and using the ROM for quite some time but today I noticed when I was recording Videos the Secondary Camera at the back (tiny hole above the camera) does not pick up any sound and the audio in the videos I recorded were very faint. I don't know if its only me or anyone else has the same problem but if anyone is having the same issue please let me know as I have warranty on the phone till the end of this month. I know you asked to provide logs but I don't think its relevant for this issue. Just want to know if its a common issue or a problem with my handset.
Using 12.1-20150730-UNOFFICIAL-odin on Sony Xperia ZL (C6503)
Thanks in advance for any reply/help and keep the development going!
Help my speakers of SONY Xperia ZL
As the title says,My speakers of my smartphone was broken after the selinux be permissive d.
Could you tell me how to fix this problem?
I tried to wipe /system,/cache and /dalvik-cache,but it haven't recover from this status.
Please help me:'(
issue
Hi CYAN users, i got bugs with last build, after fresh installation with wipes. Chrome browser didn't work, it closes with errors.
Gapps issue
Hi all cyan users! Someone got problems with latest build, the issue is that chrome browser closes with error. Maybe there is more problems with gapps, I did not check. I can not provide screenshots, because I installed build from 30.07.2015.
does the official Sony's apps work in it? like Walkman movies and specially clear audio+ ?
abdullah.darwish said:
does the official Sony's apps work in it? like Walkman movies and specially clear audio+ ?
Click to expand...
Click to collapse
As far as I know those apps won't work because they make use of sonys framework, which is not included in cm. But there are ports of some apps, you can find them somewhere here on xda in the general apps-forum.
I'm not sure about clear audio, but there are audio mods for cm, maybe those can do the job too.
chromecast problem
Someone managed to screencast to google chromecast with CM12.1?
I tried, and it did not work,
I have another device with stock Android and it works great.
There are any solutions to the problem?
Using the latest nightly from november 14 I experience a huge battery drain, about 4% idle. BBS tells ne I have a kernel wakelock from "lm_work_queue".
Does anyone know what it is and how to fix it?
Edit: the phone never gets into deep sleep
Nevermind, no problems left with nightly from nov. 20
The sensors are not working well
Sometimes they do and sometimes they don't also camera buttons functions are not working ( like turning on the screen by half pressing the camera button)
Media Server eat battery as hell. 23% in 1.5 hours of listening music with off screen.
On LP 5.1 Milestone 2 release and even nightlies from CM12 (clean install)
Audio output from speaker (not speaker on the back but the one that you hold up to your ear) when making calls doesn't work using the Phone app.
I don't know why.
All other audio works (from rear speaker, not ear speaker thing).
XPERIA_ZL_IL said:
Someone managed to screencast to google chromecast with CM12.1?
I tried, and it did not work,
I have another device with stock Android and it works great.
There are any solutions to the problem?
Click to expand...
Click to collapse
Not working too, and mhl does not working too.
CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 13.0 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y) by CTXz and hennymcc.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Internal Root
Brightness slider
Option to use soft keys
Additional settings (Buttons menu in settings)
HW accelerated GUI
Camera (pictures+video: Back+Front)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Lock Screen
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Multi-Window support (new experimental CM setting, can be enabled via developer settings)
Fingerprint scanner
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
The newest CM 13.0 releases as well as the latest TWRP can be found here:
https://aykevl.nl/android
-Credit and thanks to @ayke
CM 13.0 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 6.0, one of the following two is recommended:
Open GApps Project, Platform:ARM, Android:6.0, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 13.0.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 13.0 ROM zip-package
Install the GApps zip-package
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
25/03/2016:
* USB OTG disabled by default for improved waterproofness (can be re-actived via Advanced Settings App)
* how to enable USB OTG:
* start the "Advanced Settings" App
* open the "USB-OTG Mode" setting
* select "Powered (Not waterproof)"
* add support for call recording
* how to record a call:
* start/Receive a call with the CM Dialer App
* During call open settings (icon: three vertical dots)
* Select "record call"
* (if you get an error message that recording failed, try to enable developer settings and enable root access for apps+adb)
* how to playback recorded call:
* open the call history in the Dialer app (icon: clock symbol)
* open details of recorded call
* in the detailed calling list, click on the play button for the recorded call
* removing fingerprints works now
* updated some stock libs with LP versions
* support for F2FS (needs new TWRP recovery)
* updated TWRP recovery (with F2FS support)
* synch with latest CM sources
22/02/2016:
* Fixed lock-screen freeze
* Fixed Infrared support
* Fixed search for mobile networks (search will take ~1min until results are shown)
* Updated some libs with LP versions
* Initial support for a fingerprint scanner
* Sync with CM sources
16/02/2016:
* Fixed camera problems with WhatsApp
* Fixed preferred radio family settings (LTE/GSM/...)
* Added default long-press actions for home and app-switch buttons (DJSteve)
* Switched to LP kernel (G800FXXU1BOL4)
* libsensors: replaced with open source implementation (fixes light sensor which is needed for auto-brightness)
* Preliminary (and very inaccurate) support for heart-rate sensor
* Update to TWRP 3.0 (TWRP 2.x will still work)
* Sync with CM sources
30/01/2016:
* Fixed BT calling problems (only noise)
* CM Camera replaced with CM Snap Camera
* better image quality (check picture quality settings), resulting in image file sizes of > 1MB instead of 200KB
* Saving images to SD card supported (check settings)
* Improved RIL support
* Use stock soft-key layout (left capacitive button is app-switch instead of menu now)
* Key-layout can be configured via button settings.
* Fixed adb root problem (root permissions were lost after reboot)
* SamsungServiceMode app works now
* Sync with CM sources
14/01/2016:
* Add soft keys option under settings > buttons
* Fix crash after hanging up call
* Sync with newest CM sources
31/12/2015:
* Receiving calls works now
* psyafter: SD-Card can be used as internal storage (new Android M feature).
Can be used to store photos on SD-Card.
IMPORTANT: the SD-Card will be formatted if you activate this feature.
* GPS works now
* Sensors work now (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter).
Light and Pulse sensors do not work yet.
* Youtube/Screencast crash fixed
26/12/2015:
* Wifi and Mobile Data work
20/12/2015 Hennymcc :
* Audio Fix
- Audio is now working (Still a bit quiet though)
- Making Calls is now working
14/12/2015 Hennymcc, CTXz :
* 6.0.1
- Updated to Android 6.0.1
- Fixed reboot when locking phone
- Fixed Internal Root in developer options not working
30/10/2015 CTXz :
* Added 'Buttons' settings
- Integrated Buttons/Capacitive Keys menu into settings
- Double tapping or holding button to open camera now works (In CM12 it didn't work)
- Power Menu is added under buttons menu
- Minor fixes
-!- NOTE : Setup Wizard may have some issues/crashes with this build. I will exclude it in the next one
29/10/2015 CTXz :
* Synced to newest sources
- Ugly looking Google search box removed
28/10/2015 CTXz :
* Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
28/10/2015 hennymcc:
* First CM 13.0 test-build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz for his awesome work on getting Marshmallow to the G800F
Thanks to spookcity138 and ayke for providing new builds of this ROM.
Thanks to Psyafter for some patches and working on the G800F.
Thanks to Unjustified Dev from Team Regular for the initial work to get the G800F ready with CM.
XDA:DevDB Information
[G800F/M/Y][ROM][6.0][MHC19J] CyanogenMod 13.0 for G800F/M/Y [Beta 25/03/2016] [eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, Unjustified Dev, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-10-28
Last Updated 2017-01-26
If you already flashed stock LP, you will get the following message on boot:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
If you wait for some seconds (or press some buttons) the message text turns blue:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
and after some seconds (or buttons presses) CM will start.
Reserved
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
$wap said:
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
Click to expand...
Click to collapse
Ditto!
Sent from my SM-G800F using XDA Premium HD app
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
hennymcc said:
This is just a test build.
At the moment you have to flash the following boot.img with Odin after installing CM 13:
https://www.androidfilehost.com/?fid=24052804347848059
CM 13 may reboot after the initial configuration and may not be able to start again. I wiped the data partition and started again. This time it worked without a reboot (I also choose English as language and did not configure Wifi).
Click to expand...
Click to collapse
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
n3n00 said:
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
Click to expand...
Click to collapse
CM13 is for people that enjoy its minor speed boost, smoother animations, cool new features and less Android related bugs over Lollipop. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
CTXz said:
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
CM13 is for people that enjoy its speed and less internal bugs. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
Click to expand...
Click to collapse
Hi, so you think it will be easier to make a CM13 version with less bugs than the unfinished CM12 (Yes / No) ?
I enjoy to use a rom for every day not just having the last version to amaze my friends...
Depends. What I know for sure is that bugs related to Lollipop will be fixed. However we are hoping to get it as stable as cm12 if not more
Screehots
Screenshots with phone frame
Screenshots within Android
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
WarStars said:
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
Click to expand...
Click to collapse
We didn't build the correct RIL yet but it should be working in hopefully only few builds
New update
Download link has been updated
Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
Also for anyone asking if there are really some differences in Marshmallow compared to Lollipop. Yes, the animations are allot smoother. There are some new native features. It has cleaned the mess of Lollipop's Android related bugs and is what Lollipop should have been from begin on. It is snappier than Lollipop and I can see/feel that. You may have realized that gingerbread-ish google toolbar. This is CM13 related since the official CyanogenMod 13 source is still in beta. However we no longer have the problem that the toolbar is laggy, instead it has a smooth animation when selecting it.
Could you please give some information when the RIL is done? Thank you in advance.
WarStars said:
Could you please give some information when the RIL is done? Thank you in advance.
Click to expand...
Click to collapse
It's on our priority list so hopefully soon
You know I have both the G800H and the G800F (the camera bug on the G800H prompted me to get the G800F), and now I don't know which one I should get rid of... I know, I know: "hard problem there KC... ya bloody wanker"
CTXz said:
It's on our priority list so hopefully soon
Click to expand...
Click to collapse
Awesome job so far, guys!
Sent from my SM-G800F using XDA Premium HD app
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
CTXz said:
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
Click to expand...
Click to collapse
Working features from page 1 still the same for this new build?
Sent from my SM-G800F using XDA Premium HD app
Mobile connections working now?
CyanogenMod 14.1 is a free, community built, aftermarket firmware distribution of Android 7.1.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Other Issues Not in Known Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), use adb or any other file explorer tool to pull a copy of
/sys/fs/pstore/console-ramoops (command: adb pull /sys/fs/pstore/console-ramoops)
after the reboot and provide that.
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)
Download Links
CyanogenMod: ROM @ http://download.crpalmer.org/nightlies/pme-cm-14.1/
Google apps addon:
We are using Open GApps (Link) Arm64 version. (make sure to use 64bit when using other packages), others might also be working and make sure you download the right version. I do not recommend stock or full or anything that replaces default apps as this has been known to cause problems (e.g. replacing the dialer with a stock dialer can make it crash).
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow or later ROM. Do not boot with an older gapps or without one and then try to install it later.
Note: If you install a package which replaces the default dialer (mostly "Stock Gapps") you have to go to Settings->Apps->Gear-Icon and set the new dialer as a default telephony app to prevent force closing of apps
Known Issues
SELinux is in permissive mode
Bluetooth headsets do not work for wide band voice calls (narrow band calls work)
LiveDisplay doesn't work
LED notification settings are available but don't work
Home "button" cannot be disabled, even when using virtual keys
Home "button" cannot be long pressed
Fingerprint sensor does not work if you are on M firmware
Magnet detection/Ice View not working
Rear Camera Force Closes when enabling HDR (? is this a problem on N, I haven't tested it)
If you encounter any other issues, please let me know with:
logs
steps to reproduce
carrier
firmware: stock M or N as your last RUU/official update
problems reported without all of this information will usually be ignored and even occasionally flamed...
XDA:DevDB Information
CyanogenMod 14.1, ROM for the HTC 10
Contributors
crpalmer
Source Code: https://github.com/CyanogenMod/android_kernel_htc_msm8996
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-17
Last Updated 2016-12-29
Reserved
Reserved
About to try this new one with firmware 401.9 Nougat...is tested for that firmware or it's only for M firmware?
--anx-- said:
About to try this new one with firmware 401.9 Nougat...is tested for that firmware or it's only for M firmware?
Click to expand...
Click to collapse
I am using N firmware.
crpalmer said:
I am using N firmware.
Click to expand...
Click to collapse
...and that's what I wanted to hear...:laugh:
Just the time to install it and stock opengapps...
---------- Post added at 04:54 PM ---------- Previous post was at 04:06 PM ----------
Fingerprints and home button don't work...Had to flash a fix zip in order to let home and FP go ok.
Audio is ok.
Don't know about GPS, but it seems to be ok...
Pretty solid release, at least my first impression.
there it comes . 14.1 hit much earlier than 13
Is woofer working?
And no audio from play music app and cm music ...From YouTube yes.
Woofer ok. GPS I doubt.
Maybe the audio from music wasn't fixed yet...
--anx-- said:
And no audio from play music app and cm music ...From YouTube yes.
Woofer ok. GPS I doubt.
Maybe the audio from music wasn't fixed yet...
Click to expand...
Click to collapse
Audio is working perfectly for me (except for headphones which will be fixed in the next build). YouTube and Google Play Music.
GPS is working perfectly for me.
What firmware are you running and please provide logs (and steps to reproduce, which you did) or else I tend to ignore your report of something not working...
Thx for your work @crpalmer..
3MK744070S306872R
??
crpalmer said:
Audio is working perfectly for me (except for headphones which will be fixed in the next build). YouTube and Google Play Music.
GPS is working perfectly for me.
What firmware are you running and please provide logs (and steps to reproduce, which you did) or else I tend to ignore your report of something not working...
Click to expand...
Click to collapse
i am on MM firmware , my condition is same as you said . headphone fix and its done , 14.1 done. nice job man .
crpalmer said:
Audio is working perfectly for me (except for headphones which will be fixed in the next build). YouTube and Google Play Music.
GPS is working perfectly for me.
What firmware are you running and please provide logs (and steps to reproduce, which you did) or else I tend to ignore your report of something not working...
Click to expand...
Click to collapse
Firmware 2.28.401.9 on HTC 10 International (HTC__001) running Italian operator. The one with no red text, posted in the news and guide section.
I've installed rom, fpfix.zip in order to have home and FP works, and after that STOCK gapps pack, latest.
EDIT:
This is the logcat.
Steps: booted first, initial settings, 2 updates from play store and then immediately into play music. Only one song plays, everything else not.
Choosen ONLY DOWNLOADED MUSIC for having only SD songs.
--anx-- said:
Firmware 2.28.401.9 on HTC 10 International (HTC__001) running Italian operator.
Click to expand...
Click to collapse
Hey, try with some FLACs? I got FLACs to work but not MP3s.
Posted logcat into previous post.
Not flaming, as you can see...but only trying to understand why music won't play...
Camera crash on startup after enableing power shutter
Open camera > Swipe from left to open menu > Click on settings > Advanced > Enable "Power shutter" > Swipe Camera app from recents > Open camera > Crash
Clearing Camera app data makes it work again.
Carrier: Vodafone Germany
Firmware: 1.95.401.5 MM
--anx-- said:
Firmware 2.28.401.9 on HTC 10 International (HTC__001) running Italian operator. The one with no red text, posted in the news and guide section.
I've installed rom, fpfix.zip in order to have home and FP works, and after that STOCK gapps pack, latest.
EDIT:
This is the logcat.
Steps: booted first, initial settings, 2 updates from play store and then immediately into play music. Only one song plays, everything else not.
Choosen ONLY DOWNLOADED MUSIC for having only SD songs.
Click to expand...
Click to collapse
Try with viper4aries-for me fixed Google Play music.
--anx-- said:
Posted logcat into previous post.
Not flaming, as you can see...but only trying to understand why music won't play...
Click to expand...
Click to collapse
To get a meaningful logcat, you need to enable root in developer options. Without it, it looks like all you get is the logcat generated by the program itself and not the system messages.
Strange but I've enabled root... Ran the first time and saw from options that was required root for additional info, so I've enabled it and then done again same steps...
dj_chapz said:
Camera crash on startup after enableing power shutter
Open camera > Swipe from left to open menu > Click on settings > Advanced > Enable "Power shutter" > Swipe Camera app from recents > Open camera > Crash
Clearing Camera app data makes it work again.
Carrier: Vodafone Germany
Firmware: 1.95.401.5 MM
Click to expand...
Click to collapse
I don't have much practice with reading logs, but I found this:
Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.SecurityException: No permission to prevent power key: Neither user 10050 nor current process has android.permission.PREVENT_POWER_KEY.
It seems to be a permission issue? Maybe the app doesn't have that permission declared, it isn't granted, or something similar? crpalmer will probably know.
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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/odin
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/odin/
About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
Device tree : https://github.com/fusion3-common/android_device_sony_Odin/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
[/INDENT]
LineageOS available for Odin also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZL, ROM for the Sony Xperia ZL
Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2017-07-17
Last Updated 2017-11-10
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Fully enforced
Thanks and good luck on getting this official.
Thanks for your hard work,it works fine
Successfully upgraded from Chippa_a's unofficial Lineage 170413 build without wipe. Thanks.
after bootind in recovery (twrp), wiped cache and data, flashed the zip lineage-14.1-20170716-UNOFFICIAL-odin.zip and open_gapps-arm-7.1-mini-20170722.zip and rebooted. After that, only black screen and no boot into system, only fastboot or flash mode...
previously using a stock rom in 5.1.1 with root and recovery.
any help?
ps: after that, tried to flash the boot.img in fast boot mode, get this error:
>fastboot flash boot c:\boot.img
sending 'boot' (14972 KB)...
OKAY [ 0.293s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.297s
PS 2: tried flashing a ftf via flashtool, but get some errors too...
23/036/2017 18:36:01 - INFO - Opening device for R/W
23/036/2017 18:36:03 - INFO - Reading device information
23/036/2017 18:36:12 - INFO - Unable to read from phone after having opened it.
23/036/2017 18:36:12 - INFO - trying to continue anyway
23/036/2017 18:36:12 - INFO - Phone ready for flashmode operations.
23/036/2017 18:36:12 - INFO - Opening TA partition 2
23/036/2017 18:36:12 - INFO - Start Flashing
23/036/2017 18:36:12 - INFO - No loader in the bundle. Searching for one
23/036/2017 18:36:16 - INFO - Processing loader.sin
23/036/2017 18:36:16 - INFO - Checking header
23/036/2017 18:36:16 - ERROR - Processing of loader.sin finished with errors.
23/036/2017 18:36:16 - INFO - Ending flash session
23/036/2017 18:36:16 - ERROR - Error in processHeader : 22 : O dispositivo não reconhece o comando.
23/036/2017 18:36:16 - ERROR - Error flashing. Aborted
23/036/2017 18:36:16 - INFO - Device disconnected
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
NamenIos said:
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
Click to expand...
Click to collapse
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that
and now, i can´t even boot to recovery. tried to flash recovery.img through fastboot with no success...
saddambea said:
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that...
Click to expand...
Click to collapse
What error did you get? Maybe you have to go back to stock via flashtool for this.
saddambea said:
... and now, i can´t even boot to recovery.
Click to expand...
Click to collapse
This should be normal if you used Dual Recovery on the stock rom before. Dualrecovery is on the /system partition, that you wiped while flashing.
saddambea said:
... tried to flash recovery.img through fastboot with no success...
Click to expand...
Click to collapse
This can't work as we don't have have a recovery partition. Our recovery is either in the boot.img or the system partition. LineageOS uses the boot.img and optionally then boots the recovery in the FOTA Kernel partition if you press vol up.
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Thank you Daedroza!
You're a scholar and a gentleman. Gimme a week or so ( I am caught up with assignments and exams ) and i will have a look at it...
I'm pretty sure it will be a super stable build as always...
I am already running a Chippa's build with some changes to the XML audio if i am not wrong, and i could already hear some improvements.
The notifications remained very low though... I think the EU specific limitation for the audio needs to be commented / removed in order to see serious improvements .
Kind regards
Gorilla no Baka
Daedroza said:
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Click to expand...
Click to collapse
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Linwood.Ferguson said:
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Click to expand...
Click to collapse
- No idea about phone coverage. I had preferred if you could do a diff with signal measuring app or something of sort? That would give you a base stock result and one from Lineage.
- The phone's display gets slow / laggy / unresponsive systemwide or it just the apps? Maybe both the apps consume a lot of space on internal and cache. Hence you need to clear them.
On the original firmware there was a dialer code to show usable bands; it does not work on LineageOS. I have tried without success to find a way to tell which bands are supported in the current OS. With some playstore apps I can see the current band but not all usable bands.
The original C6506 (odin rimy) documentation listed the bands available, and compared to the C6503 (odin gina). There are a number of differences. The C6506 supports LTE I, IV and XVII that the C6503 does not; the C6503 supports LTE III, VII, VIII and XX that the C6506 does not. My understanding (but I am not certain) is that this is a hardware limitation of the device, which of course corresponds to the stock firmware. It could also be that the radios are the same, but the restriction on bands was purely in software tied to the model.
My reading of old postings on the cynogenmod software was it was based on the C6503, and so my question is what is the result. It seems POSSIBLE that it only then supports the bands they had in common: LTE I and V, which leaves a lot missing. Or it is also POSSIBLE that it supports all the C6503 bands which (again, my loose understanding) were not ideal for US/AT&T use, which is what the C6506 was fo.
Basically I know only enough to wonder if the LineageOS is limiting the bands the phone can use? And how I might tell for sure? And/or if you have all the source, can you tell, or is this buried in the blobs that are opaque?
As to the laggy: I think it is the whole system, but it is hard to say as I'm generally using some app. They do begin to start up slower as well as operate slower, but it is most noticeable on things that scroll. Frankly I would likely not notice other slowness if the scrolling did not hesitate. A list of stories in the CNN app, for example, if you touch and start scrolling hesitates nearly a second before it moves. Clear dalvik and there's no hesitation. It is also worth noting I use very little on the phone - mail, CNN, News360, weatherbug, calendar, and the phone are just about it. All visible resources (that I know how to look at) show lots of free space. Now that I know how to quickly fix it not a big deal.
Does the IR blaster work with this build? Does it work with other apps like Anymote?
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS (see here). You have to check which bands your provider uses in your region and then use an app to check if you get connected to which band, I don't think there is an alternative. The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
edit:
JLBouras said:
Does the IR blaster work with this build? Does it work with other apps like Anymote?
Click to expand...
Click to collapse
Only with one app (the one that worked on CM13), root access and selinux disabled, we have to add file permissions, ownership and selinux rules. This is not yet tested enough though. edit: Just tested with selinux disabled, works well with preconfigured remotes, slightly flaky when learning imo.
NamenIos said:
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS ....
The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Click to expand...
Click to collapse
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503. Does the software incorporated within LineageOS support all bands listed in the partition mentioned?
I tried to find the old discussion I remember without success. Closest I got was this which brings it up (look for "bands"), but people are saying "mine works". The issue of course is if some bands work but not others the phone may "work" but not have the same coverage where you have less bands or more congestion.
I was hoping there was a way to actually query the phone for which have actual hardware+software support, but it sounds like there no longer exists that ability with the loss of that service menu.
NamenIos said:
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
Click to expand...
Click to collapse
Frankly it may have been the same there. I'm wondering if, being news related apps I use most, if they are leaking/cluttering up the cache in some way more than normal use (Dalvik is for the VM, right? Do apps cache data there or just the VM cache app code there?). Regardless, I have an easy workaround, it takes just a few minutes to clear and get back fully up.
I absolutely agree getting fully supported is great. I hope to get a Pixel2 when they come out, and leave this as a backup phone, so would love to get a few more years utility out of it. It's been a really great phone, I still rarely see any with the low percentage of wasted space on the front as this.
Linwood.Ferguson said:
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503.
Click to expand...
Click to collapse
Modem partitions are not affected in case of installation of LineageOS/CyanogenMod. This ROM is universal for all models (C6502/6503/6506).
NamenIos said:
The supported bands are stored in partitions not touched by LineageOS
Click to expand...
Click to collapse
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Daedroza said:
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Click to expand...
Click to collapse
And just a day later, August Security Patches was released...