[NEWS & UPDATES] Badadroid - ARMLinux (Android Kernel) on S8530/S8500 - Android Development on Bada

Hey there!
This thread has been approved by Oleg_K - first developer of port.
It is general summary, project news, and development discussion about continuation of Android porting project for Wave.
All non-development post in this thread will be reported, deleted, and computers of their authors desintegrated immediately.
There were reports, and I experienced it myself that using Badadroid can destroy your battery calibration and significantly lower your battery capacity. I suspect this can be avoided by reducing time of connection to USB when Badadroid is running there.
Short development history:
The project has been started by Oleg in March 2011 - development progress has been made rapidly by him, however, he had been using JTAG Riff Box to make Wave oneNAND memory organisation the same like in Samsung Galaxy S (SGS) I9000 - phone with very similiar hardware to Wave. The problem is it's very expensive and advanced stuff. In the meantime mijoma found security hole in Wave's Bootloader3 (BL3) FOTA loading code and made PoC-exploit for that. That allowed me to create, with help of srg.mstr, mijoma and b.kubica, simple Badadroid bootloader, loading kernel zImage from moviNAND flash memory - this is where port has been made bootable on literally any Wave phone. However, oneNAND layout still remains untouched and by default kernel is configured to use SGS oneNAND partitions. So nbates66 and anghelyi put all their efforts into making this method of booting operatible. It succeed after few days and ShadowAS1 had released unofficial tutorial explaining how to bring up pre-alpha Android into S8500 device. The problem was that only 1 bootloader version was supported this time, mijoma came up with idea of making our FOTA bootloader capable of supporting alot of bootloaders - he created "BL Univ Boot FOTA". Oleg became very busy with his real life stuff so kernel development practically stopped. Currently I'm the most active kernel developer, altough I'm not so experienced as Oleg is and I'm learning from scratch so it goes very, very slow.
December 2011 - KB_Jetdroid contacted me and we started to work on Jet&Wave modem driver.
April 2012 - mikegapinski has joined the project to get things together and make first really working ROM.
9 April 2012 - Mike got ICS platform booting.
Mike has stopped maintaining platform so I took it over.
Oleg has finally got S8530 in his hands and made SCLCD driver for it. Praise him!
Both S8500 and S8530 versions are semi operatible. The most complicated, annyoing, and needed driver is Modemctl+RIL.
March 2013 - World's first working non-AT commands based RIL for non-Android phone has been released. Most of the implementation was done by KB_Jetdroid, me and Volk204, basing on opensource Replicant's RIL for Samsung Galaxy S.
April 2013 I finally fixed S8530 display driver.
September 2013 - we've got working microphone recording, and shortly after Tigrouzen found a proper patch fixing voice communication during calls.
22 September 2013 - we released first version capable of multicalls.
~~October 2013 - GPRS connections are working
Currently most of the core work is done.
We are working hard with Volk204 on RIL interface, doing small progress day by day.
Remember - there were no ETA, there is no ETA, and there will be no ETA (Estimated Time of Arrival).
Badadroid sources are based on kernel of I9000 (https://github.com/CyanogenMod/android_kernel_samsung_aries/).
Dev only - "Fastbooting" of kernel is possible through bTerm - scripts are in bTerm directory of badadroid repo.
We do not release binaries according to any schedule - if you want to know real releases time, please refer to Blizzard - "When it's ready."
Also:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to donate and increase our will to work - you can find donation links in our profiles. Right next to our posts and profiles.
Links:
Original Oleg's thread: http://forum.xda-developers.com/showthread.php?t=1012856
Developers call: http://forum.xda-developers.com/showthread.php?t=1382801
Tools SVN repository (FOTA exploit and various debug and config stuff): http://code.google.com/p/badadroid/
Platform git repositories: https://github.com/Badadroid/
Jetdroid project: http://code.google.com/p/jetdroid/
One of the first sources releases by Oleg: https://github.com/Oleg-k/
The opening of the Wave bootloader through FOTA: http://forum.xda-developers.com/showthread.php?t=1020444
CM10 port thread, description and sources: http://forum.xda-developers.com/showthread.php?t=1118436
bTerm - bada terminal application: http://forum.xda-developers.com/showthread.php?t=1298950
Oleg's thread on Badablog.ru (it's in Russian language): http://badablog.ru/forum/topic683start780.html
CM10.2 port thread by Volk204: http://forum.xda-developers.com/showthread.php?t=2550138
CM11 port thread by Volk204, description and sources: http://forum.xda-developers.com/showthread.php?t=2609560 <- THE MOST RECENT
To clarify - building and releasing binaries is not porting. In this moment, real porting team consists of Volk204 and myself.
You can often meet me on irc.freenode.net #badadroid

Hello my friends,i'm back))

<placeholder for any future need >
Thread has been slighty updated, and finally opened - but please use other threads to ask any questions - though most, or all of them had been already answered, just use SEARCH!
@Post below:
Thank you very much for good word, but I'd rather prefer if you not write it here.

What you are doing is just awsome. You can be proud of your work. Just keep going like this it is just perfect.
Thanks a lot.

Oleg_k welcome. You are the king. I love you. Please finish this project. Thank you.

HI . May i know how can i do android on Bada .... i am using S8530
can show me the procedure !?
many many thanks @@

I like to be honest. So to be completely honest - many of people seems to be too big idiots to keep this thread opened.

Updated first post abit and linked to most recent kernel repository (we moved to GitHub).

https://code.google.com/p/badadroid/source/detail?r=474
you can find source there:
https://github.com/Rebell/bdroid/tree/3.0.8
I used master branch from AOSP, built for crespo.
System partition:
http://code.google.com/p/badadroid/downloads/detail?name=AOSP_crespo_system.tar.gz
Read commit messages and init scripts if you want to get it working.

I've uploaded latest FOTA which can be used to boot our HEAD kernel. It won't work with older kernels.
Only 2 bootloaders are supported. S8500XXKL5 is also in our downloads section.
http://code.google.com/p/badadroid/downloads/detail?name=armlinux_boot_S8500XXKL5.zip
http://code.google.com/p/badadroid/downloads/detail?name=armlinux_boot_S8500XXJEE.zip
Note that all flashing you do is fully at your own risk! Badadroid team offer absolutely zero support for that.
CHANGELOG:
- Kernel, named "zImage", has to be in root directory of User partition.
- Sbl binary nor galaxyboot directory is unneeded anymore.
Click to expand...
Click to collapse

There were reports, and I experienced it myself that using Badadroid can destroy your battery calibration and significantly lower your battery capacity. I suspect this can be avoided by reducing time of connection to USB when Badadroid is running there.

SD Card handling has been fixed.
Big kudos goes to volk204 for pointing out proper change and nbates66 for testing out all my weird stuff.
Here's prebuilt kernel for S8500: http://d-h.st/cgg
I can proudly announce that all major kernel bugs unrelated to modem are fixed.

New FOTA
For usage only with latest jellybean kernel branch.
http://goo.im/devs/Rebellos/wave/armlinux_boot_S8500XXKL5.zip

There's sourcepack for 2.6+ kernel for Wave S8530 I got from Oleg some time ago.
https://dl.dropbox.com/u/32145655/lg4573_sources_kern2.6.rar
These sources were working all fine.
If anyone could compare it against my current kernel and try to find out what's wrong that would be greatly appreciated.

LCD driver for the latest kernel is almost finished. It's displaying properly now.
I've updated repositories. Just adding binaries to the CM10 thread.

0.07 version of CM10 is upcoming. Most of the changes are already in upstream repositories.
The biggest change is that there's no more needed separate kernels nor platforms for S8500 and S8530. All difference between them now is FOTA.
New FOTA versions are there (corresponding platform and kernel binaries are not yet ready, you can compile them yourself, and please don't release):
http://goo.im/devs/Rebellos/wave/armlinux_boot_S8500XXKL5.zip
http://goo.im/devs/Rebellos/wave/armlinux_boot_S8530NELH2.zip
Also - OP has been slighty updated.

We achieved world's first useable opensource AP-CP interface for Samsung 3G non-android phone, it should be mostly compatibile with phones like Jet or Wave 3.
0.1 version of CM10 just dropped. It does include RIL lib (based on Replicant's Samsung-RIL) supporting battery fuel gauge readings.

Version 0.2 got released yesterday.
Most of the release credits goes to Volk204.
This is only RIL update, but it is real breakthrough as it introduces support for Netwok Registration, SIMcard communication, SMS, Call notifications.

Well Done! From reading about the modems drivers, it appear's to be the hardest thing to fix. I applaud your progress.

S8530 display driver got enough of love finally + there's a big batch of changes from Volk to the RIL. 0.3 release should be dropped soon.

Related

Unify Thread for Furrydaus Creations

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Unified Thread for all of my Creations from ROMs to Mods!
This thread serves as a platform to unify everyone into a single thread and to clutter the whole of the Xperia SP Development Forums
Support will be given to the best of my ability here and I hope the community does the same with a modicum of respect
Cyanogenmod 12.1
Not Maintained by me anymore. Check and discuss about CM12.1 in the link below. (Thanks to @Mrcl1450 )
Thread Link: http://forum.xda-developers.com/xperia-sp/development/5-1-cyanogenmod-12-1-t3067460,
Cyanogenmod 11s
UBL Bugs: Unconfirmed, This is an old build. Don't get confused lol
Download the Latest UBL Build Here: https://basketbuild.com/devs/furrydaus/CM11s/Sony Xperia SP (Huashan)
GApps (Google Apps)
Download the Minimal Edition GApps from @jajb (Recommended): http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
SuperSU
Download @Chainfire 's Superuser Flashable Zip File here: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Contributing
To contribute to any of the above works, I recommend committing changes to the respective repositories in my Github Account: https://github.com/furrydaus
Alternatively, send me the file that you want to contribute and i'll review it and credit you accordingly if it goes pass my checking
Disclaimer
| The Software provided through this thread or any other sources does not ensure 100% functionality although I'll try my best to keep it stable.
| By Downloading the Software provided through this thread, you are bound by your own actions thereafter and I will not be responsible for anything that occurs to your device
| I do not appreciate re-distribution methods by any forms of media. Either credit or link it back here.
| Mirrors are not allowed unless you have sent me a Private Message to seek permission. Only then will I review it and give permissions for publishing the mirror.
| The rest is solely based of XDA Rules. Follow them or you shall be summoned into the hands of the Moderators
Powered by:
SuperSU, GitHub, Android, CyanogenMod, ResurrectionRemix, Sony, XDA Developers and the community, Other Developers of the AOSP Project and its subsidiaries.
Clutter this thread as much as you want but stay away from the first 10 posts!​
Reasons for Inactivity (1 reason as of 23 March 2015):
You're probably wondering who this guy is. Let me give you a brief introduction of who he is:
Mr Lee Kuan Yew is the man responsible for the outstanding growth of Singapore (My Country) from being a mere Fishing Village to a Modernized Country whom most know as the Garden City. From being a Third-World Country, this man has brought this country to a First World Country in a matter of 3Decades which by far, is an extroadinary feat. Sadly, Mr Lee Kuan Yew, the founding fathers of Singapore has died in the Singapore General Hospital on the 23 of March 2015.
The Picture i posted is a tribute to his work and his legacy that has brought Singapore to the place I call home. For more information about Mr Lee Kuan Yew, do Google him up. This is one of the reasons why I have been busy lately I hope you all understand
What's next?
1) My exams [O-Level National Examinations] (Till 6 November)
2) CM11s has been sleeping for far too long, let's try to revive its legacy shall we? (Experimental but should be stable)
3) Release of the HitBox Kernel you've all been waiting for! (Undecided)
4) Stable & Updated PAC-MAN ROM (Stable sources from NeXusPrime. Just a Re-Build) (Cancelled)
How to check for Progress:
1) Don't ask me for ETA's god damn it
2) Check my Github for Commits and potential bug fixes at https://github.com/furrydaus
3) Catch my streams (If I activate em) at http://twitch.tv/furrydaus
How to ask for support:
1) Use proper English pleaseeeee
2) Use the SPELL CHECKING TOOL
3) Ask Politely
4) Check for any potential solutions first
5) Give a full description of the problem you require support in
How to report Bugs:
1) Give me a CatLog please
2) Tell me what triggers the bug
3) Tell me if you find any fixes
Moderator' Space to Speak:
Code:
(None at the moment)
Kernel's Usable:
RR 5.0-5.1 LBL: Any Stock Based Ones (DooMKernel/Williams Kernel)
RR 5.0-5.1 UBL: Any CM12 Based Ones (HitBox Kernel/Tangerine Kernel)
CM12.1: Any CM12 Based Ones (HitBox Kernel)
CM11s: Any CM11 Based Ones (Williams Kernel)
Community Input Section!
Include Apps or not?
http://goo.gl/forms/6hVaqGF3eY​
Bugs:
Resurrection Remix UBL Build 4:
Rare SystemUI, AOSP Keyboard and Screen cast FC's
CM Simple Recovery (Flash Philz with Rashr)
SIM Card Detection (Flash Tangerine Kernel)
How to Install RR UBL Build 4/5:
-Download the ROM, GApps and SuperSU 2.4.6
-Reboot to Philz Recovery (Recommended)
-Choose "Factory Reset -> Wipe for Installing a ROM" Option
-Flash the ROM and SuperSu
-Reboot
-Open Rashr and Flash Philz Recovery
-Reboot to recovery (Settings->Developer Option->Advanced Reboot)
-Flash GApps
-Reboot and Enjoy
Last Reservation
Now Speak!
Such excitement Much wow:highfive::victory::laugh:
All I will say is that I will be aware of the progress of this thread and I expect great things from him.
Good work Furydaus
I'm sorry for all the delay this week as you can see from the github commits for this week. Been truly devastated by the lost of our government leader. No matter, development will continue and hopefully I can get the Cm12.1 build as soon as possible
Sent from my Xperia SP using xda Forum
Furrydaus said:
I'm sorry for all the delay this week as you can see from the github commits for this week. Been truly devastated by the lost of our government leader. No matter, development will continue and hopefully I can get the Cm12.1 build as soon as possible
Sent from my Xperia SP using xda Forum
Click to expand...
Click to collapse
No problem. It's nice to have somebody actively working on our device. Please take your time, we'll be patient for CM 12.1.
Oh, and what about an LBL version of CM 12.1?
Simply. I dont have words to thank you
Youre the only developer who is doing his best for the device when others have andoned it
Furrydaus said:
I'm sorry for all the delay this week as you can see from the github commits for this week. Been truly devastated by the lost of our government leader. No matter, development will continue and hopefully I can get the Cm12.1 build as soon as possible
Sent from my Xperia SP using xda Forum
Click to expand...
Click to collapse
I think when I unlocked my bootloader the problems on 4.4 became with the touchscreen. It gets unresponsive after few hours of use and I don't have that problem on 4.3. Plzz help me
Furry you break my heart
I thought it was a new phone for us all and you said no
I thought it was a new Rom but it`s not
But can it please be somewhere that users respect and learn from
On 5.02 with all the fixes being applied but looking forward to a new Rom with thanks :good:
Imperial_Raj said:
No problem. It's nice to have somebody actively working on our device. Please take your time, we'll be patient for CM 12.1.
Oh, and what about an LBL version of CM 12.1?
Click to expand...
Click to collapse
So here's the main issue with lbl:
1) Incompatible Source Code
2) I will be creating lbl sources ground up from the main huashan device repos and hopefully all goes as planned with the help of MrSteve
Sent from my Xperia SP using xda Forum
Treboeth said:
Furry you break my heart
I thought it was a new phone for us all and you said no
I thought it was a new Rom but it`s not
But can it please be somewhere that users respect and learn from
On 5.02 with all the fixes being applied but looking forward to a new Rom with thanks :good:
Click to expand...
Click to collapse
Will be doing my best to get everything up by June
Sent from my Xperia SP using xda Forum

[ROM][AOSP][6.0/7.1][K3.4] Unlegacy Android Project

The Unlegacy Android Project​Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Nexus 7 (2012) include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only! no point of f2fs on /cache)
- SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- We received some RIL bug reports on 3G variants - other than that, there are no known issues.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if we don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7
Contributors
Ziyan, sheffzor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2015-06-07
Last Updated 2017-12-23
Reserved
GApps
If you want to install GApps, we recommend Open GApps Pico.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Yesss is it snappy?
I was able to workaround the panel errors in the kernel - PWM control isn't working for some reason, so I had to use an alternative method to enable backlight, meaning it's using a fixed brightness. This isn't important right now (I want the core functionality to work before making stuff bug-free). I also forward-ported the touchscreen driver, so it's mostly working now - it still needs some fixups for 3.4. My next goal: audio and video decoding.
View attachment 3350098
anzi2001 said:
Yesss is it snappy?
Click to expand...
Click to collapse
Kernel/common android-3.4 branch could be merged into the kernel after it's fixed up, which will surely make it more efficient.
great, i wish you very much success :fingers-crossed:
While I try to do my best to keep myself from working on this 24/7, I couldn't resist... and fixed camera, video encoding and decoding, and audio (party, just the rear speaker works yet) also works now :silly: what this means? Blobs won't stop us, as they work fine on 3.4 as well.
Man you really are doing the job man any way i can help? i want to help
I'm so subscribing to this
I never thought we will get to
3.4
Subbed for sure. Very good news here.
Will definitely be keeping my eye on this one.
Today, I fixed sensors and panel PWM control (meaning brightness can be changed, auto-brightness works fine as well), and Bluetooth. Doing this alone requires a huge amount of time and work, as there's still a zillion thing to do, like merging in android-3.4, fixing up touchscreen (there are ghost touches and packet spams slowing down the kernel), fixing up suspend (need to press power button multiple times to wake up), audio, otg, etc...
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
do you happen to have an img for testing?
Ophidian_DarkCore said:
do you happen to have an img for testing?
Click to expand...
Click to collapse
No, you need to hardcode your pcbid and projectid into board-grouper-misc.c atm which you can get from last kmsg (just grep for those things when catting a kmsg in adb shell).
Can i help somehow? i want to help lol
I want to help too !
HTCDreamOn said:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
Click to expand...
Click to collapse
I tried to build (img) but without success...As you said on a recent post you cannot build .img but you need to to hardcode your pcbid and projectid into board-grouper-misc.c but i dont know how to do it :S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i will subscribe to this thread, just to see how it goes...
It was a long time since i was not so excited in xda

[ROM] v5.1.1 GamerROM Orbis v1.1 jflte Update Released: 06/13/15

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GamerROM Orbis
what is new in this version?, why is it better then GamerROM 5 LE?
A: Well GamerROM Orbis is based of Sony's OS on the PS3 Using the linux code, however this is android not a odficial os of the ps3 os but similar, runs like the ps3
Code:
[B]Changelog:[/B]
* 6/13: New Launcher Based off of GR7
Updated Google Search
New Alucard PWR Core CM12.1 Kernel
We removed many apps to specs to decrease cpu usage and increase battery life and performance
New Redesigned Calender Powerd By HTC Calendar
Added FM Radio listen.on.the go to your local radio stations (headphones required to use)
New File Manager Powerd HTC File Manager
Dalvik VM improvements
Redesigned The stock browser
Bug fixes
Please don't mind the size of the rom we usally high compress it, my pc was slow compressing it highly at the moment
* 6/11: Intital Release
Code:
[B]Features:[/B]
* View your network traffic right on your status bar allowing you to view how much data at the speed your going at
* Faster FPS Speeds with less heating issues
* Better Thermal Control via STweaks
* Tune up your cpu with the alucard kernel and STweaks App (Credit to Alucard_One)
* Awsome visual effects and support for F2SF
* Launcher from GR5 was transfered to this os and much more
Code:
[B]Intructions To Install:[/B]
1: Download the rom and place it in your internal or external SDCard
2: Reboot Into your recovery and back up improtant data before proceeding
3: After data backup wipe the following partitions
Dalvik-Cache
/system
/data
/cache
/preload
4: then install the rom where you placed in your internal or extsd
5: once completed reboot and enjoy
USERS FEEL FREE TO MESSAGE ME YOUR KERNELS, IDEAS ETC TO ADD TO ROM
THE KERNEL SRC IS AVAILABLE BY THE ORIGINAL SRC DEVELOPERS ON GITHUB VIEW THEIR SRC HERE: GitGub SRC
Proper Credit For kernel is: Alucard_24, & kryten2k35 thanks for your hard work in the src
Supported Models:
GT-I9505
GT-I9505G
GT-I9507
GT-I9508
Any SCH-I545
Any SCH-R970
Any SGH-I337
Any SGH-M919
Any SPH-L720
GT-I9515 isnt currently supported Yet
Want To Help Our Development/Projects, You May Donate to us, it is appricated but not expected to
Donate Now
For questions, bug repirts or support regarding the rom, Please email me at: [email protected]
XDA:DevDB Information
GamerROM OS, ROM for the Verizon Samsung Galaxy S 4
Contributors
g7755725, MattBooth, Alucard_24
Source Code: https://github.com/Alucard24/Alucard-Kernel-jfltexx/tree/my-aospv2-5.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Current Beta Version: 1.1
Beta Release Date: 2015-06-13
Created 2015-06-12
Last Updated 2015-06-13
KANG...
Dear Dev,
SS compatible? Doubt it ?
krazy_smokezalot said:
SS compatible? Doubt it ?
Click to expand...
Click to collapse
No. It has a CM base.
Will not run on stock kernel.
smeroni68 said:
Dear Dev,
Click to expand...
Click to collapse
This isnt kang as you can see, and nor its not assoicated with it, get it right man
smeroni68 said:
Dear Dev,
Click to expand...
Click to collapse
Also to know if your saying my rom is kang then your saying other roms are kang right..i didnt think so, please keep negative comments to yourself thank you
KANG
g7755725 said:
This isnt kang as you can see, and nor its not assoicated with it, get it right man
Click to expand...
Click to collapse
ROFLMFAO - it is clear to all that all you are doing is taking real devs work and presenting it as your own, it's a fantastic copy and paste exercise granted.
KANG
g7755725 said:
Also to know if your saying my rom is kang then your saying other roms are kang right..i didnt think so, please keep negative comments to yourself thank you
Click to expand...
Click to collapse
You took the Optimized CM12.1 as a base for your ROM (there is insurmountable proof of this) without permission. It is not an official CM ROM, it is the culmination of several people's hard work fixing things on CM and optimising for all of the jf device tree...
You're absolutely free to sync the code from GitHub and compile yourself on your own machine. That is what open source is for. But we are publishing the ROM on XDA and we are not giving permission for it to be used as a base. You should sync our sources and build yourself (we will know if you've done this, or just taken our zip), not take our zip package and modify it and put up donation links. You can also use the Official CM builds for your base, but not ours.
Futhermore, and probably besides the point, but the claims in this thread about optimised CPU usage and great for gaming is totally spurious and unsubstantiated. All you've done is "debloat", add Gogole Apps, and add useless build.prop values
@malybru
Please, A bit of Concentration on this Thread would be Heartly Appreciated, As the Thread, is HURTING The Original Authors & The Whole JDCTeam​
@g7755725 @oka1
First of all I would like to ask excuses for the posts I've done, but they where a reaction to the situation.
Now, Forum Mod has evaluated the informations we gave him, and due to the fact the download links where removed, we assume that on this rom there is something not correct.
I managed in PM with another user ( @minidude2012 that has offered his help to sort out this situation) some exchange of informations.
I clearly stated that JDC Team nor any of his members has given permission for such a kind of MODDING of the original Optimized CM12.1 by JDC Team ROM.
My suggestions where oriented on two directions:
1) Instead of doing a complete ROM, to create a "package" to mod our ROM to obtain the result you want (to be applyed after ROM flash for example).
2) To build by yourself from sources a ROM that have on sources consistent changes VS our github (to build the rom on our sources as they are, would be just a copy)... if instead the changes on source are consistent, it can become a different ROM, but you need to work correctly with github, commits, no reauthoring... this means you can demonstrate you are a developer and that you know what means open source.
This are the rules for this second option (from a PM of @AntaresOne , LEAD DEVELOPER of OPTIMIZED CM12.1):
----------------------------------------------------------------
- Modified sources clearly linked to his GitHub (with a well-made commit history: no kangs, no reauthoring, cherry-pick and merge conflicts in case of to keep the author intact)
- All the credits to JDCTeam and CyanogenMod for the base sources used
- Make consistent modifications in our code (otherwise just start over from unofficial CM instead of our)
- Don't unzip, modify our builds and publish (kang)
----------------------------------------------------------------
This message has been already given to @minidude2012 and has been probably forwarded in PM to @g7755725
Now here I published all the informations. Is up to OP to decide how he would like to work.
Thanks for your attention.
smeroni68 & JDC Team
smeroni68 said:
@g7755725 @oka1
First of all I would like to ask excuses for the posts I've done, but they where a reaction to the situation.
Now, Forum Mod has evaluated the informations we gave him, and due to the fact the download links where removed, we assume that on this rom there is something not correct.
I managed in PM with another user ( @minidude2012 that has offered his help to sort out this situation) some exchange of informations.
I clearly stated that JDC Team nor any of his members has given permission for such a kind of MODDING of the original Optimized CM12.1 by JDC Team ROM.
My suggestions where oriented on two directions:
1) Instead of doing a complete ROM, to create a "package" to mod our ROM to obtain the result you want (to be applyed after ROM flash for example).
2) To build by yourself from sources a ROM that have on sources consistent changes VS our github (to build the rom on our sources as they are, would be just a copy)... if instead the changes on source are consistent, it can become a different ROM, but you need to work correctly with github, commits, no reauthoring... this means you can demonstrate you are a developer and that you know what means open source.
This are the rules for this second option (from a PM of @AntaresOne , LEAD DEVELOPER of OPTIMIZED CM12.1):
----------------------------------------------------------------
- Modified sources clearly linked to his GitHub (with a well-made commit history: no kangs, no reauthoring, cherry-pick and merge conflicts in case of to keep the author intact)
- All the credits to JDCTeam and CyanogenMod for the base sources used
- Make consistent modifications in our code (otherwise just start over from unofficial CM instead of our)
- Don't unzip, modify our builds and publish (kang)
----------------------------------------------------------------
This message has been already given to @minidude2012 and has been probably forwarded in PM to @g7755725
Now here I published all the informations. Is up to OP to decide how he would like to work.
Thanks for your attention.
smeroni68 & JDC Team
Click to expand...
Click to collapse
Well the moderator and i has dicussed this problem and we are sorting this out in a friendly manner and hes right about it all he has given a second chance ss he stating i might be a promising dev as said in my work but requiring permission from the original dev do further work, however i faild to ask permission resulting this havok upon my thread i do apologize and hopefully eork together to build a stonger and better gaming os, i cannot deny the info you provided but i will glasly look over my actions before proceeding in compiling my builds as so i apologize and ask for forgiveness?
g7755725 said:
Well the moderator and i has dicussed this problem and we are sorting this out in a friendly manner and hes right about it all he has given a second chance ss he stating i might be a promising dev as said in my work but requiring permission from the original dev do further work, however i faild to ask permission resulting this havok upon my thread i do apologize and hopefully eork together to build a stonger and better gaming os, i cannot deny the info you provided but i will glasly look over my actions before proceeding in compiling my builds as so i apologize and ask for forgiveness?
Click to expand...
Click to collapse
I appreciate your post... everyone can do a fault... not all are able to admit...
Find your way respecting rules... and you are welcome everywhere.
g7755725 said:
Well the moderator and i has dicussed this problem and we are sorting this out in a friendly manner and hes right about it all he has given a second chance ss he stating i might be a promising dev as said in my work but requiring permission from the original dev do further work, however i faild to ask permission resulting this havok upon my thread i do apologize and hopefully eork together to build a stonger and better gaming os, i cannot deny the info you provided but i will glasly look over my actions before proceeding in compiling my builds as so i apologize and ask for forgiveness?
Click to expand...
Click to collapse
Perhaps you should publish how exactly you will make a gaming OS, because it just looks like you've removed system apps and added magical build.prop "tweaks", whereas to properly optimise for any kind of CPU/GPU activities you'd need to be knee deep in low-level code and building from source.
If you can publish how you have achieved this, you'd probably have a lot of supporters across the whole forum.
EDIT:
Also, it's good you've apologised and realised the error of your ways. I will say no more on this.
From the Moderator
To all the Devs and Op... please carry this conversation in a PM it will be more productive, and avoid the random troll trying to take sides ..........
..... Also, I would encourage that all of you try to work these issues in a helpful manner..... the OP does show promise and some insight from a more experienced dev like some of you would help lift up another to a higher level of skill
Be Kind, Be civil .......... Thanks ...... ~~~ oka1
From the Moderator
From the Moderator .......... I will close until the OP has time revise and reissue his work
........... OP let me know when you have your new work ready to post and I will reopen
............... THREAD CLOSED ...................
~~~ oka1

[10][UNOFFICIAL][r41] CarbonROM | 20200813 [i9100]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is PAX?
Our release of Android 10, titled CR-8.0, is codenamed PAX after the latin word for peace and Pax, the roman godess for peace.
PAX provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. PAX delivers a set of unique features, like a systemwide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Download (AFH)
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Samsung Galaxy SII
Contributors
linusdan, rINanDO, Myself5, CarbonROM
Source Code: https://github.com/carbon-i9100
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Testing
Created 2020-07-08
Last Updated 2020-08-13
Current state:
Working:
- PowerHAL
- Audio, including headset, bluetooth
- Wifi
- IMEI
- Touchkeys
- Camera Pictures
- Camera Videorecording
- Hardware encode/decoder
- Display
Not working/known issues:
- GPS
- BLN (Maybe never)
- Brightness button light
- HDMI (MHL) (support broken/removed since CM 10)
- Wallpaper (screen goes black even if alternating with another image)
- Home button (to minimize the problem, use gesture navigation of android 10 in Settings > Carbon Fibers > Gestures > System navigation)
Not tested:
- Sensors
- RIL (Phone/SMS)
- DRM, for e.g. Netflix
- Screencast (Chromecast)
Changelog
13082020
Required recovery: TWRP 3.4.0-i9100 for Android 10
Initial release
Vintage tee, brand new phone
Just installed this rom. Looks very nice and works fine so far (no gapps installed). Love the bootanimation too!
Thank you very much!
Bug report - RIL fails when attempting to call
Clean install, SIM inserted, carrier service signal OK after reboot.
Running phone dialer app when placing call - I get immediately 'no service' ('x' on carrier signal icon).
Only way to restore is reboot, but bug is persistant.
logcat url:
crash starts at line 869
RIL fails at line 1633:
TinyALSA-Audio RIL Interface: ril_connect() failed
About magisk
I can't adapt for CarbonROM at the moment, because I need to download the source code to the HD and at the moment I don't have enough space. As soon I can, I generate the adaptation.
linusdan said:
Current state:
Working:
- GPS
Click to expand...
Click to collapse
Clean ROM and no gapps, GPS Test shows no location
(No Fix). What do you mean by "Working GPS"?
.
ze7zez said:
Clean ROM and no gapps, GPS Test shows no location
(No Fix). What do you mean by "Working GPS"?
.
Click to expand...
Click to collapse
I knew I was forgetting something. Sorry
OKEY
I decided not to continue with the maintenance of the bliss as it takes 2 times longer to compile due to the immense amount of fonts and other things that I have no idea what it is, doubling the file size and the costs with the server.
In order not to open another topic, I decided to modify this one and move on.
For anyone who was wearing bliss, sorry. Keep good memories.
Link of CR-8.0 build available on OP.
About magisk: Read here
Hello.
Sorry, if you are a real ROM developer then please look at the camera driver in the open source code published by Samsung for the model GT-I9100P, there mentioned a possibility to take pictures (and may videous) with 10bit per color component colour depth! (Currently our device can take 8bit photos only.)
Please, if you are programmer then make a ROM which takes 10bit photos (may 10bit RGB TIFF, 32bit per pixel PNG or at least 10bit RGB DNG).
I can offer bounty of 50USD if you will able to do it for me and for others.
May you can make this improvement to the device as a paid patch and sell it.
If you will achieve that then it will be a great step beyond for our old Galaxy S2.
I had attached a photo taken by our device and we can expect yet more rich colour improvement together with a significant dynamic range widening if 10bit colour depth will be achieved.
P.S.: May you can cooperate with the people from PentaxHack web-site.
Code:
;)
;) ;) -;) ;) ;)
;) ;) ;) ;) ;) ;)
;) ;) -;) ;) ;)
;)

[BETA][ROM][Unofficial] ArrowOS 12.1 | Latest release: November 27th 2022 [DISCONTINUED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
Code:
/*
* 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.
*It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
DISCONTINUED
Why?
__________________________________________________________________________________________________________________
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Credits:
@xxseva44
@AShiningRay
@ROMSG
@askermk2000
@Stealth1226
Rom details
Release Kernel: 4.4.205
Android Version: 12.1
Adreno Driver: 5xx
Selinux: Permissive
Maintainer: Me, xxseva44
What works and what doesn't?
Refer to my wiki page:
V20 Device Functionality
LGE_8996_COMMON. Contribute to xxseva44/LGE_device_msm8996-common development by creating an account on GitHub.
github.com
Want root?
Use magisk v25.2, availible here. Change the file extention from apk to zip and flash in recovery.
Want gapps?
Use nikgapps, availible here.
AND A MESSAGE FROM ONE OF THE TWO KERNEL DEVS:​
[BETA][ROM][Unofficial] ArrowOS 12.1
ArrowOS /* * 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...
forum.xda-developers.com
####################NOTE#########################​You MUST update to twrp V3.70 before flashing.
You can downlaod it here: https://twrp.me/Devices/
Thanks @npjohnson
FAILING TO DO SO MAY RESULT IN CORRUPT FILE SYSTEM ONLY FIXABLE THROUGH LG UP OR 9008 RECOVERY MODE. YOU MAY ALSO END UP IN A RECOVERY BOOTLOOP ONLY RECOVERABLE BY FLASHING THE REOCVERY PARTITION. YOU HAVE BEEN WARNED​##################################################​TREES:
##################################################################################
##################################################################################
CAF display
GitHub - xxseva44/hardware_qcom-caf_msm8996_display
Contribute to xxseva44/hardware_qcom-caf_msm8996_display development by creating an account on GitHub.
github.com
CAF media
GitHub - PixelExperience/hardware_qcom-caf_msm8996_media
Contribute to PixelExperience/hardware_qcom-caf_msm8996_media development by creating an account on GitHub.
github.com
Broadcom FM(Modified)
GitHub - stendro/android_hardware_broadcom_fm
Contribute to stendro/android_hardware_broadcom_fm development by creating an account on GitHub.
github.com
Kernel
GitHub - LGE-G5-G6-V20/msm8996_lge_kernel
Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.
github.com
Dac interface
GitHub - SGCMarkus/android_hardware_lge
Contribute to SGCMarkus/android_hardware_lge development by creating an account on GitHub.
github.com
MSM8996 common
GitHub - xxseva44/LGE_device_msm8996-common: LGE_8996_COMMON
LGE_8996_COMMON. Contribute to xxseva44/LGE_device_msm8996-common development by creating an account on GitHub.
github.com
V20 variants
GitHub - xxseva44/LGE_8996-Variants
Contribute to xxseva44/LGE_8996-Variants development by creating an account on GitHub.
github.com
V20 common
GitHub - xxseva44/LGE_device_v20-common
Contribute to xxseva44/LGE_device_v20-common development by creating an account on GitHub.
github.com
LG common
GitHub - xxseva44/LGE_Device_common
Contribute to xxseva44/LGE_Device_common development by creating an account on GitHub.
github.com
Vendor
GitHub - xxseva44/LGE_proprietary_vendor
Contribute to xxseva44/LGE_proprietary_vendor development by creating an account on GitHub.
github.com
##################################################################################
##################################################################################
Screenshots:
CHANGELOG​
Code:
Initial release | September 25th 2022
N/A
2nd release | November 11th 2022
-Fingerprint is now functional(Core functions)
-Dac is now functional
-October security patch
-Extra perf by killing logspam
3rd Release | November 27th 2022
-All dac functions from stock work on 12
-Ported dac filters from V30 (Big shoutout to SGCMarkus for his initial work)
-Enabled Dac AVC volume comtrol (Again, Big shoutout to SGCMarkus for his initial work)
-DRM is now functional
-Added schedtune profiles
-Killed iorapd
-Tweaked down_rate_limit_us
DOWNLOADS/RELEASES​DOWNLOAD
VS995:​27/11/2022: Uploaded
________________________________________________________________________________________________________________
H990:​27/11/2022: Uploaded
________________________________________________________________________________________________________________
H910:​27/11/2022: Uploaded
________________________________________________________________________________________________________________
H918:​27/11/2022: Uploaded
________________________________________________________________________________________________________________
LS997:​27/11/2022: Uploaded
_________________________________________________________________________________________________________________
INSTALLING STEPS​********************************************Prerequisites**********************************************​1.If coming from stock, you MUST be on NOUGAT FIRMWARE​2.Own a v20 (duh)​3.Unlocked bootloader (if you are using a us996 or vs995, i can assist you, if not, look around on xda for a guide)​********************************************************************************************************​STEPS:
1.Reboot into recovery via the hardware button combo
2. Wipe system, data, delvik, cache, system and data
3.Flash the OS
4.Flash anything else you want to run (magisk, etc) DO NOT FLASH ANY KERNEL UNLESS IT"S AN UPDATED 4,4 KERNEL
5.Reboot
6.Enjoy Android 12 on the V20
That's right! We're finally releasing the first 4.4 open beta, starting with Android 12.1 for G5, G6 and V20!
I'm the one of the main kernel devs on this project, so i'll be adding info on this part of the development and beta testing.
________________________________________________________
To anyone who wants to beta test this and the upcoming CRDroid rom by @ROMSG: We're using a dedicated github organization to handle feedback, bugs, trees and general development.
That organization is located here, with @xxseva44 moving the trees above to that same org soon:
LGE G5 G6 V20
Devices, vendor trees and new 4.4 kernel for LGE G5, G6 and V20 devices - LGE G5 G6 V20
github.com
If you have any issues that span across multiple roms using this newer kernel and updated device trees, or simply know that what you're facing is something that's bound to happen irrespective of a specific ROM, please open an issue in that org detailing the problem, your phone model, etc.
________________________________________________________
For a list of features that already work in kernel 4.4, we have a wiki page with just that:
Kernel V4.4 New _ Feature states in Android 11 ROMs
Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.
github.com
________________________________________________________
Kernel issues should ideally be opened here:
Issues · LGE-G5-G6-V20/msm8996_lge_kernel
Contribute to LGE-G5-G6-V20/msm8996_lge_kernel development by creating an account on GitHub.
github.com
Please note that this kernel is shared by the LG G5, V20 and G6, so when opening an issue, we need to know at least which device you're using, but the model (VS995, H872, etc) can give us more insight.
________________________________________________________
ROM issues will probably work best as xda posts for now, since those are already going to be separated by phone.
________________________________________________________
Quick primer of what to expect:
For the kernel: It's fast, really fast. Not only did we clean up tons of LGE code from the kernel trees, saving up a lot of memory and overhead, but also added lots of optimizations on top of a custom branch to make what's essentially a mix of @askermk2000's mk2000 and my own SwanKernel.
For the roms: We've been working with people from G5 and G6 as well, and in turn managed to do a major overhaul of the rom-side blobs, drivers and hals, resulting on much improved performance and stability, even during internal tests.
For issues: We didn't iron out all of the issues yet and are far from testing those things in a large scale, hence the open beta. We already have some known issues to fix, such as the much slower charge curve, usb OTG not being as fully fledged on the V20 as it was on 3.18, IR working slightly better than 3.18 but still not great, camera still freezing randomly... In any case, most of the other kernel features either work just like in 3.18, or better.
________________________________________________________
Known issues outside of Android 12 and 4.4:
Both TWRP and SHRP can have issues while flashing 12 due to incomplete support, so be careful and have a complete backup (including the recovery image itself) beforehand.
Performance on the initial build. No tweaks. Consider supporting the 4.4 kernel devs(@askermk2000 & @AShiningRay) as this is mostly thanks to their hard work and dedication, as well as insanity to do such a thing to an lg device. You can expect it to get even better as I iron out issues within 12, this score was achived with excessive log spam, looking at you radio.
Some kernel tunables I'd recommend changing to make your experience better:​
Change "down_rate_limit_us" from 10 000 on both big and LITTLE cores to 25 000 on the little cores, and 20 000 on the big cores. This will significantly improve responsiveness.
Change the minimum gpu frequency from 133mhz to 214 mhz, This will improve the ui rendering and smoothness.
You will obviously need root to change these.
These changes will appear in the next release which will likely come in the following weeks.
IGNORE
Hi. installed on H918. does not see the sim card.
Dukeys said:
Hi. installed on H918. does not see the sim card.
Click to expand...
Click to collapse
Did you even read the initial post?
Wow this is impresive...Going to try this out when I find my old v20
Hi this sounds like it could be awesome! Is there plans to get radio working so that the phone could be a daily driver with this, or is that not a focus?
Thanks for your hard work everybody!
How to donate? Do you think you can fix the rest non Woking issues?
nostupidthing said:
How to donate? Do you think you can fix the rest non Woking issues?
Click to expand...
Click to collapse
The issues will be worked out as devs get more free time. Hopefully we'll even be able to get A13 up and running at some point!
koodz said:
Hi this sounds like it could be awesome! Is there plans to get radio working so that the phone could be a daily driver with this, or is that not a focus?
Thanks for your hard work everybody!
Click to expand...
Click to collapse
He's been busy lately but we have multiple devs looking into the radio and fingerprint and several other issues looking into the issue. Mainly it was due to the kernel needing to be updated to 4.4 (which we did) but that brought on issues, such as the radio. Just give it time and they will be solved in due time!
nostupidthing said:
How to donate? Do you think you can fix the rest non Woking issues?
Click to expand...
Click to collapse
Theres a donation link in my about section on my profile As for the non working issues, They're easy to fix, although cellular is the only tricky one. Well that and the powered dock issue. However they should be fixed as time goes on.
koodz said:
Hi this sounds like it could be awesome! Is there plans to get radio working so that the phone could be a daily driver with this, or is that not a focus?
Thanks for your hard work everybody!
Click to expand...
Click to collapse
Radio is currently the primary focus, however admittedly it is proving to be a tricky one.
xxseva44 said:
Radio is currently the primary focus, however admittedly it is proving to be a tricky one.
Click to expand...
Click to collapse
What if you flash the modem into a US996 ?
Im saying that because my cellular network was not working on Lineage 18.1 and once i flashed the US996 modem on my vs995 everything was working for the DAC there is always the app to active it Dac fix app ons
here the link to download it : US996 Modem 10F IMG
jejeroy said:
What if you upgrade the modem into a US996 ?
here the link to download it : US996 Modem 10F IMG
Click to expand...
Click to collapse
The issue isn't with the modem image.
Update time
What's new?
-Fingerprint is now functional
-Dac is now functional
-October security patch
-Extra perf by killing logspam
Keep an eye out for new uploads
All builds have been uploaded
Only radio is left is needed for me I think, what does drm does?
nostupidthing said:
Only radio is left is needed for me I think, what does drm does?
Click to expand...
Click to collapse
Drm is digital rights management. Required for certain applications and services, netflix for example.

Categories

Resources