Related
I wanted to ask, witch Roms are stable and support all features of Kenzo.
It seems that in several Roms there are different Problems,
from wakelocks and Battery drain,
over Wifi Problems
to missing Fingerprint or VolTE support.
Is it a Problem with Android 6.0 or also with 5.1 based Roms?
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
jimakos98 said:
This should be in the Questions & Answers section. However, I have official CM 13.0 and I haven't encountered any of the problems that you mentioned above. If you read instructions carefully and understand what you're doing, you won't have any trouble as long as the rom you are flashing supports those features. If you head over to the Android Development section, you can see the features that each rom does and doesn't support. If the OP says it is supported but you can't get it to work, then the problem comes from your side. Before flashing make sure you have read and understood the required steps and have taken all the necessary precautions to avoid ending up with a "bricked" device. Let me know if you have any trouble.
Click to expand...
Click to collapse
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
DarkAlucard said:
Thanks for your reply,
yes i know what im doing (had Nexus 4 and flashed it more than a hundred times).
I normally check first post (+ following from OP) and the last sites of the Thread to see if there are bugs or not (cause "no bugs" in OP-Thread is not always correct).
But if CM13 is, so far, bug free and full featured (fingerprint and so on) than i will give it a try.
Click to expand...
Click to collapse
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
jimakos98 said:
It is. I've been using it for almost 1 month now, and I can say it's probably the most stable and complete rom for me. I also flashed the CM 13.0 supported firmware along with Radon Kernel and the device is blazing fast. As for the battery, I can get 1 week+ with minimal usage, and about 2-3 days with heavy usage which is pretty impressive for a hexa-core device with a 1080p screen.
Click to expand...
Click to collapse
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
DarkAlucard said:
I was wondering about this "firmware" thing, never had to upgrade any software. Normaly just flash the Rom.
I was also wondering what's the difference to the unofficial CM13
Click to expand...
Click to collapse
Well, if you are going to flash this rom you are going to have to flash the appropriate firmware too, since CM is based on it. If you flash the rom without flashing the firmware, you might end up with missing options in settings (I tried this and the "fingerprints" tab was missing). As soon as I flashed the firmware everything got fixed. Also, an official rom means that it is developed by a member or a group of members that have created the original project, while unofficial roms can be built by anyone. For example I can take a CM build and customize it the way i want and then release it to the public. This makes it an unofficial rom, since I'm not a member of the CM development team. But if a rom or an update releases on the CM website, then it is considered to be official.
By the way about the VoLTE support, quoting from OP Q&A:
Q) Is VoLTE supported? (Also useful if you have GApps related problems).
A) No. We use all proprietary blobs from MIUI Marshmallow alpha 'leaked' builds and those builds itself do not have it working. So we'll have to wait until Xiaomi fixes it in their marshmallow builds in future. Also we can't fallback to old LP radio blobs/libs and are not suited with current setup. #blamexiaomi
Click to expand...
Click to collapse
I guess you'll have to wait for Xiaomi to release a stable working MM build if you want voLTE support. :/
I'm not sure what the holdup is on the
Official Lineage Verizon builds for the G3,
(as of this writing that directory is still empty), but I just switched over to Verizon with their new Unlimited data plan and I decided to build my own this morning. I saw that a few people had been wanting this, so I figured I'd put it up here.
** Note that I compiled this with 'export WITH_SU=true' so there is no need to use the 'addonsu-arm-signed.zip' (root addon) that they provide, as it's built into this rom already.
LineageOS:
Lineage-14.1-Verizon-vs985
GApps: (ARM, 7.1, Nano)
http://opengapps.org/
have bugs?
ngato35 said:
have bugs?
Click to expand...
Click to collapse
sure, it has plenty of bugs, but no more than any other current lineage 14.1 build (I've tested lineage on a samsung galaxy s5, htc one m8, lg g3 (ls990), lg g3 (d851), and an lg g3 (d855)... this build works virtually identical to those.
cm13 is still the best way to go for now if you need stability, i just wish miracast worked better... lineage 14.1 did improve miracast quite a bit, but theres other problems... like conflicts with certain apps (like power toggles, the hotspot won't function properly, you have to enable that via lineage menus, might be an issue with their new su/root implementation) stuff like that.
but... it runs just as well as any of the 'official' builds if that helps answer your question
good work thank you
Upload
Thank you for this, been waiting.
Uploaded with Banks Dynamic Mini Gapps and 35B modem. Everything is clean and seems to be working great. Will you continue to keep it updated with the latest from lineage as they continue to update the rom.
Great rom, but when I enable encryption and reboot the phone hangs on the LG logo and bootloops.
Edit: Encryption is broken in Lineage 14.1 currently
the bot builds on fridays
Been using 307 Rom for two days and am impressed. Great battery life, smooth, and good calling on 35b.
Thanks for your work.
looks like it's finally been added to the official builds,
i'll continue to do builds of lineage 13.0 for this phone, as thats what i'm using,
but no sense in continuing this thread....
here's the first official build:
https://lineageos.mirrorhub.io/full/vs985/20170310/lineage-14.1-20170310-nightly-vs985-signed.zip
Bailx said:
looks like it's finally been added to the official builds,
i'll continue to do builds of lineage 13.0 for this phone, as thats what i'm using,
but no sense in continuing this thread....
here's the first official build:
https://lineageos.mirrorhub.io/full/vs985/20170310/lineage-14.1-20170310-nightly-vs985-signed.zip
Click to expand...
Click to collapse
Has anyone used the official build for the G3?
My fiance has one, and I may steal her phone and flash it. Battery life would be nice, as well as getting rid of the VZ bloat. Any bugs? App compatibility? Thanks!
yes im using nice rom
I have used Bailx 304 and 307 roms, and loaded the official Lineage 310 rom today. Lineage had done a great job with 14.1 with excellent battery life, smoothness, and speed. I have tried all the 7.1 roms for the G-3, and all are exceptional in how far they have come with reliability. I basically use my phone for that purpose, a few texts, and a few photos, so I'm not much into a lot of mods. The only one I really use is Nova Launcher to set up the way I like. The Gapps I used were the Banks Dynamic Mini and by the time I had finished setting my phone up I had used 5.9 gig of 32.
any chance these builds can have volte on vs985? Is that feasible at all? Please let me know.
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?
This thread may be under construction, watch out!
An introduction to my new Oreo sauce...
This is a modified LineageOS 15.1 ROM meant to fill my personal needs, including my minimalistic Lambda Kernel out-of-the-box and a few customizations to provide a different, privacy-focused, Android experience, just for you.
What are the very best features included?
~> Always latest vanilla LineageOS 15.1 codebase;
~> Root virginity preserved, unrooted;
~> SafetyNet bypass out-of-the-box;
~> Google PlayStore device certification;
~> Privacy oriented Bromite web browser;
~> Compiled with SDClang LLVM 4.0 toolchain;
~> Dex-preoptimization of boot image and system server;
~> Minimalistic Lambda Kernel, more information right down below.
What does this magical Kernel support?
~> Cleanly built on top of the latest QCOM reference Kernel for MSM8996;
~> Up-to-date camera_v2 driver stack according to Nougat (LA.UM.5.5) code base;
~> Proper OEM Kernel code adjusted per target (ZL1/X2) and adapted to the new base;
~> Adjusted headset detection framework to account for Type-C adapter;
~> Optimized and adjusted for the -O2 GCC compilation flag;
~> Minimal configuration with the bare minimum drivers needed;
~> Safe fast charging input, regulated per stock Kernel definitions;
~> A little bit faster panel wake up and touchscreen initialization;
~> Unlocked bootloader state bypass, reports green.
What are the known issues so far?
?> Ambient display feature makes the panel wake up a bit funky, you'll see it when compared to the disabled state, which doesn't have that funkiness.
?> Time registering is broken, the daemon doesn't write properly to the Kernel for some reason and ends up not having the correct time after a reboot with the internet turned off.
?> CDLA sometimes has some pops in the background when not listening to anything, pretty minor though.
Nice, where are the downloads?
The downloads are available in the dev release tag in my Github's lineage_releases repository, there you'll find the zip file for installation and the md5sum for checking the file's integrity.
#WelcomeToOurWorld
XDA:DevDB Information
LineageOS Pro for the Le Max2, ROM for the LeEco Le Max 2
Contributors
GalaticStryder, Sultanxda
Source Code: https://github.com/GalaticStryder/android_vendor_patcher
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Chinese 26S
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2018-05-05
Created 2018-04-05
Last Updated 2018-05-05
Reserved
Mine.
Did anyone mention FAQ?
A series of questions, answers, and wonders about all the things she I said in case you didn't get it already.
&> Q. Why isn't this a new project instead of just a simple variant of LineageOS? There are already a ton of them...
&> A. I think there's already a ton of Android "projects" and I don't feel like nor have time to create yet another one that I probably wouldn't be able to maintain for long.
&> Q. How much time will this "variant" be supported?
&> A. Only future wilt tell us but most likely our brave "variant" will resist at least one Android cycle starting from now, all the way through P, even after LineageOS officially drops it we can still have some OEL support if other developers keep the game going.
&> Q. How does it diverge from official LineageOS builds?
&> A. This one aims at providing a snapshot-like experience - if you remember CyanogenMod gold era - which uses the non-debugging user flavor instead of userdebug as Google keeps pushing their draconian restrictions to have access to their apps and services, we need to fake it to avoid forfeiting.
&> Q. My device is "certified" on Google PlayStore, how?
&> A. The bootloader green check in Kernel and user flavor made it possible. I'm not sure how much longer will it take to Google before they go with something deeper to restrict the access of their services by custom ROMs unconditionally. This is a trick though, your device will never be certified with an unlocked bootloader and non-OEM ROM.
&> Q. Will you ever include root support out-of-the-box?
&> A. No, never. You can flash Magisk if you want it, the latest the better in this case. Not sure about the addonsu from LineageOS itself as I never used it.
&> Q. Will you include Dolby Atmos, ViperFX, $(insert_nice_name_here) out-of-the-box?
&> A. No, not at all.
Heeyo! Are you using official LineageOS trees for building your variant?
prajjwal.laad said:
Heeyo! Are you using official LineageOS trees for building your variant?
Click to expand...
Click to collapse
Synced today, no fools included
Well cause i liked your kernel i will try out this rom also!
Nice timing tbh. Just bricked my current rom rn.
True. I've been using his kernel since 24 hours and damn it is the best kernel for x2. My phone's battery temperature doesn't cross 42°C even though my country's normal temperature outdoors is around 38-40°C these days. I get around 20%/hour drain on medium usage which is awesome for my 15 month old battery. Will definitely flash your rom and give feedback.
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
This is Awesome! The legend is back!
I am so pumped right now! :d:d
@GalaticStryder
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
cloche;76136607 [user=6175749 said:
@GalaticStryder[/user]
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
Click to expand...
Click to collapse
First: Big THX @GalaticStryder for this awesome build.
Tested it for an hour now and everything seems perfect. Sound quality is excellent (through Headphones). Rom itself very smooth.
Will report battery Backup later.
Gapps are NOT included, Root is NOT included.
Heyyo, congrats on the release GalaticStryder! She sounds super promising!
A request
I am going to make a very dumb request, can you create an overclocked kernel for this build? Would it be possible?
Thanks so much
Has same bugs as official (eg slow motion video recording not working)?
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
maylton said:
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
Click to expand...
Click to collapse
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Tell me, how about Vulcan drivers? Are they present in yours build? If not, do you plan add them?
Thx 4 ur work
N-Gage4ever said:
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
Click to expand...
Click to collapse
why the **** you go on ranting on every roms about this, already GalaticStryder has explained u regarding this in his lambda kernel
I've been trying since last night, unfortunately I noticed freez and random reboots.
Fp is very very slowly.
TheMichalos said:
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Click to expand...
Click to collapse
Yes, that would be the best choice for everyone.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
As you all V20 owners know, there's only one kernel available for Rooted Stock Oreo ROM and it is MK2000. However it's a good kernel and its developer has put a great effort on it but unfortunately it doesn't function properly on H990DS variant. Some problems like intensive lags and battery draining are two major examples.
If you remember we had a good DOTS kernel in nougat. If someone could fork it for Oreo it would be great as well.
Anyways, here's what we need:
[*]Stock kernel based on H990ds Oreo sources (20a or 20b)
[*]Dirty Santa fixes applied (You can read about this in H990* root thread under TECHNICAL DISCUSSION section)
[*]RCTD, Triton and whatever related removed
[*]"ForceEncryption" and "dm(avb)verity" removed
[*]KCAL, EXFAT and USB Quick Charge support
[*]More CPU governors (We will talk about this in the group)
[*]Overclocked
[*]Make the project Open Source
If you think you can do something, PM me! I'll send you additional information required.
Also I'll give you a link for a Telegram group where you can share what you have and it can be tested out.
Anyone interested in testing potential builds, also contact me for the Telegram link.
The current list of supporters:
----------------------------------------------------
$15 -- @Daved+
$15 -- @mikekote666
$5 -- @Chucknorris1975
$10 -- @aygross1929
$5 -- Uditha
$5 -- @rivaldo21
$5 -- @giriraj121
$5 -- Taufik Kusuma
$15 -- @tapir1505
$10 -- @albaniax
$10 -- @henrylar
$10 -- @DrugsBunny
$10 -- @lefffen1
$5 -- @bronze_eye
$5 -- @Blissv
$20 -- @Qron
$20 -- @NoName!
----------------------------------------------------
Total: $170
Due to some problems I can't manage this thread soon enough, so please contact @Daved+ for more information.
He will also collect the bounties and release the kernel when ready. Stay tuned!!!
Last update: 2020-3-26 /// 16:16 (GMT +3:30)
After the H990DS variant, we can ask for the other variants if people support it!
So we are looking for money to pay a dev to make a good H990DS kernel (And after that for more models). This is important! Thanks for your collaboration.
Good work creating the thread.
Hope more people jump in
Thanks for pushing this, let's get some more life outta this phone and make rooted oreo usable.
Commenting as a reminder to add to donation list
how do I financially support?
henrylar said:
how do I financially support?
Click to expand...
Click to collapse
Please write the amount of your donation, you can transfer the money when the stable release of the kernel will be ready.
10$
10$
$10
reza_xdv said:
We want the kernel to populate custom NTCODE (Being able to change ntcode for region changes)
Click to expand...
Click to collapse
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
askermk2000 said:
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
Click to expand...
Click to collapse
Hey,
the AutoMID option in h990ds hidden menu doesn't allow to modify anything. OP partition in v20 is a complete waste of space and full of junk stuff. We have edited the ntcode in misc by hex editor and have addressed the custom ntcode in cust to use the desired path, but the phone reads the ntcode from the modem as we can still see the factory ntcode in the hidden menu (SVC, Version Info). If we populate the custom ntcode at the kernel level (smem) maybe we can overcome this obstacle. Read this post: https://forum.xda-developers.com/v20/how-to/bounty-thread-lg-v20-root-h990ds-t3493062/post72323004
And thanks for the Re-uploaded kernel. It's more stable than the previous stable 2.2 build.
Personally I was using 2.2 beta 26 as it was working better than other builds, but I can confirm that the new re-uploaded build is slightly better than beta 26. Benchmarks: Antutu -> 2.2 beta 26 (156K) --- 2.2 Stable Re-uploaded (161K)
We would greatly appreciate if you could help us to fix some issues regarding the development of the stock kernel as you know how to deal with the dirty santa stuff. (We've found out that it's causing more issues than expected) If you're willing to guide us and tell us the steps I can send you the Telegram kernel development group link.
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
henrylar said:
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
Click to expand...
Click to collapse
If you're upgrading the current kernel just dirty flashing the new version over the old version followed by magisk is enough.
But if wanna flash a different kernel, you should first flash a clean bootimage then flash the custom kernel followed by magisk.
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Dishe said:
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Click to expand...
Click to collapse
We need to get something working first, then we will open the game to the other variants but we need help raising money to get this done, so if you care about a new kernel for your v20 please help us with the money now.
We have about $130 now. But it isn't enough for an expert dev to make this happen.
Currently we are dealing with touchscreen issue. LG sources are trash and a real dev knows how to deal with them.
i95swervin said:
Curious is anyone on a h990 has tried alpha kernel from my rom project. If you have let me know what was working and what wasnt.
Also why not mk2k kernel ? The dev has done a lot of work for this device.
Click to expand...
Click to collapse
No we haven't tried that kernel. Kindly send me the boot image so I can test it.
About the mk kernel. It's the only kernel available for us, but we have some problems with it like general lagging, apps getting killed and memory problems. And these problems are more severe for h990ds variant.
I the end, if you can help us with kernel development (building or just helping to fix few issues), I can send you the group link.
UPDATE:
I flashed the h910 stock kernel inside the AO rom.
It has static screen issue. However I fixed it by covering the proximity sensor for some seconds. (However this trick won't work on h990ds kernels.)
Sims do not being read.
The UI was smoother comparing to MK kernel but it started lagging after a few minutes.
I can tell stuff were crashing in the background.
Hi Guys,
I am ready to become beta tester for this kernel. I have this device with root and its H990DS India version. I know bit about android and give you crash reports. Please post me link of telegram. I have already replaced its thermal paste to make it cooler and this mod really worked as now device lot better than earlier hot pot condition. Even with mk2000 kernel (great respect for developer) its standby battery sucks. I have Lenovo Z2 plus which also does have same Qc 820 and poor software but due to developer efforts now it is smooth as butter. Hope this kernel solves most of the problems and I am ready to dive into depths of kernel development to save this last of its kind removable battery super phone. Kudos to all developers.
I m also ready to become a tester
Count me in. I'll donate $20.