CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
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.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls (the first ingoing call seems to have no sound)
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
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)
CM 14.1 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, 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 14.1.
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 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:
07/11/2016:
* Initial 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, Psyafter, spookcity138 and ayke for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NDE63P] CyanogenMod 14.1 for G800F/M/Y [Test 07/11/2016][eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-07
Last Updated 2017-02-01
Reserved
This is just a test build. CM 14.1 is not released yet and still instable. There are lots of known issues.
Here a short list of known problems:
First incoming call has no sound
Camera app crashes when you try to switch between camera and video recording mode (in this case: restart the app and recording will work)
Messages with "Browser crashed" will occur from time to time
The default browser does not always display all the text that was typed into a text field.
This was an awesome ROM but now I propose LineageOS 14.1
It works perfect (at least until now) for me ? great job
I hope @ayke brings OTA updates here to make everything easier
Enviado desde mi SM-G800F mediante Tapatalk
This rom is really great! Smooth and without big issues. Everything works as you said and here are some screenshots of Antutu if someone need them. Thanks devs!
What's the problem with first income call? The first one is the only one with no sound?
Great job Henny
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
what about battery drain?
sgilyin said:
what about battery drain?
Click to expand...
Click to collapse
seems normal so far
is this normal?
CostasGr said:
seems normal so far
Click to expand...
Click to collapse
With my usage yes.
The only problem is robotic voice
Hey !
Thanks for your amazing job (all of you), I don't have any browser crashes since I use chrome and I remove the stock browser, I also don't have any crash with my camera. I use Google Camera for that. Here is a list of bugs I've noticed:
- Chrome (stable) has crashed the first time I've opened it (only one time, that's why I did say that I don't have any browser crashes)
- Sometimes, something like "MTP Host" crashes..
- In Allo, while sending a message, there's a little sound, that's not a bug since it's in the app... But that sound is garbled (I don't know if that word is correct, I've used Google Translate for it)
I guess that's all..
Also, I don't have robotic voice... Good bye ! And thanks again
EDIT: About the "MTP Host" app.. it's the download app :/
Bugs
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?
Anyone have the link for xposed framework of this version?
Thomzey said:
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?
Click to expand...
Click to collapse
I also experienced that with some internet players when watching HD content..
Enviado desde mi SM-G800F mediante Tapatalk
CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk
spookcity138 said:
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
You had changed the device tree as I remember and you fixed it last time ( I might be wrong I have no idea about developing) anyhow any help would be awesome because I need my phone for my work so I cant have that robotic voice... Thank you
Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76
Sunn76 said:
Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76
Click to expand...
Click to collapse
Most oft the current issues are Cm related so the CM-Team needs to update their sources time by time
Sent from my SM-G800F using XDA-Developers mobile app
Related
Unofficial CM 10 for HTC Desire 300 (g3u)
device_htc_g3u v0.8b (24/12/15)
Traded stagefright bug for a new kernel
(no more stagefright and a freshly compiled kernel)
device_htc_g3u v0.77b3 (04/10/14)
Battery comsumption (hot)fix
(rls should no longer drain your device)
device_htc_g3u v0.77b2 (01/10/14)
Wifi is working
(wifi0 is forced into compliance)
device_htc_g3u v0.77b (25/9/14)
jellybean
(nom nom nom)
Full Disclosure
This is my first android project, so go easy on me.
Project Status
It's usable as a phone
So any willing beta testers are welcome to join the 'fun' and report further bugs.
Project !Status
mobiledata works but will drain your battery
(if you need to use it, reboot after switching it off)
libaudio is not fully functional
(stock has no mic unless in a call and custom has no speaker)
USB only works in mtp mode
(mass_storage mode appears to be incompatible with rmt_storage)
FM Radio not available
(required apps are currently not compiling)
Camera (front) appears unstable
(didn't bother to check what might be the cause)
TODO
[high priority]
fix libaudio (recording in stock or speaker in custom)
[medium priority]
fix libril -> mobile data drains the battery
[low priority]
enable apps2sd -> 2GB internal should suffice for the time being
check if cm supports proximity & light sensors -> they do work fine
fix mass_storage -> mtp is working
fix video recording -> it's a phone not a camcorder
fix video playback -> at least they are running
fix camera -> it's a phone dammit
find a better fix for wifi -> it works for now
fix graphical glitches
Disclaimer
Use at you own risk. This is a public beta and not meant for daily use. Please keep that in mind.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Requirements
HTC Desire 300 with unlocked Bootloader and custom recovery
(S-ON or S-OFF does not matter)
Download
Click me if you want the initial wifi free version (9d0a8fcca957d09dbaf306a1986d14dd)
Click me if you want to drain your battery (688c2779b4864ed9b568260477708049)
Click me if you like the stock kernel (1ba8a225bc7772f34f1e56bff51bfe27)
Click me if you dare (78bbcf5bf0eb26520efff6d49adac106)
Warning!!! If you are not a certified beta tester the zip file might explode upon extraction!!! You have been warned!
Installation
Enter recovery and begin by backing up your current system.
Next choose Wipe Data / Factory Reset from the main menu and Wipe Dalvic from the advanced submenu.
Last but not least use the mount submenu to format system.
Now use sideload or zip install to start beta testing this tasty jellybean.
Special Thanks
go out to anyone who has ever contributed something to a msm8225, ath6kl or htc related android project
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(My mind is a swirling miasma of scintillating thoughts and turgid ideas.)
What are the requirements ? I guess I should use the only recovery available for the device ? and also, since we don't have s-off working for this device I think we have to flash the boot.img right ?
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
I'm downloading the files now, will test and report ASAP
Can i promote this in 2 german Forums? ist German translation available?
when do you think you will fix wifi?
HUGE THANKS IN FORWARD FOR COMPILING CM!
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
4m8 said:
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
Click to expand...
Click to collapse
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
bassam_tayyan said:
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
Click to expand...
Click to collapse
Ah yes FM. It's included in the custom libaudio that can't connect to the speaker.
Which I currently simply replace with the stock lib to make it work as a phone so it can be used to test battery consuption etc.
Sadly the cm apps used for fm won't compile for me. So even if I get libaudio working FM would still be untestable without non cm apps.
I'll add it to the todo once the libaudio trouble is resolved.
The wifi is an annoying issue. I manged to get it to load the drivers so the p2p0 socket gets created.
But it tries to restart it as STA which if my google fu is correct it shouldn't do, since this firmware does not need restarting.
The front camera is a curious bug. It works absoluetly fine for me until I point it towards my face.
So it's either a problem with the proximity sensor or the nasty htc camera tries some facial recognition crap and dies.
If I ever decide to logcat the camera I can tell you more.
Now for a higher version, don't get your hopes up. At least not from my side.
First I'll try my best to fix this up. Then I'll wait for htc to release the kernel so I can get a closer look at the configuration
for this device and maybe adjust it to make this rom even better. Then again the last kernel I compiled was 10 years ago for a gentoo install.
LukeHorizon said:
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
Click to expand...
Click to collapse
If you are quick it will install fine. So if you prefer to live dangereously, don't let me stop you
I don't know if it is only an error that is presented on my device. Or maybe it was updated since then.
But for me philz recovery by SPSPawn does boot into a dead state. If you reboot it will crash until a panic reset is triggered.
Actually it is allready crashed while you are in recovery. Therefore you are on a timer until the device resets or you decide to
take out the battery.
I had the same problem on my build and it was caused by cwm always ignoring the ueventd.rc I had prepared because I didn't know
I had to copy it to root and not to recovery.
I've never bothered to figure out which missing element of this script was responsible because I had to substitute it in any case.
But honestly, tell me. Why do you prefer philz? I'm allready (so far unsuccessfully) trying to port twrp. If you have a few good arguments
I might be willing to try compiling a fixed version of philz aswell.
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
LukeHorizon said:
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
Click to expand...
Click to collapse
It always tried to download the google language pack for my region until I aborted it. So, yes mobile data should be available.
You mean put the recovery into an update zip thingy, right. Well I could, but you will have used a pc before I'll find the time to upload it.
I'll keep it in consideration for the next update.
Well, atleast internet
When do you think you'll fix wifi?
Regarding to wifi, it will be fixed once it's fixed. Or if you prefer the usual response: When it's done.
This will happen either after or before libaudio is fixed. And that's about as specific as I can get.
Well, it was worth a try still thanks for your effort!
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
Overall very nice, keep up the good work!
luxb said:
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
Overall very nice, keep up the good work!
Click to expand...
Click to collapse
I guess wifi isnt working for you right?
It's not working, but I didn't put it on the list since he already knows it's bugged.
Well, i'll try today
Lets see what happens
Anyway, forgot to unpack the file ... GApps come with it?
SOOO, booting went fine, working like a charm... quicksettings page not available, quicksettings bar is working properly
Mobile Data works flawless, and i guess the rest is just fine
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
I'd like to promote it in German forums if i WiFi is fixed in near future
regards!
LukeHorizon said:
[...]
GApps come with it?
[...]
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
[...]
Click to expand...
Click to collapse
No, you have to get gapps on your own. Since there are multiple options you can choose for yourself. But if you did not format system,
as I've mentioned in the install instructions, chances are high that google apps did get picked up by the install script.
I am not sure if it can take them from the stock rom but it can and will take them from a cm rom and keep them on reinstall.
(I am really not very pleased by this behavior!)
I also should have mentioned that the primary language is decided by the simcard. (Which is annoying since I prefer english in any case)
Randnotiz:
Es freut mich das ich Dir den Spass am Gerät zurückgeben konnte.
Natürlich darfst Du es in deutschen Foren weiterverbreiten sobald die gröbsten Fehler behoben sind.
Einzige Vorraussetzung ist, daß Du es nicht als Deine Arbeit ausgibst.
luxb said:
[...]
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
[...]
Click to expand...
Click to collapse
Wow. That's much more broken than I expected it to be. Kudos.
Regarding the sensors. I currently am using the stock lib. And logcat let's me assume that they are working as they should.
(i.e they don't crash or drift into madness afaik)
Maybe the stock lib doesn't play well with cm, or you are expecting features from cm that are not implemented.
I will definetly try to compile a working sensor lib in the future, so I guess we'll see....
Camera is also just the stock lib for now. So it's no surprise that somethings might be acting up.
I need a lot of research into that subject before I can specify the requirements for the camera in my boardconfig.
The graphical glitches are rather minor and can be ignored for now. I am aware they exist.
But for now I'd rather focus on the more prominent broken features.
Like wireless for those of us that can't or won't use mobile data. (I belong to the 2nd group)
I noticed the signal indicator aswell. but that should be a problem of the radio compatibility.
We can't flash radio and I'm using the stock libril as the radio interface which should give maximum compatibility in theory.
Of course it doesn't irl... typical -_- (I hate you, Murphy!)
Sidenote:
Why did you remove your avatar? I really wanted to make some "stop trying to kill spoderman" remark...
@all:
Does anyone have any clue how to use the mock locations for gps? They are enabled, but so far I couldn't find any way to set them to a specific location.
XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd
reserved
reserved 2
Does safety net pass with or without magisk?
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?
Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.
hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?
Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~
RevengeOS for LG V30
RevengeOS is an aftermarket firmware based on AOSP. We are dedicated to a beautiful, fast, stable and minimal customized ROM, honesty and communication with our users, and openness with our code, Hope you will enjoy.
Known Bugs:
Guide on AOSP ROMs, troubleshooting & recommendations
XDA doesn't allow Telegram and a few other site links so I'm taking down the thread as I don't want to post an incomplete guide. You may find the full guide here: https://bit.ly/3rGKKtQ , this will be the only place I maintain bugs and guides.
forum.xda-developers.com
Changelog:
- March Security Patch
- fixed USB issues(Android Auto, lsusb not detecting an id)
Download:
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Thanks to
@SGCMarkus for his device trees
Telegram Group:
LG V30
You can view and join @LGEV30 right away.
t.me
XDA:DevDB Information
[ROM] [Unofficial] RevengeOS 4.0 [11.0] [V30], ROM for the LG V30
Contributors
supremmotu, SGCMarkus
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Pie Blobs from Stock
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 3.2
Stable Release Date: 2020-08-22
Created 2020-08-22
Last Updated 2020-08-22
Does volte or vowifi work?
markdcouto said:
Does volte or vowifi work?
Click to expand...
Click to collapse
Of course not. No V30 LOS-based ROM has VoLTE and never will. That has to be present in the V30 parent LOS tree, and that Dev says it's basically impossible. So, it will never be a feature in a ROM based on V30 LOS. It's only possible in V30 stock-based custom ROMs like A.I.X.
Here's the V30 Custom ROMs FAQ -- which is linked in the WTF Instructions to read before you actually bootloader unlocked your phone. See #5.
RevengeOS 4.0 [11.0]
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Changelog:
- March Security Patch
- fixed USB issues(Android Auto, lsusb not detecting an id)
Download:
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Thanks to
@SGCMarkus for his device trees
Telegram Group:
LG V30
You can view and join @LGEV30 right away.
t.me
can you use microg with this rom?
I really like the build and speed of this. WiFi worked right out the gate which is what prompted me to ditch trying to get Android 10 working. The ROM doesnt include any of the google apps so I used NikGapps to get the store and things working.
The issue is that any games or apps request that i use the google play services which is already installed and running. Not sure how to overcome this. Anyone else have this problem and perhaps a solution?
Edit: Nevermind. I used the unofficial open gapps and it worked fine. I included it in the zip queue from TWRP when i flashed the rom. I did the following:
Manually wipe (format) your System partition
Flash your ROM
Flash Open GApps package
Wipe the Dalvik & cache
Reboot
Is it good for a daily?
@supremmotu
supremmotu
Any way you could upload the ROM to another file hosting service such as mega? When I try to download from the link it says there have been too many downloads in the past 24-hours.
Can't wait to test out Android 11 on this excellent device.
Edit: I was able to get through and download it
Can this rom work on korean Version?
V300L30p bootloader unlocker and twrp running.
packyman said:
Can this rom work on korean Version?
V300L30p bootloader unlocker and twrp running.
Click to expand...
Click to collapse
yes
So far so good (US998) - Wifi works, cell service works, GPS seems to work, tethering works. I'm running Magisk v22 fine, I installed Magisk App Debug and flashed Magisk-22.zip (just rename the apk to .zip) and MicroG works fine without the need to mess around with signature spoofing.
Edit: I could only get tethering to work from wifi, not mobile data (for internet access)
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way. I tried using a 3rd party app Always On Edge, but it uses too much battery to use aside from charging. FM Radio also doesn't work, but that isn't a deal breaker for the newest Android for me.
aventurer said:
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way. I tried using a 3rd party app Always On Edge, but it uses too much battery to use aside from charging. FM Radio also doesn't work, but that isn't a deal breaker for the newest Android for me.
Click to expand...
Click to collapse
Try the Always On AMOLED app from the store. I've been using that for the last year as an alternative to the broken AOD on Android 10. I haven't noticed any significant battery drain, perhaps because, as the name suggests, it's designed for AMOLED displays.
@Osprey00
Ty so much. This app seems a lot better. I had an issue at first where the permissions wouldn't go through, I just killed the app and cache and reloaded then it worked.
It also seemed to drain the battery a ton at first, but then I rebooted my phone and stopped messing with the settings so it seems fine now.
I also was wrong about tethering working, I could only get tethering to work via Wifi, not mobile data for internet, which defeats the purpose, maybe someone has some ideas viewing this?
aventurer said:
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way.
Click to expand...
Click to collapse
Even though you worked around it by using the app that I recommended and may even prefer to continue using it, I just saw this AOD fix on Telegram, credit to ɐoɔɐɾ:
This should fix the black screen bug when waking the device from sleep with aod on
This is tested and confirmed to work on DotOS and LineageOS A11, it is not for A10 and may not work on other A11 roms
Flash this after first boot, may not fix ddtw
Credit to @marvinhrivera for finding this fix
Click to expand...
Click to collapse
Hi, I have just flashed this ROM and it is great so far. Everything works fine exept finger print sensor. I am able to unlock the device etc. but sensor is not accessible in some apps (internet banking, Lastpass). Have you experienced this issue, too? It is a bit annoying, especially for these apps wher biometrics is essential. Thank you.
nekicz said:
Hi, I have just flashed this ROM and it is great so far. Everything works fine exept finger print sensor. I am able to unlock the device etc. but sensor is not accessible in some apps (internet banking, Lastpass). Have you experienced this issue, too? It is a bit annoying, especially for these apps wher biometrics is essential. Thank you.
Click to expand...
Click to collapse
yeah that's a known issue, should be fixed in the next build
sinkoo1979 said:
can you use microg with this rom?
Click to expand...
Click to collapse
Yes. Use the microg settings to grant the spoof permission (tap the unchecked "system spoofs signature" box to trigger the requst) and run
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Thanks for the build, it seems solid. Some minor features (e.g. edge lighting, voicemail notifications) that didn't work on HavocOS for me work out of the box here. There are only two issues so far:
- The styles and wallpapers system app doesn't work: it won't open whether accessed from the launcher or in the settings menu. I can change wall papers and icons using the shortcuts from long pressing on the home screen, but not theme/colors (it crashes if I pick that tab)
- I cannot get file transfer over USB to work; the phone doesn't show up in Windows explorer. It's not my box or cable; the same setup works just fine for USB debugging or file transfer in TWRP. I had the same issue on HavocOS, but there swapping off file transfer and back would trigger detection, but not on this ROM
This ROM has less customization than some (you can't swap the navbar layout, for example) but this looks nice. I'll try this out as a daily driver for a week or two and see.
EsotericScreenName said:
Yes. Use the microg settings to grant the spoof permission (tap the unchecked "system spoofs signature" box to trigger the requst) and run
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Thanks for the build, it seems solid. Some minor features (e.g. edge lighting, voicemail notifications) that didn't work on HavocOS for me work out of the box here. There are only two issues so far:
- The styles and wallpapers system app doesn't work: it won't open whether accessed from the launcher or in the settings menu. I can change wall papers and icons using the shortcuts from long pressing on the home screen, but not theme/colors (it crashes if I pick that tab)
- I cannot get file transfer over USB to work; the phone doesn't show up in Windows explorer. It's not my box or cable; the same setup works just fine for USB debugging or file transfer in TWRP. I had the same issue on HavocOS, but there swapping off file transfer and back would trigger detection, but not on this ROM
This ROM has less customization than some (you can't swap the navbar layout, for example) but this looks nice. I'll try this out as a daily driver for a week or two and see.
Click to expand...
Click to collapse
I fixed the USB issue by doing a reinstall and not using the stock kdz first (flashing directly to a fresh format). According to the dev, the styles app requires GApps, so it won't work if you use microG
I'm also having success with this ROM. I tried a couple of other (A 10 based) ROMs, but couldn't get the wifi to work despite loading old modems etc. Revenge appears to be fully functional (with the exception of spotty fingerprint access as noted above). For me the hotspot also worked straightaway.
Nice rom, simple whit FMradio application.
Installed on a freshly unlocked and rooted H930 with pico Gapps (open_gapps-arm64-11.0-pico-20210130-TEST.zip). But I'm stupid, I saw the instructions afterwards, and I didn't install a recent pie stock rom after the root, I've install directly this rom.
The wifi and USB transfer does not work. The wifi can be fixed with the fix for Android 10 : see here : https://forum.xda-developers.com/t/q-wifi-fix-for-north-american-variants.4012635/post-83473401.
Can I flash a stock rom now? which one?
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions.
I'm using pico/nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Work
almost all
Known Issues
- camera
Links
LineageOS Builds
6. 20210419: april security patch: https://drive.google.com/file/d/1-Lxf_C_K7saHJPgzJj_tSv8J5FfPS468/view?usp=sharing
5. 20201221: december security patch: https://drive.google.com/file/d/1tYzL31kIA9dA3Cpe66h2AUD57kT9r5eY/view?usp=sharing
4. 20200910: latest sources, update kernel, huge audio update (youtube): https://drive.google.com/file/d/1hyn-Q3mkQPjVr2zOBFT2aDEFdR7kkkRJ/view?usp=sharing
3. 20200826: update mixer (mic): https://drive.google.com/file/d/1gOIimcp1rf7BvexhTSOoGURN_oDWq0nT/view?usp=sharing
2. 20200825: update cpu build settings, update power profile, huge kernel update, better clean install: https://drive.google.com/file/d/14XhE-O8Yic8tbJZPcafh8y8w23sDkFno/view?usp=sharing
1. 20200824: init build: https://drive.google.com/file/d/1r7mSz2BIeA2B0pqvUW24dOwO0FC0OWtu/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Recovery
Use official version from: https://twrp.me/samsung/samsunggalaxynotepro122exynoswifi.html
Root
Install latest magisk from: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to LineageOS team
As you promised in your technical preview version , thanks a lot :good: will install it and give feedback
Many thanks @Valera1978.
Cleanly flashed with Data format used the TWRP 3.3.1-0 like for LOS16, instead of 3.4.0-0 with BiTGapps and Magisk.
No more unwanted appearences on the screen when turning. :good:
When focussing on a text the field now shows the letters. :good:
Camera, as you wrote, not working at all. so what
Will carry on testing.
LOS16 will be abandoned, or not?
Is there any battery efficiency improvements with these updates?
Running LOS 14 without gapps -1% per minute. Using the tablet as a remote mouse/keyboard for pc
bmwdroid said:
Many thanks @Valera1978.
Cleanly flashed with Data format used the TWRP 3.3.1-0 like for LOS16, instead of 3.4.0-0 with BiTGapps and Magisk.
No more unwanted appearences on the screen when turning. :good:
When focussing on a text the field now shows the letters. :good:
Camera, as you wrote, not working at all. so what
Will carry on testing.
LOS16 will be abandoned, or not?
Click to expand...
Click to collapse
I think yes. start to the los 16 was done for several reasons:
- I had the experience of switching to the android 10 on 3 different series (exynos7870, qcom800 and qcom820) - in all cases with working android 9 it was a huge number of problems, switch to android 10 I think the most difficult in my memory
- Old device config, every new version has some problems, so it was easier to jump from working 14.1 to 16.0
- faster build 16 minutes on my computer for los 16 vs 26 minutes
Right now in the los 16 we have more problems, then in los 17, and i don't see any reason to spend a weeks for fix it. Better focus on los 17 for some code clean up.
I can live with the death of LOS16 very well.
Having your LOS17 on my T325 as well and I love it.
Btw. Firefox has still the same problems while other browsers work.
bmwdroid said:
I can live with the death of LOS16 very well.
Having your LOS17 on my T325 as well and I love it.
Btw. Firefox has still the same problems while other browsers work.
Click to expand...
Click to collapse
firefox issues on t325 or p900?
Only on P900.
After first usage and sync plus installation of some add-ons it doesn't connect any longer.
Same add-ons and sync on T325 without a problem.
bmwdroid said:
Many thanks @Valera1978.
Cleanly flashed with Data format used the TWRP 3.3.1-0 like for LOS16, instead of 3.4.0-0 with BiTGapps and Magisk.
No more unwanted appearences on the screen when turning. :good:
When focussing on a text the field now shows the letters. :good:
Camera, as you wrote, not working at all. so what
Will carry on testing.
LOS16 will be abandoned, or not?
Click to expand...
Click to collapse
Where can i find BiTGapps?
I did a clean flash, downloaded ARM GAPPS Stock and i'm having errors "updating ok google model service".
Everytime I try to use the mic the tab restarts.
Other than that it looks amazing *w*
bmwdroid said:
Only on P900.
After first usage and sync plus installation of some add-ons it doesn't connect any longer.
Same add-ons and sync on T325 without a problem.
Click to expand...
Click to collapse
It does connect, pages take time to load but nothing is rendered.
I did get a reboot when using the pen in Squid but after restart I played with Squid for a while with no problem!
BIG thanks to Valera !!!
Don't care about a working firefox any longer as I just saw how new version looks like on other device.
So I'm gonna switch browser anyhow.
bmwdroid said:
Don't care about a working firefox any longer as I just saw how new version looks like on other device.
So I'm gonna switch browser anyhow.
Click to expand...
Click to collapse
Thats why I had to modify the APK so it will not update.
The old firefox (I think) is the best browser for this tablet.
The new firefox is much worse, even for normal phones.
So a fix for whyever firefox does not render the pages would be great
Anyone having troubles using the Mic? Everytime I try to use anything related the tab restarts o.o
Also having "updating OK Google model service" download error.
Which GApps version did you guys install?
Thanks!
Thanks @Valera1978 for LOS 17.1 it works good with a few problems but it maybe the apps like Firefox causing reboots and camera otherwise I like this ROM. Thanks again for your great work ???
LionheartSilver said:
Anyone having troubles using the Mic? Everytime I try to use anything related the tab restarts o.o
Also having "updating OK Google model service" download error.
Which GApps version did you guys install?
Thanks!
Click to expand...
Click to collapse
Didn't test mic yet as camera not working don't need it then.
Usually I'm using Opengapps pico but that still includes Google TTS what BiTGapps doesn't.
The latter you find in XDA.
Both ARM of course.
Don't have the link right now.
Just noticed pen not recognised at all.
Edit: suddenly it does. Didn't do anything special.
bmwdroid said:
Didn't test mic yet as camera not working don't need it then.
Usually I'm using Opengapps pico but that still includes Google TTS what BiTGapps doesn't.
The latter you find in XDA.
Both ARM of course.
Don't have the link right now.
Click to expand...
Click to collapse
Tried Clean Install using GApps nano, pico, micro and stock, same problem: "updating OK Google model service".
Tried using BitGapps, same problem
Also, mic doesn't work, restarts the tab as soon as you want to use it.
@Valera1978 congrats! it's an amazing ROM *w* everything feels smooth and fast.
Just the Mic Problem, i need it to use Microsoft Teams for calls xD
Congrats!
new update:
1. updated cpu config in dev tree (correct variant cortex-15 config)
2. updated power profile (and here found interesting setting in kernel to speed-up cpu freq up to 2100MHz and seem it's work)
3. updated kernel - net part, I had issues with net on start and made small fix, but now ported all net part from my msm8974 (same 3.4 kernel, but more up to date). firefox still dnw (will continue check), but at least no kernel panic
mic - this is my next priority
Feedback to built one (20200824):
- FPS drops when watching YouTube in higher than 480p (starts lagging behind audio)
- graphic bugs still exist (pixels and boxes)
Will now re-flash and try the new built :good:
Feedback to built one (20200825):
- reboots
- wlan sporadic not working
- freeze sometimes
Feedback to built one (20200824):
youtube bug (same above)
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
6. Uncheck Update Lineage Recovery alongside the OS option during start wizard
Work
almost all
Known Issues
Links
3. 20210509: may security patch: https://drive.google.com/file/d/1xzUPsV8cYLR9OyseUe294VNJfcCffpF9/view?usp=sharing
2. 20210430: april security patch: https://drive.google.com/file/d/1gTDS_1wgnJ9KfIw--CzljLgZ8ahxAR9v/view?usp=sharing
1. 20201224: initial technical build: https://drive.google.com/file/d/19tzaR1YE001awwqThNAn48IXsk6FOobm/view?usp=sharing
Gapps
opengapps: https://sourceforge.net/projects/opengapps/files/arm/test/20210130/
BiTGApps: https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/
P.s. for BiTGApps: Chrome workaround with gapps: Chrome should be a part of system app in Android R (11) but we install it as user app, which break sign-in and sync in chrome. To fix this, allow contacts permission for chrome. Restart chrome and you can add your google account.
Root
Install latest magisk (21.1+) from canary channel: https://github.com/topjohnwu/Magisk/releases/tag/v21.1
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/lineageos
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
Nice
Will there be also a P900 build?
Thank you Valera 1978!
PS. I have "Serial console enabled Performance is impacted. To disable, check bootloader" message.
Today I saw that BT is not working at all
BT is already crashed in the last 17 Version from 2020/12 several times. Maybe a common issue?
A build for the P900 would be great! Many thanks to the developers for keeping this get tablet alive and better than ever!
Valera1978, gratitude for keeping our Tablet alive. How is the S-Pen working in this ROM?
Well, I think to try tomorrow to install it! Good work like always Dev
What would I necessarily have to do to Port this to p900
I tried this for a little time. For me it is laggy too much. It's better at the moment Lineage 17.1 even if I need to find the version with palm rejection working because in the last (for me) not work.
I tried this rev. but I immediatly rolled back to 17.1
So buggy and slow. I hope in next updates
finessefigure said:
What would I necessarily have to do to Port this to p900
Click to expand...
Click to collapse
Any progress?
Hi! I flashed the new version and this is perfect, not slow like the other!
I would want use Duo app but from the other side not hear me. If I do a simple video with camera app I can hear my voice. What problem can be???
Thanks a lot
Edit: I found this problem in lineage 17.1 too. Maybe there is some settings that I don't know?!
Edit2: If u want call via skype, duo or other things just use earphones... what a bug lol!
Tanks a lot Valera1978 for the New Update...
No possibility with p900?
New build's great, much smoother than 17.1 and no crashes or other issues so far
Edit: Found out that the lag is somehow caused by me changing the wallpaper. Not sure why since the wallpaper is not live and is only 1920x1200 so it shouldn't cause lag.
Also, system UI keeps stopping when trying to enter settings from the notification shade
Too bad can't download it (neither of them). There seems to be some kind of cooldown or something on Drive. Can anyone confirm?
Edit: Got it installed. Seems to be super smooth. Thank you very much for your work OP. You are da real MVP, this tabled is old but you keep this alive!
its not better compare to 17.1 . change colorful wallpapers in few programs/home unable to change. some graphics issue. video still same as 17.1 camera can not take video .but can take pictures. Thanks Valera1978 for the new upgrade
Updated April security patch. runs smooth, but still everything same camera only can use for photo and few apk graphic could not see. but over all it stable and nice thanks again Valera1978
updated May security patch. unfortunately can not boot. keep goes to recovery mode .do any one can help me what to do to boot as regular system.did any one face same problem