I have a Pumpkin KD-C0109-US-A HU. It is a single DIN in which the android screen rolls out and flips up. I addition to the screen it has a radio LED display that shows data like input source, RDS etc. The problem is that when I install Malaysk custom firmware, the radio LED's never indicate that the upgrade process is completed. The letters INIT and the recovery mode graphics continue indefinitely even though the radio works and Malaysk's version of Android functions well. Is there some incompatability between the firmware and the MCU for this type of dual display arrangement? The MCU is MTCB-KLD5-V2.77. Is there a work around? Thanks.
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Brendo said:
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Click to expand...
Click to collapse
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
lotherius said:
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
Click to expand...
Click to collapse
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
windseye said:
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
Click to expand...
Click to collapse
I think the best option would be to run the factory firmware with a 2gb partition. Will test that over this weekend.
I confirmed that the latest "factory firmware" on the HuiFei unit (20150821) functions correctly with the LED display on our single-DIN KLD units. Others reported that the 20150820 download from the same site works as well.
MalaySK uses a 20150820 base that has a slightly earlier timestamp by a few hours. So either his earlier build doesn't support it, or one of the changes he has made has broken support for the LED.
Our units ship with the later 20150820 build and 20150821 build that has been confirmed to be working from the HuiFei firmware site (http://huifei.fs-fileserver.de/cont....4/800x480/KLD 800x480 20150821 DSA Modified/). The 20150821 (dunno about the 820) already has the 2GB partition mod and root, so it's ready to roll.
I don't think I'm going to test further, as I installed the 20150821 from DAS and it has the 2GB partition I wanted, and everything is working. I didn't try the newer build (20151019).
But with that said, I think this thread isn't going to be necessary as the standard KLD Roms *DO* support our single-DIN LED Display - it is just MalaySK that does not.
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Brendo said:
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Click to expand...
Click to collapse
Well personally I got it working buy using one of the "stock" roms with 2gb, so I'm satisfied for now. If anyone else wants to play with it further they can.
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
mgh33 said:
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
Click to expand...
Click to collapse
Great solution. Definetly will try that.
Any ideea if the MCU for this one-din units is a special one? I installed MTCB-KLD-V2.78 from (HuiFei Server) and now I cannot control the flip-up screen. My unit is MTCB KLD one-din with Android 4.4.
Related
This is a flashable ROM from generated from Football's RUU_Vision_Hutch_AUS_1.85.861.3 release. It includes all applications and original vendor configuration. In other words, it is untouched with the exception of the following:
Rooted with my customized version of Superuser (required until ChainsDD releases a version with my patches).
Deodexed with moderate compression throughout.
Busybox installed in /system/xbin.
Added large APNS list to /system/etc.
WWE-equivalent language support.
There are no other changes. Just to be blindingly clear, this is NOT Virtuous; although a future version of Virtuous may be based on this ROM. Anyone building ROMs is welcome to use this as a base. Thanks again to Football for continuing to provide us with the latest RUUs.
Disclaimer: This is a one-time release. Unless a problem can be identified with the changes mentioned above (rooting, deodexing, etc), it will not be updated or supported. Use this as-is or find a ROM which uses this release as its' base if you would like support and/or expect to see changes.
Remember to hit the "Thanks" button if my work ends up being useful to you.
Download ROM
(MD5:a764d0e09975209ab4268cfa3cef3167)
Please do not ask me how this is different than the 1.85 orange release, as HTC does not exactly provide us change logs.
Orange, it is a name of telecom provider, right? If yes is it possible for you to get similar stock ROM but for Era polish provider and a little older, like 1.7...?
I am asking because as a newbe I didn't make any backup for my stock ROM delivered with my phone and I would like have a possibilty to back to the original stock for Era when for example I will have to give my phone back to service.
Or maybe You can suggest other way to back to Era stock, please indicate any thread if you know.
Thanks a lot for helping
Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?
denich said:
Just flashed this ROM. It has a slow desktop draw issue. When I go to the main screen all icons appear very slowly. I do not understand if this ROM is untoched why it has the same issue as Virtuous?
Click to expand...
Click to collapse
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.
Just wondering, What did you use to Deodexed the apks/jars?
rmk40 said:
It's clearly a bug this version of Sense and has nothing to do with Virtuous. This is actually the case with many of the bugs in the ROM, we inherit them from HTC.
Click to expand...
Click to collapse
Seems like a bug only with froyo sense...
bigmoew said:
Seems like a bug only with froyo sense...
Click to expand...
Click to collapse
Push Rosie.apk from 1.82 or 1.72 to fix the problem.
rmk40 said:
Push Rosie.apk from 1.82 or 1.72 to fix the problem.
Click to expand...
Click to collapse
I applied the patch which returns rosie to 1.72 (the patch from virtuous thread). it do no help the problem remains
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1
I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...
You just need to update to latest Color OS available first. Its right HERE. Then unify your storage. After that you're good to go.
Sent ya a message on hangouts mate!
Also, you've probably got a newer LCD panel - most ROMs and recoveries are not compatible with LCD Panel R63419.
Dialing *##*37847# should tell you the screen type.
Latest TWRP recovery and OmniROM are compatible with LCD Panel R63419.
pobbel said:
Also, you've probably got a newer LCD panel - most ROMs and recoveries are not compatible with LCD Panel R63419.
Dialing *##*37847# should tell you the screen type.
Latest TWRP recovery and OmniROM are compatible with LCD Panel R63419.
Click to expand...
Click to collapse
I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware :crying:
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...:fingers-crossed::fingers-crossed:
rahul.90 said:
I just checked and I actually don't have the new LCD screen, maybe another indicator as to why my device came preloaded with the oldest firmware :crying:
So based on stormtroopers reply, do I need to upgrade to the latest firmware first in order to do ANYTHING? Can I jump from 1.2.1i to 2.1.4i with no issues?
It's a shame COS is so buggy, I'm sure the potential of the hardware inside isn't being put to use with this crappy rom.
An absolute beginners guide to this would be so appreciated...:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Omnirom is the only rom that support new lcd for now. Just follow the step.
StormTrooper89 said:
Omnirom is the only rom that support new lcd for now. Just follow the step.
Click to expand...
Click to collapse
he does not have the new lcd screen
suraj.das said:
he does not have the new lcd screen
Click to expand...
Click to collapse
Thats what happen when read while eat. :laugh:
Hi all.
I've got an taiwanese HTC 10 which is on the MM firmware, but I wish to try the Nougat on a custom ROM.
I realise that there is plenty of ROMs, but it seems that's nobody intention to stay close to the stock experience.
Is there any "untouched" Nougat ROM available to flash for S-On devices running MM firmware?
By "untouched" I mean the minimum necessary changes to make things compatible.
Thank in advance.
btoledob said:
Hi all.
I've got an taiwanese HTC 10 which is on the MM firmware, but I wish to try the Nougat on a custom ROM.
I realise that there is plenty of ROMs, but it seems that's nobody intention to stay close to the stock experience.
Is there any "untouched" Nougat ROM available to flash for S-On devices running MM firmware?
By "untouched" I mean the minimum necessary changes to make things compatible.
Thank in advance.
Click to expand...
Click to collapse
...our rom looks and feels complete stock if you install it, we also use the stock htc kernel.
All modifications are optional and can be configured in our Tweaks control app or flashed over our hub.
If you still care about that then flash MaximusHD, that's really the closest to stock..still has some modifications like extenced APM and maybe some other.
Still not safisfied? Then flash the stock deodexed Dev Edition Rom. Fingerprint will be broken, flash this to fix it: https://www.androidfilehost.com/?fid=529152257862688644
not sure what you mean with "minimum necessary changes to make things compatible" doubt any sense roms around here break stock features.
j to the 4n said:
...our rom looks and feels complete stock if you install it, we also use the stock htc kernel.
All modifications are optional and can be configured in our Tweaks control app or flashed over our hub.
If you still care about that then flash MaximusHD, that's really the closest to stock..still has some modifications like extenced APM and maybe some other.
Still not safisfied? Then flash the stock deodexed Dev Edition Rom. Fingerprint will be broken, flash this to fix it: https://www.androidfilehost.com/?fid=529152257862688644
not sure what you mean with "minimum necessary changes to make things compatible" doubt any sense roms around here break stock features.
Click to expand...
Click to collapse
Thank you very much for the feedback.
I've tried your ROM, which is excelent, but I got a little problem with the camera app. If I take a picture on the Pro mode with RAW enabled, the RAW image does not follow the device orientation, and consequently the Google Photo app does not suggest enhances, because the RAW and the JPEG are different from each other. I need to take pictures only on landscape mode and only with the home button on the right side in order to work properly. As I never had the opportunity to test the completly stock Nougat ROM from HTC, I don't know if this problem is specific to your ROM or from the HTC's Nougat source code.
The other ROM that I've tried is LeeDroid. I found a bug on his ROM where the default audio profile does not turn ON when playing some music on my headphones, so everytime I need reenable my profile in order to make it to work again. The other minor thing is that he changed the wallpapers.
As I never had the opportunity to test the completely stock Nougat ROM from HTC, I can't be sure if those glitches are avoidable.
btoledob said:
Thank you very much for the feedback.
I've tried your ROM, which is excelent, but I got a little problem with the camera app. If I take a picture on the Pro mode with RAW enabled, the RAW image does not follow the device orientation, and consequently the Google Photo app does not suggest enhances, because the RAW and the JPEG are different from each other. I need to take pictures only on landscape mode and only with the home button on the right side in order to work properly. As I never had the opportunity to test the completly stock Nougat ROM from HTC, I don't know if this problem is specific to your ROM or from the HTC's Nougat source code.
The other ROM that I've tried is LeeDroid. I found a bug on his ROM where the default audio profile does not turn ON when playing some music on my headphones, so everytime I need reenable my profile in order to make it to work again. The other minor thing is that he changed the wallpapers.
As I never had the opportunity to test the completely stock Nougat ROM from HTC, I can't be sure if those glitches are avoidable.
Click to expand...
Click to collapse
the roms are based on an unreleased WWE 2.28 leak...the offical WWE version will be 2.4x. Since it's a leak there seem to be a few bugs still. Should be sorted on the official one.
If you can't wait, you could s-off, change to dev ed cid and mid and flash the US Unlocked RUU.
For the issues with raw images...disable the google photo app and install the A9 Sense 8 Gallery and photoenhancer available in venomhub and check if it solves the issues.
I've spent a bunch of time trying to understand why the modem in a particular E980 doesn't work in Cyanogenmod 12. Others should benefit from my efforts.
Searching reveals several posts about the modem issue, but quite a few of the responses are either links or references that require significant background to understand.
The community consensus is that one must flash "madmack's modem" when using CM with the E980 & variants. Without it, many phones can't enter deep sleep and thus drain the battery. Others can't use the modem at all.
(Madmack's modem post: https://forum.xda-developers.com/showthread.php?t=2430456)
(Current source of CyanogenMod 12.1: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html)
"Madmack's modem" is the image for the BM9615A-CEFWMAZM-3.0.113012. Some users had a driver for a CM9615A[...] variant instead. For those users, flashing the BM9615A driver allowed the phone to go into deep sleep. Hooray!
---
Unfortunately, other E980 owners have a completely different modem: the APQ8064/MDM 9x15M. In this case, flashing the BM9615A file doesn't help.
If your modem appeared as an APQ8064/MDM9x15M on stock, it appears as the BM9615A upon flashing CM12. Unfortunately, its still an APQ8064 on the inside. This makes it seem like CM 12.1 is hard-coded to the BM9615A modem. When CM tries to speak BM9615A-ese to an APQ8064, the result is "No Sim" (or rather intermittently detecting and dropping the SIM).
Flashing the BM9615A image on an APQ8064 doesn't help -- the modem can't understand itself. CM and the modem firmware may speak the same language, but the image that runs the modem isn't right for the hardware.
At least, thats what I think is happening. I would appreciate it if someone with experience could please let me know if my understanding is incorrect.
Until someone finds a way around this, those people whose modem is APQ8064/MDM9x15M on stock may want to hold off on trying the available roms. Most are based on CyanogenMod and thus can be expected to have the same problem.
I wrote this post both to consolidate information and to ask for help. Does anyone have a way of getting an E980 with a APQ8064/MDM9x15M to work with CM 12.1?
(Note: Tried Emmanuel's wild kernel. Didn't help.)
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
ShadySquirrel said:
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
Click to expand...
Click to collapse
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
facepalm5 said:
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
Click to expand...
Click to collapse
Which CM build are you trying to use?
ShadySquirrel said:
Which CM build are you trying to use?
Click to expand...
Click to collapse
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
facepalm5 said:
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
Click to expand...
Click to collapse
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
ShadySquirrel said:
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
Click to expand...
Click to collapse
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
facepalm5 said:
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
Click to expand...
Click to collapse
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Intended a direct reply. See below.
ShadySquirrel said:
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Click to expand...
Click to collapse
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
facepalm5 said:
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
Click to expand...
Click to collapse
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
ShadySquirrel said:
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
Click to expand...
Click to collapse
Thanks. I'll give it a try, but let me make sure that I understand which one. There are two mirrors on the EOL thread: basketbuild & androidfilehost.
The newest build on basketbuild is 02072016. Androidfilehost has a 021816, however there is a note in the EOL thread that 021916 shouls be deleted because it doesn't work. Is that the same as 021816 or is 021616 really the same as 021616?
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
ShadySquirrel said:
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
Click to expand...
Click to collapse
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
facepalm5 said:
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
Click to expand...
Click to collapse
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
ShadySquirrel said:
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
Click to expand...
Click to collapse
I can confirm the builds he has uploaded work for me, including the kernel fix for LMK which he posted this past year. ROM runs great