Official nightlies aren't happening anymore,
so here's a more up to date build. Vanilla cm12.1 except for eri.xml/apn tweaks and binfmt_misc enabled in kernel.
Special for the a5_chl Virgin Mobile US Desire 816,
may work ok on other a5's too.
Note: a5_dug, a5_dwg dual sim telephony are not working correctly. buyer beware.
Flashes fine with official TWRP.
Official HTC firmware here:
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
I strongly suggest updating your firmware to htc lollipop with an official ruu or you may have hardware issues like touchscreen, wifi, and/or bluetooth problems. It might work with kitkat firmware though, and you are free to try if you want. Post results if you do.
It appears kitkat firmware can cause not only touch issues but wifi issues.
xXminiWHOOPERxX said:
Okay ,
Rom and firmware are two different things... inside OTA's it contains a firmware.zip at which updates bootloader, radio, etc.... so without taking firmware upgrades and just installing what's released on XDA will lead you to bugs other users don't have ..
For Example :
4.4.4 firmware will work with 5.0.2 fine for some users and some have to update too 5.0.2 for Wi-Fi to work...
But any Android version past 5.0.2 you need to have either lollipop firmware or marshmallow firmware in order for Wi-Fi to work...
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Wipe cache, data, and system for clean flash.
Dirty flash not recommended. 5.0 gapps crash on 5.1
If you wanna try a dirty flash I recommend wiping system, cache, and dalvik cache, then your apps and some settings may survive.
Disclaimer: Void warranty, not responsible for anything, you know flashing is your choice and any damage is your own problem.
issues:
mobile data sometimes needs toggled to activate, using airplane mode on/off.
apparently the livedisplay function isn't working well ( maybe not at all)
as mentioned above, dual sim devices not fully functional.
I'm afraid that since I have a mostly working marshmallow build, that needs TLC and attention paid to it, that I can't justify putting any more time into cm12. So unless there security patches released or something, the 12/25 is the last cm12 build I'm releasing.
Download folder:
https://androidfilehost.com/?w=files&flid=45601
visual voicemail see here: http://forum.xda-developers.com/showpost.php?p=64395211&postcount=38
sultanxda's SnapdragonCamera is included as of 12/25 build. it seems to freeze on the first picture after installation but works ok after that once rebooted.
I'm leaving the link to the source built from the ROM standalone camera zip in case anyone needs it. Flash in recovery. If you flashed the one I ripped from the Yureka forum, flash this one over it.
You may have to clear its app data if flashing over, and it may freeze. The 12/25 ROM seems to get along OK with the camera after the first picture and a reboot if you really want the camera.
https://www.androidfilehost.com/?w=files&flid=46051
Source: official CM repo with these changes:
https://github.com/bigsupersquid/android_device_htc_a5
https://github.com/TheMuppets/proprietary_vendor_htc
https://github.com/bigsupersquid/kernel_htc_msm8974_arch_arm_configs_cm_a5_defconfig
https://github.com/bigsupersquid/frameworks_base_core_res_res_xml_eri.xml
https://github.com/bigsupersquid/vendor_cm_prebuilt_common_etc_apns-conf.xml
https://github.com/bigsupersquid/android_packages_apps_SnapdragonCamera
screenshot of interesting format of app drawer:
{
"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"
}
Thanks for continuing the builds! I'm flashing right now and will let you know how it works.
(Flashing on HTC A5_CHL Sprint Prepaid)
EDIT:
Everything seems to be running smoothly, and I haven't found any bugs. (I haven't tested cellular or data, just wifi)
Even though it is said it's for CHL, I would appreciate if someone would try it on UL version and post the results.
bonczas said:
Even though it is said it's for CHL, I would appreciate if someone would try it on UL version and post the results.
Click to expand...
Click to collapse
it's tweaked for chl, but the device code detects several varieties.
according to the zip updater script:
This package is for device: a5,a5tl,a5dug,a5dwg,a5chl,a5ul;
as people test them I can add to the OP.
I only have a chl myself.
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Is the dual sim problem on a5dug will ever be fixed on our phone or is just a cyanogenmod 12 problem that will never be fixed. I searched hours on google and didn`t find anything useful...
Shedal said:
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Click to expand...
Click to collapse
It works as well as any other CM 12.1 build I've run on a device. I haven't found any bugs yet, besides the wifi cutting out briefly once.
I had flashed on 816W dual sim ,Both sim couldn't be detected
@bigsupersquid is 320 DPI the standard for the HTC Desire 816, or is that just the default that CM applies? Just curious, because the UI elements seem much bigger in CM than stock.
Thanks.
@bigsupersquid
Thanks man! I've been running it for about 3 hours with no problems, and its nice to have a up to date secure version of CM. Thanks a bunch for your work!
Flashed it on a5dug and could not detect both sims. I really hope u could make it work for all variants. I have been using 5.1.1 as my daily driver for 2 months now and i love it.
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
@Icelus I can try turning on BT and seeing how long it will stay on if you want. Is there a better way to test?
Icelus said:
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
Click to expand...
Click to collapse
my mms is OK on virgin mobile, and bt seems OK. I'll leave it on a while, then try to pair stuff and toggle it on and off to let you know.
over two hours, bt still on, pairs/forgets/pairs again/ fine, toggles off/on and reconnects automatically.
anyone with hardware issues:
I had another user update their firmware to lollipop to get around touchscreen problems with this rom and it worked.
I will add that to the OP with more info from users to verify the firmware needs to be updated. My htc evo 3d is certainly picky about its firmware and rom combinations.
Bandit Development said:
@bigsupersquid is 320 DPI the standard for the HTC Desire 816, or is that just the default that CM applies? Just curious, because the UI elements seem much bigger in CM than stock.
Thanks.
Click to expand...
Click to collapse
according to pdadb.net,
Pixel density (dot pitch): 266.4 pixel/inch (0.09533 millimetre/pixel)
I haven't checked the original build.prop to see what htc set it at.
qaliza said:
Flashed it on a5dug and could not detect both sims. I really hope u could make it work for all variants. I have been using 5.1.1 as my daily driver for 2 months now and i love it.
Click to expand...
Click to collapse
crazybasss said:
Is the dual sim problem on a5dug will ever be fixed on our phone or is just a cyanogenmod 12 problem that will never be fixed. I searched hours on google and didn`t find anything useful...
Click to expand...
Click to collapse
while I'd like to help with that, but I don't have the hardware to test on; without that there's too much guesswork. Google isn't much help, implies RIL patch based on other phones with same issue. Sorry. I'll add the info to the OP though.
Shedal said:
How usable is this build? Would you recommend it for daily smartphone use? Or is this just a preview / proof of concept?
Thanks!
Click to expand...
Click to collapse
This seems stable to me, actually haven't had one random reboot yet, or other noticable hiccup. Way better than the kitkat I daily drivered on my old optimus v.
Now if I decide to play with marshmallow, and actually get it booting, that would be proof of concept/alpha most likely.
Does this have the issue where Bluetooth turns off randomly while on and it becomes unable to be reenable until reboot? Cuz that's my only issue with cm12 so far
Icelus said:
Do MMS and Bluetooth work well on this? Every other version of CM I've tried, bluetooth turns off after an hour or two and not even a reboot will turn it on again.
Click to expand...
Click to collapse
bigsupersquid said:
my mms is OK on virgin mobile, and bt seems OK. I'll leave it on a while, then try to pair stuff and toggle it on and off to let you know.
over two hours, bt still on, pairs/forgets/pairs again/ fine, toggles off/on and reconnects automatically.
anyone with hardware issues:
I had another user update their firmware to lollipop to get around touchscreen problems with this rom and it worked.
I will add that to the OP with more info from users to verify the firmware needs to be updated. My htc evo 3d is certainly picky about its firmware and rom combinations.
Click to expand...
Click to collapse
exProphecy said:
Does this have the issue where Bluetooth turns off randomly while on and it becomes unable to be reenable until reboot? Cuz that's my only issue with cm12 so far
Click to expand...
Click to collapse
I'm not having any bluetooth problems at all. but I haven't done much more than test it to be sure it works, either. I'll leave it on longer and see if it drops out.
bigsupersquid said:
I'm not having any bluetooth problems at all. but I haven't done much more than test it to be sure it works, either. I'll leave it on longer and see if it drops out.
Click to expand...
Click to collapse
I can't keep mobile data going...I'm on VM but apparently where I'm at the switching between 3G and 4G makes it angry...
Sent from my 710C using Tapatalk
Related
{
"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 everyone once again to a brand new Android. Here you will find unofficial builds for LiquidSmooth v4.0 running Android 5.0 Lollipop. Bare in mind that these are currently in the ALPHA stage, so expect bugs here and there and things to be a little off. This is early in development and may or may not be daily driver ready yet. And now, on with the show.
Click to expand...
Click to collapse
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
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.
We ask that you do your part to know your device and know how to recover from problems before you flash!
Code:
[URL="https://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]
Code:
You can download the latest build from [URL="https://www.androidfilehost.com/?fid=95832962473398652"][COLOR="Blue"]]RIGHT HERE[/COLOR][/COLOR][/URL] (Current Build: 12/06 )
Gapps can be found [URL="https://www.androidfilehost.com/?fid=95832962473398367"][COLOR="Blue"]here[/COLOR][/URL] thanks to @rogersb11
INSTALLATION INSTRUCTIONS
1) DO A BACKUP!
2) If you haven't prior to this step, flash the Shift Eternal CM12 kernel, then reboot recovery.
3) Factory Reset, Wipe Cache, Wipe Dalvik.
4) Wipe System
4) Flash ROM then flash Gapps.
5) Reboot and enjoy!
Also note that the initial boot takes a good amount of time. Upwards of 10 minutes in some cases. Just be patient when you get ready to boot into the system. It will eventually start up.
IMPORTANT NOTE:
You must be on a Lollipop compatible kernel and recovery for this to flash. Currently, the only one available is the Shift Eternal CM12 kernel from @rogersb11. You can download it here. This ROM package contains the same kernel so you will not have to reflash it after flashing the ROM. Questions related to the kernel can be directed to this thread.
You will not have a keyboard upon the initial boot. Skip through the initial setup process then do the following:
Go to Settings>Language and Input
Select the current keyboard.
A pop up will then come up and you need to flip the hardware switch in the top right corner to on.
After this you can then go through with signing in with your account, setting up wifi, etc.
Please remember that these are UNOFFICIAL ALPHA BUILDS. This meaning nobody from the LiquidSmooth team should be expected to help you if you run into any issues. Bugs should be reported to THIS THREAD ONLY. I will do my best to address and fix them as I can. I'm not a master developer, just a builder. But I am learning, and I will try my best to track down fixes to relevant bugs.
Click to expand...
Click to collapse
KNOWN ISSUES
As reported by @rogersb11 in his CM12 thread, "If you don't have WiFi on the device will reboot upon going to sleep so LEAVE THE WIFI ON." This is a Lollipop bug in general, and currently has no fix.
SPECIAL THANKS
Special thanks to the entire LiquidSmooth team for building this awesome ROM. I just compile it from source for this device and the ROM would not be here without their dedication and hard work to provide it.
Special thanks also once again to @rogersb11 for his help and guidance and tireless work to bring the device tree up to be ready for Android 5.0 ... Seriously, this dude has coded his fingers to the bone to make this a reality. I wouldn't have this thread up and going already without him. So be sure to let him know how thankful you are for his work to keep this device alive.
XDA:DevDB Information
Unofficial LiquidSmooth v4.0 for the SGH-I777/959G, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
TheGeekyNimrod, rogersb11
Source Code: https://github.com/LiquidSmooth/android
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Current Beta Version: LiquidSmooth v4.0
Beta Release Date: 2014-12-06
Created 2014-12-07
Last Updated 2014-12-07
RESERVED
Reserved one more just because
TheGeekyNimrod said:
Reserved one more just because
Click to expand...
Click to collapse
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
omar71693 said:
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
Click to expand...
Click to collapse
Hmm. I'm not sure. Haven't had that issue. A guess says it could be the Gapps, but I can't say that for sure though because I tested with different Gapps than the ones listed. Have you tried going back and wiping Dalvik and reinstalling Gapps?
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
Hmm. I'm not sure. Haven't had that issue. A guess says it could be the Gapps, but I can't say that for sure though because I tested with different Gapps than the ones listed. Have you tried going back and wiping Dalvik and reinstalling Gapps?
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Yeah, I actually did. I'm going to try some other things throughout the day and report back.
OMG, I can't believe there is ANOTHER lollipop build for the s2 . Oh BTW where you listed me as a contributer if you remove the @ before my username it will link me correctly. You don't need that on DevDB. Just edit profect at the top and then it automatically links the username without the @ in those contributor boxes
omar71693 said:
Thanks for all the hard work. Just a quick question. I assume this isn't happening to everyone, but Google Play Services crashes, not allowing me to create my backup account. Does the same on the cm12 build.
Click to expand...
Click to collapse
Yah, I'm having the same google play services FCs. I also tried bpear's Lollipop Gapps and that didn't work either . . .
NOTE: I did have the same problem on @rogersb11 Cm12 build too
I tested this with the 5.0 gapps from here. But if you try it, you will have to strip a few unneeded apps out of it for the sake of internal storage space. I can't remember exactly which ones I pulled out of it, but you can pretty much just use Google Play, Play Services, and Google Services Frameworks, and download the rest from the PlayStore
rogersb11 said:
OMG, I can't believe there is ANOTHER lollipop build for the s2 . Oh BTW where you listed me as a contributer if you remove the @ before my username it will link me correctly. You don't need that on DevDB. Just edit profect at the top and then it automatically links the username without the @ in those contributor boxes
Click to expand...
Click to collapse
Got it. I'm really not sure I like how the whole DevDB thing works. Should have just started a regular thread
I may possibly have another build out tomorrow with a few minor tweaks and a little overhaul to the UI. I don't know about everyone else, but I don't like the dark background of, say, the settings app. I'll be working on this and a few minor things tomorrow.
Sent from my SAMSUNG-SGH-I747
I haven't been able to get a working system. It usually hangs on the boot animation (animation freezes). Sometimes it gets to the optimizing apps screen, but it will hang there too. However, if I do NOT flash gapps, it's able to boot, but then hangs on the welcome screen (it freezes and doesn't accept any input). Between failed boot attempts, I'll wipe everything or even go as far as reflashing.
Any ideas?
sciguy125 said:
I haven't been able to get a working system. It usually hangs on the boot animation (animation freezes). Sometimes it gets to the optimizing apps screen, but it will hang there too. However, if I do NOT flash gapps, it's able to boot, but then hangs on the welcome screen (it freezes and doesn't accept any input). Between failed boot attempts, I'll wipe everything or even go as far as reflashing.
Any ideas?
Click to expand...
Click to collapse
Don't bother wiping everything.. Tried that two different times, still having the same results as you. I reverted back to KK and I'm just gonna wait for another build.
Sent from my SGH-I777 using XDA Free mobile app
Remember these are alpha builds. While I haven't had that issue with it yet, doesn't mean it won't happen for others. On mine, once I got to the setup screen I had to reboot the first time, then it allowed me to skip through until I was able to enable the keyboard. And it worked fine after that.
It will stabilize as time goes by for sure.
Sent from my SAMSUNG-SGH-I747
I had hoped to have another build out today, but I had a learning curve to get through first. But now that I have learned, should be late tonight or tomorrow. Mainly UI fixes, maybe a tweak or two elsewhere.
Sent from my SAMSUNG-SGH-I747
Finally! Android L for my GS2! Now to wait for an at&t GS4 custom Lollipop ROM.
[Q] About booting this ROM
When I flash the shift eternal kernel does it give me the right clockwork mod recovery I need to flash the rom? If not,where can I download it?
StoneyJSG said:
When I flash the shift eternal kernel does it give me the right clockwork mod recovery I need to flash the rom? If not,where can I download it?
Click to expand...
Click to collapse
It comes with PhilzTouch which is very a custom recovery based on CWM. It will be the right version for you to flash this and also the version and kernel that the ROM will be running.
Sent from my SAMSUNG-SGH-I747
Was hoping to have a new build posted today, but there are a few too many quirks with it for me to feel comfortable putting it out there. It boots, but there's a few things going crazy. I do believe I can get it worked out though, and will try to get another build done and put out tonight or tomorrow.
Biggest change right now is that I have reverted the Material Dark theme in favor of the Material Light theme that Lollipop is more known for right now. In the future, according to one of LS's lead developers, there will be a switch to go between the two.
Anyhoo, carry on.
My internal storage is not working. Google play services not working. Browser is also not working. Unable to install any app at all. Very nice rom though. Once a stable version is released i will use it as daily driver.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
General:
AOSP 5.1 and CM12.1 for Samsung Galaxy Ace 4 (SM-G313HU). Note that Google apps are not included.
What works:
Pretty much everything
What does not:
FM Radio (removed from the firmware)
Download:
Downloads moved.
CM12.1
AOSP
Google Apps
Screenies:
{
"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"
}
Sources:
Device tree
Kernel repo
Please report any bugs to this thread.
Thanks alot to TheNikiz for a device tree and helping me with some thingies.
Did you figure out the codec issues? For example the Facebook video playback?
Nikiz said:
Did you figure out the codec issues? For example the Facebook video playback?
Click to expand...
Click to collapse
Yeah, you need to patch frameworks_av like in cm12 to add YcbYCr color format, and add proper media_codecs.xml. Haven't tested facebook tho, but video recording/playing and apps like youtube work. Check out git repo.
Tho that routing still annoys crap outta me, it tries to add route to gateway, but fails, cause gw is in another network, we need to add static route to rmnet0 address instead, i tested adding it manually and it worked.
@itigr Thanks for the ROM but isn't there any possibility of getting the mobile data thing fixed permanently?
Also,ROM with pretty much everything working with tiltle[Experimental].
weird. @Nikiz how did you unlock the bootloader of the almost dead Trend 2 or it wasn't locked?
Edwin Hamal said:
@itigr Thanks for the ROM but isn't there any possibility of getting the mobile data thing fixed permanently?
Also,ROM with pretty much everything working with tiltle[Experimental].
weird.
Click to expand...
Click to collapse
No, at least not now. And i don't want to spend one more week figuring out why it doesn't work, i will probably pause dev for indefinite period 'coz i'm tired of this.
Yep, cause i messed with sources alot
Edwin Hamal said:
@Nikiz how did you unlock the bootloader of the almost dead Trend 2 or it wasn't locked?
Click to expand...
Click to collapse
Umm, what? The Trend 2 bootloader was never locked. (Well, it shows the invalid signature check, but still allows booting) I think you mixed it up with the Huawei Y5-project I have now. (Got the bootloader unlocked and a custom recovery running on it within 24 hours of owning it.. )
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Edwin Hamal said:
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Click to expand...
Click to collapse
Got the bootloader unlocked by just typing "fastboot oem unlock-go" into the terminal. I just made a minimal device tree for this phone, with the partition information, TWRP settings and the fstab-file. I just built it and I was surprised that it booted on the first try. All I had to do was to fix the fstab-file, change the pixel format and add couple of recovery settings to make it fully working. Building CM12.1 now. (Luckily there was couple of officially supported, similar Huawei devices, so I just copied bunch of code from there.. )
Nikiz said:
Got the bootloader unlocked by just typing "fastboot oem unlock-go" into the terminal. I just made a minimal device tree for this phone, with the partition information, TWRP settings and the fstab-file. I just built it and I was surprised that it booted on the first try. All I had to do was to fix the fstab-file, change the pixel format and add couple of recovery settings to make it fully working. Building CM12.1 now. (Luckily there was couple of officially supported, similar Huawei devices, so I just copied bunch of code from there.. )
Click to expand...
Click to collapse
Lucky for you that almost all Huawei are Snapdragon.
doesntexits said:
Lucky for you that almost all Huawei are Snapdragon.
Click to expand...
Click to collapse
Yeah, this processor is supported by AOSP too, so no patching needs to be done, which is nice. Currently I have only got to the boot animation. ADB doesn't work for some reason. (eng-build and insecure ADB)
Nikiz said:
Yeah, this processor is supported by AOSP too, so no patching needs to be done, which is nice. Currently I have only got to the boot animation. ADB doesn't work for some reason. (eng-build and insecure ADB)
Click to expand...
Click to collapse
Welcome to my world Now i'm still stuck at Samsung logo. adb shell works fine but logcat gives me a blinking cursor, ueventd.scx15.rc is included in out/target/vivalto3gvn/root. Idk the reason why it doesn't even gives me a boot animation. Tried stock init but it reboots straight to recovery mode. Now i wish i have a buddy to work with this phone.
Edwin Hamal said:
@itigr ok... but...
First of all AOSP sucks(It doesn't even have a file manager)
There's alot more bugs i.e
Wifi does't work (always shows exclamation even though the wifi is working good)
Calls doesn't end(mention about the work around for this too)
Last thing isn't there anyway that I can flash both ROM's by @Nikiz and you without editing things?
Coz having to switch recovery is really a hard task!
Click to expand...
Click to collapse
Welp aosp still isn't as bad, i used to use it with xposed on my old xperia Maybe at some time i will compile cm12.1 or AOSPA (or it's still dead?).
Wifi and calls work, maybe i uploaded an old zip, i was drunk as hell and can't recall it really lol. Reuploading right now, ETA: 40 mins.
Idk how do you want to flash two roms, i've heard it only supported on nexus and still has bugs..
Front camera video recording doesn't work....
Why is this faster than CM12.1?
I wonder why you prefer AOSP over CM though?
@itigr
Codec issues has gone too.(I guess coz fb videos play now)
Edwin Hamal said:
Front camera video recording doesn't work....
Why is this faster than CM12.1?
I wonder why you prefer AOSP over CM though?
@itigr
Codec issues has gone too.(I guess coz fb videos play now)
Click to expand...
Click to collapse
No idea, i just kinda like pure android lol. Dunno how to fix front camera tho. I'm compilling cm12 now and omni 6.0 tomorrow.
Great but CyanogenMod is also stock android isn't it? with added features which stock lacks.
By the way you're compiling CM12 or CM12.1?
Omni?! Guess you're die heart fan of stock Android! Pure Stock Android rather! @itigr
Edwin Hamal said:
Great but CyanogenMod is also stock android isn't it? with added features which stock lacks.
By the way you're compiling CM12 or CM12.1?
Omni?! Guess you're die heart fan of stock Android! Pure Stock Android rather! @itigr
Click to expand...
Click to collapse
Yeah. CM12.1, i already compiled it and "fixed" mobile data (not really but now you don't have to mess with scripter since workaround is added to boot image). Uploading it now, 50 minutes left. Only thing is left to fix is offline charger but i got no idea how.
Not really
The reason i am compiling omni because i already had it downloaded, i would compile cm13.0 but i'm on my 2nd house now and internet here is crappy + i also heard it's not complete yet and compilinig can fail sometimes. It took me around 2 days to download cm12.1 source with a lot of disconnects.
Added cm12.1 and pushed data fix and patches to github.
itigr said:
Added cm12.1 and pushed data fix and patches to github.
Click to expand...
Click to collapse
Installed CM12.1 and there's one more problem.
Don't known if I'm only one who has this issue
but after some time device doesn't detect any
Sim cards till a reboot.(Faced this in the AOSP as well)
Has it happend to you?
Edwin Hamal said:
Installed CM12.1 and there's one more problem.
Don't known if I'm only one who has this issue
but after some time device doesn't detect any
Sim cards till a reboot.(Faced this in the AOSP as well)
Has it happend to you?
Click to expand...
Click to collapse
I was testing it for 2 days and have never noticed it.
Did you wipe data/cache/system after flashing?
itigr said:
I was testing it for 2 days and have never noticed it.
Did you wipe data/cache/system after flashing?
Click to expand...
Click to collapse
Nah,just did wipe to install new ROM! using
philz.I think it does wipe everything required...
Edit:After flashing???
Edit:Figured out that decive doesn't detect sim card when I soft reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cyanogenmod 12.1 Unofficial Kinzie Port
Hi, everyone! Here's a little surprise for you: @Xadro and I have been working the last couples of weeks on porting CM12.1 to our Kinzie devices... and we have! So we wanted to share this little present with you, a port of CM12.1 for our brand new X Force device.
SCREENS
Some good old screens for you
COMPATIBILITY
From what we've tested, it works on EU Moto X Force, we don't know if it will work on devices from other zones - China, Brazil... Also, even if you could flash the ROM on US Droid Turbo 2 it probably wouldn't work as it doesn't have the Verizon vendor files on it, sorry .
WHAT WORKS
As far as we know, everything that's not Moto related.
What does that mean? No Moto Voice, Moto Actions or Moto Display, so please think carefully before flashing so you don't have to go back to store Moto later. Moto Gallery and Moto Camera can be flashed, though.
Also, if you see anything that's not working properly, please contact us.
WHAT DOESN'T WORK
As stated before, most Moto Apps will just FC.
Some applications fail to install from Play Store with an SDCard on the device.
Anything else you find while using it.
DOWNLOADS
CM12.1 for Kinzie ROM - [27/02/2016]
23/02/2016 version - works fine with multiSIM
Open GApps - Choose ARM64 and 5.1!
Modems
Lollipop 5.1 EU Modem
Lollipop 5.1 LATAM Modem
INSTRUCTIONS
Please follow these instructions carefully:
Copy the ROM and the GApps zip to your phone storage - internal or sdcard, it doesn't matter.
Unlock bootloader. CAUTION: this will probably void your warranty AND WIPE ALL YOUR DATA, INCLUDING INTERNAL STORAGE - photos, songs, documents...
Flash TWRP recovery from bootloader. I recommend using @Xadro's. If you are using mine, install this one, since mine won't let you flash the ROM.
Code:
fastboot flash recovery TWRP-3.0.0_kinzie.img
If you were already on Android 6.0, flash the Android 5.1 modem. Otherwise you'll have network issues.
Code:
fastboot flash modem modem.bin
Reboot to recovery.
Do a full backup - you'll probably thank me later .
Wipe data, some settings from stock ROM may lead to bootloops or malfunction.
Install CM from the zip.
Install GApps.
Reboot and enjoy!
SOURCES
Kinzie Porting Github - the repos may be messy, we'll try to tidy them up a bit in the future.
CREDITS
CyanogenMod team for their base source and documentation.
AICP Team for their clark sources, since we used them as a base for kinzie.
Of course, @Arasthel and @Xadro .
CHANGELOG
[27/02/2016]
CPU freqs adjusted to stock ROM ones
Solved charging white screen issue - and probably, overheating while charging
IR sensors working!
[23/02/2016]
Added compatibility with MX and BR devices.
Improved WiFi connection stability by changing the way dhcpcd is started.
[20/02/2016] - Initial upload
Thanks a lot, I'll test it tomorrow!
I have a question : why lollipop?
Inviato dal mio XT1580 utilizzando Tapatalk
Razorbacktrack5535 said:
Thanks a lot, I'll test it tomorrow!
I have a question : why lollipop?
Inviato dal mio XT1580 utilizzando Tapatalk
Click to expand...
Click to collapse
One has to start somewhere.
Xadro said:
One has to start somewhere.
Click to expand...
Click to collapse
Why not with CM14 then?
Edit: Awesome guys!!! Thank you so much for your hard work
Sent from my XT1580
I'm crrying... THANK YOU. Any bug too critical for daily driver?
Edit: Reporting, everything seems BUTTERY SMOOTH, flashed LL modem, and got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?
MuyKurioso said:
I'm crrying... THANK YOU. Any bug too critical for daily driver?
Edit: Reporting, everything seems BUTTERY SMOOTH, flashed LL modem, and got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?
Click to expand...
Click to collapse
I also just tried flashing and everything seems to work except for no sim card recognized. I also have mexican moto x Force. If anyone can tell us how to get service that would be great.
mr2sweet said:
I also just tried flashing and everything seems to work except for no sim card recognized. I also have mexican moto x Force. If anyone can tell us how to get service that would be great.
Click to expand...
Click to collapse
I'm going to try to flash UK modem and see if that will fix it, I don't really care if i lose the second sim slot. I don't use the dual sim setup anyway. Downloading right now, will report back if succesfull.
Edit: Nope, no SIM...
I wonder if they can do whatever they did to the eu modem to our mx modem to make it work with the port?
Arasthel said:
IR Sensor won't work as it deeply depends on Motorola framework files to work. Maybe we can port it someday, but it's not likely to happen any time soon.
Click to expand...
Click to collapse
CM dev got the Moto Quark IR sensors to work just fine. (Droid Turbo XT1254, Moto Turbo XT1225, "international" Moto Maxx XT1225, U.S. Moto Maxx XT1250)
So, it's possible.
We have 12.0, 12.1 (Lollipop 5.1.1) and now Preview Build of CM 13 (Marshmallow), all with Motorola IR sensors. Other Quark ROMs are also using CM's code.
mr2sweet said:
I wonder if they can do whatever they did to the eu modem to our mx modem to make it work with the port?
Click to expand...
Click to collapse
Actually, we didn't do anything to the EU modem, it's the stock 5.1 one. If you flash the MX 5.1 one and it doesn't work, that's because build.prop is not configured properly. It would be helpful if you upload your stock build.prop, but it will be difficult to detect your phone region in order to use the configuration you need. Maybe @Xadro can think of a better solution.
ChazzMatt;=65436576 said:
CM dev got the Moto Quark IR sensors to work just fine. (Droid Turbo XT1254, Moto Turbo XT1225, "international" Moto Maxx XT1225, U.S. Moto Maxx XT1250)
It's possible.
Click to expand...
Click to collapse
We're not saying it's not possible, we're saying it's a really difficult task. Quark uses the STM401 sensor device with Moto Sensor Hub to make IR work. Instead, Clark and Kinzie use the STML47X sensor. While there is a library module for STM401 there doesn't seem to be one for STM4L. Maybe the STM401 will partially work, but I wouldn't bet on that...
MuyKurioso said:
flashed LL modem, got everything working except sim, i'm getting the only emergency calls. Is a Mexican Moto X Force. Anyone has a clue of how can i get it to work?
Click to expand...
Click to collapse
Not clear which modem you flashed...
Re-flash your stock modem for YOUR phone.
If you already did that, sorry.
Ok, so here's my Build.prop, I don't know if that would help. Anyway, thanks a lot.
https://drive.google.com/file/d/0B14IVKIVgBZWOTdJU01qaW5YdHM/view?usp=docslist_api
Edit: it's the lollipop stock Build.prop
MuyKurioso said:
Ok, so here's my Build.prop, I don't know if that would help. Anyway, thanks a lot.
https://drive.google.com/file/d/0B14IVKIVgBZWOTdJU01qaW5YdHM/view?usp=docslist_api
Edit: it's the lollipop stock Build.prop
Click to expand...
Click to collapse
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.
Arasthel said:
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.
Click to expand...
Click to collapse
Yeah, i've already flashed the right módem, in fact i downgraded to stock 5.1.1 to be ready for your ROM cause CM or AOSP is what I was craving for the X Force since i've found the stock to be solid, but sluggish at times. Will try this Build in a few hours, when I can get some WiFi coverage, and then report back. Thank you for your hard work.
Arasthel said:
Thanks for the build.prop, I was able to make a new configuration for LATAM Kinzie. Can you try this version? Also, remember to flash the right modem (LATAM for 5.1). It's the "NON-HLOS.bin" file that comes on the stock ROM zip, or at least it was on EU.
Click to expand...
Click to collapse
So, still no SIM... Luckily I made a backup this time...
Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier
Arasthel said:
Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier
Click to expand...
Click to collapse
in the stock firmware, or in your rom?
It should give the same result on both of them.
Arasthel said:
It should give the same result on both of them.
Click to expand...
Click to collapse
oh, ok. give me a sec, i can't seem to get my pc to recognize my moto x force in the ADB devices list with your rom. Will restore backup and try on the stock one.
---------- Post added at 10:18 PM ---------- Previous post was at 10:09 PM ----------
Arasthel said:
Could you tell me what's the result of using:
Code:
adb shell getprop ro.boot.carrier
Click to expand...
Click to collapse
retmx
CM14.1 is here for the LS990, aka the Sprint LG G3.
This is unofficial until one framework change gets merged in for fixing LteOnCdma support. Once that merge happens, we'll get nighties.
This should have fully working modem, nfc and all the things you've come to enjoy. World phone mode is enabled, but I do not have an activated GSM sim to fully test the GSM side.
Instructions
This has only be validated on ZVC or newer firmware.
Download cm-14.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
The latest will be available at:
http://downloads.codefi.re/shelnutt2/g3/ls990/cm14_1/
Gapps:
OpenGapps:
http://opengapps.org/?api=7.1&variant=nano
Click to expand...
Click to collapse
Known Issue
None!
Click to expand...
Click to collapse
Change Log
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
invisiblek
Kasual52e
rashed
Click to expand...
Click to collapse
Source
http://github.com/CyanogenMod
Click to expand...
Click to collapse
Is the speakerphone Echo fixed?
There is a setting in stock phone "call settings" that has to be changed in order to keep it from happening.
In the stock "call settings" you have to turn off noise suppression and turn on voice enhancement:
{
"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 think all of the source built Roms are built with this setting set to it's default settings which causes the echo even in the stock Roms until it's changed to the above. (The pic is from MM but it's prevalent in the Nougat Roms as well).
People do a lot to try to fix the problem, change: mixer_paths.xml to no avail. turning the volume down, changing the Mic settings doesn't take the problem away.
I would love to see this fixed. I can't use any of the source built Roms because of it. (I can't stand to put the phone to my head, I have to have speakerphone).
Anyway hope this gives the right people the insight to fix the problem.
Thanks for taking the time to bring us these awesome builds.
? Sent from DjRobBlaze's VS985 ? Rockin' ? Fulmics 6.6 ? using Tapatalk. ? ®
Shelnutt2 said:
CM14.1 is here for the LS990, aka the Sprint LG G3.
This is unofficial until one framework change gets merged in for fixing LteOnCdma support. Once that merge happens, we'll get nighties.
This should have fully working modem, nfc and all the things you've come to enjoy. World phone mode is enabled, but I do not have an activated GSM sim to fully test the GSM side.
Click to expand...
Click to collapse
That framework change you mentioned to fix LteOnCdma support, is that in this release and you are waiting for it to be merged with CM official?
Just wanted to thank the OP, this rom is working perfectly (dec 15 build). It's actually more stable than the cm14.1 nightlies for the d851 G3 (T-Mobile). I've had no sim card or data issues of any kind. Miracast works great as well.
bavarianblessed said:
That framework change you mentioned to fix LteOnCdma support, is that in this release and you are waiting for it to be merged with CM official?
Click to expand...
Click to collapse
It is included in these unofficial builds. It is awaiting merge upstream, https://review.cyanogenmod.org/#/c/176865/
in light of the news today, I'm guessing the ls990 is never getting merged into the nightlies, and we might be looking at a whole new rom in the future (lineage).
its hard to believe really... cyanogenmod seemed like it was poised to take over... its been my favorite rom for about 3 years now, and was really starting to get good in this 14.1 build (miracast finally works!)
i guess just thanks for building these, not sure where we all go from here...
Whatever happens there will continue to be unofficial builds of either cm or lineage until we are able to get the necessary changes merged to make stable official builds
Engineers running businesses get owned by business people running businesses. From 10k km, it seems the cyanogen Corp got edged out by 'partners' with less then admirable ethics and motives. The code is still ours, thanks to GPL. Our community will continue to build and rebuild. Kondik has learned to play hardball the hard way, and will hopefully dust himself off and come back even stronger. The hope for a mainstream android fork continues... and it's likely to keep on that way just like 2017 is going to finally be the year of desktop Linux. In the mean time, thank and donate to our developers, their blood oils the machinery of free software.
Rooted ZVC Firmware?
Where can I find rooted ZVC Firmware? I tried this with the rooted ZVB firmware at https://forum.xda-developers.com/sp...990-zvb-root-method-zvb-rooted-stock-t3211878, but after rebooting, it doesn't look like I have root privileges.
rogerdc said:
Where can I find rooted ZVC Firmware? I tried this with the rooted ZVB firmware at https://forum.xda-developers.com/sp...90-zvb-root-method-zvb-rooted-stock-t3211878, but after rebooting, it doesn't look like I have root privileges.
Click to expand...
Click to collapse
Rooted ZVC:
http://forum.xda-developers.com/sprint-lg-g3/development/barecee-zvc-t3257826
Straight stock partitions http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVC
There's a nice little modem/rpm/tz flasher zip in the ZVB folder there that can be commandeered to flash the relevant ZVC partitions with a little zip hacking.
just flashed this after failing at the Resurection and Cypher N roms. I couldnt get data, cell, text or any networks to work.
This worked fine out of the box. Awesome! Nice and smooth. No force closes. Bluetooth appears to be nice and stable at least on my headphones which are a foot away from me. Havent tried my car yet.
On a side note, the whole reason I was trying to upgrade to something nougat based was to get the google assistant working. There appears to be a workaround if you are not a pixel phone listed here. https://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Then I started reading and it doesnt appear the g3 is on its list of supported phones for this. Has anyone tried it yet? Does it work, and if so, what technique did you use?
CMILD561 said:
On a side note, the whole reason I was trying to upgrade to something nougat based was to get the google assistant working. There appears to be a workaround if you are not a pixel phone listed here. https://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Then I started reading and it doesnt appear the g3 is on its list of supported phones for this. Has anyone tried it yet? Does it work, and if so, what technique did you use?
Click to expand...
Click to collapse
You can get Assistant working on the G3... I had it working with AICP and I'm sure it will work with CM but I haven't reinstalled it. The big issue for me was loosing "OK Google" Hotword. I followed the instructions here... https://forum.xda-developers.com/android/apps-games/google-pixel-experience-launcher-dialer-t3478907
Also, if anyone is interested, CrazySuperKernel is working very well with this ROM.... https://forum.xda-developers.com/lg-g3/development/kernel-crazysuperkernel-v1-t3521121
Matteo1219 said:
Also, if anyone is interested, CrazySuperKernel is working very well with this ROM.... https://forum.xda-developers.com/lg-g3/development/kernel-crazysuperkernel-v1-t3521121
Click to expand...
Click to collapse
Thanks, i will give this ROM and Kernel a try once i get my replacement battery
Installed this ROM and so far it is pretty good! Thanks to the dev for the time and effort to put out a good system unlike some of the others who are posting N ROMs that do not work with the phone (ie data, mms, etc). I hope to see further development of this ROM but that might be difficult with CM getting out of the custom OS business.... Great work and thanks again!
len207 said:
Installed this ROM and so far it is pretty good! Thanks to the dev for the time and effort to put out a good system unlike some of the others who are posting N ROMs that do not work with the phone (ie data, mms, etc). I hope to see further development of this ROM but that might be difficult with CM getting out of the custom OS business.... Great work and thanks again!
Click to expand...
Click to collapse
keep an eye on this page, we're supposed to start seeing official builds this weekend (hopefully today)
https://download.lineageos.org/
chat:
https://webchat.freenode.net/?channels=lineageos
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
I got stuck on "Tap & Go" during setup... Don't have another device to try this and it's not letting me skip it
Matteo1219 said:
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
Click to expand...
Click to collapse
Is data texting mms working on sprint?? Still domestic roaming issue??
Matteo1219 said:
The great @Shelnutt2 has continued posting updates for the ls990.... http://downloads.codefi.re/shelnutt2/g3/ls990/laos14_1
Click to expand...
Click to collapse
latest vesion of that rom still switches from digital roaming to sprint. i get lte texting on digital roaming and calls on sprint (
erik077 said:
I got stuck on "Tap & Go" during setup... Don't have another device to try this and it's not letting me skip it
Click to expand...
Click to collapse
With a clean install? Which GApps package are you using?
{
"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"
}
LG V20
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the LG V20.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official Builds:
h910
h918
h990
ls997
us996
us996d
vs995
Unofficial - built once a month by me, includes GApps and Pixel goodies:
h910
h918
h990
ls997
us996
us996d
vs995
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
This uses a port of Linux kernel version 4.4.
Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996
Builds will roll within a week!
as this is based on android 12, and this device is about 6 years old, isn't it slow?
itt533 said:
as this is based on android 12, and this device is about 6 years old, isn't it slow?
Click to expand...
Click to collapse
Runs fine enough here - no worse than A11.
itt533 said:
as this is based on android 12, and this device is about 6 years old, isn't it slow?
Click to expand...
Click to collapse
better than 11 in my experience
Have anyoned tried dirty flashing from LOS18?
Cheers.
loyukfai said:
Have anyoned tried dirty flashing from LOS18?
Cheers.
Click to expand...
Click to collapse
Builds aren't out yet
Thanks for bringing 12 to the v20! Not complaining or arguing at all but why didn't you just skip 12 and move to 13 all together?
Lenny_One said:
Thanks for bringing 12 to the v20! Not complaining or arguing at all but why didn't you just skip 12 and move to 13 all together?
Click to expand...
Click to collapse
I planned to but Bluetooth is horridly broken on 13 for one reason or another - figured I wouldn't hold release back for it.
I'm new to the V20 and picked my used device last Thursday (990DS variant), already unlocked thanks to this forum and played with some ROM's and Kernels for a while.
I already downloaded and flashed the unofficial version and I really don't like the design language/choices that Google made, but it's working very well. The only thing that's not working (and I didn't notice on other ROM's) it's the FM Radio (I don't use, but tested with the stock before unlocking).
Since I try not using the physical buttons unless it's really necessary I use in Lineage 18 the volume panel to change it (the same panel it's not available in this release), and Simple Reboot for other tasks that requires the power button menu. But I discovered that the double tap to wake don't work after 5 seconds when you lock your device (If you try to use between 1 and 3 seconds it works), but after that you need to use the power button or the fingerprint. But If I wanna check notifications or the time without unlocking my device DT2W it's useful.
I personally use LineageOS for microG and when it's available there (or even a regular Lineage without gapps for testing) I will use this V20 as a daily driver since my OnePlus3 it's out of service because of my mistake with the LCD.
My sincere congratulations for the 4.4 Kernel porting, it's really impressive the work of the community here.
Off-topic: Since my last device was an OP3 I was really used to off screen gestures (flashlight, music playback etc). There's something similar that could be used in this device? Thanks!
Hi, thanks for your hard work OP and everyone who contributed to keep this old device of ours running up to date. We really appreciate it! It's my first time flashing a custom rom since the phone was released. Phone broke on me after a year of using (stock no root, ig something inside got damaged because of excessive heat) and on it's fourth year of hibernating I picked it up again and it miraculously somehow fixed itself. I'm in LOS 18.1 right now and so far IR isn't working. Where can I download the 19.1 and I see it's not in known bugs anymore, does IR work?
BTW, is it really not possible to use twrp instead of lineage recovery? Does migrate work on lineage recovery?
dextructor said:
Off-topic: Since my last device was an OP3 I was really used to off screen gestures (flashlight, music playback etc). There's something similar that could be used in this device? Thanks!
Click to expand...
Click to collapse
It's impossible to bake this in custom rom. Your best bet is to use apps that remap the button. There's plenty in play store.
0ldsoul said:
Hi, thanks for your hard work OP and everyone who contributed to keep this old device of ours running up to date. We really appreciate it! It's my first time flashing a custom rom since the phone was released. Phone broke on me after a year of using (stock no root, ig something inside got damaged because of excessive heat) and on it's fourth year of hibernating I picked it up again and it miraculously somehow fixed itself. I'm in LOS 18.1 right now and so far IR isn't working. Where can I download the 19.1 and I see it's not in known bugs anymore, does IR work?
BTW, is it really not possible to use twrp instead of lineage recovery? Does migrate work on lineage recovery?
Click to expand...
Click to collapse
You can use another recovery if you really want to, although los recovery streamlines everything. And i believe the ota updates may rely on having los recovery, npj will need to comment on that.
Overall, no, you don't NEED to use los recovery, but i'd recomend using it.
Also, no, ir still does not work.
xxseva44 said:
You can use another recovery if you really want to, although los recovery streamlines everything. And i believe the ota updates may rely on having los recovery, npj will need to comment on that.
Overall, no, you don't NEED to use los recovery, but i'd recomend using it.
Also, no, ir still does not work.
Click to expand...
Click to collapse
Lineage Recovery is needed for OTA yes.
And, really? IR is still broken?
npjohnson said:
Lineage Recovery is needed for OTA yes.
And, really? IR is still broken?
Click to expand...
Click to collapse
Yes, it still is broken on 4.4 unfortunately (and there's no sign of what the issue could be since 3.18), although we intend to patch it up once we're done with USB as a whole.
xxseva44 said:
You can use another recovery if you really want to, although los recovery streamlines everything. And i believe the ota updates may rely on having los recovery, npj will need to comment on that.
Overall, no, you don't NEED to use los recovery, but i'd recomend using it.
Also, no, ir still does not work.
Click to expand...
Click to collapse
I see. I don't really use OTA. I always manually update roms thru recovery.
AShiningRay said:
Yes, it still is broken on 4.4 unfortunately (and there's no sign of what the issue could be since 3.18), although we intend to patch it up once we're done with USB as a whole.
Click to expand...
Click to collapse
I guess the only way to get LOS 19.1 is thru OTA? I went to LOS website and there's only 18.1 available.
If 19.1 becomes available and I'm in 18.1 rn do I have to factory reset first before flashing 19.1?
0ldsoul said:
I see. I don't really use OTA. I always manually update roms thru recovery.
I guess the only way to get LOS 19.1 is thru OTA? I went to LOS website and there's only 18.1 available.
If 19.1 becomes available and I'm in 18.1 rn do I have to factory reset first before flashing 19.1?
Click to expand...
Click to collapse
Just follow the wiki guide, everything will work fineJust follow the wiki guide, everything will work fine
('h830', 'Wednesday, 2023-03-29')
('h850', 'Sunday, 2023-04-02')
('h910', 'Thursday, 2023-03-30')
('h918', 'Thursday, 2023-03-30')
('h990', 'Sunday, 2023-04-02')
('ls997', 'Sunday, 2023-04-02')
('rs988', 'Sunday, 2023-04-02')
('us996', 'Thursday, 2023-03-30')
('vs995', 'Tuesday, 2023-03-28')
Here is the build schedule for 19.1
Sorry if this is not allowed here. I just want to ask my v20 is still suffering from thermal throttling. Is my phone bad or does v20 really act like this? I'm in Los 18.1. I only do browsing and watching videos. I know this phone broke on me before due to excessive heating it even reached 50°C+. Currently the highest I had is 47.2°C while using. Are there any mods for Android 11? I saw one for Nougat. I don't think it will work on newer versions.
0ldsoul said:
Sorry if this is not allowed here. I just want to ask my v20 is still suffering from thermal throttling. Is my phone bad or does v20 really act like this? I'm in Los 18.1. I only do browsing and watching videos. I know this phone broke on me before due to excessive heating it even reached 50°C+. Currently the highest I had is 47.2°C while using. Are there any mods for Android 11? I saw one for Nougat. I don't think it will work on newer versions.
Click to expand...
Click to collapse
I don't have much to say for you software wise but you can try to replace the thermal pads and see if it yields better results for you.